Some questions
Dear all, I have more then 1 question; 1. Can I have multiple smsboxes for one number to have a sort of load balancing? 2. If I have different smsboxes can I also have different logs for all smsboxes and also different logs for the bearerbox? 3. When I can make multiple connections to the Telecom with more then one server, should I also need a hardware device between my adsl and my servers (something like a router with load balancing support)? Most of my questions are based on load balancing, I don't even know if I generate enough traffic that I need to start load balancing, because I heard Kannel should be able to handle much more sms/sec, but in real life I haven't been able to do this yet. Dave
configuration issues with Siemens MC35i
Hi all I've tried searching the archives and found lots of useful info but I'm not having success. I'm running 1.4.0 on Debian Here's part of my kannel.conf: group = core admin-port = 13000 admin-password = blah admin-allow-ip = 127.0.0.1 log-file = /tmp/kannel.log log-level = 1 access-log = access.log # Smsbox related smsbox-port = 13001 box-allow-ip = 127.0.0.1 store-file = kannel.store sms-incoming-queue-limit = 0 # Wapbox related udp-deny-ip = *.*.*.* include = /etc/kannel/modems.conf # SMSC GSM group = smsc smsc = at nokiaphone | ericsson modemtype = siemens_mc35i device = /dev/ttyUSB0 #pin = 2345 validityperiod = 167 ...and here's my modems.conf: group = modems id = siemens_mc35i name = Siemens MC35i detect-string = SIEMENS detect-string2 = MC35i init-string = AT+CNMI=1,2,0,1,1 init-string = AT+CSMS=1 speed = 115200 enable-hwhs = AT\\Q3 need-sleep = true I can communicate with the modem fine using minicom, with hw flowcontrol off, and speed set to 115200. When I fire up bearerbox, this is what I get: #/usr/sbin/bearerbox -v 1 /etc/kannel/kannel.conf INFO: Debug_lvl = 1, log_file = none, log_lvl = 0 WARNING: DLR: using default 'internal' for storage type. INFO: DLR using storage type: internal INFO: Added logfile `/tmp/kannel.log' with level `1'. INFO: Started access logfile `access.log'. INFO: HTTP: Opening server at port 13000. INFO: BOXC: 'smsbox-max-pending' not set, using default (100). INFO: DLR rerouting for smsc id (null) disabled. INFO: AT2[/dev/ttyUSB0]: configuration shows modemtype siemens_mc35i INFO: AT2[/dev/ttyUSB0]: read modem definition for Siemens MC35i INFO: INFO: Kannel bearerbox II version 1.4.0 starting INFO: Loading store file `kannel.store' INFO: Store-file size 1556, starting to unpack INFO: Retrieved 4 messages, non-acknowledged messages: 4 INFO: MAIN: Start-up done, entering mainloop INFO: AT2[/dev/ttyUSB0]: trying to use speed 115200 from modem definition/usr/sbin/bearerbox -v 1 /etc/kannel/kannel.conf 2008-02-07 12:34:48 [6364] [0] INFO: Debug_lvl = 1, log_file = none, log_lvl = 0 2008-02-07 12:34:48 [6364] [0] WARNING: DLR: using default 'internal' for storage type. 2008-02-07 12:34:48 [6364] [0] INFO: DLR using storage type: internal 2008-02-07 12:34:48 [6364] [0] INFO: Added logfile `/tmp/kannel.log' with level `1'. 2008-02-07 12:34:48 [6364] [0] INFO: Started access logfile `access.log'. 2008-02-07 12:34:48 [6364] [0] INFO: HTTP: Opening server at port 13000. 2008-02-07 12:34:48 [6364] [0] INFO: BOXC: 'smsbox-max-pending' not set, using default (100). 2008-02-07 12:34:48 [6364] [0] INFO: DLR rerouting for smsc id (null) disabled. 2008-02-07 12:34:48 [6364] [0] INFO: AT2[/dev/ttyUSB0]: configuration shows modemtype siemens_mc35i 2008-02-07 12:34:48 [6364] [0] INFO: AT2[/dev/ttyUSB0]: read modem definition for Siemens MC35i 2008-02-07 12:34:48 [6364] [0] INFO: 2008-02-07 12:34:48 [6364] [0] INFO: Kannel bearerbox II version 1.4.0 starting 2008-02-07 12:34:48 [6364] [0] INFO: Loading store file `kannel.store' 2008-02-07 12:34:48 [6364] [0] INFO: Store-file size 1556, starting to unpack 2008-02-07 12:34:48 [6364] [0] INFO: Retrieved 4 messages, non-acknowledged messages: 4 2008-02-07 12:34:48 [6364] [0] INFO: MAIN: Start-up done, entering mainloop 2008-02-07 12:34:48 [6364] [7] INFO: AT2[/dev/ttyUSB0]: trying to use speed 115200 from modem definition 2008-02-07 12:34:48 [6364] [7] INFO: AT2[/dev/ttyUSB0]: opening device 2008-02-07 12:34:49 [6364] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 115200 2008-02-07 12:35:03 [6364] [7] INFO: AT2[/dev/ttyUSB0]: closing device 2008-02-07 12:35:03 [6364] [7] INFO: AT2[/dev/ttyUSB0]: speed in modem definition don't work, will autodetect 2008-02-07 12:35:03 [6364] [7] INFO: AT2[/dev/ttyUSB0]: opening device 2008-02-07 12:35:04 [6364] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 115200 2008-02-07 12:35:18 [6364] [7] INFO: AT2[/dev/ttyUSB0]: closing device 2008-02-07 12:35:18 [6364] [7] INFO: AT2[/dev/ttyUSB0]: opening device 2008-02-07 12:35:19 [6364] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 57600 AT2[/dev/ttyUSB0]: opening device INFO: AT2[/dev/ttyUSB0]: speed set to 115200 INFO: AT2[/dev/ttyUSB0]: closing device AT2[/dev/ttyUSB0]: speed in modem definition don't work, will autodetect AT2[/dev/ttyUSB0]: opening device AT2[/dev/ttyUSB0]: speed set to 115200 INFO: AT2[/dev/ttyUSB0]: closing device INFO: AT2[/dev/ttyUSB0]: opening device INFO: AT2[/dev/ttyUSB0]: speed set to 57600 [...] the last few lines keep repeating, with decreasing speeds to 9600, then it starts again at 115200. I'm tearing my hair out here - can someone point out what is obviously a glaring error in my config's above? Many thanks in anticipation Peter Salvage
Re: configuration issues with Siemens MC35i
Hi Tommi My notebook doesn't have a serial port so I'm using a USB to Serial port converter. Regards, Peter Tommi Linna wrote: I think you are not connecting to modem using USB, are you? The modem doesn't have USB port as far as I know. My modem is connected throught serial cable and that information should be used in Debian also. Try setting device = /dev/ttyUSB0 to device = /dev/ttyS0. BTW, I'm having problems with Siemens modem. For some reason it seems to freeze computer totally occasionally (couple of times a week). Any body with Siemens MC35i had similar issues? BR, Tommi Peter Salvage kirjoitti: Hi all I've tried searching the archives and found lots of useful info but I'm not having success. I'm running 1.4.0 on Debian Here's part of my kannel.conf: group = core admin-port = 13000 admin-password = blah admin-allow-ip = 127.0.0.1 log-file = /tmp/kannel.log log-level = 1 access-log = access.log # Smsbox related smsbox-port = 13001 box-allow-ip = 127.0.0.1 store-file = kannel.store sms-incoming-queue-limit = 0 # Wapbox related udp-deny-ip = *.*.*.* include = /etc/kannel/modems.conf # SMSC GSM group = smsc smsc = at nokiaphone | ericsson modemtype = siemens_mc35i device = /dev/ttyUSB0 #pin = 2345 validityperiod = 167 ...and here's my modems.conf: group = modems id = siemens_mc35i name = Siemens MC35i detect-string = SIEMENS detect-string2 = MC35i init-string = AT+CNMI=1,2,0,1,1 init-string = AT+CSMS=1 speed = 115200 enable-hwhs = AT\\Q3 need-sleep = true I can communicate with the modem fine using minicom, with hw flowcontrol off, and speed set to 115200. When I fire up bearerbox, this is what I get: #/usr/sbin/bearerbox -v 1 /etc/kannel/kannel.conf INFO: Debug_lvl = 1, log_file = none, log_lvl = 0 WARNING: DLR: using default 'internal' for storage type. INFO: DLR using storage type: internal INFO: Added logfile `/tmp/kannel.log' with level `1'. INFO: Started access logfile `access.log'. INFO: HTTP: Opening server at port 13000. INFO: BOXC: 'smsbox-max-pending' not set, using default (100). INFO: DLR rerouting for smsc id (null) disabled. INFO: AT2[/dev/ttyUSB0]: configuration shows modemtype siemens_mc35i INFO: AT2[/dev/ttyUSB0]: read modem definition for Siemens MC35i INFO: INFO: Kannel bearerbox II version 1.4.0 starting INFO: Loading store file `kannel.store' INFO: Store-file size 1556, starting to unpack INFO: Retrieved 4 messages, non-acknowledged messages: 4 INFO: MAIN: Start-up done, entering mainloop INFO: AT2[/dev/ttyUSB0]: trying to use speed 115200 from modem definition/usr/sbin/bearerbox -v 1 /etc/kannel/kannel.conf 2008-02-07 12:34:48 [6364] [0] INFO: Debug_lvl = 1, log_file = none, log_lvl = 0 2008-02-07 12:34:48 [6364] [0] WARNING: DLR: using default 'internal' for storage type. 2008-02-07 12:34:48 [6364] [0] INFO: DLR using storage type: internal 2008-02-07 12:34:48 [6364] [0] INFO: Added logfile `/tmp/kannel.log' with level `1'. 2008-02-07 12:34:48 [6364] [0] INFO: Started access logfile `access.log'. 2008-02-07 12:34:48 [6364] [0] INFO: HTTP: Opening server at port 13000. 2008-02-07 12:34:48 [6364] [0] INFO: BOXC: 'smsbox-max-pending' not set, using default (100). 2008-02-07 12:34:48 [6364] [0] INFO: DLR rerouting for smsc id (null) disabled. 2008-02-07 12:34:48 [6364] [0] INFO: AT2[/dev/ttyUSB0]: configuration shows modemtype siemens_mc35i 2008-02-07 12:34:48 [6364] [0] INFO: AT2[/dev/ttyUSB0]: read modem definition for Siemens MC35i 2008-02-07 12:34:48 [6364] [0] INFO: 2008-02-07 12:34:48 [6364] [0] INFO: Kannel bearerbox II version 1.4.0 starting 2008-02-07 12:34:48 [6364] [0] INFO: Loading store file `kannel.store' 2008-02-07 12:34:48 [6364] [0] INFO: Store-file size 1556, starting to unpack 2008-02-07 12:34:48 [6364] [0] INFO: Retrieved 4 messages, non-acknowledged messages: 4 2008-02-07 12:34:48 [6364] [0] INFO: MAIN: Start-up done, entering mainloop 2008-02-07 12:34:48 [6364] [7] INFO: AT2[/dev/ttyUSB0]: trying to use speed 115200 from modem definition 2008-02-07 12:34:48 [6364] [7] INFO: AT2[/dev/ttyUSB0]: opening device 2008-02-07 12:34:49 [6364] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 115200 2008-02-07 12:35:03 [6364] [7] INFO: AT2[/dev/ttyUSB0]: closing device 2008-02-07 12:35:03 [6364] [7] INFO: AT2[/dev/ttyUSB0]: speed in modem definition don't work, will autodetect 2008-02-07 12:35:03 [6364] [7] INFO: AT2[/dev/ttyUSB0]: opening device 2008-02-07 12:35:04 [6364] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 115200 2008-02-07 12:35:18 [6364] [7] INFO: AT2[/dev/ttyUSB0]: closing device 2008-02-07 12:35:18 [6364] [7] INFO: AT2[/dev/ttyUSB0]: opening device 2008-02-07 12:35:19 [6364] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 57600 AT2[/dev/ttyUSB0]: opening device INFO: AT2[/dev/ttyUSB0]: speed set to 115200 INFO: AT2[/dev/ttyUSB0]: closing device AT2[/dev/ttyUSB0]: speed in modem definition don't work, will autodetect AT2[/dev/ttyUSB0]:
Re: SMPP to HTTP
You have no idea? Please.. Mickael - System Administrator (WebD Services) a écrit : Hello !! I would like to use as a gateway kannel SMPP to HTTP. Example: SMPP port (Kannel) Port: 13002 User: Client1 Pass: lambda User: Client2 Pass: lambda Connection OK. Kannel sent to : http://sms.myprovider.com/SendSMS.php?user=myuserpassword=mypassto=%tocontent=%msg I did not fully understand the configuration of Kannel. All the examples that I try to put into practice only work ever. Can you help? Thanks
Re: configuration issues with Siemens MC35i
My modem config . # SIEMENS MODEM SETUP group = modems id = SIEMENS MC35i name = siemens_ mc35i detect-string = SIEMENS detect-string2 = MC35i init-string = AT+CNMI=1,2,0,1,1 enable-hwhs = AT\\Q3 need-sleep = true and my smsc .. # SMSC CONNECTIONS group = smsc smsc = at modemtype = auto device = /dev/ttyS0 speed = 9600 that works like magic 4 me --- Peter Salvage [EMAIL PROTECTED] wrote: Hi Tommi My notebook doesn't have a serial port so I'm using a USB to Serial port converter. Regards, Peter Tommi Linna wrote: I think you are not connecting to modem using USB, are you? The modem doesn't have USB port as far as I know. My modem is connected throught serial cable and that information should be used in Debian also. Try setting device = /dev/ttyUSB0 to device = /dev/ttyS0. BTW, I'm having problems with Siemens modem. For some reason it seems to freeze computer totally occasionally (couple of times a week). Any body with Siemens MC35i had similar issues? BR, Tommi Peter Salvage kirjoitti: Hi all I've tried searching the archives and found lots of useful info but I'm not having success. I'm running 1.4.0 on Debian Here's part of my kannel.conf: group = core admin-port = 13000 admin-password = blah admin-allow-ip = 127.0.0.1 log-file = /tmp/kannel.log log-level = 1 access-log = access.log # Smsbox related smsbox-port = 13001 box-allow-ip = 127.0.0.1 store-file = kannel.store sms-incoming-queue-limit = 0 # Wapbox related udp-deny-ip = *.*.*.* include = /etc/kannel/modems.conf # SMSC GSM group = smsc smsc = at nokiaphone | ericsson modemtype = siemens_mc35i device = /dev/ttyUSB0 #pin = 2345 validityperiod = 167 ...and here's my modems.conf: group = modems id = siemens_mc35i name = Siemens MC35i detect-string = SIEMENS detect-string2 = MC35i init-string = AT+CNMI=1,2,0,1,1 init-string = AT+CSMS=1 speed = 115200 enable-hwhs = AT\\Q3 need-sleep = true I can communicate with the modem fine using minicom, with hw flowcontrol off, and speed set to 115200. When I fire up bearerbox, this is what I get: #/usr/sbin/bearerbox -v 1 /etc/kannel/kannel.conf INFO: Debug_lvl = 1, log_file = none, log_lvl = 0 WARNING: DLR: using default 'internal' for storage type. INFO: DLR using storage type: internal INFO: Added logfile `/tmp/kannel.log' with level `1'. INFO: Started access logfile `access.log'. INFO: HTTP: Opening server at port 13000. INFO: BOXC: 'smsbox-max-pending' not set, using default (100). INFO: DLR rerouting for smsc id (null) disabled. INFO: AT2[/dev/ttyUSB0]: configuration shows modemtype siemens_mc35i INFO: AT2[/dev/ttyUSB0]: read modem definition for Siemens MC35i INFO: INFO: Kannel bearerbox II version 1.4.0 starting INFO: Loading store file `kannel.store' INFO: Store-file size 1556, starting to unpack INFO: Retrieved 4 messages, non-acknowledged messages: 4 INFO: MAIN: Start-up done, entering mainloop INFO: AT2[/dev/ttyUSB0]: trying to use speed 115200 from modem definition/usr/sbin/bearerbox -v 1 /etc/kannel/kannel.conf 2008-02-07 12:34:48 [6364] [0] INFO: Debug_lvl = 1, log_file = none, log_lvl = 0 2008-02-07 12:34:48 [6364] [0] WARNING: DLR: using default 'internal' for storage type. 2008-02-07 12:34:48 [6364] [0] INFO: DLR using storage type: internal 2008-02-07 12:34:48 [6364] [0] INFO: Added logfile `/tmp/kannel.log' with level `1'. 2008-02-07 12:34:48 [6364] [0] INFO: Started access logfile `access.log'. 2008-02-07 12:34:48 [6364] [0] INFO: HTTP: Opening server at port 13000. 2008-02-07 12:34:48 [6364] [0] INFO: BOXC: 'smsbox-max-pending' not set, using default (100). 2008-02-07 12:34:48 [6364] [0] INFO: DLR rerouting for smsc id (null) disabled. 2008-02-07 12:34:48 [6364] [0] INFO: AT2[/dev/ttyUSB0]: configuration shows modemtype siemens_mc35i 2008-02-07 12:34:48 [6364] [0] INFO: AT2[/dev/ttyUSB0]: read modem definition for Siemens MC35i 2008-02-07 12:34:48 [6364] [0] INFO: 2008-02-07 12:34:48 [6364] [0] INFO: Kannel bearerbox II version 1.4.0 starting 2008-02-07 12:34:48 [6364] [0] INFO: Loading store file `kannel.store' 2008-02-07 12:34:48 [6364] [0] INFO: Store-file size 1556, starting to unpack 2008-02-07 12:34:48 [6364] [0] INFO: Retrieved 4 messages, non-acknowledged messages: 4 2008-02-07 12:34:48 [6364] [0] INFO: MAIN: Start-up done, entering mainloop 2008-02-07 12:34:48 [6364] [7] INFO: AT2[/dev/ttyUSB0]: trying to use speed 115200 from modem definition 2008-02-07 12:34:48 [6364] [7] INFO: AT2[/dev/ttyUSB0]: opening device 2008-02-07 12:34:49 [6364] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 115200 2008-02-07 12:35:03 [6364] [7] INFO: AT2[/dev/ttyUSB0]: closing device 2008-02-07 12:35:03 [6364] [7] INFO:
Re: How to override GSM encoding ? (Kannel 1.4.1-2 / Debian)
Hi Stipe,
Thank you for your answer.
Ok, i'll try to test gw/sms.c:fields_to_dcs().
So, is there a temporaly hack to force dcs to 0 ?
Regards,
Olivier PELLEGRINO
MIL'NR3
Le jeudi 07 février 2008 à 15:42 +0100, Stipe Tolj a écrit :
Olivier PELLEGRINO schrieb:
Output:
2008-02-05 15:42:28 [20444] [14] DEBUG: [debug perso #1]
msg-sms.alt_dcs: -1, smpp-conn-alt_dcs: 0,
pdu-u.submit_sm.data_coding: 0, SMPP_DEFAULT_CHARSET: UTF-8,
smpp-alt_charset: ISO-8859-1
2008-02-05 15:42:28 [20444] [14] DEBUG: [debug perso #2] if condition
2008-02-05 15:42:28 [20444] [14] DEBUG: [debug perso #3]
msg-sms.alt_dcs: -1, smpp-conn-alt_dcs: 0,
pdu-u.submit_sm.data_coding: 241, SMPP_DEFAULT_CHARSET: UTF-8,
smpp-alt_charset: ISO-8859-1
ok, which proves that the submit_sm.data_coding = 241 is set within the if
condition branch, hence via fields_to_dcs(msg, 1);
Please check within gw/sms.c:fields_to_dcs() which if branch set the dcs
value
accordingly.
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: sendota with kannel 1.4.1
Remon Magdy schrieb:
Hello Stipe,
I've had the same issue and wasn't able to send any OMA OTA settings to
any device, while I used the same XML document with nowsms and it was
successfully submitted, I think there is a problem with Kannel in that
area.
Hi Remon,
which Kannel version have you been using? Can you please confirm that this
effect is still within CVS HEAD?
Meaning: please define which XML input you used, and if it worked with NowSMS
and didn't work with Kannel.
If this is really the case then I (or Aarno) should get into the byte-code
mangling to see what is going on.
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: SMPP to HTTP
Mickael - System Administrator (WebD Services) schrieb:
Hello !!
I would like to use as a gateway kannel SMPP to HTTP.
Example:
SMPP port (Kannel)
Port: 13002
User: Client1
Pass: lambda
User: Client2
Pass: lambda
Connection OK.
Kannel sent to :
http://sms.myprovider.com/SendSMS.php?user=myuserpassword=mypassto=%tocontent=%msg
I did not fully understand the configuration of Kannel.
All the examples that I try to put into practice only work ever.
the architecture is not quite clear to me. Which protocol is the server side and
which is the client side?
If you are trying to do something like this:
SMSC -HTTP- kannel -SMPP- clients
then you can't do this with the normal Kannel, since you will require the SMPP
server side, providing full SMPP v3.4 server capabilities for the clients
connecting. For this purpose I'm offering the Kannel SMPP v3.4 server (smppbox)
commercial add-on.
If you try to do it the other way arround:
SMSC -SMPP- kannel -HTTP- clients
then Kannel obviously does exactly this. Then you should consult the user's
guide and get yourself known with the details.
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: sendota with kannel 1.4.1
Hello Stipe,
Actually all OMA documents didn't work, e.g XML document below
wap-provisioningdoc
characteristic type=BOOTSTRAP
parm name=NAME value=IRAQNA WAP/
parm name=PROXY-ID value= WAP_Proxy/
/characteristic
characteristic type=NAPDEF
parm name=NAME value= WAP/
parm name=NAPID value= WAP_NAPID/
parm name=BEARER value=GSM-GPRS/
parm name=NAP-ADDRESS value=wap1/
parm name=NAP-ADDRTYPE value=APN/
/characteristic
characteristic type=PXLOGICAL
parm name=NAME value= WAP/
parm name=PROXY-ID value= WAP_Proxy/
characteristic type=PXPHYSICAL
parm name=PHYSICAL-PROXY-ID value= WAP_PhProxy/
parm name=PXADDR value=10.10.10.1/
parm name=PXADDRTYPE value=IPV4/
parm name=TO-NAPID value= WAP_NAPID/
characteristic type=PORT
parm name=PORTNBR value=8080/
/characteristic
/characteristic
/characteristic
characteristic type=APPLICATION
parm name=APPID value=w2/
parm name=NAME value= WAP/
parm name=TO-PROXY value= WAP_Proxy/
characteristic type=RESOURCE
parm name=NAME value= WAP/
parm name=URI value=http://www..com/
parm name=STARTPAGE/
/characteristic
/characteristic
/wap-provisioningdoc
This document works from NowSMS but not from Kannel, I've traced the
WBXML for both and it is different, I think there is a conversion problem.
Regards,
Remon
Stipe Tolj wrote:
Remon Magdy schrieb:
Hello Stipe,
I've had the same issue and wasn't able to send any OMA OTA settings
to any device, while I used the same XML document with nowsms and it
was successfully submitted, I think there is a problem with Kannel in
that area.
Hi Remon,
which Kannel version have you been using? Can you please confirm that
this effect is still within CVS HEAD?
Meaning: please define which XML input you used, and if it worked with
NowSMS and didn't work with Kannel.
If this is really the case then I (or Aarno) should get into the
byte-code mangling to see what is going on.
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: How to override GSM encoding ? (Kannel 1.4.1-2 / Debian)
Hi,
The wrong dcs value is fixed in this part (gw/sms.c) :
/* mode 1 */
else {
debug(bb.sms.smpp, 0, [debug perso #1] dcs: %d, dcs);
dcs |= 0xF0; /* sets bits 7-3 */
debug(bb.sms.smpp, 0, [debug perso #2] dcs: %d, dcs);
if(msg-sms.coding != DC_UNDEF){
dcs |= (msg-sms.coding 2); /* only DC_7BIT or
DC_8BIT, sets bit 2*/
debug(bb.sms.smpp, 0, [debug perso #3] dcs: %d,
dcs);
}
if (msg-sms.mclass == MC_UNDEF){
dcs |= 1; /* default meaning: ME specific */
debug(bb.sms.smpp, 0, [debug perso #4] dcs: %d,
dcs);
}else{
dcs |= msg-sms.mclass; /* sets bit 1,0 */
debug(bb.sms.smpp, 0, [debug perso #5] dcs: %d,
dcs);
}
debug(bb.sms.smpp, 0, [debug perso #6] dcs: %d, dcs);
}
Logs :
2008-02-07 17:37:18 [11772] [14] DEBUG: [debug perso #1] dcs: 0
2008-02-07 17:37:18 [11772] [14] DEBUG: [debug perso #2] dcs: 240
2008-02-07 17:37:18 [11772] [14] DEBUG: [debug perso #3] dcs: 240
2008-02-07 17:37:18 [11772] [14] DEBUG: [debug perso #5] dcs: 241
2008-02-07 17:37:18 [11772] [14] DEBUG: [debug perso #6] dcs: 241
Regards,
Olivier PELLEGRINO
MIL'NR3
Le jeudi 07 février 2008 à 15:42 +0100, Stipe Tolj a écrit :
Olivier PELLEGRINO schrieb:
Output:
2008-02-05 15:42:28 [20444] [14] DEBUG: [debug perso #1]
msg-sms.alt_dcs: -1, smpp-conn-alt_dcs: 0,
pdu-u.submit_sm.data_coding: 0, SMPP_DEFAULT_CHARSET: UTF-8,
smpp-alt_charset: ISO-8859-1
2008-02-05 15:42:28 [20444] [14] DEBUG: [debug perso #2] if condition
2008-02-05 15:42:28 [20444] [14] DEBUG: [debug perso #3]
msg-sms.alt_dcs: -1, smpp-conn-alt_dcs: 0,
pdu-u.submit_sm.data_coding: 241, SMPP_DEFAULT_CHARSET: UTF-8,
smpp-alt_charset: ISO-8859-1
ok, which proves that the submit_sm.data_coding = 241 is set within the if
condition branch, hence via fields_to_dcs(msg, 1);
Please check within gw/sms.c:fields_to_dcs() which if branch set the dcs
value
accordingly.
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: How to override GSM encoding ? (Kannel 1.4.1-2 / Debian)
Hi Stipe,
Ok, i understand.
So, it's possible to have a dcs value of 0 ONLY when we send flash
sms (directly displayed) ?!
I need dcs=0 also with normal sms (sms to mobile) ...
Is it possible ?
Thanks.
Regards,
Olivier PELLEGRINO
MIL'NR3
Le jeudi 07 février 2008 à 18:54 +0100, Stipe Tolj a écrit :
Olivier PELLEGRINO schrieb:
Hi,
The wrong dcs value is fixed in this part (gw/sms.c) :
/* mode 1 */
else {
debug(bb.sms.smpp, 0, [debug perso #1] dcs: %d, dcs);
dcs |= 0xF0; /* sets bits 7-3 */
debug(bb.sms.smpp, 0, [debug perso #2] dcs: %d, dcs);
if(msg-sms.coding != DC_UNDEF){
dcs |= (msg-sms.coding 2); /* only DC_7BIT or
DC_8BIT, sets bit 2*/
debug(bb.sms.smpp, 0, [debug perso #3] dcs: %d,
dcs);
}
if (msg-sms.mclass == MC_UNDEF){
dcs |= 1; /* default meaning: ME specific */
debug(bb.sms.smpp, 0, [debug perso #4] dcs: %d,
dcs);
}else{
dcs |= msg-sms.mclass; /* sets bit 1,0 */
debug(bb.sms.smpp, 0, [debug perso #5] dcs: %d,
dcs);
}
debug(bb.sms.smpp, 0, [debug perso #6] dcs: %d, dcs);
}
Logs :
2008-02-07 17:37:18 [11772] [14] DEBUG: [debug perso #1] dcs: 0
2008-02-07 17:37:18 [11772] [14] DEBUG: [debug perso #2] dcs: 240
ok, this means we have this within gw/smsc/smsc_smpp.c:
/*
* set the data coding scheme (DCS) field
* check if we have a forced value for this from the smsc-group.
* Note: if message class is set, then we _must_ force alt_dcs otherwise
* dcs has reserved values (e.g. mclass=2, dcs=0x11). We check MWI flag
* first here, because MWI and MCLASS can not be set at the same time and
* function fields_to_dcs check MWI first, so we have no need to force
alt_dcs
* if MWI is set.
*/
if (msg-sms.mwi == MWI_UNDEF msg-sms.mclass != MC_UNDEF)
pdu-u.submit_sm.data_coding = fields_to_dcs(msg, 1); /* force
alt_dcs */
else
hence mclass IS SET, correct?
checking your mail resolved that you DID send:
X-Kannel-Mclass: 1
Bingo, that's the reason we are forced to set the dcs value. If you need
dcs=0,
ensure you don't send mclass towards smsbox.
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: SMPP retries set to null for SMSC
Hi George,
[EMAIL PROTECTED] schrieb:
Yes thanks Stipe,
Yes you have correctly understood, but its not our end resending, but
its the final SMSc or intermediate SMPP provider.
I was hoping maybe there could be someway to send messages to instruct
either the intermediate SMPP or final SMSc not to retry to send even
when it has not received some ACK from handset. From what you have
mentioned this is not possible due to strict SMPP spec.
this sounds like a hassle with the SMSC communication layer. Obviously either
the final SMSC has issues on the SS7 layer while signaling the SM to the device,
or the intermediary SMPP server resends messages to the final SMSC.
In any case, it's out of scope from what we (you and Kannel) can see or change.
So the SMPP servers that we are pushing SMS to are playing up and
resending messages.. too many!!
I guess we can't do anything about it from our end then :(
yep, that's right... all you can do it claim the misbehavior to your SMPP
provider. Can you drop me a private note on which one it is?
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: SMPP retries set to null for SMSC
Yes thanks Stipe,
Yes you have correctly understood, but its not our end resending, but
its the final SMSc or intermediate SMPP provider.
I was hoping maybe there could be someway to send messages to instruct
either the intermediate SMPP or final SMSc not to retry to send even
when it has not received some ACK from handset. From what you have
mentioned this is not possible due to strict SMPP spec.
So the SMPP servers that we are pushing SMS to are playing up and
resending messages.. too many!!
I guess we can't do anything about it from our end then :(
Thanks again.
G
Is there any SMPP parameter that will prevent SMSc from trying to
resend SMS (MT's) when there is no ack from handset?
Carriers SMSc is playing up and resending SMS assuming that they
haven't been delivered, therefore if we can force a parameter maybe we
help the SMSc not to resend.
?? the inquiry isn't clear to me.
bearerbox sends submit_sm PDUs towards an SMPP SMSC. If the SMSC fails to ack
the PDU via submit_sm_resp PDU, bearerbox has to assume that the MT is not
accepted/delivered, hence bearerbox will retry.
Is this what you mean?
BTW, there is no way to accept silently a non-acked submit_sm PDU, since the
SMPP spec is strict about confirmations with response PDUs. We can't think
it's ok that we passed PDU to SMSC if we don't get any response. There must
be a
reason why we don't get a response PDU, and that reason is either technical
issue on the underlying communication layer or a broken SMPP server.
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: sendota with kannel 1.4.1
Remon Magdy schrieb:
Hello Stipe,
Actually all OMA documents didn't work, e.g XML document below
wap-provisioningdoc
characteristic type=BOOTSTRAP
parm name=NAME value=IRAQNA WAP/
parm name=PROXY-ID value= WAP_Proxy/
/characteristic
characteristic type=NAPDEF
parm name=NAME value= WAP/
parm name=NAPID value= WAP_NAPID/
parm name=BEARER value=GSM-GPRS/
parm name=NAP-ADDRESS value=wap1/
parm name=NAP-ADDRTYPE value=APN/
/characteristic
characteristic type=PXLOGICAL
parm name=NAME value= WAP/
parm name=PROXY-ID value= WAP_Proxy/
characteristic type=PXPHYSICAL
parm name=PHYSICAL-PROXY-ID value= WAP_PhProxy/
parm name=PXADDR value=10.10.10.1/
parm name=PXADDRTYPE value=IPV4/
parm name=TO-NAPID value= WAP_NAPID/
characteristic type=PORT
parm name=PORTNBR value=8080/
/characteristic
/characteristic
/characteristic
characteristic type=APPLICATION
parm name=APPID value=w2/
parm name=NAME value= WAP/
parm name=TO-PROXY value= WAP_Proxy/
characteristic type=RESOURCE
parm name=NAME value= WAP/
parm name=URI value=http://www..com/
parm name=STARTPAGE/
/characteristic
/characteristic
/wap-provisioningdoc
This document works from NowSMS but not from Kannel, I've traced the
WBXML for both and it is different, I think there is a conversion problem.
Hi Remon,
thanks for the detailed example.
Did you check latest CVS HEAD, where I had commited a change recently:
2008-02-02 Stipe Tolj stolj at kannel.org
* gw/ota_compiler.c: fix bug #405, where we forget to switch codepage
when no inline value is processed for WBXML compilation. Thanks go to
Maxim Sobolev sobomax at sippysoft.com for reporting and proving patch.
[Msg-Id: [EMAIL PROTECTED]]
can you confirm that this patch solves or even breaks the OMA OTA?
I'd like to ask you kindly to try a CVS version before and after this commit, to
confirm if this patch itself is maybe causing the break or fixes. From reviewing
Maxim's patch this should be of course a fix.
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: How to override GSM encoding ? (Kannel 1.4.1-2 / Debian)
Olivier PELLEGRINO schrieb:
Hi,
The wrong dcs value is fixed in this part (gw/sms.c) :
/* mode 1 */
else {
debug(bb.sms.smpp, 0, [debug perso #1] dcs: %d, dcs);
dcs |= 0xF0; /* sets bits 7-3 */
debug(bb.sms.smpp, 0, [debug perso #2] dcs: %d, dcs);
if(msg-sms.coding != DC_UNDEF){
dcs |= (msg-sms.coding 2); /* only DC_7BIT or
DC_8BIT, sets bit 2*/
debug(bb.sms.smpp, 0, [debug perso #3] dcs: %d,
dcs);
}
if (msg-sms.mclass == MC_UNDEF){
dcs |= 1; /* default meaning: ME specific */
debug(bb.sms.smpp, 0, [debug perso #4] dcs: %d,
dcs);
}else{
dcs |= msg-sms.mclass; /* sets bit 1,0 */
debug(bb.sms.smpp, 0, [debug perso #5] dcs: %d,
dcs);
}
debug(bb.sms.smpp, 0, [debug perso #6] dcs: %d, dcs);
}
Logs :
2008-02-07 17:37:18 [11772] [14] DEBUG: [debug perso #1] dcs: 0
2008-02-07 17:37:18 [11772] [14] DEBUG: [debug perso #2] dcs: 240
ok, this means we have this within gw/smsc/smsc_smpp.c:
/*
* set the data coding scheme (DCS) field
* check if we have a forced value for this from the smsc-group.
* Note: if message class is set, then we _must_ force alt_dcs otherwise
* dcs has reserved values (e.g. mclass=2, dcs=0x11). We check MWI flag
* first here, because MWI and MCLASS can not be set at the same time and
* function fields_to_dcs check MWI first, so we have no need to force
alt_dcs
* if MWI is set.
*/
if (msg-sms.mwi == MWI_UNDEF msg-sms.mclass != MC_UNDEF)
pdu-u.submit_sm.data_coding = fields_to_dcs(msg, 1); /* force alt_dcs
*/
else
hence mclass IS SET, correct?
checking your mail resolved that you DID send:
X-Kannel-Mclass: 1
Bingo, that's the reason we are forced to set the dcs value. If you need dcs=0,
ensure you don't send mclass towards smsbox.
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: Un-predictable SMS Behavior
hi Vinay, If its with some GSM modem; just play with your AT+CNMI initialization in your modem.conf file. these initialization parameters varies for different vendors - for Sierra875 Aircard, working configuration are group = modems id = sierra875 name = sierra875 init-string = AT+CNMI=1,1,0,1,0 speed = 115200 #need-sleep = true regards, Hammad On Feb 7, 2008 8:11 PM, [EMAIL PROTECTED] wrote: Hi Hammad, Do you know what you changed. I am running into the same issue. Thanks, Vinay Hammad-5 wrote: Hello Everyone, Please share your thoughts on it. In previous mailing list; I could see two or three times the same question was raised but wasnt replied. I have come too far to go back and select some other gateway - all our applications are currently developed integrated with Kannel.. Pleas... Hammad On Nov 8, 2007 9:08 AM, Khan, Hammad Aslam [EMAIL PROTECTED] wrote: hi All, I am currently using Sierra Aircard 875 (GSM Modem). Sms sending/receiving are working but one problem. - Sometime SMS receive works (by sending a default response) but sometimes itdoesnot. - When i restart kannel, it releases all previously stored SMSs - After restart, sometimes it responds to some already halted sms again and again Any thoughts? what segment should be worked on? Thanking in anticipation. Hammad FlexilogiX Inc. Quoted from: http://www.nabble.com/Un-predictable-SMS-Behavior-tp13641241p13681136.html
SMPP retries set to null for SMSC
Hello, Is there any SMPP parameter that will prevent SMSc from trying to resend SMS (MT's) when there is no ack from handset? Carriers SMSc is playing up and resending SMS assuming that they haven't been delivered, therefore if we can force a parameter maybe we help the SMSc not to resend.
Re: How to override GSM encoding ? (Kannel 1.4.1-2 / Debian)
Olivier PELLEGRINO schrieb:
Output:
2008-02-05 15:42:28 [20444] [14] DEBUG: [debug perso #1]
msg-sms.alt_dcs: -1, smpp-conn-alt_dcs: 0,
pdu-u.submit_sm.data_coding: 0, SMPP_DEFAULT_CHARSET: UTF-8,
smpp-alt_charset: ISO-8859-1
2008-02-05 15:42:28 [20444] [14] DEBUG: [debug perso #2] if condition
2008-02-05 15:42:28 [20444] [14] DEBUG: [debug perso #3]
msg-sms.alt_dcs: -1, smpp-conn-alt_dcs: 0,
pdu-u.submit_sm.data_coding: 241, SMPP_DEFAULT_CHARSET: UTF-8,
smpp-alt_charset: ISO-8859-1
ok, which proves that the submit_sm.data_coding = 241 is set within the if
condition branch, hence via fields_to_dcs(msg, 1);
Please check within gw/sms.c:fields_to_dcs() which if branch set the dcs value
accordingly.
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: Some questions
Dave Jong A Lock schrieb:
1. Can I have multiple smsboxes for one number to have a sort of load
balancing?
depends. It's not clear from the question for which direction (MT/MO) you want
to provision one number. Is it for MO? Generally Kannel uses the concept of
internal load-balancing via connecting N smsboxes to bearerbox and resolving
internal load status via heartbeat messages internally. So generally speaking,
yes, you can connect several smsboxes to bearerbox.
2. If I have different smsboxes can I also have different logs for all
smsboxes and also different logs for the bearerbox?
yes, each smsbox would have it's own config file and hence an own smsbox group
and hence an own log-file defines. Bearerbox has one global log-file but can
also seperate the smsc-id specific entries to own log-files, see user's guide.
3. When I can make multiple connections to the Telecom with more then
one server, should I also need a hardware device between my adsl and my
servers (something like a router with load balancing support)?
grrr, things get complicated when you try to load-balance towards telcos.
Reason here is the architecture side. You are the client towards the SMSCs. A
load-balancing is usually on the server side. So there is no need to
load-balance as client. Things get more complicated when it comes to HA issues.
Most of my questions are based on load balancing, I don't even know if I
generate enough traffic that I need to start load balancing, because I
heard Kannel should be able to handle much more sms/sec, but in real life I
haven't been able to do this yet.
let us know what your expected maximum peak rate sms/sec would be? ;)
load-balancing comes into play when you have something more around 400-500
sms/sec. The bottleneck is usually the SMSC connections, not Kannel capacities,
except you are VERY VERY close to the SMSCs and they push you really hard.
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
SMS Billing VIA SMPP
Hello Guys,
I read a post sometime in 2003 about SMPP Billing somehow it wasn't
conclusive, does anyone know how kannel can Implement Billing via an SMPP
connection to an SMSC?
Else {
Suggestions as to how to implement reverse billing. ;)
}
Regards,
Mike Nwaogu
Tel: 234_802_325_6437
Eml: [EMAIL PROTECTED]
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
Re: SMS Billing VIA SMPP
Mike Nwaogu schrieb:
Hello Guys,
I read a post sometime in 2003 about SMPP Billing somehow it wasn't
conclusive, does anyone know how kannel can Implement Billing via an SMPP
connection to an SMSC?
Else {
Suggestions as to how to implement reverse billing. ;)
}
billing within SMPP v3.4 itself is not a defined concept. Which means the
protocol isn't aware of any logic or semantic about the billing. The protocol
handles in its core only the transport logic. This is why a lot of SMPP
operators use optional TLV fields that are within the vendor-specific range to
implement specific billing/accounting logic.
What we do inside the SMPP client module is:
Use deliver_sm.serivce_type to map to an sms.binfo field that can be used at
application layer.
Same the other way arroun for MT, so sms.binfo is injected to
submit_sm.service_type.
Which does not mean this is enough for billing. It all depends on your SMPP
provider, please get into touch with them and let them define you explicitly how
to handle.
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
Re: configuration issues with Siemens MC35i
Had a lot of problems setting up a plane MC35 for data/PPP sessions on a real commport. Found we needed the following AT commands setting: ATS18 #Extended error reporting. AT+IPR=0#Autobauding on the PC interface AT\Q3 #Hardware flow control AT+CBST=0,0,1 #Autobauding on the Air interface ATD*99***1# #Dial command We had a lot of PPP authentication OK reports, but it would immediatly fall out. The only dial string that worked was the *99***1# all the others fell out. Suspect that the crucial AT cammands are the CBST and the AT\Q3. Hope this helps. Leo +32 495 503814 In a study, scientists report that drinking beer can be good for your liver. I'm sorry, did I say 'scientists'? I meant Irish people. Message: 1 Date: Thu, 07 Feb 2008 13:19:06 +0200 From: Peter Salvage [EMAIL PROTECTED] Subject: To: users@kannel.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hi all I've tried searching the archives and found lots of useful info but I'm not having success. I'm running 1.4.0 on Debian Here's part of my kannel.conf: - This email message was delivered by Psand.net
Re: SMPP retries set to null for SMSC
[EMAIL PROTECTED] schrieb:
Is there any SMPP parameter that will prevent SMSc from trying to
resend SMS (MT's) when there is no ack from handset?
Carriers SMSc is playing up and resending SMS assuming that they
haven't been delivered, therefore if we can force a parameter maybe we
help the SMSc not to resend.
?? the inquiry isn't clear to me.
bearerbox sends submit_sm PDUs towards an SMPP SMSC. If the SMSC fails to ack
the PDU via submit_sm_resp PDU, bearerbox has to assume that the MT is not
accepted/delivered, hence bearerbox will retry.
Is this what you mean?
BTW, there is no way to accept silently a non-acked submit_sm PDU, since the
SMPP spec is strict about confirmations with response PDUs. We can't think
it's ok that we passed PDU to SMSC if we don't get any response. There must be a
reason why we don't get a response PDU, and that reason is either technical
issue on the underlying communication layer or a broken SMPP server.
Stipe
---
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany
tolj.org system architecture Kannel Software Foundation (KSF)
http://www.tolj.org/ http://www.kannel.org/
mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org
---
SMS More Than 500 Chars in 1 MT
Hi List, Im trying to send MT with more than 500 chars, and already add max-messages to 5. But can not work. What else should I set to make it work? Many thanks for your kind replies and helps. Regards, Willy
Re: configuration issues with Siemens MC35i - SOLVED!
Hi all Got it working...my config was fine. The problem was the USB to serial converter; it didn't do HW flow control. The clue was that I couldn't attach to the MC35i using Minicom with HW flow control on, only off. However it appears that Kannel expects HW flow control(?) so I jimmied together a serial cable with pins 1,4 and 6 shorted together, and it worked. Now to play :-) Thanks for all the suggestions and advice, guys! Regards, Peter Leo McManus wrote: Had a lot of problems setting up a plane MC35 for data/PPP sessions on a real commport. Found we needed the following AT commands setting: ATS18 #Extended error reporting. AT+IPR=0#Autobauding on the PC interface AT\Q3 #Hardware flow control AT+CBST=0,0,1 #Autobauding on the Air interface ATD*99***1# #Dial command We had a lot of PPP authentication OK reports, but it would immediatly fall out. The only dial string that worked was the *99***1# all the others fell out. Suspect that the crucial AT cammands are the CBST and the AT\Q3. Hope this helps. Leo +32 495 503814 In a study, scientists report that drinking beer can be good for your liver. I'm sorry, did I say 'scientists'? I meant Irish people. Message: 1 Date: Thu, 07 Feb 2008 13:19:06 +0200 From: Peter Salvage [EMAIL PROTECTED] Subject: To: users@kannel.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hi all I've tried searching the archives and found lots of useful info but I'm not having success. I'm running 1.4.0 on Debian Here's part of my kannel.conf: - This email message was delivered by Psand.net
