How to setup 2 NowSms instances in different machines | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 23, 2007 ⬆ |
◄ ► |
Author | Message | |||
Marcos Nowosad New member Username: Mnowosad Post Number: 7 Registered: 08-2006 |
I am trying to have NowSms running in 2 different machines, executing 2-Way commands, that are pointing to the same SMSC connection (same Server Host Name, same Server Port). Our SMSC is mBlox. The reason is that we need to setup one testing environment separate from production environment. Each connection has a different Sender Address, so the SMSC is able to distinguish between the outbound requests coming from the two machines. However, when I try to setup this two-machine scenario, what happens is that one machine captures all inbound SMPP coming from the SMSC, while the other does not receive any of them. Is there a way to have the two machines receiving the SMPP messages coming from the SMSC, using the same Server Host/Server Post connection settings? | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6630 Registered: 10-2002 |
Hi Marcos, Unfortunately, this is all under the control of the SMSC to which you are connecting. The behaviour that you describe is not uncommon ... after all, that SMSC has no way of knowing what your intentions are if you are logging in with the same account credentials for both connections. That said, there are criteria within the SMPP protocol that are designed to address this issue. However, I would be surprised if mBlox supported this (they might ... I'd put probability at around 25 to 33%). When you bind to an SMPP connection as a receiver (or transceiver), you can specify an "address range" parameter. This parameter is intended to specify the destination addresses for which this connection wishes to receive. This parameter can be specified as an optional parameter when you define the SMPP connection to NowSMS. The SMPP protocol defines this parameter as being a Unix regular expression, and here is a discussion of the syntax from the SMPP protocol specification:
|