Resend an sms through a different route, when error 67 is returned ...

Resend an sms through a different route, when error 67 is returned ... SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through November 14, 2013 » Resend an sms through a different route, when error 67 is returned in Accounting Callback (SMSIN) « Previous || Next »
Author Message
OlzZzy
New member
Username: Olsi

Post Number: 3
Registered: 12-2012
Posted on Monday, June 10, 2013 - 12:26 pm:   

Hi everyone,

I am just testing Accounting Callbacks in NowSMS and they are really coming in handy.
I am trying to see if there is any option to resubmit an sms through a different route, when the SMSIN callback gets an Error 67 (ported number)? Anyone has any idea?

Thanks in advance,
Olsi.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4536
Registered: 08-2008
Posted on Tuesday, June 11, 2013 - 11:37 am:   

Hi Olsi,

If I understand correctly, it would be the SMSOUT callback that you would want to react to. NowSMS generates this callback when it is successfully transmitted to an upstream SMSC, or when an upstream SMSC returns an error.

Unfortunately, we have not implemented functionality to allow rerouting from an SMSOUT error callback. This is something we are considering for future updates.

Currently you could react to the callback by resubmitting a new message with the same parameters but to a different route. There is also support for a config parameter to try a different SMSC after a message fails on a particular SMSC, but this setting is not very flexible. Search for ReRouteOnError for details on that parameter.

--
Des
NowSMS Support
OlzZzy
New member
Username: Olsi

Post Number: 4
Registered: 12-2012
Posted on Wednesday, June 12, 2013 - 01:50 pm:   

Hi Des,
thank you for the reply. Yes, that was supposed to be SMSOut :)

I have two SMSCs in my setup. A CIMD2 and an SMPP.

I try to send the message through the first one, and if it doesn't work, I want to reroute it to the second one.

I have out ReRouteOnError=secondroute in the configuration of the CIMD connection, and put retry attempts = 1, and I immediately get the failed message in the event log.

I'm not sure if I am doing something wrong. Any help would be very appreciated!

Thanks a lot,
Olsi.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4537
Registered: 08-2008
Posted on Wednesday, June 12, 2013 - 02:42 pm:   

Hi Olsi,

Does secondroute match the RouteName= parameter under the SMPP connection?

Can you post the SMSGW.INI (remove usernames and password before posting)?

What is the NowSMS version?

I'd also be curious to see what the SMSDEBUG.LOG shows when the message send attempt fails.

--
Des
NowSMS Support
OlzZzy
New member
Username: Olsi

Post Number: 5
Registered: 12-2012
Posted on Wednesday, June 12, 2013 - 02:49 pm:   

Hi Des,

This is my SMSGW.ini


//SMSGW.ini
[SMSGW]
WebAuth=Yes
WebMenu=Yes
WebPort=8800
SeparateUserQueues=Yes
ReceiveSMS=Yes
ReceiveMMS=No
CIMDRejectErrorCodes=All
PHPEnable=No
PHPAllowRemote=No
ReceiveSMSCharset=utf-8
SMSAccountingURL=http://192.168.0.112/portability/cb.php
Modem1=SMPP - connect.beepsend.com:7337
ReceiveSMSCommand1=* http://192.168.0.112/portability/log.php?sender=@@SENDER@@&sms=@@FULLSMS@@ No *
SMPPPort=4400
SMPPPortSSL=4401
Modem2=CIMD - XXX.XXX.XXX.XXX:XXXX
[SMPP - XXX.XXX.XXX.XXX:XXX]
RouteName=defaultroute
SMPPVersion=v3.4
UserName=XXX
Password=XXX
SenderAddressOverride=Yes
Receive=Yes
ReceiveMMS=No
UseSSL=No
LongSMSAlt=Yes
SourceTON=5
SourceNPI=1
DestTON=1
DestNPI=1
WindowSize=10
[CIMD - XXX.XXX.XXX.XXX:XXXX]
RouteName=firstroute
UserName=XXXX
Password=XXXX
Receive=Yes
ReceiveMMS=No
KeepAlive=60
ReRouteOnError=defaultroute
SenderAddressOverride=Yes
RoutePrefOnly=Yes
//END of SMSGW.ini
OlzZzy
New member
Username: Olsi

Post Number: 6
Registered: 12-2012
Posted on Wednesday, June 12, 2013 - 02:53 pm:   

NowSMS version is 2012.06.28, but I cant seem to find a SMSDEBUG.LOG file.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4538
Registered: 08-2008
Posted on Wednesday, June 12, 2013 - 03:07 pm:   

