Fw: is UCP 52 supported in the EMI connection ?
Hi, Could anybody help me in understanding what exactly the difference is between UCP 01 and UCP 52, and how I would be affected if UCP 52 is the only one accepted by my provider ? Is Kannel supporting it ? Thanks Stephane -- Stephane Rosa IT Security Network Specialist, EMEA Tel: +41 21 966-1238 Cell: +41 79 616-0828 Stryker EMEA Grand Rue 92 CH-1820 Montreux http://www.europe.stryker.com - Forwarded by Stephane Rosa/MTX/Stryker on 18-10-05 11:29 - Stephane Rosa 17-08-05 10:04 To users@kannel.org cc Subject is UCP 52 supported in the EMI connection ? My SMSC is investigating the exclusive use of UCP 52 for MO. Until now they were using UCP 01 for normal text MO with max 160 chars, and UCP 52 for long MO, pictures, etc. Is Kannel supporting UCP 52 at all for MO ? I tried to send a long MO to a test service but it wasnt processed correctly : 2005-08-17 09:52:39 [31782] [4] INFO: Starting to service T from 004179xxx to 30xxx 2005-08-17 09:52:40 [31782] [4] INFO: Starting to service T from 004179xxx to 30xxx It was processed as two separate message and the %k which was ACK in the message was somehow understood as a graphical character by the service. Any advice appreciated. Thanks Stephane
Re: Re:Re: problem in connecting twist modem to kannel
On Tue, Oct 18, 2005 at 12:09:36AM +0200, Chouaieb Ben Smail wrote: Hi Mr Wilfried, yes you are right, i forgot to put the new log :), ok so i set it to debug level may be it would be easier to resolve this problem : and Kannel responds as below: [EMAIL PROTECTED] gw]# ./bearerbox -v 0 smskannel.conf 2005-10-17 22:13:02 [4936] [0] INFO: Debug_lvl = 0, log_file = none, log_lvl = 0 2005-10-17 22:13:02 [4936] [0] DEBUG: Loading include file `modems.conf' (on line 77 of file smskannel.conf). 2005-10-17 22:13:02 [4936] [0] WARNING: DLR: using default 'internal' for storage type. 2005-10-17 22:13:02 [4936] [0] INFO: DLR using storage type: internal 2005-10-17 22:13:02 [4936] [0] DEBUG: Kannel bearerbox version `1.4.0'. Build `Oct 8 2005 12:10:53', compiler `3.4.3 20041212 (Red Hat 3.4.3-9.EL4)'. System Linux, release 2.6.9-5.ELsmp, version #1 SMP Wed Jan 5 19:30:39 EST 2005, machine i686. Hostname x.xxx, IP 127.0.0.1. Libxml version 2.6.16. Using OpenSSL 0.9.7a Feb 19 2003. Using native malloc. 2005-10-17 22:13:02 [4936] [0] INFO: HTTP: Opening server at port 13000. 2005-10-17 22:13:02 [4936] [0] DEBUG: Started thread 1 (gwlib/fdset.c:poller) 2005-10-17 22:13:02 [4936] [0] DEBUG: Started thread 2 (gwlib/http.c:server_thread) 2005-10-17 22:13:02 [4936] [0] DEBUG: Started thread 3 (gw/bb_http.c:httpadmin_run) 2005-10-17 22:13:02 [4936] [0] DEBUG: starting smsbox connection module 2005-10-17 22:13:02 [4936] [0] INFO: BOXC: 'smsbox-max-pending' not set, using default (100). 2005-10-17 22:13:02 [4936] [0] DEBUG: Started thread 4 (gw/bb_boxc.c:sms_to_smsboxes) 2005-10-17 22:13:02 [4936] [1] DEBUG: Thread 1 (gwlib/fdset.c:poller) maps to pid 4936. 2005-10-17 22:13:02 [4936] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) maps to pid 4936. 2005-10-17 22:13:02 [4936] [0] DEBUG: Started thread 5 (gw/bb_boxc.c:smsboxc_run) 2005-10-17 22:13:02 [4936] [0] INFO: DLR rerouting for smsc id (null) disabled. 2005-10-17 22:13:02 [4936] [0] INFO: AT2[/dev/ttyS0]: configuration doesn't show modemtype. will autodetect 2005-10-17 22:13:02 [4936] [0] DEBUG: Started thread 6 (gw/smsc/smsc_at.c:at2_device_thread) 2005-10-17 22:13:02 [4936] [0] DEBUG: Started thread 7 (gw/bb_smscconn.c:sms_router) 2005-10-17 22:13:02 [4936] [0] INFO: 2005-10-17 22:13:02 [4936] [0] INFO: Kannel bearerbox II version 1.4.0 starting 2005-10-17 22:13:02 [4936] [3] DEBUG: Thread 3 (gw/bb_http.c:httpadmin_run) maps to pid 4936. 2005-10-17 22:13:02 [4936] [4] DEBUG: Thread 4 (gw/bb_boxc.c:sms_to_smsboxes) maps to pid 4936. 2005-10-17 22:13:02 [4936] [5] DEBUG: Thread 5 (gw/bb_boxc.c:smsboxc_run) maps to pid 4936. 2005-10-17 22:13:02 [4936] [0] INFO: MAIN: Start-up done, entering mainloop 2005-10-17 22:13:02 [4936] [0] DEBUG: AT2[/dev/ttyS0]: start called 2005-10-17 22:13:02 [4936] [6] DEBUG: Thread 6 (gw/smsc/smsc_at.c:at2_device_thread) maps to pid 4936. 2005-10-17 22:13:02 [4936] [6] DEBUG: AT2[/dev/ttyS0]: detecting modem type 2005-10-17 22:13:02 [4936] [6] INFO: AT2[/dev/ttyS0]: opening device 2005-10-17 22:13:02 [4936] [6] DEBUG: AT2[/dev/ttyS0]: device opened 2005-10-17 22:13:02 [4936] [7] DEBUG: Thread 7 (gw/bb_smscconn.c:sms_router) maps to pid 4936. 2005-10-17 22:13:02 [4936] [7] DEBUG: sms_router: time to sleep 2005-10-17 22:13:02 [4936] [7] DEBUG: sms_router: list_len = 0 2005-10-17 22:13:03 [4936] [6] DEBUG: AT2[/dev/ttyS0]: device opened 2005-10-17 22:13:03 [4936] [6] INFO: AT2[/dev/ttyS0]: speed set to 2400 2005-10-17 22:13:03 [4936] [6] DEBUG: AT2[/dev/ttyS0]: -- ^M 2005-10-17 22:13:05 [4936] [6] DEBUG: AT2[/dev/ttyS0]: -- AT^M 2005-10-17 22:13:09 [4936] [6] DEBUG: AT2[/dev/ttyS0]: -- ATF^M 2005-10-17 22:13:13 [4936] [6] DEBUG: AT2[/dev/ttyS0]: detecting modem strange. it should do ATI or something like that here. type 2005-10-17 22:13:13 [4936] [6] INFO: AT2[/dev/ttyS0]: opening device 2005-10-17 22:13:13 [4936] [6] WARNING: AT2[/dev/ttyS0]: trying to open device with not closed device!!! Please report!!! 2005-10-17 22:13:13 [4936] [6] INFO: AT2[/dev/ttyS0]: closing device 2005-10-17 22:13:13 [4936] [6] DEBUG: AT2[/dev/ttyS0]: device opened 2005-10-17 22:13:14 [4936] [6] DEBUG: AT2[/dev/ttyS0]: device opened 2005-10-17 22:13:14 [4936] [6] INFO: AT2[/dev/ttyS0]: speed set to 2400 2005-10-17 22:13:14 [4936] [6] DEBUG: AT2[/dev/ttyS0]: -- ^M 2005-10-17 22:13:15 [4936] [0] WARNING: Killing signal or HTTP admin command received, shutting down... 2005-10-17 22:13:15 [4936] [0] DEBUG: Shutting down Kannel... 2005-10-17 22:13:15 [4936] [0] DEBUG: shutting down smsc 2005-10-17 22:13:15 [4936] [0] DEBUG: AT2[/dev/ttyS0]: Shutting down SMSCConn,
RE: intermittent problem retrieving sms
I do remember having a MC35 work with Kannel. So it should be possible. Unfortunately, I don't have that model of phone anymore to test with. Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Wilfried Goesgens Sent: maandag 17 oktober 2005 14:16 To: users@kannel.org Subject: Re: intermittent problem retrieving sms On Sun, Oct 16, 2005 at 01:08:33AM +0200, Rene Kluwen wrote: I dont have an answer to the original problem. But does this means that the MC35 breaks ETSI specs? The incoming indication is clearly MT, 15. Which means that the message can be found in MT memory at slot 15. As opposed to all the memories that the phone possibly can have. most modems / phones i've met don't have a proper implementation of the flat memory model (mt) which just puts sm and me after each other. some pretent to, many don't even try. allso the mc35 has some very weirdo behaviour if it gets cr/lf's / ^Z's in the wrong sort of order to the rest of the arguments. Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Wilfried Goesgens Sent: donderdag 13 oktober 2005 19:37 To: users@kannel.org Subject: Re: intermittent problem retrieving sms On Thu, Oct 13, 2005 at 06:15:29PM +0100, Gareth Reakes wrote: Hi all, I have an Seimens MC35 hooked up to a 1.4 kannel installation on redhat. About 1 in 10 times an sms is received it does not come through. The following error in the logs occurs: your mc35 is a verry modern piece of tec. it offers you not just the sim-memory, but allso its own. (SM, ME) so if a message is received, the first available slot is used. if you use the ME memory, your sim-memory doesn't get polled. i've added the functionality to block messages in thte new at driver, called hogs. you can find my version at http://tar.gzipped.org/gateway.tar.bz2 2005-10-13 13:17:03 [29359] [29] DEBUG: Octet string dump ends. 2005-10-13 13:17:24 [29359] [25] DEBUG: boxc_receiver: heartbeat with load value 0 received 2005-10-13 13:17:29 [29359] [6] DEBUG: AT2[orange]: -- +CMTI: MT,15 2005-10-13 13:17:29 [29359] [6] DEBUG: AT2[orange]: +CMTI incoming SMS indication: +CMTI: MT,15 2005-10-13 13:17:31 [29359] [6] DEBUG: AT2[orange]: -- AT+CPMS=MT^M 2005-10-13 13:17:33 [29359] [6] DEBUG: AT2[orange]: -- +CPMS: 16,40,16,40,16,40 2005-10-13 13:17:33 [29359] [6] DEBUG: AT2[orange]: -- OK 2005-10-13 13:17:33 [29359] [6] DEBUG: AT2[orange]: -- AT+CMGR=15^M 2005-10-13 13:17:33 [29359] [6] DEBUG: AT2[orange]: -- +CMGR: 0,,20 2005-10-13 13:17:35 [29359] [6] ERROR: AT2[orange]: got +CMT but waiting for next line timed out 2005-10-13 13:17:37 [29359] [6] DEBUG: AT2[orange]: failed to get message 15. 2005-10-13 13:17:37 [29359] [6] ERROR: AT2[orange]: CMTI notification received, but no message found in memory! 2005-10-13 13:17:37 [29359] [6] ERROR: System error 1: Operation not permitted 2005-10-13 13:17:37 [29359] [6] DEBUG: AT2[orange]: -- AT+CPMS=SM^M 2005-10-13 13:17:53 [29359] [6] DEBUG: AT2[orange]: -- 0791449785788987040C91449726240030500131312175000141 2005-10-13 13:17:53 [29359] [6] DEBUG: AT2[orange]: -- ERROR 2005-10-13 13:17:53 [29359] [6] ERROR: AT2[orange]: Error occurs: ERROR (error number not known to us. ask google and add it.) Can someone explain to me what is going on? Would trying out the new AT driver sort me out? Cheers all, Gareth -- Gareth Reakes, Managing Director Embrace Mobile +44-1865-811197 http://www.embracemobile.com
RE: HTTP APi's Configuration Problem in Kannel
I think Kannel doesn't support Clickatell's http api out of the box. I remember people working on it. Google on the Kannel archives for that. From the userguide: This special SMSC is used for HTTP based connections with other gateways and various other relay services, when direct SMSC is not available. This module can be easily adopted to other HTTP-based interfaces. Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Kamlesh Kumar Sent: dinsdag 18 oktober 2005 7:01 To: users@kannel.org Subject: HTTP APi's Configuration Problem in Kannel Hi I am trying to configure clickatell's http api in Kannel. Though, i have configured that but i am not getting sms. When i get the status i get following comments which show that sms was failed. Here is the status. -- Status: running, uptime 0d 0h 2m 12s WDP: received 0 (0 queued), sent 0 (0 queued) SMS: received 0 (0 queued), sent 0 (0 queued), store size -1 SMS: inbound 0.00 msg/sec, outbound 0.00 msg/sec DLR: 0 queued, using internal storage Box connections: smsbox:(none), IP 127.0.0.1 (0 queued), (on-line 0d 0h 1m 26s) SMSC connections: clickatellHTTP:kannel (online 132s, rcvd 0, sent 0, failed 1, queued 0 msgs) Here is the kennel's configuration group = core admin-port = 13000 admin-password = bar status-password = foo smsbox-port = 3001 admin-allow-ip = 192.168.2.45;127.0.0.1;200.100.0.* log-file = /tmp/kannel.log log-level = 0 access-log = /tmp/kannel-access.log # SMSBOX SETUP group = smsbox bearerbox-host = localhost sendsms-port = 3003 sendsms-chars = 0123456789 +- global-sender = Kamlesh log-file = /tmp/smsbox.log log-level = 0 access-log = /tmp/smsbox-access.log # SMSC HTTP group = smsc smsc = http smsc-id = clickatell system-type = kannel smsc-username = testme smsc-password = testme connect-allow-ip = 192.168.2.45;127.0.0.1;200.100.0.* port = 13015 send-url = http://api.clickatell.com/http/sendmsg?api_id=1234user=testmepassword=tes tme # SEND-SMS USERS group = sendsms-user username = testme password = testme # SMS SERVICE 'Default' # there should be default always group = sms-service keyword = default text = No Thanks --- Here is the log for the transaction. --- 2005-10-18 09:39:11 [2197] [14] DEBUG: Octet string dump ends. 2005-10-18 09:39:11 [2197] [14] DEBUG: HTTP: Status line: HTTP/1.1 200 OK 2005-10-18 09:39:11 [2197] [14] DEBUG: HTTP: Received response: 2005-10-18 09:39:11 [2197] [14] DEBUG: Octet string at 0x81d1f78: 2005-10-18 09:39:11 [2197] [14] DEBUG: len: 223 2005-10-18 09:39:11 [2197] [14] DEBUG: size: 1024 2005-10-18 09:39:11 [2197] [14] DEBUG: immutable: 0 2005-10-18 09:39:11 [2197] [14] DEBUG: data: 44 61 74 65 3a 20 54 75 65 2c 20 31 38 20 4f 63 Date: Tue, 18 Oc 2005-10-18 09:39:11 [2197] [14] DEBUG: data: 74 20 32 30 30 35 20 30 34 3a 33 39 3a 30 37 20 t 2005 04:39:07 2005-10-18 09:39:11 [2197] [14] DEBUG: data: 47 4d 54 0d 0a 53 65 72 76 65 72 3a 20 41 70 61 GMT..Server: Apa 2005-10-18 09:39:11 [2197] [14] DEBUG: data: 63 68 65 2f 31 2e 33 2e 33 33 20 28 55 6e 69 78 che/1.3.33 (Unix 2005-10-18 09:39:11 [2197] [14] DEBUG: data: 29 20 50 48 50 2f 34 2e 34 2e 30 20 6d 6f 64 5f ) PHP/4.4.0 mod_ 2005-10-18 09:39:11 [2197] [14] DEBUG: data: 73 73 6c 2f 32 2e 38 2e 32 33 20 4f 70 65 6e 53 ssl/2.8.23 OpenS 2005-10-18 09:39:11 [2197] [14] DEBUG: data: 53 4c 2f 30 2e 39 2e 37 61 0d 0a 58 2d 50 6f 77 SL/0.9.7a..X-Pow 2005-10-18 09:39:11 [2197] [14] DEBUG: data: 65 72 65 64 2d 42 79 3a 20 50 48 50 2f 34 2e 34 ered-By: PHP/4.4 2005-10-18 09:39:11 [2197] [14] DEBUG: data: 2e 30 0d 0a 54 72 61 6e 73 66 65 72 2d 45 6e 63 .0..Transfer-Enc 2005-10-18 09:39:11 [2197] [14] DEBUG: data: 6f 64 69 6e 67 3a 20 63 68 75 6e 6b 65 64 0d 0a oding: chunked.. 2005-10-18 09:39:11 [2197] [14] DEBUG: data: 43 6f 6e 74 65 6e 74 2d 54 79 70 65 3a 20 74 65 Content-Type: te 2005-10-18 09:39:11 [2197] [14] DEBUG: data: 78 74 2f 68 74 6d 6c 0d 0a 0d 0a 49 44 3a 20 32 xt/htmlID: 2 2005-10-18 09:39:11 [2197] [14] DEBUG: data: 63 62 34 34 63 31 31 36 30 66 30 64 65 33 63 33 cb44c1160f0de3c3 2005-10-18 09:39:11 [2197] [14] DEBUG: data: 62 35 35 65 30 65 36 32 32 66 61 30 62 38 34 b55e0e622fa0b84 2005-10-18 09:39:11 [2197] [14] DEBUG: Octet string dump ends. 2005-10-18 09:39:19 [2197] [2] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'. 2005-10-18 09:39:19 [2197] [3] DEBUG: HTTP: Destroying HTTPClient area 0x81d1110. 2005-10-18 09:39:19 [2197] [3] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'. 2005-10-18 09:39:24 [2197] [2] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'. 2005-10-18 09:39:24 [2197] [3] DEBUG: HTTP: Destroying HTTPClient area
Problems with motorola v710
I'm a new member of the list, so I'm unable to reply to this message I found in the archives. I did some trouble-shooting on the network connections and think I located the problem. I suspect that this phone doesn't actually support WAP and instead pushes everything through HTTP regardless of setting. I set my traffic to go through a privoxy proxy and everything seemed to work ok with my own simple html pages (xhtml 1.1 strict, but nothing fancy). Web Sessions Menu (each entry has these properties) Homepage: http://homepage (fixed without hex-editing) User ID: Password: Gateway IP: (ipv4 gateway ip) Gateway 1: (appears to be a DNS name entry, but the resolver fails) Service Type: (options are WAP or HTTP) Port 1: (Regardless of Service type, opening the browser tries to connect to this port with TCP, not UDP - VZW port 8080 default) EXE Port 1: (no clue what this is for - VZW port 8080 default) LXL Port 1: (VZW default 443, assuming something to do with https) Original Message Below: # I'm having trouble getting my Motorola v710 (Verizon) phone to access the Internet through a kannel WAP gateway I've set up on my server. It works fine when I just use an HTTP gateway with squid as the proxy. I don't know if the problem is my phone or the kannel setup, since I have no other phone to test it with. I'm using the Debian packages, version 1.2.1-5, on a Debian sid system. bearerbox and wapbox seem to start up okay. I can even see my phone attempting to connect: 2004-09-14 16:45:05 [13] INFO: Client connected from 166.156.206.207 2004-09-14 16:45:05 [13] DEBUG: setting up systems for new wapbox 2004-09-14 16:45:05 [13] DEBUG: Started thread 14 (gw/bb_boxc.c:boxc_sender) 2004-09-14 16:45:30 [13] INFO: Connection closed by the box 166.156.206.207 2004-09-14 16:45:30 [14] DEBUG: Thread 14 (gw/bb_boxc.c:boxc_sender) terminates. 2004-09-14 16:45:30 [13] DEBUG: Thread 13 (gw/bb_boxc.c:function) terminates. Where 166.156.206.207 is definitely my phone. But it terminates after about 30 seconds, and the phone says connection lost. There is no activity in wapbox.log during this time period; however. I am using a very basic config, basically right out of the box: group = core admin-port = 13000 admin-password = [...xxx...] admin-deny-ip = *.*.*.* admin-allow-ip = 127.0.0.1 wapbox-port = 13002 wdp-interface-name = * log-file = /var/log/kannel/bearerbox.log box-deny-ip = box-allow-ip = *.*.*.* group = wapbox bearerbox-host = localhost log-file = /var/log/kannel/wapbox.log Can anyone suggest what I'm doing wrong or how to further troubleshoot this issue? -- Adam Rosi-Kessel http://adam.rosi-kessel.org
