Alphanumeric Recepient [MMS]

Alphanumeric Recepient [MMS] SearchSearch
NowSMS Support Forums ⬆
NowSMS Support - SMS Issues ⬆
Archive through April 11, 2011 ⬆
 ◄    ►
Author Message
Hussam Dahbour
New member
Username: Hussam83

Post Number: 10
Registered: 08-2005
Posted on Monday, December 20, 2010 - 09:54 pm:   
Dear Des,
When trying to send MMS to alias:12345678, it failed because it handled by gateway as below:
<Recipients>
<To>
<ShortCode>alias:12345678</ShortCode>
</To>
</Recipients>
While it should be:
<Recipients>
<To>
<Number>alias:12345678</Number>
</To>
</Recipients>
Waiting your feedback

Thanks
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2773
Registered: 08-2008
Posted on Tuesday, December 21, 2010 - 02:40 pm:   
Hi Hussam,

We are willing to try this.

It would be much easier if this particular provider had some documentation and/or examples.

I've reviewed the MMS specifications, and a recipient address of the format "alias:12345678" should be considered a short code.

Here is a section of the specification that describes the 3 address formats (e-mail address, number or alphanumeric short code).

quote:

1.if it contains the “@” character, the address should be interpreted as an FQDN RFC822 address
2.if it is completely numeric, except possibly including “+”, “*”, or “#”, it should be interpreted as "/TYPE= PLMN", e.g. an E.164 address, a local telephone number, or a numeric short code,
3.otherwise, it should be interpreted as an unqualified RFC822 address (alphanumeric short code)



We will change the behaviour for the AllowAlphaRecip=Yes setting to use <Number> instead of <ShortCode> in this instance to see if this resolves the issue with using alias/distribution lists with this particular provider. A test version with this behaviour change has been uploaded to http://www.nowsms.com/download/nowsmstestversion.zip

--
Des
NowSMS Support
Search Search Search Last 30 Days Login / Register Logout

NowSMS Technical Bulletins
Read more