There is a checkbox option on the "Serial #" page to enable SMSDEBUG.LOG...sorry, I should have mentioned that.
OlzZzy
New member
Username: Olsi

Post Number: 7
Registered: 12-2012
Posted on Thursday, June 13, 2013 - 06:12 am:   

Hi Des,
this is the SMSDEBUG log.

application/octet-stream
SMSDEBUG.LOG (10.4 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4539
Registered: 08-2008
Posted on Thursday, June 13, 2013 - 01:30 pm:   

The ReRouteOnError setting was added in early 2012. I see a note in our changes file that the original implementation did not work with all SMSC connection types.

Download the update at http://www.nowsms.com/download/nowsms20130531.zip, and this should resolve any issues with that setting.

--
Des
NowSMS Support
OlzZzy
New member
Username: Olsi

Post Number: 8
Registered: 12-2012
Posted on Thursday, June 13, 2013 - 01:49 pm:   

Des, you are my favorite person in the world!
Works perfectly!

Thank you!!! :)
OlzZzy
New member
Username: Olsi

Post Number: 11
Registered: 12-2012
Posted on Tuesday, June 18, 2013 - 01:04 pm:   

Des, one more question if I may :)

I am getting the ENROUTE status back several time for the same message. Is it possible to disable this status, and only return a final one?

Thank you!
OlzZzy
New member
Username: Olsi

Post Number: 12
Registered: 12-2012
Posted on Tuesday, June 18, 2013 - 01:55 pm:   

Des, sorry to bug you again, but I think I am having a major issue. I have many messages in queue, and they are being sent very slowly.

I am using CallBacks and in the SMSDEBUG I see this 17:48:50:281 [15] ReportOverThreshold: Debug.

I have two SMPP connections and the callbacks define where the message will go through.

Please let me know if I am doing something wrong.

Thanks in advance!
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4543
Registered: 08-2008
Posted on Tuesday, June 18, 2013 - 02:15 pm:   

Hi,

Unfortunately, whether or not the upstream SMSC generates ENROUTE reports is up to the upstream SMSC.

(For technical completeness only - There is a bit flag for whether or not intermediate delivery reports are requested, and NowSMS always sets this to NOT requested. But this flag is typically ignored.)

Regarding the delivery speed, what speed is your NowSMS license, and what is the speed at which messages seem to be getting sent out? (If you do not wish to post details here, send to nowsms@nowsms.com with Attention: Des in the subject line.)

--
Des
NowSMS Support
OlzZzy
New member
Username: Olsi

Post Number: 13
Registered: 12-2012
Posted on Tuesday, June 18, 2013 - 02:20 pm:   

Hi Des,

From what I see in the NowSMS window, the speed is 50 messages per second.

Before I started to use callbacks messages were being delivered very quickly, now it seems like less than 1 per second, and it gets blocked sometimes.

Thanks a lot for the fast responses!
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4544
Registered: 08-2008
Posted on Tuesday, June 18, 2013 - 04:44 pm:   

Hi Olsi,

Callbacks can slow things down, depending on how long they take to process. I can see from your previously posted log that it takes about 5 to 6 ms to process a callback, which is plenty fast for keeping pace with 50 messages per second.

However, the SMSDEBUG entry "ReportOverThreshold: Debug" suggests that NowSMS might be throttling performance. I say might because this debug entry doesn't necessarily mean it is. The entry indicates that NowSMS is close to processing the max number of messages allowed in the current minute, and a stat counter is being updated to reflect this. On the serial # page, a new stat indicates how many minutes the system was at or near capacity.

So I'm a little confused...I don't know whether to troubleshoot the callbacks (checking the SMSDEBUG.LOG to determine how long it typically takes to process a callback to determine if they are a cause of delay) ... or to troubleshoot the license.

One thing I will suggest is making sure that async mode is enabled for SMPP under the advanced settings for the SMPP connections. This will help compensate some if the callbacks are slow and taking extra time to process.

I would like to see an SMSDEBUG.LOG to help me better understand the current callback timing.

I'd also like to see a current SMSOUT-yyyymmdd.LOG to help me understand the timing of outbound messages.

And finally, a screen capture of the "Serial #" page to validate your license details and to see what that threshold counter is indicating.

If you do not wish to post the details here, send to nowsms@nowsms.com with Attention: Des in the subject line.

--
Des
NowSMS Support

Login Login / Register Logout Logout Search Last 30 Days Topics Topics