Rene Kluwen wrote:
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.
yep, agree'ing here. It's a semantical misbehaviour in interpreting the specs
and the error (the invalid number in fact) from the SMSC side.
So we souldn't change a thing.
For the user itself that uses that "buggy" SMSC, I'd suggest that you garantee
that no invalid number is passed to the SMSC, ie. already filtering in the
application layer?
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
-------------------------------------------------------------------
