| Problem with SMPP and UCP |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 26, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| xavi mourad New member Username: Xavi08 Post Number: 1 Registered: 08-2009 |
hi all. i am new here and want to know something about NowSMS. i have created two connection with NowSMS to different providers(SMSC) which will use the same short code(for ex :5544) . i developped an application in VB whih attacks the SMSIN directory and looks for every (*.SMS)file extract the content of : phoneNumber, Sender, and DATA, i did good and could read the files, make my condititions then send the response to the clients. all is ok for one connection (the one UCP protocol).but when i added the second connection (SMPP protocol with the same shortcode.i do not knwo how to separe messages between the connections. i want to answer the clients by using the same connection which received the request(Send and receive message by the same connection SMPP transceiver). i checked this option in SMPP advanced config but it says("ERROR: ESME already in Bound State - ESME_RALYBAND"). i know there will be an other solution to my problem.so plz help And if anything is needed i am here. Best regards. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1128 Registered: 08-2008 |
Hi, There seem to be two different issues here. The "transceiver" option has no effect on message routing. It is a configuration option for the SMPP connection. The default behaviour for NowSMS when both sending and receiving via an SMPP connection is to establish two separate binds ... a sender bind and a receiver bind. That offers the best performance, but it takes up more resources on the provider, so some providers prefer that a single "transceiver" bind be used. Whether it is one SMPP bind or two SMPP binds has no effect on message routings. The error message that was returned by your provider when you tried the transceiver option "ERROR: ESME already in Bound State - ESME_RALYBAND" most likely happened for one of the following reasons: 1.) The provider does not support the transceiver bind type. Older SMPP systems frequently do not support the transceiver bind type and will reject transceiver bind attempts. 2.) The provider system requires extra time to end a previous connection. NowSMS has to disconnect the existing connections to create a transceiver connection. Some providers require extra time to register that the previous connection has been terminated, before they will allow a new connection from that account. If this is what you are experiencing, stop the NowSMS service, wait 2 minutes, and then try again. -- However ... as I mentioned ... the transceiver option has nothing to do with your original question about message routing. If you are processing message files directly from the SMS-IN directory, there will be a ModemName= entry in the .SMS file which identifies the route through which the message was originally received (e.g., ModemName=SMPP - server:port). When submitting a message for sending back through NowSMS, the same value can be specified as an explicit route for sending the message back out. When submitting via HTTP, this value gets specified in the "&SMSCRoute=" parameter. (Note that the value must be URL escaped to be encoded in an HTTP parameter, so space characters become "%20" or "+".) If you are using standard 2-way commands (instead of processing the .SMS files directly), it is also possible to edit SMSGW.INI, and under the [SMSGW] header add 2WayReplySameServer=Yes. In this case, NowSMS automatically adds the route parameter to the reply so that it is routed via the correct connection. There is some more discussion of handling multiple operator connections using the same short code here: http://blog.nowsms.com/2008/06/2-way-sms-multiple-operators-with-same.html -- Des NowSMS Support | |||
| xavi mourad New member Username: Xavi08 Post Number: 3 Registered: 08-2009 |
Desosms thank you very much for teh explanation. i am doing my best to solve teh problem. i will try what you said and return to you. 100000 tahnks for teh reply. | |||
