Invalid TON/NPI

Invalid TON/NPI SearchSearch
Author Message
Alex Kaiser
Frequent Contributor
Username: Alex_k

Post Number: 94
Registered: 07-2006
Posted on Monday, March 29, 2010 - 01:48 pm:   

Hi,

We trying to submit messages with short code as source address (5088) but receiving Invalid source address TON. Then we dump packets with wireshark, src_addr_ton = 3, i believe that is incorrect. NowSMS auto detects TON/NPI settings, please advise how we can set up correct settings.

Regards,
Alex K.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1973
Registered: 08-2008
Posted on Monday, March 29, 2010 - 10:03 pm:   

Hi Alex,

Source address TON 3 is required by a lot of service providers for messages sent from a short code.

If your provider does not accept this value, you can either override the default source address TON for this connection (which applies to all messages sent via a connection, even if different source addresses are used), or set MaxSMPPShortCodeLen=20.

For more discussion of TON/NPI defaults, see http://blog.nowsms.com/2009/01/ton-and-npi-settings-for-smpp-and.html

--
Des
NowSMS Support
Alex Kaiser
Frequent Contributor
Username: Alex_k

Post Number: 95
Registered: 07-2006
Posted on Monday, March 29, 2010 - 11:38 pm:   

Hi Des,

As far as I can judge both approaches have serious disadvantages:
1. If we override connection settings, another types of src_addr can't pass over it (like alpha sender)
2. It affects all SMSC connections, that isn't suitable because require another hard test with each connection (we have about 30) and incompatibility could occur.

If my statements true, it would be nice if you make some re-mapping for standard smpp setting per connection, like:
OldSourceTON=3
NewSourceTON=1
and so on.

I hope that my thoughts have sense.

Regards,
Alex K.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1979
Registered: 08-2008
Posted on Tuesday, March 30, 2010 - 10:42 pm:   

Hi Alex,

I think you'll be OK with MaxSMPPShortCodeLen=20.

It will prevent NowSMS from using TON=3 for short codes.

Yes, it does effect all outbound connections. But I believe TON=0 will work for short codes with most providers. I double checked my notes, and it is just a couple of aggregators that require TON=3 for short codes (that we know of at least).

If you encounter problems, it would not be difficult to implement this MaxSMPPShortCodeLen on a per-connection basis.

--
Des
NowSMS Support