Hi,

Thanks for the response.

Do you know what code to add and where to add the code in Kannel, to get
Kannel to call the dlr-url with NACK/xxx where xxx is the error code?

Rgds

> -----Original Message-----
> From: Peter Christensen [mailto:[EMAIL PROTECTED]
> Sent: 08 December 2005 13:51
> To: Andreas Fink
> Cc: [EMAIL PROTECTED]; Kannel Devel
> Subject: Re: How to pickup that you have run out of credits
>
>
> Hi,
>
> Just for the record - IF kannel did call the dlr-url, the state of the
> message would be NACK/xxx where xxx is the error code (as a decimal
> number, if I remember correct)
>
>
> Best regards
>
> Peter Christensen
>
> Andreas Fink wrote:
> >
> > On 30.11.2005, at 15:55, Hillel wrote:
> >
> >> Hi,
> >>
> >> Thanks for your response.
> >>
> >> Some SMSC providers indicate you have run out of credits by giving
> >> back in
> >> the bearerbox.log:
> >>
> >> 2005-11-28 23:19:10 [27849] [6] ERROR: SMPP[smsc1]: SMSC
> returned  error
> >> code 0x00000058 (Throttling error) in response to submit_sm.
> >> 2005-11-28 23:19:10 [27849] [6] DEBUG:   command_status: 88 =
> >> 0x00000058
> >>
> >> Their reasoning is there is no other parameter in the SMPP spec to
> >> indicate
> >> you have run out of credits. When this happens the SMS is not
> sent and I
> >> wondered if there is any way to get back the command_status when
> >> sending an
> >> SMS.
> >
> > there are other messages the SMSC can send back. Throttling is
> > definitively the wrong response. A real SMSC would not do that (most
> > real SMSC's dont have credit limits and only work postpaid) And frankly
> > having a DLR url for that would mean you get this being called even
> > withouth being out of credit but simply because you send a lot of data
> > quickly. Talk to your provider and ask him to send you back some other
> > error message which is more to the spec. I'm sure you talk to some
> > aggregator software, not a real SMSC.
> >
> > I just checked what our SMSC does in this case and it does return
> > ESME_RMSGQFUL if you have a connection bound. If you try to connect, it
> > returns ESME_RBINDFAIL. The problem with throttling is that its only a
> > TEMPORARY failure and Kannel MUST step back and wait a second
> or two and
> > then continue sending, meaning retrying the SMS over and over again.
> > Thats the purpose of the throttling message. Its there for flow
> control.
> > So it doesn't make any sense to generate any kind of DLR for it. It
> > would not result in what you are looking for.
> >
> >
> > Andreas Fink
> > Fink Consulting GmbH
> >
> > ---------------------------------------------------------------
> > Tel: +41-61-6666332 Fax: +41-61-6666331  Mobile: +41-79-2457333
> > Address: Clarastrasse 3, 4058 Basel, Switzerland
> > E-Mail:  [EMAIL PROTECTED]
> > Homepage: http://www.finkconsulting.com
> > ---------------------------------------------------------------
> >
> > ICQ: 101946485 MSN: [EMAIL PROTECTED] AIM: smsrelay Skype: andreasfink
> > Yahoo: finkconsulting SMS: +41792457333
> > PGP9: 0714 DF2B A189 A760 6201  5CBD D040 3E71 4DAF 68BB
> >
> >
> >
>
>



Reply via email to