SonicMQ, Telenor

ErrorCodeShortDescriptionLongDescription
200OKOK. The message was processed and billed successfully.
210The message was successfully sent, but billing of the message failed on the first attemptThe 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.
220The message was successfully sent, but real time billing was not doneThe 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.
230The message was successfully sent, but billing was not done.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) will generate this reply code, as well as all messages sent from a content provider to another content provider.
701Checksum errorChecksum error in message to SMSC (message not sent to end user)
702Syntax ErrorSyntax error in message to SMSC. Possibly wrong header in binary messages (message not sent to end user)
703Operation not supportedOperation not supported by system (SMSC). Possibly an error in the header field of binary messages (message not sent to end user).
704Operation not allowedOperation not allowed (by SMSC). Possibly an error in the header field of binary messages (message not sent to end user).
705Call barring active.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).
706Invalid ADCInvalid ADC. The receiver number of the message is invalid according to the SMSC (message not sent to end user).
707Other SMSC negative ackOther SMSC negative acknowledges.
719Acknowledgement too longAcknowledgement from SMS-C too long.
720No contact with SMSCNo contact with SMS-C (message not sent to end user).
721Message not acceptedMessage not accepted by SMSC (message not sent to end user).
722Message too oldFrom SMSC: Message too old (message not sent to end user).
723Message emptyFrom SMSC: The message was empty (message not sent to end user).
724Message too longFrom SMSC: The message was too long (message not sent to end user).
725Invalid messageFrom SMSC: Invalid message (message not sent to end user).
726Ack not received from SMSCAcknowledge was not received from SMSC
727Invalid ackInvalid acknowledgement from SMSC
728Invalid a-numberFrom SMSC: Invalid a-number (message not sent to end user).
729IO error between CPA and SMSCIO error between CPA and SMS-C (message not sent to end user).
730Undefined errorUndefined error in communication with SMSC
800Illegal pricegroupThe 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.
801Illegal billing accountThe 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.
802General system errorGeneral 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.
803Invalid messageThe message is not a valid message (message not sent to end user). Error occurred during converting message from JMS message to CPA message.
804Message rejectedMessage 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.
805Message to another provider was recectedContent 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.
806No sender information foundNo sender information found. Message not sent to end-user.
807The parameter sno in message not a legal sender account for content providerThe parameter sno in message not a legal sender account for content provider (check against a list in CPA), message not sent to end-user.
808Sender of message to be set as the same as receiver of message, but msn missingSender of message to be set as the same as receiver of message, but msn missing, message not sent to end-user.
809Error when trying to get the MSISDN number from a Static Id value sent in messageError when trying to get the MSISDN number from a Static Id value sent in message from content provider (for positioning services).
901Requested subscription service is unknown in the subscription serverRequested subscription service is unknown in the subscription server
1000Successfully sent, no billingEITHER: The message was successfully sent, but billing was not done; billing is only simulated in CPA (configurable), a special “no-billing” account customer is specified as billing account, or some illegal parameters was sent to the billing system. OR: Sending of message failed, but the end user was billed, and the recall of the billing event failed.
1001Not in useNot in use.
1002Not in useNot in use.
1003No contact with the billing systemUnable 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).
1004Billing problemsWhen 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.
1005No balancePrepaid customer has no balance left (message not sent to end user).
1006Invalid customer accountInvalid 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.
1007Invalid pricegroupInvalid pricecategory in billing system.
1008Billing failedBilling failed because of an unspecified functional error, message sent to end user.
1009Customer is barredCustomer is barred (message not sent to end user). The customer account is for some reason blocked by Telenor Mobil (stolen mobile, missing payment etc).
1010User not allowed to buy content.The user is not allowed to buy content.
1020AgeNotAllowedThe parameter "age" or "priceplan" is not allowed for the content provider in CPA
1021AgeMismatchThe parameter "age" or "priceplan" doesn't match the customer settings in the customer database.
1022Unable to verify ageBilling failed because CPA was unable to verify the customers age. Only applicable when parameter "age" is set.
1023Unable to verify priceplanBilling failed because CPA was unable to verify the customers priceplan. Only applicable when parameter "priceplan" is set
1024Customer did not exist in COSBilling failed because customer did not exist in COS. Only applicable when parameter "age" and/or "priceplan" is set.
1050Internal technical problemInternal technical problems regarding communication with subscription system, the message will be tried again. No point in resending message.
1051Invalid subscriptionInvalid subscription (message not sent to end-user). This reply code could indicate that some kind of country code is included in the customer account to be billed. The customer account must consist of 8 digits. The customer account alternatively may not be a TnM customer.
1052Subscription blockedSubscription blocked in CPA (message not sent to end-user). For questions about the block reason, please contact TnM customer service.