Hi,
this has been detected after trying to figure out why WAP OTA
configurations can not be send using the latest CVS snapshot:
The problem is valid for _both_ old CVS 2001-03-19 _and_ new CVS
2001-07-17!
Szenario:
We have 2 SMSCs configurated:
group = smsc
smsc-id = m20
smsc = at
denied-smsc-id = "emi;m20"
modemtype = siemens
device = /dev/ttyS1
pin = xxxx
group = smsc
smsc-id = emi
smsc = emi2
preferred-smsc-id = "emi;m20"
host = 1.2.3.4
port = 12345
smsc-username = xxx
smsc-password = xxx
receive-port = 700
and 2 sendsms-users, one for sending OTA configurations and the other
for text SMS. Both are forced to use emi via:
group = sendsms-user
[...]
forced-smsc = emi
so this configuration should _only_ send messages using smsc-id emi
and _not_ m20.
But(!) sometimes when there are a couple of incoming request from the
same or from both of the sendsms-users, the smsc-id m20 is chosen to
send the message. This happens especially in the following case:
sendsms-user A sends normal text SMS using emi
sendsms-user A sends first part of OTA SMS using emi
sendsms-user A sends second part of OTA SMS using m20 (GSM modem)
which obviosly breaks the OTA message.
I do think that there is something heavily broken within the SMS
routing in Kannel :((
To reproduce the problem setup one GSM modem which is used to get
incoming SMS messages and route all outgoing to an EMI connection.
Has anyone detected similiar problems within the routing?
Unfortunatly I'm currently very busy and don't have the time to serve
with a self-made fix, so assistance is highly welcome.
Regards,
Stipe
[EMAIL PROTECTED]
-------------------------------------------------------------------
Wapme Systems AG
M�nsterstr. 248
40470 D�sseldorf
Tel: +49-211-74845-0
Fax: +49-211-74845-299
E-Mail: [EMAIL PROTECTED]
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are
