| With SMPPOption sending dr as submit_sm |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 16, 2008 ⬆ |
◄ ► |
| Author | Message | |||
| Jimmy Cherian New member Username: Jimmykc Post Number: 2 Registered: 05-2008 |
Dear Bryce, Kindly help regarding this issue, I have an operator he is requested for three smpp options to add on connecting with them and we had added and its working fine for MO and MT. But we are facing problem while using "SMPPOption_ChargingExtensionValue", because this parameter is checking the end user(mobile) has enough credit or not and if the end user doesn't have enough credits its(smsc) sending us error "00000457". Now here starts the problem when now sms receive this "unknown error" from smsc, It is sending another submit_sm with message as delivery report (id:48313EB4 sub:001 dlvrd:000 submit date:0805191250 done date:0805191250 stat:REJECTD err:457 text:Testing with charging). This second sumbit_sm we don't want to send. But this is working fine if we don't request the delivery report. Please help me urgently, On smsgw.ini file we have added SMPPRejectErrorCodes=FE,FF,450,457 also. Note:-Sorry mistakenly I posted on the advanced forum also. Regards Jims | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7576 Registered: 10-2002 |
Hi Jims, Apologies for the delay in response. I'd need to understand the message flow a little better. What I think is happening is that NowSMS is generating a non-delivery receipt because the SMSC rejected the message. NowSMS will do this ... only if the originally submitted message requested a delivery receipt. If no delivery receipt is requested, NowSMS will not generate this message. It sounds like you want other delivery receipts, just not this one? Wouldn't you have a similar problem with other delivery receipts generated by the operator also? -bn | |||
| Jimmy Cherian New member Username: Jimmykc Post Number: 3 Registered: 05-2008 |
Hi Bryce, Thank you for you reply and I am sorry for the delay caused, kindly check the following my questions. 1) If Content Provider asks for delivery report in submit_sm message, SMSC is sending back delivery report giving the final state of the message (delivered, expired, failed). What is non-delivery receipt and why is NowSMS generating it and sending it towards SMSC? 2) So if we ask for delivery report, SMSC is sending it. If we are submitting message and message fails (not sent), SMSC will not generate delivery report (message is not even sent), there is no need that NowSMS sends it (specially to SMSC). NowSMS should not send any delivery report messages towards SMSC, right? I think it is clear to you now, please advice on this. Waiting for you reply, Jims | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7629 Registered: 10-2002 |
Hi Jims, 1.) I don't know. I would need to see the message flow through your system in order to understand this better. Wait ... what version of NowSMS are you running? I found this change entry for 2007.01.30, which sounds like it describes your problem: * SMS Gateway: When a delivery (or non-delivery) receipt is requested, and the message is rejected at the SMSC submission level, NowSMS generates a delivery failure receipt. Fix for a problem with this feature where if the submitting user was using HTTP, NowSMS may try to route the delivery failure receipt externally to an SMSC connection instead of routing via 2-way SMS. That definitely sounds like the problem you are experiencing. The latest version of NowSMS will fix this. If your maintenance is expired and it won't let you apply this latest update, try this security update instead (which also includes this fix): http://www.nowsms.com/download/nowsms20080222.zip -bn | |||
| Jimmy Cherian New member Username: Jimmykc Post Number: 4 Registered: 05-2008 |
Thanks Bryce, You guys are the perfect for sms connections. Thank you Thank you  | |||
| Jimmy Cherian New member Username: Jimmykc Post Number: 5 Registered: 05-2008 |
Dear Bryce, One more Small question, While sending mt reply how I can check the value of submit_sm_resp ? Because depends on the submit_sm_resp we need to send another mt to the user. Please help me on this also. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7654 Registered: 10-2002 |
There isn't any way to do this. When NowSMS accepts the message from your application, it queues the message for outbound delivery. It won't know the submit_sm_resp from the service provider until after it has already sent the response back to your application. I've never heard of submit_sm_resp being used for this type of trigger. Perhaps if you can explain we can come up with a solution? | |||
| Jimmy Cherian New member Username: Jimmykc Post Number: 6 Registered: 05-2008 |
Dear Bryce, Thank you for the reply, here is what exactly our service provider requires from us. "NowSMS should send notification to user in case he doesn't have enough balance. Error 1111 in submit_sm_resp In case that you receive this error 0x0457, you should submit something like - please recharge your balance and try again. (charging code 0)" This error we can see on the sms_out file, is there any way I can get the error with the http or http response, so we can solve it. Please help us on this also Thank you Jims | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 16 Registered: 08-2008 |
Hi Jims, Bryce has been busy with several big projects, so he hasn't been able to get back to the discussion board. I'm not sure what the best way to handle this situation would be. NowSMS will not know the submit_sm_resp from the service provider until after it has sent the HTTP response back to your application. The only thing I could see would be to request a delivery report when you submit the message. If the message is rejected with this error code, you will get a non-delivery notification message back which should include this error code. As I look back to this thread, it looks like that is where you started. With the update fixing the circular routing of the non-delivery report, hopefully would again be able to try to sovle this with delivery report processing. -- Des NowSMS Support | |||
