Oracle® Communications Services Gatekeeper SDK User's Guide Release 5.0 Part Number E17722-02 |
|
|
View PDF |
This appendix lists the exceptions codes generated by the ATE VCSs.
Exceptions with an SVC prefix indicate an error against the service. Exceptions with a POL prefix indicate a violation of a policy enforcement. See Managing Service-Level Agreements for information about setting policy enforcements in the VCS.
The following exceptions are generated by the Short Messaging VCS.
Exception ID: SVC0001
Exception Type: service error
Cause: Any problem sending the sms.
Exception ID: SVC0002
Exception Type: invalid input error
Cause: No delivery status available for the given request identifier.
The following the exceptions are generated by the Multimedia Messaging VCS.
Exception ID: SVC0001
Exception Type: service error
Cause: Any problem sending the mms.
Exception ID: SVC0002
Exception Type: invalid input error
Cause: The requestIdentifier is invalid.
Exception ID: SVC0002
Exception Type: invalid input error
Cause: The messageRefIdentifier is invalid.
Exception ID: SVC0002
Exception Type: invalid input error
Cause: The registrationIdentifier is invalid.
The following exceptions are generated by the Terminal Location VCS.
Exception ID: SVC0002
Exception Type: invalid input error
Cause: Address is null.
Exception ID: SVC0004
Exception Type: invalid address error
Cause: No terminal with specified address.
Exception ID: POL0003
Exception Type: too many addresses error
Cause: Too many addresses specified.
Exception ID: POL0230
Exception Type:requested accuracy not supported
Cause: The requestedAccuracy or acceptableAccuracy is too low.
Exception ID: SVC0002
Exception Type: invalid input error
Cause: Address is null, or latitude is not in [-90, 90] range, or longitude is not in [-180, 180] range.
Exception ID: SVC0004
Exception Type: invalid address error
Cause: No terminal with specified address.
Exception ID: SVC0002
Exception Type: invalid input error
Cause: No callback endpoint or correlator provided, or latitude is not in [-90, 90] range, or longitude is not in [-180, 180] range.
Exception ID: SVC0004
Exception Type: invalid address error
Cause: No valid addresses provided.
Exception ID: SVC0005
Exception Type: duplicate correlator
Cause: The same correlator is registered multiple times.
Exception ID: POL0003
Exception Type: too many addresses error
Cause: Too many addresses provided.
Exception ID: POL0004
Exception Type: unlimited notifications not supported
Cause: Count equals zero.
Exception ID: POL0005
Exception Type: too many notifications requested
Cause: Count is too high.
Exception ID: POL0009
Exception Type: invalid frequency error
Cause: Invalid frequency requested.
Exception ID: POL0230
Exception Type: requested accuracy not supported
Cause: The requestedAccuracy or acceptableAccuracy is too low.
Exception ID: POL0231
Exception Type: geographic notification error
Cause: Geographic notification is not available.
Exception ID: SVC0002
Exception Type: invalid input error
Cause: No callback endpoint or correlator provided.
Exception ID: SVC0004
Exception Type: invalid address error
Cause: No terminal with specified address.
Exception ID: SVC0005
Exception Type: duplicate correlator
Cause: The same correlator is registered multiple times.
Exception ID: POL0003
Exception Type: too many addresses error
Cause: Too many addresses provided.
Exception ID: POL0009
Exception Type: invalid frequency error
Cause: Invalid frequency requested.
Exception ID: POL0232
Exception Type: periodic notification error
Cause: Periodic notification is not available.
The following exceptions are generated by the Terminal Status VCS.
Exception ID: SVC0002
Exception Type: invalid input error
Cause: Address is null.
Exception ID: SVC0004
Exception Type: invalid address error
Cause: No valid addresses provided.
Exception ID: SVC0002
Exception Type: invalid input error
Cause: Address is null.
Exception ID: SVC0004
Exception Type: invalid address error
Cause: No valid addresses provided.
Exception ID: POL0003
Exception Type: too many addresses error
Cause: Too many addresses provided.
Exception ID: SVC0002
Exception Type: invalid input error
Cause: No callback endpoint or correlator provided, or latitude is not in [-90, 90] range, or longitude is not in [-180, 180] range.
Exception ID: SVC0004
Exception Type: invalid address error
Cause: No valid addresses provided.
Exception ID: SVC0005
Exception Type: duplicate correlator
Cause: The same correlator is registered multiple times.
Exception ID: POL0003
Exception Type: too many addresses error
Cause: Too many addresses provided.
Exception ID: POL0004
Exception Type: unlimited notifications not supported
Cause: Count equals zero.
Exception ID: POL0005
Exception Type: too many notifications requested
Cause: Count is too high.
Exception ID: POL0009
Exception Type: invalid frequency error
Cause: Invalid frequency requested.
Exception ID: POL0200
Exception Type: busy criterion not supported
Cause: isBusyAvailable
is set to false
and criteria include busy
.
The following exceptions are generated by the Third Party Call VCS.
Exception ID: SVC0002
Exception Type: invalid input value for call identifier
Cause: Call identifier is null.
Exception ID: SVC0260
Exception Type: call already connected
Cause: The specified call has already connected and can not be canceled.
Exception ID: SVC0002
Exception Type: invalid input value for call identifier
Cause: Call identifier is null.
Exception ID: SVC261
Exception Type: call already terminated
Cause: The specified call has already terminated.
Exception ID: SVC0001
Exception Type: service error
Cause: Called party or callee party status is invalid.
Exception ID: SVC0002
Exception Type: invalid input value for call identifier
Cause: Call identifier is null.
Exception ID: SVC0002
Exception Type: invalid input value for call identifier
Cause: Call identifier is null.
The following exceptions are generated by the Payment VCS.
Exception ID: SVC0002
Exception Type: invalid input value
Cause: The user ID or some other parameter value is invalid.
Exception ID: SVC0007
Exception Type: invalid charging information
Cause: The charging information is invalid.
Exception ID: SVC0270
Exception Type: charge failed
Cause: The charge failed.
Exception ID: SVC0002
Exception Type: invalid input value
Cause: The user ID or some other parameter value is invalid.
Exception ID: SVC0007
Exception Type: invalid charging information
Cause: The charging information is invalid.
Exception ID: SVC0270
Exception Type: charge failed
Cause: The charge failed.
Exception ID: SVC0002
Exception Type: invalid input value
Cause: The user ID or some other parameter value is invalid.
Exception ID: SVC0007
Exception Type: invalid charging information
Cause: The charging information is invalid.
Exception ID: SVC0270
Exception Type: charge failed
Cause: The charge failed.
Exception ID: SVC0271
Exception Type: invalid sum of percent allocations
Cause: The sum of the percentage allocations does not equal 100.
Exception ID: POL0250
Exception Type: too many end-user identifiers
Cause: The number of end-user identifiers exceeds defined policy.
Exception ID: POL0251
Exception Type: split charging not supported
Cause: Split charging is not supported by defined policy.
Exception ID: SVC0002
Exception Type: invalid input value
Cause: The user ID or some other parameter value is invalid.
Exception ID: SVC0007
Exception Type: invalid charging information
Cause: The charging information is invalid.
Exception ID: SVC0270
Exception Type: charge failed
Cause: The charge failed.
Exception ID: SVC0002
Exception Type: invalid input value
Cause: The user ID or some other parameter value is invalid.
Exception ID: SVC0007
Exception Type: invalid charging information
Cause: The charging information is invalid.
Exception ID: SVC0270
Exception Type: charge failed
Cause: The charge failed.
Exception ID: SVC0002
Exception Type: invalid input value
Cause: The user ID or some other parameter value is invalid.
Exception ID: SVC0007
Exception Type: invalid charging information
Cause: The charging information is invalid.
Exception ID: SVC0270
Exception Type: charge failed
Cause: The charge failed.
The following exceptions are generated by the Short Messaging VCS.
Exception ID:
Exception Type:
Cause: Any problem sending the binary SMS.
Exception ID:
Exception Type: duplicate correlator
Cause: Duplicate correlator used when starting a notification.
Exception ID:
Exception Type: invalid correlator
Cause: The correlator is invalid.