Disclaimer: These archives are mirrored from smsforum.net in 2007 before the forum got closed. Please only part of the forum is available here.
For any clarifications regarding these archives you can contact us at http://www.telecomspace.com/contact.

      TELECOMSPACE HOME PAGE         TELECOM DISCUSSION FORUM          CONTACT

+  SMS Forum Online Discussion
|-+  SMS Technologies
| |-+  GSM-Related (Moderator: SMS Forum Support)
| | |-+  SMS rejection and error cause mapping
« previous next »
Pages: [1] Go Down Print
Author Topic: SMS rejection and error cause mapping  (Read 620 times)
thinker
Jr. Member
**
Offline Offline

Posts: 9


« on: August 10, 2006, 15:23:42 UTC »

Scenario -
subscriber send a SMS
before reaching to the SMSC there is a IN service that checks if the subs is allowed to send SMS to the particular number, if blocked then IN service releases the SMScall and send back the cause value to the MSC.
Now my ques is -
does the MSC send that cause value with its text description to the MS?
or MSC just send the cause value to the MS and MS display the text associated with the cause?
Does it mean that the error cause value interpretation is done at the MS?
Also is it possible to define a new error cause value and associated text such that in some special cases user will recieve different error text?
Please highlight.
Thanks
Logged
SMS Forum Support
SMS Forum Support
Administrator
Sr. Member
*****
Offline Offline

Posts: 1754


WWW
« Reply #1 on: August 10, 2006, 18:49:33 UTC »

All error passing MAP is by number and not text.. and while the standards can evolve.. there is no notion of customising such error codes on a per-product basis.

Many systems that wish to interact back to the user, just send back a new message after the rejection.
Logged

Regards,
   Cormac Long
   Webmaster & Technical Enquiry Moderator,
   SMS Forum

thinker
Jr. Member
**
Offline Offline

Posts: 9


« Reply #2 on: August 10, 2006, 20:59:29 UTC »

then how do we see those messages back on MS saying "message failed" or "message could not be deliverred" or "message sent".
is it the MS that interpret those numeric cause values sent by MSC?
Logged
RussCrush
Sr. Member
****
Offline Offline

Posts: 66



« Reply #3 on: August 11, 2006, 02:08:28 UTC »

There are 2 reasons why you get the "Message failed" response on the phone.

Reject or timeout.

The SMSC launches an SRI_SM to the number that you are sending to, and a response comes back with routing information (SMSC address) on which HLR the sub is assigned to. 

The SMSC then launches an MO_FSM toward the SMSC that has the sub, and gets a response back indicating that the message: Passed or Failed. Failures can range from the receiving phone's memory is full (temporary failure) to the phone does not support SMS (permanent failure). This response is passed to the phone as the generic "Message failed"

If you send a message and the phone sits there for about 30 seconds, and then fails, that is a timeout failure, meaning that one of the Called Nodes failed to answer, and the dialogue timed out.

Did that help?
« Last Edit: August 11, 2006, 02:25:48 UTC by RussCrush » Logged
SMS Forum Support
SMS Forum Support
Administrator
Sr. Member
*****
Offline Offline

Posts: 1754


WWW
« Reply #4 on: August 11, 2006, 08:37:20 UTC »

then how do we see those messages back on MS saying "message failed" or "message could not be deliverred" or "message sent".
is it the MS that interpret those numeric cause values sent by MSC?

exactly.. it is the MS putting text to error.. but generalising mostly as opposed to being error specific.
Logged

Regards,
   Cormac Long
   Webmaster & Technical Enquiry Moderator,
   SMS Forum

Pages: [1] Go Up Print 
« previous next »
Jump to:  


Login with username, password and session length