Any body use the Kannel as a wap box?
I Try to use the Kannel as a wap box. And have a problem: If I use a MS emulator - kannel work OK, But if I use a real MS - kannel doesn't work. This is part wapbox.log -- 2005-08-31 13:22:16 [10229] [1] DEBUG: WSP: machine 0xa1855e8, state CONNECTING, event S-Connect.res 2005-08-31 13:22:16 [10229] [1] DEBUG: WSP: Mapping `Encoding-Version', WSP 1.2 to 0x. 2005-08-31 13:22:16 [10229] [5] DEBUG: WTP: resp_machine 0, state RESULT_WAIT, event TR-Result.req. 2005-08-31 13:22:16 [10229] [5] DEBUG: WTP: begin_sar_result(): data len = 38 2005-08-31 13:22:16 [10229] [5] DEBUG: WTP: dispath_to_wdp(): psn = 0 2005-08-31 13:22:16 [10229] [5] DEBUG: WTP 0: New state RESULT_RESP_WAIT 2005-08-31 13:22:16 [10229] [1] DEBUG: WSP 0: New state CONNECTING_2 2005-08-31 13:22:23 [10229] [4] DEBUG: Timeout-R elapsed. 2005-08-31 13:22:23 [10229] [5] DEBUG: WTP: resp_machine 0, state RESULT_RESP_WAIT, event Timeout-R. 2005-08-31 13:22:23 [10229] [5] DEBUG: WTP 0: New state RESULT_RESP_WAIT 2005-08-31 13:22:30 [10229] [4] DEBUG: Timeout-R elapsed. 2005-08-31 13:22:30 [10229] [5] DEBUG: WTP: resp_machine 0, state RESULT_RESP_WAIT, event Timeout-R. 2005-08-31 13:22:30 [10229] [5] DEBUG: WTP 0: New state RESULT_RESP_WAIT 2005-08-31 13:22:31 [10229] [5] DEBUG: WTP: resp_machine 0, state RESULT_RESP_WAIT, event RcvInvoke. 2005-08-31 13:22:31 [10229] [5] DEBUG: WTP 0: New state RESULT_RESP_WAIT 2005-08-31 13:22:37 [10229] [4] DEBUG: Timeout-R elapsed. 2005-08-31 13:22:37 [10229] [5] DEBUG: WTP: resp_machine 0, state RESULT_RESP_WAIT, event Timeout-R. 2005-08-31 13:22:37 [10229] [5] DEBUG: WTP 0: New state RESULT_RESP_WAIT 2005-08-31 13:22:44 [10229] [4] DEBUG: Timeout-R elapsed. 2005-08-31 13:22:44 [10229] [5] DEBUG: WTP: resp_machine 0, state RESULT_RESP_WAIT, event Timeout-R. 2005-08-31 13:22:44 [10229] [5] DEBUG: WTP 0: New state RESULT_RESP_WAIT
[REPOST] DLR on wappushes ?
Hello I'm reposting this question because I have still no clue. 1) In the past I used binary SMS messages to send WAP-PUSHES in that way I was able to set dlr-mask=31 and a dlr-url and I have been receiving DLRs easily when the phone received the SMS. Sometimes the phone did not understand the wap-push message as a binary-message but the DLR arrived in any case. The 'call' was something like GET /sendsms? and I was using the bearerbox and the smsbox to send those binary sms. 2) Now I use the bearerbox, smsbox and wapbox and I send XML files to the wapbox using a POST but when I set the dlr-url and dlr-mark variables in the POST, I receive no DLRs at all. Does anyone know if the transcodification from XML to BINARY made by the wapbox do include dlr ? Thanks PS: I'm not interested to be notified if the wappush is understood or not, I just want to know if the wappush sms is got by the phone.
kannel.store keeps filling up
Hello, we have put kannel in production and it is serving 10 EMI/UCP connections and a couple of smpp connections. Sometimes however we see that sms's just stay behind in the kannel.store file without any further ado. Both MT push and MO sms are sometimes left behind in the kannel. When i restart the smpp/ucp link concerned (via the webinterface) the sms mostly gets discarded but sometimes it does not and i have to restart the whole of kannel. As this happens quite often it is not very workable... we are using Kannel bearerbox version `cvs-20050528'. doies anyone have any suggestions or similar experiences with kannel ? Thnx
Problems with the installation
Thanks Lars, but this didn't fixed my problem. there is still this error message, i had discribed before. Is there anybody who can help me?? Please - It's very important. Arne Kröger
Re: [REPOST] DLR on wappushes ?
Mike Nwaogu wrote: Hello Julien, The position on your dlr-mask in the post command is what I think the issue is. Maybe you are true, but if I do POST /wappush HTTP/1.1 Host: 10.100.10.5:8080 Connection: close Content-Type: multipart/related; boundary=123321; type=application/xml Content-Length: 1174 username=ppgusernamepassword=ppgpassworddlr-mask=31dlr-url=[encoded url] XML ATTACHMENT CUT then the ppg says: HTTP/1.1 401 Unauthorized Server: Kannel/1.4.0 Content-Length: 32 Connection: close WWW-Authenticate: Basic realm=berlinzoowappush You must show your credentials. if I do: POST /wappush?username=ppgusernamepassword=ppgpassword HTTP/1.1 Host: 10.100.10.5:8080 Connection: close Content-Type: multipart/related; boundary=123321; type=application/xml Content-Length: 1174 username=ppgusernamepassword=ppgpassworddlr-mask=31dlr-url=[encoded url] (same as before but with user/pass in the POST url) the I get: HTTP/1.1 202 Accepted Perhaps you should URL ENCODE the content or relocate the dlr-mask parameter before the actual message. I could be wrong though but I think that's what it is. It is encoded,the protocol implementation seems ok to me, I think is something different related to the box receiving and decoding the paramenters. Cheers Julien --- Julien Buratto [EMAIL PROTECTED] wrote: Hello I'm reposting this question because I have still no clue. 1) In the past I used binary SMS messages to send WAP-PUSHES in that way I was able to set dlr-mask=31 and a dlr-url and I have been receiving DLRs easily when the phone received the SMS. Sometimes the phone did not understand the wap-push message as a binary-message but the DLR arrived in any case. The 'call' was something like GET /sendsms? and I was using the bearerbox and the smsbox to send those binary sms. 2) Now I use the bearerbox, smsbox and wapbox and I send XML files to the wapbox using a POST but when I set the dlr-url and dlr-mark variables in the POST, I receive no DLRs at all. Does anyone know if the transcodification from XML to BINARY made by the wapbox do include dlr ? Thanks PS: I'm not interested to be notified if the wappush is understood or not, I just want to know if the wappush sms is got by the phone. Mike Nwaogu Metro Technologies Resources Ltd. 48 Tunde Idiagbon Road, Tanke, Ilorin. __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com
Re: sms send problem
Hi John, Let me suggest you the reading of the following document, specially, chapter 4. http://www.kannel.org/download/1.3.2/arch-1.3.2/arch.html You can´t send SMS to internet and expect they will arrive to your phone. The only ways are: through a direct connection to an operator´s SMSC or using a GSM modem (v.g. GSM phone) connected to the serial port of your Kannel machine. FAKE SMSC is only for test purposes, not for sending nor receiving any messages. Rodrigo. On 9/12/05, john decot [EMAIL PROTECTED] wrote: Here are the logs which i get ./smsbox -v 1 smskannel.conf 2005-09-11 16:13:18 [3481] [0] INFO: Debug_lvl = 1, log_file = none, log_lvl = 0 2005-09-11 16:13:18 [3481] [0] INFO: Service global sender set as '13013' 2005-09-11 16:13:18 [3481] [0] INFO: HTTP: Opening server at port 13013. 2005-09-11 16:13:18 [3481] [0] INFO: Set up send sms service at port 13013 2005-09-11 16:13:18 [3481] [0] INFO: Connected to bearerbox at localhost port 13001. 2005-09-11 16:13:27 [3481] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms from 127.0.0.1 2005-09-11 16:13:28 [3481] [3] INFO: smsbox: Got HTTP request /favicon.ico from 127.0.0.1 2005-09-11 16:13:54 [3481] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms from 127.0.0.1 2005-09-11 16:13:54 [3481] [3] INFO: sendsms used by tester 2005-09-11 16:13:54 [3481] [3] INFO: sendsms sender:tester:13013 (127.0.0.1) to:xxxyy msg:hello 2005-09-11 16:13:56 [3481] [3] INFO: smsbox: Got HTTP request /favicon.ico from 127.0.0.1 ./bearerbox -v 1 smskannel.conf 2005-09-11 16:13:15 [3472] [0] INFO: Debug_lvl = 1, log_file = none, log_lvl = 0 2005-09-11 16:13:15 [3472] [0] WARNING: DLR: using default 'internal' for storage type. 2005-09-11 16:13:15 [3472] [0] INFO: DLR using storage type: internal 2005-09-11 16:13:15 [3472] [0] INFO: HTTP: Opening server at port 13000. 2005-09-11 16:13:15 [3472] [0] INFO: BOXC: 'smsbox-max-pending' not set, using default (100). 2005-09-11 16:13:15 [3472] [0] INFO: DLR rerouting for smsc id (null) disabled. 2005-09-11 16:13:15 [3472] [0] INFO: HTTP: Opening server at port 10011. 2005-09-11 16:13:15 [3472] [0] INFO: HTTP[(null)]: Initiated and ready 2005-09-11 16:13:15 [3472] [0] INFO: 2005-09-11 16:13:15 [3472] [0] INFO: Kannel bearerbox II version 1.4.0 starting 2005-09-11 16:13:15 [3472] [0] INFO: MAIN: Start-up done, entering mainloop 2005-09-11 16:13:18 [3472] [9] INFO: Client connected from 127.0.0.1 2005-09-11 16:13:57 [3472] [12] ERROR: Error while gw_gethostbyname occurs. 2005-09-11 16:13:57 [3472] [12] ERROR: System error 1: Operation not permitted 2005-09-11 16:13:57 [3472] [12] ERROR: gethostbyname failed 2005-09-11 16:13:57 [3472] [12] ERROR: error connecting to server `localhost:13013' at port `13013' 2005-09-11 16:13:57 [3472] [12] ERROR: Couldn't send request to http://localhost:13013?username=testerpassword=foobarto=xxxyytext=hellofrom=13013coding=0dlr-url= 2005-09-11 16:13:57 [3472] [7] ERROR: HTTP[(null)]: Couldn't connect to SMS center (retrying in 10 seconds). smskannel.conf looks follows # # THIS IS A SAMPLE CONFIGURATION FOR SMS KANNEL # # It is run like this: # # 1% gw/bearerbox gw/smskannel.conf # 2% gw/smsbox gw/smskannel.conf # 3% test/fakesmsc -p 1 -H localhost -i 1 -m 100 123 345 text nop # # ..all 3 commands in separate shells (or screen sessions) # # For any modifications to this file, see Kannel User Guide # If that does not help, send email to users@kannel.org # # Kalle Marjola May 2000 # Changed for new fakesmsc version by Uoti Urpala Jan 2001 # Added service and sendsms for HTTP SMSC by Kalle Marjola Mar 2001 # group = core admin-port = 13000 smsbox-port = 13001 admin-password = bar #status-password = foo #admin-deny-ip = admin-allow-ip = #log-file = /tmp/kannel.log #log-level = 0 box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 #unified-prefix = +358,00358,0;+,00 #access-log = /tmp/access.log #store-file = /tmp/kannel.store #ssl-server-cert-file = cert.pem #ssl-server-key-file = key.pem #ssl-certkey-file = mycertandprivkeyfile.pem # SMSC CONNECTIONS group = smsc smsc = http system-type= kannel port = 10011 connect-allow-ip = 127.0.0.1 smsc-username= tester smsc-password= foobar send-url = http://localhost:13013; # SMSBOX SETUP group = smsbox bearerbox-host = localhost sendsms-port = 13013 global-sender = 13013 sendsms-chars = 0123456789 +- #log-file = /tmp/smsbox.log #log-level = 0 #access-log = /tmp/access.log # SEND-SMS USERS group = sendsms-user username = tester password = foobar #user-deny-ip = #user-allow-ip = # SERVICES group = sms-service keyword = nop text = You asked nothing and I did it! # there should be default always group = sms-service keyword = default text = No service specified Rene Kluwen [EMAIL PROTECTED] wrote: Did you set up an smsc connection under group =
kannel sms and wap push
I'm trying to impelment a mobile content distribution server using Kannel. The developers prior to me got smsbox working and now I'm trying to setup wapbox and ppg. Are wapbox and ppg both necessary for mobile content (i.e. ringtones, wallpapers and other binary file) distribution? Also, when I try to use a web query (through smsc = http) I get the following error in the smsbox.log 2005-09-12 15:56:55 [10020] [4] INFO: Starting to service test from 0018081234567 to 0018081234567 2005-09-12 15:56:55 [10020] [5] INFO: No reply sent, denied. If anyone could shed some light on this I'd be very appreciative. I was thrown into this and haven't had (and don't have) much time to tinker with kannel as we are on a big time crunch. Here's my kannel.conf group = core admin-port = 13000 admin-password = password status-password = password admin-deny-ip = *.*.*.* admin-allow-ip = 127.0.0.1 smsbox-port = 13001 wapbox-port = 13002 #box-deny-ip = *.*.*.* box-allow-ip = *.*.*.* udp-allow-ip = *.*.*.* wdp-interface-name=* log-file = /tmp/kannel.log log-level = 1 access-log = /tmp/kannel.access unified-prefix = +358,00358,0;+,00 white-list = sms_send group = smsc smsc = at smsc-id = wave293 #keepalive=5 #sim-buffering=true max-error-count=2 modemtype = wavecom device = /dev/ttyS0 group = smsc smsc = at smsc-id = sierra #allowed-smsc-id = modemtype = sierra_750 device = /dev/modem #speed = 9600 #keepalive = 60 sim-buffering = true #max-error-count = 5 # SMSBOX SETUP group = smsbox bearerbox-host = localhost sendsms-port = 13013 log-file = /tmp/smsbox.log log-level = 1 access-log = /tmp/smsaccess.log # SMS SERVICE Default # there should be default always group = sms-service keyword = default get-url = http://mydomain.org/z_send/sms.php?from=%pbody=%a; max-messages=0 #text = No service specified assume-plain-text = true group = sendsms-user username = sms_send password = password max-messages = 5 include = /etc/kannel/modems.conf # WAPBOX SETUP group = wapbox bearerbox-host = localhost log-file = /tmp/wapbox.log log-level = 1 syslog-level = none access-log = /tmp/wapaccess.log # PPG SETUP group = ppg ppg-url = /wapppush ppg-port = 8080 concurrent-pushes = 50 users = 52 ppg-allow-ip = *.*.*.* trusted-pi = false group = wap-push-user wap-push-user = pi_user ppg-username = wap_pusher ppg-password = password group = smsc smsc = http smsc-id = HTTP port = 1 system-type = kannel smsc-username = sms_send smsc-password = password no-sender = true no-coding = true send-url = http://mydomain.org/wapstuff Thanks, John
Re: kannel sms and wap push
Hi, For me it's easier to send WAP PUSH using this method: $title = title; $url = the_url; $text = %01; // transid $text .= %06; // PDU Type (push) //$text .= %04%03; // length of content-type $text .= %01; $text .= %AE%81%EA; // content-type: application/vnd.wap.sic $text .= %02; // wbxml_version $text .= %05; // si_public_id $text .= %6A; // charset= (sibxml-charset) $text .= %00; // string table length $text .= %45; // si $text .= %C6; // indication.. $text .= %0C%03.rawurlencode($url).%00; // href=url $text .= %01; // end indication $text .= %03.rawurlencode(trim($title)).%00; $text .= %01; // /indication $text .= %01; // /si And push it with http://url/cgi-bin/sendsms?...udh=%06%05%04%0B%84%23%F0text=$text; FYI I use PHP. Hope it can help you :) Regards Willy - Original Message - From: John M L [EMAIL PROTECTED] To: users@kannel.org Sent: Tuesday, September 13, 2005 3:11 AM Subject: kannel sms and wap push I'm trying to impelment a mobile content distribution server using Kannel. The developers prior to me got smsbox working and now I'm trying to setup wapbox and ppg. Are wapbox and ppg both necessary for mobile content (i.e. ringtones, wallpapers and other binary file) distribution? Also, when I try to use a web query (through smsc = http) I get the following error in the smsbox.log 2005-09-12 15:56:55 [10020] [4] INFO: Starting to service test from 0018081234567 to 0018081234567 2005-09-12 15:56:55 [10020] [5] INFO: No reply sent, denied. If anyone could shed some light on this I'd be very appreciative. I was thrown into this and haven't had (and don't have) much time to tinker with kannel as we are on a big time crunch. Here's my kannel.conf group = core admin-port = 13000 admin-password = password status-password = password admin-deny-ip = *.*.*.* admin-allow-ip = 127.0.0.1 smsbox-port = 13001 wapbox-port = 13002 #box-deny-ip = *.*.*.* box-allow-ip = *.*.*.* udp-allow-ip = *.*.*.* wdp-interface-name=* log-file = /tmp/kannel.log log-level = 1 access-log = /tmp/kannel.access unified-prefix = +358,00358,0;+,00 white-list = sms_send group = smsc smsc = at smsc-id = wave293 #keepalive=5 #sim-buffering=true max-error-count=2 modemtype = wavecom device = /dev/ttyS0 group = smsc smsc = at smsc-id = sierra #allowed-smsc-id = modemtype = sierra_750 device = /dev/modem #speed = 9600 #keepalive = 60 sim-buffering = true #max-error-count = 5 # SMSBOX SETUP group = smsbox bearerbox-host = localhost sendsms-port = 13013 log-file = /tmp/smsbox.log log-level = 1 access-log = /tmp/smsaccess.log # SMS SERVICE Default # there should be default always group = sms-service keyword = default get-url = http://mydomain.org/z_send/sms.php?from=%pbody=%a; max-messages=0 #text = No service specified assume-plain-text = true group = sendsms-user username = sms_send password = password max-messages = 5 include = /etc/kannel/modems.conf # WAPBOX SETUP group = wapbox bearerbox-host = localhost log-file = /tmp/wapbox.log log-level = 1 syslog-level = none access-log = /tmp/wapaccess.log # PPG SETUP group = ppg ppg-url = /wapppush ppg-port = 8080 concurrent-pushes = 50 users = 52 ppg-allow-ip = *.*.*.* trusted-pi = false group = wap-push-user wap-push-user = pi_user ppg-username = wap_pusher ppg-password = password group = smsc smsc = http smsc-id = HTTP port = 1 system-type = kannel smsc-username = sms_send smsc-password = password no-sender = true no-coding = true send-url = http://mydomain.org/wapstuff Thanks, John
wapbox service not found
When I check my wapbox log I notice that it never pulls anything from the wap server. ERROR: Request /wappush from 127.0.0.1: service not found Can someone explain how you link the wap gateway to pull from you apache server? Or is this even necessary. I'm a bit confused since apache can serve wml pages to the openwave browser anyway. What is the point to using wapbox? - John
service not found message
Can anyone tell me why the test_ppg app produces an error “push failed, service not found”? I must be missing something in both the wap and ppg conf in kannel. Here's the test_ppg output: [EMAIL PROTECTED] test]# ./test_ppg tppg 2005-09-12 22:36:02 [11628] [0] INFO: a configuration file input assumed 2005-09-12 22:36:02 [11628] [0] DEBUG: Dumping Cfg 0x9362198 2005-09-12 22:36:02 [11628] [0] DEBUG: filename = tppg 2005-09-12 22:36:02 [11628] [0] DEBUG: dumping group (test-ppg): 2005-09-12 22:36:02 [11628] [0] DEBUG: group = test-ppg 2005-09-12 22:36:02 [11628] [0] DEBUG: dumping group (configuration): 2005-09-12 22:36:02 [11628] [0] DEBUG: pap-file = /etc/kannel/test/pappush.txt 2005-09-12 22:36:02 [11628] [0] DEBUG: group = configuration 2005-09-12 22:36:02 [11628] [0] DEBUG: push-url = http://localhost:8080/wappush 2005-09-12 22:36:02 [11628] [0] DEBUG: content-file = /etc/kannel/test/si.txt 2005-09-12 22:36:02 [11628] [0] DEBUG: username = wap_pusher 2005-09-12 22:36:02 [11628] [0] DEBUG: password = xa 2005-09-12 22:36:02 [11628] [0] DEBUG: Dump ends. 2005-09-12 22:36:02 [11628] [0] DEBUG: Started thread 1 (test/test_ppg.c:push_thread) 2005-09-12 22:36:02 [11628] [1] DEBUG: Thread 1 (test/test_ppg.c:push_thread) maps to pid 11628. 2005-09-12 22:36:02 [11628] [1] DEBUG: we have push content 2005-09-12 22:36:02 [11628] [1] DEBUG: Octet string at 0x935df70: 2005-09-12 22:36:02 [11628] [1] DEBUG: len: 949 2005-09-12 22:36:02 [11628] [1] DEBUG: size: 1024 2005-09-12 22:36:02 [11628] [1] DEBUG: immutable: 0 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 0d 0a 2d 2d 61 73 64 6c 66 6b 6a 69 75 72 77 67 ..--asdlfkjiurwg 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 68 61 73 66 0d 0a 43 6f 6e 74 65 6e 74 2d 54 79 hasf..Content-Ty 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 70 65 3a 20 61 70 70 6c 69 63 61 74 69 6f 6e 2f pe: application/ 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 78 6d 6c 0d 0a 0d 0a 3c 3f 78 6d 6c 20 76 65 72 xml?xml ver 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 73 69 6f 6e 3d 22 31 2e 30 22 3f 3e 20 0a 3c 21 sion=1.0? .! 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 44 4f 43 54 59 50 45 20 70 61 70 20 50 55 42 4c DOCTYPE pap PUBL 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 49 43 20 22 2d 2f 2f 57 41 50 46 4f 52 55 4d 2f IC -//WAPFORUM/ 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 2f 44 54 44 20 50 41 50 2f 2f 45 4e 22 20 0a 22 /DTD PAP//EN . 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 68 74 74 70 3a 2f 2f 77 77 77 2e 77 61 70 66 6f http://www.wapfo 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 72 75 6d 2e 6f 72 67 2f 44 54 44 2f 70 61 70 5f rum.org/DTD/pap_ 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 31 2e 30 2e 64 74 64 22 3e 20 0a 3c 70 61 70 3e 1.0.dtd .pap 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 20 0a 3c 70 75 73 68 2d 6d 65 73 73 61 67 65 20.push-message 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 70 75 73 68 2d 69 64 3d 22 39 66 6a 65 6f 33 39 push-id=9fjeo39 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 6a 66 30 38 34 40 70 69 2e 63 6f 6d 22 20 0a 64 [EMAIL PROTECTED] .d 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 65 6c 69 76 65 72 2d 62 65 66 6f 72 65 2d 74 69 eliver-before-ti 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 6d 65 73 74 61 6d 70 3d 22 32 30 30 31 2d 30 39 mestamp=2001-09 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 2d 32 38 54 30 36 3a 34 35 3a 30 30 5a 22 20 0a -28T06:45:00Z . 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 64 65 6c 69 76 65 72 2d 61 66 74 65 72 2d 74 69 deliver-after-ti 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 6d 65 73 74 61 6d 70 3d 22 32 30 30 31 2d 30 32 mestamp=2001-02 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 2d 32 38 54 30 36 3a 34 35 3a 30 30 5a 22 20 0a -28T06:45:00Z . 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 70 72 6f 67 72 65 73 73 2d 6e 6f 74 65 73 2d 72 progress-notes-r 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 65 71 75 65 73 74 65 64 3d 22 66 61 6c 73 65 22 equested=false 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 3e 20 0a 3c 61 64 64 72 65 73 73 20 61 64 64 72.address addr 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 65 73 73 2d 76 61 6c 75 65 3d 22 57 41 50 50 55 ess-value=WAPPU 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 53 48 3d 31 39 32 2e 31 36 38 2e 32 31 34 2e 31 SH=192.168.214.1 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 2f 54 59 50 45 3d 49 50 56 34 40 7a 65 62 72 61 /[EMAIL PROTECTED] 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 6d 6d 2e 64 79 6e 64 6e 73 2e 6f 72 67 22 2f 3e mm.dyndns.org/ 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 20 0a 3c 71 75 61 6c 69 74 79 2d 6f 66 2d 73 65.quality-of-se 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 72 76 69 63 65 20 70 72 69 6f 72 69 74 79 3d 22 rvice priority= 2005-09-12 22:36:02 [11628] [1] DEBUG: data: 6c 6f 77 22 20 0a 64 65 6c 69 76 65 72 79 2d 6d
Re: kannel sms and wap push
I have test it on major brand such as NOKIA, Siemens, Sony Ericcson and all work fine, but actually there are some other methodes which you can find in the mailing list archieves. Regards Willy - Original Message - From: John M L [EMAIL PROTECTED] To: users@kannel.org Sent: Tuesday, September 13, 2005 9:49 AM Subject: Re: kannel sms and wap push Thanks, willy. Do all phones support this method? - John [EMAIL PROTECTED] wrote: Hi, For me it's easier to send WAP PUSH using this method: $title = title; $url = the_url; $text = %01; // transid $text .= %06; // PDU Type (push) //$text .= %04%03; // length of content-type $text .= %01; $text .= %AE%81%EA; // content-type: application/vnd.wap.sic $text .= %02; // wbxml_version $text .= %05; // si_public_id $text .= %6A; // charset= (sibxml-charset) $text .= %00; // string table length $text .= %45; // si $text .= %C6; // indication.. $text .= %0C%03.rawurlencode($url).%00; // href=url $text .= %01; // end indication $text .= %03.rawurlencode(trim($title)).%00; $text .= %01; // /indication $text .= %01; // /si And push it with http://url/cgi-bin/sendsms?...udh=%06%05%04%0B%84%23%F0text=$text; FYI I use PHP. Hope it can help you :) Regards Willy - Original Message - From: John M L [EMAIL PROTECTED] To: users@kannel.org Sent: Tuesday, September 13, 2005 3:11 AM Subject: kannel sms and wap push I'm trying to impelment a mobile content distribution server using Kannel. The developers prior to me got smsbox working and now I'm trying to setup wapbox and ppg. Are wapbox and ppg both necessary for mobile content (i.e. ringtones, wallpapers and other binary file) distribution? Also, when I try to use a web query (through smsc = http) I get the following error in the smsbox.log 2005-09-12 15:56:55 [10020] [4] INFO: Starting to service test from 0018081234567 to 0018081234567 2005-09-12 15:56:55 [10020] [5] INFO: No reply sent, denied. If anyone could shed some light on this I'd be very appreciative. I was thrown into this and haven't had (and don't have) much time to tinker with kannel as we are on a big time crunch. Here's my kannel.conf group = core admin-port = 13000 admin-password = password status-password = password admin-deny-ip = *.*.*.* admin-allow-ip = 127.0.0.1 smsbox-port = 13001 wapbox-port = 13002 #box-deny-ip = *.*.*.* box-allow-ip = *.*.*.* udp-allow-ip = *.*.*.* wdp-interface-name=* log-file = /tmp/kannel.log log-level = 1 access-log = /tmp/kannel.access unified-prefix = +358,00358,0;+,00 white-list = sms_send group = smsc smsc = at smsc-id = wave293 #keepalive=5 #sim-buffering=true max-error-count=2 modemtype = wavecom device = /dev/ttyS0 group = smsc smsc = at smsc-id = sierra #allowed-smsc-id = modemtype = sierra_750 device = /dev/modem #speed = 9600 #keepalive = 60 sim-buffering = true #max-error-count = 5 # SMSBOX SETUP group = smsbox bearerbox-host = localhost sendsms-port = 13013 log-file = /tmp/smsbox.log log-level = 1 access-log = /tmp/smsaccess.log # SMS SERVICE Default # there should be default always group = sms-service keyword = default get-url = http://mydomain.org/z_send/sms.php?from=%pbody=%a; max-messages=0 #text = No service specified assume-plain-text = true group = sendsms-user username = sms_send password = password max-messages = 5 include = /etc/kannel/modems.conf # WAPBOX SETUP group = wapbox bearerbox-host = localhost log-file = /tmp/wapbox.log log-level = 1 syslog-level = none access-log = /tmp/wapaccess.log # PPG SETUP group = ppg ppg-url = /wapppush ppg-port = 8080 concurrent-pushes = 50 users = 52 ppg-allow-ip = *.*.*.* trusted-pi = false group = wap-push-user wap-push-user = pi_user ppg-username = wap_pusher ppg-password = password group = smsc smsc = http smsc-id = HTTP port = 1 system-type = kannel smsc-username = sms_send smsc-password = password no-sender = true no-coding = true send-url = http://mydomain.org/wapstuff Thanks, John
