Re: smpp, ton and npi problem

Damjan <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <[email protected]>
> if you need different npi/ton settings than kannel default set you can use kannel.conf
> to set them:
> source-addr-ton = X
> dest-addr-ton   = X
> source-addr-npi = X
> dest-addr-npi   = X

I know this. But the problem then is that I can't send messages
with alphanumeric source.


>> I don't know if it is a bug, and I don't even know if it's
>> specific to SMPP only, but ... ok here is the problem.
>> 
>> I'm using latest kannel-cvs (as of now, with full SMPP debuging), and 
>> connecting to comverse SMPP smsc. When kannel receives a SMS from the
>> smsc, I get:
>> 
>>     source_addr_ton: 1 = 0x00000001
>>     source_addr_npi: 1 = 0x00000001
>>     source_addr: "38970359xxx"
>>     dest_addr_ton: 1 = 0x00000001
>>     dest_addr_npi: 1 = 0x00000001
>>     destination_addr: "221"
>> 
>> Now when kannel tries to reply to this message (the simplest
>> default sms-service returns a string only) it tries like this:
>>     source_addr_ton: 2 = 0x00000002
>>     source_addr_npi: 1 = 0x00000001
>>     source_addr: "221"
>>     dest_addr_ton: 2 = 0x00000002
>>     dest_addr_npi: 1 = 0x00000001
>>     destination_addr: "38970359xxx"
>> 
>> which doesn't work (the smsc returns an error). It would be
>> better if kannel would reply to the message with the same ton and
>> npi (both source and destination) as in the message received.

-- 
Damjan Georgievski
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.