Dlr Rejected

Dlr Rejected SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through May 19, 2016 » Dlr Rejected « Previous || Next »
Author Message
Diego Verlato
New member
Username: Diegover

Post Number: 1
Registered: 05-2015
Posted on Friday, May 15, 2015 - 02:45 pm:   

Hi,


We make a tests in nowsms but see a fail (maybe config).


I connect ozeki ----> nowsms ---> Iqsim (smsc) and make this test:


Send a sms to invalid number. Nowsms return this error code to Ozeki:

05/15/2015 11:32:13 - INFO 3512: Message successfully sent through connection: SMPP2.
05/15/2015 11:32:18 - INFO 3153: Matching delivery report received to reference '55563DE5'.
05/15/2015 11:32:18 - INFO 3515: Message delivery rejected. 045;TESTE


Now same test directly Ozeki to my Iqsim System:

05/15/2015 11:27:47 - INFO 3328: Sending message with sequence number 1139
05/15/2015 11:27:52 - [189.2.52.14:2775] -> 0000001880000004000000450000047300042300030301F4
05/15/2015 11:27:52 - ERROR 1363: Envelope rejected by SMSC. SMPP error 69.


So, the correct is Ozeki because the code is rerouteable. Nowsms send me DLR failed in this case (all cases i see) but correct is a SMS Refused and no a Delivery Failed. So, in this cases my client lost sms and cant reroute possible good numbers !

Maybe have a config to back correct code (sms refuse and delivery failed) to client.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5302
Registered: 08-2008
Posted on Friday, May 15, 2015 - 03:03 pm:   

Hi,

I'm sorry, but I don't have enough information to answer your question. I think I understand, but I may be missing your point.

NowSMS is a store-and-forward server.

So, when you submit the message to NowSMS (submit_sm), NowSMS accepts the message and returns a successful submit_sm_resp. At this point, it does not know that its upstream connection is going to reject the message. When the upstream server rejects the message, NowSMS generates the delivery report to indicate failure.

Unfortunately, that is the way it works with a store and forward system. There may be many clients submitting messages, and for performance reasons, it is not practical to delay the submit_sm_resp until an upstream attempt can be made.

If you know what number ranges the NowSMS server can handle (or if you have an API to query them), then a "PreAuth" accounting callback can be installed in NowSMS which allows you to proactively reject messages with an error code as they are submitted. If you want to learn about these callbacks, here is a reference: http://www.nowsms.com/doc/advanced-configuration-settings/sms-accounting-callbac ks

--
Des
NowSMS Support
Diego Verlato
New member
Username: Diegover

Post Number: 2
Registered: 05-2015
Posted on Friday, May 15, 2015 - 03:16 pm:   

Hi,


Ok, i understand this point. I dont want compare ozeki x nowsms, but Ozeki store sms too and in the cases of SMSC Reject SMS (queue full, no ports available or others error) system return error code (rerouteable) to client and not a Delivery Reject.

We have two types of error. SMSC Errors and Delivery Errors.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5303
Registered: 08-2008
Posted on Tuesday, May 19, 2015 - 04:02 pm:   

Hi,

I am sorry that NowSMS does not work the way you want it to.

Keep in mind that there may be multiple outbound routes defined to the NowSMS server, and that the outbound route might not even be SMPP based.

If we delayed the submit_sm_resp until an outbound delivery attempt could be made, this would increase the likelihood of unexpected client timeouts and undetected resubmissions/duplicates.

We are considering a "first delivery attempt" mode for future releases, which would be a per user account setting to delay upstream submission until an upstream submission was made.

All this said, I'd be very surprised if Ozeki had this type of mode. So it is possible that I am misunderstanding your issue. Are they returning an error in the submit_sm_resp, or is the DLR indicating a different non-permanent error condition?

--
Des
NowSMS Support
Diego Verlato
New member
Username: Diegover

Post Number: 3
Registered: 05-2015
Posted on Tuesday, May 19, 2015 - 11:32 pm:   

Hi,


Se this two condictions in Ozeki:

