B VCS Exception Codes

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.

Short Messaging Exception Codes

The following exceptions are generated by the Short Messaging VCS.

SendSms.sendSms

SendSms.sendSms

Exception ID: SVC0001

Exception Type: service error

Cause: Any problem sending the sms.

SendSms.getSmsDeliveryStatus

SendSms.getSmsDeliveryStatus

Exception ID: SVC0002

Exception Type: invalid input error

Cause: No delivery status available for the given request identifier.

ReceiveSms.getReceivedSms

ReceiveSms.getReceivedSms

Exception ID: SVC0001

Exception Type: service error

Cause: Any problem retrieving an sms.

SmsNotificationManager.startSmsNotification

SmsNotificationManager.startSmsNotification

Exception ID: SVC0005

Exception Type: duplicate correlator

Cause: Duplicate correlator used when starting a notification.

Multimedia Messaging Exception Codes

The following the exceptions are generated by the Multimedia Messaging VCS.

SendMessage.sendMessage

SendMessage.sendMessage

Exception ID: SVC0001

Exception Type: service error

Cause: Any problem sending the mms.

SendMessage.getMessageDeliveryStatus

SendMessage.getMessageDeliveryStatus

Exception ID: SVC0002

Exception Type: invalid input error

Cause: The requestIdentifier is invalid.

ReceiveMessage.getMessage

ReceiveMessage.getMessage

Exception ID: SVC0002

Exception Type: invalid input error

Cause: The messageRefIdentifier is invalid.

ReceiveMessage.getReceivedMessage

ReceiveMessage.getReceivedMessages

Exception ID: SVC0002

Exception Type: invalid input error

Cause: The registrationIdentifier is invalid.

MessageNotificationManager.startMessageNotification

MessageNotificationManager.startMessageNotification

Exception ID: SVC0005

Exception Type: duplicate correlator

Cause: The same correlator is registered multiple times.

MessageNotitifcationManager.stopMessageNotification

MessageNotificationManager.stopMessageNotification

Exception ID: SVC0002

Exception Type: invalid input error

Cause: The correlator is invalid.

Terminal Location Exception Codes

The following exceptions are generated by the Terminal Location VCS.

TerminalLocation.getLocation

TerminalLocation.getLocation

Exception ID: SVC0002

Exception Type: invalid input error

Cause: Address is null.

TerminalLocation.getLocation

Exception ID: SVC0004

Exception Type: invalid address error

Cause: No terminal with specified address.

TerminalLocation.getLocationForGroup

Exception ID: POL0003

Exception Type: too many addresses error

Cause: Too many addresses specified.

TerminalLocation.getLocation

Exception ID: POL0230

Exception Type:requested accuracy not supported

Cause: The requestedAccuracy or acceptableAccuracy is too low.

TerminalLocation.getTerminalDistance

TerminalLocation.getTerminalDistance

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.

TerminalLocation.getTerminalDistance

Exception ID: SVC0004

Exception Type: invalid address error

Cause: No terminal with specified address.

TerminalLocationNotificationManager.startGeographicalNotification

TerminalLocationNotificationManager.startGeographicalNotification

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.

TerminalLocationNotificationManager.startGeographicalNotification

Exception ID: SVC0004

Exception Type: invalid address error

Cause: No valid addresses provided.

TerminalLocationNotificationManager.startGeographicalNotification

Exception ID: SVC0005

Exception Type: duplicate correlator

Cause: The same correlator is registered multiple times.

TerminalLocationNotificationManager.startGeographicalNotification

Exception ID: POL0003

Exception Type: too many addresses error

Cause: Too many addresses provided.

TerminalLocationNotificationManager.startGeographicalNotification

Exception ID: POL0004

Exception Type: unlimited notifications not supported

Cause: Count equals zero.

TerminalLocationNotificationManager.startGeographicalNotification

Exception ID: POL0005

Exception Type: too many notifications requested

Cause: Count is too high.

TerminalLocationNotificationManager.startGeographicalNotification

Exception ID: POL0009

Exception Type: invalid frequency error

Cause: Invalid frequency requested.

TerminalLocationNotificationManager.startGeographicalNotification

Exception ID: POL0230

Exception Type: requested accuracy not supported

Cause: The requestedAccuracy or acceptableAccuracy is too low.

TerminalLocationNotificationManager.startGeographicalNotification

Exception ID: POL0231

Exception Type: geographic notification error

Cause: Geographic notification is not available.

TerminalLocationNotificationManager.startPeriodicNotification

TerminalLocationNotificationManager.startPeriodicNotification

Exception ID: SVC0002

Exception Type: invalid input error

