Re: wap push sms mask
Isn't there any way I can change the mask without restarting kannel? On Fri, Sep 14, 2012 at 12:11 PM, [Digital^Dude] ® millennium@gmail.com wrote: Hi, I have set up kannel 1.5.0 with wap push and testing the send process using test_ppg. The mask is always 1234. How can I change it? Regards
Re: WAP push message over USSD
Hello Willy, USSD feature for sending normal message is already present in Kannel. I want to push WAP message over USSD as we used push over normal SMS. On Thu, May 17, 2012 at 7:11 PM, Willy Mularto sangpr...@gmail.com wrote: Is this Kannel's new feature? I read the user guide and found no information regarding this thing. AFAIK USSD is telco's territory, based on common practice, usually telco provide us some API. Here in Indonesia USSD final instruction will hit some URL and or simulate MO. On May 17, 2012, at 7:28 PM, GSM Revolution wrote: Hi, Please provide some idea how to send WAP push message over USSD. Thanks in advance.. Regards Rk Willy Mularto F300HD+MR18DE (NLC1725)
Re: WAP push message over USSD
Is this Kannel's new feature? I read the user guide and found no information regarding this thing. AFAIK USSD is telco's territory, based on common practice, usually telco provide us some API. Here in Indonesia USSD final instruction will hit some URL and or simulate MO. On May 17, 2012, at 7:28 PM, GSM Revolution wrote: Hi, Please provide some idea how to send WAP push message over USSD. Thanks in advance.. Regards Rk Willy Mularto F300HD+MR18DE (NLC1725)
Re: WAP Push
Hi, What you are asking is outside the spec. PPG should be sent over SMS. Normal wap traffic is sent over UDP. PPG over UDP is not supported, nor it will ever be. BR, Nikos - Original Message - From: Andrew Caruana To: users@kannel.org Sent: Monday, April 25, 2011 7:55 PM Subject: WAP Push Dear all, We have just been reading from the Kannel Architecture and Design (Revision: 1.19) document as available online that Kannel currently implements WDP (over SMS) only as a WAP push bearer. In this respect, what is the current status in supporting UDP (over IP) as an alternative WAP push bearer? We are currently running Kannel 1.4.3. Thanks and regards, Andrew Deborah
RE: wap push notification over SMS, Telcel network
Could you post some log files, config files? -Original Message- From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Zhnupy Gonzalez Sent: Saturday, 02 April, 2011 10:50 To: users@kannel.org Subject: wap push notification over SMS, Telcel network Hello Does anybody else in the community have experienced problems sending wap push notifications over SMS on Telcel network (México)? I'm using test_ppg, bearerbox's log shows the data delivered to modem (I validate the data is ok using: http://twit88.com/home/utility/sms-pdu-encode-decode), but yet every time the SMS received is empty having no clue about what is wrong I tried with nowsms (trial version) and the SMS received is also empty, which makes me think maybe the operator is not allowing that kind of SMSs, does anyone knows something about it? regards smime.p7s Description: S/MIME cryptographic signature
Re: wap push notification over SMS, Telcel network
Hi, You should contact your provider. You need wap-enabled SIM card, to get wap-pushes. Can you wap-push from another mobile? BR, Nikos - Original Message - From: Zhnupy Gonzalez zhn...@gmail.com To: users@kannel.org Sent: Saturday, April 02, 2011 11:50 AM Subject: wap push notification over SMS, Telcel network Hello Does anybody else in the community have experienced problems sending wap push notifications over SMS on Telcel network (Mιxico)? I'm using test_ppg, bearerbox's log shows the data delivered to modem (I validate the data is ok using: http://twit88.com/home/utility/sms-pdu-encode-decode), but yet every time the SMS received is empty having no clue about what is wrong I tried with nowsms (trial version) and the SMS received is also empty, which makes me think maybe the operator is not allowing that kind of SMSs, does anyone knows something about it? regards
RE: Wap push problem
Hi Edwin, From what I can tell, you haven't url encoded the udh. Its supposed to have several percentage signs(%) in between the message and udh.coding is not even that important. I had the same problem till I read through this resource: http://dev.sellingsource.com/category/kannel/ Eg for WAP PUSH the udh field in the send-url is meant to be %06%05%04%0B%84%23%F0 as opposed to 0605040B8423F0 and the messages is also meant to have these percentage signs in between to encode the text. An example of my send-url part is as follows: ..to=udh=%06%05%04%0B%84%23%F0text=%1B%06%01%AE%02%05%6A%00%45%C6%0C%0 3%77%61%70%2E%79%61%68%6F%6F%2E%63%6F%6D%00%01%03%56%69%73%69%74%20%59%61%68 %6F%6F%21%20%6F%6E%20%79%6F%75%72%20%70%68%6F%6E%65%00%01%01from=.. Read the resource I posted above and it might help. Rapture From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Edwin Malo Sent: Wednesday, December 29, 2010 2:21 PM To: users@kannel.org Subject: Wap push problem Hi all, I hope someone could help me, i have some problems trying to send a wap push message using kannel, i build the message according to the specifications and it works with others operators but when i send exactly the same message to an specific one the final user only receive a sms instead the wap push. I checked with the operator and they send and receive without any problem from others but for some reasons our message does not work. I have tried everything but nothing seems to work, changes in kannel connection, set up the data coding using coding=1 alt-dcs=1 mclass=1. I also try to change the way i made the message because the operator said that only support this formats US ASCII, UTF16, LATIN but i could not find any different solution. At this point I don't have any idea about what could be the problem because i tested the same wap push with other operators and it works well using the same kannel configuration. This is the way i build the wap push: $text = '1B0601AE02056A0045C60C03'; $text .= bin2hex($url); $text .= '000103'; $text .= bin2hex(utf8_encode($text)); $text .= '000101'; The message looks like 1B0601AE02056A0045C60C03772E676F6F676C652E636F6D0001032054657374000101 Also i use the header 0605040B84, and this is part of the smpp connection log DEBUG: boxc_receiver: sms received DEBUG: send_msg: sending msg to box: 127.0.0.1 DEBUG: throughput (0.00,0.00) DEBUG: Manually forced source addr ton = 1, source add npi = 1 DEBUG: Manually forced dest addr ton = 1, dest add npi = 1 DEBUG: Sending PDU: DEBUG: SMPP PDU 0x16453e0 dump: DEBUG: type_name: submit_sm DEBUG: command_id: 4 = 0x0004 DEBUG: command_status: 0 = 0x DEBUG: sequence_number: 161 = 0x00a1 DEBUG: service_type: NULL DEBUG: source_addr_ton: 1 = 0x0001 DEBUG: source_addr_npi: 1 = 0x0001 DEBUG: source_addr: DEBUG: dest_addr_ton: 1 = 0x0001 DEBUG: dest_addr_npi: 1 = 0x0001 DEBUG: destination_addr: xxx DEBUG: esm_class: 67 = 0x0043 DEBUG: protocol_id: 0 = 0x DEBUG: priority_flag: 1 = 0x0001 DEBUG: schedule_delivery_time: NULL DEBUG: validity_period: NULL DEBUG: registered_delivery: 1 = 0x0001 DEBUG: replace_if_present_flag: 0 = 0x DEBUG: data_coding: 4 = 0x0004 DEBUG: sm_default_msg_id: 0 = 0x DEBUG: sm_length: 75 = 0x004b DEBUG: short_message: DEBUG:Octet string at 0x1645380: DEBUG: len: 75 DEBUG: size: 1024 DEBUG: immutable: 0 I hope this information could help to find any possible problem, thanks in advance. Edwin
RE: Wap push problem
Hi, Thanks for your answer, I just put the message after codification but before send it to the operator I add all the % to the url, that's just because the message are made by one entity in the process and other one take and send it to the operator. Edwin From: supp...@ims.co.ke To: agu4...@hotmail.com; users@kannel.org Subject: RE: Wap push problem Date: Wed, 29 Dec 2010 14:37:41 +0300 Hi Edwin, From what I can tell, you haven’t url encoded the udh. Its supposed to have several percentage signs(%) in between the message and udh…coding is not even that important. I had the same problem till I read through this resource: http://dev.sellingsource.com/category/kannel/ Eg for WAP PUSH the udh field in the send-url is meant to be %06%05%04%0B%84%23%F0 as opposed to 0605040B8423F0 and the messages is also meant to have these percentage signs in between to encode the text. An example of my send-url part is as follows: ……to=udh=%06%05%04%0B%84%23%F0text=%1B%06%01%AE%02%05%6A%00%45%C6%0C%03%77%61%70%2E%79%61%68%6F%6F%2E%63%6F%6D%00%01%03%56%69%73%69%74%20%59%61%68%6F%6F%21%20%6F%6E%20%79%6F%75%72%20%70%68%6F%6E%65%00%01%01from=…… Read the resource I posted above and it might help. Rapture From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf Of Edwin Malo Sent: Wednesday, December 29, 2010 2:21 PM To: users@kannel.org Subject: Wap push problem Hi all, I hope someone could help me, i have some problems trying to send a wap push message using kannel, i build the message according to the specifications and it works with others operators but when i send exactly the same message to an specific one the final user only receive a sms instead the wap push. I checked with the operator and they send and receive without any problem from others but for some reasons our message does not work. I have tried everything but nothing seems to work, changes in kannel connection, set up the data coding using coding=1 alt-dcs=1 mclass=1. I also try to change the way i made the message because the operator said that only support this formats US ASCII, UTF16, LATIN but i could not find any different solution. At this point I don't have any idea about what could be the problem because i tested the same wap push with other operators and it works well using the same kannel configuration. This is the way i build the wap push: $text = '1B0601AE02056A0045C60C03'; $text .= bin2hex($url); $text .= '000103'; $text .= bin2hex(utf8_encode($text)); $text .= '000101'; The message looks like 1B0601AE02056A0045C60C03772E676F6F676C652E636F6D0001032054657374000101 Also i use the header 0605040B84, and this is part of the smpp connection log DEBUG: boxc_receiver: sms received DEBUG: send_msg: sending msg to box: 127.0.0.1 DEBUG: throughput (0.00,0.00) DEBUG: Manually forced source addr ton = 1, source add npi = 1 DEBUG: Manually forced dest addr ton = 1, dest add npi = 1 DEBUG: Sending PDU: DEBUG: SMPP PDU 0x16453e0 dump: DEBUG: type_name: submit_sm DEBUG: command_id: 4 = 0x0004 DEBUG: command_status: 0 = 0x DEBUG: sequence_number: 161 = 0x00a1 DEBUG: service_type: NULL DEBUG: source_addr_ton: 1 = 0x0001 DEBUG: source_addr_npi: 1 = 0x0001 DEBUG: source_addr: DEBUG: dest_addr_ton: 1 = 0x0001 DEBUG: dest_addr_npi: 1 = 0x0001 DEBUG: destination_addr: xxx DEBUG: esm_class: 67 = 0x0043 DEBUG: protocol_id: 0 = 0x DEBUG: priority_flag: 1 = 0x0001 DEBUG: schedule_delivery_time: NULL DEBUG: validity_period: NULL DEBUG: registered_delivery: 1 = 0x0001 DEBUG: replace_if_present_flag: 0 = 0x DEBUG: data_coding: 4 = 0x0004 DEBUG: sm_default_msg_id: 0 = 0x DEBUG: sm_length: 75 = 0x004b DEBUG: short_message: DEBUG:Octet string at 0x1645380: DEBUG: len: 75 DEBUG: size: 1024 DEBUG: immutable: 0 I hope this information could help to find any possible problem, thanks in advance. Edwin
Re: WAP Push
The list archives is your friend :) sangprabv sangpr...@gmail.com http://www.petitiononline.com/froyo/ On Sep 6, 2010, at 4:43 PM, sapna singh wrote: Hi, Can any body give me sample of WAP Push Link. Its really helpful for me. -- Regards Sapna
Re: WAP-Push with Nokia 6210
Hi, Broken sender and destination are fine. Just ignore. My mistake. SMS is deleted at that point. If this happens only during startup, and just the first couple of SMS are requeued, it is no biggie. To avoid it check user's guide about need-sleep. If needed, just send modem logs. No other logs are necessary. BR, Nikos - Original Message - From: Thomas Sieh ts...@gmx.de To: Nikos Balkanas nbalka...@gmail.com Cc: ts...@gmx.de; users@kannel.org Sent: Tuesday, June 15, 2010 1:50 AM Subject: Re: WAP-Push with Nokia 6210 hi, sometimes the sender- and destination-adress look broken. for example bearerbox 2010-06-15 03:18:29: 2010-06-15 03:18:29 [5360] [7] INFO: NIKOS!!! sender: P^G^AI^?. destination: P^A, result: 0 is this ok? this is much more times in the log. everytime other characters. to your questions: 1) yes, i think so... there was no message left in the queue and I received a message at around 4:15. That was the reason for copy all the logs into the mail again and that it was as long ;) 2) ok, see the logs below 3) there are some NIKOS!!!-entries in bearerbox, that are not listed in smsc.log. for example: 2010-06-14 03:15:26. this entry is not in smsc.log. On Mon, Jun 14, 2010 at 08:05:00AM +0300, Nikos Balkanas wrote: Hi, A couple of questions. 1) Seems that eventually SMS is sent after 3' or so from access logs. Yet I see resend_tries up to 58, or 29'. Is the SMS ever sent? 2) Please patch additional debug msg attached. 3) Compare smsc.log ERROR times with NIKOS!!! Sent SMS, result: from bb logs. They should match absolutely. Kannel works fine. Problem is with your modem. Post detailed smsc logs of failures and successes for a single SMS with the problem. PS: In the end either download a fresh svn, or remember to edit gw/bb_smscconn.c and gw/bb_box.c and delete all references to NIKOS!!! BR, Nikos [..snip..]
Re: WAP-Push with Nokia 6210
2010-06-15 15:22:35 [17069] [7] DEBUG: sms_router: handling message (0x81b5208 vs 0x81b5208) 2010-06-15 15:22:35 [17069] [7] DEBUG: re-queing SMS not-yet-to-be resent 2010-06-15 15:22:35 [17069] [7] DEBUG: sms_router: time to sleep 30.00 secs. 2010-06-15 15:23:05 [17069] [7] DEBUG: sms_router: gwlist_len = 1 2010-06-15 15:23:05 [17069] [7] DEBUG: sms_router: handling message (0x81b5208 vs 0x81b5208) 2010-06-15 15:23:05 [17069] [7] DEBUG: Message routed successfully. smsbox :: : 2010-06-15 15:19:29 [17138] [0] DEBUG: Started thread 4 (gw/smsbox.c:obey_request_thread) 2010-06-15 15:19:29 [17138] [5] DEBUG: Thread 5 (gw/smsbox.c:url_result_thread) maps to pid 17138. 2010-06-15 15:19:29 [17138] [0] DEBUG: Started thread 5 (gw/smsbox.c:url_result_thread) 2010-06-15 15:19:29 [17138] [0] DEBUG: Started thread 6 (gw/smsbox.c:http_queue_thread) 2010-06-15 15:19:29 [17138] [0] DEBUG: Connecting to 127.0.0.1 2010-06-15 15:19:29 [17138] [6] DEBUG: Thread 6 (gw/smsbox.c:http_queue_thread) maps to pid 17138. 2010-06-15 15:19:29 [17138] [0] INFO: Connected to bearerbox at localhost port 13001. 2010-06-15 15:19:29 [17138] [0] DEBUG: Started thread 7 (gw/heartbeat.c:heartbeat_thread) 2010-06-15 15:19:29 [17138] [7] DEBUG: Thread 7 (gw/heartbeat.c:heartbeat_thread) maps to pid 17138. 2010-06-15 15:19:29 [17138] [2] DEBUG: Thread 2 (gwlib/http.c:server_thread) maps to pid 17138. 2010-06-15 15:21:01 [17138] [2] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'. 2010-06-15 15:21:01 [17138] [2] DEBUG: HTTP: Created HTTPClient area 0x815b080. 2010-06-15 15:21:01 [17138] [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms from 127.0.0.1 2010-06-15 15:21:01 [17138] [3] INFO: sendsms used by tester 2010-06-15 15:21:01 [17138] [3] INFO: sendsms sender:tester:+4915779** (127.0.0.1) to:+4917649** msg:das ist eine sms 2010-06-15 15:21:01 [17138] [3] DEBUG: Stored UUID 61bea839-e84d-42c4-a60a-021e16c9bc74 2010-06-15 15:21:01 [17138] [3] DEBUG: message length 16, sending 1 messages 2010-06-15 15:21:01 [17138] [3] DEBUG: Status: 202 Answer: Sent. 2010-06-15 15:21:01 [17138] [3] DEBUG: Delayed reply - wait for bearerbox 2010-06-15 15:21:01 [17138] [0] DEBUG: Got ACK (0) of 61bea839-e84d-42c4-a60a-021e16c9bc74 2010-06-15 15:21:01 [17138] [0] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'. 2010-06-15 15:21:05 [17138] [3] INFO: smsbox: Got HTTP request /favicon.ico from 127.0.0.1 2010-06-15 15:21:05 [17138] [3] DEBUG: Status: 404 Answer: Unknown request. 2010-06-15 15:21:05 [17138] [3] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'. 2010-06-15 15:21:09 [17138] [3] INFO: smsbox: Got HTTP request /favicon.ico from 127.0.0.1 2010-06-15 15:21:09 [17138] [3] DEBUG: Status: 404 Answer: Unknown request. 2010-06-15 15:21:09 [17138] [3] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'. 2010-06-15 15:21:17 [17138] [1] DEBUG: HTTP: Destroying HTTPClient area 0x815b080. 2010-06-15 15:21:17 [17138] [1] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'. thanks, thomas Nikos wrote: Hi, Broken sender and destination are fine. Just ignore. My mistake. SMS is deleted at that point. If this happens only during startup, and just the first couple of SMS are requeued, it is no biggie. To avoid it check user's guide about need-sleep. If needed, just send modem logs. No other logs are necessary. BR, Nikos Original-Nachricht Datum: Mon, 14 Jun 2010 08:05:00 +0300 Von: Nikos Balkanas nbalka...@gmail.com An: ts...@gmx.de CC: users@kannel.org Betreff: Re: WAP-Push with Nokia 6210 Hi, A couple of questions. 1) Seems that eventually SMS is sent after 3' or so from access logs. Yet I see resend_tries up to 58, or 29'. Is the SMS ever sent? 2) Please patch additional debug msg attached. 3) Compare smsc.log ERROR times with NIKOS!!! Sent SMS, result: from bb logs. They should match absolutely. Kannel works fine. Problem is with your modem. Post detailed smsc logs of failures and successes for a single SMS with the problem. PS: In the end either download a fresh svn, or remember to edit gw/bb_smscconn.c and gw/bb_box.c and delete all references to NIKOS!!! BR, Nikos -- GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl. Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl
Re: WAP-Push with Nokia 6210
Hi, This is very confusing. In bb logs I see a successful transmission at 15:21:01. Yet I see no evidence of it in smsc logs. What's going on? Besides I see in bb logs requeuing SMS at 15:21:03, without sending it from smsbox, which means that when you started queue was not empty. Also you removed debugs from gw/bb_smscconn.c. Please explain, Nikos - Original Message - From: Thomas Sieh ts...@gmx.de To: Nikos Balkanas nbalka...@gmail.com Cc: users@kannel.org Sent: Tuesday, June 15, 2010 6:00 PM Subject: Re: WAP-Push with Nokia 6210 Hi Nikos, I have read you E-Mail again and have seen, that you wrote single sms, not simple sms, sorry. The Problem occurs at every time. Not only after start or the first bulk. i have already tested -- and did it again after your tip -- to set up need-sleep. I tried all variations of need-sleep and sendline-sleep. this options don't make a difference. so I have set it up like at the compatibility site described for the nokia 6210: need-sleep = true. I have done it again with your new patch. this time the first message was sent after only 2 errors. so i will attach the other logs, too. here are the logfiles: access :: : 2010-06-15 15:19:28 Log begins 2010-06-15 15:19:29 Log begins 2010-06-15 15:19:29 Log begins 2010-06-15 15:21:01 send-SMS request added - sender:tester:+4915779** 127.0.0.1 target:+4917649** request: 'das ist eine sms' 2010-06-15 15:23:10 Sent SMS [SMSC:SMSC_01] [SVC:tester] [ACT:] [BINF:] [FID:] [META:] [from:+4915779**] [to:+4917649**] [flags:-1:0:-1:-1:-1] [msg:16:das ist eine sms] [udh:0:] smsc:: :: 2010-06-15 15:19:28 [17069] [6] INFO: AT2[SMSC_01]: opening device 2010-06-15 15:19:28 [17069] [6] DEBUG: AT2[SMSC_01]: device opened. Telnet mode = 0 2010-06-15 15:19:29 [17069] [6] DEBUG: AT2[SMSC_01]: device opened 2010-06-15 15:19:29 [17069] [6] INFO: AT2[SMSC_01]: Logging in 2010-06-15 15:19:29 [17069] [6] INFO: AT2[SMSC_01]: init device 2010-06-15 15:19:29 [17069] [6] INFO: AT2[SMSC_01]: speed set to 9600 2010-06-15 15:19:29 [17069] [6] DEBUG: AT2[SMSC_01]: -- ATZ^M 2010-06-15 15:19:29 [17069] [6] DEBUG: AT2[SMSC_01]: -- OK 2010-06-15 15:19:29 [17069] [6] DEBUG: AT2[SMSC_01]: -- AT^M 2010-06-15 15:19:29 [17069] [6] DEBUG: AT2[SMSC_01]: -- AT 2010-06-15 15:19:29 [17069] [6] DEBUG: AT2[SMSC_01]: -- OK 2010-06-15 15:19:29 [17069] [6] DEBUG: AT2[SMSC_01]: -- ATF^M 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- ATF 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- OK 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- ATE0^M 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- ATE0 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- OK 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- AT+IFC=2,2^M 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- OK 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- AT+CPIN?^M 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- +CPIN: READY 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- AT+CSCA=+49177061^M 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- OK 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- AT+CMGF=0^M 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- OK 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- AT+CSMS=?^M 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- OK 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- AT+CNMI=1,2,0,1,0^M 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- +CSMS: (0,1) 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- OK 2010-06-15 15:19:30 [17069] [6] INFO: AT2[SMSC_01]: AT SMSC successfully opened. 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- OK 2010-06-15 15:21:02 [17069] [6] DEBUG: AT2[SMSC_01]: TP-Validity-Period: 24.0 hours 2010-06-15 15:21:02 [17069] [6] DEBUG: AT2[SMSC_01]: -- AT+CMGS=29^M 2010-06-15 15:21:02 [17069] [6] DEBUG: AT2[SMSC_01]: -- 2010-06-15 15:21:02 [17069] [6] DEBUG: AT2[SMSC_01]: -- 2010-06-15 15:21:02 [17069] [6] DEBUG: AT2[SMSC_01]: send command status: 1 2010-06-15 15:21:02 [17069] [6] DEBUG: AT2[SMSC_01]: -- 0011000D9194714669 2010-06-15 15:21:02 [17069] [6] DEBUG: AT2[SMSC_01]: -- **A710E4F0 2010-06-15 15:21:03 [17069] [6] DEBUG: AT2[SMSC_01]: -- 1C949ED341E5B4BB0C 2010-06-15 15:21:03 [17069] [6] DEBUG: AT2[SMSC_01]: -- 9AB7E7^Z 2010-06-15 15:21:03 [17069] [6] DEBUG: AT2[SMSC_01]: -- ERROR 2010-06-15 15:21:03 [17069] [6] ERROR: AT2[SMSC_01]: Generic error: ERROR 2010-06-15 15:21:03 [17069] [6] DEBUG: AT2[SMSC_01]: send command status: -1 2010-06-15 15:22:05 [17069] [6] DEBUG: AT2[SMSC_01]: TP-Validity-Period: 24.0 hours 2010-06-15 15:22:05 [17069] [6] DEBUG: AT2[SMSC_01]: -- AT+CMGS=29^M 2010-06-15 15:22:05 [17069] [6] DEBUG: AT2[SMSC_01]: -- 2010-06-15 15:22:05 [17069] [6] DEBUG: AT2[SMSC_01]: send command status: 1 2010-06-15 15:22:05 [17069] [6] DEBUG: AT2[SMSC_01]: -- 0011000D9194714669 2010-06-15 15:22:05 [17069] [6] DEBUG: AT2
Re: WAP-Push with Nokia 6210
(3) No it's not. But I cannot help you unless you post relevant entries from both bb and smsc logs. Posted logs end up at 00:00:26. Give me a context (+/- 3 lines) from incident and nothing more (skip access smsbox logs - not needed). Nikos - Original Message - From: Thomas Sieh ts...@gmx.de To: Nikos Balkanas nbalka...@gmail.com Cc: ts...@gmx.de; users@kannel.org Sent: Tuesday, June 15, 2010 1:50 AM Subject: Re: WAP-Push with Nokia 6210 hi, sometimes the sender- and destination-adress look broken. for example bearerbox 2010-06-15 03:18:29: 2010-06-15 03:18:29 [5360] [7] INFO: NIKOS!!! sender: P^G^AI^?. destination: P^A, result: 0 is this ok? this is much more times in the log. everytime other characters. to your questions: 1) yes, i think so... there was no message left in the queue and I received a message at around 4:15. That was the reason for copy all the logs into the mail again and that it was as long ;) 2) ok, see the logs below 3) there are some NIKOS!!!-entries in bearerbox, that are not listed in smsc.log. for example: 2010-06-14 03:15:26. this entry is not in smsc.log. On Mon, Jun 14, 2010 at 08:05:00AM +0300, Nikos Balkanas wrote: Hi, A couple of questions. 1) Seems that eventually SMS is sent after 3' or so from access logs. Yet I see resend_tries up to 58, or 29'. Is the SMS ever sent? 2) Please patch additional debug msg attached. 3) Compare smsc.log ERROR times with NIKOS!!! Sent SMS, result: from bb logs. They should match absolutely. Kannel works fine. Problem is with your modem. Post detailed smsc logs of failures and successes for a single SMS with the problem. PS: In the end either download a fresh svn, or remember to edit gw/bb_smscconn.c and gw/bb_box.c and delete all references to NIKOS!!! BR, Nikos [..snip..] the new logfiles: [..snip..]
Re: WAP-Push with Nokia 6210
Hi, when i interpret the logs correct the smsc ist opened at 15:19:30. At 15:21:01 i pushed a sms from webbrowser and the smsbox gave it directly to the bearerbox. at 15:21:02 the smsc try to send the data, but raises an error. from 15:21:03 to 15:22:03 the bearerbox tried to route the message. The smsc tries again to send the message, successless. At 15:22:05 the smsc tries again to send the data, but raises an error. Then the bearerbox routes the message again until 15:23:05. this time the smsc sends the message successfully. is this correct? then i don't understand what the smsbox should do after the initial sending to the bearerbox. and why should be there an other message in the queue? isn't it the same message that kannel tries to send multiple times and only at 15:23:05 with success? I don't have removed any debug-infos! i never thouched the source apart from the patch you sent me. and this i have installed into a fresh downloaded cvs-kannel. I have done another test and created a chronologic dependend chart of interaction between the boxes in openoffice format. i attached it. it's really schort. maybe you see something between the lines or have one more idea. possibly the routing of the bearerbox? i think you are right with the guess that there could be a problem with the phone. tomorrow i will try another cable. possibly i have luck :) thanks, thomas On Tue, Jun 15, 2010 at 06:24:51PM +0300, Nikos Balkanas wrote: Hi, This is very confusing. In bb logs I see a successful transmission at 15:21:01. Yet I see no evidence of it in smsc logs. What's going on? Besides I see in bb logs requeuing SMS at 15:21:03, without sending it from smsbox, which means that when you started queue was not empty. Also you removed debugs from gw/bb_smscconn.c. Please explain, Nikos - Original Message - From: Thomas Sieh ts...@gmx.de To: Nikos Balkanas nbalka...@gmail.com Cc: users@kannel.org Sent: Tuesday, June 15, 2010 6:00 PM Subject: Re: WAP-Push with Nokia 6210 Hi Nikos, I have read you E-Mail again and have seen, that you wrote single sms, not simple sms, sorry. The Problem occurs at every time. Not only after start or the first bulk. i have already tested -- and did it again after your tip -- to set up need-sleep. I tried all variations of need-sleep and sendline-sleep. this options don't make a difference. so I have set it up like at the compatibility site described for the nokia 6210: need-sleep = true. I have done it again with your new patch. this time the first message was sent after only 2 errors. so i will attach the other logs, too. here are the logfiles: access :: : 2010-06-15 15:19:28 Log begins 2010-06-15 15:19:29 Log begins 2010-06-15 15:19:29 Log begins 2010-06-15 15:21:01 send-SMS request added - sender:tester:+4915779** 127.0.0.1 target:+4917649** request: 'das ist eine sms' 2010-06-15 15:23:10 Sent SMS [SMSC:SMSC_01] [SVC:tester] [ACT:] [BINF:] [FID:] [META:] [from:+4915779**] [to:+4917649**] [flags:-1:0:-1:-1:-1] [msg:16:das ist eine sms] [udh:0:] smsc:: :: 2010-06-15 15:19:28 [17069] [6] INFO: AT2[SMSC_01]: opening device 2010-06-15 15:19:28 [17069] [6] DEBUG: AT2[SMSC_01]: device opened. Telnet mode = 0 2010-06-15 15:19:29 [17069] [6] DEBUG: AT2[SMSC_01]: device opened 2010-06-15 15:19:29 [17069] [6] INFO: AT2[SMSC_01]: Logging in 2010-06-15 15:19:29 [17069] [6] INFO: AT2[SMSC_01]: init device 2010-06-15 15:19:29 [17069] [6] INFO: AT2[SMSC_01]: speed set to 9600 2010-06-15 15:19:29 [17069] [6] DEBUG: AT2[SMSC_01]: -- ATZ^M 2010-06-15 15:19:29 [17069] [6] DEBUG: AT2[SMSC_01]: -- OK 2010-06-15 15:19:29 [17069] [6] DEBUG: AT2[SMSC_01]: -- AT^M 2010-06-15 15:19:29 [17069] [6] DEBUG: AT2[SMSC_01]: -- AT 2010-06-15 15:19:29 [17069] [6] DEBUG: AT2[SMSC_01]: -- OK 2010-06-15 15:19:29 [17069] [6] DEBUG: AT2[SMSC_01]: -- ATF^M 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- ATF 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- OK 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- ATE0^M 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- ATE0 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- OK 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- AT+IFC=2,2^M 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- OK 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- AT+CPIN?^M 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- +CPIN: READY 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- AT+CSCA=+49177061^M 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- OK 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- AT+CMGF=0^M 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- OK 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- AT+CSMS=?^M 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- OK 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- AT+CNMI=1,2,0,1,0^M 2010
Re: WAP-Push with Nokia 6210
Hi, Actually you are more or less right. result:0 means SMSC_SUCCESS, not queued or failed or anything else. So I assumed that when it got that at 22:04:10 modem already returned OK. Checking at the sources, however, shows that this is returned only when the SMS is put in bb's at2 queue for sending, and that the at2 driver always returns SMSC_SUCCESS (0). Therefore everything works as expected from kannel's side. Bb correctly requeues the SMS as long as it gets an ERROR from your modem. No need to check the modem cable, it is fine. Could be a problem with the SIM (network congested - change operator?) or the modem is broken - change modem. BR, Nikos - Original Message - From: Thomas Sieh ts...@gmx.de To: Nikos Balkanas nbalka...@gmail.com Cc: Thomas Sieh ts...@gmx.de; users@kannel.org Sent: Wednesday, June 16, 2010 1:26 AM Subject: Re: WAP-Push with Nokia 6210 Hi, when i interpret the logs correct the smsc ist opened at 15:19:30. At 15:21:01 i pushed a sms from webbrowser and the smsbox gave it directly to the bearerbox. at 15:21:02 the smsc try to send the data, but raises an error. from 15:21:03 to 15:22:03 the bearerbox tried to route the message. The smsc tries again to send the message, successless. At 15:22:05 the smsc tries again to send the data, but raises an error. Then the bearerbox routes the message again until 15:23:05. this time the smsc sends the message successfully. is this correct? then i don't understand what the smsbox should do after the initial sending to the bearerbox. and why should be there an other message in the queue? isn't it the same message that kannel tries to send multiple times and only at 15:23:05 with success? I don't have removed any debug-infos! i never thouched the source apart from the patch you sent me. and this i have installed into a fresh downloaded cvs-kannel. I have done another test and created a chronologic dependend chart of interaction between the boxes in openoffice format. i attached it. it's really schort. maybe you see something between the lines or have one more idea. possibly the routing of the bearerbox? i think you are right with the guess that there could be a problem with the phone. tomorrow i will try another cable. possibly i have luck :) thanks, thomas On Tue, Jun 15, 2010 at 06:24:51PM +0300, Nikos Balkanas wrote: Hi, This is very confusing. In bb logs I see a successful transmission at 15:21:01. Yet I see no evidence of it in smsc logs. What's going on? Besides I see in bb logs requeuing SMS at 15:21:03, without sending it from smsbox, which means that when you started queue was not empty. Also you removed debugs from gw/bb_smscconn.c. Please explain, Nikos - Original Message - From: Thomas Sieh ts...@gmx.de To: Nikos Balkanas nbalka...@gmail.com Cc: users@kannel.org Sent: Tuesday, June 15, 2010 6:00 PM Subject: Re: WAP-Push with Nokia 6210 Hi Nikos, I have read you E-Mail again and have seen, that you wrote single sms, not simple sms, sorry. The Problem occurs at every time. Not only after start or the first bulk. i have already tested -- and did it again after your tip -- to set up need-sleep. I tried all variations of need-sleep and sendline-sleep. this options don't make a difference. so I have set it up like at the compatibility site described for the nokia 6210: need-sleep = true. I have done it again with your new patch. this time the first message was sent after only 2 errors. so i will attach the other logs, too. here are the logfiles: access :: : 2010-06-15 15:19:28 Log begins 2010-06-15 15:19:29 Log begins 2010-06-15 15:19:29 Log begins 2010-06-15 15:21:01 send-SMS request added - sender:tester:+4915779** 127.0.0.1 target:+4917649** request: 'das ist eine sms' 2010-06-15 15:23:10 Sent SMS [SMSC:SMSC_01] [SVC:tester] [ACT:] [BINF:] [FID:] [META:] [from:+4915779**] [to:+4917649**] [flags:-1:0:-1:-1:-1] [msg:16:das ist eine sms] [udh:0:] smsc:: :: 2010-06-15 15:19:28 [17069] [6] INFO: AT2[SMSC_01]: opening device 2010-06-15 15:19:28 [17069] [6] DEBUG: AT2[SMSC_01]: device opened. Telnet mode = 0 2010-06-15 15:19:29 [17069] [6] DEBUG: AT2[SMSC_01]: device opened 2010-06-15 15:19:29 [17069] [6] INFO: AT2[SMSC_01]: Logging in 2010-06-15 15:19:29 [17069] [6] INFO: AT2[SMSC_01]: init device 2010-06-15 15:19:29 [17069] [6] INFO: AT2[SMSC_01]: speed set to 9600 2010-06-15 15:19:29 [17069] [6] DEBUG: AT2[SMSC_01]: -- ATZ^M 2010-06-15 15:19:29 [17069] [6] DEBUG: AT2[SMSC_01]: -- OK 2010-06-15 15:19:29 [17069] [6] DEBUG: AT2[SMSC_01]: -- AT^M 2010-06-15 15:19:29 [17069] [6] DEBUG: AT2[SMSC_01]: -- AT 2010-06-15 15:19:29 [17069] [6] DEBUG: AT2[SMSC_01]: -- OK 2010-06-15 15:19:29 [17069] [6] DEBUG: AT2[SMSC_01]: -- ATF^M 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- ATF 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- OK 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01]: -- ATE0^M 2010-06-15 15:19:30 [17069] [6] DEBUG: AT2[SMSC_01
Re: WAP-Push with Nokia 6210
Hi Nikos, I have done some more tests. the Problem is, that when I send the first message, it is stored in the queue, but will not be send. regardless if it is a wap push message or a normal mo push sms. the same with all other following messages. but then, for me not obviously, kannel sends a few seconds after the last message the most other messages in the queue, but not absolute all. mostly there are one or two left inside the queue. In summary I can say: kannel don't send the messages until one is accepted. but then kannel sends the most of the other messages, too. I sent the messages with the following 2 commands: lynx -dump http://localhost:13013/cgi-bin/sendsms?username=testerpassw ord=foobarfrom=%2B49157to=%2B49176smsc=SMSC_01text=D as+ist+eine+SMS lynx -dump http://localhost:13013/cgi-bin/sendsms?username=testerpassw ord=foobarfrom=%2B49157to=%2B49176udh=%06%05%04%0B%84 %23%F0smsc=SMSC_01text=%1B%06%01%AE%02%05%6A%00%45%C6%0C%03*.s elfip.org/index.wml%00%01%03Das+ist+ein+kleiner+Test%00%01%01 thanks in advance br, thomas following the full logs and the dependent config: config :: : # kannel.conf group = core admin-port = 13000 admin-password = genap status-password = genap admin-deny-ip = *.*.*.* admin-allow-ip = 127.0.0.1 log-file = /var/log/kannel/bearerbox.log log-level = 0 access-log = /var/log/kannel/access.log smsbox-port = 13001 wapbox-port = 13002 wdp-interface-name = * store-type = spool store-location = /var/spool/kannel group = smsc smsc-id = SMSC_01 smsc = at modemtype = nokiaphone speed = 9600 device = /dev/ttyUSB0 sms-center = +49177061 #keepalive = 20 log-file = /var/log/kannel/smsc.log log-level = 0 group = modems id = nokiaphone name = Nokia Phone detect-string = Nokia Mobile Phone need-sleep = true init-string = AT+CNMI=1,2,0,1,0;+CMEE=2 keepalive-cmd = AT+CBC;+CSQ enable-mms = true group = wapbox bearerbox-host = localhost log-file = /var/log/kannel/wapbox.log log-level = 0 access-log = /var/log/kannel/access.log syslog-level = none group = smsbox smsbox-id = sms_box bearerbox-host = localhost sendsms-port = 13013 sendsms-chars = 0123456789+ global-sender = +49157 log-file = /var/log/kannel/smsbox.log log-level = 0 access-log = /var/log/kannel/access.log sendsms-url = /cgi-bin/sendsms group = sendsms-user username = tester password = foobar user-allow-ip = *.*.*.* max-messages = 2 concatenation = true group = sms-service keyword = default catch-all = true max-messages = 0 get-url = http://127.0.0.1/receive_sms?from=%qdate=%ttext=%b accepted-smsc = SMSC_01 group = smsbox-route smsc-id = SMSC_01 smsbox-id = sms_box group = ppg ppg-url = /wappush ppg-port = 8080 concurrent-pushes = 100 users = 1024 trusted-pi = true ppg-allow-ip = *.*.*.* ppg-smsbox-id = sms_box default-smsc = SMSC_01 group = wap-push-user ppg-username = tester ppg-password = foobar allow-ip = *.*.*.* default-smsc = SMSC_01 access.logs :: :: 2010-06-13 15:40:06 Log begins 2010-06-13 15:40:07 Log begins 2010-06-13 15:40:07 Log begins 2010-06-13 15:40:27 send-SMS request added - sender:tester:+49157 127.0.0.1 target:+49176 request: 'Das ist eine SMS' 2010-06-13 15:40:47 send-SMS request added - sender:tester:+49157 127.0.0.1 target:+49176 request: 'Das ist eine SMS' 2010-06-13 15:40:56 send-SMS request added - sender:tester:+49157 127.0.0.1 target:+49176 request: 'Das ist eine SMS' 2010-06-13 15:41:05 send-SMS request added - sender:tester:+49157 127.0.0.1 target:+49176 request: ' UDH ' 2010-06-13 15:41:24 send-SMS request added - sender:tester:+49157 127.0.0.1 target:+49176 request: ' UDH ' 2010-06-13 15:41:39 send-SMS request added - sender:tester:+49157 127.0.0.1 target:+49176 request: 'Das ist eine SMS' 2010-06-13 15:42:04 Sent SMS [SMSC:SMSC_01] [SVC:tester] [ACT:] [BINF:] [FID:] [from:+49157] [to:+49176] [flags:-1:0:-1:-1:-1] [msg:16:Das ist eine SMS] [udh:0:] 2010-06-13 15:42:11 Sent SMS [SMSC:SMSC_01] [SVC:tester] [ACT:] [BINF:] [FID:] [from:+49157] [to:+49176] [flags:-1:0:-1:-1:-1] [msg:16:Das ist eine SMS] [udh:0:] 2010-06-13 15:42:35 Sent SMS [SMSC:SMSC_01] [SVC:tester] [ACT:] [BINF:] [FID:] [from:+49157] [to:+49176] [flags:-1:1:-1:-1:-1] [msg:72:1B0601AE02056A0045C60C03626C61636B6C6973742E73656C6669702E6F72672F696E6465 782E776D6C000103446173206973742065696E206B6C65696E65722054657374000101] [udh:7:0605040B8423F0] 2010-06-13 15:42:43 Sent SMS [SMSC:SMSC_01] [SVC:tester] [ACT:] [BINF:] [FID:] [from:+49157] [to:+49176] [flags:-1:1:-1:-1:-1] [msg:72:1B0601AE02056A0045C60C03626C61636B6C6973742E73656C6669702E6F72672F696E64657 82E776D6C000103446173206973742065696E206B6C65696E65722054657374000101] [udh:7:0605040B8423F0] 2010-06-13 15:43:03 Sent SMS [SMSC:SMSC_01] [SVC:tester] [ACT:] [BINF:] [FID:]
Re: WAP-Push with Nokia 6210
Hi, I notice that you are using the sendsms interface to send PPG. If you don't use wapbox, you might as well comment it out in your configuration. Please update to latest svn and retry. If problem persists, patch attached diagnosrics, repeat and post those logs. BR, Nikos - Original Message - From: Thomas Sieh ts...@gmx.de To: Nikos Balkanas nbalka...@gmail.com Cc: Thomas Sieh ts...@gmx.de; users@kannel.org Sent: Sunday, June 13, 2010 5:59 PM Subject: Re: WAP-Push with Nokia 6210 Hi Nikos, I have done some more tests. the Problem is, that when I send the first message, it is stored in the queue, but will not be send. regardless if it is a wap push message or a normal mo push sms. the same with all other following messages. but then, for me not obviously, kannel sends a few seconds after the last message the most other messages in the queue, but not absolute all. mostly there are one or two left inside the queue. In summary I can say: kannel don't send the messages until one is accepted. but then kannel sends the most of the other messages, too. I sent the messages with the following 2 commands: lynx -dump http://localhost:13013/cgi-bin/sendsms?username=testerpassw ord=foobarfrom=%2B49157to=%2B49176smsc=SMSC_01text=D as+ist+eine+SMS lynx -dump http://localhost:13013/cgi-bin/sendsms?username=testerpassw ord=foobarfrom=%2B49157to=%2B49176udh=%06%05%04%0B%84 %23%F0smsc=SMSC_01text=%1B%06%01%AE%02%05%6A%00%45%C6%0C%03*.s elfip.org/index.wml%00%01%03Das+ist+ein+kleiner+Test%00%01%01 thanks in advance br, thomas following the full logs and the dependent config: config :: : # kannel.conf group = core admin-port = 13000 admin-password = genap status-password = genap admin-deny-ip = *.*.*.* admin-allow-ip = 127.0.0.1 log-file = /var/log/kannel/bearerbox.log log-level = 0 access-log = /var/log/kannel/access.log smsbox-port = 13001 wapbox-port = 13002 wdp-interface-name = * store-type = spool store-location = /var/spool/kannel group = smsc smsc-id = SMSC_01 smsc = at modemtype = nokiaphone speed = 9600 device = /dev/ttyUSB0 sms-center = +49177061 #keepalive = 20 log-file = /var/log/kannel/smsc.log log-level = 0 group = modems id = nokiaphone name = Nokia Phone detect-string = Nokia Mobile Phone need-sleep = true init-string = AT+CNMI=1,2,0,1,0;+CMEE=2 keepalive-cmd = AT+CBC;+CSQ enable-mms = true group = wapbox bearerbox-host = localhost log-file = /var/log/kannel/wapbox.log log-level = 0 access-log = /var/log/kannel/access.log syslog-level = none group = smsbox smsbox-id = sms_box bearerbox-host = localhost sendsms-port = 13013 sendsms-chars = 0123456789+ global-sender = +49157 log-file = /var/log/kannel/smsbox.log log-level = 0 access-log = /var/log/kannel/access.log sendsms-url = /cgi-bin/sendsms group = sendsms-user username = tester password = foobar user-allow-ip = *.*.*.* max-messages = 2 concatenation = true group = sms-service keyword = default catch-all = true max-messages = 0 get-url = http://127.0.0.1/receive_sms?from=%qdate=%ttext=%b accepted-smsc = SMSC_01 group = smsbox-route smsc-id = SMSC_01 smsbox-id = sms_box group = ppg ppg-url = /wappush ppg-port = 8080 concurrent-pushes = 100 users = 1024 trusted-pi = true ppg-allow-ip = *.*.*.* ppg-smsbox-id = sms_box default-smsc = SMSC_01 group = wap-push-user ppg-username = tester ppg-password = foobar allow-ip = *.*.*.* default-smsc = SMSC_01 access.logs :: :: 2010-06-13 15:40:06 Log begins 2010-06-13 15:40:07 Log begins 2010-06-13 15:40:07 Log begins 2010-06-13 15:40:27 send-SMS request added - sender:tester:+49157 127.0.0.1 target:+49176 request: 'Das ist eine SMS' 2010-06-13 15:40:47 send-SMS request added - sender:tester:+49157 127.0.0.1 target:+49176 request: 'Das ist eine SMS' 2010-06-13 15:40:56 send-SMS request added - sender:tester:+49157 127.0.0.1 target:+49176 request: 'Das ist eine SMS' 2010-06-13 15:41:05 send-SMS request added - sender:tester:+49157 127.0.0.1 target:+49176 request: ' UDH ' 2010-06-13 15:41:24 send-SMS request added - sender:tester:+49157 127.0.0.1 target:+49176 request: ' UDH ' 2010-06-13 15:41:39 send-SMS request added - sender:tester:+49157 127.0.0.1 target:+49176 request: 'Das ist eine SMS' 2010-06-13 15:42:04 Sent SMS [SMSC:SMSC_01] [SVC:tester] [ACT:] [BINF:] [FID:] [from:+49157] [to:+49176] [flags:-1:0:-1:-1:-1] [msg:16:Das ist eine SMS] [udh:0:] 2010-06-13 15:42:11 Sent SMS [SMSC:SMSC_01] [SVC:tester] [ACT:] [BINF:] [FID:] [from:+49157] [to:+49176] [flags:-1:0:-1:-1:-1] [msg:16:Das ist eine SMS] [udh:0:] 2010-06-13 15:42:35 Sent SMS [SMSC:SMSC_01] [SVC:tester] [ACT:] [BINF:] [FID:] [from:+49157] [to:+49176] [flags:-1:1:-1:-1:-1] [msg:72:1B0601AE02056A0045C60C03626C61636B6C6973742E73656C6669702E6F72672F696E6465
Re: WAP-Push with Nokia 6210
Hi, A couple of questions. 1) Seems that eventually SMS is sent after 3' or so from access logs. Yet I see resend_tries up to 58, or 29'. Is the SMS ever sent? 2) Please patch additional debug msg attached. 3) Compare smsc.log ERROR times with NIKOS!!! Sent SMS, result: from bb logs. They should match absolutely. Kannel works fine. Problem is with your modem. Post detailed smsc logs of failures and successes for a single SMS with the problem. PS: In the end either download a fresh svn, or remember to edit gw/bb_smscconn.c and gw/bb_box.c and delete all references to NIKOS!!! BR, Nikos - Original Message - From: Thomas Sieh ts...@gmx.de To: Nikos Balkanas nbalka...@gmail.com Cc: ts...@gmx.de; users@kannel.org Sent: Monday, June 14, 2010 5:47 AM Subject: Re: WAP-Push with Nokia 6210 Hi Nikos, i tried it with the newest version from repository, but the same thing. i have the wapbox in the config because i have a script whit whom i send wap push sms. i only used the url-method to be sure the failure is not caused by my script. but if the server works with this method and not with my script, i'll write a new one :) after this test there is one more time one message still in the queue and will keep there until some other happenings. LATER UPDATE: 1 hour later it sends the last message, too. I have sent the complete log. hope its not too much :-/ thanks again for your help! i have patched kannel with your file and here are the new logs... [..snip..] bb_boxc.diff Description: Binary data
Re: WAP-Push with Nokia 6210
hi,
thank you for your interrest. Here are my logs again, beginning at the
point when I have sent the message. Posting regular messages is no problem.
The PAP- and SI-file are generated in the send_wappush2.php script (see
below).
br,
thomas
-send_wappush2.php---
craetes pap and si and sends it to the ppg
?
// send_wappush2.php
//require config.php;
$phone = '+49176'; // receiver
$push_url = 'http://wap.google.com';
$text = 'This is a test';
$smsc_id= 'SMSC_01';
send_wap_push($smsc_id, $phone, $push_url, $text);
function send_wap_push($smsc_id, $phone, $push_url, $text)
{
$host = 'localhost';
$port = '8080';
$url = http://.$host.:.$port;
//$ppg_user = 'testy';
//$ppg_pass = 'foobar';
$wap_push_id = time(); //pushID-.$phone.-.time();
$nl = \r\n;
$body = '--multipart-boundary'.$nl.
'Content-type: application/xml'.$nl.$nl.
'?xml version=1.0?'.$nl.
'!DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP 1.0//EN
http://www.wapforum.org/DTD/pap_1.0.dtd; '.$nl.
'pap'.$nl.
'push-message push-id='.$wap_push_id.''.$nl.
'address address-value=WAPPUSH='.$phone.'/type=p...@localhost/'.$nl.
'quality-of-service priority=high delivery-method=unconfirmed
network-required=true network=GSM bearer-required=true
bearer=SMS/'.$nl.
'/push-message'.$nl.
'/pap'.$nl.$nl.
'--multipart-boundary'.$nl.
'Content-type: text/vnd.wap.si'.$nl.$nl.
'?xml version=1.0?'.$nl.
'!DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//EN
http://www.wapforum.org/DTD/si.dtd;'.$nl.
'si'.$nl.
'indication action=signal-high si-id='.$wap_push_id.'
href='.$push_url.''.$text.'/indication'.$nl.
'/si'.$nl.
'--multipart-boundary--'.$nl;
$post = 'POST /wappush HTTP/1.1'.$nl.
'Host: '.$host.':'.$port.$nl.
//Authorization: Basic .base64_encode($ppg_user:$ppg_pass).$nl.
'X-Kannel-SMSC: '.$smsc_id.$nl.
'X-Kannel-Smsbox-Id: sms_box'.$nl.
'Content-Type: multipart/related; boundary=multipart-boundary;
type=application/xml'.$nl.
'Content-Length: '.strlen($body).$nl.$nl.
$body;
$ch = curl_init();
curl_setopt ($ch, CURLOPT_URL, $url);
curl_setopt($ch, CURLOPT_HEADER, 1);
curl_setopt($ch, CURLOPT_TIMEOUT, 30);
curl_setopt ($ch,CURLOPT_CUSTOMREQUEST , $post);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$reply = curl_exec($ch);
curl_close ($ch);
//print_r($reply. .$wap_push_id);
}
?
-
---wapbox
2010-06-12 10:53:13 [20219] [11] DEBUG: HTTP: Creating HTTPClient for
`127.0.0.1'.
2010-06-12 10:53:13 [20219] [11] DEBUG: HTTP: Created HTTPClient area 0x1b3ee90.
2010-06-12 10:53:13 [20219] [14] INFO: PPG: Accept request /wappush from
127.0.0.1
2010-06-12 10:53:13 [20219] [14] DEBUG: PPG: http_read_thread: pap multipart
accepted
2010-06-12 10:53:13 [20219] [14] INFO: client address was +49176,
accepted
2010-06-12 10:53:13 [20219] [14] DEBUG: PAP COMPILER: doing semantic analysis
for address type a phone number
2010-06-12 10:53:13 [20219] [14] DEBUG: using defaults instead of anys
2010-06-12 10:53:13 [20219] [14] DEBUG: PPG: http_read_thread: pap control
entity compiled ok
2010-06-12 10:53:13 [20219] [14] DEBUG: PPG: transform_message: push message
content and headers valid
2010-06-12 10:53:13 [20219] [14] DEBUG: PPG: push machine 0 created
2010-06-12 10:53:13 [20219] [14] DEBUG: PPG: store_push_data: push machine 0
appended to unit push list
2010-06-12 10:53:13 [20219] [14] DEBUG: PPG: send_push_response: telling pi
2010-06-12 10:53:13 [20219] [14] DEBUG: HTTP: Resetting HTTPClient for
`127.0.0.1'.
2010-06-12 10:53:13 [20219] [14] INFO: PPG: handle_push_message: push message
accepted for processing
2010-06-12 10:53:13 [20219] [14] DEBUG: PPG: OTA request for unit push
2010-06-12 10:53:13 [20219] [14] INFO: PPG: unconfirmed push delivered to OTA
2010-06-12 10:53:13 [20219] [14] DEBUG: PPG: destroying push machine 0
2010-06-12 10:53:13 [20219] [9] DEBUG: OTA: event arrived
2010-06-12 10:53:13 [20219] [9] DEBUG: OTA: made connectionless session service
request
2010-06-12 10:53:13 [20219] [2] DEBUG: WSP (UNIT): event arrived
2010-06-12 10:53:13 [20219] [2] DEBUG: WSP_UNIT: Connectionless push accepted
2010-06-12 10:53:13 [20219] [2] DEBUG: WSP: Mapping `application/vnd.wap.sic',
WSP 1.2 to 0x002e.
2010-06-12 10:53:13 [20219] [2] DEBUG: WSP: Mapping `Content-Length', WSP 1.3
to 0x000d.
2010-06-12 10:53:13 [20219] [2] DEBUG: WSP: Mapping `Content-Type', WSP 1.3 to
0x0011.
2010-06-12 10:53:13 [20219] [2] DEBUG: WSP: Mapping `Encoding-Version', WSP 1.3
to 0x0043.
2010-06-12 10:53:13 [20219] [2] DEBUG: WDP (wapbox): delivering 1 segments to
bearerbox
2010-06-12 10:53:13 [20219] [2] DEBUG: WSP (UNIT): delivering to wdp
2010-06-12 10:53:13 [20219] [0] WARNING: Received other message than wdp/admin,
ignoring!
2010-06-12
Re: WAP-Push with Nokia 6210
Sorry, i am NOT able to send normal SMS.
Re: WAP-Push with Nokia 6210
None? I thought you said only the first one gets queued. Also do not snip responses. Need to have the whole story. Nikos - Original Message - From: Thomas Sieh ts...@gmx.de To: Thomas Sieh ts...@gmx.de Cc: Nikos Balkanas nbalka...@gmail.com; users@kannel.org Sent: Saturday, June 12, 2010 2:50 PM Subject: Re: WAP-Push with Nokia 6210 Sorry, i am NOT able to send normal SMS.
Re: WAP-Push with Nokia 6210
additional information: if there is more than one message in the queue, kannel will send the later one directly. the older one is still in the queue. and if i send some more wap push sms, kannel sends them all. but generaly i don't send as much sms, so it is not a solution :-/ On Sat, Jun 12, 2010 at 02:37:56AM +0200, Thomas Sieh wrote: | hi, | | i use a nokia 6210 as smsc. when i try to send a wap push sms, i get a | generic error. the strange thing is that the message will be send | after a restart of kannel. before that it don't leave the queue. | | have someone of you an idea what could be wrong? | | thx | thomas | | | here my conf and the logs... | | SMSC: | . | | 2010-06-12 02:09:30 [23967] [6] DEBUG: AT2[SMSC_01]: -- AT+CBC;+CSQ^M | 2010-06-12 02:09:30 [23967] [6] DEBUG: AT2[SMSC_01]: -- +CBC: 1,50 | 2010-06-12 02:09:30 [23967] [6] DEBUG: AT2[SMSC_01]: -- +CSQ: 31,99 | 2010-06-12 02:09:30 [23967] [6] DEBUG: AT2[SMSC_01]: -- OK | 2010-06-12 02:09:40 [23967] [6] DEBUG: AT2[SMSC_01]: TP-Validity-Period: | 24.0 hours | 2010-06-12 02:09:40 [23967] [6] DEBUG: AT2[SMSC_01]: -- AT+CMGS=86^M | 2010-06-12 02:09:40 [23967] [6] DEBUG: AT2[SMSC_01]: -- | 2010-06-12 02:09:40 [23967] [6] DEBUG: AT2[SMSC_01]: -- | 2010-06-12 02:09:40 [23967] [6] DEBUG: AT2[SMSC_01]: send command status: 1 | 2010-06-12 02:09:40 [23967] [6] DEBUG: AT2[SMSC_01]: -- 0051000D919471 | 2010-06-12 02:09:40 [23967] [6] DEBUG: AT2[SMSC_01]: -- F60004A7470605 | 2010-06-12 02:09:40 [23967] [6] DEBUG: AT2[SMSC_01]: -- 040B8423F605AE | 2010-06-12 02:09:40 [23967] [6] DEBUG: AT2[SMSC_01]: -- 8DB8C39302056A0045 | 2010-06-12 02:09:40 [23967] [6] DEBUG: AT2[SMSC_01]: -- C60811033132373633 | 2010-06-12 02:09:40 [23967] [6] DEBUG: AT2[SMSC_01]: -- 3031333739000C0377 | 2010-06-12 02:09:40 [23967] [6] DEBUG: AT2[SMSC_01]: -- 61702E676F6F676C65 | 2010-06-12 02:09:40 [23967] [6] DEBUG: AT2[SMSC_01]: -- 2E636F6D0001035468 | 2010-06-12 02:09:40 [23967] [6] DEBUG: AT2[SMSC_01]: -- 697320697320612074 | 2010-06-12 02:09:41 [23967] [6] DEBUG: AT2[SMSC_01]: -- 657374000101 | 2010-06-12 02:09:41 [23967] [6] DEBUG: AT2[SMSC_01]: -- ERROR | 2010-06-12 02:09:41 [23967] [6] ERROR: AT2[SMSC_01]: Generic error: ERROR | 2010-06-12 02:09:41 [23967] [6] DEBUG: AT2[SMSC_01]: send command status: -1 | 2010-06-12 02:10:03 [23967] [6] DEBUG: AT2[SMSC_01]: -- AT+CBC;+CSQ^M | 2010-06-12 02:10:03 [23967] [6] DEBUG: AT2[SMSC_01]: -- +CBC: 1,50 | 2010-06-12 02:10:03 [23967] [6] DEBUG: AT2[SMSC_01]: -- +CSQ: 31,99 | 2010-06-12 02:10:03 [23967] [6] DEBUG: AT2[SMSC_01]: -- OK | | wapbox: | ... | | 2010-06-12 02:09:39 [24026] [14] INFO: PPG: Accept request /wappush from 127.0.0.1 | 2010-06-12 02:09:39 [24026] [14] DEBUG: PPG: http_read_thread: pap multipart accepted | 2010-06-12 02:09:39 [24026] [14] INFO: client address was +49176, accepted | 2010-06-12 02:09:39 [24026] [14] DEBUG: PAP COMPILER: doing semantic analysis for address type a phone number | 2010-06-12 02:09:39 [24026] [14] DEBUG: using defaults instead of anys | 2010-06-12 02:09:39 [24026] [14] DEBUG: PPG: http_read_thread: pap control entity compiled ok | 2010-06-12 02:09:39 [24026] [14] DEBUG: PPG: transform_message: push message content and headers valid | 2010-06-12 02:09:39 [24026] [14] DEBUG: PPG: push machine 0 created | 2010-06-12 02:09:39 [24026] [14] DEBUG: PPG: store_push_data: push machine 0 appended to unit push list | 2010-06-12 02:09:39 [24026] [14] DEBUG: PPG: send_push_response: telling pi | 2010-06-12 02:09:39 [24026] [14] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'. | 2010-06-12 02:09:39 [24026] [14] INFO: PPG: handle_push_message: push message accepted for processing | 2010-06-12 02:09:39 [24026] [14] DEBUG: PPG: OTA request for unit push | 2010-06-12 02:09:39 [24026] [14] INFO: PPG: unconfirmed push delivered to OTA | 2010-06-12 02:09:39 [24026] [14] DEBUG: PPG: destroying push machine 0 | 2010-06-12 02:09:39 [24026] [9] DEBUG: OTA: event arrived | 2010-06-12 02:09:39 [24026] [9] DEBUG: OTA: made connectionless session service request | 2010-06-12 02:09:39 [24026] [2] DEBUG: WSP (UNIT): event arrived | 2010-06-12 02:09:39 [24026] [2] DEBUG: WSP_UNIT: Connectionless push accepted | 2010-06-12 02:09:39 [24026] [2] DEBUG: WSP: Mapping `application/vnd.wap.sic', WSP 1.2 to 0x002e. | 2010-06-12 02:09:39 [24026] [2] DEBUG: WSP: Mapping `Content-Length', WSP 1.3 to 0x000d. | 2010-06-12 02:09:39 [24026] [2] DEBUG: WSP: Mapping `Content-Type', WSP 1.3 to 0x0011. | 2010-06-12 02:09:39 [24026] [2] DEBUG: WSP: Mapping `Encoding-Version', WSP 1.3 to 0x0043. | 2010-06-12 02:09:39 [24026] [2] DEBUG: WDP (wapbox): delivering 1 segments to bearerbox | 2010-06-12 02:09:39 [24026] [2] DEBUG: WSP (UNIT): delivering to wdp | 2010-06-12 02:09:39 [24026] [0] WARNING: Received other message than wdp/admin, ignoring! | 2010-06-12 02:09:39 [24026] [10] DEBUG: HTTP: Destroying HTTPClient area 0x272a8e0. | 2010-06-12 02:09:39 [24026] [10] DEBUG: HTTP:
Re: WAP-Push with Nokia 6210
Hi, Can you post regular messages? It is extremely difficult to help you in a threaded environment, since attachments are not preserved in responses. Please: 1) Repost original logs inline (not as attachments) 2) Post PAP and SI documents 3) Post detailed bb logs from the moment of first submission (with failed route command) BR, Nikos - Original Message - From: Thomas Sieh ts...@gmx.de To: Thomas Sieh ts...@gmx.de Cc: users@kannel.org Sent: Saturday, June 12, 2010 4:49 AM Subject: Re: WAP-Push with Nokia 6210
Re: WAP-Push with Nokia 6210 as SMSC
Hi @all again, I found the mistake by myself... keepalive = true is not a valid value. After changing to 5 it works fine. How stupid :) Thanks Thomas On Sun, May 23, 2010 at 08:41:15PM +0200, Thomas Sieh wrote: | Hi @all, | | I have got a Nokia 6210 as SMSC. When I send a WAP Push message to the | PPG I get a unforseeable number of Generic Errors - up to 30 - and then | it will send the message successfully. What could be the Problem? | I have tryed already to change sleep-times and other modem options | without success. | | BR, | Thomas | | The error messages: | ... | 2010-05-23 20:18:31 [11694] [6] DEBUG: AT2[SMSC_01]: send command status: 1 | 2010-05-23 20:18:31 [11694] [6] DEBUG: AT2[SMSC_01]: --0051000D9194714669 | 2010-05-23 20:18:31 [11694] [6] DEBUG: AT2[SMSC_01]: --4494F60004A74F0605 | 2010-05-23 20:18:31 [11694] [6] DEBUG: AT2[SMSC_01]: --040B8423F605AE | 2010-05-23 20:18:31 [11694] [6] DEBUG: AT2[SMSC_01]: --8DC0C39302056A0045 | 2010-05-23 20:18:31 [11694] [6] DEBUG: AT2[SMSC_01]: --C60811033132373436 | 2010-05-23 20:18:31 [11694] [6] DEBUG: AT2[SMSC_01]: --3337333837000C0377 | 2010-05-23 20:18:31 [11694] [6] DEBUG: AT2[SMSC_01]: --61702E676F6F676C65 | 2010-05-23 20:18:31 [11694] [6] DEBUG: AT2[SMSC_01]: --2E636F6D0001035468 | 2010-05-23 20:18:31 [11694] [6] DEBUG: AT2[SMSC_01]: --697320697320612066 | 2010-05-23 20:18:32 [11694] [6] DEBUG: AT2[SMSC_01]: --75636B696E67207465 | 2010-05-23 20:18:32 [11694] [6] DEBUG: AT2[SMSC_01]: -- 7374000101 | 2010-05-23 20:18:32 [11694] [6] DEBUG: AT2[SMSC_01]: -- | 2010-05-23 20:18:32 [11694] [6] DEBUG: AT2[SMSC_01]: -- ERROR | 2010-05-23 20:18:32 [11694] [6] ERROR: AT2[SMSC_01]: Generic error: ERROR | 2010-05-23 20:18:32 [11694] [6] DEBUG: AT2[SMSC_01]: send command status: -1 | 2010-05-23 20:19:34 [11694] [6] DEBUG: AT2[SMSC_01]: TP-Validity-Period: 24.0 hours | 2010-05-23 20:19:34 [11694] [6] DEBUG: AT2[SMSC_01]: -- AT+CMGS=94^M | 2010-05-23 20:19:34 [11694] [6] DEBUG: AT2[SMSC_01]: -- | 2010-05-23 20:19:34 [11694] [6] DEBUG: AT2[SMSC_01]: send command status: 1 | 2010-05-23 20:19:34 [11694] [6] DEBUG: AT2[SMSC_01]: --0051000D9194714669 | 2010-05-23 20:19:34 [11694] [6] DEBUG: AT2[SMSC_01]: --4494F60004A74F0605 | 2010-05-23 20:19:34 [11694] [6] DEBUG: AT2[SMSC_01]: --040B8423F605AE | 2010-05-23 20:19:34 [11694] [6] DEBUG: AT2[SMSC_01]: --8DC0C39302056A0045 | 2010-05-23 20:19:34 [11694] [6] DEBUG: AT2[SMSC_01]: --C60811033132373436 | 2010-05-23 20:19:34 [11694] [6] DEBUG: AT2[SMSC_01]: --3337333837000C0377 | 2010-05-23 20:19:34 [11694] [6] DEBUG: AT2[SMSC_01]: --61702E676F6F676C65 | 2010-05-23 20:19:34 [11694] [6] DEBUG: AT2[SMSC_01]: --2E636F6D0001035468 | 2010-05-23 20:19:34 [11694] [6] DEBUG: AT2[SMSC_01]: --697320697320612066 | 2010-05-23 20:19:35 [11694] [6] DEBUG: AT2[SMSC_01]: --75636B696E67207465 | 2010-05-23 20:19:35 [11694] [6] DEBUG: AT2[SMSC_01]: -- 7374000101 | 2010-05-23 20:19:35 [11694] [6] DEBUG: AT2[SMSC_01]: -- | 2010-05-23 20:19:35 [11694] [6] DEBUG: AT2[SMSC_01]: -- ERROR | 2010-05-23 20:19:35 [11694] [6] ERROR: AT2[SMSC_01]: Generic error: ERROR | 2010-05-23 20:19:35 [11694] [6] DEBUG: AT2[SMSC_01]: send command status: -1 | 2010-05-23 20:20:37 [11694] [6] DEBUG: AT2[SMSC_01]: TP-Validity-Period: 24.0 hours | 2010-05-23 20:20:37 [11694] [6] DEBUG: AT2[SMSC_01]: -- AT+CMGS=94^M | 2010-05-23 20:20:37 [11694] [6] DEBUG: AT2[SMSC_01]: -- | 2010-05-23 20:20:37 [11694] [6] DEBUG: AT2[SMSC_01]: -- | 2010-05-23 20:20:37 [11694] [6] DEBUG: AT2[SMSC_01]: send command status: 1 | 2010-05-23 20:20:37 [11694] [6] DEBUG: AT2[SMSC_01]: --0051000D9194714669 | 2010-05-23 20:20:37 [11694] [6] DEBUG: AT2[SMSC_01]: --4494F60004A74F0605 | 2010-05-23 20:20:37 [11694] [6] DEBUG: AT2[SMSC_01]: --040B8423F605AE | 2010-05-23 20:20:37 [11694] [6] DEBUG: AT2[SMSC_01]: --8DC0C39302056A0045 | 2010-05-23 20:20:37 [11694] [6] DEBUG: AT2[SMSC_01]: --C60811033132373436 | 2010-05-23 20:20:37 [11694] [6] DEBUG: AT2[SMSC_01]: --3337333837000C0377 | 2010-05-23 20:20:37 [11694] [6] DEBUG: AT2[SMSC_01]: --61702E676F6F676C65 | 2010-05-23 20:20:37 [11694] [6] DEBUG: AT2[SMSC_01]: --2E636F6D0001035468 | 2010-05-23 20:20:37 [11694] [6] DEBUG: AT2[SMSC_01]: --697320697320612066 | 2010-05-23 20:20:38 [11694] [6] DEBUG: AT2[SMSC_01]: --75636B696E67207465 | 2010-05-23 20:20:38 [11694] [6] DEBUG: AT2[SMSC_01]: -- 7374000101 | 2010-05-23 20:20:43 [11694] [6] DEBUG: AT2[SMSC_01]: -- +CMGS: 36 | 2010-05-23 20:20:43 [11694] [6] DEBUG: AT2[SMSC_01]: -- OK | 2010-05-23 20:20:43 [11694] [6] DEBUG: AT2[SMSC_01]: send command status: 0 | | | My Configuration: | | group = smsc | smsc-id = SMSC_01 | smsc = at | modemtype = nokiaphone | speed = 19200 | device = /dev/ttyUSB0 | sms-center = +49177061 | my-number = +491577xx | log-file = /var/log/kannel/smsc.log | log-level = 0 | keepalive = true | | group = modems | id = nokiaphone | name = Nokia Phone | detect-string = Nokia Mobile Phone | #need-sleep = true | #sendline-sleep = 1000 | init-string =
Re: wap push alert
hii alll, im new in wap_push ..i send sms succefully from kannel..but i can use it as wap gateway...after saerching finally i can configure my kannel to send wap push ...the problem that i can understand the pap xml . exactely 1* what do you mean by TYPE=IPv4 at ppg.carrier.com ? and has this any relation with the operator or the type of mobile. ps: the error that i get from the file log bearer missing thankss for your help
Re: wap push alert
Hi, Please do not report what log says, just paste relevant detailed lines from log, with context. Also read User's guide to learn about PPG pap variables. BR, Nikos - Original Message - From: sisi85 rabeb.ab...@gmail.com To: users@kannel.org Sent: Wednesday, May 19, 2010 2:50 PM Subject: Re: wap push alert hii alll, im new in wap_push ..i send sms succefully from kannel..but i can use it as wap gateway...after saerching finally i can configure my kannel to send wap push ...the problem that i can understand the pap xml . exactely 1* what do you mean by TYPE=IPv4 at ppg.carrier.com ? and has this any relation with the operator or the type of mobile. ps: the error that i get from the file log bearer missing thankss for your help
Re: wap push to midlet
Hi, Sorry, but the SMS is exactly like wap push. In fact, wap push is sent over as SMS. But you have to watch to have the correct udh and wbxml encoding. If not, it won't show up. Of course the major issue is your middlet. This is something you have done, and we cannot debug it for you. To see if your wap push works, test it as a normal push first (don't change ports). Your mobile has to have pushes enabled. BR, Nikos - Original Message - From: Henri Hovi To: Rajeev Agarwal Cc: Nikos Balkanas ; users@kannel.org Sent: Wednesday, December 16, 2009 8:52 AM Subject: Re: wap push to midlet The SMS is just signaling that the application should start, so it's not like traditional WAP Push. Some devices just starts automatically, I have seen only Nokia requesting user to confirm the start. So in other cases, there would be no case to even display the message. -- Henri On Wed, Dec 16, 2009 at 5:06 AM, Rajeev Agarwal rajeev.agarw...@gmail.com wrote: The thing that i am doing right now is changing the destination port in the UDH to 40AB (16555 in decimal). 40AB is also the midlet port. When the phone receives the msg, the midlet gets activated. But i does not display the actual text that i have in the form of an encoded URL, as shown below http://xxx.xxx.x.xxx:15015/cgi-bin/sendsms?username=testerpassword=foobarto=xxudh=%06%05%04%40%AB%23%F0text=%FF%06%01%AE%02%05%6A%00%45%C6%0C%03%77%77%77%2e%67%6f%6f%67%6c%65%2e%63%6f%2e%69%6e%2f%6d%6f%62%69%6c%65%00%01%03%57%65%6c%63%6f%6d%65%20%74%6f%20%47%6f%6f%67%6c%65%00%01%01% Any thoughts on this??.. Thanks. 2009/12/15 Nikos Balkanas n...@amdtelecom.net Hi, Wap push is at a predefined port. You cannot change it through UDH headers in wapbox. Wapbox doesn't support UDH. But you can do it through smsbox (as suggested by Henri). BR, Nikos - Original Message - From: Henri Hovi To: Rajeev Agarwal Cc: users@kannel.org Sent: Tuesday, December 15, 2009 2:36 PM Subject: Re: wap push to midlet No need to use wap push, just SMS with UDH -- Henri On Tue, Dec 15, 2009 at 2:27 PM, Rajeev Agarwal rajeev.agarw...@gmail.com wrote: hi!! I've changed the udh destination port according to my midlet port. But wen i use the encoded url for wap push it does not get displayed. i get some error!..has anyone tried this before? pls help! regards rajeev. -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com
Re: wap push to midlet
Well, when I send the SMS to start the application by using middlet push registry service, i just send an empty SMS to the port on the device which is configured for the middlet in JAD. So I don't consired it as a wap push. -- H 2009/12/16 Nikos Balkanas n...@amdtelecom.net Hi, Sorry, but the SMS is exactly like wap push. In fact, wap push is sent over as SMS. But you have to watch to have the correct udh and wbxml encoding. If not, it won't show up. Of course the major issue is your middlet. This is something you have done, and we cannot debug it for you. To see if your wap push works, test it as a normal push first (don't change ports). Your mobile has to have pushes enabled. BR, Nikos - Original Message - *From:* Henri Hovi henri.h...@patidure.com *To:* Rajeev Agarwal rajeev.agarw...@gmail.com *Cc:* Nikos Balkanas n...@amdtelecom.net ; users@kannel.org *Sent:* Wednesday, December 16, 2009 8:52 AM *Subject:* Re: wap push to midlet The SMS is just signaling that the application should start, so it's not like traditional WAP Push. Some devices just starts automatically, I have seen only Nokia requesting user to confirm the start. So in other cases, there would be no case to even display the message. -- Henri On Wed, Dec 16, 2009 at 5:06 AM, Rajeev Agarwal rajeev.agarw...@gmail.com wrote: The thing that i am doing right now is changing the destination port in the UDH to 40AB (16555 in decimal). 40AB is also the midlet port. When the phone receives the msg, the midlet gets activated. But i does not display the actual text that i have in the form of an encoded URL, as shown below http://xxx.xxx.x.xxx:15015/cgi-bin/sendsms?username=testerpassword=foobarto=xxudh= %06%05%04%40%AB%23%F0 text=%FF%06%01%AE%02%05%6A%00%45%C6%0C%03%77%77%77%2e%67%6f%6f%67%6c%65%2e%63%6f%2e%69%6e%2f%6d%6f%62%69%6c%65%00%01%03%57%65%6c%63%6f%6d%65%20%74%6f%20%47%6f%6f%67%6c%65%00%01%01% Any thoughts on this??.. Thanks. 2009/12/15 Nikos Balkanas n...@amdtelecom.net Hi, Wap push is at a predefined port. You cannot change it through UDH headers in wapbox. Wapbox doesn't support UDH. But you can do it through smsbox (as suggested by Henri). BR, Nikos - Original Message - *From:* Henri Hovi henri.h...@patidure.com *To:* Rajeev Agarwal rajeev.agarw...@gmail.com *Cc:* users@kannel.org *Sent:* Tuesday, December 15, 2009 2:36 PM *Subject:* Re: wap push to midlet No need to use wap push, just SMS with UDH -- Henri On Tue, Dec 15, 2009 at 2:27 PM, Rajeev Agarwal rajeev.agarw...@gmail.com wrote: hi!! I've changed the udh destination port according to my midlet port. But wen i use the encoded url for wap push it does not get displayed. i get some error!..has anyone tried this before? pls help! regards rajeev. -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com
Re: wap push to midlet
Hi, I don't know what you are doing with your middlet. That's your business. But 06 in udh header means wap push protocol, and wbxml body is from wap push specs. This is still a wap push to a different port, and it is send over SMS. BR, Nikos - Original Message - From: Henri Hovi To: Nikos Balkanas Cc: users@kannel.org Sent: Wednesday, December 16, 2009 11:15 AM Subject: Re: wap push to midlet Well, when I send the SMS to start the application by using middlet push registry service, i just send an empty SMS to the port on the device which is configured for the middlet in JAD. So I don't consired it as a wap push. -- H 2009/12/16 Nikos Balkanas n...@amdtelecom.net Hi, Sorry, but the SMS is exactly like wap push. In fact, wap push is sent over as SMS. But you have to watch to have the correct udh and wbxml encoding. If not, it won't show up. Of course the major issue is your middlet. This is something you have done, and we cannot debug it for you. To see if your wap push works, test it as a normal push first (don't change ports). Your mobile has to have pushes enabled. BR, Nikos - Original Message - From: Henri Hovi To: Rajeev Agarwal Cc: Nikos Balkanas ; users@kannel.org Sent: Wednesday, December 16, 2009 8:52 AM Subject: Re: wap push to midlet The SMS is just signaling that the application should start, so it's not like traditional WAP Push. Some devices just starts automatically, I have seen only Nokia requesting user to confirm the start. So in other cases, there would be no case to even display the message. -- Henri On Wed, Dec 16, 2009 at 5:06 AM, Rajeev Agarwal rajeev.agarw...@gmail.com wrote: The thing that i am doing right now is changing the destination port in the UDH to 40AB (16555 in decimal). 40AB is also the midlet port. When the phone receives the msg, the midlet gets activated. But i does not display the actual text that i have in the form of an encoded URL, as shown below http://xxx.xxx.x.xxx:15015/cgi-bin/sendsms?username=testerpassword=foobarto=xxudh=%06%05%04%40%AB%23%F0text=%FF%06%01%AE%02%05%6A%00%45%C6%0C%03%77%77%77%2e%67%6f%6f%67%6c%65%2e%63%6f%2e%69%6e%2f%6d%6f%62%69%6c%65%00%01%03%57%65%6c%63%6f%6d%65%20%74%6f%20%47%6f%6f%67%6c%65%00%01%01% Any thoughts on this??.. Thanks. 2009/12/15 Nikos Balkanas n...@amdtelecom.net Hi, Wap push is at a predefined port. You cannot change it through UDH headers in wapbox. Wapbox doesn't support UDH. But you can do it through smsbox (as suggested by Henri). BR, Nikos - Original Message - From: Henri Hovi To: Rajeev Agarwal Cc: users@kannel.org Sent: Tuesday, December 15, 2009 2:36 PM Subject: Re: wap push to midlet No need to use wap push, just SMS with UDH -- Henri On Tue, Dec 15, 2009 at 2:27 PM, Rajeev Agarwal rajeev.agarw...@gmail.com wrote: hi!! I've changed the udh destination port according to my midlet port. But wen i use the encoded url for wap push it does not get displayed. i get some error!..has anyone tried this before? pls help! regards rajeev. -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com
Re: wap push to midlet
if i dont use the midlet, the whoel thing is working perfectly fine!!!.. i know, there is some problem with the midlet!.. 2009/12/16 Nikos Balkanas nbalka...@gmail.com Hi, I don't know what you are doing with your middlet. That's your business. But 06 in udh header means wap push protocol, and wbxml body is from wap push specs. This is still a wap push to a different port, and it is send over SMS. BR, Nikos - Original Message - *From:* Henri Hovi henri.h...@patidure.com *To:* Nikos Balkanas n...@amdtelecom.net *Cc:* users@kannel.org *Sent:* Wednesday, December 16, 2009 11:15 AM *Subject:* Re: wap push to midlet Well, when I send the SMS to start the application by using middlet push registry service, i just send an empty SMS to the port on the device which is configured for the middlet in JAD. So I don't consired it as a wap push. -- H 2009/12/16 Nikos Balkanas n...@amdtelecom.net Hi, Sorry, but the SMS is exactly like wap push. In fact, wap push is sent over as SMS. But you have to watch to have the correct udh and wbxml encoding. If not, it won't show up. Of course the major issue is your middlet. This is something you have done, and we cannot debug it for you. To see if your wap push works, test it as a normal push first (don't change ports). Your mobile has to have pushes enabled. BR, Nikos - Original Message - *From:* Henri Hovi henri.h...@patidure.com *To:* Rajeev Agarwal rajeev.agarw...@gmail.com *Cc:* Nikos Balkanas n...@amdtelecom.net ; users@kannel.org *Sent:* Wednesday, December 16, 2009 8:52 AM *Subject:* Re: wap push to midlet The SMS is just signaling that the application should start, so it's not like traditional WAP Push. Some devices just starts automatically, I have seen only Nokia requesting user to confirm the start. So in other cases, there would be no case to even display the message. -- Henri On Wed, Dec 16, 2009 at 5:06 AM, Rajeev Agarwal rajeev.agarw...@gmail.com wrote: The thing that i am doing right now is changing the destination port in the UDH to 40AB (16555 in decimal). 40AB is also the midlet port. When the phone receives the msg, the midlet gets activated. But i does not display the actual text that i have in the form of an encoded URL, as shown below http://xxx.xxx.x.xxx:15015/cgi-bin/sendsms?username=testerpassword=foobarto=xxudh= %06%05%04%40%AB%23%F0 text=%FF%06%01%AE%02%05%6A%00%45%C6%0C%03%77%77%77%2e%67%6f%6f%67%6c%65%2e%63%6f%2e%69%6e%2f%6d%6f%62%69%6c%65%00%01%03%57%65%6c%63%6f%6d%65%20%74%6f%20%47%6f%6f%67%6c%65%00%01%01% Any thoughts on this??.. Thanks. 2009/12/15 Nikos Balkanas n...@amdtelecom.net Hi, Wap push is at a predefined port. You cannot change it through UDH headers in wapbox. Wapbox doesn't support UDH. But you can do it through smsbox (as suggested by Henri). BR, Nikos - Original Message - *From:* Henri Hovi henri.h...@patidure.com *To:* Rajeev Agarwal rajeev.agarw...@gmail.com *Cc:* users@kannel.org *Sent:* Tuesday, December 15, 2009 2:36 PM *Subject:* Re: wap push to midlet No need to use wap push, just SMS with UDH -- Henri On Tue, Dec 15, 2009 at 2:27 PM, Rajeev Agarwal rajeev.agarw...@gmail.com wrote: hi!! I've changed the udh destination port according to my midlet port. But wen i use the encoded url for wap push it does not get displayed. i get some error!..has anyone tried this before? pls help! regards rajeev. -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com
Re: wap push to midlet
When the midlet receives the notification from push registry, how do you capture the body of the WAP Push? Based on my knowledge,it just notifies the midlet to be executed and not forward any information for it from the message. Of course, could be that I have missed some part from the docs... -- H On Wed, Dec 16, 2009 at 11:31 AM, Rajeev Agarwal rajeev.agarw...@gmail.comwrote: if i dont use the midlet, the whoel thing is working perfectly fine!!!.. i know, there is some problem with the midlet!.. 2009/12/16 Nikos Balkanas nbalka...@gmail.com Hi, I don't know what you are doing with your middlet. That's your business. But 06 in udh header means wap push protocol, and wbxml body is from wap push specs. This is still a wap push to a different port, and it is send over SMS. BR, Nikos - Original Message - *From:* Henri Hovi henri.h...@patidure.com *To:* Nikos Balkanas n...@amdtelecom.net *Cc:* users@kannel.org *Sent:* Wednesday, December 16, 2009 11:15 AM *Subject:* Re: wap push to midlet Well, when I send the SMS to start the application by using middlet push registry service, i just send an empty SMS to the port on the device which is configured for the middlet in JAD. So I don't consired it as a wap push. -- H 2009/12/16 Nikos Balkanas n...@amdtelecom.net Hi, Sorry, but the SMS is exactly like wap push. In fact, wap push is sent over as SMS. But you have to watch to have the correct udh and wbxml encoding. If not, it won't show up. Of course the major issue is your middlet. This is something you have done, and we cannot debug it for you. To see if your wap push works, test it as a normal push first (don't change ports). Your mobile has to have pushes enabled. BR, Nikos - Original Message - *From:* Henri Hovi henri.h...@patidure.com *To:* Rajeev Agarwal rajeev.agarw...@gmail.com *Cc:* Nikos Balkanas n...@amdtelecom.net ; users@kannel.org *Sent:* Wednesday, December 16, 2009 8:52 AM *Subject:* Re: wap push to midlet The SMS is just signaling that the application should start, so it's not like traditional WAP Push. Some devices just starts automatically, I have seen only Nokia requesting user to confirm the start. So in other cases, there would be no case to even display the message. -- Henri On Wed, Dec 16, 2009 at 5:06 AM, Rajeev Agarwal rajeev.agarw...@gmail.com wrote: The thing that i am doing right now is changing the destination port in the UDH to 40AB (16555 in decimal). 40AB is also the midlet port. When the phone receives the msg, the midlet gets activated. But i does not display the actual text that i have in the form of an encoded URL, as shown below http://xxx.xxx.x.xxx:15015/cgi-bin/sendsms?username=testerpassword=foobarto=xxudh= %06%05%04%40%AB%23%F0 text=%FF%06%01%AE%02%05%6A%00%45%C6%0C%03%77%77%77%2e%67%6f%6f%67%6c%65%2e%63%6f%2e%69%6e%2f%6d%6f%62%69%6c%65%00%01%03%57%65%6c%63%6f%6d%65%20%74%6f%20%47%6f%6f%67%6c%65%00%01%01% Any thoughts on this??.. Thanks. 2009/12/15 Nikos Balkanas n...@amdtelecom.net Hi, Wap push is at a predefined port. You cannot change it through UDH headers in wapbox. Wapbox doesn't support UDH. But you can do it through smsbox (as suggested by Henri). BR, Nikos - Original Message - *From:* Henri Hovi henri.h...@patidure.com *To:* Rajeev Agarwal rajeev.agarw...@gmail.com *Cc:* users@kannel.org *Sent:* Tuesday, December 15, 2009 2:36 PM *Subject:* Re: wap push to midlet No need to use wap push, just SMS with UDH -- Henri On Tue, Dec 15, 2009 at 2:27 PM, Rajeev Agarwal rajeev.agarw...@gmail.com wrote: hi!! I've changed the udh destination port according to my midlet port. But wen i use the encoded url for wap push it does not get displayed. i get some error!..has anyone tried this before? pls help! regards rajeev. -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com
Re: wap push to midlet
I am using the song ericsson ping pong midlet. 2009/12/16 Henri Hovi henri.h...@patidure.com When the midlet receives the notification from push registry, how do you capture the body of the WAP Push? Based on my knowledge,it just notifies the midlet to be executed and not forward any information for it from the message. Of course, could be that I have missed some part from the docs... -- H On Wed, Dec 16, 2009 at 11:31 AM, Rajeev Agarwal rajeev.agarw...@gmail.com wrote: if i dont use the midlet, the whoel thing is working perfectly fine!!!.. i know, there is some problem with the midlet!.. 2009/12/16 Nikos Balkanas nbalka...@gmail.com Hi, I don't know what you are doing with your middlet. That's your business. But 06 in udh header means wap push protocol, and wbxml body is from wap push specs. This is still a wap push to a different port, and it is send over SMS. BR, Nikos - Original Message - *From:* Henri Hovi henri.h...@patidure.com *To:* Nikos Balkanas n...@amdtelecom.net *Cc:* users@kannel.org *Sent:* Wednesday, December 16, 2009 11:15 AM *Subject:* Re: wap push to midlet Well, when I send the SMS to start the application by using middlet push registry service, i just send an empty SMS to the port on the device which is configured for the middlet in JAD. So I don't consired it as a wap push. -- H 2009/12/16 Nikos Balkanas n...@amdtelecom.net Hi, Sorry, but the SMS is exactly like wap push. In fact, wap push is sent over as SMS. But you have to watch to have the correct udh and wbxml encoding. If not, it won't show up. Of course the major issue is your middlet. This is something you have done, and we cannot debug it for you. To see if your wap push works, test it as a normal push first (don't change ports). Your mobile has to have pushes enabled. BR, Nikos - Original Message - *From:* Henri Hovi henri.h...@patidure.com *To:* Rajeev Agarwal rajeev.agarw...@gmail.com *Cc:* Nikos Balkanas n...@amdtelecom.net ; users@kannel.org *Sent:* Wednesday, December 16, 2009 8:52 AM *Subject:* Re: wap push to midlet The SMS is just signaling that the application should start, so it's not like traditional WAP Push. Some devices just starts automatically, I have seen only Nokia requesting user to confirm the start. So in other cases, there would be no case to even display the message. -- Henri On Wed, Dec 16, 2009 at 5:06 AM, Rajeev Agarwal rajeev.agarw...@gmail.com wrote: The thing that i am doing right now is changing the destination port in the UDH to 40AB (16555 in decimal). 40AB is also the midlet port. When the phone receives the msg, the midlet gets activated. But i does not display the actual text that i have in the form of an encoded URL, as shown below http://xxx.xxx.x.xxx:15015/cgi-bin/sendsms?username=testerpassword=foobarto=xxudh= %06%05%04%40%AB%23%F0 text=%FF%06%01%AE%02%05%6A%00%45%C6%0C%03%77%77%77%2e%67%6f%6f%67%6c%65%2e%63%6f%2e%69%6e%2f%6d%6f%62%69%6c%65%00%01%03%57%65%6c%63%6f%6d%65%20%74%6f%20%47%6f%6f%67%6c%65%00%01%01% Any thoughts on this??.. Thanks. 2009/12/15 Nikos Balkanas n...@amdtelecom.net Hi, Wap push is at a predefined port. You cannot change it through UDH headers in wapbox. Wapbox doesn't support UDH. But you can do it through smsbox (as suggested by Henri). BR, Nikos - Original Message - *From:* Henri Hovi henri.h...@patidure.com *To:* Rajeev Agarwal rajeev.agarw...@gmail.com *Cc:* users@kannel.org *Sent:* Tuesday, December 15, 2009 2:36 PM *Subject:* Re: wap push to midlet No need to use wap push, just SMS with UDH -- Henri On Tue, Dec 15, 2009 at 2:27 PM, Rajeev Agarwal rajeev.agarw...@gmail.com wrote: hi!! I've changed the udh destination port according to my midlet port. But wen i use the encoded url for wap push it does not get displayed. i get some error!..has anyone tried this before? pls help! regards rajeev. -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com
Re: wap push to midlet
So then You must use SE forum for the issues, since the Kannel part seems to work well... -- Henri On Wed, Dec 16, 2009 at 11:43 AM, Rajeev Agarwal rajeev.agarw...@gmail.comwrote: I am using the song ericsson ping pong midlet. 2009/12/16 Henri Hovi henri.h...@patidure.com When the midlet receives the notification from push registry, how do you capture the body of the WAP Push? Based on my knowledge,it just notifies the midlet to be executed and not forward any information for it from the message. Of course, could be that I have missed some part from the docs... -- H On Wed, Dec 16, 2009 at 11:31 AM, Rajeev Agarwal rajeev.agarw...@gmail.com wrote: if i dont use the midlet, the whoel thing is working perfectly fine!!!.. i know, there is some problem with the midlet!.. 2009/12/16 Nikos Balkanas nbalka...@gmail.com Hi, I don't know what you are doing with your middlet. That's your business. But 06 in udh header means wap push protocol, and wbxml body is from wap push specs. This is still a wap push to a different port, and it is send over SMS. BR, Nikos - Original Message - *From:* Henri Hovi henri.h...@patidure.com *To:* Nikos Balkanas n...@amdtelecom.net *Cc:* users@kannel.org *Sent:* Wednesday, December 16, 2009 11:15 AM *Subject:* Re: wap push to midlet Well, when I send the SMS to start the application by using middlet push registry service, i just send an empty SMS to the port on the device which is configured for the middlet in JAD. So I don't consired it as a wap push. -- H 2009/12/16 Nikos Balkanas n...@amdtelecom.net Hi, Sorry, but the SMS is exactly like wap push. In fact, wap push is sent over as SMS. But you have to watch to have the correct udh and wbxml encoding. If not, it won't show up. Of course the major issue is your middlet. This is something you have done, and we cannot debug it for you. To see if your wap push works, test it as a normal push first (don't change ports). Your mobile has to have pushes enabled. BR, Nikos - Original Message - *From:* Henri Hovi henri.h...@patidure.com *To:* Rajeev Agarwal rajeev.agarw...@gmail.com *Cc:* Nikos Balkanas n...@amdtelecom.net ; users@kannel.org *Sent:* Wednesday, December 16, 2009 8:52 AM *Subject:* Re: wap push to midlet The SMS is just signaling that the application should start, so it's not like traditional WAP Push. Some devices just starts automatically, I have seen only Nokia requesting user to confirm the start. So in other cases, there would be no case to even display the message. -- Henri On Wed, Dec 16, 2009 at 5:06 AM, Rajeev Agarwal rajeev.agarw...@gmail.com wrote: The thing that i am doing right now is changing the destination port in the UDH to 40AB (16555 in decimal). 40AB is also the midlet port. When the phone receives the msg, the midlet gets activated. But i does not display the actual text that i have in the form of an encoded URL, as shown below http://xxx.xxx.x.xxx:15015/cgi-bin/sendsms?username=testerpassword=foobarto=xxudh= %06%05%04%40%AB%23%F0 text=%FF%06%01%AE%02%05%6A%00%45%C6%0C%03%77%77%77%2e%67%6f%6f%67%6c%65%2e%63%6f%2e%69%6e%2f%6d%6f%62%69%6c%65%00%01%03%57%65%6c%63%6f%6d%65%20%74%6f%20%47%6f%6f%67%6c%65%00%01%01% Any thoughts on this??.. Thanks. 2009/12/15 Nikos Balkanas n...@amdtelecom.net Hi, Wap push is at a predefined port. You cannot change it through UDH headers in wapbox. Wapbox doesn't support UDH. But you can do it through smsbox (as suggested by Henri). BR, Nikos - Original Message - *From:* Henri Hovi henri.h...@patidure.com *To:* Rajeev Agarwal rajeev.agarw...@gmail.com *Cc:* users@kannel.org *Sent:* Tuesday, December 15, 2009 2:36 PM *Subject:* Re: wap push to midlet No need to use wap push, just SMS with UDH -- Henri On Tue, Dec 15, 2009 at 2:27 PM, Rajeev Agarwal rajeev.agarw...@gmail.com wrote: hi!! I've changed the udh destination port according to my midlet port. But wen i use the encoded url for wap push it does not get displayed. i get some error!..has anyone tried this before? pls help! regards rajeev. -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com
Re: wap push to midlet
No need to use wap push, just SMS with UDH -- Henri On Tue, Dec 15, 2009 at 2:27 PM, Rajeev Agarwal rajeev.agarw...@gmail.comwrote: hi!! I've changed the udh destination port according to my midlet port. But wen i use the encoded url for wap push it does not get displayed. i get some error!..has anyone tried this before? pls help! regards rajeev. -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com
Re: wap push to midlet
Hi, Wap push is at a predefined port. You cannot change it through UDH headers in wapbox. Wapbox doesn't support UDH. But you can do it through smsbox (as suggested by Henri). BR, Nikos - Original Message - From: Henri Hovi To: Rajeev Agarwal Cc: users@kannel.org Sent: Tuesday, December 15, 2009 2:36 PM Subject: Re: wap push to midlet No need to use wap push, just SMS with UDH -- Henri On Tue, Dec 15, 2009 at 2:27 PM, Rajeev Agarwal rajeev.agarw...@gmail.com wrote: hi!! I've changed the udh destination port according to my midlet port. But wen i use the encoded url for wap push it does not get displayed. i get some error!..has anyone tried this before? pls help! regards rajeev. -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com
Re: wap push to midlet
The thing that i am doing right now is changing the destination port in the UDH to 40AB (16555 in decimal). 40AB is also the midlet port. When the phone receives the msg, the midlet gets activated. But i does not display the actual text that i have in the form of an encoded URL, as shown below http://xxx.xxx.x.xxx:15015/cgi-bin/sendsms?username=testerpassword=foobarto=xxudh= %06%05%04%40%AB%23%F0 text=%FF%06%01%AE%02%05%6A%00%45%C6%0C%03%77%77%77%2e%67%6f%6f%67%6c%65%2e%63%6f%2e%69%6e%2f%6d%6f%62%69%6c%65%00%01%03%57%65%6c%63%6f%6d%65%20%74%6f%20%47%6f%6f%67%6c%65%00%01%01% Any thoughts on this??.. Thanks. 2009/12/15 Nikos Balkanas n...@amdtelecom.net Hi, Wap push is at a predefined port. You cannot change it through UDH headers in wapbox. Wapbox doesn't support UDH. But you can do it through smsbox (as suggested by Henri). BR, Nikos - Original Message - *From:* Henri Hovi henri.h...@patidure.com *To:* Rajeev Agarwal rajeev.agarw...@gmail.com *Cc:* users@kannel.org *Sent:* Tuesday, December 15, 2009 2:36 PM *Subject:* Re: wap push to midlet No need to use wap push, just SMS with UDH -- Henri On Tue, Dec 15, 2009 at 2:27 PM, Rajeev Agarwal rajeev.agarw...@gmail.com wrote: hi!! I've changed the udh destination port according to my midlet port. But wen i use the encoded url for wap push it does not get displayed. i get some error!..has anyone tried this before? pls help! regards rajeev. -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com
Re: wap push to midlet
The SMS is just signaling that the application should start, so it's not like traditional WAP Push. Some devices just starts automatically, I have seen only Nokia requesting user to confirm the start. So in other cases, there would be no case to even display the message. -- Henri On Wed, Dec 16, 2009 at 5:06 AM, Rajeev Agarwal rajeev.agarw...@gmail.comwrote: The thing that i am doing right now is changing the destination port in the UDH to 40AB (16555 in decimal). 40AB is also the midlet port. When the phone receives the msg, the midlet gets activated. But i does not display the actual text that i have in the form of an encoded URL, as shown below http://xxx.xxx.x.xxx:15015/cgi-bin/sendsms?username=testerpassword=foobarto=xxudh= %06%05%04%40%AB%23%F0 text=%FF%06%01%AE%02%05%6A%00%45%C6%0C%03%77%77%77%2e%67%6f%6f%67%6c%65%2e%63%6f%2e%69%6e%2f%6d%6f%62%69%6c%65%00%01%03%57%65%6c%63%6f%6d%65%20%74%6f%20%47%6f%6f%67%6c%65%00%01%01% Any thoughts on this??.. Thanks. 2009/12/15 Nikos Balkanas n...@amdtelecom.net Hi, Wap push is at a predefined port. You cannot change it through UDH headers in wapbox. Wapbox doesn't support UDH. But you can do it through smsbox (as suggested by Henri). BR, Nikos - Original Message - *From:* Henri Hovi henri.h...@patidure.com *To:* Rajeev Agarwal rajeev.agarw...@gmail.com *Cc:* users@kannel.org *Sent:* Tuesday, December 15, 2009 2:36 PM *Subject:* Re: wap push to midlet No need to use wap push, just SMS with UDH -- Henri On Tue, Dec 15, 2009 at 2:27 PM, Rajeev Agarwal rajeev.agarw...@gmail.com wrote: hi!! I've changed the udh destination port according to my midlet port. But wen i use the encoded url for wap push it does not get displayed. i get some error!..has anyone tried this before? pls help! regards rajeev. -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com -- Henri Hovi http://www.patidure.com http://patidure.blogspot.com
Re: WAP PUSH
Hi, Try testing your configuration as described in the manual. You can use FAKE smsc, so that you don't get charged and test/test_ppg client to push your wap. you will have to supply your own pap/si xml document as detailed in the manual. BR, Nikos - Original Message - From: Rajeev Agarwal To: users@kannel.org Sent: Monday, December 14, 2009 7:12 AM Subject: WAP PUSH hi I've configure my conf file for wap push services as shown below. I would like to know what should i do next for the wap push.. Thanx Regards. # CORE group=core admin-port=12000 smsbox-port=12001 wapbox-port=12002 admin-password=bar #status-password = foo #admin-deny-ip = #admin-allow-ip = log-file = /home/rajeev/sms_mms/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 = kannel.store #ssl-server-cert-file = cert.pem #ssl-server-key-file = key.pem #ssl-certkey-file = mycertandprivkeyfile.pem #SMSC group=smsc smsc=at smsc-id=SMSC modemtype=moto device = /dev/ttyACM0 speed = 9600 #sms-center = +919849087001 #MODEM group = modems id = moto name = Motorola detect-string = Motorola keepalive-cmd = AT+CMGL #init-string = AT+CNMI=0,0, 0, 1,0 init-string=AT+CNMI=2,1,0,1,0;+CMGF=0;+CMEE=1 #enable-hwhs = false #SMSBOX group = smsbox bearerbox-host = localhost smsbox-id = dlrbox sendsms-port = 12012 global-sender = 12012 log-file = /home/rajeev/sms_mms/smsbox.log access-log = /home/rajeev/sms_mms/access.log #sendsms-user group=sendsms-user username = tester password = foobar max-messages = 3 concatenation = true # SERVICES group = sms-service keyword = complex text = You asked nothing and I did it! group = sms-service keyword = default text = No service specified #WAP-BOX group=wapbox bearerbox-host=localhost log-file = /home/rajeev/sms_mms/wapbox.log syslog-level = none #PPG-PUSH-PROXY-GATEWAY group = ppg ppg-url = /wappush ppg-port = 8080 concurrent-pushes = 100 users = 1024 #ppg-allow-ip = 194.100.32.125;127.0.0.1 #ppg-deny-ip = 194.100.32.89;194.100.32.103 trusted-pi = true #WAP-USER group = wap-push-user wap-push-user = insi ppg-username = foo ppg-password = bar service-name = ppg ppg-smsbox-id = dlrbox
Re: WAP PUSH
Here's there's a mino HOWTO I wrote some time ago on PPG and Wap Push, which includes some proof of concept sample PHP code http://article.gmane.org/gmane.comp.mobile.kannel.user/11009 Be aware that you will see the PHP code with some wrong indentations that will make it not work, if you look further on the mailing-list archives someone attached this same code some months ago with that indentation fixed 2009/12/14 Nikos Balkanas n...@amdtelecom.net: Hi, Try testing your configuration as described in the manual. You can use FAKE smsc, so that you don't get charged and test/test_ppg client to push your wap. you will have to supply your own pap/si xml document as detailed in the manual. BR, Nikos - Original Message - From: Rajeev Agarwal To: users@kannel.org Sent: Monday, December 14, 2009 7:12 AM Subject: WAP PUSH hi I've configure my conf file for wap push services as shown below. I would like to know what should i do next for the wap push.. Thanx Regards. # CORE group=core admin-port=12000 smsbox-port=12001 wapbox-port=12002 admin-password=bar #status-password = foo #admin-deny-ip = #admin-allow-ip = log-file = /home/rajeev/sms_mms/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 = kannel.store #ssl-server-cert-file = cert.pem #ssl-server-key-file = key.pem #ssl-certkey-file = mycertandprivkeyfile.pem #SMSC group=smsc smsc=at smsc-id=SMSC modemtype=moto device = /dev/ttyACM0 speed = 9600 #sms-center = +919849087001 #MODEM group = modems id = moto name = Motorola detect-string = Motorola keepalive-cmd = AT+CMGL #init-string = AT+CNMI=0,0, 0, 1,0 init-string=AT+CNMI=2,1,0,1,0;+CMGF=0;+CMEE=1 #enable-hwhs = false #SMSBOX group = smsbox bearerbox-host = localhost smsbox-id = dlrbox sendsms-port = 12012 global-sender = 12012 log-file = /home/rajeev/sms_mms/smsbox.log access-log = /home/rajeev/sms_mms/access.log #sendsms-user group=sendsms-user username = tester password = foobar max-messages = 3 concatenation = true # SERVICES group = sms-service keyword = complex text = You asked nothing and I did it! group = sms-service keyword = default text = No service specified #WAP-BOX group=wapbox bearerbox-host=localhost log-file = /home/rajeev/sms_mms/wapbox.log syslog-level = none #PPG-PUSH-PROXY-GATEWAY group = ppg ppg-url = /wappush ppg-port = 8080 concurrent-pushes = 100 users = 1024 #ppg-allow-ip = 194.100.32.125;127.0.0.1 #ppg-deny-ip = 194.100.32.89;194.100.32.103 trusted-pi = true #WAP-USER group = wap-push-user wap-push-user = insi ppg-username = foo ppg-password = bar service-name = ppg ppg-smsbox-id = dlrbox -- Juan Nin 3Cinteractive / Mobilizing Great Brands http://www.3cinteractive.com
RE: WAP Push on SPECIFIC Port
Hi, Thanks for your reply. Can you please provide some example for Get and post variables? Can I use X-Kannel-UDH in PAP DTD? Regards, Irfan Malik = Manager MIS TricastMedia Cell: +92 321-6099155 PH: +92 42 5845265 Web: www.tcm.com.pk From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: Tuesday, March 31, 2009 2:05 PM To: Irfan Malik; users@kannel.org Subject: Re: WAP Push on SPECIFIC Port Hi, You can specify udh as both a GET varable (%u=) or a post variable (udh=). Finally you can also pass it as an extended HTTP header: X-Kannel-UDH. BR, Nikos - Original Message - From: Irfan Malik mailto:irfan.ma...@tcm.com.pk To: users@kannel.org Sent: Tuesday, March 31, 2009 10:42 AM Subject: WAP Push on SPECIFIC Port Dear All, I am trying to generate WAP Push using DTD PAP 1.0. I can successfully generate WAP push on standard port that is 2948. For a particular port I have to change UDH for the WAP Push. The XML code I am sending to my WAP gateway is Message to http://mydomain.com:8080/wappush Content-Type: multipart/related; boundary=PMasdfglkjhqwert; type=application/xml --PMasdfglkjhqwert Content-Type: application/xml ?xml version=1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP 1.0//EN http://www.wapforum.org/DTD/pap_1.0.dtd; pap push-message push-id=PI/450720 address address-value=WAPPUSH=+1234567891/type=p...@mydomain.com/ /push-message /pap --PMasdfglkjhqwert Content-Type: text/vnd.wap.si ?xml version=1.0 encoding=iso-8859-1? !DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//EN http://www.wapforum.org/DTD/SI.dtd; si indication href=http://Yahoo.com; si-id = WapIDE_SI/10 Open Yahoo/indication /si --PMasdfglkjhqwert- The above XML successfully generates a WAP Push on standard port i.e. 2948. I want this WAP Push on a particular port e.g. 5500. I know this can be done by modifying UDH and by changing udh=%06%05%04%0B%84%23%F0 but don't know where to change. Any help will be much appreciated.
Re: WAP Push on SPECIFIC Port
Hi, You can specify udh as both a GET varable (%u=) or a post variable (udh=). Finally you can also pass it as an extended HTTP header: X-Kannel-UDH. BR, Nikos - Original Message - From: Irfan Malik To: users@kannel.org Sent: Tuesday, March 31, 2009 10:42 AM Subject: WAP Push on SPECIFIC Port Dear All, I am trying to generate WAP Push using DTD PAP 1.0. I can successfully generate WAP push on standard port that is 2948. For a particular port I have to change UDH for the WAP Push. The XML code I am sending to my WAP gateway is Message to http://mydomain.com:8080/wappush Content-Type: multipart/related; boundary=PMasdfglkjhqwert; type=application/xml --PMasdfglkjhqwert Content-Type: application/xml ?xml version=1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP 1.0//EN http://www.wapforum.org/DTD/pap_1.0.dtd; pap push-message push-id=PI/450720 address address-value=WAPPUSH=+1234567891/type=p...@mydomain.com/ /push-message /pap --PMasdfglkjhqwert Content-Type: text/vnd.wap.si ?xml version=1.0 encoding=iso-8859-1? !DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//EN http://www.wapforum.org/DTD/SI.dtd; si indication href=http://Yahoo.com; si-id = WapIDE_SI/10 Open Yahoo/indication /si --PMasdfglkjhqwert— The above XML successfully generates a WAP Push on standard port i.e. 2948. I want this WAP Push on a particular port e.g. 5500. I know this can be done by modifying UDH and by changing udh=%06%05%04%0B%84%23%F0 but don’t know where to change. Any help will be much appreciated.
Re: WAP Push on SPECIFIC Port
I haven't used them in such a way, so i have no examples. But there is a lot in the CVS kannel documentation about them. BR, Nikos - Original Message - From: Irfan Malik To: 'Nikos Balkanas' ; users@kannel.org Sent: Tuesday, March 31, 2009 12:13 PM Subject: RE: WAP Push on SPECIFIC Port Hi, Thanks for your reply. Can you please provide some example for Get and post variables? Can I use X-Kannel-UDH in PAP DTD? Regards, Irfan Malik = Manager MIS TricastMedia Cell: +92 321-6099155 PH: +92 42 5845265 Web: www.tcm.com.pk From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: Tuesday, March 31, 2009 2:05 PM To: Irfan Malik; users@kannel.org Subject: Re: WAP Push on SPECIFIC Port Hi, You can specify udh as both a GET varable (%u=) or a post variable (udh=). Finally you can also pass it as an extended HTTP header: X-Kannel-UDH. BR, Nikos - Original Message - From: Irfan Malik To: users@kannel.org Sent: Tuesday, March 31, 2009 10:42 AM Subject: WAP Push on SPECIFIC Port Dear All, I am trying to generate WAP Push using DTD PAP 1.0. I can successfully generate WAP push on standard port that is 2948. For a particular port I have to change UDH for the WAP Push. The XML code I am sending to my WAP gateway is Message to http://mydomain.com:8080/wappush Content-Type: multipart/related; boundary=PMasdfglkjhqwert; type=application/xml --PMasdfglkjhqwert Content-Type: application/xml ?xml version=1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP 1.0//EN http://www.wapforum.org/DTD/pap_1.0.dtd; pap push-message push-id=PI/450720 address address-value=WAPPUSH=+1234567891/type=p...@mydomain.com/ /push-message /pap --PMasdfglkjhqwert Content-Type: text/vnd.wap.si ?xml version=1.0 encoding=iso-8859-1? !DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//EN http://www.wapforum.org/DTD/SI.dtd; si indication href=http://Yahoo.com; si-id = WapIDE_SI/10 Open Yahoo/indication /si --PMasdfglkjhqwert— The above XML successfully generates a WAP Push on standard port i.e. 2948. I want this WAP Push on a particular port e.g. 5500. I know this can be done by modifying UDH and by changing udh=%06%05%04%0B%84%23%F0 but don’t know where to change. Any help will be much appreciated.
RE: WAP Push on SPECIFIC Port
I got success by modifying smss.php for HTTP GET/POST method. Thanks for your help Balkanas. Regards, Irfan Malik = Manager MIS TricastMedia Cell: +92 321-6099155 PH: +92 42 5845265 Web: www.tcm.com.pk From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: Tuesday, March 31, 2009 2:57 PM To: Irfan Malik; users@kannel.org Subject: Re: WAP Push on SPECIFIC Port I haven't used them in such a way, so i have no examples. But there is a lot in the CVS kannel documentation about them. BR, Nikos - Original Message - From: Irfan Malik mailto:irfan.ma...@tcm.com.pk To: 'Nikos Balkanas' mailto:nbalka...@gmail.com ; users@kannel.org Sent: Tuesday, March 31, 2009 12:13 PM Subject: RE: WAP Push on SPECIFIC Port Hi, Thanks for your reply. Can you please provide some example for Get and post variables? Can I use X-Kannel-UDH in PAP DTD? Regards, Irfan Malik = Manager MIS TricastMedia Cell: +92 321-6099155 PH: +92 42 5845265 Web: www.tcm.com.pk From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: Tuesday, March 31, 2009 2:05 PM To: Irfan Malik; users@kannel.org Subject: Re: WAP Push on SPECIFIC Port Hi, You can specify udh as both a GET varable (%u=) or a post variable (udh=). Finally you can also pass it as an extended HTTP header: X-Kannel-UDH. BR, Nikos - Original Message - From: Irfan Malik mailto:irfan.ma...@tcm.com.pk To: users@kannel.org Sent: Tuesday, March 31, 2009 10:42 AM Subject: WAP Push on SPECIFIC Port Dear All, I am trying to generate WAP Push using DTD PAP 1.0. I can successfully generate WAP push on standard port that is 2948. For a particular port I have to change UDH for the WAP Push. The XML code I am sending to my WAP gateway is Message to http://mydomain.com:8080/wappush Content-Type: multipart/related; boundary=PMasdfglkjhqwert; type=application/xml --PMasdfglkjhqwert Content-Type: application/xml ?xml version=1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP 1.0//EN http://www.wapforum.org/DTD/pap_1.0.dtd; pap push-message push-id=PI/450720 address address-value=WAPPUSH=+1234567891/type=p...@mydomain.com/ /push-message /pap --PMasdfglkjhqwert Content-Type: text/vnd.wap.si ?xml version=1.0 encoding=iso-8859-1? !DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//EN http://www.wapforum.org/DTD/SI.dtd; si indication href=http://Yahoo.com; si-id = WapIDE_SI/10 Open Yahoo/indication /si --PMasdfglkjhqwert- The above XML successfully generates a WAP Push on standard port i.e. 2948. I want this WAP Push on a particular port e.g. 5500. I know this can be done by modifying UDH and by changing udh=%06%05%04%0B%84%23%F0 but don't know where to change. Any help will be much appreciated.
Re: Wap Push Java Code
Walikum AsSalam Monim: Here is my configuration for wappush group = wapbox bearerbox-host = localhost log-file = /var/log/kannel/wapbox.log log-level = 0 syslog-level = none group = ppg ppg-url = /wappush ppg-port = 8080 concurrent-pushes = 100 users = 1024 ppg-allow-ip = 127.0.0.1 trusted-pi = true service-name = ppg1 I don't see any change or point that makes a difference here Regards, Ishtiaq Ahmed Monim Benaiad wrote: Asalam Alaikom Ishtiaq: the message is being delivered in two segments Maybe it's a configuration issue, because I've tested this with many types of ME , even with Chinese brands and it works the wap push message successfully received and recognized by the ME. here my configuration regarding ppg and wap box: group = wapbox bearerbox-host = localhost log-file= /var/log/wapbox.log log-level = 1 syslog-level= none group = ppg ppg-url = /wappush ppg-port = 55012 concurrent-pushes = 100 users = 1024 ppg-allow-ip = 127.0.0.1;192.168.0.* trusted-pi= true service-name = ppg1 group = wap-push-user wap-push-user = wappush ppg-username= foo ppg-password= bar allow-ip= 127.0.0.1;192.168.0.* Regards. On Tue, Mar 3, 2009 at 7:33 AM, Ishtiaq Ahmed ishtiaq.ah...@ooober.com mailto:ishtiaq.ah...@ooober.com wrote: Hi Monim, We have tried the method you wrote... but its the same issue.. the message is being delivered in two segments... Following are the wappush logs.. 2009-03-03 10:23:34 [17163] [11] DEBUG: HTTP: Creating HTTPClient for `172.21.21.21'. 2009-03-03 10:23:34 [17163] [11] DEBUG: HTTP: Created HTTPClient area 0x32a9170. 2009-03-03 10:23:34 [17163] [14] WARNING: Your ppg core configuration allow all ips 2009-03-03 10:23:34 [17163] [14] INFO: PPG: Accept request /wappush from 172.21.21.21 2009-03-03 10:23:34 [17163] [14] DEBUG: PPG: http_read_thread: pap multipart accepted 2009-03-03 10:23:34 [17163] [14] INFO: client address was +923028560819, accepted 2009-03-03 10:23:34 [17163] [14] DEBUG: PAP COMPILER: doing semantic analysis for address type a phone number 2009-03-03 10:23:34 [17163] [14] DEBUG: using defaults instead of anys 2009-03-03 10:23:34 [17163] [14] DEBUG: PPG: http_read_thread: pap control entity compiled ok 2009-03-03 10:23:34 [17163] [14] DEBUG: PPG: transform_message: push message content and headers valid 2009-03-03 10:23:34 [17163] [14] DEBUG: PPG: push machine 1 created 2009-03-03 10:23:34 [17163] [14] DEBUG: PPG: store_push_data: push machine 1 appended to unit push list 2009-03-03 10:23:34 [17163] [14] DEBUG: PPG: send_push_response: telling pi 2009-03-03 10:23:34 [17163] [14] DEBUG: HTTP: Resetting HTTPClient for `172.21.21.21'. 2009-03-03 10:23:34 [17163] [14] INFO: PPG: handle_push_message: push message accepted for processing 2009-03-03 10:23:34 [17163] [14] DEBUG: PPG: OTA request for unit push 2009-03-03 10:23:34 [17163] [9] DEBUG: OTA: event arrived 2009-03-03 10:23:34 [17163] [14] INFO: PPG: unconfirmed push delivered to OTA 2009-03-03 10:23:34 [17163] [14] DEBUG: PPG: destroying push machine 1 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP (UNIT): event arrived 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP_UNIT: Connectionless push accepted 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `application/vnd.wap.sic', WSP 1.2 to 0x002e. 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `Cache-Control', WSP 1.3 to 0x003d. 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `Pragma', WSP 1.3 to 0x001f. 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `User-Agent', WSP 1.3 to 0x0029. 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `Accept', WSP 1.3 to 0x. 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `text/html', WSP 1.2 to 0x0002. 2009-03-03 10:23:34 [17163] [9] DEBUG: OTA: made connectionless session service request 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `image/gif', WSP 1.2 to 0x001d. 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `image/jpeg', WSP 1.2 to 0x001e. 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `*', WSP 1.2 to 0x. 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `q', WSP 1.2 to 0x. 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `*/*', WSP 1.2 to 0x. 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `q', WSP 1.2 to 0x. 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `Content-Length', WSP 1.3 to 0x000d. 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `Content-Type', WSP 1.3 to 0x0011. 2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `Encoding-Version', WSP 1.3 to 0x0043. 2009-03-03 10:23:34 [17163] [2] DEBUG: WDP (wapbox):
Re: Wap Push Java Code
Hi Monim,
We have tried the method you wrote... but its the same issue.. the
message is being delivered in two segments... Following are the wappush
logs..
2009-03-03 10:23:34 [17163] [11] DEBUG: HTTP: Creating HTTPClient for
`172.21.21.21'.
2009-03-03 10:23:34 [17163] [11] DEBUG: HTTP: Created HTTPClient area
0x32a9170.
2009-03-03 10:23:34 [17163] [14] WARNING: Your ppg core configuration
allow all ips
2009-03-03 10:23:34 [17163] [14] INFO: PPG: Accept request /wappush
from 172.21.21.21
2009-03-03 10:23:34 [17163] [14] DEBUG: PPG: http_read_thread: pap
multipart accepted
2009-03-03 10:23:34 [17163] [14] INFO: client address was
+923028560819, accepted
2009-03-03 10:23:34 [17163] [14] DEBUG: PAP COMPILER: doing semantic
analysis for address type a phone number
2009-03-03 10:23:34 [17163] [14] DEBUG: using defaults instead of anys
2009-03-03 10:23:34 [17163] [14] DEBUG: PPG: http_read_thread: pap
control entity compiled ok
2009-03-03 10:23:34 [17163] [14] DEBUG: PPG: transform_message: push
message content and headers valid
2009-03-03 10:23:34 [17163] [14] DEBUG: PPG: push machine 1 created
2009-03-03 10:23:34 [17163] [14] DEBUG: PPG: store_push_data: push
machine 1 appended to unit push list
2009-03-03 10:23:34 [17163] [14] DEBUG: PPG: send_push_response: telling pi
2009-03-03 10:23:34 [17163] [14] DEBUG: HTTP: Resetting HTTPClient for
`172.21.21.21'.
2009-03-03 10:23:34 [17163] [14] INFO: PPG: handle_push_message: push
message accepted for processing
2009-03-03 10:23:34 [17163] [14] DEBUG: PPG: OTA request for unit push
2009-03-03 10:23:34 [17163] [9] DEBUG: OTA: event arrived
2009-03-03 10:23:34 [17163] [14] INFO: PPG: unconfirmed push delivered
to OTA
2009-03-03 10:23:34 [17163] [14] DEBUG: PPG: destroying push machine 1
2009-03-03 10:23:34 [17163] [2] DEBUG: WSP (UNIT): event arrived
2009-03-03 10:23:34 [17163] [2] DEBUG: WSP_UNIT: Connectionless push
accepted
2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping
`application/vnd.wap.sic', WSP 1.2 to 0x002e.
2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `Cache-Control', WSP
1.3 to 0x003d.
2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `Pragma', WSP 1.3 to
0x001f.
2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `User-Agent', WSP
1.3 to 0x0029.
2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `Accept', WSP 1.3 to
0x.
2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `text/html', WSP 1.2
to 0x0002.
2009-03-03 10:23:34 [17163] [9] DEBUG: OTA: made connectionless session
service request
2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `image/gif', WSP 1.2
to 0x001d.
2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `image/jpeg', WSP
1.2 to 0x001e.
2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `*', WSP 1.2 to
0x.
2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `q', WSP 1.2 to 0x.
2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `*/*', WSP 1.2 to
0x.
2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `q', WSP 1.2 to 0x.
2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `Content-Length',
WSP 1.3 to 0x000d.
2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `Content-Type', WSP
1.3 to 0x0011.
2009-03-03 10:23:34 [17163] [2] DEBUG: WSP: Mapping `Encoding-Version',
WSP 1.3 to 0x0043.
2009-03-03 10:23:34 [17163] [2] DEBUG: WDP (wapbox): delivering 2
segments to bearerbox
2009-03-03 10:23:34 [17163] [2] DEBUG: WSP (UNIT): delivering to wdp
2009-03-03 10:23:34 [17163] [0] WARNING: Received other message than
wdp/admin, ignoring!
2009-03-03 10:23:34 [17163] [0] WARNING: Received other message than
wdp/admin, ignoring!
Regards,
Ishtiaq Ahmed
Monim Benaiad wrote:
Dear Ishtiaq Ahmed,
Sorry for my late response, I wrote a method to do the job:
Note:- you have to change: encoding=\ISO-8859-6\ in the buffer code.
Start of method/
public String sendWapPush(String target,String downloadURL,String
downloadDetail) {
try {
StringBuffer buffer = new StringBuffer();
String vMessageID = + Math.random();
String message = ;
String host = 127.0.0.1;//kannel host
String port = 55012;//ppg port
String url = http://; + host + : + port + /wappush;
buffer.append(--asdlfkjiurwgasf\r\n).append(Content-Type:
application/xml\r\n\r\n).append(?xml
version=\1.0\?\r\n).append(!DOCTYPE pap PUBLIC
\-//WAPFORUM//DTD
PAP//EN\\r\n).append(\http://www.wapforum.org/DTD/pap_1.0.dtd\;\r\n).append(pap\r\n).append(push-message
push-id=\).append(vMessageID.trim()).append(\\r\n
deliver-before-timestamp=\2010-06-18T06:13:00Z\\r\n).append(deliver-after-timestamp=\2008-06-17T06:45:00Z\
).append(progress-notes-requested=\true\\r\n).append(address
address-value=\WAPPUSH=).append(target).append(/TYPE=PLMN\/\r\n).append(quality-of-service
delivery-method=\unconfirmed\\r\nnetwork-required=\true\\r\n
network=\GSM\\r\nbearer-required=\true\\r\nbearer=\SMS\\r\n
Re: Wap Push Java Code
Dear Ishtiaq Ahmed,
Sorry for my late response, I wrote a method to do the job:
Note:- you have to change: encoding=\ISO-8859-6\ in the buffer code.
Start of method/
public String sendWapPush(String target,String downloadURL,String
downloadDetail) {
try {
StringBuffer buffer = new StringBuffer();
String vMessageID = + Math.random();
String message = ;
String host = 127.0.0.1;//kannel host
String port = 55012;//ppg port
String url = http://; + host + : + port + /wappush;
buffer.append(--asdlfkjiurwgasf\r\n).append(Content-Type:
application/xml\r\n\r\n).append(?xml
version=\1.0\?\r\n).append(!DOCTYPE pap PUBLIC \-//WAPFORUM//DTD
PAP//EN\\r\n).append(\http://www.wapforum.org/DTD/pap_1.0.dtd\;\r\n).append(pap\r\n).append(push-message
push-id=\).append(vMessageID.trim()).append(\\r\n
deliver-before-timestamp=\2010-06-18T06:13:00Z\\r\n).append(deliver-after-timestamp=\2008-06-17T06:45:00Z\
).append(progress-notes-requested=\true\\r\n).append(address
address-value=\WAPPUSH=).append(target).append(/TYPE=PLMN\/\r\n).append(quality-of-service
delivery-method=\unconfirmed\\r\nnetwork-required=\true\\r\n
network=\GSM\\r\nbearer-required=\true\\r\nbearer=\SMS\\r\n
priority=\high\/).append(/push-message\r\n).append(/pap\r\n\r\n).append(--asdlfkjiurwgasf\r\n).append(Content-Type:
text/vnd.wap.si\r\n\r\n).append(?xml version=\1.0\
encoding=\ISO-8859-6\?\r\n).append(!DOCTYPE si PUBLIC
\-//WAPFORUM//DTD SI 1.0//EN\\r\n).append(\
http://www.wapforum.org/DTD/si.dtd\;\r\n).append(si\r\n).append(indication
action=\signal-high\ si-id=\).append(vMessageID).append(\
href=\).append(downloadURL).append(\).append(downloadDetail).append(/indication\r\n).append(/si\r\n).append(--asdlfkjiurwgasf--\r\n\r\n);
message = buffer.toString();
target = url;
String content = message;
//public static String postData(String target, String content)
throws Exception {
//System.out.println(About to post\nURL: +
target + content: + content);
String responseD = ;
URL urlc = new URL(target);
URLConnection conn = urlc.openConnection();
// Set connection parameters.
conn.setDoInput(true);
conn.setDoOutput(true);
conn.setUseCaches(false);
conn.setRequestProperty(Content-Type, multipart/related;
boundary=asdlfkjiurwgasf; type=application/xml);
//conn.setRequestProperty(Authorization, Basic \foo:bar\);
conn.setRequestProperty(X-Kannel-SMSC, smsc + smsc);
conn.setRequestProperty(X-Kannel-From, smsc);
conn.setRequestProperty(Content-Length, +
content.length());
DataOutputStream outs = new
DataOutputStream(conn.getOutputStream());
// Write out the bytes of the content string to the stream.
outs.writeBytes(content);
outs.flush();
// Read response from the input stream.
BufferedReader in = new BufferedReader(new
InputStreamReader(conn.getInputStream()));
String temp;
while ((temp = in.readLine()) != null) {
responseD += temp + \n;
}
temp = null;
outs.close();
in.close();
//System.out.println(Server response:\n + responseD + );
return responseD;
} catch (Exception e) {
e.printStackTrace();
return null;
}
}
end of method
On Thu, Feb 26, 2009 at 3:58 PM, Ishtiaq Ahmed ishtiaq.ah...@ooober.comwrote:
Hi Fellows:
Can someone help with the exact java code and minimum header set / PAP
configuration / Content File... for sending the WAP Push through Kannel
The problem with my code is that The message is being sent in two
segments
2009-02-20 06:35:02 [23465] [2] DEBUG: WSP (UNIT): event arrived
2009-02-20 06:35:02 [23465] [2] DEBUG: WSP_UNIT: Connectionless push
accepted
2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping
`application/vnd.wap.sic', WSP 1.2 to 0x002e.
2009-02-20 06:35:02 [23465] [2] ERROR: HTTP: Header does not contain a
colon. BAD.
2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping `X-Unknown', WSP 1.3 to
0x.
2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping `Cache-Control', WSP
1.3 to 0x003d.
2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping `Pragma', WSP 1.3 to
0x001f.
2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping `User-Agent', WSP 1.3
to 0x0029.
2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping `Accept', WSP 1.3 to
0x.
2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping `text/html', WSP 1.2 to
0x0002.
2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping `image/gif', WSP 1.2 to
0x001d.
2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping `image/jpeg', WSP 1.2
to 0x001e.
2009-02-20 06:35:02 [23465] [2] DEBUG: WSP: Mapping `*', WSP 1.2 to
Re: WAP Push Issue
you wappush is probably exceeded 160 chracter . please ask telco to switch on concatenation or just try to send some short url with short massage. I guess this issue raised with you on Mobilink Pakistan. ;) On Tue, Feb 10, 2009 at 7:00 PM, Ishtiaq Ahmed ishtiaq.ah...@ooober.comwrote: Hi Users Admins... I am facing a problem in sending out a wap push to a specific LA... At the other end its Logical SMSC with SMPP 3.4. I send the push and then also recieve the delivery report but no message has been delivered to device... I have checked out everything at my side... what I need is the information that either the Guys at the SMSC has to do some specific configuration for the shortcode to get the wap push through... Thanks, Ishtiaq Ahmed -- Syed Kashif Ali Bukhari +92-345-820 http://www.sysadminsline.com http://www.kashifbukhari.com
Re: WAP Push Issue
We are sending a small url like http://www.yahoo.com I hope this would not exceed the message above 160 chars... Kashif Ali Bukhari wrote: you wappush is probably exceeded 160 chracter . please ask telco to switch on concatenation or just try to send some short url with short massage. I guess this issue raised with you on Mobilink Pakistan. ;) On Tue, Feb 10, 2009 at 7:00 PM, Ishtiaq Ahmed ishtiaq.ah...@ooober.com mailto:ishtiaq.ah...@ooober.com wrote: Hi Users Admins... I am facing a problem in sending out a wap push to a specific LA... At the other end its Logical SMSC with SMPP 3.4. I send the push and then also recieve the delivery report but no message has been delivered to device... I have checked out everything at my side... what I need is the information that either the Guys at the SMSC has to do some specific configuration for the shortcode to get the wap push through... Thanks, Ishtiaq Ahmed -- Syed Kashif Ali Bukhari +92-345-820 http://www.sysadminsline.com http://www.kashifbukhari.com
Re: Wap Push (PAP) Question
Any news? Anyone? - Original Message - From: Nikos Balkanas To: users@kannel.org Sent: Friday, November 28, 2008 6:32 AM Subject: Wap Push (PAP) Question Hi, I've tried some tests and it doesn't seem that kannel supports multiple addresses/pap file as specified in the protocol. Can anyone confirm? Thanx, Nikos
Re: wap push with drm
Are you sure that your phone supports DRM for content downloaded over the air in first place? Phone Make? Phone Model? Example of what you're doing? Method to delivering the content? Web server being used to download? Mime-types are set? Logs? Whatever other info required to reproduce the error? Do not expect a lot of help by just saying it doesn't work. Do your homework first... Regards, Alejandro On Thu, Nov 6, 2008 at 5:42 AM, mohmmad jarwan [EMAIL PROTECTED]wrote: hi list i using kannel to send java game with drm via wap push, but the drm it's not working , i receive the game to my mobile but the drm not working(i can send the game via bluetooth to other device ) how i can fix it. please help me,and gave me the correct header to drm. thanks.
Re: wap push received as garbage
Hi Alejandro, Having found the meaning of the DCS (data coding scheme) here http://ozekisms.com/index.php?ow_page_number=251 I believe the needed configuration should be: DCS = 0xf5 -Compressed text -message class = 1 (to mobile) -8 bit data enconding If I add to your funcion the kannel parameter mclass = 1 it sends the DCS = 0xf5 !! as you see in the log below. However that did not solved the problem, so now I'm running out out ideas. I tried to do the same with PPG setting the header X-Kannel-MClass = 1 but the message is never delivered. Not even logged in the sms log. The message is accepted by the PPG, the wap log says the message has been deliveried to bearerbox but then and after there is no trace. I also found that the flags of the log of that message woth DCS = 0xf5 are set like this: [flags:1:1:-1:-1:-1] where [flags:%m:%c:%M:%C:%d] and charset %C is not set to 1 (binary) This might be the problem I'll keep you posted if I get something! 2008-09-25 14:06:56 [2802] [19] DEBUG: boxc_receiver: sms received 2008-09-25 14:06:56 [2802] [19] DEBUG: send_msg: sending msg to boxc: ecomm 2008-09-25 14:06:56 [2802] [6] DEBUG: SMPP[smsc_1]: Sending PDU: 2008-09-25 14:06:56 [2802] [6] DEBUG: SMPP PDU 0x2c002770 dump: 2008-09-25 14:06:56 [2802] [6] DEBUG: type_name: submit_sm 2008-09-25 14:06:56 [2802] [6] DEBUG: command_id: 4 = 0x0004 2008-09-25 14:06:56 [2802] [6] DEBUG: command_status: 0 = 0x 2008-09-25 14:06:56 [2802] [6] DEBUG: sequence_number: 7047 = 0x1b87 2008-09-25 14:06:56 [2802] [6] DEBUG: service_type: NULL 2008-09-25 14:06:56 [2802] [6] DEBUG: source_addr_ton: 2 = 0x0002 2008-09-25 14:06:56 [2802] [6] DEBUG: source_addr_npi: 1 = 0x0001 2008-09-25 14:06:56 [2802] [6] DEBUG: source_addr: [protected] 2008-09-25 14:06:56 [2802] [6] DEBUG: dest_addr_ton: 2 = 0x0002 2008-09-25 14:06:56 [2802] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2008-09-25 14:06:56 [2802] [6] DEBUG: destination_addr: [protected] 2008-09-25 14:06:56 [2802] [6] DEBUG: esm_class: 64 = 0x0040 2008-09-25 14:06:56 [2802] [6] DEBUG: protocol_id: 0 = 0x 2008-09-25 14:06:56 [2802] [6] DEBUG: priority_flag: 0 = 0x 2008-09-25 14:06:56 [2802] [6] DEBUG: schedule_delivery_time: NULL 2008-09-25 14:06:56 [2802] [6] DEBUG: validity_period: NULL 2008-09-25 14:06:56 [2802] [6] DEBUG: registered_delivery: 0 = 0x 2008-09-25 14:06:56 [2802] [6] DEBUG: replace_if_present_flag: 0 = 0x 2008-09-25 14:06:56 [2802] [6] DEBUG: data_coding: 245 = 0x00f5 2008-09-25 14:06:56 [2802] [6] DEBUG: sm_default_msg_id: 0 = 0x 2008-09-25 14:06:56 [2802] [6] DEBUG: sm_length: 50 = 0x0032 2008-09-25 14:06:56 [2802] [6] DEBUG: short_message: 2008-09-25 14:06:56 [2802] [6] DEBUG:Octet string at 0x2c002130: 2008-09-25 14:06:56 [2802] [6] DEBUG: len: 50 2008-09-25 14:06:56 [2802] [6] DEBUG: size: 1024 2008-09-25 14:06:56 [2802] [6] DEBUG: immutable: 0 2008-09-25 14:06:56 [2802] [6] DEBUG: data: 06 05 04 0b 84 23 f0 1b 06 01 ae 02 05 6a 00 45 .#...j.E 2008-09-25 14:06:56 [2802] [6] DEBUG: data: c6 0c 03 68 74 74 70 3a 2f 2f 77 77 77 2e 67 6f ...http://www.go 2008-09-25 14:06:56 [2802] [6] DEBUG: data: 6f 67 6c 65 2e 63 6f 6d 00 01 03 74 65 73 74 00 ogle.com...test. 2008-09-25 14:06:56 [2802] [6] DEBUG: data: 01 01 .. 2008-09-25 14:06:56 [2802] [6] DEBUG:Octet string dump ends. 2008-09-25 14:06:56 [2802] [6] DEBUG: SMPP PDU dump ends. From: Alejandro Guerrieri Sent: Friday, September 26, 2008 1:19 AM To: Alex Arias Cc: users@kannel.org ; [EMAIL PROTECTED] ; [EMAIL PROTECTED] Subject: Re: wap push received as garbage Hmm, you could try using the alt-dcs, coding and other available parameter to set the data-coding (check the userguide for the details). I'm checking the SMPP Specs, and thos data coding values are: 0x05 - JIS (X 0208-1990) 0xF5 - Extended Kanji JIS (X 0212-1990) Checking on Kannel's source code, Kannel doesn't even know how to handle 0x05, are you sure about that? Regards, Alejandro On Thu, Sep 25, 2008 at 4:26 PM, Alex Arias [EMAIL PROTECTED] wrote: Hi Alejandro, I see that I have exactly the same problem as Christian Vandrei in this post http://www.mail-archive.com/users@kannel.org/msg08136.html and the same problem as Joaquin Vera in this post http://www.mail-archive.com/users@kannel.org/msg10058.html So both believe that the problem is the data_coding parameter that should be set to something different than 0x04. It should be 0xf5 or 0x05 Christian, Joaquin were you able to solve this already? Thanks Alex From: Alex Arias Sent: Thursday, September 25, 2008 9:48 PM To: Alejandro Guerrieri Cc: Aarno Syvänen ; users@kannel.org Subject: Re: wap push received as garbage Hi Alejandro, Thank you for your reply. I already used your funcion (thanks BTW
Re: wap push received as garbage
[2802] [6] DEBUG: SMPP PDU dump ends. *From:* Alejandro Guerrieri [EMAIL PROTECTED] *Sent:* Friday, September 26, 2008 1:19 AM *To:* Alex Arias [EMAIL PROTECTED] *Cc:* users@kannel.org ; [EMAIL PROTECTED] ; [EMAIL PROTECTED] *Subject:* Re: wap push received as garbage Hmm, you could try using the alt-dcs, coding and other available parameter to set the data-coding (check the userguide for the details). I'm checking the SMPP Specs, and thos data coding values are: 0x05 - JIS (X 0208-1990) 0xF5 - Extended Kanji JIS (X 0212-1990) Checking on Kannel's source code, Kannel doesn't even know how to handle 0x05, are you sure about that? Regards, Alejandro On Thu, Sep 25, 2008 at 4:26 PM, Alex Arias [EMAIL PROTECTED] wrote: Hi Alejandro, I see that I have exactly the same problem as Christian Vandrei in this post http://www.mail-archive.com/users@kannel.org/msg08136.html and the same problem as Joaquin Vera in this post http://www.mail-archive.com/users@kannel.org/msg10058.html So both believe that the problem is the data_coding parameter that should be set to something different than 0x04. It should be 0xf5 or 0x05 Christian, Joaquin were you able to solve this already? Thanks Alex *From:* Alex Arias [EMAIL PROTECTED] *Sent:* Thursday, September 25, 2008 9:48 PM *To:* Alejandro Guerrieri [EMAIL PROTECTED] *Cc:* Aarno Syvänen [EMAIL PROTECTED] ; users@kannel.org *Subject:* Re: wap push received as garbage Hi Alejandro, Thank you for your reply. I already used your funcion (thanks BTW), but unfortunately I got the same results. Below is the log using your function. It produces basically the same parameters as sending through PPG. I believe is the case of an old case from Joaquin Vera with subject Wap push as a text SMS. The problem seems to be in the parameter data_coding that currently is 0x04 but should be 0xf5. Do you know how to change that parameter in Kannel? 2008-09-24 11:18:04 [2802] [19] DEBUG: boxc_receiver: sms received 2008-09-24 11:18:04 [2802] [19] DEBUG: send_msg: sending msg to boxc: ecomm 2008-09-24 11:18:04 [2802] [6] DEBUG: SMPP[smsc_1]: Sending PDU: 2008-09-24 11:18:04 [2802] [6] DEBUG: SMPP PDU 0x2c000d40 dump: 2008-09-24 11:18:04 [2802] [6] DEBUG: type_name: submit_sm 2008-09-24 11:18:04 [2802] [6] DEBUG: command_id: 4 = 0x0004 2008-09-24 11:18:04 [2802] [6] DEBUG: command_status: 0 = 0x 2008-09-24 11:18:04 [2802] [6] DEBUG: sequence_number: 1228 = 0x04cc 2008-09-24 11:18:04 [2802] [6] DEBUG: service_type: NULL 2008-09-24 11:18:04 [2802] [6] DEBUG: source_addr_ton: 2 = 0x0002 2008-09-24 11:18:04 [2802] [6] DEBUG: source_addr_npi: 1 = 0x0001 2008-09-24 11:18:04 [2802] [6] DEBUG: source_addr: 34488 2008-09-24 11:18:04 [2802] [6] DEBUG: dest_addr_ton: 2 = 0x0002 2008-09-24 11:18:04 [2802] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2008-09-24 11:18:04 [2802] [6] DEBUG: destination_addr: [protected] 2008-09-24 11:18:04 [2802] [6] DEBUG: esm_class: 64 = 0x0040 2008-09-24 11:18:04 [2802] [6] DEBUG: protocol_id: 0 = 0x 2008-09-24 11:18:04 [2802] [6] DEBUG: priority_flag: 0 = 0x 2008-09-24 11:18:04 [2802] [6] DEBUG: schedule_delivery_time: NULL 2008-09-24 11:18:04 [2802] [6] DEBUG: validity_period: NULL 2008-09-24 11:18:04 [2802] [6] DEBUG: registered_delivery: 0 = 0x 2008-09-24 11:18:04 [2802] [6] DEBUG: replace_if_present_flag: 0 = 0x 2008-09-24 11:18:04 [2802] [6] DEBUG: data_coding: 4 = 0x0004 2008-09-24 11:18:04 [2802] [6] DEBUG: sm_default_msg_id: 0 = 0x 2008-09-24 11:18:04 [2802] [6] DEBUG: sm_length: 50 = 0x0032 2008-09-24 11:18:04 [2802] [6] DEBUG: short_message: 2008-09-24 11:18:04 [2802] [6] DEBUG:Octet string at 0x2c000f40: 2008-09-24 11:18:04 [2802] [6] DEBUG: len: 50 2008-09-24 11:18:04 [2802] [6] DEBUG: size: 1024 2008-09-24 11:18:04 [2802] [6] DEBUG: immutable: 0 2008-09-24 11:18:04 [2802] [6] DEBUG: data: 06 05 04 0b 84 23 f0 1b 06 01 ae 02 05 6a 00 45 .#...j.E 2008-09-24 11:18:04 [2802] [6] DEBUG: data: c6 0c 03 68 74 74 70 3a 2f 2f 77 77 77 2e 67 6f ...http://www.go 2008-09-24 11:18:04 [2802] [6] DEBUG: data: 6f 67 6c 65 2e 63 6f 6d 00 01 03 74 65 73 74 00 ogle.com...test. 2008-09-24 11:18:04 [2802] [6] DEBUG: data: 01 01 .. 2008-09-24 11:18:04 [2802] [6] DEBUG:Octet string dump ends. 2008-09-24 11:18:04 [2802] [6] DEBUG: SMPP PDU dump ends. 2008-09-24 11:18:04 [2802] [6] DEBUG: SMPP[smsc_1]: Got PDU: 2008-09-24 11:18:04 [2802] [6] DEBUG: SMPP PDU 0x2c000d40 dump: 2008-09-24 11:18:04 [2802] [6] DEBUG: type_name: submit_sm_resp 2008-09-24 11:18:04 [2802] [6] DEBUG: command_id: 2147483652 = 0x8004 2008-09-24 11:18:04 [2802] [6] DEBUG: command_status: 0 = 0x 2008-09-24 11:18:04 [2802] [6] DEBUG: sequence_number: 1228
Re: wap push received as garbage
Hi, yes but it if PPG binary coding is working you would not need a separate script for for every strange phone. So it is better to try to use PPG and fix it if it is not working. Aarno On 25 Sep 2008, at 19:33, Alejandro Guerrieri wrote: Alex, Wap push is a binary-coded message. What PPG does is to transform your request into a binary message, so there's nothing unusual about it. Some carriers does not support sending binary messages on their networks, so maybe the problem is not with your request but with the network. I don't know if that's the case, but if you can test the same message over a different link maybe you can discard this. I've made a small php function that encodes the binary message without using the PPG at all. You can try it if you want, if this also renders garbled text you can be almost certain that there's a problem with the network. Check here: http://www.mail-archive.com/users@kannel.org/msg03255.html Hope it helps, Alejandro Guerrieri On Thu, Sep 25, 2008 at 1:40 PM, Alex Arias [EMAIL PROTECTED] wrote: Hi Aarno, Thank you very much for your reply. I tried to send a wap push (binary). The process is as follows: Wap push sent to Kannel PPG using PAP format Kannel encode the PAP request and send it to the operator via SMPP Operator acknowledges the mesage and deliver it to the phone The phone get weird characters instead of the functional wap push I took the resultant binary message from the smsbox log and posted here Any idea? I believe the problem is in the parameters sent in the SMPP protocol. For example I had to patch Kannel and change the value of esm_class to 0 as the operator rejected the sms. This might be something similar. How do I tell the operator, in the SMPP protocol, that the message is a wap push? What parameters are involved and what should be the right value? Thank you Alex From: Aarno Syvänen Sent: Thursday, September 25, 2008 10:16 AM To: Alex Arias Cc: users@kannel.org Subject: Re: wap push received as garbage Hi, did you try to send a binary message, or text ? Aarno On 24 Sep 2008, at 17:53, Alex Arias wrote: Hi everybody, I'm trying to send a wap push to an operator via PAP-PPG-SMPP and they get garbage instead of a functional wap push. I'm using Kannel as PPG. The message is accepted OK by Kannel and delivered OK to operator, but they don't get the right message. Thank you so much for your help! Below are the details PAP MESSAGE --multipart-boundary Content-Type: application/xml ?xml version=1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP 1.0//EN http://www.wapforum.org/DTD/pap_1.0.dtd; pap push-message push-id=[EMAIL PROTECTED] deliver-before- timestamp=2009-11-01T06:45:00Z deliver-after- timestamp=2007-02-27T06:45:00Z progress-notes-requested=false address address-value=WAPPUSH=[protected]/[EMAIL PROTECTED] / /push-message /pap --multipart-boundary Content-Type: text/vnd.wap.si ?xml version=1.0? !DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//EN http://www.wapforum.org/DTD/si.dtd; si indication action=signal-high created=1999-06-25T15:23:15Z si- expires=2009-06-25T15:23:15Z si-id=[EMAIL PROTECTED] href=http://www.google.com Test/indication /si --multipart-boundary-- BINARY MESSAGE binary message:010605AE8DBDC39302056A0045C6080AC3071999062515231510C30720090625152315110335406463682E636F6D000D03676F6F676C652E636F6D00010354657374000101 UDH:0605040B8423F0 CORE LOG (debug) 2008-09-24 08:27:47 [2802] [17] DEBUG: boxc_receiver: got sms from wapbox 2008-09-24 08:27:47 [2802] [17] DEBUG: send_msg: sending msg to box: 127.0.0.1 2008-09-24 08:27:47 [2802] [6] DEBUG: SMPP[movistar_arg]: Sending PDU: 2008-09-24 08:27:47 [2802] [6] DEBUG: SMPP PDU 0x1b117f50 dump: 2008-09-24 08:27:47 [2802] [6] DEBUG: type_name: submit_sm 2008-09-24 08:27:47 [2802] [6] DEBUG: command_id: 4 = 0x0004 2008-09-24 08:27:47 [2802] [6] DEBUG: command_status: 0 = 0x 2008-09-24 08:27:47 [2802] [6] DEBUG: sequence_number: 546 = 0x0222 2008-09-24 08:27:47 [2802] [6] DEBUG: service_type: NULL 2008-09-24 08:27:47 [2802] [6] DEBUG: source_addr_ton: 2 = 0x0002 2008-09-24 08:27:47 [2802] [6] DEBUG: source_addr_npi: 1 = 0x0001 2008-09-24 08:27:47 [2802] [6] DEBUG: source_addr: [protected] 2008-09-24 08:27:47 [2802] [6] DEBUG: dest_addr_ton: 2 = 0x0002 2008-09-24 08:27:47 [2802] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2008-09-24 08:27:47 [2802] [6] DEBUG: destination_addr: [protected] 2008-09-24 08:27:47 [2802] [6] DEBUG: esm_class: 64 = 0x0040 2008-09-24 08:27:47 [2802] [6] DEBUG: protocol_id: 0 = 0x 2008-09-24 08:27:47 [2802] [6] DEBUG: priority_flag: 0 = 0x 2008-09-24 08:27:47 [2802] [6] DEBUG: schedule_delivery_time: NULL 2008-09-24 08:27:47 [2802] [6] DEBUG: validity_period: 080925152747000+ 2008-09-24 08:27:47 [2802] [6] DEBUG
Re: wap push received as garbage
Hi, If you want to know did the operator deliver the the push to the phone, you can ask for delivery reports (see user guide). Aarno On 26 Sep 2008, at 09:28, Aarno Syvänen wrote: Hi, yes but it if PPG binary coding is working you would not need a separate script for for every strange phone. So it is better to try to use PPG and fix it if it is not working. Aarno On 25 Sep 2008, at 19:33, Alejandro Guerrieri wrote: Alex, Wap push is a binary-coded message. What PPG does is to transform your request into a binary message, so there's nothing unusual about it. Some carriers does not support sending binary messages on their networks, so maybe the problem is not with your request but with the network. I don't know if that's the case, but if you can test the same message over a different link maybe you can discard this. I've made a small php function that encodes the binary message without using the PPG at all. You can try it if you want, if this also renders garbled text you can be almost certain that there's a problem with the network. Check here: http://www.mail-archive.com/users@kannel.org/msg03255.html Hope it helps, Alejandro Guerrieri On Thu, Sep 25, 2008 at 1:40 PM, Alex Arias [EMAIL PROTECTED] wrote: Hi Aarno, Thank you very much for your reply. I tried to send a wap push (binary). The process is as follows: Wap push sent to Kannel PPG using PAP format Kannel encode the PAP request and send it to the operator via SMPP Operator acknowledges the mesage and deliver it to the phone The phone get weird characters instead of the functional wap push I took the resultant binary message from the smsbox log and posted here Any idea? I believe the problem is in the parameters sent in the SMPP protocol. For example I had to patch Kannel and change the value of esm_class to 0 as the operator rejected the sms. This might be something similar. How do I tell the operator, in the SMPP protocol, that the message is a wap push? What parameters are involved and what should be the right value? Thank you Alex From: Aarno Syvänen Sent: Thursday, September 25, 2008 10:16 AM To: Alex Arias Cc: users@kannel.org Subject: Re: wap push received as garbage Hi, did you try to send a binary message, or text ? Aarno On 24 Sep 2008, at 17:53, Alex Arias wrote: Hi everybody, I'm trying to send a wap push to an operator via PAP-PPG-SMPP and they get garbage instead of a functional wap push. I'm using Kannel as PPG. The message is accepted OK by Kannel and delivered OK to operator, but they don't get the right message. Thank you so much for your help! Below are the details PAP MESSAGE --multipart-boundary Content-Type: application/xml ?xml version=1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP 1.0//EN http://www.wapforum.org/DTD/pap_1.0.dtd; pap push-message push-id=[EMAIL PROTECTED] deliver-before- timestamp=2009-11-01T06:45:00Z deliver-after- timestamp=2007-02-27T06:45:00Z progress-notes-requested=false address address-value=WAPPUSH=[protected]/[EMAIL PROTECTED] / /push-message /pap --multipart-boundary Content-Type: text/vnd.wap.si ?xml version=1.0? !DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//EN http://www.wapforum.org/DTD/si.dtd; si indication action=signal-high created=1999-06-25T15:23:15Z si- expires=2009-06-25T15:23:15Z si-id=[EMAIL PROTECTED] href=http://www.google.com Test/indication /si --multipart-boundary-- BINARY MESSAGE binary message:010605AE8DBDC39302056A0045C6080AC3071999062515231510C30720090625152315110335406463682E636F6D000D03676F6F676C652E636F6D00010354657374000101 UDH:0605040B8423F0 CORE LOG (debug) 2008-09-24 08:27:47 [2802] [17] DEBUG: boxc_receiver: got sms from wapbox 2008-09-24 08:27:47 [2802] [17] DEBUG: send_msg: sending msg to box: 127.0.0.1 2008-09-24 08:27:47 [2802] [6] DEBUG: SMPP[movistar_arg]: Sending PDU: 2008-09-24 08:27:47 [2802] [6] DEBUG: SMPP PDU 0x1b117f50 dump: 2008-09-24 08:27:47 [2802] [6] DEBUG: type_name: submit_sm 2008-09-24 08:27:47 [2802] [6] DEBUG: command_id: 4 = 0x0004 2008-09-24 08:27:47 [2802] [6] DEBUG: command_status: 0 = 0x 2008-09-24 08:27:47 [2802] [6] DEBUG: sequence_number: 546 = 0x0222 2008-09-24 08:27:47 [2802] [6] DEBUG: service_type: NULL 2008-09-24 08:27:47 [2802] [6] DEBUG: source_addr_ton: 2 = 0x0002 2008-09-24 08:27:47 [2802] [6] DEBUG: source_addr_npi: 1 = 0x0001 2008-09-24 08:27:47 [2802] [6] DEBUG: source_addr: [protected] 2008-09-24 08:27:47 [2802] [6] DEBUG: dest_addr_ton: 2 = 0x0002 2008-09-24 08:27:47 [2802] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2008-09-24 08:27:47 [2802] [6] DEBUG: destination_addr: [protected] 2008-09-24 08:27:47 [2802] [6] DEBUG: esm_class: 64 = 0x0040 2008-09-24 08:27:47 [2802] [6] DEBUG: protocol_id: 0 = 0x 2008-09-24 08:27:47 [2802] [6] DEBUG: priority_flag: 0
Re: wap push received as garbage
Hi, did you set binary data when you sent the message ? Aarno PS. No, I live in Basel. On 25 Sep 2008, at 18:43, Alex Arias wrote: Hey Aarno, BTW do you live in Helsinki? Because if you do, I live here too so I'll be really happy is you may have 10 min to analyze this problem with me. Let me know Thank you! Alex From: Aarno Syvänen Sent: Thursday, September 25, 2008 10:16 AM To: Alex Arias Cc: users@kannel.org Subject: Re: wap push received as garbage Hi, did you try to send a binary message, or text ? Aarno On 24 Sep 2008, at 17:53, Alex Arias wrote: Hi everybody, I'm trying to send a wap push to an operator via PAP-PPG-SMPP and they get garbage instead of a functional wap push. I'm using Kannel as PPG. The message is accepted OK by Kannel and delivered OK to operator, but they don't get the right message. Thank you so much for your help! Below are the details PAP MESSAGE --multipart-boundary Content-Type: application/xml ?xml version=1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP 1.0//EN http://www.wapforum.org/DTD/pap_1.0.dtd; pap push-message push-id=[EMAIL PROTECTED] deliver-before- timestamp=2009-11-01T06:45:00Z deliver-after- timestamp=2007-02-27T06:45:00Z progress-notes-requested=false address address-value=WAPPUSH=[protected]/[EMAIL PROTECTED] / /push-message /pap --multipart-boundary Content-Type: text/vnd.wap.si ?xml version=1.0? !DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//EN http://www.wapforum.org/DTD/si.dtd; si indication action=signal-high created=1999-06-25T15:23:15Z si- expires=2009-06-25T15:23:15Z si-id=[EMAIL PROTECTED] href=http://www.google.com Test/indication /si --multipart-boundary-- BINARY MESSAGE binary message:010605AE8DBDC39302056A0045C6080AC3071999062515231510C30720090625152315110335406463682E636F6D000D03676F6F676C652E636F6D00010354657374000101 UDH:0605040B8423F0 CORE LOG (debug) 2008-09-24 08:27:47 [2802] [17] DEBUG: boxc_receiver: got sms from wapbox 2008-09-24 08:27:47 [2802] [17] DEBUG: send_msg: sending msg to box: 127.0.0.1 2008-09-24 08:27:47 [2802] [6] DEBUG: SMPP[movistar_arg]: Sending PDU: 2008-09-24 08:27:47 [2802] [6] DEBUG: SMPP PDU 0x1b117f50 dump: 2008-09-24 08:27:47 [2802] [6] DEBUG: type_name: submit_sm 2008-09-24 08:27:47 [2802] [6] DEBUG: command_id: 4 = 0x0004 2008-09-24 08:27:47 [2802] [6] DEBUG: command_status: 0 = 0x 2008-09-24 08:27:47 [2802] [6] DEBUG: sequence_number: 546 = 0x0222 2008-09-24 08:27:47 [2802] [6] DEBUG: service_type: NULL 2008-09-24 08:27:47 [2802] [6] DEBUG: source_addr_ton: 2 = 0x0002 2008-09-24 08:27:47 [2802] [6] DEBUG: source_addr_npi: 1 = 0x0001 2008-09-24 08:27:47 [2802] [6] DEBUG: source_addr: [protected] 2008-09-24 08:27:47 [2802] [6] DEBUG: dest_addr_ton: 2 = 0x0002 2008-09-24 08:27:47 [2802] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2008-09-24 08:27:47 [2802] [6] DEBUG: destination_addr: [protected] 2008-09-24 08:27:47 [2802] [6] DEBUG: esm_class: 64 = 0x0040 2008-09-24 08:27:47 [2802] [6] DEBUG: protocol_id: 0 = 0x 2008-09-24 08:27:47 [2802] [6] DEBUG: priority_flag: 0 = 0x 2008-09-24 08:27:47 [2802] [6] DEBUG: schedule_delivery_time: NULL 2008-09-24 08:27:47 [2802] [6] DEBUG: validity_period: 080925152747000+ 2008-09-24 08:27:47 [2802] [6] DEBUG: registered_delivery: 0 = 0x 2008-09-24 08:27:47 [2802] [6] DEBUG: replace_if_present_flag: 0 = 0x 2008-09-24 08:27:47 [2802] [6] DEBUG: data_coding: 4 = 0x0004 2008-09-24 08:27:47 [2802] [6] DEBUG: sm_default_msg_id: 0 = 0x 2008-09-24 08:27:47 [2802] [6] DEBUG: sm_length: 76 = 0x004c 2008-09-24 08:27:47 [2802] [6] DEBUG: short_message: 2008-09-24 08:27:47 [2802] [6] DEBUG: Octet string at 0x2c000dc0: 2008-09-24 08:27:47 [2802] [6] DEBUG: len: 76 2008-09-24 08:27:47 [2802] [6] DEBUG: size: 1024 2008-09-24 08:27:47 [2802] [6] DEBUG: immutable: 0 2008-09-24 08:27:47 [2802] [6] DEBUG: data: 06 05 04 0b 84 23 f0 01 06 05 ae 8d bd c3 93 02 .#.. 2008-09-24 08:27:47 [2802] [6] DEBUG: data: 05 6a 00 45 c6 08 0a c3 07 19 99 06 25 15 23 15 .j.E%.#. 2008-09-24 08:27:47 [2802] [6] DEBUG: data: 10 c3 07 20 09 06 25 15 23 15 11 03 35 40 64 63 ... [EMAIL PROTECTED] 2008-09-24 08:27:47 [2802] [6] DEBUG: data: 68 2e 63 6f 6d 00 0d 03 67 6f 6f 67 6c 65 2e 63 h.com...google.c 2008-09-24 08:27:47 [2802] [6] DEBUG: data: 6f 6d 00 01 03 54 65 73 74 00 01 01 om...Test... 2008-09-24 08:27:47 [2802] [6] DEBUG: Octet string dump ends. 2008-09-24 08:27:47 [2802] [6] DEBUG: SMPP PDU dump ends. 2008-09-24 08:27:47 [2802] [6] DEBUG: SMPP[movistar_arg]: Got PDU: 2008-09-24 08:27:47 [2802] [6] DEBUG: SMPP PDU 0x2c000d40 dump: 2008-09-24 08:27:47 [2802] [6] DEBUG: type_name: submit_sm_resp 2008-09-24 08:27:47 [2802] [6] DEBUG: command_id: 2147483652 = 0x8004 2008-09-24 08:27:47 [2802
Re: wap push received as garbage
Hi, did you try to send a binary message, or text ? Aarno On 24 Sep 2008, at 17:53, Alex Arias wrote: Hi everybody, I'm trying to send a wap push to an operator via PAP-PPG-SMPP and they get garbage instead of a functional wap push. I'm using Kannel as PPG. The message is accepted OK by Kannel and delivered OK to operator, but they don't get the right message. Thank you so much for your help! Below are the details PAP MESSAGE --multipart-boundary Content-Type: application/xml ?xml version=1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP 1.0//EN http://www.wapforum.org/DTD/pap_1.0.dtd; pap push-message push-id=[EMAIL PROTECTED] deliver-before- timestamp=2009-11-01T06:45:00Z deliver-after- timestamp=2007-02-27T06:45:00Z progress-notes-requested=false address address-value=WAPPUSH=[protected]/ [EMAIL PROTECTED]/ /push-message /pap --multipart-boundary Content-Type: text/vnd.wap.si ?xml version=1.0? !DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//EN http://www.wapforum.org/DTD/si.dtd; si indication action=signal-high created=1999-06-25T15:23:15Z si- expires=2009-06-25T15:23:15Z si-id=[EMAIL PROTECTED] href=http://www.google.com Test/indication /si --multipart-boundary-- BINARY MESSAGE binary message:010605AE8DBDC39302056A0045C6080AC3071999062515231510C30720090625152315110335406463682E636F6D000D03676F6F676C652E636F6D00010354657374000101 UDH:0605040B8423F0 CORE LOG (debug) 2008-09-24 08:27:47 [2802] [17] DEBUG: boxc_receiver: got sms from wapbox 2008-09-24 08:27:47 [2802] [17] DEBUG: send_msg: sending msg to box: 127.0.0.1 2008-09-24 08:27:47 [2802] [6] DEBUG: SMPP[movistar_arg]: Sending PDU: 2008-09-24 08:27:47 [2802] [6] DEBUG: SMPP PDU 0x1b117f50 dump: 2008-09-24 08:27:47 [2802] [6] DEBUG: type_name: submit_sm 2008-09-24 08:27:47 [2802] [6] DEBUG: command_id: 4 = 0x0004 2008-09-24 08:27:47 [2802] [6] DEBUG: command_status: 0 = 0x 2008-09-24 08:27:47 [2802] [6] DEBUG: sequence_number: 546 = 0x0222 2008-09-24 08:27:47 [2802] [6] DEBUG: service_type: NULL 2008-09-24 08:27:47 [2802] [6] DEBUG: source_addr_ton: 2 = 0x0002 2008-09-24 08:27:47 [2802] [6] DEBUG: source_addr_npi: 1 = 0x0001 2008-09-24 08:27:47 [2802] [6] DEBUG: source_addr: [protected] 2008-09-24 08:27:47 [2802] [6] DEBUG: dest_addr_ton: 2 = 0x0002 2008-09-24 08:27:47 [2802] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2008-09-24 08:27:47 [2802] [6] DEBUG: destination_addr: [protected] 2008-09-24 08:27:47 [2802] [6] DEBUG: esm_class: 64 = 0x0040 2008-09-24 08:27:47 [2802] [6] DEBUG: protocol_id: 0 = 0x 2008-09-24 08:27:47 [2802] [6] DEBUG: priority_flag: 0 = 0x 2008-09-24 08:27:47 [2802] [6] DEBUG: schedule_delivery_time: NULL 2008-09-24 08:27:47 [2802] [6] DEBUG: validity_period: 080925152747000+ 2008-09-24 08:27:47 [2802] [6] DEBUG: registered_delivery: 0 = 0x 2008-09-24 08:27:47 [2802] [6] DEBUG: replace_if_present_flag: 0 = 0x 2008-09-24 08:27:47 [2802] [6] DEBUG: data_coding: 4 = 0x0004 2008-09-24 08:27:47 [2802] [6] DEBUG: sm_default_msg_id: 0 = 0x 2008-09-24 08:27:47 [2802] [6] DEBUG: sm_length: 76 = 0x004c 2008-09-24 08:27:47 [2802] [6] DEBUG: short_message: 2008-09-24 08:27:47 [2802] [6] DEBUG: Octet string at 0x2c000dc0: 2008-09-24 08:27:47 [2802] [6] DEBUG: len: 76 2008-09-24 08:27:47 [2802] [6] DEBUG: size: 1024 2008-09-24 08:27:47 [2802] [6] DEBUG: immutable: 0 2008-09-24 08:27:47 [2802] [6] DEBUG: data: 06 05 04 0b 84 23 f0 01 06 05 ae 8d bd c3 93 02 .#.. 2008-09-24 08:27:47 [2802] [6] DEBUG: data: 05 6a 00 45 c6 08 0a c3 07 19 99 06 25 15 23 15 .j.E%.#. 2008-09-24 08:27:47 [2802] [6] DEBUG: data: 10 c3 07 20 09 06 25 15 23 15 11 03 35 40 64 63 ... [EMAIL PROTECTED] 2008-09-24 08:27:47 [2802] [6] DEBUG: data: 68 2e 63 6f 6d 00 0d 03 67 6f 6f 67 6c 65 2e 63 h.com...google.c 2008-09-24 08:27:47 [2802] [6] DEBUG: data: 6f 6d 00 01 03 54 65 73 74 00 01 01 om...Test... 2008-09-24 08:27:47 [2802] [6] DEBUG: Octet string dump ends. 2008-09-24 08:27:47 [2802] [6] DEBUG: SMPP PDU dump ends. 2008-09-24 08:27:47 [2802] [6] DEBUG: SMPP[movistar_arg]: Got PDU: 2008-09-24 08:27:47 [2802] [6] DEBUG: SMPP PDU 0x2c000d40 dump: 2008-09-24 08:27:47 [2802] [6] DEBUG: type_name: submit_sm_resp 2008-09-24 08:27:47 [2802] [6] DEBUG: command_id: 2147483652 = 0x8004 2008-09-24 08:27:47 [2802] [6] DEBUG: command_status: 0 = 0x 2008-09-24 08:27:47 [2802] [6] DEBUG: sequence_number: 546 = 0x0222 2008-09-24 08:27:47 [2802] [6] DEBUG: message_id: 6fa7a87a 2008-09-24 08:27:47 [2802] [6] DEBUG: SMPP PDU dump ends.
Re: wap push received as garbage
Alex, Wap push is a binary-coded message. What PPG does is to transform your request into a binary message, so there's nothing unusual about it. Some carriers does not support sending binary messages on their networks, so maybe the problem is not with your request but with the network. I don't know if that's the case, but if you can test the same message over a different link maybe you can discard this. I've made a small php function that encodes the binary message without using the PPG at all. You can try it if you want, if this also renders garbled text you can be almost certain that there's a problem with the network. Check here: http://www.mail-archive.com/users@kannel.org/msg03255.html Hope it helps, Alejandro Guerrieri On Thu, Sep 25, 2008 at 1:40 PM, Alex Arias [EMAIL PROTECTED] wrote: Hi Aarno, Thank you very much for your reply. I tried to send a wap push (binary). The process is as follows: 1. Wap push sent to Kannel PPG using PAP format 2. Kannel encode the PAP request and send it to the operator via SMPP 3. Operator acknowledges the mesage and deliver it to the phone 4. The phone get weird characters instead of the functional wap push I took the resultant binary message from the smsbox log and posted here Any idea? I believe the problem is in the parameters sent in the SMPP protocol. For example I had to patch Kannel and change the value of esm_class to 0 as the operator rejected the sms. This might be something similar. How do I tell the operator, in the SMPP protocol, that the message is a wap push? What parameters are involved and what should be the right value? Thank you Alex *From:* Aarno Syvänen [EMAIL PROTECTED] *Sent:* Thursday, September 25, 2008 10:16 AM *To:* Alex Arias [EMAIL PROTECTED] *Cc:* users@kannel.org *Subject:* Re: wap push received as garbage Hi, did you try to send a binary message, or text ? Aarno On 24 Sep 2008, at 17:53, Alex Arias wrote: Hi everybody, I'm trying to send a wap push to an operator via PAP-PPG-SMPP and they get garbage instead of a functional wap push. I'm using Kannel as PPG. The message is accepted OK by Kannel and delivered OK to operator, but they don't get the right message. Thank you so much for your help! Below are the details PAP MESSAGE --multipart-boundary Content-Type: application/xml ?xml version=1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP 1.0//EN http://www.wapforum.org/DTD/pap_1.0.dtd; pap push-message push-id=[EMAIL PROTECTED] deliver-before-timestamp=2009-11-01T06:45:00Z deliver-after-timestamp=2007-02-27T06:45:00Z progress-notes-requested=false address address-value=WAPPUSH=[protected]/[EMAIL PROTECTED]/protected/[EMAIL PROTECTED]/ /push-message /pap --multipart-boundary Content-Type: text/vnd.wap.si ?xml version=1.0? !DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//EN http://www.wapforum.org/DTD/si.dtd; si indication action=signal-high created=1999-06-25T15:23:15Z si-expires=2009-06-25T15:23:15Z si-id=[EMAIL PROTECTED] href= http://www.google.com;Test/indicationhttp://www.google.com%22%3ETest%3C/indication /si --multipart-boundary-- BINARY MESSAGE binary message: 010605AE8DBDC39302056A0045C6080AC3071999062515231510C30720090625152315110335406463682E636F6D000D03676F6F676C652E636F6D00010354657374000101 UDH:0605040B8423F0 CORE LOG (debug) 2008-09-24 08:27:47 [2802] [17] DEBUG: boxc_receiver: got sms from wapbox 2008-09-24 08:27:47 [2802] [17] DEBUG: send_msg: sending msg to box: 127.0.0.1 2008-09-24 08:27:47 [2802] [6] DEBUG: SMPP[movistar_arg]: Sending PDU: 2008-09-24 08:27:47 [2802] [6] DEBUG: SMPP PDU 0x1b117f50 dump: 2008-09-24 08:27:47 [2802] [6] DEBUG: type_name: submit_sm 2008-09-24 08:27:47 [2802] [6] DEBUG: command_id: 4 = 0x0004 2008-09-24 08:27:47 [2802] [6] DEBUG: command_status: 0 = 0x 2008-09-24 08:27:47 [2802] [6] DEBUG: sequence_number: 546 = 0x0222 2008-09-24 08:27:47 [2802] [6] DEBUG: service_type: NULL 2008-09-24 08:27:47 [2802] [6] DEBUG: source_addr_ton: 2 = 0x0002 2008-09-24 08:27:47 [2802] [6] DEBUG: source_addr_npi: 1 = 0x0001 2008-09-24 08:27:47 [2802] [6] DEBUG: source_addr: [protected] 2008-09-24 08:27:47 [2802] [6] DEBUG: dest_addr_ton: 2 = 0x0002 2008-09-24 08:27:47 [2802] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2008-09-24 08:27:47 [2802] [6] DEBUG: destination_addr: [protected] 2008-09-24 08:27:47 [2802] [6] DEBUG: esm_class: 64 = 0x0040 2008-09-24 08:27:47 [2802] [6] DEBUG: protocol_id: 0 = 0x 2008-09-24 08:27:47 [2802] [6] DEBUG: priority_flag: 0 = 0x 2008-09-24 08:27:47 [2802] [6] DEBUG: schedule_delivery_time: NULL 2008-09-24 08:27:47 [2802] [6] DEBUG: validity_period: 080925152747000+ 2008-09-24 08:27:47 [2802] [6] DEBUG: registered_delivery: 0 = 0x 2008-09-24 08:27:47 [2802] [6] DEBUG
Re: wap push received as garbage
Hi Alejandro, Thank you for your reply. I already used your funcion (thanks BTW), but unfortunately I got the same results. Below is the log using your function. It produces basically the same parameters as sending through PPG. I believe is the case of an old case from Joaquin Vera with subject Wap push as a text SMS. The problem seems to be in the parameter data_coding that currently is 0x04 but should be 0xf5. Do you know how to change that parameter in Kannel? 2008-09-24 11:18:04 [2802] [19] DEBUG: boxc_receiver: sms received 2008-09-24 11:18:04 [2802] [19] DEBUG: send_msg: sending msg to boxc: ecomm 2008-09-24 11:18:04 [2802] [6] DEBUG: SMPP[smsc_1]: Sending PDU: 2008-09-24 11:18:04 [2802] [6] DEBUG: SMPP PDU 0x2c000d40 dump: 2008-09-24 11:18:04 [2802] [6] DEBUG: type_name: submit_sm 2008-09-24 11:18:04 [2802] [6] DEBUG: command_id: 4 = 0x0004 2008-09-24 11:18:04 [2802] [6] DEBUG: command_status: 0 = 0x 2008-09-24 11:18:04 [2802] [6] DEBUG: sequence_number: 1228 = 0x04cc 2008-09-24 11:18:04 [2802] [6] DEBUG: service_type: NULL 2008-09-24 11:18:04 [2802] [6] DEBUG: source_addr_ton: 2 = 0x0002 2008-09-24 11:18:04 [2802] [6] DEBUG: source_addr_npi: 1 = 0x0001 2008-09-24 11:18:04 [2802] [6] DEBUG: source_addr: 34488 2008-09-24 11:18:04 [2802] [6] DEBUG: dest_addr_ton: 2 = 0x0002 2008-09-24 11:18:04 [2802] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2008-09-24 11:18:04 [2802] [6] DEBUG: destination_addr: [protected] 2008-09-24 11:18:04 [2802] [6] DEBUG: esm_class: 64 = 0x0040 2008-09-24 11:18:04 [2802] [6] DEBUG: protocol_id: 0 = 0x 2008-09-24 11:18:04 [2802] [6] DEBUG: priority_flag: 0 = 0x 2008-09-24 11:18:04 [2802] [6] DEBUG: schedule_delivery_time: NULL 2008-09-24 11:18:04 [2802] [6] DEBUG: validity_period: NULL 2008-09-24 11:18:04 [2802] [6] DEBUG: registered_delivery: 0 = 0x 2008-09-24 11:18:04 [2802] [6] DEBUG: replace_if_present_flag: 0 = 0x 2008-09-24 11:18:04 [2802] [6] DEBUG: data_coding: 4 = 0x0004 2008-09-24 11:18:04 [2802] [6] DEBUG: sm_default_msg_id: 0 = 0x 2008-09-24 11:18:04 [2802] [6] DEBUG: sm_length: 50 = 0x0032 2008-09-24 11:18:04 [2802] [6] DEBUG: short_message: 2008-09-24 11:18:04 [2802] [6] DEBUG:Octet string at 0x2c000f40: 2008-09-24 11:18:04 [2802] [6] DEBUG: len: 50 2008-09-24 11:18:04 [2802] [6] DEBUG: size: 1024 2008-09-24 11:18:04 [2802] [6] DEBUG: immutable: 0 2008-09-24 11:18:04 [2802] [6] DEBUG: data: 06 05 04 0b 84 23 f0 1b 06 01 ae 02 05 6a 00 45 .#...j.E 2008-09-24 11:18:04 [2802] [6] DEBUG: data: c6 0c 03 68 74 74 70 3a 2f 2f 77 77 77 2e 67 6f ...http://www.go 2008-09-24 11:18:04 [2802] [6] DEBUG: data: 6f 67 6c 65 2e 63 6f 6d 00 01 03 74 65 73 74 00 ogle.com...test. 2008-09-24 11:18:04 [2802] [6] DEBUG: data: 01 01 .. 2008-09-24 11:18:04 [2802] [6] DEBUG:Octet string dump ends. 2008-09-24 11:18:04 [2802] [6] DEBUG: SMPP PDU dump ends. 2008-09-24 11:18:04 [2802] [6] DEBUG: SMPP[smsc_1]: Got PDU: 2008-09-24 11:18:04 [2802] [6] DEBUG: SMPP PDU 0x2c000d40 dump: 2008-09-24 11:18:04 [2802] [6] DEBUG: type_name: submit_sm_resp 2008-09-24 11:18:04 [2802] [6] DEBUG: command_id: 2147483652 = 0x8004 2008-09-24 11:18:04 [2802] [6] DEBUG: command_status: 0 = 0x 2008-09-24 11:18:04 [2802] [6] DEBUG: sequence_number: 1228 = 0x04cc 2008-09-24 11:18:04 [2802] [6] DEBUG: message_id: 370c07a 2008-09-24 11:18:04 [2802] [6] DEBUG: SMPP PDU dump ends. From: Alejandro Guerrieri Sent: Thursday, September 25, 2008 8:33 PM To: Alex Arias Cc: Aarno Syvänen ; users@kannel.org Subject: Re: wap push received as garbage Alex, Wap push is a binary-coded message. What PPG does is to transform your request into a binary message, so there's nothing unusual about it. Some carriers does not support sending binary messages on their networks, so maybe the problem is not with your request but with the network. I don't know if that's the case, but if you can test the same message over a different link maybe you can discard this. I've made a small php function that encodes the binary message without using the PPG at all. You can try it if you want, if this also renders garbled text you can be almost certain that there's a problem with the network. Check here: http://www.mail-archive.com/users@kannel.org/msg03255.html Hope it helps, Alejandro Guerrieri On Thu, Sep 25, 2008 at 1:40 PM, Alex Arias [EMAIL PROTECTED] wrote: Hi Aarno, Thank you very much for your reply. I tried to send a wap push (binary). The process is as follows: 1.. Wap push sent to Kannel PPG using PAP format 2.. Kannel encode the PAP request and send it to the operator via SMPP 3.. Operator acknowledges the mesage and deliver it to the phone 4.. The phone get weird characters instead of the functional wap push I took
Re: wap push received as garbage
Hi Alejandro, I see that I have exactly the same problem as Christian Vandrei in this post http://www.mail-archive.com/users@kannel.org/msg08136.html and the same problem as Joaquin Vera in this post http://www.mail-archive.com/users@kannel.org/msg10058.html So both believe that the problem is the data_coding parameter that should be set to something different than 0x04. It should be 0xf5 or 0x05 Christian, Joaquin were you able to solve this already? Thanks Alex From: Alex Arias Sent: Thursday, September 25, 2008 9:48 PM To: Alejandro Guerrieri Cc: Aarno Syvänen ; users@kannel.org Subject: Re: wap push received as garbage Hi Alejandro, Thank you for your reply. I already used your funcion (thanks BTW), but unfortunately I got the same results. Below is the log using your function. It produces basically the same parameters as sending through PPG. I believe is the case of an old case from Joaquin Vera with subject Wap push as a text SMS. The problem seems to be in the parameter data_coding that currently is 0x04 but should be 0xf5. Do you know how to change that parameter in Kannel? 2008-09-24 11:18:04 [2802] [19] DEBUG: boxc_receiver: sms received 2008-09-24 11:18:04 [2802] [19] DEBUG: send_msg: sending msg to boxc: ecomm 2008-09-24 11:18:04 [2802] [6] DEBUG: SMPP[smsc_1]: Sending PDU: 2008-09-24 11:18:04 [2802] [6] DEBUG: SMPP PDU 0x2c000d40 dump: 2008-09-24 11:18:04 [2802] [6] DEBUG: type_name: submit_sm 2008-09-24 11:18:04 [2802] [6] DEBUG: command_id: 4 = 0x0004 2008-09-24 11:18:04 [2802] [6] DEBUG: command_status: 0 = 0x 2008-09-24 11:18:04 [2802] [6] DEBUG: sequence_number: 1228 = 0x04cc 2008-09-24 11:18:04 [2802] [6] DEBUG: service_type: NULL 2008-09-24 11:18:04 [2802] [6] DEBUG: source_addr_ton: 2 = 0x0002 2008-09-24 11:18:04 [2802] [6] DEBUG: source_addr_npi: 1 = 0x0001 2008-09-24 11:18:04 [2802] [6] DEBUG: source_addr: 34488 2008-09-24 11:18:04 [2802] [6] DEBUG: dest_addr_ton: 2 = 0x0002 2008-09-24 11:18:04 [2802] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2008-09-24 11:18:04 [2802] [6] DEBUG: destination_addr: [protected] 2008-09-24 11:18:04 [2802] [6] DEBUG: esm_class: 64 = 0x0040 2008-09-24 11:18:04 [2802] [6] DEBUG: protocol_id: 0 = 0x 2008-09-24 11:18:04 [2802] [6] DEBUG: priority_flag: 0 = 0x 2008-09-24 11:18:04 [2802] [6] DEBUG: schedule_delivery_time: NULL 2008-09-24 11:18:04 [2802] [6] DEBUG: validity_period: NULL 2008-09-24 11:18:04 [2802] [6] DEBUG: registered_delivery: 0 = 0x 2008-09-24 11:18:04 [2802] [6] DEBUG: replace_if_present_flag: 0 = 0x 2008-09-24 11:18:04 [2802] [6] DEBUG: data_coding: 4 = 0x0004 2008-09-24 11:18:04 [2802] [6] DEBUG: sm_default_msg_id: 0 = 0x 2008-09-24 11:18:04 [2802] [6] DEBUG: sm_length: 50 = 0x0032 2008-09-24 11:18:04 [2802] [6] DEBUG: short_message: 2008-09-24 11:18:04 [2802] [6] DEBUG:Octet string at 0x2c000f40: 2008-09-24 11:18:04 [2802] [6] DEBUG: len: 50 2008-09-24 11:18:04 [2802] [6] DEBUG: size: 1024 2008-09-24 11:18:04 [2802] [6] DEBUG: immutable: 0 2008-09-24 11:18:04 [2802] [6] DEBUG: data: 06 05 04 0b 84 23 f0 1b 06 01 ae 02 05 6a 00 45 .#...j.E 2008-09-24 11:18:04 [2802] [6] DEBUG: data: c6 0c 03 68 74 74 70 3a 2f 2f 77 77 77 2e 67 6f ...http://www.go 2008-09-24 11:18:04 [2802] [6] DEBUG: data: 6f 67 6c 65 2e 63 6f 6d 00 01 03 74 65 73 74 00 ogle.com...test. 2008-09-24 11:18:04 [2802] [6] DEBUG: data: 01 01 .. 2008-09-24 11:18:04 [2802] [6] DEBUG:Octet string dump ends. 2008-09-24 11:18:04 [2802] [6] DEBUG: SMPP PDU dump ends. 2008-09-24 11:18:04 [2802] [6] DEBUG: SMPP[smsc_1]: Got PDU: 2008-09-24 11:18:04 [2802] [6] DEBUG: SMPP PDU 0x2c000d40 dump: 2008-09-24 11:18:04 [2802] [6] DEBUG: type_name: submit_sm_resp 2008-09-24 11:18:04 [2802] [6] DEBUG: command_id: 2147483652 = 0x8004 2008-09-24 11:18:04 [2802] [6] DEBUG: command_status: 0 = 0x 2008-09-24 11:18:04 [2802] [6] DEBUG: sequence_number: 1228 = 0x04cc 2008-09-24 11:18:04 [2802] [6] DEBUG: message_id: 370c07a 2008-09-24 11:18:04 [2802] [6] DEBUG: SMPP PDU dump ends. From: Alejandro Guerrieri Sent: Thursday, September 25, 2008 8:33 PM To: Alex Arias Cc: Aarno Syvänen ; users@kannel.org Subject: Re: wap push received as garbage Alex, Wap push is a binary-coded message. What PPG does is to transform your request into a binary message, so there's nothing unusual about it. Some carriers does not support sending binary messages on their networks, so maybe the problem is not with your request but with the network. I don't know if that's the case, but if you can test the same message over a different link maybe you can discard this. I've made a small php function that encodes the binary message without using the PPG at all. You can try it if you want, if this also renders garbled text you
Re: Wap push
Hi Christian, You need to send the User Data Header and the message as binary. There is some further information and an exampel here, http://dev.sellingsource.com/2006/12/07/sending-wap-push-messages-with-kannel-php/ For more information about how to build a wap push message, you should look at the GSM specifications. .. Med venlig hilsen / Best Regards Mads N. Vestergaard Teknisk ansvarlig / CTO CoolSMS www.coolsms.com Phone: +45 7026 1272 Fax:+45 7630 1046 Mobile: +45 4270 1272 This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Den 27/08/2008 kl. 17.29 skrev Christian Jensen: Hi, I have a client that wants to do a simple URL + Title wap push (bookmark i think it is called) Anyone know the simplest way to hit the HTTP interface of kannel? Is this documented somewhere? Thanks! Christian
Re: wap push (PPG)
trusted-pi = false set to true On Tue, Aug 5, 2008 at 8:00 PM, bahassi rim hajar [EMAIL PROTECTED] wrote: hi everyboby, i have a problem with wap push and i don't know what's the matter . this is my configuration : group = core admin-port = 13000 smsbox-port = 13001 wapbox-port = 13002 wdp-interface-name = * admin-password = bar box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 group = sendsms-user username = tester password = foobar max-messages=5 concatenation = true # WAPBOX SETUP, for pushing and for pulling (fetching) the wap data group = wapbox bearerbox-host = 127.0.0.1 #log-file = /tmp/wapbox.log #log-level = 0 #syslog-level = none # PPG CORE SETUP, for defining the push request interface group = ppg ppg-url = /cgi-bin/wap-push ppg-port = 8080 global-sender= 13013 ppg-allow-ip = *.*.*.* concurrent-pushes = 100 ppg-smsbox-id = dlrbox trusted-pi = false users = 1024 # PPG USER SETUP, for authorizing a specific push user group = wap-push-user wap-push-user = tester ppg-username = tester ppg-password = foobar smsbox-id = dlrbox dlr-url=* # SMSC CONNECTIONS, for pushing SI, SL, MMS notifications or whatever over SMS group = smsc smsc = smpp host = * port = * smsc-username = * smsc-password = * system-type = * address-range = * source-addr-ton=1 source-addr-npi=1 # SMSBOX SETUP (a kludge!) group = smsbox bearerbox-host = 127.0.0.1 smsbox-id = dlrbox sendsms-port = 13013 global-sender = 13013 group = sms-service keyword = default text = No service specified when i use this request : http://localhost:8080/cgi-bin/wap-push?username=testerpassword=foobarfrom=13254698to=21261393828text=%3c%3fxml+version%3d%221.0%22%3f%3e%0d%0a%3c!DOCTYPE+si+PUBLIC+%22-%2f%2fWAPFORUM%2f%2fDTD+SI+1.0%2f%2fEN%22%0d%0a%22http%3a%2f%2fwww.wapforum.org%2fDTD%2fsi.dtd%22%3e%0d%0a%3csi%3e%0d%0a%3cindication+href%3d%22http%3a%2f%2fwww.gni.ch%22%0d%0asi-id%3d%221%40gni.ch%22%3e%0d%0aYou+have+4+new+emails%0d%0a%3c%2findication%3e%0d%0a%3c%2fsi%3e i have this message : You are not allowed to use this service. Do not retry. i don't undersand what's matter , pleas help regards Rim _ Envoyez avec Yahoo! Mail. Une boite mail plus intelligente http://mail.yahoo.fr -- Syed Kashif Ali Bukhari +92-300-4295604 http://www.sysadminsline.com http://www.kashifbukhari.com
Re: wap push project
thanks but how can i send the contant to mobile and how i can
tell him where contant location ?
seik [EMAIL PROTECTED] wrote:
in short,
you do not send directly any content to the recipient via wap push
its binary sms providing the receiver's mobile device
with information about the URL of web server hosted content
so in general, via the wap push sms you send the location, i.e. the URL
of a particular file to the client.
its their choice to download the content or not.
-Original Message-
From: mohmmad jarwan [EMAIL PROTECTED]
Sent: 15 ? 2008 ?.
To: seik
Subject:wap push project
Hi
i want to do wap push project to send ringtone and pictuer to mobile
this is my kannel config
/
group = core
admin-port = 15000
admin-password = ros123
admin-deny-ip = *.*.*.*
admin-allow-ip =
wapbox-port = 13002
wdp-interface-name = vas
log-file = /var/log/kannel/bearerbox.log
box-deny-ip = *.*.*.*
box-allow-ip = 127.0.0.1
group = wapbox
bearerbox-host = localhost
log-file = /var/log/kannel/wapbox.log
group = ppg
ppg-url = /wappush
ppg-port = 8080
concurrent-pushes = 50
users = 52
ppg-allow-ip =194.100.32.125;127.0.0.1
trusted-pi = false
group = wap-push-user
wap-push-user = picom
ppg-username = vas
ppg-password = ros123
allow-ip = 62.254.217.163
/
and this is my code
$host = 'localhost';
$port = '8080';
$url = http://$host:$port;;
$wap_push_id = 1;
$xx=http://ci/uploads/$name;;
//$file= bin2hex($xx);
$body = --multipart-boundary\r\n.
Content-type: application/xml\r\n\r\n.
' '.\r\n.
' 'http://www.wapforum.org/DTD/pap_1.0.dtd; '.\r\n.
' '.\r\n.
' '.\r\n.
'
address-value=WAPPUSH='.$phone_no.'/TYPE=PLMN ppg.nokia.com/'.\r\n.
' bearer=SMS/'.
\r\n.
\r\n\r\n.
--multipart-boundary\r\n.
Content-type: text/vnd.wap.si\r\n\r\n.
' '.\r\n.
' 'http://www.wapforum.org/DTD/si.dtd;'.\r\n.
\r\n.
' href='.$push_url.''.$text.' '.\r\n.
\r\n.
--multipart-boundary--\r\n;
$post = POST /wappush HTTP/1.1\r\n.
Host: $host:$port\r\n.
Authorization: Basic .base64_encode($ppg_user:$ppg_pass).\r\n;
X-Kannel-SMSC: $smsc_id\r\n.
'Content-Type: multipart/related; boundary=multipart-boundary;
type=application/xml'.\r\n.
Content-Length: .strlen($body).\r\n.\r\n.$body;
//echo $url;
$ch = curl_init();
curl_setopt ($ch, CURLOPT_URL, $url);
curl_setopt($ch, CURLOPT_HEADER, 1);
curl_setopt($ch, CURLOPT_TIMEOUT, 15);
curl_setopt ($ch,CURLOPT_CUSTOMREQUEST , $post);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$reply = curl_exec($ch);
curl_close ($ch);
if (empty($reply))
{
print Sorry, example.com are a bunch of poopy-heads.
;
}
else
{
print $reply;
}
///
the problem is where and how i put the contant ( ringtone or pictuer . )
and i don't use sms gatway that effect on sending ( must i use it to send mms
).
can any one help me and thanx.
between -00-00 and -99-99
Yahoo! for Good helps you
href=http://us.rd.yahoo.com/mailuk/taglines/isp/control/*http://us.rd.yahoo.com/evt=51947/*http://uk.promotions.yahoo.com/forgood/;make
a difference
___
Yahoo! For Good helps you make a difference
http://uk.promotions.yahoo.com/forgood/
RE: WAP Push format
Hi Juan, I am going through the web page, thanks a lot... Actully, I am having problem with sony ericsson handstes, to be frank I have not tested it with Motorola yetbut thanks for the information... Regards Ashwani -Original Message- From: Juan Nin [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 10:11 PM To: ashwani Subject: Re: WAP Push format Hi Ashwani! Here's the PPG mini HOWTO I sent to the list some time ago: http://article.gmane.org/gmane.comp.mobile.kannel.user/11009/match=ppg+send+ url] It includes sample PHP code for sending Wap Push via PPG question: are the phones not receiving the Wap Push Motorola ones?? many Motorola's like V3's, V300's and others many times come bad configured, and despite the fact that they receive the Wap Push, they don't show it some configuration on MsgBrowser has to be changed for hose to show it I've also seen many times that V3's stop receiving (or showing) Wap Pushes, and you power them off, and then on, and they start receiving hope this helps Juan On Nov 8, 2007 4:46 AM, ashwani [EMAIL PROTECTED] wrote: Hi, I am using kannel 1.4.1, I need to know wap push format which I can use to send WAP Push to the end user using kannel. The format which I am using is not working on some handsets, the message gets delivered on the handset (I can get the delivery notification) but there is nothing on the handsets. Any Help would be appreciated Regards Ashwani Kumar
Re: WAP Push format
Hi, Try using only Content-Length header Aarno On 08 Nov 2007, at 09:17, ashwani wrote: Hi Aarno, Thanks for the information, but if you can explain this little more, it will be very helpful Regards Ashwani From: Aarno Syvänen [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 1:44 PM To: ashwani Cc: users@kannel.org lst Subject: Re: WAP Push format Hi, the problem is that all handsets do not conform with standard formats. One thing to do is to send minimal amount of headers. Aarno On 08 Nov 2007, at 07:46, ashwani wrote: Hi, I am using kannel 1.4.1, I need to know wap push format which I can use to send WAP Push to the end user using kannel. The format which I am using is not working on some handsets, the message gets delivered on the handset (I can get the delivery notification) but there is nothing on the handsets. Any Help would be appreciated Regards Ashwani Kumar
Re: WAP Push format
Hi, the problem is that all handsets do not conform with standard formats. One thing to do is to send minimal amount of headers. Aarno On 08 Nov 2007, at 07:46, ashwani wrote: Hi, I am using kannel 1.4.1, I need to know wap push format which I can use to send WAP Push to the end user using kannel. The format which I am using is not working on some handsets, the message gets delivered on the handset (I can get the delivery notification) but there is nothing on the handsets. Any Help would be appreciated Regards Ashwani Kumar
Re: WAP Push format
On 11/8/07, ashwani [EMAIL PROTECTED] wrote: Hi, I am using kannel 1.4.1, I need to know wap push format which I can use to send WAP Push to the end user using kannel. The format which I am using is not working on some handsets, the message gets delivered on the handset (I can get the delivery notification) but there is nothing on the handsets. Any Help would be appreciated Maybe this article can help you: http://dev.mobi/node/616 -- Andrea Trasatti Personal Blog: http://blog.trasatti.it/
RE: WAP Push
Hi
Thanks, I got it working!!
I am trying to send normal SMS text as well but the sms received contain
garbage. I know it has something to do with encoding but just can't figure
it out.
I need to send both English and Chinese.
Is this the right way to send?
$url = /cgi-bin/sendsms?username= . $CONFIG_KANNEL_USER_NAME
. password= . $CONFIG_KANNEL_PASSWORD
. charset=UCS-2coding=2
. to=$in_phoneNumber
. text= . urlencode( mysql_iconv('utf-8', 'ucs-2', $in_msg) )
. dlr-mask=19;
assuming the first part is correct since the above only shows the part after
the kannel host and port.
Thanks and hope someone would shed some light into this.
Peter
_
From: Ady Wicaksono [mailto:[EMAIL PROTECTED]
Sent: Monday, July 02, 2007 11:18 PM
To: [EMAIL PROTECTED]
Cc: Remon Magdy; Captain Garbage; users@kannel.org
Subject: Re: WAP Push
Seems that's the text message :)
WAP Push as you seen contain text message + URL :)
On 7/2/07, Peter Lum [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
wrote:
Hi Remon
Thanks!
Must I set
smsc=
Udh=%06%05%04%0B%84%23%F0
Text=%1B%06%01%AE%02%05%6A%00%45%C6%0C%03{WAP_URL}%00%01%03{WAP_Push}%00%01%
01
{WAP_URL} should be something like http://wap.somesite.com but
What is the {WAP_Push}?
Thanks and hope to hear from you soon.
Regards,
Peter
-Original Message-
From: Remon Magdy [mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
]
Sent: Monday, July 02, 2007 3:10 PM
To: [EMAIL PROTECTED]; Captain Garbage; users@kannel.org
Subject: RE: WAP Push
Hello Peter,
You can send WAP push by either the WAP Box or through the http get request.
I prefer using the http get request.
Through the http request the body of the message has to be encoded and a UDH
has to be added Here is an example:
http://KANNEL_IP:13013/cgi-bin/sendsms?user=test
http://KANNEL_IP:13013/cgi-bin/sendsms?user=testpass=testfrom=Senderto=2
0 pass=testfrom=Senderto=20
12XXsmsc=TestSMSCudh=%06%05%04%0B%84%23%F0text=%1B%06%01%AE%02%05%6A%
00%45%C6%0C%03{WAP_URL}%00%01%03{WAP_Push}%00%01%01
Just make sure to replace {WAP_URL} and {WAP_Push} in the above URL as
desired for your business.
Regards,
Remon
From: Peter Lum [mailto:[EMAIL PROTECTED]
Sent: Monday, July 02, 2007 3:59 AM
To: 'Captain Garbage'; users@kannel.org
Subject: WAP Push
Hi
How to do a WAP Push?
(a) Must I set up a WAP Box? Yes/No
(b) Can I use the http get request like send SMS to send WAP Push? Yes/No
Thanks and regards,
Peter
--
Regards,
Ady Wicaksono
Email:
ady.wicaksono at gmail.com
RE: WAP Push
Hello Peter,
You can send WAP push by either the WAP Box or through the http get request.
I prefer using the http get request.
Through the http request the body of the message has to be encoded and a UDH
has to be added
Here is an example:
http://KANNEL_IP:13013/cgi-bin/sendsms?user=testpass=testfrom=Senderto=2012XXsmsc=TestSMSCudh=%06%05%04%0B%84%23%F0text=%1B%06%01%AE%02%05%6A%00%45%C6%0C%03{WAP_URL}%00%01%03{WAP_Push}%00%01%01
Just make sure to replace {WAP_URL} and {WAP_Push} in the above URL as desired
for your business.
Regards,
Remon
From: Peter Lum [mailto:[EMAIL PROTECTED]
Sent: Monday, July 02, 2007 3:59 AM
To: 'Captain Garbage'; users@kannel.org
Subject: WAP Push
Hi
How to do a WAP Push?
(a) Must I set up a WAP Box? Yes/No
(b) Can I use the http get request like send SMS to send WAP Push? Yes/No
Thanks and regards,
Peter
RE: WAP Push
Hi Remon
Thanks!
Must I set
smsc=
Udh=%06%05%04%0B%84%23%F0
Text=%1B%06%01%AE%02%05%6A%00%45%C6%0C%03{WAP_URL}%00%01%03{WAP_Push}%00%01%
01
{WAP_URL} should be something like http://wap.somesite.com but
What is the {WAP_Push}?
Thanks and hope to hear from you soon.
Regards,
Peter
-Original Message-
From: Remon Magdy [mailto:[EMAIL PROTECTED]
Sent: Monday, July 02, 2007 3:10 PM
To: [EMAIL PROTECTED]; Captain Garbage; users@kannel.org
Subject: RE: WAP Push
Hello Peter,
You can send WAP push by either the WAP Box or through the http get request.
I prefer using the http get request.
Through the http request the body of the message has to be encoded and a UDH
has to be added Here is an example:
http://KANNEL_IP:13013/cgi-bin/sendsms?user=testpass=testfrom=Senderto=20
12XXsmsc=TestSMSCudh=%06%05%04%0B%84%23%F0text=%1B%06%01%AE%02%05%6A%
00%45%C6%0C%03{WAP_URL}%00%01%03{WAP_Push}%00%01%01
Just make sure to replace {WAP_URL} and {WAP_Push} in the above URL as
desired for your business.
Regards,
Remon
From: Peter Lum [mailto:[EMAIL PROTECTED]
Sent: Monday, July 02, 2007 3:59 AM
To: 'Captain Garbage'; users@kannel.org
Subject: WAP Push
Hi
How to do a WAP Push?
(a) Must I set up a WAP Box? Yes/No
(b) Can I use the http get request like send SMS to send WAP Push? Yes/No
Thanks and regards,
Peter
RE: WAP Push
{WAP_Push} will be displayed to the receiver as message description.
The smsc field is not important as long as you do not want force the message
from a specific smsc.
The UDH is mandatory to be set with the below value.
Note also that the URL should not include the http://; part as it will be
appended automatically when sent to the receiver.
e.g.
Text=%1B%06%01%AE%02%05%6A%00%45%C6%0C%03MyFirstWAP_Push%00%01%03wap.somesite.com%00%01%01
Regards,
Remon
-Original Message-
From: Peter Lum [mailto:[EMAIL PROTECTED]
Sent: Monday, July 02, 2007 12:44 PM
To: Remon Magdy; 'Captain Garbage'; users@kannel.org
Subject: RE: WAP Push
Hi Remon
Thanks!
Must I set
smsc=
Udh=%06%05%04%0B%84%23%F0
Text=%1B%06%01%AE%02%05%6A%00%45%C6%0C%03{WAP_URL}%00%01%03{WAP_Push}%00%01%
01
{WAP_URL} should be something like http://wap.somesite.com but
What is the {WAP_Push}?
Thanks and hope to hear from you soon.
Regards,
Peter
-Original Message-
From: Remon Magdy [mailto:[EMAIL PROTECTED]
Sent: Monday, July 02, 2007 3:10 PM
To: [EMAIL PROTECTED]; Captain Garbage; users@kannel.org
Subject: RE: WAP Push
Hello Peter,
You can send WAP push by either the WAP Box or through the http get request.
I prefer using the http get request.
Through the http request the body of the message has to be encoded and a UDH
has to be added Here is an example:
http://KANNEL_IP:13013/cgi-bin/sendsms?user=testpass=testfrom=Senderto=20
12XXsmsc=TestSMSCudh=%06%05%04%0B%84%23%F0text=%1B%06%01%AE%02%05%6A%
00%45%C6%0C%03{WAP_URL}%00%01%03{WAP_Push}%00%01%01
Just make sure to replace {WAP_URL} and {WAP_Push} in the above URL as
desired for your business.
Regards,
Remon
From: Peter Lum [mailto:[EMAIL PROTECTED]
Sent: Monday, July 02, 2007 3:59 AM
To: 'Captain Garbage'; users@kannel.org
Subject: WAP Push
Hi
How to do a WAP Push?
(a) Must I set up a WAP Box? Yes/No
(b) Can I use the http get request like send SMS to send WAP Push? Yes/No
Thanks and regards,
Peter
Re: WAP Push Error
Sorry, I put the wrong document. I have put the example a friend of mine gave for making wap push. The actual document is this one: POST /wappush?username=foopassword=bar HTTP/1.1 Host: localhost:13014 Content-Type: multipart/related; boundary=asdlfkjiurwghasf; type=application/xml Content-Lenght: 926 --asdlfkjiurwghasf Content-Type: application/xml ?xml version=1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP 1.0//EN http://www.wapforum.org/DTD/pap_1.0.dtd; pap product-name=Muito Curta Push Initiator push-message push-id=1177440196 source-reference=MuitoCurta ppg-notify-requested-to=false address address-value=WAPPUSH=+552181952574/TYPE= [EMAIL PROTECTED]/ /push-message /pap --asdlfkjiurwghasf Content-Type: text/vnd.wap.si ?xml version=1.0? !DOCTYPE si PUBLIC -//WAPFORUM//DTD.SI.1.0//EN http://www.wapforum.org/DTD/si.dtd; si indication href= http://prill.game-host.org:9090/dmc/dmc?objeto=compraracao=consultarcodItem=5codFormato=1codInternet=1codParceiro=04975922000175 Clique aqui para assistir ao vÃdeo no Muito Curta!br / A tarifa de tráfego GPRS será cobrada normalmente na sua próxima fatura. :-) /indication /si --asdlfkjiurwghasf-- 2007/4/24, Alexander Ramos Jardim [EMAIL PROTECTED]: Hello, That is my first post. I am getting an error when I try to send this requisition to Kannel: ** POST /wappush?username=XXXpassword=YYY HTTP/1.1 Content-Type: multipart/related; boundary=multipart-boundary; type=application/xml Autorization: Basic YTph User-Agent: My App WAP Push Host: myapp.com Accept: */* Connection: keep-alive Content-Lenght: 926 --multipart-boundary Content-Type: application/xml ?xml version= 1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP 1.0//EN http://www.wapforum.org/DTD/pap_1.0.dtd pap product-name=My App Push Initiator push-message push-id=1177097317 source-reference=MyApp ppg-notify-requested-to=false address address-value=WAPPUSH=+552181925954/TYPE= [EMAIL PROTECTED]/ /push-message /pap --multipart-boundary Content-Type: text/vnd.wap.si ?xml version=1.0? !DOCTYPE si PUBLIC -//WAPFORUM//DTD.SI.1.0//EN http://www.wapforum.org/DTD/si.dtd; si indication href=http://myapp.com:9090/wappush; MyApp WAP Message :-) /indication /si --multipart-boundary-- The error message I get is this one: 2007-04-20 16:18:11 [3513] [11] DEBUG: HTTP: Creating HTTPClient for `201.37.49.245'. 2007-04-20 16:18:11 [3513] [11] DEBUG: HTTP: Created HTTPClient area 0x81908e8. 2007-04-20 16:18:11 [3513] [14] WARNING: Your ppg core configuration allow all ips 2007-04-20 16:18:11 [3513] [14] INFO: PPG: Accept request /wappush from 201.37.49.245 2007-04-20 16:18:11 [3513] [14] WARNING: PPG: No MIME content received, the request unacceptable 2007-04-20 16:18:11 [3513] [14] DEBUG: PPG: send_bad_message_response: telling pi 2007-04-20 16:18:11 [3513] [14] DEBUG: HTTP: Resetting HTTPClient for `201.37.49.245'. 2007-04-20 16:19:11 [3513] [10] DEBUG: Timeout for fd:40 appeares. 2007-04-20 16:19:11 [3513] [10] DEBUG: HTTP: Destroying HTTPClient area 0x81908e8. 2007-04-20 16:19:11 [3513] [10] DEBUG: HTTP: Destroying HTTPClient for `201.37.49.245'. Does anyone have any idea of what is hapening? -- Alexander Ramos Jardim Prill Tecnologia [EMAIL PROTECTED] Cel: 55 21 8123-1240 http://www.prill.com.br -- Alexander Ramos Jardim Prill Tecnologia [EMAIL PROTECTED] Cel: 55 21 8123-1240 http://www.prill.com.br
Re: WAP Push to a variety of phones/carriers
Many US operators simply don't allow binary messages to pass and Verizon is CDMA... let's wait the get to the modern age :-D Julien Justin Foell ha scritto: Hello, I have kannel working on Linux 2.6.19 sending SMS through a MultiTech modem with a T-Mobile SIM card. However, I only seem to be able to send (successfully) WAP Push messages to T-Mobile phones. I have used test_ppg with a SI and PAP document, as well as sending a raw wbxml encoded SI document to http://localhost:13013/cgi-bin/sendsms. Both of these worked for WAP enabled T-Mobile phones, but not others. Is there anything I can do with the wbxml message or udh to successfully deliver WAP Push messages to phones on other (non-T-mobile) carriers like Cingular, Sprint, Verizon, et. al? Are there any already-known hurdles preventing me from accomplish this? -- Justin Foell Software Architect The Selling Source, Inc. Technology Driven Marketing Solutions http://.SellingSource.com http://.sellingsource.com/ [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Direct P: 702-407-0707 ext. 2188 F: 702-407-0711 P: 800-397-7706
Re: Wap Push
Pyro Surya wrote:
Hi,
I'm new to the kannel wap gateway..
I've configured the Kannel gateway... (attached the config file)
I'want to wappush to nokia 7210 simulator, I'm using Linux and wine for
7210.
I've tried the wappush using the following control and content entities:
si.txt :
?xml version=1.0?
!DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//EN
http://www.wapforum.org/DTD/si.dtd;
si
indication href=http://wap.google.com;
si-id= [EMAIL PROTECTED]
action=signal-high
created=1999-06-25T15:23:15Z
si-expires=2005-06-30T00:00:00Z
You have 4 new emails
/indication
/si
first mistake here. See the 'si-expires' attribute. It's obviously in the
past. So even if we do send the SI document to the client, it will silently
ignore, since the expires timestamp is in the past.
Make sure times are accurate!
pap contro: iptestppg.txt
?xml version=1.0?
!DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP//EN
http://www.wapforum.org/DTD/pap_1.0.dtd;
pap
push-message push-id=[EMAIL PROTECTED]
deliver-after-timestamp=2001-02-28T06:45:00Z
progress-notes-requested=false
address address-value=WAPPUSH=127.0.0.1/[EMAIL PROTECTED]
/address
quality-of-service
priority=low
delivery-method=unconfirmed
bearer-required=true
bearer=csd
network-required=true
network=gsm
/quality-of-service
/push-message
/pap
Started the bearer box: ./bearerbox -v 1 mygw.conf
Started the wapbox:./wapbox -v 1 mygw.conf
Started the test http server which uses theport 8080: ./test_http_server
Started the 7210 simulator: $ wine 7210.exe -classpath
'/opt/Nokia/Devices/Nokia_7210_MIDP_SDK_v1_0/lib/classes.zip
Done the wappush:
./test_ppg
http://localhost:8080/cgi-bin/wappush.cgi?username=suryapassword=password;
si.txt iptestppg.txt
The test_http_server says (I have attached the output ):
2007-03-14 10:23:59 [28832] [1] DEBUG: Octet string dump ends.
Entity: line 1: parser error : Start tag expected, '' not found
Sent.
^
2007-03-14 10:23:59 [28832] [1] WARNING: PAP COMPILER: pap_compile: parse
error in pap source
2007-03-14 10:23:59 [28832] [1] WARNING: TEST_PPG: receive_push_reply:
cannot compile pap message
obviously the PAP compiler shouts here to have an XML parsing error.
Are you sure the PAP document is XML valid in terms of structure?
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: Wap push help!!!
Hi Tushar, Configuration for PPG is very simple. You just follow the Kannel-UserGuide. You can also post your present configuration. To send Push: 1) You can use test_ppg (which is under kannel_gateway source. 2) You can also write PHP/Java/.Net application to push sms. regards, Prasad On 1/19/07, Tushar [EMAIL PROTECTED] wrote: Hi, I tried to configure PPG but then also I was unable to send a web push…..Can u help me with the configuration settings…..and more over plz tell me, wot I have to do for sending a push? Thanks and regards, Tushar
RE: WAP Push Over CDMA Network
Every so many months people ask me about it. For me it is the same if I post the diff every so many months. Or mail it to them directly. Rene Kluwen Chimit -Original Message- From: Julien Buratto [mailto:[EMAIL PROTECTED] Sent: woensdag 18 oktober 2006 11:37 To: Rene Kluwen Cc: 'Fajar'; 'Kannel Users' Subject: Re: WAP Push Over CDMA Network Wouldn't be a good idea to post the diff ? Julien Rene Kluwen ha scritto: I am not sure if you are from the same company as the person as I spoke to earlier this week. Also I am not sure if your problem is the same as I have solved for another company earlier this year. But I do have a patch for Kannel that solves sending WAP Pushes over sending CDMA networks. It works by replacing a submit_sm pdu with a data_sm pdu. It is open source. Let me know if you are interested to try it out. Rene Kluwen Chimit -Original Message- *From:* Fajar [mailto:[EMAIL PROTECTED] *Sent:* dinsdag 17 oktober 2006 6:11 *To:* Kannel Users *Subject:* WAP Push Over CDMA Network Hello there, I'm connecting to SMPP server our telco company. We would like to send wap push that will be sent into cdma mobile. Is Kannel supporting this feature? I'm settingup ppg, but it seems the wap push never get sent into mobile? Maybe someone willing helping me out. Thanks Fajar -- Il messaggio risulta non infetto. Linkas Srl
RE: WAP Push Over CDMA Network
Title: Message It is still SMS as in short-message service. It is not SMS as in the GSM-MAP standard. In stead they have a similar implementation called IS-41. Rene Kluwen Chimit -Original Message-From: Andrea Trasatti [mailto:[EMAIL PROTECTED] Sent: woensdag 18 oktober 2006 14:46To: Kannel UsersCc: Rene KluwenSubject: Re: WAP Push Over CDMA NetworkI would be interested to know more about this patch too.On how many devices does this work?Originally CDMA did not have SMS and my understanding is that what they have now is an emulation, not the real SMS as in the GSM standard. - Andrea On 10/18/06, Julien Buratto [EMAIL PROTECTED] wrote: Wouldn't be a good idea to post the diff ?JulienRene Kluwen ha scritto: I am not sure if you are from the same company as the person as I spoke to earlier this week. Also I am not sure if your problem is the same as I have solved for another company earlier this year. But I do have a patch for Kannel that solves sending WAP Pushes over sending CDMA networks. It works by replacing a submit_sm pdu with a data_sm pdu. It is open source. Let me know if you are interested to try it out. Rene Kluwen Chimit -Original Message- *From:* Fajar [mailto: [EMAIL PROTECTED]] *Sent:* dinsdag 17 oktober 2006 6:11 *To:* Kannel Users *Subject:* WAP Push Over CDMA Network Hello there, I'm connecting to SMPP server our telco company. We would like to send wap push that will be sent into cdma mobile. Is Kannel supporting this feature? I'm settingup ppg, but it seems the wap push never get sent into mobile? Maybe someone willing helping me out. Thanks Fajar -- Il messaggio risulta non infetto. Linkas Srl-- Andrea Trasatti[EMAIL PROTECTED]Personal Blog: http://trasatti.blogspot.com
Re: WAP Push Over CDMA Network
On Wed, Oct 18, 2006 at 02:45:59PM +0200, Andrea Trasatti wrote: AT I would be interested to know more about this patch too. AT AT On how many devices does this work? AT Originally CDMA did not have SMS and my understanding is that what they have AT now is an emulation, not the real SMS as in the GSM standard. AT AT - Andrea AT Heh. Please, go to http://www.tiaonline.org/standards/technology/cdma2000/cdma2000table.cfm and read TIA/EIA-637-B. -- Regards, Alex Antropoff
Re: WAP Push Over CDMA Network
Wouldn't be a good idea to post the diff ? Julien Rene Kluwen ha scritto: I am not sure if you are from the same company as the person as I spoke to earlier this week. Also I am not sure if your problem is the same as I have solved for another company earlier this year. But I do have a patch for Kannel that solves sending WAP Pushes over sending CDMA networks. It works by replacing a submit_sm pdu with a data_sm pdu. It is open source. Let me know if you are interested to try it out. Rene Kluwen Chimit -Original Message- *From:* Fajar [mailto:[EMAIL PROTECTED] *Sent:* dinsdag 17 oktober 2006 6:11 *To:* Kannel Users *Subject:* WAP Push Over CDMA Network Hello there, I'm connecting to SMPP server our telco company. We would like to send wap push that will be sent into cdma mobile. Is Kannel supporting this feature? I'm settingup ppg, but it seems the wap push never get sent into mobile? Maybe someone willing helping me out. Thanks Fajar -- Il messaggio risulta non infetto. Linkas Srl
Re: WAP Push Over CDMA Network
I would be interested to know more about this patch too.On how many devices does this work?Originally CDMA did not have SMS and my understanding is that what they have now is an emulation, not the real SMS as in the GSM standard. - AndreaOn 10/18/06, Julien Buratto [EMAIL PROTECTED] wrote: Wouldn't be a good idea to post the diff ?JulienRene Kluwen ha scritto: I am not sure if you are from the same company as the person as I spoke to earlier this week. Also I am not sure if your problem is the same as I have solved for another company earlier this year. But I do have a patch for Kannel that solves sending WAP Pushes over sending CDMA networks. It works by replacing a submit_sm pdu with a data_sm pdu. It is open source. Let me know if you are interested to try it out. Rene Kluwen Chimit -Original Message- *From:* Fajar [mailto: [EMAIL PROTECTED]] *Sent:* dinsdag 17 oktober 2006 6:11 *To:* Kannel Users *Subject:* WAP Push Over CDMA Network Hello there, I'm connecting to SMPP server our telco company. We would like to send wap push that will be sent into cdma mobile. Is Kannel supporting this feature? I'm settingup ppg, but it seems the wap push never get sent into mobile? Maybe someone willing helping me out. Thanks Fajar -- Il messaggio risulta non infetto. Linkas Srl-- Andrea Trasatti [EMAIL PROTECTED]Personal Blog: http://trasatti.blogspot.com
Re :RE: WAP Push Over CDMA Network
hi,I wud like to know more about the patch, wud also like to get the same.Regardssandesh k"Rene Kluwen" wroteMessageI am not sure if you are from the same company as the person as I spoke to earlier this week.Also I am not sure if your problem is the same as I have solved for another company earlier this year.But I do have a patch for Kannel that solves sending WAP Pushes over sending CDMA networks.It works by replacing a submit_sm pdu with a data_sm pdu.It is open source. Let me know if you are interested to try it out.Rene KluwenChimit-Original Message-From: Fajar [mailto:[EMAIL PROTECTED] Sent: dinsdag 17 oktober 2006 6:11To: Kannel UsersSubject: WAP Push Over CDMA NetworkHello there,I'm connecting to SMPP server our telco company. We would like to send wap push that will be sent into cdma mobile. Is Kannel supporting this feature? I'm settingup ppg, but it seems the wap push never get sent into mobile? Maybe someone willing helping me out.ThanksFajar
Re: WAP Push Over CDMA Network
Hello Fajar, Kannel does support this feature, the problem is CDMA operators inIndonesia does not support the feature. They all implement the OMA DRM method for content delivery. CMIIW ;) Regards Willy - Original Message - From: Fajar To: Kannel Users Sent: Tuesday, October 17, 2006 11:11 AM Subject: WAP Push Over CDMA Network Hello there, I'm connecting to SMPP server our telco company. We would like to send wap push that will be sent into cdma mobile. Is Kannel supporting this feature? I'm settingup ppg, but it seems the wap push never get sent into mobile? Maybe someone willing helping me out. Thanks Fajar
RE: WAP Push Over CDMA Network
Title: Message I am not sure if you are from the same company as the person as I spoke to earlier this week. Also I am not sure if your problem is the same as I have solved for another company earlier this year. But I do have a patch for Kannel that solves sending WAP Pushes over sending CDMA networks. It works by replacing a submit_sm pdu with a data_sm pdu. It is open source. Let me know if you are interested to try it out. Rene Kluwen Chimit -Original Message-From: Fajar [mailto:[EMAIL PROTECTED] Sent: dinsdag 17 oktober 2006 6:11To: Kannel UsersSubject: WAP Push Over CDMA Network Hello there, I'm connecting to SMPP server our telco company. We would like to send wap push that will be sent into cdma mobile. Is Kannel supporting this feature? I'm settingup ppg, but it seems the wap push never get sent into mobile? Maybe someone willing helping me out. Thanks Fajar
Re: WAP PUSH not received in some mobile phones
Hey, On the blackberry there is a security setting. The user can turn them on and off. Its the same on quite a few phones (I saw a motorola on the weekend and I have seen nokias like it). The standard security setting on windows mobile does now allow WAP push either and you can't even configure this. A lot of new phones highlight links in SMS the same way as you mail client do. We use that a lot now as well. All in all its a complete mine field. Gareth On 5 Sep 2006, at 16:37, Christian Vandrei wrote: Hi, I made the same experience with Wap-Push messages on Blackberry. As far as I found it can only be solved by using some kind of Blackberry-Gateway. In case I might at least partially right, I'll be delighted receiving further enlightment=). Ciao, Chris. [EMAIL PROTECTED] wrote: I have been sending/receiving SMS with kannel for years without a problem, and now I am investigating wap push. I have configured the following groups: wapbox, ppg and wap-push-user. After that I have created a test si.xml and pap.xml files, and tried them with test_ppg. The problem I am experiencing is that the SMS is not delivered to certain mobile phones, at least Blackberry 7100, Blackberry 7730 and Movistar TSM7 (all are modern mobiles, and recieve wap push from other sources) don't receive the SMS. Sending the binary code directly to the HTTP interface produces the same bad result. Is wap push mobile-dependent? How can I send a device-independent wap-push? Regards, J.L. __ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com -- Gareth Reakes, Managing Director Embrace Mobile +44-1865-811197 http://www.embracemobile.com
Re: WAP Push to Motorola
Hi Alberto, Thanks for your java code, it works for me too. Here is the PDU in my kannel log :0051000B910631136858F90004A7860605040B8423F002062DAEBD809F80A94A6176612F312E352E305F3036008082809D809E80062A00802E3200800580802E32008DCFC39302056A0045C60811037072617361644034343334352E636F6D000C037761702E7961686F6F2E636F6D000103446F776E6C6F61642074686520466F6F64726567204170706C69636174696F6E000101 I am also attaching my content ...***8-// appending message buffer.append(--asdlfkjiurwgasf\r\n) .append(Content-Type: application/xml\r\n\r\n) .append(?xml version=\1.0\?\r\n) .append(!DOCTYPE pap PUBLIC \-//WAPFORUM//DTD PAP//EN\\r\n) .append(\ http://www.wapforum.org/DTD/pap_1.0.dtd\\r\n) .append(pap\r\n) .append(push-message push-id=\) .append(vMessageID.trim()) .append(\\r\n deliver-before-timestamp=\2007-09-28T06:45:00Z\ \r\n) .append(deliver-after-timestamp=\2006-07-28T06:45:00Z\ ) .append(progress-notes-requested=\true\\r\n) .append(address address-value=\WAPPUSH=) .append(target) .append(/TYPE=PLMN\/\r\n) .append(quality-of-service delivery-method=\unconfirmed\\r\nnetwork-required=\true\\r\n network=\GSM\\r\nbearer-required=\true\\r\nbearer=\SMS\/) .append(/push-message\r\n) .append(/pap\r\n\r\n) .append(--asdlfkjiurwgasf\r\n) .append(Content-Type: text/vnd.wap.si\r\n\r\n) .append(?xml version=\1.0\?\r\n) .append(!DOCTYPE si PUBLIC \-//WAPFORUM//DTD SI 1.0//EN\\r\n) .append(\ http://www.wapforum.org/DTD/si.dtd\\r\n) .append(si\r\n) .append(indication action="" si-id=\) .append(vMessageID) .append(\ href=""> .append(http://wap.yahoo.com) .append(\) .append(Download the Foodreg Application) .append(/indication\r\n) .append(/si\r\n) .append( --asdlfkjiurwgasf--\r\n\r\n);-***- Thanks and all the best.Prasad
Re: WAP Push to Motorola
I am posting the PDU sent by the bearernode after a test_ppg push (smsc is at2): 0051000B914396995776F10004A7 4B0605040B8423F00B061AAE8713806561676C65657965006561676C65657965008DA7C39302056A0045C60C03726967612E636F6D000AC3072004120410294008010350696E636861000101 I have not found your PHP script to compare the generated PDU. I am contacting you in private. Thanks for your help, Alberto On Monday 28 August 2006 23:46, Alejandro Guerrieri wrote: AFAIK, any correctly compiled wap-push should work. I use a php script to manually encode the wap-pushes and, besides not being notified, never had any problems with motorolas. The source it's on the list archives (let me know if you cant' find it). Are you in Spain? I can also try sending a wap-push from our platform to that Motorola so you can discard a phone bug or any other network-related problem. Contact me in private if you wish (I speak spanish if you prefer). Hope it helps, On 8/28/06, Alberto Devesa [EMAIL PROTECTED] wrote: Thank you Linkas and Alejandro for your response. I have checked every where in the configuration of the phone and I can't see the message anywhere. Indeed what is more strange is that I have tested downloading a melody from a third party vendor (I think it was from movilisto) and the wappush gets delivered perfectly. Do you know if wp to Motorola has to be encoded in a different way from the ones to Nokia, Sony, etc ? Regards, Alberto On Sunday 27 August 2006 23:35, Linkas wrote: Also Sony Ericsson P800 don't notify, but saves the wappushes into the bookmarks! J Alejandro Guerrieri ha scritto: Are you sure that they are not being delivered unnoticed? Some Motorolas doesn't notify you when the wap-push arrives. I don't know why, but they seem to do just that. I'm not sure if it's a design feature, a bug or if you should set some flag on the wap-push pdu to make them behave the right way and notify you when a wap-push arrives. Try manually checking on the Service Inbox if the messages are not just lying there unnoticed, it happened to me before... Also check if your phone message memory's not full. Try deleting some messages from the inboxes. Hope it helps, Alejandro. On 8/26/06, Alberto Devesa [EMAIL PROTECTED] wrote: Hello, I have not any problem sending wap pushes to several models of Nokia and Sony phones but it seems that the Motorolas ignore the messages. I have tried with V3 and C385 models. Do this phones need something different to get the wp delivered ? I have tested it from Java code as well with the familiar test_ppg using the following pap and si files: ?xml version=1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP 1.0//EN http://www.wapforum.org/DTD/pap_1.0.dtd; pap push-message push-id= source-reference=EagleEye address address-value=WAPPUSH=+34x/TYPE=PLMN/ quality-of-service delivery-method=unconfirmed network=GSM bearer=SMS/ /push-message /pap ?xml version=1.0? !DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//EN http://www.wapforum.org/DTD/si.dtd; si indication href=http:/riga.com created=2004-12-04T10:29:40Z action=signal-highAlert/indication /si Regards, Alberto
Re: WAP Push to Motorola
Hi Prasad,
Can you please send me the PDU that you are sending so I can compare it with
the one that is not working for me ?
BTW this is the Java code I use to to connect to the PPG:
-
public void sendWAPPush(String ppgUrl, String ppgUser, String ppgPasswd,
String to, String href, String payload) throws PPGException{
try {
LOGGER.debug(Connecting to PPG at: + ppgUrl);
URL url = new URL(ppgUrl);
URLConnection urlConn = url.openConnection();
//Set Authorization params if needed
if (ppgUser != null ppgPasswd != null
!ppgUser.equals() !ppgPasswd.equals()) {
LOGGER.debug(Setting HTTP Authentication);
String userPasswd = ppgUser + : + ppgPasswd;
String upEnc = new BASE64Encoder().
encode(userPasswd.getBytes());
urlConn.setRequestProperty (Authorization, Basic +
upEnc);
}
urlConn.setDoInput(true);
urlConn.setDoOutput(true);
urlConn.setUseCaches(false);
urlConn.setRequestProperty(Content-Type,
multipart/related; boundary= + BOUNDARY +
; type=application/xml);
DataOutputStream output =
new DataOutputStream(urlConn.getOutputStream());
String content = getContent(to, href, payload);
LOGGER.debug(Sending to PPG: + content);
output.writeBytes(content);
output.flush();
output.close();
BufferedReader input =
new BufferedReader(
new InputStreamReader(urlConn.getInputStream()));
LOGGER.info(Received from PPG: );
boolean responseOK = false;
String response = null;
while ((response = input.readLine()) != null) {
LOGGER.info(response);
if (response.indexOf(1001) != -1) {
responseOK = true;
}
}
if (!responseOK) {
throw new Exception(PPG did not accept the message);
}
} catch (Exception e) {
LOGGER.error(Catched Exception, e);
throw new PPGException(Error accessing PPG, e);
}
}
-
Hope it helps.
Regards,
Alberto
On Tuesday 29 August 2006 04:54, Kavuri Prasad wrote:
Hi Alberto,
I am using Motorola Phone. I have no problem in receiving WAP Push using
test_ppg. Now Iam trying with Java codes and I do not know How to send it
from Java. Can you please help me by posting your java codes.
Thanks,
Prasad
On 8/26/06, Alberto Devesa [EMAIL PROTECTED] wrote:
Hello,
I have not any problem sending wap pushes to several models of Nokia and
Sony
phones but it seems that the Motorolas ignore the messages. I have tried
with
V3 and C385 models. Do this phones need something different to get the wp
delivered ?
I have tested it from Java code as well with the familiar test_ppg using
the
following pap and si files:
?xml version=1.0?
!DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP 1.0//EN
http://www.wapforum.org/DTD/pap_1.0.dtd;
pap
push-message push-id=
source-reference=EagleEye
address address-value=WAPPUSH=+34x/TYPE=PLMN/
quality-of-service
delivery-method=unconfirmed
network=GSM bearer=SMS/
/push-message
/pap
?xml version=1.0?
!DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//EN
http://www.wapforum.org/DTD/si.dtd;
si
indication href=http:/riga.com
created=2004-12-04T10:29:40Z
action=signal-highAlert/indication
/si
Regards,
Alberto
Re: WAP Push to Motorola
Alberto, http://www.mail-archive.com/users@kannel.org/msg03255.html Hope it helps, On 8/29/06, Alberto Devesa [EMAIL PROTECTED] wrote: I am posting the PDU sent by the bearernode after a test_ppg push (smsc is at2): 0051000B914396995776F10004A7 4B0605040B8423F00B061AAE8713806561676C65657965006561676C65657965008DA7C39302056A0045C60C03726967612E636F6D000AC3072004120410294008010350696E636861000101 I have not found your PHP script to compare the generated PDU. I am contacting you in private. Thanks for your help, Alberto On Monday 28 August 2006 23:46, Alejandro Guerrieri wrote: AFAIK, any correctly compiled wap-push should work. I use a php script to manually encode the wap-pushes and, besides not being notified, never had any problems with motorolas. The source it's on the list archives (let me know if you cant' find it). Are you in Spain? I can also try sending a wap-push from our platform to that Motorola so you can discard a phone bug or any other network-related problem. Contact me in private if you wish (I speak spanish if you prefer). Hope it helps, On 8/28/06, Alberto Devesa [EMAIL PROTECTED] wrote: Thank you Linkas and Alejandro for your response. I have checked every where in the configuration of the phone and I can't see the message anywhere. Indeed what is more strange is that I have tested downloading a melody from a third party vendor (I think it was from movilisto) and the wappush gets delivered perfectly. Do you know if wp to Motorola has to be encoded in a different way from the ones to Nokia, Sony, etc ? Regards, Alberto On Sunday 27 August 2006 23:35, Linkas wrote: Also Sony Ericsson P800 don't notify, but saves the wappushes into the bookmarks! J Alejandro Guerrieri ha scritto: Are you sure that they are not being delivered unnoticed? Some Motorolas doesn't notify you when the wap-push arrives. I don't know why, but they seem to do just that. I'm not sure if it's a design feature, a bug or if you should set some flag on the wap-push pdu to make them behave the right way and notify you when a wap-push arrives. Try manually checking on the Service Inbox if the messages are not just lying there unnoticed, it happened to me before... Also check if your phone message memory's not full. Try deleting some messages from the inboxes. Hope it helps, Alejandro. On 8/26/06, Alberto Devesa [EMAIL PROTECTED] wrote: Hello, I have not any problem sending wap pushes to several models of Nokia and Sony phones but it seems that the Motorolas ignore the messages. I have tried with V3 and C385 models. Do this phones need something different to get the wp delivered ? I have tested it from Java code as well with the familiar test_ppg using the following pap and si files: ?xml version=1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP 1.0//EN http://www.wapforum.org/DTD/pap_1.0.dtd; pap push-message push-id= source-reference=EagleEye address address-value=WAPPUSH=+34x/TYPE=PLMN/ quality-of-service delivery-method=unconfirmed network=GSM bearer=SMS/ /push-message /pap ?xml version=1.0? !DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//EN http://www.wapforum.org/DTD/si.dtd; si indication href=http:/riga.com created=2004-12-04T10:29:40Z action=signal-highAlert/indication /si Regards, Alberto -- Alejandro Guerrieri Magicom http://www.magicom-bcn.net/ LinkedIn: http://www.linkedin.com/in/aguerrieri
Re: Wap push sanity check
First byte of UDH should be the udh lenght. In your example you have a UDHL of
0B while the lenght of your header is 06.
Am i missing something ?
On Thursday 24 August 2006 06:48, Mi Reflejo wrote:
I post wappushes constructing the pdu by hand too.
With some phones i has problems putting the http://;
Please try $submittedwappushurl = urlencode(www.google.com); //without
http://
PD: If it don't work. Take a look to this working pdu, may help you:
0B05040B8423F0 (udh)
0003 (wappush)
95 (serialID)
0101 ( one message of one )
DC0601AE02056A0045C60C03
7761702E676F6F676C652E636F6D (url)
00010344657363617267612079612022476F6F676C6522 (Message)
000101
Martin.
On 8/22/06, Alex Kinch [EMAIL PROTECTED] wrote:
Hi Aarno
Must admit I haven't tried it yet, I've just been using PHP to
construct and send a wap push via the normal sendsms http interface.
Also tried it via sqlbox and no luck.
Will have a go with PPG and let you know how it goes..
Alex
On 8/21/06, Aarno Syvänen [EMAIL PROTECTED] wrote:
Hello,
does PPG work ?
Aarno
On 18 Aug 2006, at 23:12, Alex Kinch wrote:
Hello,
Seem to be having some problems with WAP push. The code to construct
the UDH and message is below. It used to work, but then somewhere
along the line it stopped.
Tried to both Nokia and SonyEricsson handsets, and both are ignoring
the message.
If someone could take a look and make sure my construction techniques
are right I would appreciate it.
Thanks,
Alex
$from = Sender;
$to = 44xxx;
function hex_encode( $text, $joiner='' ) {
for ($l=0; $lstrlen($text); $l++) {
$letter = substr($text, $l, 1);
$ret .= sprintf(%s%02X, $joiner, ord($letter));
}
return $ret;
}
$submittedwappushurl = urlencode(http://www.google.com;);
$submittedwappushtext = test;
// override messagebody with wappush and set udh
$messageudh = %06%05%04%0B%84%23%F0;
$messagebody =
%1B%06%01%AE%02%05%6A%00%45%C6%0C%03.hex_encode
($submittedwappushurl,'%').%00%01%03.hex_encode
($submittedwappushtext,'%').%00%01%01;
Re: WAP Push to Motorola
Hi Alejandro, I have tested your script and it works perfectly :-), I received the push in the Motorola C385... now the question is... why ? ;-) The PDU sent is the following: 005100098196995776F10004A7 2B0605040B8423F01B0601AE02056A0045C60C037761702E6E6F6B69612E646500010350696E636861000101 It differs very much from the one sent by kannel PPG using my PAP and SI documents. I guess that your hardcoded PDU belongs to a PAP/SI different from the ones I am using and that should be the reason why the PDUs differ. So, if I used that PAP/SI documents, the PDU generated by Kannel should be the same as your hardcoded PDU. Do you have that PAP/SI documents ? It will be also great to get the specifications of WP to know what each byte in the PDU means (it is incredible but I cannot find it anywhere) and that way I could also build the PAP/SI documents from the PDU. P.D: You have won a beer my friend ! I would be happy to invite you. Thanks, Alberto On Tuesday 29 August 2006 19:56, Alejandro Guerrieri wrote: Alberto, http://www.mail-archive.com/users@kannel.org/msg03255.html Hope it helps, On 8/29/06, Alberto Devesa [EMAIL PROTECTED] wrote: I am posting the PDU sent by the bearernode after a test_ppg push (smsc is at2): 0051000B914396995776F10004A7 4B0605040B8423F00B061AAE8713806561676C65657965006561676C65657965008DA7C39 302056A0045C60C03726967612E636F6D000AC3072004120410294008010350696E6368610 00101 I have not found your PHP script to compare the generated PDU. I am contacting you in private. Thanks for your help, Alberto On Monday 28 August 2006 23:46, Alejandro Guerrieri wrote: AFAIK, any correctly compiled wap-push should work. I use a php script to manually encode the wap-pushes and, besides not being notified, never had any problems with motorolas. The source it's on the list archives (let me know if you cant' find it). Are you in Spain? I can also try sending a wap-push from our platform to that Motorola so you can discard a phone bug or any other network-related problem. Contact me in private if you wish (I speak spanish if you prefer). Hope it helps, On 8/28/06, Alberto Devesa [EMAIL PROTECTED] wrote: Thank you Linkas and Alejandro for your response. I have checked every where in the configuration of the phone and I can't see the message anywhere. Indeed what is more strange is that I have tested downloading a melody from a third party vendor (I think it was from movilisto) and the wappush gets delivered perfectly. Do you know if wp to Motorola has to be encoded in a different way from the ones to Nokia, Sony, etc ? Regards, Alberto On Sunday 27 August 2006 23:35, Linkas wrote: Also Sony Ericsson P800 don't notify, but saves the wappushes into the bookmarks! J Alejandro Guerrieri ha scritto: Are you sure that they are not being delivered unnoticed? Some Motorolas doesn't notify you when the wap-push arrives. I don't know why, but they seem to do just that. I'm not sure if it's a design feature, a bug or if you should set some flag on the wap-push pdu to make them behave the right way and notify you when a wap-push arrives. Try manually checking on the Service Inbox if the messages are not just lying there unnoticed, it happened to me before... Also check if your phone message memory's not full. Try deleting some messages from the inboxes. Hope it helps, Alejandro. On 8/26/06, Alberto Devesa [EMAIL PROTECTED] wrote: Hello, I have not any problem sending wap pushes to several models of Nokia and Sony phones but it seems that the Motorolas ignore the messages. I have tried with V3 and C385 models. Do this phones need something different to get the wp delivered ? I have tested it from Java code as well with the familiar test_ppg using the following pap and si files: ?xml version=1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP 1.0//EN http://www.wapforum.org/DTD/pap_1.0.dtd; pap push-message push-id= source-reference=EagleEye address address-value=WAPPUSH=+34x/TYPE=PLMN/ quality-of-service delivery-method=unconfirmed network=GSM bearer=SMS/ /push-message /pap ?xml version=1.0? !DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//EN http://www.wapforum.org/DTD/si.dtd; si indication href=http:/riga.com created=2004-12-04T10:29:40Z action=signal-highAlert/indication /si Regards, Alberto
Re: WAP Push to Motorola
Hi Alberto, I am using Motorola Phone. I have no problem in receiving WAP Push using test_ppg. Now Iam trying with Java codes and I do not know How to send it from Java. Can you please help me by posting your java codes. Thanks, Prasad On 8/26/06, Alberto Devesa [EMAIL PROTECTED] wrote: Hello,I have not any problem sending wap pushes to several models of Nokia and Sonyphones but it seems that the Motorolas ignore the messages. I have tried with V3 and C385 models. Do this phones need something different to get the wpdelivered ?I have tested it from Java code as well with the familiar test_ppg using thefollowing pap and si files:?xml version= 1.0?!DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP 1.0//ENhttp://www.wapforum.org/DTD/pap_1.0.dtdpappush-message push-id= source-reference=EagleEyeaddress address-value=WAPPUSH=+34x/TYPE=PLMN/quality-of-service delivery-method=unconfirmed network=GSM bearer=SMS/ /push-message/pap?xml version=1.0?!DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//ENhttp://www.wapforum.org/DTD/si.dtd siindication href="">created=2004-12-04T10:29:40Zaction="">/siRegards, Alberto-- Thanks,Prasad KavuriSoftware ConsultantMobile Lifestyle Sdn. Bhd.Unit F10 Block 3 (2320)Century Square63000 CyberjayaMalaysia. Tel: +60 3 8318 6691Fax:+60 3 8318 7760HP: +60 12 927 4711
Re: WAP Push to Motorola
Are you sure that they are not being delivered unnoticed? Some Motorolas doesn't notify you when the wap-push arrives. I don't know why, but they seem to do just that. I'm not sure if it's a design feature, a bug or if you should set some flag on the wap-push pdu to make them behave the right way and notify you when a wap-push arrives. Try manually checking on the Service Inbox if the messages are not just lying there unnoticed, it happened to me before... Also check if your phone message memory's not full. Try deleting some messages from the inboxes. Hope it helps, Alejandro. On 8/26/06, Alberto Devesa [EMAIL PROTECTED] wrote: Hello, I have not any problem sending wap pushes to several models of Nokia and Sony phones but it seems that the Motorolas ignore the messages. I have tried with V3 and C385 models. Do this phones need something different to get the wp delivered ? I have tested it from Java code as well with the familiar test_ppg using the following pap and si files: ?xml version=1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP 1.0//EN http://www.wapforum.org/DTD/pap_1.0.dtd; pap push-message push-id= source-reference=EagleEye address address-value=WAPPUSH=+34x/TYPE=PLMN/ quality-of-service delivery-method=unconfirmed network=GSM bearer=SMS/ /push-message /pap ?xml version=1.0? !DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//EN http://www.wapforum.org/DTD/si.dtd; si indication href=http:/riga.com created=2004-12-04T10:29:40Z action=signal-highAlert/indication /si Regards, Alberto -- Alejandro Guerrieri Magicom http://www.magicom-bcn.net/ LinkedIn: http://www.linkedin.com/in/aguerrieri
Re: Wap push sanity check
if you use PPG instead, it would do all this work for you
Aarno
On 24 Aug 2006, at 06:48, Mi Reflejo wrote:
I post wappushes constructing the pdu by hand too.
With some phones i has problems putting the http://;
Please try $submittedwappushurl = urlencode(www.google.com); //
without http://
PD: If it don't work. Take a look to this working pdu, may help you:
0B05040B8423F0 (udh)
0003 (wappush)
95 (serialID)
0101 ( one message of one )
DC0601AE02056A0045C60C03
7761702E676F6F676C652E636F6D (url)
00010344657363617267612079612022476F6F676C6522 (Message)
000101
Martin.
On 8/22/06, Alex Kinch [EMAIL PROTECTED] wrote:
Hi Aarno
Must admit I haven't tried it yet, I've just been using PHP to
construct and send a wap push via the normal sendsms http interface.
Also tried it via sqlbox and no luck.
Will have a go with PPG and let you know how it goes..
Alex
On 8/21/06, Aarno Syvänen [EMAIL PROTECTED] wrote:
Hello,
does PPG work ?
Aarno
On 18 Aug 2006, at 23:12, Alex Kinch wrote:
Hello,
Seem to be having some problems with WAP push. The code to
construct
the UDH and message is below. It used to work, but then somewhere
along the line it stopped.
Tried to both Nokia and SonyEricsson handsets, and both are
ignoring
the message.
If someone could take a look and make sure my construction
techniques
are right I would appreciate it.
Thanks,
Alex
$from = Sender;
$to = 44xxx;
function hex_encode( $text, $joiner='' ) {
for ($l=0; $lstrlen($text); $l++) {
$letter = substr($text, $l, 1);
$ret .= sprintf(%s%02X, $joiner, ord
($letter));
}
return $ret;
}
$submittedwappushurl = urlencode(http://www.google.com;);
$submittedwappushtext = test;
// override messagebody with wappush and set udh
$messageudh = %06%05%04%0B%84%23%F0;
$messagebody =
%1B%06%01%AE%02%05%6A%00%45%C6%0C%03.hex_encode
($submittedwappushurl,'%').%00%01%03.hex_encode
($submittedwappushtext,'%').%00%01%01;
Re: Wap push sanity check
Hi Aarno
Must admit I haven't tried it yet, I've just been using PHP to
construct and send a wap push via the normal sendsms http interface.
Also tried it via sqlbox and no luck.
Will have a go with PPG and let you know how it goes..
Alex
On 8/21/06, Aarno Syvänen [EMAIL PROTECTED] wrote:
Hello,
does PPG work ?
Aarno
On 18 Aug 2006, at 23:12, Alex Kinch wrote:
Hello,
Seem to be having some problems with WAP push. The code to construct
the UDH and message is below. It used to work, but then somewhere
along the line it stopped.
Tried to both Nokia and SonyEricsson handsets, and both are ignoring
the message.
If someone could take a look and make sure my construction techniques
are right I would appreciate it.
Thanks,
Alex
$from = Sender;
$to = 44xxx;
function hex_encode( $text, $joiner='' ) {
for ($l=0; $lstrlen($text); $l++) {
$letter = substr($text, $l, 1);
$ret .= sprintf(%s%02X, $joiner, ord($letter));
}
return $ret;
}
$submittedwappushurl = urlencode(http://www.google.com;);
$submittedwappushtext = test;
// override messagebody with wappush and set udh
$messageudh = %06%05%04%0B%84%23%F0;
$messagebody =
%1B%06%01%AE%02%05%6A%00%45%C6%0C%03.hex_encode
($submittedwappushurl,'%').%00%01%03.hex_encode
($submittedwappushtext,'%').%00%01%01;
Re: Wap push sanity check
Hello,
does PPG work ?
Aarno
On 18 Aug 2006, at 23:12, Alex Kinch wrote:
Hello,
Seem to be having some problems with WAP push. The code to construct
the UDH and message is below. It used to work, but then somewhere
along the line it stopped.
Tried to both Nokia and SonyEricsson handsets, and both are ignoring
the message.
If someone could take a look and make sure my construction techniques
are right I would appreciate it.
Thanks,
Alex
$from = Sender;
$to = 44xxx;
function hex_encode( $text, $joiner='' ) {
for ($l=0; $lstrlen($text); $l++) {
$letter = substr($text, $l, 1);
$ret .= sprintf(%s%02X, $joiner, ord($letter));
}
return $ret;
}
$submittedwappushurl = urlencode(http://www.google.com;);
$submittedwappushtext = test;
// override messagebody with wappush and set udh
$messageudh = %06%05%04%0B%84%23%F0;
$messagebody =
%1B%06%01%AE%02%05%6A%00%45%C6%0C%03.hex_encode
($submittedwappushurl,'%').%00%01%03.hex_encode
($submittedwappushtext,'%').%00%01%01;
Re: WAP push - please fill in the blank
Simon C. Wex ha scritto: I have an SMPP connection to an SMSC that I currently use for an application that acts as an SMS chat server. I'd like to add mobile content delivery (ringtones, wallpapers etc) to the application. As I understand it, the best way to do this is via WAP push. So, sending the WAP Push message shouldn't be too complicated, but this is where my expertise (and I use that term lightly) ends. I know I need to set up a WAP gateway (Kannel seems like the best choice) that will then proxy the request/response with my webserver. How do I get the wap server addressed? Is it simply over DNS? Do the carriers use the internet for communicating with WAP gateways? No this is not true. A wap gateway is not mandatory, and I think is really too much. You can also send a simple wap-push using a binary SMS as a Service Indication. In the wap-push message you will need to set the URL for the content. The URL can be a normal webserver with good wap headers. The wapbox could be useful if you don't know how to create a wap-push binary sms. If someone could explain this or point me to that document that I've been unable to find I would be eternally grateful. Cheers, Simon. Check for http://www.google.it/search?hl=itq=sms+%22service+indication%22+wap+pushbtnG=Cercameta= you will find some google links to read, this one can be a point to start: http://discussion.forum.nokia.com/forum/archive/index.php/t-7278.html J PS: I've not tested the binary in that link, it's just to let you understand what I mean.
RE: Wap push help
Hi Pieter, Kannel did not like your PAP file content. Try this: ?xml version=1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP//EN http://www.wapforum.org/DTD/pap_1.0.dtd pap push-message push-id=[EMAIL PROTECTED] address address-value=WAPPUSH=+27835018600/[EMAIL PROTECTED] / /push-message /pap Best regards, Rayson Lee InnoAge Hong Kong Limited From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pieter Martin Sent: Saturday, April 08, 2006 12:22 AM To: users@kannel.org Subject: Wap push help Hi I am trying to do a wap push using kannel using the test_ppg program. I am getting the following error PAP COMPILER: unknown element: I have attached the .conf file and the log files. I am calling the test program as follows ./test_ppg -q http://localhost:9090/cgi-bin/wap-push.cgi ./ppgPap.xml ./ppgSI.xml My pap file looks as follows ?xml version=1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP//EN http://www.wapforum.org/DTD/pap_1.0.dtd pap push-message push-id=[EMAIL PROTECTED] deliver-before-timestamp=2006-09-28T06:45:00Z deliver-after-timestamp=20061-02-28T06:45:00Z progress-notes-requested=false address address-value=WAPPUSH=+27835018600/[EMAIL PROTECTED]/ /push-message /pap My SI file follows ?xml version=1.0? !DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//EN http://www.wapforum.org/DTD/si.dtd si indication href="" href="/exchweb/bin/redir.asp?URL="" target="_blank">http://www.google.com si-id=[EMAIL PROTECTED] action=""> created=1999-06-25T15:23:15Z si-expires=2006-06-30T00:00:00Z Want to test a fetch? /indication /si Any help will be appreciated. Thanks Pieter
RE: Wap push help
Hi Having wappush dlr problems now. The wap push works fine. I am using openwave's api. I canretrieve the dlr for a normal sms but not for a wap push. I am running all three servers and my ppg group has a "ppg-smsbox-id = dlrbox" and the smsbox group has a "smsbox-id = dlrbox" Is anything else needed? Attached is my config file. Thanks Pieter From: Rayson Lee [mailto:[EMAIL PROTECTED]Sent: Wed 4/19/2006 1:02 PMTo: Pieter Martin; users@kannel.orgSubject: RE: Wap push help Hi Pieter, Kannel did not like your PAP file content. Try this: ?xml version="1.0"? !DOCTYPE pap PUBLIC "-//WAPFORUM//DTD PAP//EN" "http://www.wapforum.org/DTD/pap_1.0.dtd" pap push-message push-id="[EMAIL PROTECTED]" address address-value="WAPPUSH=+27835018600/[EMAIL PROTECTED]" / /push-message /pap Best regards, Rayson Lee InnoAge Hong Kong Limited From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pieter MartinSent: Saturday, April 08, 2006 12:22 AMTo: users@kannel.orgSubject: Wap push help Hi I am trying to do a wap push using kannel using the test_ppg program. I am getting the following error "PAP COMPILER: unknown element:" I have attached the .conf file and the log files. I am calling the test program as follows ./test_ppg -q http://localhost:9090/cgi-bin/wap-push.cgi ./ppgPap.xml ./ppgSI.xml My pap file looks as follows ?xml version="1.0"?!DOCTYPE pap PUBLIC "-//WAPFORUM//DTD PAP//EN" "http://www.wapforum.org/DTD/pap_1.0.dtd"pap push-message push-id="[EMAIL PROTECTED]" deliver-before-timestamp="2006-09-28T06:45:00Z" deliver-after-timestamp="20061-02-28T06:45:00Z" progress-notes-requested="false" address address-value="WAPPUSH=+27835018600/[EMAIL PROTECTED]"/ /push-message/pap My SI file follows ?xml version="1.0"?!DOCTYPE si PUBLIC "-//WAPFORUM//DTD SI 1.0//EN" "http://www.wapforum.org/DTD/si.dtd"si indication href=""/exchweb/bin/redir.asp?URL="" target=_blank>http://www.google.com" si-id="[EMAIL PROTECTED]" action="" created="1999-06-25T15:23:15Z" si-expires="2006-06-30T00:00:00Z" Want to test a fetch? /indication/si Any help will be appreciated. Thanks Pieter wapPushTest2.conf Description: wapPushTest2.conf
RE: WAP Push query
Dear Dipan, Your appreciation should go to the list, they are the people you should thank. Best regards, Rayson Lee InnoAge Hong Kong Limited From: Dipan [mailto:[EMAIL PROTECTED] Sent: Saturday, April 01, 2006 1:57 PM To: Rayson Lee Subject: RE: WAP Push query Hi rayson, It finally worked. We learned that if there is even a single byte error in cotent framing, the receving phone will not respond at all as if it never recevied anything. So we couldn't trace back the error at all. The string you sent worked, which made this discovery happen. Thanks a lot. I extremely appriciate the peoplewho has put in efforts to make Kannel wap gateway Dipan. -Original Message- From: Rayson Lee [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 29, 2006 11:21 AM To: 'Dipan'; users@kannel.org Subject: RE: WAP Push query Dear Dipan, Please refer to Willys more detail PHP sample on how to generate the text stream. However if you want to push a variety of contents, I think you better use the http post interface as detailed in the user guide. Best regards, Rayson Lee InnoAge Hong Kong Limited From: Dipan [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 29, 2006 1:33 PM To: Rayson Lee Subject: RE: WAP Push query Thanks for your quick reply. I will be able to check tomm. only so will let you know if there are any problems. I think we have done WAP PUSH - Allow all in the phone. So we thought that would be okay. I am not sure any other thing that needs to be set. Will try to find out and use it. By the way, what is this new stream that you generated ? How did you generated this ? Can you tell us simpler way to generate requried SI, SL or WML into such binary URLs ? The content could by by and large hardcoded. Thanks. Dipan. -Original Message- From: Rayson Lee [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 29, 2006 12:38 AM To: 'Dipan' Subject: RE: WAP Push query Dear Dipan, First of all, please make sure you have enabled WAP Push inbox in your handsets. In your sendsms link try to set text=%1B%06%01%AE%02%05%6A%00%45%C6%0C%03wap.nokia.de%00%01%03Download%00%01%01 and see if that works. Good Luck. Rayson Lee InnoAge Hong Kong Limited From: Dipan [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 28, 2006 10:34 PM To: [EMAIL PROTECTED] Subject: WAP Push query I am using Kannal and trying to send WAP push to some mobile phone. I have been able to successfully send SMSs using Kannel's bearrer box so far. The config is attached here. I am setting up WAP box and using test_ppg (the one supplied by kannel's default destribution). Using this when i try to send out a WAP push to a NON-wap capable phone it receives an SMS indicating that message cannot be displayed here. However, when the WAP push is done to a WAP,WML capable phone which is either the Sony Erricsion K700i as well as Nokia 6630, neither of the phones receives anything. Alternatively, we got SMS box running (which can successfully send SMS) with UDH (http://localhost:13013/cgi-bin/sendsms?username=kannelpassword=rL4y to=9820756920udh=%06%05%04%0B%84%23%F0 text=%07%06%17%B0%96%6C%6F%63%61%6C%68%6F%73%74%3A%39%30%38%30%00 %AF%80%8D%95%B4%02%06%6A%00%85%09%03wap.nokia.de%00%01) to the same numbers the behaviors is same. The bearer is un-confirmed SMS. The message length typically is not exceeding 140 char. The bearer box shows one SMS is being sent and the GSM phone (used as a message) and the SMS sending charge is also deducted from the credit. Please help me. This is a bit urgent. Thanks a lot. Dipan. group = core admin-port = 13000 smsbox-port = 13001 wapbox-port = 13002 admin-password = bar # status-password = foo #admin-deny-ip = #admin-allow-ip = wdp-interface-name = * log-file = /tmp/bearerbox.log log-level = 0 box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 unified-prefix = +358,00358,0;+,00,+91 #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 # WAPBOX SETUP, for pushing and for pulling (fetching) the wap data group = wapbox bearerbox-host = localhost log-file = /tmp/wapbox.log log-level = 0 syslog-level = none # PPG CORE SETUP, for defining the push request interface group = ppg ppg-url = ""> ppg-port = 15000 #ppg-ssl-port = 8081 concurrent-pushes = 100 trusted-pi = true users = 1024 # global-sender = +919820205446 global-sender = +919820756920 #ppg-deny-ip = *.*.*.* ppg-allow-ip = *.*.*.* #ssl-server-cert-file = cert.pem #ssl-server-key-file = key.pem # PPG USER SETUP, for authorizing a specific push user group = wap-push-user wap-push-user = foo ppg-username = foo ppg-password = bar country-prefix = +358,+91 #allowed-pref
RE: WAP Push
Same question? From: Nirav doshi [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 28, 2006 10:15 PM To: [EMAIL PROTECTED]; users@kannel.org Subject: WAP Push H, My problem is Whenever i m sending the WAP Push to a phone which does not have WAP facility in it, the phone receives an error Content cant be displayed i feel thats OK but when i send to a WAP-enabled phone i m not getting the message but the money is deducted and the bearerbox shows that it had sent the message. I have tried many things but nothing works right at this moment. The configuration file and related content documents are as follows: group = core admin-port = 13000 smsbox-port = 13001 wapbox-port = 13002 admin-password = bar # status-password = foo #admin-deny-ip = #admin-allow-ip = wdp-interface-name = * log-file = /tmp/bearerbox.log log-level = 0 box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 unified-prefix = +358,00358,0;+,00,+91 #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 # WAPBOX SETUP, for pushing and for pulling (fetching) the wap data group = wapbox bearerbox-host = localhost log-file = /tmp/wapbox.log log-level = 0 syslog-level = none # PPG CORE SETUP, for defining the push request interface group = ppg ppg-url = ""> ppg-port = 15000 #ppg-ssl-port = 8081 concurrent-pushes = 100 trusted-pi = true users = 1024 # global-sender = +919820205446 global-sender = +919820756920 #ppg-deny-ip = *.*.*.* ppg-allow-ip = *.*.*.* #ssl-server-cert-file = cert.pem #ssl-server-key-file = key.pem # PPG USER SETUP, for authorizing a specific push user group = wap-push-user wap-push-user = foo ppg-username = foo ppg-password = bar country-prefix = +358,+91 #allowed-prefix = 40;60;70 #denied-prefix = 50 #white-list = http://localhost:8082/whitelist #black-list = http://localhost:8082/blacklist #deny-ip = *.*.*.* allow-ip = 127.0.0.1 # SMSC CONNECTIONS, for pushing SI, SL, MMS notifications or whatever over SMS # group = smsc # smsc = fake # smsc-id = FAKE # port = 1 # connect-allow-ip = 127.0.0.1 # SMSBOX SETUP (a kludge!) 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 # TEST PAP PROTOCOL group = test-ppg retries = 2 pi-ssl = yes #ssl-client-certkey-file = /etc/kannel/certkey.pem ssl-client-certkey-file = /home/sachin/nirav/gatway-1.4.0/gw/cert.pem # CONFIGURATION GROUP group = configuration push-url = ""> #pap-file = /etc/kannel/ipnoqos.txt pap-file = /home/sachin/nirav/gateway-1.4.0/test/iptestppg.xml #content-file = /etc/kannel/si.txt content-file = /home/sachin/nirav/gateway-1.4.0/test/si.xml username = foo password = bar # MODEM GROUP group = modems id = my-id name = my-name detect-string = MODEM group = modems id = my-id name = my-name detect-string = MODEM detect-string2 = init-string = AT init-string = ATFcr init-string = AT V1E0S0=0D2C1cr init-string = AT +CMEE=1cr speed = 9600 enable-hwhs = +IFC=2,2 need-sleep = false no-pin = false no-smsc = false sendline-sleep = 100 keepalive-cmd = AT broken = false message-storage = SM enable-mms = false #group = modems id = ericsson_t68 name = Ericsson T68 detect-string = Ericsson detect-string2 = T68 init-string = AT +CMEE=1 keepalive-cmd = AT+CBC;+CSQ #AT group = smsc smsc = at modemtype = ericsson_t68 device = /dev/ttyS0 speed = 9600 pin = 2345 validityperiod = 167 # SEND-SMS USERS group = sendsms-user username = tester password = foobar user-deny-ip = user-allow-ip = 10.125.17.141 group = sendsms-user username = kannel password = rL4y user-deny-ip = *.*.*.* user-allow-ip = 127.0.0.1 I m using the url to send message: http://localhost:13013/cgi-bin/sendsms?username=kannelpassword=rL4y to=9820756920udh=%06%05%04%0B%84%23%F0 text=%07%06%17%B0%96%6C%6F%63%61%6C%68%6F%73%74%3A%39%30%38%30%00 %AF%80%8D%95%B4%02%06%6A%00%85%09%03wap.nokia.de%00%01 I got this url from the net. I have also tried using WAP box. Now i have tried using it smsbox to push the message but samething occurs in both the situation. Please suggest a way out or instruct me how to go further. Thanks in advance. ---BeginMessage--- Dear Dipan, First of all, please make sure you have enabled WAP Push inbox in your handsets. In your sendsms link try to set text=%1B%06%01%AE%02%05%6A%00%45%C6%0C%03wap.nokia.de%00%01%03Download%00%01%01 and see if that works. Good Luck. Rayson Lee InnoAge Hong Kong Limited From: Dipan [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 28, 2006 10:34 PM To: [EMAIL PROTECTED] Subject: WAP Push query I am using Kannal and trying to send WAP push to some mobile phone. I have been able to successfully send SMSs using Kannel's bearrer box so far. The config is attached here. I am setting up WAP box and using test_ppg
Re: WAP Push
Hi,
It is better to send the WAP PUSH over SMS with UDH
(%06%05%04%0B%84%23%F0), below is a simple and tested PHP function of the WAP
PUSH construction:
function WAPpsh($URL,
$vendor){$text = "%01"; // transid$text .= "%06";
// PDU Type (push)$text .= "%04%03"; // length of
content-type$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="">$text .= "%01"; // end indication$text .=
"%03".rawurlencode(trim($vendor))."%00";$text .= "%01"; //
/indication$text .= "%01"; //
/sireturn $text;}
$text =
WAPpsh("MTRAX","1.2.3.4/path/to/script.php");
Please modify and fit your need. And send it with
no URLENCODE with kannel's sendsms script.
Regards
Willy
- Original Message -
From:
Nirav doshi
To: [EMAIL PROTECTED] ; users@kannel.org
Sent: Tuesday, March 28, 2006 9:15
PM
Subject: WAP Push
H,My problem isWhenever i m sending the
WAP Push to a phone which does not have WAP facility in it, the phone receives
an error Content cant be displayed i feel thats OK but when i send to a
WAP-enabled phone i m not getting the message but the money is deducted and
the bearerbox shows that it had sent the message. I have tried many things but
nothing works right at this moment. The configuration file and related content
documents are as follows:group = coreadmin-port =
13000smsbox-port = 13001wapbox-port = 13002admin-password =
bar# status-password = foo#admin-deny-ip = ""#admin-allow-ip =
""wdp-interface-name = "*"log-file = "/tmp/bearerbox.log"log-level
= 0box-deny-ip = "*.*.*.*"box-allow-ip = "127.0.0.1"unified-prefix
= "+358,00358,0;+,00,+91"#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"# WAPBOX SETUP, for pushing and for pulling
(fetching) the wap datagroup = wapboxbearerbox-host =
localhostlog-file = "/tmp/wapbox.log"log-level = 0syslog-level =
none# PPG CORE SETUP, for defining the push request
interfacegroup = ppgppg-url = "">ppg-port =
15000#ppg-ssl-port = 8081concurrent-pushes = 100trusted-pi =
trueusers = 1024# global-sender = "+919820205446"global-sender =
"+919820756920"#ppg-deny-ip = "*.*.*.*"ppg-allow-ip =
"*.*.*.*"#ssl-server-cert-file = "cert.pem"#ssl-server-key-file =
"key.pem"# PPG USER SETUP, for authorizing a specific push
usergroup = wap-push-userwap-push-user = fooppg-username =
fooppg-password = barcountry-prefix = +358,+91#allowed-prefix =
"40;60;70"#denied-prefix = 50#white-list =
http://localhost:8082/whitelist#black-list =
http://localhost:8082/blacklist#deny-ip = "*.*.*.*"allow-ip =
"127.0.0.1"# SMSC CONNECTIONS, for pushing SI, SL, MMS notifications
or whatever over SMS# group = smsc# smsc = fake# smsc-id =
FAKE# port = 1# connect-allow-ip = 127.0.0.1# SMSBOX SETUP
(a kludge!)group = smsboxbearerbox-host =
localhostsendsms-port = 13013global-sender = 13013sendsms-chars =
"0123456789 +-"log-file = "/tmp/smsbox.log"log-level = 0access-log
= "/tmp/access.log"# TEST PAP PROTOCOLgroup =
test-ppgretries = 2pi-ssl = yes#ssl-client-certkey-file =
/etc/kannel/certkey.pemssl-client-certkey-file =
/home/sachin/nirav/gatway-1.4.0/gw/cert.pem# CONFIGURATION
GROUPgroup = configurationpush-url =
"">#pap-file =
/etc/kannel/ipnoqos.txtpap-file =
/home/sachin/nirav/gateway-1.4.0/test/iptestppg.xml#content-file =
/etc/kannel/si.txtcontent-file =
/home/sachin/nirav/gateway-1.4.0/test/si.xmlusername = foopassword =
bar# MODEM GROUPgroup = modemsid = "my-id"name =
"my-name"detect-string = "MODEM"group = modemsid = "my-id"name
= "my-name"detect-string = "MODEM"detect-string2 = ""init-string =
"AT"init-string = "ATFcr"init-string = "AT
V1E0S0=0D2C1cr"init-string = "AT
+CMEE=1cr"speed = 9600enable-hwhs = "+IFC=2,2"need-sleep =
falseno-pin = falseno-smsc = falsesendline-sleep =
100keepalive-cmd = "AT"broken = falsemessage-storage =
"SM"enable-mms = false#group = modemsid = ericsson_t68name =
"Ericsson T68"detect-string = "Ericsson"detect-string2 =
"T68"init-string = "AT +CMEE=1"keepalive-cmd =
"AT+CBC;+CSQ"#ATgroup = smscsmsc = atmodemtype =
ericsson_t68device = /dev/ttyS0speed = 9600pin =
2345validityperiod = 167# SEND-SMS USERSgroup =
sendsms-userusername = testerpassword = foobaruser-deny-ip =
""user-allow-ip = "10.125.17.141"group = sendsms-userusername
= kannelpassword = rL4yuser-deny-ip = "*.*.*.*"user-allow-ip =
"127.0.0.1"I m using the url to send
