SMPP Server - Routing | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 08, 2009 ⬆ |
◄ ► |
Author | Message | |||
spinnerudi New member Username: Spinnerudi Post Number: 3 Registered: 02-2009 |
Hi SMPP-Server: I have configured the SMPP Server in NowSMS. I have created different users in "SMS Users" with enabled "Enable SMPP Login for this user". SMSC Connections: In the "SMSC" Tab I have configured 2 HTTP SMSC-Connections. Routing?: How can I configure for the users which SMSC Connections to use?? | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 490 Registered: 08-2008 |
Hi, The easiest way is to use sender based routing. Let me see if I can explain it simply in the context of your configuration ... and then I'll point you to a link with more details. In your HTTP SMSC connections, define a "Sender Address" for each connection. Your environment sounds like a simulated environment, but in a real world environment, this would be the sender (source) address for all SMS messages sent through this connection. Then in the "SMS Users" account definition, there is a "Forced Sender Address" setting. For any messages received from this setting, NowSMS will apply the "Forced Sender Address" as the "Sender Address" of the message. When NowSMS looks to route the message out to an SMSC connection, it first looks for a matching "Sender Address" to indicate which route the message should go out via. There's more general information on SMS routing here: http://blog.nowsms.com/2008/07/routing-sms-messages-to-specifc-smsc.html (And a few more options that I notice are not mentioned in that link ... but I suspect the sender based routing will work for your environment.) -- Des NowSMS Support | |||
spinnerudi New member Username: Spinnerudi Post Number: 4 Registered: 02-2009 |
Your configuration described works fine. But am I right, that the original sender address of the message cannot be used to send the message through the SMSC connection, because the "Froced Sender Address" property of "SMS Users" overwrites the orginal sender address? Is there a way to use the original sender address, even we configured the sender based routing like your describtion? | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 618 Registered: 08-2008 |
Yes, that is correct. An alternative is the AllowedUser settings. There is a description in the 6th post on the following thread: http://support.nowsms.com/discus/messages/1/24404.html -- Des NowSMS Support | |||
spinnerudi New member Username: Spinnerudi Post Number: 5 Registered: 02-2009 |
If I use this AllowedUser settings for a SMSC Connection, do I have to configure the "Support any outbound message traffic" and the "Preferred SMSC Connection"?? | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 623 Registered: 08-2008 |
It depends on how complex your configuration is. But the short answer is that yes you should still configure those settings. The AllowedUser only settings are evaluated before any other routing information. The routing evaluation continues by looking at only the routes for which the user is allowed. So, we're still going to do the recipient address pattern matching against only those routes for which the user is allowed. In a simple scenario with SMSUserA routing all messages to SMSC1 and SMSUserB routing all messages to SMSC2, you'd have the following: [header for SMSC1] AllowedUserOnly=Yes AllowedUser1=SMSUserA [header for SMSC2] AllowedUserOnly=Yes AllowedUser1=SMSUserB You would also have "Support any outbound message traffic" enabled for both SMSCs. That setting would only be evaluated when routing messages for an account on the "allowed" list. -- Des NowSMS Support |