RE: smpp, ton and npi problem

No need to change the source code in order to change the TON and NPI values used - the are configuration directives to do that.



--
Oded Arbel
m-Wise mobile solutions



> -----Original Message-----
> From: Damjan [mailto:[email protected]]
> Sent: Thursday, October 03, 2002 12:13 AM
> To: [email protected]
> Subject: smpp, ton and npi problem
> 
> 
> 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.
> 
> Curently I solve this problem by modifying smsc_smpp.c, and
> changind default ton and npi values.
> 
> 
> 
> 
> Another thing, I don't know if this is Comverse specific, but for
> alphanumeric source adresses, Comverse requires TON=5 and NPI=1.
> In Kannel it's TON=5 and NPI=0.
> 
> 
> 
> 
> 
> -- 
> Damjan Georgievski
> 
>