Comments (31)
dfilipovic39
commented on June 28, 2024
1
I can confirm this issue. there were no changes on both server and client side except for go-smpp library upgrade and the handler doesn't trigger anymore.
from go-smpp.
nezorflame
commented on June 28, 2024
1
@sandeepkdpl @fiorix "PDU not implemented" is fired in codec.go in Decode func.
It assumes that we can't handle this type of PDU right now, Read fails because of Decode and connection drops.
This is true for:
- AlertNotificationID
- CancelSMID
- CancelSMRespID
- DataSMID
- DataSMRespID
- OutbindID
- ReplaceSMID
- ReplaceSMRespID
I wonder what is the header for 0x44617461534d though...
from go-smpp.
fiorix
commented on June 28, 2024
1
Alright. Thanks @nezorflame for jumping in.
from go-smpp.
fiorix
commented on June 28, 2024
Could be a protocol mismatch? The fact that the status is changing (reconnecting) sounds like one of the peers is disconnecting upon a message on the wire. Can only help if we have logs or packet captures.
from go-smpp.
sandeepkdpl
commented on June 28, 2024
Please see the log.
16:40:54:129 (00000430) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received bind request
16:40:56:133 (00000430) 192.168.0.103 <-: 38 byte packet
16:40:56:133 (00000430) 192.168.0.103 <-: 00 00 00 26 00 00 00 09 00 00 00 00 00 00 00 01 &
16:40:56:133 (00000430) 192.168.0.103 <-: 73 61 6E 64 65 65 70 00 6B 64 70 6C 40 31 32 33 sandeep kdpl@123
16:40:56:133 (00000430) 192.168.0.103 <-: 00 00 34 00 00 00 4
16:40:56:133 (00000430) 192.168.0.103 <-: 38 byte packet
16:40:56:133 (00000430) 192.168.0.103 <-: 00 00 00 26 00 00 00 09 00 00 00 00 00 00 00 01 &
16:40:56:134 (00000430) 192.168.0.103 <-: 73 61 6E 64 65 65 70 00 6B 64 70 6C 40 31 32 33 sandeep kdpl@123
16:40:56:134 (00000430) 192.168.0.103 <-: 00 00 34 00 00 00 4
16:40:56:134 (00000430) 192.168.0.103 ->: 28 byte packet
16:40:56:134 (00000430) 192.168.0.103 ->: 00 00 00 1C 80 00 00 09 00 00 00 00 00 00 00 01
16:40:56:134 (00000430) 192.168.0.103 ->: 4E 6F 77 53 4D 53 00 02 10 00 01 34 NowSMS 4
16:40:56:137 (00000430) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received a submit message
16:40:56:137 (00000430) 192.168.0.103 <-: 53 byte packet
16:40:56:137 (00000430) 192.168.0.103 <-: 00 00 00 35 00 00 00 04 00 00 00 00 00 00 00 02 5
16:40:56:137 (00000430) 192.168.0.103 <-: 00 00 00 2B 39 31 39 37 31 31 31 37 34 31 36 31 +919711174161
16:40:56:137 (00000430) 192.168.0.103 <-: 00 00 00 00 00 00 00 00 00 00 00 00 00 07 73 61 sa
16:40:56:137 (00000430) 192.168.0.103 <-: 6E 64 65 65 70 ndeep
16:40:56:141 (00000430) 192.168.0.103 ->: 25 byte packet
16:40:56:141 (00000430) 192.168.0.103 ->: 00 00 00 19 80 00 00 04 00 00 00 00 00 00 00 02
16:40:56:141 (00000430) 192.168.0.103 ->: 35 39 33 45 44 38 33 36 00 593ED836
16:41:06:137 (00000430) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:41:16:137 (00000430) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:41:26:138 (00000430) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:41:36:139 (00000430) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:41:46:140 (00000430) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:41:56:142 (00000430) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:42:06:142 (00000430) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:42:16:143 (00000430) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:42:26:144 (00000430) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:42:36:145 (00000430) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:42:46:146 (00000430) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:42:47:146 (00000430) 192.168.0.103 ->: 72 byte packet
16:42:47:146 (00000430) 192.168.0.103 ->: 00 00 00 48 00 00 01 03 00 00 00 00 00 00 00 01 H
16:42:47:146 (00000430) 192.168.0.103 ->: 00 01 01 39 31 39 37 31 31 31 37 34 31 36 31 00 919711174161
16:42:47:146 (00000430) 192.168.0.103 ->: 01 01 39 31 39 35 36 30 35 30 30 31 33 35 00 00 919560500135
16:42:47:146 (00000430) 192.168.0.103 ->: 00 00 04 24 00 12 46 72 6F 6D 20 73 61 6E 64 65 $ From sande
16:42:47:146 (00000430) 192.168.0.103 ->: 65 70 20 4B 75 6D 61 72 ep Kumar
16:42:47:147 (00000430) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: ioctlsocket failed, no data
16:42:47:147 (00000430) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: ioctlsocket failed, no data
16:42:47:147 CheckSmppServerAsyncQ: Mark deliver as complete
16:42:49:149 (00000298) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received bind request
16:42:49:149 (00000298) 192.168.0.103 <-: 38 byte packet
16:42:49:149 (00000298) 192.168.0.103 <-: 00 00 00 26 00 00 00 09 00 00 00 00 00 00 00 0E &
16:42:49:149 (00000298) 192.168.0.103 <-: 73 61 6E 64 65 65 70 00 6B 64 70 6C 40 31 32 33 sandeep kdpl@123
16:42:49:149 (00000298) 192.168.0.103 <-: 00 00 34 00 00 00 4
16:42:49:149 (00000298) 192.168.0.103 <-: 38 byte packet
16:42:49:149 (00000298) 192.168.0.103 <-: 00 00 00 26 00 00 00 09 00 00 00 00 00 00 00 0E &
16:42:49:150 (00000298) 192.168.0.103 <-: 73 61 6E 64 65 65 70 00 6B 64 70 6C 40 31 32 33 sandeep kdpl@123
16:42:49:150 (00000298) 192.168.0.103 <-: 00 00 34 00 00 00 4
16:42:49:150 (00000298) 192.168.0.103 ->: 28 byte packet
16:42:49:150 (00000298) 192.168.0.103 ->: 00 00 00 1C 80 00 00 09 00 00 00 00 00 00 00 0E
16:42:49:150 (00000298) 192.168.0.103 ->: 4E 6F 77 53 4D 53 00 02 10 00 01 34 NowSMS 4
16:42:49:152 (00000298) 192.168.0.103 ->: 72 byte packet
16:42:49:152 (00000298) 192.168.0.103 ->: 00 00 00 48 00 00 01 03 00 00 00 00 00 00 00 01 H
16:42:49:152 (00000298) 192.168.0.103 ->: 00 01 01 39 31 39 37 31 31 31 37 34 31 36 31 00 919711174161
16:42:49:152 (00000298) 192.168.0.103 ->: 01 01 39 31 39 35 36 30 35 30 30 31 33 35 00 00 919560500135
16:42:49:152 (00000298) 192.168.0.103 ->: 00 00 04 24 00 12 46 72 6F 6D 20 73 61 6E 64 65 $ From sande
16:42:49:152 (00000298) 192.168.0.103 ->: 65 70 20 4B 75 6D 61 72 ep Kumar
16:42:49:153 (00000298) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: ioctlsocket failed, no data
16:42:49:153 (00000298) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: ioctlsocket failed, no data
16:42:49:153 CheckSmppServerAsyncQ: Mark deliver as complete
16:42:51:155 (0000039C) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received bind request
16:42:51:155 (0000039C) 192.168.0.103 <-: 38 byte packet
16:42:51:155 (0000039C) 192.168.0.103 <-: 00 00 00 26 00 00 00 09 00 00 00 00 00 00 00 0F &
16:42:51:155 (0000039C) 192.168.0.103 <-: 73 61 6E 64 65 65 70 00 6B 64 70 6C 40 31 32 33 sandeep kdpl@123
16:42:51:155 (0000039C) 192.168.0.103 <-: 00 00 34 00 00 00 4
16:42:51:155 (0000039C) 192.168.0.103 <-: 38 byte packet
16:42:51:155 (0000039C) 192.168.0.103 <-: 00 00 00 26 00 00 00 09 00 00 00 00 00 00 00 0F &
16:42:51:155 (0000039C) 192.168.0.103 <-: 73 61 6E 64 65 65 70 00 6B 64 70 6C 40 31 32 33 sandeep kdpl@123
16:42:51:156 (0000039C) 192.168.0.103 <-: 00 00 34 00 00 00 4
16:42:51:156 (0000039C) 192.168.0.103 ->: 28 byte packet
16:42:51:156 (0000039C) 192.168.0.103 ->: 00 00 00 1C 80 00 00 09 00 00 00 00 00 00 00 0F
16:42:51:156 (0000039C) 192.168.0.103 ->: 4E 6F 77 53 4D 53 00 02 10 00 01 34 NowSMS 4
16:43:01:158 (0000039C) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:43:11:158 (0000039C) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:43:19:160 (0000039C) 192.168.0.103 ->: 72 byte packet
16:43:19:160 (0000039C) 192.168.0.103 ->: 00 00 00 48 00 00 01 03 00 00 00 00 00 00 00 01 H
16:43:19:160 (0000039C) 192.168.0.103 ->: 00 01 01 39 31 39 37 31 31 31 37 34 31 36 31 00 919711174161
16:43:19:160 (0000039C) 192.168.0.103 ->: 01 01 39 31 39 35 36 30 35 30 30 31 33 35 00 00 919560500135
16:43:19:160 (0000039C) 192.168.0.103 ->: 00 00 04 24 00 12 46 72 6F 6D 20 73 61 6E 64 65 $ From sande
16:43:19:160 (0000039C) 192.168.0.103 ->: 65 70 20 4B 75 6D 61 72 ep Kumar
16:43:19:161 (0000039C) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: ioctlsocket failed, no data
16:43:19:161 (0000039C) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: ioctlsocket failed, no data
16:43:19:161 CheckSmppServerAsyncQ: Mark deliver as complete
16:43:21:162 (000004B8) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received bind request
16:43:21:162 (000004B8) 192.168.0.103 <-: 38 byte packet
16:43:21:162 (000004B8) 192.168.0.103 <-: 00 00 00 26 00 00 00 09 00 00 00 00 00 00 00 12 &
16:43:21:162 (000004B8) 192.168.0.103 <-: 73 61 6E 64 65 65 70 00 6B 64 70 6C 40 31 32 33 sandeep kdpl@123
16:43:21:162 (000004B8) 192.168.0.103 <-: 00 00 34 00 00 00 4
16:43:21:163 (000004B8) 192.168.0.103 <-: 38 byte packet
16:43:21:163 (000004B8) 192.168.0.103 <-: 00 00 00 26 00 00 00 09 00 00 00 00 00 00 00 12 &
16:43:21:163 (000004B8) 192.168.0.103 <-: 73 61 6E 64 65 65 70 00 6B 64 70 6C 40 31 32 33 sandeep kdpl@123
16:43:21:163 (000004B8) 192.168.0.103 <-: 00 00 34 00 00 00 4
16:43:21:163 (000004B8) 192.168.0.103 ->: 28 byte packet
16:43:21:163 (000004B8) 192.168.0.103 ->: 00 00 00 1C 80 00 00 09 00 00 00 00 00 00 00 12
16:43:21:163 (000004B8) 192.168.0.103 ->: 4E 6F 77 53 4D 53 00 02 10 00 01 34 NowSMS 4
16:43:31:164 (000004B8) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:43:41:164 (000004B8) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:43:51:166 (000004B8) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:44:01:168 (000004B8) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:44:11:168 (000004B8) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:44:19:169 (000004B8) 192.168.0.103 ->: 72 byte packet
16:44:19:169 (000004B8) 192.168.0.103 ->: 00 00 00 48 00 00 01 03 00 00 00 00 00 00 00 01 H
16:44:19:169 (000004B8) 192.168.0.103 ->: 00 01 01 39 31 39 37 31 31 31 37 34 31 36 31 00 919711174161
16:44:19:169 (000004B8) 192.168.0.103 ->: 01 01 39 31 39 35 36 30 35 30 30 31 33 35 00 00 919560500135
16:44:19:169 (000004B8) 192.168.0.103 ->: 00 00 04 24 00 12 46 72 6F 6D 20 73 61 6E 64 65 $ From sande
16:44:19:169 (000004B8) 192.168.0.103 ->: 65 70 20 4B 75 6D 61 72 ep Kumar
16:44:19:170 (000004B8) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: ioctlsocket failed, no data
16:44:19:170 (000004B8) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: ioctlsocket failed, no data
16:44:19:170 CheckSmppServerAsyncQ: Mark deliver as complete
16:44:21:173 (000004A8) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received bind request
16:44:21:173 (000004A8) 192.168.0.103 <-: 38 byte packet
16:44:21:173 (000004A8) 192.168.0.103 <-: 00 00 00 26 00 00 00 09 00 00 00 00 00 00 00 18 &
16:44:21:173 (000004A8) 192.168.0.103 <-: 73 61 6E 64 65 65 70 00 6B 64 70 6C 40 31 32 33 sandeep kdpl@123
16:44:21:173 (000004A8) 192.168.0.103 <-: 00 00 34 00 00 00 4
16:44:21:173 (000004A8) 192.168.0.103 <-: 38 byte packet
16:44:21:173 (000004A8) 192.168.0.103 <-: 00 00 00 26 00 00 00 09 00 00 00 00 00 00 00 18 &
16:44:21:173 (000004A8) 192.168.0.103 <-: 73 61 6E 64 65 65 70 00 6B 64 70 6C 40 31 32 33 sandeep kdpl@123
16:44:21:173 (000004A8) 192.168.0.103 <-: 00 00 34 00 00 00 4
16:44:21:173 (000004A8) 192.168.0.103 ->: 28 byte packet
16:44:21:173 (000004A8) 192.168.0.103 ->: 00 00 00 1C 80 00 00 09 00 00 00 00 00 00 00 18
16:44:21:173 (000004A8) 192.168.0.103 ->: 4E 6F 77 53 4D 53 00 02 10 00 01 34 NowSMS 4
16:44:30:052 (000004A8) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: ioctlsocket failed, no data
16:44:51:597 (000004C8) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received bind request
16:44:51:597 (000004C8) 192.168.0.103 <-: 38 byte packet
16:44:51:597 (000004C8) 192.168.0.103 <-: 00 00 00 26 00 00 00 09 00 00 00 00 00 00 00 02 &
16:44:51:597 (000004C8) 192.168.0.103 <-: 73 61 6E 64 65 65 70 00 6B 64 70 6C 40 31 32 33 sandeep kdpl@123
16:44:51:597 (000004C8) 192.168.0.103 <-: 00 00 34 00 00 00 4
16:44:51:597 (000004C8) 192.168.0.103 <-: 38 byte packet
16:44:51:597 (000004C8) 192.168.0.103 <-: 00 00 00 26 00 00 00 09 00 00 00 00 00 00 00 02 &
16:44:51:597 (000004C8) 192.168.0.103 <-: 73 61 6E 64 65 65 70 00 6B 64 70 6C 40 31 32 33 sandeep kdpl@123
16:44:51:597 (000004C8) 192.168.0.103 <-: 00 00 34 00 00 00 4
16:44:51:598 (000004C8) 192.168.0.103 ->: 28 byte packet
16:44:51:598 (000004C8) 192.168.0.103 ->: 00 00 00 1C 80 00 00 09 00 00 00 00 00 00 00 02
16:44:51:598 (000004C8) 192.168.0.103 ->: 4E 6F 77 53 4D 53 00 02 10 00 01 34 NowSMS 4
16:44:51:599 (000004C8) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: ioctlsocket failed, no data
16:45:52:533 (000004EC) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received bind request
16:45:52:533 (000004EC) 192.168.0.103 <-: 38 byte packet
16:45:52:533 (000004EC) 192.168.0.103 <-: 00 00 00 26 00 00 00 09 00 00 00 00 00 00 00 01 &
16:45:52:533 (000004EC) 192.168.0.103 <-: 73 61 6E 64 65 65 70 00 6B 64 70 6C 40 31 32 33 sandeep kdpl@123
16:45:52:533 (000004EC) 192.168.0.103 <-: 00 00 34 00 00 00 4
16:45:52:533 (000004EC) 192.168.0.103 <-: 38 byte packet
16:45:52:533 (000004EC) 192.168.0.103 <-: 00 00 00 26 00 00 00 09 00 00 00 00 00 00 00 01 &
16:45:52:533 (000004EC) 192.168.0.103 <-: 73 61 6E 64 65 65 70 00 6B 64 70 6C 40 31 32 33 sandeep kdpl@123
16:45:52:534 (000004EC) 192.168.0.103 <-: 00 00 34 00 00 00 4
16:45:52:534 (000004EC) 192.168.0.103 ->: 28 byte packet
16:45:52:534 (000004EC) 192.168.0.103 ->: 00 00 00 1C 80 00 00 09 00 00 00 00 00 00 00 01
16:45:52:534 (000004EC) 192.168.0.103 ->: 4E 6F 77 53 4D 53 00 02 10 00 01 34 NowSMS 4
16:45:52:536 (000004EC) 192.168.0.103 ->: 72 byte packet
16:45:52:536 (000004EC) 192.168.0.103 ->: 00 00 00 48 00 00 01 03 00 00 00 00 00 00 00 01 H
16:45:52:536 (000004EC) 192.168.0.103 ->: 00 01 01 39 31 39 37 31 31 31 37 34 31 36 31 00 919711174161
16:45:52:536 (000004EC) 192.168.0.103 ->: 01 01 39 31 39 35 36 30 35 30 30 31 33 35 00 00 919560500135
16:45:52:536 (000004EC) 192.168.0.103 ->: 00 00 04 24 00 12 46 72 6F 6D 20 73 61 6E 64 65 $ From sande
16:45:52:536 (000004EC) 192.168.0.103 ->: 65 70 20 4B 75 6D 61 72 ep Kumar
16:45:52:536 (000004EC) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: ioctlsocket failed, no data
16:45:52:537 (000004EC) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: ioctlsocket failed, no data
16:45:52:537 CheckSmppServerAsyncQ: Mark deliver as complete
16:45:54:537 (000004F0) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received bind request
16:45:54:537 (000004F0) 192.168.0.103 <-: 38 byte packet
16:45:54:537 (000004F0) 192.168.0.103 <-: 00 00 00 26 00 00 00 09 00 00 00 00 00 00 00 02 &
16:45:54:537 (000004F0) 192.168.0.103 <-: 73 61 6E 64 65 65 70 00 6B 64 70 6C 40 31 32 33 sandeep kdpl@123
16:45:54:538 (000004F0) 192.168.0.103 <-: 00 00 34 00 00 00 4
16:45:54:538 (000004F0) 192.168.0.103 <-: 38 byte packet
16:45:54:538 (000004F0) 192.168.0.103 <-: 00 00 00 26 00 00 00 09 00 00 00 00 00 00 00 02 &
16:45:54:538 (000004F0) 192.168.0.103 <-: 73 61 6E 64 65 65 70 00 6B 64 70 6C 40 31 32 33 sandeep kdpl@123
16:45:54:538 (000004F0) 192.168.0.103 <-: 00 00 34 00 00 00 4
16:45:54:538 (000004F0) 192.168.0.103 ->: 28 byte packet
16:45:54:538 (000004F0) 192.168.0.103 ->: 00 00 00 1C 80 00 00 09 00 00 00 00 00 00 00 02
16:45:54:538 (000004F0) 192.168.0.103 ->: 4E 6F 77 53 4D 53 00 02 10 00 01 34 NowSMS 4
16:46:04:539 (000004F0) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:46:14:539 (000004F0) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:46:20:543 (000004F0) 192.168.0.103 ->: 78 byte packet
16:46:20:543 (000004F0) 192.168.0.103 ->: 00 00 00 4E 00 00 01 03 00 00 00 00 00 00 00 01 N
16:46:20:543 (000004F0) 192.168.0.103 ->: 00 01 01 39 31 39 37 31 31 31 37 34 31 36 31 00 919711174161
16:46:20:543 (000004F0) 192.168.0.103 ->: 01 01 39 31 39 35 36 30 35 30 30 31 33 35 00 00 919560500135
16:46:20:543 (000004F0) 192.168.0.103 ->: 00 00 04 24 00 18 46 72 6F 6D 20 73 61 6E 64 65 $ From sande
16:46:20:543 (000004F0) 192.168.0.103 ->: 65 70 20 4B 75 6D 61 72 20 68 65 6C 6C 6F ep Kumar hello
16:46:20:544 (000004F0) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: ioctlsocket failed, no data
16:46:20:544 (000004F0) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: ioctlsocket failed, no data
16:46:20:544 CheckSmppServerAsyncQ: Mark deliver as complete
16:46:22:545 (0000039C) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received bind request
16:46:22:545 (0000039C) 192.168.0.103 <-: 38 byte packet
16:46:22:545 (0000039C) 192.168.0.103 <-: 00 00 00 26 00 00 00 09 00 00 00 00 00 00 00 05 &
16:46:22:545 (0000039C) 192.168.0.103 <-: 73 61 6E 64 65 65 70 00 6B 64 70 6C 40 31 32 33 sandeep kdpl@123
16:46:22:545 (0000039C) 192.168.0.103 <-: 00 00 34 00 00 00 4
16:46:22:545 (0000039C) 192.168.0.103 <-: 38 byte packet
16:46:22:545 (0000039C) 192.168.0.103 <-: 00 00 00 26 00 00 00 09 00 00 00 00 00 00 00 05 &
16:46:22:545 (0000039C) 192.168.0.103 <-: 73 61 6E 64 65 65 70 00 6B 64 70 6C 40 31 32 33 sandeep kdpl@123
16:46:22:545 (0000039C) 192.168.0.103 <-: 00 00 34 00 00 00 4
16:46:22:545 (0000039C) 192.168.0.103 ->: 28 byte packet
16:46:22:545 (0000039C) 192.168.0.103 ->: 00 00 00 1C 80 00 00 09 00 00 00 00 00 00 00 05
16:46:22:545 (0000039C) 192.168.0.103 ->: 4E 6F 77 53 4D 53 00 02 10 00 01 34 NowSMS 4
16:46:22:551 (0000039C) 192.168.0.103 ->: 78 byte packet
16:46:22:551 (0000039C) 192.168.0.103 ->: 00 00 00 4E 00 00 01 03 00 00 00 00 00 00 00 02 N
16:46:22:551 (0000039C) 192.168.0.103 ->: 00 01 01 39 31 39 37 31 31 31 37 34 31 36 31 00 919711174161
16:46:22:551 (0000039C) 192.168.0.103 ->: 01 01 39 31 39 35 36 30 35 30 30 31 33 35 00 00 919560500135
16:46:22:551 (0000039C) 192.168.0.103 ->: 00 00 04 24 00 18 46 72 6F 6D 20 73 61 6E 64 65 $ From sande
16:46:22:551 (0000039C) 192.168.0.103 ->: 65 70 20 4B 75 6D 61 72 20 68 65 6C 6C 6F ep Kumar hello
16:46:22:552 (0000039C) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: ioctlsocket failed, no data
16:46:22:552 (0000039C) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: ioctlsocket failed, no data
16:46:22:552 CheckSmppServerAsyncQ: Mark deliver as complete
16:46:24:553 (00000498) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received bind request
16:46:24:553 (00000498) 192.168.0.103 <-: 38 byte packet
16:46:24:553 (00000498) 192.168.0.103 <-: 00 00 00 26 00 00 00 09 00 00 00 00 00 00 00 06 &
16:46:24:553 (00000498) 192.168.0.103 <-: 73 61 6E 64 65 65 70 00 6B 64 70 6C 40 31 32 33 sandeep kdpl@123
16:46:24:553 (00000498) 192.168.0.103 <-: 00 00 34 00 00 00 4
16:46:24:554 (00000498) 192.168.0.103 <-: 38 byte packet
16:46:24:554 (00000498) 192.168.0.103 <-: 00 00 00 26 00 00 00 09 00 00 00 00 00 00 00 06 &
16:46:24:554 (00000498) 192.168.0.103 <-: 73 61 6E 64 65 65 70 00 6B 64 70 6C 40 31 32 33 sandeep kdpl@123
16:46:24:554 (00000498) 192.168.0.103 <-: 00 00 34 00 00 00 4
16:46:24:554 (00000498) 192.168.0.103 ->: 28 byte packet
16:46:24:554 (00000498) 192.168.0.103 ->: 00 00 00 1C 80 00 00 09 00 00 00 00 00 00 00 06
16:46:24:554 (00000498) 192.168.0.103 ->: 4E 6F 77 53 4D 53 00 02 10 00 01 34 NowSMS 4
16:46:34:555 (00000498) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:46:44:556 (00000498) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:46:52:567 (00000498) 192.168.0.103 ->: 78 byte packet
16:46:52:567 (00000498) 192.168.0.103 ->: 00 00 00 4E 00 00 01 03 00 00 00 00 00 00 00 01 N
16:46:52:567 (00000498) 192.168.0.103 ->: 00 01 01 39 31 39 37 31 31 31 37 34 31 36 31 00 919711174161
16:46:52:567 (00000498) 192.168.0.103 ->: 01 01 39 31 39 35 36 30 35 30 30 31 33 35 00 00 919560500135
16:46:52:567 (00000498) 192.168.0.103 ->: 00 00 04 24 00 18 46 72 6F 6D 20 73 61 6E 64 65 $ From sande
16:46:52:567 (00000498) 192.168.0.103 ->: 65 70 20 4B 75 6D 61 72 20 68 65 6C 6C 6F ep Kumar hello
16:46:52:567 (00000498) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: ioctlsocket failed, no data
16:46:52:567 (00000498) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: ioctlsocket failed, no data
16:46:52:568 CheckSmppServerAsyncQ: Mark deliver as complete
16:46:54:569 (00000500) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received bind request
16:46:54:569 (00000500) 192.168.0.103 <-: 38 byte packet
16:46:54:570 (00000500) 192.168.0.103 <-: 00 00 00 26 00 00 00 09 00 00 00 00 00 00 00 09 &
16:46:54:570 (00000500) 192.168.0.103 <-: 73 61 6E 64 65 65 70 00 6B 64 70 6C 40 31 32 33 sandeep kdpl@123
16:46:54:570 (00000500) 192.168.0.103 <-: 00 00 34 00 00 00 4
16:46:54:570 (00000500) 192.168.0.103 <-: 38 byte packet
16:46:54:570 (00000500) 192.168.0.103 <-: 00 00 00 26 00 00 00 09 00 00 00 00 00 00 00 09 &
16:46:54:570 (00000500) 192.168.0.103 <-: 73 61 6E 64 65 65 70 00 6B 64 70 6C 40 31 32 33 sandeep kdpl@123
16:46:54:570 (00000500) 192.168.0.103 <-: 00 00 34 00 00 00 4
16:46:54:570 (00000500) 192.168.0.103 ->: 28 byte packet
16:46:54:570 (00000500) 192.168.0.103 ->: 00 00 00 1C 80 00 00 09 00 00 00 00 00 00 00 09
16:46:54:570 (00000500) 192.168.0.103 ->: 4E 6F 77 53 4D 53 00 02 10 00 01 34 NowSMS 4
16:47:04:571 (00000500) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:47:14:572 (00000500) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:47:24:572 (00000500) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
16:47:34:572 (00000500) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: received enquire_link, acknowledging
from go-smpp.
fiorix
commented on June 28, 2024
Seems like something that happens right before this:
16:42:47:147 (00000430) 192.168.0.103 --: WaitForResponseSMPP: SMPP Debug: ioctlsocket failed, no data
is what's causing the disconnect. Can't tell which end of the connection is problematic.
from go-smpp.
sandeepkdpl
commented on June 28, 2024
Please send me any smsc server link by which we can test your sample in real time.
from go-smpp.
fiorix
commented on June 28, 2024
Can one of you help bisect this to the problematic diff? Maybe @nezorflame and/or @wOvAN know about this too.
from go-smpp.
fiorix
commented on June 28, 2024
@sandeepkdpl for testing I normally use http://www.seleniumsoftware.com/downloads.html but I haven't done this in a while.
from go-smpp.
nezorflame
commented on June 28, 2024
I'll test too and try to see what's wrong.
from go-smpp.
nezorflame
commented on June 28, 2024
Can't reproduce the problem with Jasmin SMPPSim (which is based on Selenium I guess):
from go-smpp.
nezorflame
commented on June 28, 2024
Also if you select for the ConnStatus like below, no errors are caught:
for {
select {
case c := <-tx.Bind():
if c == nil {
return
}
switch c.Status() {
case smpp.Connected:
log.Print("Gate bound")
case smpp.ConnectionFailed:
log.Printf("Unable to connect: %s", c.Error())
case smpp.BindFailed:
log.Printf("Unable to bind: %s", c.Error())
case smpp.Disconnected:
log.Printf("Gate disconnected: %s", c.Error())
}
}
}
Only 'Gate bound' followed by SMPPSim received messages.
What OSes do you use, Go version?
from go-smpp.
sandeepkdpl
commented on June 28, 2024
Go Version is
go version go1.7.5 windows/amd64
from go-smpp.
dfilipovic39
commented on June 28, 2024
Mine is go1.8rc3 linux/amd64. Ill try to upgrade to 1.8.3-1 and check if
thats the problem. But i doubt it
EDIT:
Ok, seems i was wrong :) the DeliverSM fires now.
Maybe if someone else would confirm this? It would be good to add go version requirement to README in that case.
…On Mon, 24 Jul 2017 at 07:21 sandeepkdpl ***@***.***> wrote:
Go Version is
go version go1.7.5 windows/amd64
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#52 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFNhCGjVq0ZjEduw77xlZbarjyk7moi8ks5sRCnagaJpZM4N7Bug>
.
from go-smpp.
sandeepkdpl
commented on June 28, 2024
See error after using your code @nezorflame. I have upgraded go version also to latest version.
from go-smpp.
nezorflame
commented on June 28, 2024
OK, that is strange.
I'll try to reproduce this on my Windows and Linux machines later.
Unable to reproduce this on macOS.
from go-smpp.
sandeepkdpl
commented on June 28, 2024
OK, We are waiting for your response...
from go-smpp.
nezorflame
commented on June 28, 2024
I see that you're using NowSMS, I'll try to get an account and try with it.
from go-smpp.
sandeepkdpl
commented on June 28, 2024
Yes, We are using NowSMS trial version, you can also get trial version for testing purpose.
from go-smpp.
nezorflame
commented on June 28, 2024
I've set up Windows in VBox, installed Go 1.7.
Installed NowSMS trial, set it up like this:
The connection seems stable, no drops, and your code runs absolutely fine:
Maybe you've set up some specific settings in NowSMS which are interfering?
from go-smpp.
sandeepkdpl
commented on June 28, 2024
Yes everything run fines till the sms receive event. Please cross check sms receive event.
We are configuring smsc server using usb. We have connected a device with usb. Device contains a sim card by which we are sending sms and receiving sms.
from go-smpp.
nezorflame
commented on June 28, 2024
@fiorix were you able to reproduce this?
from go-smpp.
sandeepkdpl
commented on June 28, 2024
Yes I am receiving this error every time... Still not received a single receive event. I can send sms from this but unable to get receive sms event.
from go-smpp.
nezorflame
commented on June 28, 2024
No problem with receiving messages either:
from go-smpp.
nezorflame
commented on June 28, 2024
I've played a bit with NowSMS server and still unable to reproduce the issue.
@tarqe39 please tell me, how did you reproduce it on your machine?
from go-smpp.
fiorix
commented on June 28, 2024
@nezorflame I haven't tried yet
from go-smpp.
sandeepkdpl
commented on June 28, 2024
@nezorflame are you using the same code which I have mentioned or you have done something else because at my side its not firing receive sms event. I have tried may things which I can do but their is no success.
You can debug my case if you want we are ready for run any sample package by which you can create logs if you want....
from go-smpp.
nezorflame
commented on June 28, 2024
Yes, I am using exactly the same code as you.
package main
import (
"log"
"time"
"github.com/fiorix/go-smpp/smpp"
"github.com/fiorix/go-smpp/smpp/pdu"
"github.com/fiorix/go-smpp/smpp/pdu/pdufield"
"github.com/fiorix/go-smpp/smpp/pdu/pdutext"
)
func main() {
f := func(p pdu.Body) {
switch p.Header().ID {
case pdu.DeliverSMID:
f := p.Fields()
src := f[pdufield.SourceAddr]
dst := f[pdufield.DestinationAddr]
txt := f[pdufield.ShortMessage]
log.Printf("Short message from=%q to=%q: %q",
src, dst, txt)
}
}
tx := &smpp.Transceiver{
Addr: "localhost:4444",
User: "default",
Passwd: "password",
Handler: f, // Handle incoming SM or delivery receipts.
}
// Create persistent connection, wait for the first status.
conn := <-tx.Bind()
if conn.Status() != smpp.Connected {
log.Fatal(conn.Error())
}
sm, err := tx.Submit(&smpp.ShortMessage{
Src: "src",
Dst: "des",
Text: pdutext.Raw("sandeep"),
Register: pdufield.NoDeliveryReceipt,
})
if err != nil {
log.Fatal(err)
}
log.Println("Message ID:", sm.RespID())
for {
time.Sleep(time.Millisecond * 1600)
}
}from go-smpp.
nezorflame
commented on June 28, 2024
@sandeepkdpl OK, you have 2 things to consider.
- You should really learn how to debug Go applications (https://github.com/derekparker/delve) so next time you can set breakpoints and see for yourself where's the problem.
- I have my fork of this lib. I've inserted Println's into the Decode func, so when the problem occurs, the program will write the name of the problematic PDU in charge.
Checkout thetestbranch from my repo https://github.com/nezorflame/go-smpp/tree/test, place it in "GOPATH/src/github.com/nezorflame/go-smpp" and replace original imports in the code with mine.
Post the result window here after you're launched the app.
from go-smpp.
sandeepkdpl
commented on June 28, 2024
See this
from go-smpp.
sandeepkdpl
commented on June 28, 2024
There is a problem in our nowsms server setting which has been modified today. Data_SM PDU is checked. After uncheck that setting for user. We are able to receive message event.
Thanks for all your corporation. @nezorflame and @fiorix
from go-smpp.
Related Issues (20)
- Using tx.Submit in thread HOT 2
- Easier way to manager delivery receipts - missing receipted_message_id and PDU Sequence Management HOT 1
- [QUESTION] - How to register multiple delivery for transceiver
- [BUG] - message encoding not working for long unicode message
- timeout waiting for response - RESOLVED using RespTimeout parameter HOT 5
- Converting the hex in text field of delivery receipt to original UCS2 text submitted
- Use GSM(packed) to encode and then decode, there is an extra '@' character HOT 4
- Concatenated / Multipart
- Multipart Message using UCS2
- server example
- Concatenated problem HOT 1
- getValidityPeriod format YYMMDDhhmmssUTCR
- disconnect when receive data_sm HOT 2
- error in var udhList []UDH
- Gracefully stop HOT 1
- Implements generic_nack on ESME side
- Not able to set dynamic listening IP and port HOT 1
- How to set sequence while creating submit_SM ? HOT 1
- SUBMIT_SMRESP not received in the callback.
- Check connected client(s) HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from go-smpp.