| Q Folder & messages marked as ERROR |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 10, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Dimitris Chatzopoulos New member Username: Xatzo Post Number: 7 Registered: 01-2005 |
Dear NowSMS, As I mention in other posts I have 4 SMPP and 1 CIMD2 connection. Now I'm testing the quality of the gateway in matters of speed and capacity (messages that can be sent per second). In my .NET application I have set a loop that sends 3 msg/sec. With the CIMD2 connection all seems to be okay but with the SMPP connection I get errors. I can see this errors in the SMSDEBUG.LOG and it's like this one "11:30:01:437 [6] ThreadProcessModem: Error: ERROR: Invalid Source Address". Every time the gateway encounters this error instead of creating this file "41F4C018.req" I get a 41F4C018.ERR" and the message will stuck in the queue forever. Why is that? How can I tell the gateway to retry send this messages? In case that we lost the connection with the provider for 5 minutes all the queue messages will become ERROR messages. How can we bypass this problem? Thank you. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3984 Registered: 10-2002 |
Hi Dimitris, We've already exchanged some e-mail about this, so let's follow-up there. From the log files that you've sent me, it looks like the provider is randomly returning "invaild source address" errors when messages are submitted via SMPP. This error is supposed to be interpreted as a permanent error indicating that the message should not be retried. What is odd is that from your logs, I can see that the exact same message sometimes works and sometimes fails. That is definitely not normal. We're probably going to need to get some feedback from the provider to see if they can determine from their logs why these messages are being rejected with "invalid source address". But in the meantime, I'm also going to suggest an Ethereal trace to see if we can observe anything unusual over the TCP/IP connection. -bn | |||
