| SMPP Asynchronous, and desabled time out response |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through June 21, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| MedSalimALI Frequent Contributor Username: Salim Post Number: 117 Registered: 04-2005 |
Dear Bryce, Hope you are going well.. I have one problem with one of our operators that: When we submit one SMS less than 160 characters it's going like before... When we submit lenghty, NowSMS was concatenated as one SMS usbmission Now, They upgrade their SMSC, and the lenghty SMS is queuing, after delaying time, its sending but it creating LCK file in Q.. I check the SMPPDEBUG it look like below 16:20:51:218 (00000120) 212.0.128.13 --: WaitForResponseSMPP: SMPP select timeout 16:20:51:218 (00000120) 212.0.128.13 --: SMPPSubmitMessage: SMPP response failed 16:20:51:218 (00000120) 212.0.128.13 --: SMPPEnquireLink: Sending enquire_link 16:20:51:312 (00000120) 212.0.128.13 --: SMPPEnquireLink: Response received for enquire_link 16:20:51:312 (00000120) 212.0.128.13 ->: 208 byte packet 16:20:51:312 (00000120) 212.0.128.13 ->: 00 00 00 D0 00 00 00 04 00 00 00 00 00 00 00 04 16:20:51:312 (00000120) 212.0.128.13 ->: 00 05 00 31 34 32 38 00 01 01 32 34 39 39 31 32 1428 249912 16:20:51:312 (00000120) 212.0.128.13 ->: 33 39 38 33 37 34 00 40 00 00 00 00 00 00 00 00 398374 @ 16:20:51:312 (00000120) 212.0.128.13 ->: 9F 05 00 03 BA 04 02 20 63 6F 6E 66 69 67 75 72 configur 16:20:51:312 (00000120) 212.0.128.13 ->: 65 73 20 61 20 6E 75 6D 62 65 72 20 6F 66 20 73 es a number of s 16:20:51:312 (00000120) 212.0.128.13 ->: 65 63 75 72 69 74 79 20 73 65 74 74 69 6E 67 73 ecurity settings 16:20:51:312 (00000120) 212.0.128.13 ->: 20 74 68 61 74 20 64 65 66 69 6E 65 20 68 6F 77 that define how 16:20:51:312 (00000120) 212.0.128.13 ->: 20 75 73 65 72 73 20 62 72 6F 77 73 65 20 49 6E users browse In 16:20:51:312 (00000120) 212.0.128.13 ->: 74 65 72 6E 65 74 20 61 6E 64 20 69 6E 74 72 61 ternet and intra 16:20:51:312 (00000120) 212.0.128.13 ->: 6E 65 74 20 57 65 62 20 73 69 74 65 73 2E 20 54 net Web sites. T 16:20:51:312 (00000120) 212.0.128.13 ->: 68 65 20 63 6F 6E 66 69 67 75 72 61 74 69 6F 6E he configuration 16:20:51:312 (00000120) 212.0.128.13 ->: 20 61 6C 73 6F 20 72 65 64 75 63 65 73 20 74 68 also reduces th 16:20:51:312 (00000120) 212.0.128.13 ->: 65 20 65 78 70 6F 73 75 72 65 20 6F 66 20 79 6F e exposure of yo The operator, suggested to use SMPP asynchronous. I download path for 5.51h version.... because we are using 5.51 version... is there any suggestion which can help us? thank you. Salim | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7012 Registered: 10-2002 |
Hi Salim, I'm curious to see more of the log. Are you saying that the message does eventually get accepted by the SMSC, it just has a considerable delay before it is completely accepted? Enabling async mode might help ... but it's hard to guess what is actually going on at the SMSC during this delay, as that is quite odd. Normally async mode is enabled in NowSMS under the "Advanced" settings for "Properties" of the SMPP connection in the "SMSC" list. But I'm not sure about the version in which this setting was first added. Initially it may have required a WindowSize=### setting under the [SMPP - host:port] section of SMSGW.INI. -bn | |||
| MedSalimALI Frequent Contributor Username: Salim Post Number: 118 Registered: 04-2005 |
Hello Bryce, Thank you for your curiosity, and note that Mobitel solved the problem from their side, by enabling synchronous mode, after one week, we already migrated our 5.51K into the 2006 version where we specified the asynch mode manually... is there any mistake on the Windows size=### ?, I didn't setup it... It was costing us days and service delaying in which many SMS2TV live services are running... Mrs. Lisa was helpful for the activation code, and we have now the 2006 version which also solved the MMS issue of Mobitel Sudan... Regards, Salim | |||
