| Routing Issue when single bind handles multiple senders |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through October 19, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| RMD New member Username: Thinkfr33ly Post Number: 3 Registered: 02-2007 |
Bryce, Here is my setup: 5 SMPP Connections: 1) (US) Sender Address = 11111 (bind is for just 11111 traffic) 2) (UK) Sender Address = 22222 3) (UK) Sender Address = 22222 4) (US) Sender Address = 33333 5) (US) Bind #5 handles traffic for 44444 and 55555. We are sending messages to NowSMS via HTTP with the Sender url parameter. NowSMS is having a very difficult time figuring out which SMSC connection to use. I am trying to avoid using the SMSCRoute paraemter. I have tried setting the sender=44444,55555 and many small variations of that. I was able to put a temporary fix in where the only bind that has "Support Any outbound message traffic" checked is Bind #5, however as soon as we have another shortcode added to binds 1-4, we will have the problem again. I would think that the routing algorithm should properly support a comma deliminiated list in the Sender Address field, but it doesnt appear to be working and/or supported. Thanks! | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7091 Registered: 10-2002 |
Hi RMD, We did recently make a change to support a comma delimited list in the "Sender Address" field. Initially we had added this capability for the "Forced Sender Address" field associated with an "SMS Users" account ... it wasn't supported for outbound routing via the "SMSC" list. But this was added very recently in the 2007.03.06 update. At this point, I'd recommend downloading http://www.nowsms.com/download/20070412.zip for the latest update which would incorporate this change: * SMS Gateway: Extension for sender based routing. When NowSMS routes an SMS message, it first looks to see if a sender address has been specified for the message submission (via HTTP this would be specified with the optional "&Sender=" parameter). If a sender address was specified, NowSMS checks to see if the sender address matches the "Default Sender Address" that is configured for any of the SMSC links (or "the "Phone Number" associated with GSM modem links). If NowSMS finds a match, then it will route the message only via an SMSC connection with a matching sender address. This update adds support for multiple sender addresses to be associated with a single SMSC connection for sender-based routing. To configure this, multiple sender addresses can be specified in the "Default Sender Address" field, separated by a comma (example: 1111,1112,1113). NowSMS will still use the first entry as the "Default Sender Address" for messages that are sent via the connection that do not have a sender address. However, other listed sender addresses can be used to facilitate sender based routing. If "Allow Sender Address Override" is not checked, and multiple phone numbers are specified in the "Default Sender Address" field, NowSMS will check the sender address to see if it matches one of the values listed in the "Default Sender Address" field. If it does not, the sender address will automatically be switched to the first sender address in the list. | |||
| ekow des bordes New member Username: Ekowdb Post Number: 4 Registered: 10-2006 |
I have a similar problem. I have two sender addresses coming on one SMPP bind, as in the network has routed all incoming messages for either of the sender addresses onto one account for us to bind to. is there a way to have multiple users being routed onto the same smpp bind and receiving the different sender ID's as and when they come in? | |||
