Getting Time-out error from SMPP adapter when TLV value is wrong

Getting Time-out error from SMPP adapter when TLV value is wrong SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Getting Time-out error from SMPP adapter when TLV value is wrong « Previous || Next »
Author Message
Aditya Chopra
New member
Username: Adifreaks86

Post Number: 3
Registered: 08-2020
Posted on Monday, August 24, 2020 - 08:55 am:   

I am sending three additional TLV parameters as below in the SMPP INI file.


DefaultSMPPOptions=PE_id=1001030926875310928;Template_id=1007371600699397295;TM_id=1001030926875310928

[SMPPOptions]

PE_id=1400,String

Template_id=1401,String

TM_id=1402,String

When i am passing the correct value as expected by the Adapter the message is successfully getting delivered to the handsets.

However, when i am sending the wrong value in TM ID which is expected by SMPP adapter it gives me standard error in SMS OUT logs file instead of the specific error code being sent by the adapter.

ERROR - Timeout waiting for response from server or lost connection.

Where can i see these logs
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 6172
Registered: 08-2008
Posted on Monday, August 24, 2020 - 04:39 pm:   

Hi,

I don't think the logs are going to show you anything different. This "standard error" displayed as "ERROR - Timeout waiting for response from server or lost connection" is returned for 2 reasons ... a timeout (our default wait is 120 seconds, so this is rare) or the other side has dropped the connection.

If you enable the SMSDEBUG.LOG in NowSMS (option is on the Serial # page), this will also enable a log named SMPPDEBUG.LOG, where the raw SMPP packets are logged. These are raw packets with no explanation or decoding. For most situations where you have a question about raw protocol details, it is best to use a tool like WireShark to intercept and decode the live protocol traffic.

--
Des
NowSMS Support
Aditya Chopra
New member
Username: Adifreaks86

Post Number: 4
Registered: 08-2020
Posted on Tuesday, August 25, 2020 - 09:48 am:   

I have enabled the debug logs and as mentioned two files are generated SMSDEBUG.LOG and SMPPDEBUG.LOG but how to open it in wireshark since it need .PCAP file to open.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 6173
Registered: 08-2008
Posted on Tuesday, August 25, 2020 - 04:07 pm:   

Sorry for not explaining this better.

WireShark will not open these log files. WireShark can be used to capture live network traffic (and save in .PCAP format), and it provides a fun decode of numerous protocols, such as SMPP.

By contrast, SMPPDEBUG.LOG just logs the raw protocol details, but requires manual decoding.

If you have difficulty working with WireShark, I can try to assist in decoding information from SMPPDEBUG.LOG.

--
Des
NowSMS Support
Aditya Chopra
New member
Username: Adifreaks86

Post Number: 5
Registered: 08-2020
Posted on Tuesday, August 25, 2020 - 04:47 pm:   

wont be able to capture logs over wireshark since working over VPN in these covid times.

PFA the SMPPDEBUG.LOG, if you check for 16:23 as per my adaptor specifications, he is sending me error code 70. How can i verify the same from these?

16:23:57:492 (000007EC) 10.14.136.47 --: SMPPConnect: Exiting
16:23:57:495 (000007EC) 10.14.136.47 ->: 41 byte packet
16:23:57:495 (000007EC) 10.14.136.47 ->: 00 00 00 29 00 00 00 02 00 00 00 00 00 00 00 01 )
16:23:57:495 (000007EC) 10.14.136.47 ->: 53 4B 56 5F 74 65 73 74 5F 50 31 00 3F 3F 3F 3F SKV_test_P1 ????
16:23:57:495 (000007EC) 10.14.136.47 ->: 3F 3F 3F 00 00 34 00 00 00 ??? 4
16:23:57:912 (000007EC) 10.14.136.47 --: SMPPBind: Got an SMPP response
16:23:57:912 (000007EC) 10.14.136.47 <-: 28 byte packet
16:23:57:912 (000007EC) 10.14.136.47 <-: 00 00 00 1C 80 00 00 02 00 00 00 01 00 00 00 01
16:23:57:912 (000007EC) 10.14.136.47 <-: 53 4B 56 5F 74 65 73 74 5F 50 31 00 SKV_test_P1


application/octet-streamSMPPDEBUG.LOG
SMPPDEBUG.LOG (10.3 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 6175
Registered: 08-2008
Posted on Tuesday, August 25, 2020 - 08:51 pm:   

Hi,

Those are all bind requests being rejected with error code 1 (ESME_RINVMSGLEN - Message Length is invalid).

16:23:57:492 (000007EC) 10.14.136.47 --: SMPPConnect: Exiting
16:23:57:495 (000007EC) 10.14.136.47 ->: 41 byte packet
16:23:57:495 (000007EC) 10.14.136.47 ->: 00 00 00 29 00 00 00 02 00 00 00 00 00 00 00 01 )
16:23:57:495 (000007EC) 10.14.136.47 ->: 53 4B 56 5F 74 65 73 74 5F 50 31 00 3F 3F 3F 3F SKV_test_P1 ????
16:23:57:495 (000007EC) 10.14.136.47 ->: 3F 3F 3F 00 00 34 00 00 00 ??? 4
16:23:57:912 (000007EC) 10.14.136.47 --: SMPPBind: Got an SMPP response
16:23:57:912 (000007EC) 10.14.136.47 <-: 28 byte packet
16:23:57:912 (000007EC) 10.14.136.47 <-: 00 00 00 1C 80 00 00 02 00 00 00 01 00 00 00 01
16:23:57:912 (000007EC) 10.14.136.47 <-: 53 4B 56 5F 74 65 73 74 5F 50 31 00 SKV_test_P1

00 00 00 02 - bind_transmitter
80 00 00 02 - bind_transmitter_resp
00 00 00 01 - command_status - 0 would be OK, 1 is ESME_RINVMSGLEN, which makes no sense in this context

In the log, there are more instances where 09 replaces 02, which is bind_transceiver. In all cases, the bind/login fails, so it never makes it far enough to be able to submit a message.

--
Des
NowSMS Support

Add Your Message Here, or click here to create a new discussion topic.
Post:
Bold text Italics Underline Create a hyperlink Insert a clipart image
Posting Information:
This is a private posting area. Only registered users and moderators may post messages here.
Click here to create an account.
Username:
Password:
Options: Automatically activate URLs in message
Action:

Login Login / Register Logout Logout Search Last 30 Days Topics Topics