From smpp to http smsc | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through May 20, 2013 ⬆ |
◄ ► |
Author | Message | |||
peter chanq New member Username: Qqblog Post Number: 7 Registered: 10-2012 |
i want to setup nowsms to receive sendsms request from smpp and then route the sendsms to another http smsc. is this possible? sendsms request -> smpp -> nowsms -> http smsc (custom, not using nowsms) | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4224 Registered: 08-2008 |
Hi Peter, Yes. Define an HTTP SMSC connection in NowSMS. Verify that it is working by submitting messages directly in NowSMS. Then enable the SMPP server in NowSMS and define a client account under "SMS Users". Use those account credentials to connect your SMPP client to NowSMS. This article provides info on the SMPP server setup: http://www.nowsms.com/using-nowsms-as-an-smpp-server-for-another-application -- Des NowSMS Support | |||
peter chanq New member Username: Qqblog Post Number: 8 Registered: 10-2012 |
could different smpp user route to different http smsc? eg. user1 -> http smsc 1 user2 -> http smsc 2 or advise any other routing options | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4226 Registered: 08-2008 |
Hi Peter, There are a few different ways to do this. It's hard to recommend a best way without understanding more about your setup (for example, is it only going to be two accounts or does it have the possibility to grow to many more)... The most scalable approach is if it is possible to use the same HTTP SMSC connection but pass the account name as a parameter. @@SUBMITUSER@@ in the URL will be replaced with the original SMPP account name. If that is not practical, there are other routing options. The easiest is if at least one of the accounts can always use a specific sender address (your HTTP connection can always reassign/override it). This is easiest because NowSMS will perform sender-based routing. Configure a "Forced Sender Address" for user1, then configure that same "Sender Address" for HTTP SMSC1, and that will tell NowSMS to route messages from user1 out HTTP SMSC1. (This "Sender Address" can be made up as you do not need to include the @@SENDER@@ value in the URL string.) More info on sender based routing can be found here: http://www.nowsms.com/routing-sms-messages-to-a-specifc-smsc-route If sender-based routing is not practical, there is also a more complex way to restrict outbound routes to particular users. There's a good explanation of that setup in the following thread: http://support.nowsms.com/discus/messages/1/20749.html -- Des NowSMS Support |