Cause: No callback endpoint or correlator provided.

TerminalLocationNotificationManager.startPeriodicNotification

Exception ID: SVC0004

Exception Type: invalid address error

Cause: No terminal with specified address.

TerminalLocationNotificationManager.startPeriodicNotification

Exception ID: SVC0005

Exception Type: duplicate correlator

Cause: The same correlator is registered multiple times.

TerminalLocationNotificationManager.startPeriodicNotification

Exception ID: POL0003

Exception Type: too many addresses error

Cause: Too many addresses provided.

TerminalLocationNotificationManager.startPeriodicNotification

Exception ID: POL0009

Exception Type: invalid frequency error

Cause: Invalid frequency requested.

TerminalLocationNotificationManager.startPeriodicNotification

Exception ID: POL0232

Exception Type: periodic notification error

Cause: Periodic notification is not available.

TerminalLocationNotificationManager.endNotification

TerminalLocationNotificationManager.endNotification

Exception ID: SVC0002

Exception Type: invalid input error

Cause: Invalid correlator.

Terminal Status Exception Codes

The following exceptions are generated by the Terminal Status VCS.

TerminalStatus.getStatus

TerminalStatus.getStatus

Exception ID: SVC0002

Exception Type: invalid input error

Cause: Address is null.

TerminalStatus.getStatus

Exception ID: SVC0004

Exception Type: invalid address error

Cause: No valid addresses provided.

TerminalStatus.getStatusForGroup

TerminalStatus.getStatusForgroup

Exception ID: SVC0002

Exception Type: invalid input error

Cause: Address is null.

TerminalStatus.getStatusForGroup

Exception ID: SVC0004

Exception Type: invalid address error

Cause: No valid addresses provided.

TerminaStatus.getStatusForGroup

Exception ID: POL0003

Exception Type: too many addresses error

Cause: Too many addresses provided.

TerminalStatusNotificationManager.startNotification

TerminalStatusNotificationManager.startNotification

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.

TerminalStatusNotificationManager.startNotification

Exception ID: SVC0004

Exception Type: invalid address error

Cause: No valid addresses provided.

TerminalStatusNotificationManager.startNotification

Exception ID: SVC0005

Exception Type: duplicate correlator

Cause: The same correlator is registered multiple times.

TerminalStatusNotificationManager.startNotification

Exception ID: POL0003

Exception Type: too many addresses error

Cause: Too many addresses provided.

TerminalStatusNotificationManager.startNotification

Exception ID: POL0004

Exception Type: unlimited notifications not supported

Cause: Count equals zero.

TerminalStatusNotificationManager.startNotification

Exception ID: POL0005

Exception Type: too many notifications requested

Cause: Count is too high.

TerminalStatusNotificationManager.startNotification

Exception ID: POL0009

Exception Type: invalid frequency error

Cause: Invalid frequency requested.

TerminalStatusNotificationManager.startNotification

Exception ID: POL0200

Exception Type: busy criterion not supported

Cause: isBusyAvailable is set to false and criteria include busy.

TerminalStatusNotificationManager.endNotification

TerminalStatusNotificationManager.endNotification

Exception ID: SVC0002

Exception Type: invalid input error

Cause: No valid correlator provided.

Third Party Call Exception Codes

The following exceptions are generated by the Third Party Call VCS.

ThirdPartyCallImpl.cancelCallRequest

ThirdPartyCallImpl.cancelCallRequest

Exception ID: SVC0002

Exception Type: invalid input value for call identifier

Cause: Call identifier is null.

ThirdPartyCallImpl.cancelCallRequest

Exception ID: SVC0260

Exception Type: call already connected

Cause: The specified call has already connected and can not be canceled.

ThirdPartyCallImpl.endCall

ThirdPartyCallImpl.endCall

Exception ID: SVC0002

Exception Type: invalid input value for call identifier

Cause: Call identifier is null.

ThirdPartyCallImpl.endCall

Exception ID: SVC261

Exception Type: call already terminated

Cause: The specified call has already terminated.

ThirdPartyCallImpl.getCallInformation

ThirdPartyCallImpl.getCallInformaton

Exception ID: SVC0001

Exception Type: service error

Cause: Called party or callee party status is invalid.

ThirdPartyCallImpl.getCallInformaton

Exception ID: SVC0002

Exception Type: invalid input value for call identifier

Cause: Call identifier is null.

ThirdPartyCallImpl.makeCall

ThirdPartyCallImpl.makeCall

Exception ID: SVC0002

Exception Type: invalid input value for call identifier

Cause: Call identifier is null.

ThirdPartyCallImpl.sendMessage

