| Concat messages & SMSCRoute param |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 26, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| Alex Kaiser New member Username: Alex_k Post Number: 40 Registered: 07-2006 |
Hello, We faced the following problem, when we assign SMSCRoute param for concat SMS in SMSSend request some messages got stuck. That scheme works if we use only one route but when it's more than one(round robin - load balancing mechanism), different parts of the same message can be routed to the different route and of course they won't be accepted. We can track parts of these messages and assign correct route but i think that would be so resources consuming. It's better if you force SMSCRoute param for all parts of concat messages from the 1st part. Regards, Alex K. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1286 Registered: 08-2008 |
Hi Alex, I don't have a good answer for you. Under normal routing scenarios, NowSMS ensures that all parts of a concatenated message go out via the same route. However, if you're using the dynamic callbacks to set the routing, it's going to override that logic. I agree that it's a headache to track, but since the callback is handling the routing, I think the callback needs to manage this. -- Des NowSMS Support | |||