First is smsc reject sms (i use iqsim and one condiction for this error is port no have credit to send a sms) and my client receive this and can reroute for another route:

05/19/2015 20:13:08 - [199.9.99.99:2775] <- 0000006F00000004000000000001D757000101343431323334353637313100010135353131393535 3233363134340008000000000100000036564B3A203436313739202D20757365207468697320636F 646520746F20616374697661746520796F757220564B2070726F66696C652E
05/19/2015 20:13:08 - INFO 3328: Sending message with sequence number 120663
05/19/2015 20:13:39 - [199.99.99.99:2775] -> 0000001880000004000000450001D75700042300030301F4
05/19/2015 20:13:39 - ERROR 1363: Envelope rejected by SMSC. SMPP error 69.
05/19/2015 20:13:39 - [188.888.8.888:19126] <- 000000D20000000500000000000000B9000101353531313935353233363134340001013434313233 343536373131000400000000000000009969643A3933373036373639207375623A30303020646C76 72643A303030207375626D697420646174653A3135303531393038313320646F6E6520646174653A 3135303531393038313320737461743A52454A45435444206572723A30303120746578743A455252 4F5220313336333A20456E76656C6F70652072656A656374656420627920534D53432E20534D5050 206572726F722036392E
05/19/2015 20:13:39 - [188.888.8.888:19126] -> 000000118000000500000000000000B900


This is a second condiction (Dlr Rejected) and my client receive this:


05/19/2015 17:33:15 - INFO 3512: Message successfully sent through connection: SMS Internacional 2.
05/19/2015 17:33:18 - INFO 3153: Matching delivery report received to reference '1816211183'.
05/19/2015 17:33:18 - INFO 3515: Message delivery rejected. 024;....................
05/19/2015 17:33:18 - Returning delivery report to client
05/19/2015 17:33:18 - Getting SMPP sequence number
05/19/2015 17:33:18 - [00.00.000.00:50112] <- 000000A4000000050000000000000049000001353533353831313031313839000101343431323334 3536373131000400000000000000006C69643A3936323732393031207375623A30303020646C7672 643A303031207375626D697420646174653A3135303531393035333320646F6E6520646174653A31 35303531393035333320737461743A554E44454C4956206572723A30303020746578743A39363237 32393031
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5305
Registered: 08-2008
Posted on Wednesday, May 20, 2015 - 12:35 am:   

Hi,

OK, I'm glad I asked. I was misunderstanding your issue. I was thinking about somewhat complex technical scenarios, but the differences here are simple low-tech differences.

In both of your examples, the SMPP server is returning a DLR. The only real difference is the text of the DLR, which suggests that your client's SMPP application is parsing the text of the DLR in deciding what action to take.

In practice, NowSMS and Ozeki are returning very similar responses. If the client is behaving differently, then it is likely because it is looking for text that is very specific to Ozeki.

Here is the text as extracted from your example...

First condition (smsc reject/no credit):

id:93706769 sub:000 dlvrd:000 submit date:1505190813 done date:1505190813 stat:REJECTD err:001 text:ERROR 1363: Envelope rejected by SMSC. SMPP error 69.

Second condition (dlr rejected):

id:96272901 sub:000 dlvrd:001 submit date:1505190533 done date:1505190533 stat:UNDELIV err:000 text:96272901

With NowSMS, you would see a very similar DLR.

For the first condition:

id:93706769 sub:000 dlvrd:000 submit date:1505190813 done date:1505190813 stat:REJECTD err:??? text:xxxxxxxxxx

??? would be the upstream error code, which may be upstream provider specific. xxxxxxxxxx is the starting text of the original message.

For the second condition, the text of the DLR is generated by the upstream provider (if upstream is SMPP).

It looks to me like this client is looking for the text "ERROR 1363: Envelope rejected by SMSC. SMPP error 69." If so, that is a response that is very specific to Ozeki...and you should not expect to see that exact response from any other SMPP server.

I think you need to talk to whoever developed the SMPP client to get them to add some flexibility to handle similar conditions with other servers in different environments.


--
Des
NowSMS Support

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