| 2-Way SMS dropping the message text |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through March 09, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Michael Morris New member Username: Otjam Post Number: 1 Registered: 02-2004 |
I am evaluating the current demo and having issues with the auto response failing. Packet sniffer traces shows the delivery of the message text submitted via the the SMSC, however NowSMS is not receiving it. I am aware that messages with no text will not be delivered, how do I resolve this? FYI: From SMSIN - 2004-02-14 00:48:54,XXXXX50145,Text, From SMSOUT - 2004-02-14 00:48:56,402DB6C8.req,Auto-response to XXXXX50145,XXXXX50145,OK -- SMPP - 172.16.2.60:5000,Text="Echo " From SMSDEBUG - 00:48:54:437 [3] SMPPReceiveMessageCallback: inbound message: sender=XXXXX50145, pid=0, dcs=0, udh=, msg= 00:48:55:203 [4] ThreadProcessInboundSMS: Processing 402DB6C6.in... 00:48:55:250 [4] smsData Before: 00:48:55:250 [4] smsData After: 00:48:55:250 [4] ThreadProcessInboundSMS: Executing c:\winnt\system32\cmd.exe /c echo Echo 00:48:55:296 [4] ThreadProcessInboundSMS: Echo 00:48:56:281 [2] ThreadProcessModem: Processing 402DB6C8.req... 01:00:00:203 [0] main: 56 Days remaining in trial version | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1904 Registered: 10-2002 |
Hi Michael, Apologies for the delay in responding back to you. I wish you had posted these "packet sniffer traces". Without that detail, I can only say that this problem does not sound familiar. Then again, this is an SMPP environment. And we did recently make some adjustments for parsing of messages when the "message_payload" interface is used. That might be what the problem is here. I'd like to send you an update to see if this addresses your problem. I'm going to check the discussion board to see if you've registered an e-mail address with it. If you have, then I will send you the update. Otherwise, please send an e-mail to nowsms@now.co.uk referencing this thread, and I will send you the update. If the update doesn't solve the problem, I'd like to see the SMPPDEBUG.LOG file, as that should have the details of the actual SMPP transaction. -bn | |||
