| Changing SMSC/Route on delivery error |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through October 19, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Morten Jensen New member Username: Hansherlighed Post Number: 5 Registered: 06-2006 |
Hi all, I was wonering if anyone knows of a way to setup nowsms to switch to another smsc/route if the SMS cannot be delivered. I have a GSM modem route and a SMPP route setup in now SMS. I prefer to use the GSM route to send SMS, but when sending many SMS at the sametime, the modem cannot keep up and generates errors. I use the "Route=xxxx" option when submitting my SMS to NOWSMS. Is there anyway i can make NOWSMS first try to send the SMS through the GSM route, and if that fails, send it through the SMPP route? Thanks in advance. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7392 Registered: 10-2002 |
Hi Morten, It is possible to have multiple connections service the same route. However, because the SMPP connection is faster, that would mean more messages would get routed via the SMPP connection, which is not what you want. So I'm not aware of any way to accomplish what you want. This is something that we should add in the future. Any suggestions for how you would like to see the rules defined would be helpful. In my mind, the hardest part of implementing such a feature is determining how to define the rules. -bn | |||
| Morten Jensen New member Username: Hansherlighed Post Number: 6 Registered: 06-2006 |
Hi Bruce, thanks for the quick reply. I would think that a parameter in SMSGW.ini would do the trick. Something like a parameter called "Alternativeroute=" that could be defined under each modem/smpp/http connection in SMSGW.ini. It could work together with the "Retry" paramters so that when the "RetryMaxAttempts=" limit has been reached and the "Alternativeroute=" parameter has been set, then the SMS will be routed through the "Alternativeroute=" connection instead. You just have to do some kind of check/limit so that you do not create a infitive loop where the first connections "Alternativeroute=" points to the second connection, and the second connections "Alternativeroute=" points back to the first connection. If both connections fails to deliver there needs to be a limit of tries. Hope you can use it for something, It would really be great if something like that could be implemented. I Have another wierd problem with the latest version of NOWSMS. I'm doing some testing to see if we are to upgrade, and i'm currently using the 60 day trail version. The problem is that the "allow sender address override" in the SMPP connection does not seems to work. I have checked the option under the SMPP connection and defined a "Sender address". Even though I use the "&Sender=" in my post to NOWSMS, it still uses the "Sender address" instead. I have tested that the "&Sender=" is actually being posted to NOWSMS, and it is. If i leave the "Sender address" field empty and post the exact same message to NOWSMS, the sender is correct. This has never been an issue in the 5.51K version? Any ideas? | |||
| Morten Jensen New member Username: Hansherlighed Post Number: 7 Registered: 06-2006 |
A note to my last post. The "&Sender=" parameter is not being processed even though the "Sender Address" field is empty. No matter what i Try, i cannot get NOWSMS to accept another sender address than the one listed in "Sender address". I have even tryed to define more than one Sender addres by placing a comma in between, but no luck:-( My post to NOWSMS is: http://localhost:8800/PhoneNumber=12345678&Text=Test+SMS&ReceiptRequested=Yes&se nder=TEST&route=smpp | |||
| Morten Jensen New member Username: Hansherlighed Post Number: 8 Registered: 06-2006 |
Another note.... It seems that the "allow address override" does not accept letters. As soon as i change the "&Sender=" to something like "1234", then it works. Changing nothing else in the post but "1234" to "Test", then it fails. Also it seems that the "&Route=" parameter is being ignored as well? I'm using the "OpenSMPP SMSC simulator" and I have 2 SMPP connections setup in NOWSMS: [SMPP - 127.0.0.1:8900] RouteName=modem SMPPVersion=v3.4 UserName=pavel Password=pavel SenderAddress=Test SenderAddressOverride=No Receive=Yes ReceiveMMS=No UseSSL=No LongSMSAlt=Yes [SMPP - 127.0.0.1:9000] RouteName=smpp SMPPVersion=v3.4 UserName=pavel Password=pavel SenderAddressOverride=Yes Receive=Yes ReceiveMMS=No UseSSL=No LongSMSAlt=Yes SenderAddress=Testing When sending 10 messages via IE by using the URL: http://localhost:8800/PhoneNumber=87654321&Text=Test+SMS&ReceiptRequested=Yes&se nder=12345678&route=smpp I get 10 entrys in smsdebug.log: 01:30:59:921 [14] ThreadProcessConnection: Processing connection from 192.168.1.103... 01:30:59:921 [14] ThreadProcessConnection: Processing request /PhoneNumber=87654321&Text=Test+SMS&ReceiptRequested=Yes&sender=12345678&route=s mpp but i get this in the smsout.log: 2007-07-19 01:30:58,469541BC.req,192.168.1.103,87654321,OK -- SMPP - 127.0.0.1:8900,Sender=Test;SMSCMsgId=Smsc2002;Text="Test SMS" 2007-07-19 01:31:00,469541BD.req,192.168.1.103,87654321,OK -- SMPP - 127.0.0.1:9000,Sender=12345678;SMSCMsgId=Smsc2038;Text="Test SMS" 2007-07-19 01:32:00,469541BF.req,192.168.1.103,87654321,OK -- SMPP - 127.0.0.1:9000,Sender=12345678;SMSCMsgId=Smsc2039;Text="Test SMS" 2007-07-19 01:32:00,469541BE.req,192.168.1.103,87654321,OK -- SMPP - 127.0.0.1:8900,Sender=Test;SMSCMsgId=Smsc2003;Text="Test SMS" 2007-07-19 01:33:00,469541C1.req,192.168.1.103,87654321,OK -- SMPP - 127.0.0.1:9000,Sender=12345678;SMSCMsgId=Smsc2040;Text="Test SMS" (I have only pasted the 5 first entries from the smsout.log, but as you can see, the SMS' are being routed to both SMSC's? Any ideas? | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7398 Registered: 10-2002 |
Hi Morten, There is a problem with alpha senders in the "&Sender=" parameter. I'm investigating this, but it appears to be related to the change to support port addressing by including ":port" in a sender and/or recipient phone number. The logic that parses the ":" out of the "&Sender=" parameter appears to strip any non-numeric characters from the parameter. The "&Route=" problem is easier to explain. It should be "&SMSCRoute=", then it will be recognised. -bn | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7404 Registered: 10-2002 |
Follow-up ... I've posted a patch to address the alpha sender problem with the "&Sender=" parameter. For the moment it is available for download at the link http://www.nowsms.com/download/morten.zip. -bn | |||
| Morten Jensen New member Username: Hansherlighed Post Number: 9 Registered: 06-2006 |
Hi Bryce, Thanks for the update, however it has not solved all my problems:-( The non alpha sender name is now being processed correclty, but at a very very low speed. The limit for the trial version is 30 SMS/minut, but when using a non alpha sender name, it doesn't live up to that. It takes around 2-3 miutes to send 1 SMS, and 2-3 minutes for the inbound delivery repport to be registered in nowsms. If i do use a alpha sender number, then it works as it should both incoming and outgoing. I'm using the openSMPP simulator to test the speed. The old version 5.51k has no problems with the same setup, it's only in nowsms2007? Regards Morten | |||
| SMSCOMM New member Username: Smstext Post Number: 2 Registered: 07-2007 |
I updated to NOWSMS 2007. but is has become very very slow in sending messages. Why is this?? | |||
