Code

Meaning

200

OK. The message was processed and billed successfully. If external_ackwanted is set to false for a message, this ackcode will not be returned to content provider. Revenuesplit according to the agreement.

210

The message was successfully sent, but billing of the message failed on the first attempt. The message will be attempted billed later (a configurable maximum number of times). No point in resending message, end user has received it. This acknowledgement does not guarantee revenuesplit, cf. the Main Agreement art. 11.

Messages generating this type of ack will eventually generate an additional ack with the same messageid when the message is done (either billed succesfully or reached max number of attempts). This ack will also be sent to the content provider. If external_ackwanted is set to false for a message, 210 will not be returned to content provider. The additional ack will in this case also not be returned to content provider in cases where billing eventually succeeds (ackcode 200).

220

The message was successfully sent, but real time billing was not done because of problems with rating system. The message will be attempted billed later (a configurable maximum number of times). No point in resending message, end user has received it. This acknowledgement does not guarantee revenuesplit, cf. the Main Agreement art. 11.

Messages generating this type of ack will eventually generate an additional ack with the same messageid when the message is done (either billed succesfully or billed failed). This ack will also be sent to the content provider. If external_ackwanted is set to false for a message, 220 will not be returned to content provider. The additional ack will in this case also not be returned to content provider in cases where billing eventually succeeds (ackcode 200).

230

The message was successfully sent, but billing was not done. The message was not supposed to be billed. End user has received message. All messages sent with free price categories (eg. KAT20, CPA000) will generate this reply code, as well as all messages sent from a content provider to another content provider, and all positioning requests from content provider.

701

Checksum error in message to SMSC (message not sent to end user)

702

Syntax error in message to SMSC. Possibly wrong header in binary messages (message not sent to end user)

703

Operation not supported by system (SMSC). Possibly an error in the header field of binary messages (message not sent to end user).

704

Operation not allowed (by SMSC). Possibly an error in the header field of binary messages or message buffer in SMSC is full (message not sent to end user).

705

Call barring active. The receiver of the message is not allowed to receive any more messages from the SMSC at the moment (message not sent to end user).

706

Invalid ADC. The receiver number of the message is invalid according to the SMSC (message not sent to end user).

707

Other SMSC negative acknowledges.

719

Acknowledgement from SMS-C too long.

720

Not in use.

721

Message not accepted by SMSC (message not sent to end user).

722

Not in use.

723

From SMSC: The message was empty (message not sent to end user).

724

From SMSC: The message was too long (message not sent to end user).

725

From SMSC: Invalid message (message not sent to end user).

726

Acknowledge was not received from SMSC

727

Invalid acknowledgement from SMSC

728

Not in use.

729

Not in use.

730

Undefined error in communication with SMSC

800

The price group is illegal (message not sent to end user), ie. price group is not defined as a legal price group for the content provider in CPA.

801

The billing account is illegal (message not sent to end user). If the content provider is configured in CPA to be able to set the account which is to be billed for the message (in the billingmsn field of the message), this reply code may be returned if a check against a list of predefined legal billing accounts in CPA fails, or if the billingmsn field is missing.

802

General internal system error when validating message (message not sent to end user). Error occurred while checking billing type, billing account and price group of the message.

803

The message is not a valid message (message not sent to end user). Error occurred during converting message from JMS message to CPA message.

804

Message distribution rejected on the last attempt. The message was tried resent several times (configurable number of times), but distribution failed. See the field ack_description for information on what kind of error that occurred in CPA leading to resending. Message not sent to end user.

805

Content provider’s attempt to send a message to another content provider was rejected. In order to be able to send to another content provider this has to be configured in CPA.

806

No sender information found. Message not sent to end-user. Possible reasons:

• Large account is to be set as sender of message, but large account for content provider not found in CPA, and sno missing in message.
• Sno is to be checked against a list of legal sender accounts in CPA, but sno missing in message.
• Anyone can be set as sender of message, but sno missing in message.

807

The parameter sno in message not a legal sender account for content provider (check against a list in CPA), message not sent to end-user.

808

Sender of message to be set as the same as receiver of message, but msn missing, message not sent to end-user.

809

Error when trying to get the MSISDN number from a Static Id value sent in message from content provider (for positioning services).

901

Requested subscription service is unknown in the subscription server

902

CPA is not authorized to access the CPSC server

903

CPA failed to connect to the Subscription server (CPSC).

1000

Not in use.

1001

Special account. Billing is turned off, message sent to end-user.

1002

Illegal billing parameters.

1003

Unable to connect to the billing system when trying to recall billing event (when distribution failed), e.g. timeout when trying to connect to billing system.

If timeout occurs when trying to bill, the message will be sent, the billing event will be put in a queue, and tried to be billed later. Then the reply code 220 will be returned instead of 1003 (reply code 220 is described above).

1004

When billing event has been retried a configurable maximum number of times without being billed (because of error from the billing system), this code is eventually logged in the CPA system. This is actually no reply code to the content provider; the content provider will receive the reply code 210 the first time the billing event is put in queue, and no other reply codes for that message.

1005

Prepaid customer has no balance left (message not sent to end user).

1006

Invalid customer account (message not sent to end user). The customer account, which is to be billed for the message, is not a valid Telenor Mobil customer anymore. If this is a subscription/alert type of service, the content provider should consider deleting this account from its database.

1007

Invalid pricecategory in billing system.

1008

Billing failed because of an unspecified functional error, message sent to end user.

1009

Customer is barred (message not sent to end user). The customer account is for some reason blocked by Telenor Mobil (stolen mobile, missing payment etc).

1050

Not in use.

1051

Not in use.

1052

Not in use.