SMPP Error Code Handling

SMPP Error Code Handling SearchSearch
Author Message
Chris
New member
Username: Chrisc

Post Number: 49
Registered: 12-2008
Posted on Tuesday, September 21, 2010 - 03:24 pm:   

Hi guys

We've seen the post you've made on your blog about SMPP Error Code Handling, but we're wondering if it is possible to configure these same settings at bind level?

The problem is, since we're connecting to a few providers, some of them are wanting us to retry error ESME_RSUBMITFAIL, 0x45 - which is NowSMS's default behavior - and other providers want us to make it a final response that won't initiate any further retries.

Can you help us out with something along these lines??

Thank you

Regards
Chris
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2520
Registered: 08-2008
Posted on Tuesday, September 21, 2010 - 07:54 pm:   

Hi Chris,

That would make sense. We did recently extend other retry settings so that they can be applied at the connection level instead of just globally.

We need to apply this same logic to the SMPPRejectErrorCodes setting.

It doesn't exist now, but there is an update pending for late this week or early next, and I think we can get this implemented so that the setting can be connection specific.

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2524
Registered: 08-2008
Posted on Wednesday, September 22, 2010 - 09:32 pm:   

Hi Chris,

This is a bit earlier than expected, but apparently the change to look for SMPPRejectErrorCodes first from the [SMPP - server:port] section, and if not found there, then looking at the [SMSGW] section was extremely simple.

So, it was able to go into the update that is now available at http://www.nowsms.com/download/nowsms20100921.zip.

--
Des
NowSMS Support
Chris
New member
Username: Chrisc

Post Number: 50
Registered: 12-2008
Posted on Thursday, September 23, 2010 - 09:23 am:   

Hi Des

Thanks for putting the change in so quickly! Here I was going through my emails about to set a reminder for next week and I find lower down that there's already an update Thanks a lot guys!

Regards
Chris