Re: GSM 03.38 packed data in SMPP messages
25 2003, 06:30,Rafael 'Dido'
Sevilla:
I finally realized that the SMPP message center we've been using
actually receives and sends text that is packed according to section
6.1.2 of GSM 03.38. I had to write a patch to Kannel in order to make
it unpack the data received and pack the data being sent.
There are already functions in the AT driver that handle this - check out
at2_encode7bituncompressed() and at2_decode7bituncompressed(). maybe these
should be moved to the sms.{h,c} files.
Are such
SMSC's that send text data packed as per GSM 03.38 common?
you have to do this for GSM modems as they speak directly on the wire. all
SMPP SMSCs I've talked with do this for you so you don't need to worry about
it.
Or maybe unpatched Kannel has an option to do this unpacking that I'm
unaware of? :/
See AT driver.
--
Oded Arbel
m-Wise mobile solutions
[EMAIL PROTECTED]
+972-9-9581711 (116)
+972-67-340014
::..
The makers may make
and the users may use,
but the fixers must fix
with but minimal clues
Re: GSM 03.38 packed data in SMPP messages
On Thu, Dec 25, 2003 at 01:42:42PM +0200, Oded Arbel wrote: Are such SMSC's that send text data packed as per GSM 03.38 common? you have to do this for GSM modems as they speak directly on the wire. all SMPP SMSCs I've talked with do this for you so you don't need to worry about it. The SMPP SMSC made by ZTE (http://www.zte.com.cn) apparently sends and expects to receive GSM SMS text packed in that way, oddly enough. Does SMPP 3.3/3.4 say that it should be received unpacked or packed? Don't have the specs on hand...
Re: GSM 03.38 packed data in SMPP messages
25 2003, 14:05,Rafael 'Dido' Sevilla: On Thu, Dec 25, 2003 at 01:42:42PM +0200, Oded Arbel wrote: Are such SMSC's that send text data packed as per GSM 03.38 common? you have to do this for GSM modems as they speak directly on the wire. all SMPP SMSCs I've talked with do this for you so you don't need to worry about it. The SMPP SMSC made by ZTE (http://www.zte.com.cn) apparently sends and expects to receive GSM SMS text packed in that way, oddly enough. Does SMPP 3.3/3.4 say that it should be received unpacked or packed? Don't have the specs on hand... The SMPP spec only defines that the character set to be used is GSM 7 bit alphabet according to GSM 03.38. GSM 03.38 defines this on page 7: quote GSM 7 bit default alphabet indicates that the TP-UD is coded from the GSM 7 bit default alphabet given in clause 6.1.2. when this character set is used, the character of the message are packed in octets as shown in clause 6.1.2.1.1, and the message can consist of upto 160 characters. /quote This says to me that 7bit text should always be packed by the originating entity, but apparently this is not the case. -- Oded Arbel m-Wise mobile solutions [EMAIL PROTECTED] +972-9-9581711 (116) +972-67-340014 ::.. /real/ kernel hackers do dd if=/dev/urandom of=/vmlinuz and influence the Universal Randomosity Field. -- Gaal Yahas
Re: Missing files to compile on Cygwin
Jarrod Hermer wrote: Hi, I cannot seem to compile Kannel 1.3.1 or latest CVS due to some files missing. Could someone pls take a look at the ./configure output. My dev knowledge is quite limited. I don't see anything missing. configure did complete it's configuiration step and pre-building of config files. Kannel builds definetly out-of-the-box on a correctly installed vannila Cygwin installation. Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf, NRW, Germany phone: +49.211.74845.0 fax: +49.211.74845.299 mailto:[EMAIL PROTECTED] http://www.wapme-systems.de/ --- -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.2.2 (Cygwin) mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2 nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H g2HyLAEKQIp30Q== =aYCI -END PGP PUBLIC KEY BLOCK-
connection failed with SMSC
Hi all Iam using CMG-MMT SMSC tester to connect to our kannel SMS gateway. The problem is my receive socket() is not getting connected. My send socket from the kannel() gets succesfully connected. The kannel bearer box debug show the following 2003-12-26 02:55:52 [0] INFO: Debug_lvl = 1, log_file = none, log_lvl = 0 2003-12-26 02:55:53 [0] WARNING: DLR: using default 'internal' for storage type. 2003-12-26 02:55:53 [0] INFO: SSL not supported, no SSL initialization done. 2003-12-26 02:55:53 [0] INFO: 2003-12-26 02:55:53 [0] INFO: Kannel bearerbox II version 1.2.1 starting 2003-12-26 02:55:53 [7] ERROR: connect failed 2003-12-26 02:55:53 [7] ERROR: System error 111: Connection refused 2003-12-26 02:55:53 [7] ERROR: error connecting to server `192.168.2.42' at port `' 2003-12-26 02:55:53 [7] ERROR: SMPP[SMPP:192.168.2.42:/:STT:VMA]: Couldn't connect to server. 2003-12-26 02:55:53 [7] ERROR: SMPP[SMPP:192.168.2.42:/:STT:VMA]: Couldn't connect to SMS center (retrying in 10 seconds). 2003-12-26 02:55:53 [0] INFO: MAIN: Start-up done, entering mainloop 2003-12-26 02:56:03 [7] ERROR: connect failed 2003-12-26 02:56:03 [7] ERROR: System error 111: Connection refused 2003-12-26 02:56:03 [7] ERROR: error connecting to server `192.168.2.42' at port `' 2003-12-26 02:56:03 [7] ERROR: SMPP[SMPP:192.168.2.42:/:STT:VMA]: Couldn't connect to server. 2003-12-26 02:56:03 [7] ERROR: SMPP[SMPP:192.168.2.42:/:STT:VMA]: Couldn't connect to SMS center (retrying in 10 seconds). 2003-12-26 02:56:04 [0] WARNING: Killing signal received, shutting down... 2003-12-26 02:55:52 [0] INFO: Debug_lvl = 1, log_file = none, log_lvl = 0 2003-12-26 02:55:53 [0] WARNING: DLR: using default 'internal' for storage type. 2003-12-26 02:55:53 [0] INFO: SSL not supported, no SSL initialization done. 2003-12-26 02:55:53 [0] INFO: 2003-12-26 02:55:53 [0] INFO: Kannel bearerbox II version 1.2.1 starting 2003-12-26 02:55:53 [7] ERROR: connect failed 2003-12-26 02:55:53 [7] ERROR: System error 111: Connection refused 2003-12-26 02:55:53 [7] ERROR: error connecting to server `192.168.2.42' at port `' 2003-12-26 02:55:53 [7] ERROR: SMPP[SMPP:192.168.2.42:/:STT:VMA]: Couldn't connect to server. 2003-12-26 02:55:53 [7] ERROR: SMPP[SMPP:192.168.2.42:/:STT:VMA]: Couldn't connect to SMS center (retrying in 10 seconds). 2003-12-26 02:55:53 [0] INFO: MAIN: Start-up done, entering mainloop 2003-12-26 02:56:03 [7] ERROR: connect failed 2003-12-26 02:56:03 [7] ERROR: System error 111: Connection refused 2003-12-26 02:56:03 [7] ERROR: error connecting to server `192.168.2.42' at port `' 2003-12-26 02:56:03 [7] ERROR: SMPP[SMPP:192.168.2.42:/:STT:VMA]: Couldn't connect to server. 2003-12-26 02:56:03 [7] ERROR: SMPP[SMPP:192.168.2.42:/:STT:VMA]: Couldn't connect to SMS center (retrying in 10 seconds). - My smskannel.conf file has the following config - group = core admin-port = 13000 smsbox-port = 13001 admin-password = bar box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 unified-prefix = 00358,0 # SMSC CONNECTIONS group = smsc smsc = fake port = 1 connect-allow-ip = 127.0.0.1 group = smsc smsc = smpp host = 192.168.2.42 port = receive-port = smsc-username = STT smsc-password = foo system-type = VMA #address-range = ..and so on... I have configured the following ports in CMG-MMT SMSCtester Remote ip address = 192.168.2.41 Remote connect port = Local connect port = 0 Local listern port = --- the ethereal dump tells that iam getting a RST for the SYN which kannel is sending... I appologize for the long post... I would be thankful if anyone could throw light on this issue... - Thanx Regards ./zahoor
