Re: smsc routing problem

Rory

The quickest way to do what you want to do is to create two separate config
files, and run them as separate instances - this way you can use the default
filter to catch responses and do different things for them really easily.

Both of your SMPP connections are on 8000 so you're never going to get any
traffic on 8001 unless your SMSC configures this for you :)

Also look at using the denied-smsc-id= and preferred-smsc-id= in your group
= smsc's.

A user forum rather than dev. question?

Alex

> ########################################################################
> # SMSC
> ########################################################################
> group = smsc
> smsc-id = orangeshort
> allowed-smsc-id = orangeshort
> smsc = smpp
> host = xxxxxxxxxxxx
> port = 8000
> receive-port = 8000
> smsc-username = username
> smsc-password = password
> system-type = "SMPP"
> dest-addr-ton = 1
> dest-addr-npi = 1
> source-addr-ton = 3
> source-addr-npi = 1
>
> group = smsc
> smsc-id = orangelong
> allowed-smsc-id = orangelong
> smsc = smpp
> host = 193.36.81.53
> port = 8000
> receive-port = 8000
> smsc-username = username
> smsc-password = password
> system-type = "SMPP"
> dest-addr-ton = 2
> dest-addr-npi = 1
> source-addr-ton = 1
> source-addr-npi = 1