| NowSMS not processing incoming SMS message |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 23, 2007 ⬆ |
◄ ► |
| Author | Message | ||||
| Marcos Nowosad New member Username: Mnowosad Post Number: 11 Registered: 08-2006 |
Hi, The following situation is happening from time to time with our testing NowSMS system and is really disrupting our testing schedule, besides raising concerns about NowSMS availability in a production environment. We have a SMSC connection configured with mBlox. Most of the times, things work well, meaning MO messages are sent from handsets, routed by mBlox and received by NowSMS (content of the incoming message can be seen in SMSIN*.LOG file). However, from time to time, MO messages will stop arriving at the NowSMS message. If you check the SMSIN*.LOG file, there is no new entry. If you call mBlox, they will say that, for each incoming SMS message, their system is correctly routing it to our server and that NowSMS is hand-shaking, sending the acknowledgment that it has received the message. For there on, nothing happens at NowSMS (no new entry is created in SMSIN*.LOG and the associated 2-Way command is not activated). We turned on the NowSMS debugging to check what was going on. After sending the MO message again, the SMSDEBUG.LOG file did not contain any further valuable information. However, the SMPPDEBUG.LOG file showed us that NowSMS seemed to enter in some loop process after acknowledging the incoming message, which prevented it from doing any further process. Check the attached SMPPDEBUG.LOG file content. To make it NowSMS work again (and force it to leave this non-functional state), we usually have to stop and start the service endless times. After a while, it really becomes frustrating, because neither we are sure about the root cause of the problem, nor if restarting the service really solves the problem (or is just coincidental). We would like to have some advice about the situation. Thanks, Marcos
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6661 Registered: 10-2002 |
Hi Marcos, The SMPPDEBUG.LOG that you show is normal behaviour. By default, approximately every 60 seconds, NowSMS sends an enquire_link command over an SMPP connection, and expects to see an enquire_link response come back. This time period is customisable for each SMPP connection ... but the default is good for most providers. Basically, with most providers, if they do not receive an enquire link within a timeout period configured on their end, then they will drop your connection. Basically, this is a "keep alive" feature in the SMPP protocol. I don't see any evidence in this log of a message being received ... and NowSMS would definitely not send an acknowledgment of a message being received without indicating this in that log. So I suspect that something else must be going on. I seem to remember in another thread that you had a test server and a production server logging into the same account. Is it possible that a different server is connected to the account and receiving the messages? I realise this is very frustrating for you ... but I simply cannot accept that the explanation that mBlox is giving you unless there is a multiple system scenario accessing the account, as there is no way that NowSMS would send an acknowledgment for a message that it did not process. If you want to verify that something else isn't going on which isn't being reported in the NowSMS SMPPDEBUG.LOG, you could always setup a protocol capture with Ethereal (www.ethereal.com). It's a real easy tool to use, and it lets you capture all of the traffic that is actually being sent and received. I've really got to figure that unless something is wrong on the mBlox side, that the only viable explanation is multiple systems connecting into the same account. -bn | ||||
SMPP Log file