ThirdPartyCallImpl.sendMessage

Exception ID: SVC0001

Exception Type: service error

Cause: Called party or callee party status is invalid.

ReceiveMessage.makeCall

ReceiveMessage.makeCall

Exception ID: SVC0004

Exception Type: invalid input value

Cause: Called party or callee party address is invalid.

Payment Exception Codes

The following exceptions are generated by the Payment VCS.

AmountCharging.ChargeAmount

AmountCharging.ChargeAmount

Exception ID: SVC0002

Exception Type: invalid input value

Cause: The user ID or some other parameter value is invalid.

AmountCharging.ChargeAmount

Exception ID: SVC0007

Exception Type: invalid charging information

Cause: The charging information is invalid.

AmountCharging.ChargeAmount

Exception ID: SVC0270

Exception Type: charge failed

Cause: The charge failed.

AmountCharging.RefundAmount

AmountCharging.RefundAmount

Exception ID: SVC0002

Exception Type: invalid input value

Cause: The user ID or some other parameter value is invalid.

AmountCharging.RefundAmount

Exception ID: SVC0007

Exception Type: invalid charging information

Cause: The charging information is invalid.

AmountCharging.RefundAmount

Exception ID: SVC0270

Exception Type: charge failed

Cause: The charge failed.

AmountCharging.ChargeSplitAmount

AmountCharging.ChargeSplitAmount

Exception ID: SVC0002

Exception Type: invalid input value

Cause: The user ID or some other parameter value is invalid.

AmountCharging.ChargeSplitAmount

Exception ID: SVC0007

Exception Type: invalid charging information

Cause: The charging information is invalid.

AmountCharging.ChargeSplitAmount

Exception ID: SVC0270

Exception Type: charge failed

Cause: The charge failed.

AmountCharging.ChargeSplitAmount

Exception ID: SVC0271

Exception Type: invalid sum of percent allocations

Cause: The sum of the percentage allocations does not equal 100.

AmountCharging.ChargeSplitAmount

Exception ID: POL0250

Exception Type: too many end-user identifiers

Cause: The number of end-user identifiers exceeds defined policy.

AmountCharging.ChargeSplitAmount

Exception ID: POL0251

Exception Type: split charging not supported

Cause: Split charging is not supported by defined policy.

ReserveAmountCharging.ReserveAmount

ReserveAmountCharging.ReserveAmount

Exception ID: SVC0002

Exception Type: invalid input value

Cause: The user ID or some other parameter value is invalid.

ReserveAmountCharging.ReserveAmount

Exception ID: SVC0007

Exception Type: invalid charging information

Cause: The charging information is invalid.

ReserveAmountCharging.ReserveAmount

Exception ID: SVC0270

Exception Type: charge failed

Cause: The charge failed.

ReserveAmountCharging.ReserveAdditionalAmount

ReserveAmountCharging.ReserveAdditionalAmount

Exception ID: SVC0002

Exception Type: invalid input value

Cause: The user ID or some other parameter value is invalid.

ReserveAmountCharging.ReserveAdditionalAmount

Exception ID: SVC0007

Exception Type: invalid charging information

Cause: The charging information is invalid.

ReserveAmountCharging.ReserveAdditionalAmount

Exception ID: SVC0270

Exception Type: charge failed

Cause: The charge failed.

ReserveAmountCharging.ChargeReservation

ReserveAmountCharging.ChargeReservation

Exception ID: SVC0002

Exception Type: invalid input value

Cause: The user ID or some other parameter value is invalid.

ReserveAmountCharging.ChargeReservation

Exception ID: SVC0007

Exception Type: invalid charging information

Cause: The charging information is invalid.

ReserveAmountCharging.ChargeReservation

Exception ID: SVC0270

Exception Type: charge failed

Cause: The charge failed.

ReserveAmountChargingReleaseReservation

ReserveAmountCharging.ReleaseReservation

Exception ID: SVC0002

Exception Type: invalid input value

Cause: The user ID or some other parameter value is invalid.

Binary SMS Exception Codes

The following exceptions are generated by the Short Messaging VCS.

SendBinarySms.sendMessage

SendBinarySms.sendMessage

Exception ID:

Exception Type:

Cause: Any problem sending the binary SMS.

BinarySmsNotificationManager.startMessageNotification

BinarySmsNotificationManager.startMessageNotification

Exception ID:

Exception Type: duplicate correlator

Cause: Duplicate correlator used when starting a notification.

BinarySmsNotificationManager.stopMessageNotification

Exception ID:

Exception Type: invalid correlator

Cause: The correlator is invalid.