| Client ESME's, provider HTTP (two ways) |  Search
|
|
NowSMS Support Forums ⬆ NowSMS NextGen Support ⬆ |
◄ ► |
| Author | Message | |||
| Florian Overkamp New member Username: Florianoverkamp Post Number: 1 Registered: 02-2021 |
Hi, I'm evaluating NowSMSNG as conversion gateway from HTTP API's to legacy platforms using SMPP. I've defined both an HTTP SMSC for outbound and a user for inbound. For testing, I've got a kannel set up to be ESME client to NowSMS. The links are all up and functional, but I'm struggling with routing. I found the parameters to pass the user on from the HTTP side, using 'LocalUser=' (with or without 'InboundMessage=yes' does not seem to make a difference) The message is properly submitted from the HTTP side, and the resulting message does have a 'RouteToLocalUser=<esme-acct>' line in the SMS-IN directory. However, the message just sits in the Message Inbox and is not routed to the ESME client. I would like to be able to route without any dependance on what recipient number is being used, so the 'Recipient address(es) to route to this account:' should be fairly generic. '*' however starts looping back even the messages the ESME account itself is sending, so it is not reusable over multiple accounts, so my idea is this needs to be empty. What am I missing? Thanks, Florian | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 6232 Registered: 08-2008 |
HI Florian, This is somewhat illogical, but you need to "enable 2-way commands for SMS" under the section header "SMS 2-Way Commands", otherwise the messages get stuck. The 2-way command list can remain empty. Regards, Des NowSMS Support | |||
| Florian Overkamp New member Username: Florianoverkamp Post Number: 2 Registered: 02-2021 |
Hi Des, Thanks for your swift response, that did the trick indeed, I can now pass messages back and forth through the entire chain. Best regards, Florian | |||
