| PDU Error |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 05, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Nii Laryea New member Username: Niiso Post Number: 1 Registered: 08-2006 |
I will be grateful if I can get some help on a configuration task for an v3.3 SMPP Connection to an operator's SMSC, I was able to connect with full functionality on the receiver and transceiver ports, but after a while of it working ok, i.e. sending and receiving messages it stopped working although it can still receive messages, the error message that is recorded in the log files says::2006-08-26 11:54:43,System,,SMPP - 212.96.11.250:5018,SMPP Failure -- Unable to bind to SMPP receiver port 5018 2006-08-26 11:55:23,System,,SMPP - 212.96.11.250:5018,SMPP Failure -- Unable to bind to SMPP receiver port 5018 2006-08-26 11:55:53,44F03695.req,80.87.77.136,233275161717,Retry Pending - ERROR: Error in the optional part of the PDU Body. -- SMPP - 212.96.11.250:5018 2006-08-26 11:55:56,44F03695.req,80.87.77.136,233275161717,Retry Pending - ERROR: Error in the optional part of the PDU Body. -- SMPP - 212.96.11.250:5018 2006-08-26 11:55:57,44F0337B.req,80.87.77.136,233275161717,Retry Pending - ERROR: Error in the optional part of the PDU Body. -- SMPP - 212.96.11.250:5018 What can be done to solve it as the operator does not seem to have any problems with its SMSC ?? Please advice. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6445 Registered: 10-2002 |
Hi, We need to see a more complete log file in order to understand the context of these errors. Please enable the smsdebug.log file on the Serial # page of the configuration dialog. Capture an smsdebug.log and smppdebug.log that includes these errors occuring. These logs will include password information...so you may want to block that out before posting them here. Or you can email the logs to nowsms@now.co.uk...put "Attention Bryce" in the subject line, and include a reference to this thread in the email so that I know why I'm looking at the logs. -bn | |||
| Nii Laryea New member Username: Niiso Post Number: 2 Registered: 08-2006 |
Bryce, I emailed the logs to you as you had requested for, could you please advice on how I could resolve the problem I am confronted with. Please help. Thanks | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6448 Registered: 10-2002 |
Hello Nii, Thanks for sending the logs, that helps to more quickly understand your configuration and the context of the errors. "SMPP Failure -- Unable to bind to SMPP receiver port 5018" - This error is caused by having multiple services bind to the same port. But in this case, it is easy to identify the conflict and provide an explanation. You have configured both the sender and receiver port under the SMPP Advanced settings to 5018. This port setting refers to the local (or source) port number on your machine, not the port number on the remote server. It is quite rare for an SMPP service provider to require you to bind locally to a particular port (it is more common in UCP/EMI environments). I notice that in your case, the SMPP server port is also configured as 5018, so I suspect that these settings have been configured by mistake. If your provider does want you to use 5018 as your local port, then they probably expect you to connect as a transceiver (which is another option in the advanced configuration for SMPP ... but I don't think that was supported in SMPP v3.3). By default, when you configure NowSMS to both send and recieve over an SMPP connection, it opens 2 connections to the server ... one as a sender, and one as a receiver. However, if the "transceiver" option is used, then only a single connection to the server is used for both sending and receiving messages. Since it's an SMPP 3.3 server, it is likely that the transceiver option would not be supported ... and you probably do not need to specify the sender/receiver local port numbers. Regarding the other error ... "ERROR: Error in the optional part of the PDU Body" ... that is a mystery. The SMSC is returning error code 0xC0. That error code is not defined in the SMPP 3.3 specification. NowSMS is returning the text for what this error code is defined as meaning in the SMPP 3.4 specification. Your provider might have defined some of their own additional error codes which overlap with the SMPP 3.4 error codes. But I do have a guess for what the problem might be. It looks like there is no sender address in the messages that you are sending. Configure a "Default Sender Address" for the SMPP connection in NowSMS, and NowSMS will apply this sender address when sending outbound messages. -bn | |||
| Nii Laryea New member Username: Niiso Post Number: 3 Registered: 08-2006 |
Thanks Bryce Ur suggestions worked on all fronts. Thanks again  | |||
