| WaitForResponseSMPP: SMPP select failed |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 03, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
I have configured the NowSMS SMPP server to push SMS messages to a SMSC. For 1 particular message, the SMPP server keeps polling the SMSC every 500 ms and keeps logging the "WaitForResponseSMPP: SMPP select failed," message. What could be going wrong? This happens to only messages for 1 particular MSISDN. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3231 Registered: 10-2002 |
It sounds like the SMSC is terminating the connection, presumably because it does not like something about the message. (Normally, you would expect the SMSC to return an error code instead, but this message might be triggering a program error in the SMSC.) After some retries (the exact default number does vary by version of NowSMS), NowSMS will give up. So I'm puzzled about the "every 500 ms". Can you provide any more detail?? I'm also confused because you say that you're using the NowSMS SMPP server, which would mean that the other end is connecting as a client. In that instance, if the client terminates the connection when we are attempting a message delivery, we will present that same message when the client reconnects. Unfortunately, I think we would need to see what is actually happening with the client end. Why is the client terminating the connection to the SMSC when it receives this message from us? Basically, the select failed just means that the connection was dropped unexpectedly by the other side. -bn | |||
| Anonymous |
It seems that something else is wrong. I am having the same problem! | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3257 Registered: 10-2002 |
If this message is only appearing in the debug log (SMPPDEBUG.LOG), but you are not seeing any other errors, then this is nothing to be concerned about. This is a cosmetic issue in v5.50e (and maybe v5.50d as well). We added some debug code to help identify a problem with a particular connection, and this is causing extra information to be written to the debug log. There is not an actual problem occurring ... at least this statement appearing over and over again in the debug log is not a problem. -bn | |||
