Routing SMS via several SMSC's

Routing SMS via several SMSC's SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through July 14, 2005 » Routing SMS via several SMSC's « Previous || Next »
Author Message
Posted on Monday, May 23, 2005 - 11:00 pm:   


We'd be interested in using NowSMS as an SMPP server. It should accept messages arriving via SMPP through multiple inbound user connections and route them through several outbound SMPP SMSC links. Messages arrive with random Sender ID-s, which the server may not alter. The delivery receips should route back to users.

In this "transparent" mode, can the following be configured:

1. Messages with Sender ID-s within a defined range, or beginning with a certain digit must always be sent over certain SMSC-s. For example, we want all messages with numeric Sender ID-s beginning with 9 and at least 6 digits long to send over SMSC-s A and B only, while the rest of messages must send through C and D. I expected that the leading digit filtering would work by entering 9* in the "Sender Address" field in the SMSC definition, but it did not.

2. For each inbound link, we can define daily/monthly sending limits per user, which is great. How can the same be done for outbound connections? This is often required since some operators limit the number of messages their customers are allowed to send to foreign networks.

3. Is it possible to setup SMPP connections for backup, e.g., if the main SMSC is down the traffic would automatically switch to the fail-over link? Can we define several backup links taking over sequentially, for redundancy and managing costs?

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4600
Registered: 10-2002
Posted on Thursday, May 26, 2005 - 04:35 pm:   

Hi Paul,

Unfortunately, I don't think we have all of the capabilities that you require.

1.) We don't do any pattern matching on the sender address. That is a good idea, but not something that we currently support.

We did just add the ability to explicitly specify a route when a message is submitted via HTTP. And our plan is to add an HTTP callback where we pass details about each message and ask you what the allowed routes are. But this capability is still most likely a few months out.

2.) That's an interesting requirement. Again, not something that we support. I'm wondering if this scenario is one that we could somehow work into our plans for the routing callbacks that I mentioned above.

3.) If you want them to be true fail over, this only works if the fail-over is of the same type (e.g., both SMPP or HTTP) ... and listening on the same port. Here's details on this setup:

Darek Chorazewicz
New member
Username: Daro

Post Number: 30
Registered: 03-2004
Posted on Wednesday, June 01, 2005 - 10:42 pm:   

If you are looking for sms gateway that can send sms messages with random SENDER ID just check


Login Login / Register Logout Logout Search Last 30 Days Topics Topics