Re: Malformed addr for Incoming short code
Stipe Tolj <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Organization | tolj.org system architecture |
| Message-ID | <[email protected]> |
Arne K. Haaje wrote: >> @Alex: is it enough to set 'dest-addr-ton', 'dest-addr-npi' inside >> smsc group to get rid of this. Or is the checking done before that and >> hence we baild out? > > > Yes, if we could set it ourself that would help a lot. I am seeing this > now on connections to two different operators with the latest snapshots. > Running an old snapshot (before the data_sm patch I think) make the > problem go away > >> @Amol: you should contact your SMSC provider and let them now that >> their desination-ton for the shortcode is not right, they should send >> the appropriate TON value for network internal numbers (shortcode). > > > I contacted on of the operators above regarding this, but they insisted > values were correct. Thus, they were unwilling to change anything and I > had to downgrade to an older version so it does not helo in setting 'dest-add-ton' ? Stipe