New feature
Intermediate delivery reports on GW250
Intermediate delivery reports will give you better control on your messages.
Updated:
(4.12.2006)
Intermediate delivery reports will give you a status for the messages when the message could not be delivered to the user on first attempt. The message will be stored in the SMSC and the delivery status will be sent.
ViaNett have full support for intermediate delivery reports on GW220 and GW250. It's also partly supported on GW230.
You will find prices and conditions on this page: http://smsnew.vianett.com/kat/000046.asp
Here is a list of GW250 status codes (each gateway has different sets with status codes). These status codes will also be available in the statistics under message details for each message.
1 |
unknownSubscriber |
2 |
unknownBaseStation |
3 |
unknownMSC |
5 |
unidentifiedSubscriber. |
6 |
absentsubscriberSM |
7 |
unknownEquipment |
8 |
roamingNotAllowed |
9 |
illegalSubscriber |
10 |
bearerServiceNotProvisioned |
11 |
teleserviceNotProvisioned |
12 |
illegalEquipment |
13 |
callBarred |
14 |
forwardingViolation |
15 |
cugReject |
16 |
illegalSSOperation |
17 |
ssErrorStatus |
18 |
ssNotAvailable |
19 |
ssSubscriptionViolation |
20 |
ssIncompatibility |
21 |
facilityNotSupported |
23 |
invalidTargetBaseStation |
24 |
noRadioResourceAvailable |
25 |
noHandoverNumberAvailable |
26 |
subsequentHandoverFailure |
27 |
absentSubscriber. The mobile is switched of or not reachable. |
28 |
incompatibleTerminal |
29 |
shortTermDenial |
30 |
longTermDenial |
31 |
subscriberBusyForMTSMS |
32 |
smDeliveryFailure |
33 |
messageWaitingListFull |
34 |
systemFailure |
35 |
dataMissing |
36 |
unexpectedDataValue |
37 |
pwRegistrationFailure |
38 |
negativePWCheck |
39 |
noRoamingNumberAvailable |
40 |
tracingBufferFull |
43 |
numberOfPWAttemptsViolation |
44 |
numberChanged |
45 |
busySubscriber |
46 |
noSubscriberReply |
47 |
forwardingFailed |
48 |
orNotAllowed |
49 |
atiNotAllowed |
50 |
noGroupCallNumberAvailable |
51 |
resourceLimitation |
52 |
unauthorizedRequestingNetwork |
53 |
unauthorizedLCSClient |
54 |
positionMethodFailure |
58 |
unknownOrUnreachableLCSClient |
71 |
unknownAlphabet |
72 |
ussdBusy |
86 |
subscriberLocationReport |
8448 |
Unrecognized component |
8449 |
Mistyped component |
8450 |
Badly structured component |
8704 |
Duplicate invoke ID |
8705 |
Unrecognized operation |
8706 |
Mistyped parameter |
8707 |
Resource limitation |
8708 |
Initiating release |
8709 |
Unrecognized linked ID |
8710 |
Linked response unexpected |
8711 |
Unexpected linked operation |
8960 |
Unrecognized invoke ID |
8961 |
Return Result unexpected |
8962 |
Mistyped parameter |
9216 |
Unrecognized invoke ID |
9217 |
Return Error unexpected |
9218 |
Unrecognized error |
9219 |
Unexpected error |
9220 |
Mistyped parameter |
24576 |
memoryCapacityExceeded. SIM card full. |
24577 |
equipmentProtocolError |
24578 |
equipmentNotSMEquipped |
24579 |
unknownServiceCentre |
24580 |
scCongestion |
24581 |
invalidSMEAddress |
24582 |
subscriberNotSCSubscriber |
32768 |
Unrecognized message type |
32769 |
Unrecognized transaction ID |
32770 |
Badly formatted transaction portion |
32771 |
Incorrect transaction portion |
32772 |
Resource limitation |
32779 |
Dialogue collision |
32784 |
Node not reachable. Routing failure (invalid MSISDN etc.). |
49153 |
scAddressNotIncluded. SC address not included in message waiting list. |
49154 |
mnrfSet. Mobile subscriber not reachable. |
49156 |
mcefSet.SIM card full. |
49160 |
mnrgSet. Mobile station not reachable for GPRS. |
57345 |
The dialogue has received a MAPDELIMITER unexpectedly. |
57346 |
The dialogue has received a MAPSERVICEREQUEST unexpectedly. |
57360 |
Could not decode an ASN.1 encoded parameter. |
57361 |
Could not ASN.1 encode a parameter. |
57376 |
Dialogue queue size exceeded. |
57408 |
Dialogue timed out, i.e. the far side did not respond or there is a network problem. |
57472 |
Invalid delivery outcome (< 0 or > 2 on any MAP level, or 1 on MAP 1) |
57473 |
Invalid destination address |
65535 |
Internal Error |
Print the article