Re: TON error on SMSpush

Hi Alex. Thanks very much for your mail. I am using 1.3.1.
The problem I reported seems to be solveable by also setting the dest-addr-npi = 1.

Regards
Rory

On Thu, Mar 27, 2003 at 09:27:52PM -0000, Alex Judd wrote:
> Sounds like it might be a bug. The code was modified so that you can force
> the destination TON in the same way as you are forcing the source TON etc.
> but it looks like that's not working in the way it should do. I'll check my
> CVS version tomorrow and submit any bug changes necessary.

> ----- Original Message ----- 
> From: <[email protected]>
> To: <[email protected]>
> Sent: Thursday, March 27, 2003 9:05 PM
> Subject: TON error on SMSpush
> 
> 
> > Hi. I'm a newbie user of Kannel. I've posted a message to the user list
> but not heard a response yet, so I thought I would post a query here.
> >
> > I'm connecting to an Orange SMSC. I am sending using both short and long
> numbers. For the long numbers I need to se the source_addr_ton to 1 and for
> short numbers to 3. In both cases I need to set the dest_addr_ton to 1 (to
> target handsets).
> >
> > My SMSC Config has the lines:
> >  group=smsc
> >  smsc-id=oshort
> >  host = xxxxx
> >  port = 8000
> >  receive-port=8000
> >  smsc-username=xxx
> >  smsc-password=xxx
> >  system-type=SMPP
> >  dest-addr-ton=1
> >  source-addr-ton=3
> >  source-addr-npi=1
> >
> > However, while the bearerbox log shows that "Manually forced the source
> addr ton = 3, source add npi = 1", the dest_addr_ton is stuck on 2. This is
> odd, because is should default to 0.
> >
> > Is this a bug?
> > Thanks for any help
> > Rory
> 
>