Thanks for your solutions,
just using the allowed-prefix does not help, because you can generate a wrong number by a right prefix. but of course this is a good solution.
we intercept the wrong numbers in our application but it is very hard to catch all of errors if you don know the right format or even lenght of destinations.
some operators use the country code (as prefix) with defferent lenght for their numbers.
Hope this kind of problems been solved in the next version of SMPP ;-)
Regards
Mostafa
-----Original Message-----
From: Mihai Zsigmond [mailto:[EMAIL PROTECTED]]
Sent: Mon 2006/07/10 11:00 AM
To: Rene Kluwen; Stipe Tolj
Cc: Hadian, Mostafa; [email protected]
Subject: Re: SMPP status
Hi,
Sorry to barge in. This is tipical situation when everybody is right, but things dont't go as we need.
The guys at SMSC are somewhat right, it is a system error. The Kannel system is right, being a system error keeps retry.
Now to be practical. I doubt the guys at SMSC would change anything to point to some other error type. That leaves two other options for our friend Mostafa
1) use allowed-prefix= ... option in the configuration part to that link ot SMSC and put here only allowable code here; thus, the Kannel will fail the sending and not retry anymore.
2) intercept the wrong number at your application level and do not send it to SMSC.
Hope it helps.
Mihai Zsigmond
----- Original Message -----
From: Rene Kluwen
To: Stipe Tolj
Cc: Hadian, Mostafa ; [email protected]
Sent: Monday, July 10, 2006 3:08 AM
Subject: RE: SMPP status
Why?
Because it seems that their SMSC returns a RSYSERR (and keeps doing this) in
return of an invalid number.
It is a provider-error, non conform the specs.
Rene Kluwen
Chimit
-----Original Message-----
From: Stipe Tolj [mailto:[EMAIL PROTECTED]]
Sent: zondag 9 juli 2006 19:12
To: Rene Kluwen
Cc: Hadian, Mostafa; [email protected]
Subject: Re: SMPP status
Rene Kluwen wrote:
> SMPP statusA system error (SMPP_ESME_RSYSERR) is considered a temporary
> failure of the SMSC.
> So basically your smsc gives back an invalid error code.
>
> I would have expected an SMPP_ESME_RINVDSTADR or something like that.
>
> I am not sure if you have any influence on the peeps running the SMSC...
So
> they can change it... In the other (most probable) case, you can change
the
> function smpp_status_to_smscconn_failure_reason in gw/smsc/smsc_smpp.c and
> adjust the switch function.
why?... if this is a temporary error code, we are obliged to re-try.
Stipe
-------------------------------------------------------------------
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
-------------------------------------------------------------------
Title: RE: SMPP status
- RE: SMPP status Hadian, Mostafa
- Re: SMPP status Stipe Tolj
