Guys,....everything works fine as of now.. I just replicated my smsc conf to enable five simultaneous binds...
Thanks for your suggestions Thanks Jinson On Mon, Jul 20, 2009 at 6:26 PM, Alejandro Guerrieri < [email protected]> wrote: > If connectivity is ok, you could try establishing more connections, > assuming the carrier allows you to do that (ask them about how many > simultaneous links they allow you to establish). > Try cloning the smsc group you have now, to establish two simultaneous > binds and see if that improves things a bit. > You're not setting max-pending-submits right? (The default is 10, which > should be ok). > > Regards, > > Alejandro > > > On Mon, Jul 20, 2009 at 2:49 PM, Jinson <[email protected]> wrote: > >> Alejandro, >> >> There are no throttling errors in my logs.... >> >> Thanks >> >> >> >> On Mon, Jul 20, 2009 at 6:09 PM, Alejandro Guerrieri < >> [email protected]> wrote: >> >>> I'd first rule out throttling errors. If your smsc returns throttling >>> errors, your throughput will drop drastically since messages will be retried >>> and delayed. >>> Also consider upgrading to latest CVS, there's a lot of improvements on >>> the SMPP module regarding throughput handling. >>> >>> Regards, >>> >>> Alejandro >>> >>> >>> On Mon, Jul 20, 2009 at 2:28 PM, Jinson <[email protected]> wrote: >>> >>>> How about connecting with multiple sessions to handle the heavy MT. My >>>> provider suggested me to do this. But how to do the routing?.. >>>> >>>> Thanks >>>> Jinson >>>> >>>> >>>> On Mon, Jul 20, 2009 at 5:56 PM, Alejandro Guerrieri < >>>> [email protected]> wrote: >>>> >>>>> Yes, probably the SMSC's not accepting messages fast enough. >>>>> Check on your logs to see if you're getting throttling errors, you may >>>>> need to play with the throughput parameter, and maybe max-pending-submits >>>>> as well. >>>>> >>>>> Regards, >>>>> >>>>> Alejandro >>>>> >>>>> >>>>> On Mon, Jul 20, 2009 at 2:06 PM, Jinson <[email protected]> wrote: >>>>> >>>>>> Hello Users, >>>>>> >>>>>> I'm having 4 SMSCs configured. And one among that has a heavy sms >>>>>> push. >>>>>> I am routing messages by specifying SMSC parameter in url >>>>>> >>>>>> The problem is my messages in SMSC3 are getting queued up heavily. Is >>>>>> it because of any throughput issues from the provider? >>>>>> >>>>>> can somebody suggest a solution for this? >>>>>> >>>>>> (online 7254s, rcvd 18359, sent 18359, failed 0, queued 0 msgs) >>>>>> (online 71658s, rcvd 190, sent 190, failed 0, queued 0 msgs) >>>>>> (online 71658s, rcvd 74893, sent 38434, failed 7, queued 50728 >>>>>> msgs) >>>>>> (online 3795s, rcvd 0, sent 0, failed 0, queued 0 msgs) >>>>>> >>>>>> Thanks >>>>>> Jinson >>>>>> >>>>>> >>>>> >>>> >>> >> >
