WAP PUSH Via Wapbox using PHP
I have tried most of the php script in the mailing list and they don't work as always get this curl reply: badrequest and in my Wapbox.log file: WARNING: erroroneous control entity WARNING: PPG: unable to parse mime content, the request unacceptable . Can someone share a working php script for wap push? Regards, TOSIN AMUDA Telecoms Integration Lead L5lab | Betazoo
WAP PUSH
Hi, I want to send a WAP Push through Kannel. I am using URL : http:// [Kannel-IP]:13131/cgi-bin/sendsms?username=[password]password=[password]to=[mobile-no]coding=1from=[from]udh=%06%05%04%F1%C0%33%4Btext=[Hexadecimal-encoded-text] but its delivering only simple text or it sometimes says that the format is not supported. Plz help me. *Thanks Regards,* *SAURABH JAIN* Skype IM sorabh2008 Hangout IM sorabh2008
Wap-Push URL
Hi guys, I am trying to send a wap push through URL of Kannel, but what i receive on my phone is either a NULL or simple text or it just says that 'format is not supported' Pls suggest some solution on urgent bases. URL :: http://10.11.233.21:13131/cgi-bin/sendsms?username=[user-name]password=[password]to=[number]coding=1from=[number]UDH=0605040B8423F0text=www.google.com *Thanks Regards,* *SAURABH JAIN* Contact(+91) 783 - 707 - 1512 Follow meBlog http://blog.splayit.in/ facebookhttp://www.facebook.com/sorabh2008 Skype IM sorabh2008 Hangout IM sorabh2008
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
wap push sms mask
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: Kannel WAP Push in production
So in wap 1.0 I can't change the mask? On Wed, Sep 12, 2012 at 2:05 AM, Alvaro Cornejo cornejo.alv...@gmail.comwrote: Hi I think kannel supports only wap 1.0 For wap 2.0, mms others you might want to try mbuni... Regards Alvaro On 9/11/12, [Digital^Dude] ® millennium@gmail.com wrote: Hello, Having tested wap pushes as explained in: http://kannel.org/download/kannel-userguide-snapshot/userguide.html#PPG 1. Is there any way wap pushes can be used via API? Just like smses are sent via kannel? I am using SMPP for sms. 2. How do I change the mask of wap push messages? -- Thanks -- |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.NET www.smsglobal.com.mx y www.pravcom.com
Re: Kannel WAP Push in production
FeaturesWAP - Fully compliant with WAP 1.1 specification - Already implements some WAP 1.2 and even WAP 2.0 features. Source: http://kannel.org/download/kannel-userguide-snapshot/userguide.html On Wed, Sep 12, 2012 at 2:06 PM, [Digital^Dude] ® millennium@gmail.comwrote: So in wap 1.0 I can't change the mask? On Wed, Sep 12, 2012 at 2:05 AM, Alvaro Cornejo cornejo.alv...@gmail.comwrote: Hi I think kannel supports only wap 1.0 For wap 2.0, mms others you might want to try mbuni... Regards Alvaro On 9/11/12, [Digital^Dude] ® millennium@gmail.com wrote: Hello, Having tested wap pushes as explained in: http://kannel.org/download/kannel-userguide-snapshot/userguide.html#PPG 1. Is there any way wap pushes can be used via API? Just like smses are sent via kannel? I am using SMPP for sms. 2. How do I change the mask of wap push messages? -- Thanks -- |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.NET www.smsglobal.com.mx y www.pravcom.com
Kannel WAP Push in production
Hello, Having tested wap pushes as explained in: http://kannel.org/download/kannel-userguide-snapshot/userguide.html#PPG 1. Is there any way wap pushes can be used via API? Just like smses are sent via kannel? I am using SMPP for sms. 2. How do I change the mask of wap push messages? -- Thanks
Re: Kannel WAP Push in production
Hi I think kannel supports only wap 1.0 For wap 2.0, mms others you might want to try mbuni... Regards Alvaro On 9/11/12, [Digital^Dude] ® millennium@gmail.com wrote: Hello, Having tested wap pushes as explained in: http://kannel.org/download/kannel-userguide-snapshot/userguide.html#PPG 1. Is there any way wap pushes can be used via API? Just like smses are sent via kannel? I am using SMPP for sms. 2. How do I change the mask of wap push messages? -- Thanks -- |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.NET www.smsglobal.com.mx y www.pravcom.com
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)
WAP push message over USSD
Hi, Please provide some idea how to send WAP push message over USSD. Thanks in advance.. Regards Rk
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)
php Wap push help (Solved)
I have solved the problem below by following instructions given in the PPG mini howto http://article.gmane.org/gmane.comp.mobile.kannel.user/11009 and used http://localhost/wappush.php instead of http://localhost:8080/wappush.php. Thanks a lot! On Fri, Sep 23, 2011 at 5:27 PM, christopher serumola serumo...@gmail.comwrote: Please help as per below; -- Forwarded message -- From: christopher serumola serumo...@gmail.com Date: Thu, Sep 22, 2011 at 11:37 PM Subject: Re: php Wap push help To: Juan Nin jua...@gmail.com Thanks Juan. I did replace the portion you referred to below with the code you provided below but i am still getting the same result. Maybe there is something else beyond this. I pass the following url to the firefox browser to execute the wappush script, http://localhost:8080/wappush.php. Port 8080 is the ppg-port. Strangely,immediately after getting the error message, when i change the php script name to any other name e.g to wap.php i still get the same error from the browser even though wap.php script does not exist in my webserver. In this case i expect it to return a Page not found error. I have also used the non-ppg script you suggested below but it returns a blank page and the message is not delivered to the mobile phone. Even when i view its page source it is blank. This one i ran it directly on port 80(default) i.e http://localhost/testwap.php. Any ideas? On Thu, Sep 22, 2011 at 3:12 AM, Juan Nin jua...@gmail.com wrote: The only differences I see are on this part, this is your code: 'push-message push-id='.$wap_push_id.''.\r\n\t. 'address address-value= WAPPUSH=+'.$country_code.$phone.'/TYPE=p...@ppg.nokia.comWAPPUSH=+%27.$country_code.$phone.%27/TYPE=p...@ppg.nokia.com /'.\r\n\t. 'quality-of-service delivery-method=unconfirmed network-required=true network=GSM bearer-required=true bearer=SMS/'. \r\n/push-message\r\n. /pap\r\n\r\n. This is my original code: 'push-message push-id='.$wap_push_id.''.\r\n. 'address address-value=WAPPUSH=+'.$country_code.$phone.'/TYPE=PLMN@x/'.\r\n. 'quality-of-service delivery-method=unconfirmed network=GSM bearer=SMS/'. /push-message\r\n. /pap\r\n\r\n. On the first 2 lines you added a \t, not sure if that would affect, don't think so, but I had a hard time getting my original code to work, since PPG was very picky about the line breaks and line feeds On the third line you added network-required=true and bearer-required=true, I guess you checked those are valid options On the 4th line you added a \r\n at the beginning, although it would make sense for that one to go, it may be the one breaking the thing. As I mentioned, I spent lots of time tweaking line breaks and line feeds, cause a missing one or an extra one would break it. So, I would start by taking out that extra \r\n from the 4th line. If that doesn't make it, I would take out the \t's And if that doesn't make it, take out the attributes you added. Another approach is to send wap push without PPG, via sendsms cgi, which is much easier and you avoid running an extra service. See here: http://www.blogalex.com/archives/12 On this article you can find what each hexadecimal value on the resultant message means, and you can even do a more complete version: http://mobiforge.com/developing/story/binary-sms-sending-rich-content-devices-using-sms I'm currently using Alex's approach with something similar to this (simplified code below): $udh = '%06%05%04%0B%84%23%F0'; $text = '%1B%06%01%AE%02%05%6A%00%45%C6%0C%03'.hexEncode($url, '%'). '%00%11%03'.hexEncode($si_id, '%').'%00%07%01%03'.hexEncode($subject, '%').'%00%01%01'; Hope this helps. On 9/21/11 3:02 AM, christopher serumola wrote: Yes, these are single lines on the php script. Its only that i use a dell mini netbook with a small screen size which tends to wrap the text to the next line when it is long. could that be the cause of the problem? On Tue, Sep 20, 2011 at 11:16 PM, Juan Nin jua...@gmail.com wrote: Do you have these lines that on your email look like more than 1 line each as 1 line or more than 1 line? (should be 1) '!DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP 1.0//EN'.\r\n. 'address address-value=WAPPUSH= +'.$country_code.$phone.'/TYPE=p...@ppg.nokia.com/'.\r\n\t. 'quality-of-service delivery-method=unconfirmed network-required=true network=GSM bearer-required=true bearer=SMS/'. '?xml version=1.0?'.\r\n. '!DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//EN'.\r \n. 'indication action=signal-high si-id='.$wap_push_id.' href='. $push_url .''.$text.'/indication'.\r\n. X-Kannel-SMSC: $smsc_id\r\n.'Content-Type: multipart/related; boundary=multipart-boundary; type=application/xml'.\r\n. On 9/20/11 4:38 PM, chris wrote: I have installed kannel 1.5.0 on ubuntu 10.0.4 and configured bearerbox,smsbox and wapbox. All are working well except that i can't send wap
Fwd: php Wap push help
Please help as per below; -- Forwarded message -- From: christopher serumola serumo...@gmail.com Date: Thu, Sep 22, 2011 at 11:37 PM Subject: Re: php Wap push help To: Juan Nin jua...@gmail.com Thanks Juan. I did replace the portion you referred to below with the code you provided below but i am still getting the same result. Maybe there is something else beyond this. I pass the following url to the firefox browser to execute the wappush script, http://localhost:8080/wappush.php. Port 8080 is the ppg-port. Strangely,immediately after getting the error message, when i change the php script name to any other name e.g to wap.php i still get the same error from the browser even though wap.php script does not exist in my webserver. In this case i expect it to return a Page not found error. I have also used the non-ppg script you suggested below but it returns a blank page and the message is not delivered to the mobile phone. Even when i view its page source it is blank. This one i ran it directly on port 80(default) i.e http://localhost/testwap.php. Any ideas? On Thu, Sep 22, 2011 at 3:12 AM, Juan Nin jua...@gmail.com wrote: The only differences I see are on this part, this is your code: 'push-message push-id='.$wap_push_id.''.\r\n\t. 'address address-value= WAPPUSH=+'.$country_code.$phone.'/TYPE=p...@ppg.nokia.comWAPPUSH=+%27.$country_code.$phone.%27/TYPE=p...@ppg.nokia.com /'.\r\n\t. 'quality-of-service delivery-method=unconfirmed network-required=true network=GSM bearer-required=true bearer=SMS/'. \r\n/push-message\r\n. /pap\r\n\r\n. This is my original code: 'push-message push-id='.$wap_push_id.''.\r\n. 'address address-value=WAPPUSH=+'.$country_code.$phone.'/TYPE=PLMN@x/'.\r\n. 'quality-of-service delivery-method=unconfirmed network=GSM bearer=SMS/'. /push-message\r\n. /pap\r\n\r\n. On the first 2 lines you added a \t, not sure if that would affect, don't think so, but I had a hard time getting my original code to work, since PPG was very picky about the line breaks and line feeds On the third line you added network-required=true and bearer-required=true, I guess you checked those are valid options On the 4th line you added a \r\n at the beginning, although it would make sense for that one to go, it may be the one breaking the thing. As I mentioned, I spent lots of time tweaking line breaks and line feeds, cause a missing one or an extra one would break it. So, I would start by taking out that extra \r\n from the 4th line. If that doesn't make it, I would take out the \t's And if that doesn't make it, take out the attributes you added. Another approach is to send wap push without PPG, via sendsms cgi, which is much easier and you avoid running an extra service. See here: http://www.blogalex.com/archives/12 On this article you can find what each hexadecimal value on the resultant message means, and you can even do a more complete version: http://mobiforge.com/developing/story/binary-sms-sending-rich-content-devices-using-sms I'm currently using Alex's approach with something similar to this (simplified code below): $udh = '%06%05%04%0B%84%23%F0'; $text = '%1B%06%01%AE%02%05%6A%00%45%C6%0C%03'.hexEncode($url, '%'). '%00%11%03'.hexEncode($si_id, '%').'%00%07%01%03'.hexEncode($subject, '%').'%00%01%01'; Hope this helps. On 9/21/11 3:02 AM, christopher serumola wrote: Yes, these are single lines on the php script. Its only that i use a dell mini netbook with a small screen size which tends to wrap the text to the next line when it is long. could that be the cause of the problem? On Tue, Sep 20, 2011 at 11:16 PM, Juan Nin jua...@gmail.com wrote: Do you have these lines that on your email look like more than 1 line each as 1 line or more than 1 line? (should be 1) '!DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP 1.0//EN'.\r\n. 'address address-value=WAPPUSH= +'.$country_code.$phone.'/TYPE=p...@ppg.nokia.com/'.\r\n\t. 'quality-of-service delivery-method=unconfirmed network-required=true network=GSM bearer-required=true bearer=SMS/'. '?xml version=1.0?'.\r\n. '!DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//EN'.\r \n. 'indication action=signal-high si-id='.$wap_push_id.' href='. $push_url .''.$text.'/indication'.\r\n. X-Kannel-SMSC: $smsc_id\r\n.'Content-Type: multipart/related; boundary=multipart-boundary; type=application/xml'.\r\n. On 9/20/11 4:38 PM, chris wrote: I have installed kannel 1.5.0 on ubuntu 10.0.4 and configured bearerbox,smsbox and wapbox. All are working well except that i can't send wap pushes through ppg from the php sample script posted in the mailing lists named wappush.conf. i have checked all the related postings on the matter and implemented the suggestions without success.So i need help. The error message i get from the browser is; This XML file does not appear to have any style information associated
Re: php Wap push help
14:
$rand_value = n;
break;
case 15:
$rand_value = o;
break;
case 16:
$rand_value = p;
break;
case 17:
$rand_value = q;
break;
case 18:
$rand_value = r;
break;
case 19:
$rand_value = s;
break;
case 20:
$rand_value = t;
break;
case 21:
$rand_value = u;
break;
case 22:
$rand_value = v;
break;
case 23:
$rand_value = w;
break;
case 24:
$rand_value = x;
break;
case 25:
$rand_value = y;
break;
case 26:
$rand_value = z;
break;
case 27:
$rand_value = 0;
break;
case 28:
$rand_value = 1;
break;
case 29:
$rand_value = 2;
break;
case 30:
$rand_value = 3;
break;
case 31:
$rand_value = 4;
break;
case 32:
$rand_value = 5;
break;
case 33:
$rand_value = 6;
break;
case 34:
$rand_value = 7;
break;
case 35:
$rand_value = 8;
break;
case 36:
$rand_value = 9;
break;
}
return $rand_value;
}
function get_rand_numbers($length)
{
if($length0)
{
$rand_id=;
for($i=1; $i=$length; $i++)
{
mt_srand((double)microtime() * 100);
$num = mt_rand(27,36);
$rand_id .= assign_rand_value($num);
}
}
return $rand_id;
}
?
and from the wap log file;
2011-09-20 21:02:23 [1833] [14] INFO: PPG: Accept request/wappush.php
from127.0.0.1
2011-09-20 21:02:23 [1833] [14] WARNING: PPG: No MIME content received,
the request unacceptable
2011-09-20 21:02:23 [1833] [14] DEBUG: PPG: send_bad_message_response:
telling pi
2011-09-20 21:02:23 [1833] [14] DEBUG: HTTP: Resetting HTTPClient for
`127.0.0.1'.
2011-09-20 21:02:23 [1833] [11] DEBUG: HTTP: Creating HTTPClient for
`127.0.0.1'.
2011-09-20 21:02:23 [1833] [11] DEBUG: HTTP: Created HTTPClient area
0x99ec880.
2011-09-20 21:02:24 [1833] [14] ERROR: Request/favicon.ico from
127.0.0.1: service not found
2011-09-20 21:02:24 [1833] [14] DEBUG: your configuration
uses /wappush.php
2011-09-20 21:02:24 [1833] [14] DEBUG: HTTP: Resetting HTTPClient for
`127.0.0.1'.
2011-09-20 21:03:23 [1833] [10] DEBUG: HTTP: Destroying HTTPClient area
0x99ec880.
2011-09-20 21:03:23 [1833] [10] DEBUG: HTTP: Destroying HTTPClient for
`127.0.0.1'.
and my kannel configuration file;
group = core
admin-port = 13050
smsbox-port = 13051
wapbox-port= 13052
admin-password= chris
dlr-storage = mysql
wdp-interface-name=*
log-file = /var/log/kannel/bearerbox.**log
log-level=0
box-deny-ip = *.*.*.*
box-allow-ip = 127.0.0.1
group=smsc
smsc-id=mysmsc-id
port=13053
smsc=at
modemtype=huawei
device=/dev/ttyUSB0
#speed=115200
my-number=xx
validityperiod=167
pin=7172
sim-buffering=true
#keepalive=5
sms-center=+xx
group=modems
id=huawei
name=huawei E230
detect-string=huawei
init-string=ATZ
init-string=AT+CNMI=2,1,2,2,**0
enable-hwhs=false
message-storage=SM
message-start=0
#speed=115200
group=smsbox
#smsbox-id=smsbox1
bearerbox-host=127.0.0.1
sendsms-port=13054
global-sender=xxx
sendsms-chars=0123456789+-
log-file = /var/log/kannel/smsbox.log
log-level=0
group=sendsms-user
username=kannel
password=kannel
concatenation=true
max-messages=10
#Receive MO sms and direct to specified url
group=sms-service
keyword=default
get-url=http://localhost/**receivesms.php?sender=%ptext=**%b;
#accept-x-kannel-headers=true
#accepted-smsc=smsbox1
max-messages=1
catch-all=true
#Set up wap pushes
group=wapbox
bearerbox-host=127.0.0.1
log-file = /var/log/kannel/wapbox.log
access-log=/var/log/kannel/**wapacess.log
log-level=0
syslog-level=none
group=ppg
ppg-url=/wappush.php
ppg-port=8080
concurrent-pushes=100
global-sender=xxx
users=1024
ppg-allow-ip=127.0.0.1
trusted-pi=true
group=wap-push-user
wap-push-user=wappusher
ppg-username=push
ppg-password=push
allow-ip=*.*.*.*
#Use mysql database for storing delivery reports for MT sms
group=mysql-connection
id=mydlr
host=localhost
username=root
password=
database=dlr
max-connections=1
group=dlr-db
id=mydlr
table=dlr
field-smsc=smsc
field-timestamp=ts
field-destination=destination
field-source=source
field-service=service
field-url=url
field-mask=mask
field-status=status
field-boxc-id=boxc
#group = sqlbox
#id = sqlbox-db
#smsbox-id = smsbox
#bearerbox-host = 127.0.0.1
#bearerbox-port = 13003
#smsbox-port = 13005
#log-file = /var/log/kannel/sqlbox.log
#log-level = 0
# Example MYSQL Connection
#group = mysql-connection
#id = sqlbox-db
#host = localhost
#username = root
#password =
#database = dlr
i would really appreciate as comprehensive help as possible.
Re: php Wap push help
pin=7172 sim-buffering=true #keepalive=5 sms-center=+xx group=modems id=huawei name=huawei E230 detect-string=huawei init-string=ATZ init-string=AT+CNMI=2,1,2,2,0 enable-hwhs=false message-storage=SM message-start=0 #speed=115200 group=smsbox #smsbox-id=smsbox1 bearerbox-host=127.0.0.1 sendsms-port=13054 global-sender=xxx sendsms-chars=0123456789+- log-file = /var/log/kannel/smsbox.log log-level=0 group=sendsms-user username=kannel password=kannel concatenation=true max-messages=10 #Receive MO sms and direct to specified url group=sms-service keyword=default get-url=http://localhost/receivesms.php?sender=%ptext=%b http://localhost/receivesms.php?sender=%ptext=%b #accept-x-kannel-headers=true #accepted-smsc=smsbox1 max-messages=1 catch-all=true #Set up wap pushes group=wapbox bearerbox-host=127.0.0.1 log-file = /var/log/kannel/wapbox.log access-log=/var/log/kannel/wapacess.log log-level=0 syslog-level=none group=ppg ppg-url=/wappush.php ppg-port=8080 concurrent-pushes=100 global-sender=xxx users=1024 ppg-allow-ip=127.0.0.1 trusted-pi=true group=wap-push-user wap-push-user=wappusher ppg-username=push ppg-password=push allow-ip=*.*.*.* #Use mysql database for storing delivery reports for MT sms group=mysql-connection id=mydlr host=localhost username=root password= database=dlr max-connections=1 group=dlr-db id=mydlr table=dlr field-smsc=smsc field-timestamp=ts field-destination=destination field-source=source field-service=service field-url=url field-mask=mask field-status=status field-boxc-id=boxc #group = sqlbox #id = sqlbox-db #smsbox-id = smsbox #bearerbox-host = 127.0.0.1 #bearerbox-port = 13003 #smsbox-port = 13005 #log-file = /var/log/kannel/sqlbox.log #log-level = 0 # Example MYSQL Connection #group = mysql-connection #id = sqlbox-db #host = localhost #username = root #password = #database = dlr i would really appreciate as comprehensive help as possible.
Re: php Wap push help
The only differences I see are on this part, this is your code:
'push-message push-id='.$wap_push_id.''.\r\n\t.
'address
address-value=WAPPUSH=+'.$country_code.$phone.'/TYPE=p...@ppg.nokia.com/'.\r\n\t.
'quality-of-service delivery-method=unconfirmed
network-required=true network=GSM bearer-required=true
bearer=SMS/'.
\r\n/push-message\r\n.
/pap\r\n\r\n.
This is my original code:
'push-message push-id='.$wap_push_id.''.\r\n.
'address
address-value=WAPPUSH=+'.$country_code.$phone.'/TYPE=PLMN@x/'.\r\n.
'quality-of-service delivery-method=unconfirmed network=GSM
bearer=SMS/'.
/push-message\r\n.
/pap\r\n\r\n.
On the first 2 lines you added a \t, not sure if that would affect,
don't think so, but I had a hard time getting my original code to work,
since PPG was very picky about the line breaks and line feeds
On the third line you added network-required=true and
bearer-required=true, I guess you checked those are valid options
On the 4th line you added a \r\n at the beginning, although it would
make sense for that one to go, it may be the one breaking the thing.
As I mentioned, I spent lots of time tweaking line breaks and line
feeds, cause a missing one or an extra one would break it.
So, I would start by taking out that extra \r\n from the 4th line.
If that doesn't make it, I would take out the \t's
And if that doesn't make it, take out the attributes you added.
Another approach is to send wap push without PPG, via sendsms cgi, which
is much easier and you avoid running an extra service.
See here: http://www.blogalex.com/archives/12
On this article you can find what each hexadecimal value on the
resultant message means, and you can even do a more complete version:
http://mobiforge.com/developing/story/binary-sms-sending-rich-content-devices-using-sms
I'm currently using Alex's approach with something similar to this
(simplified code below):
$udh = '%06%05%04%0B%84%23%F0';
$text = '%1B%06%01%AE%02%05%6A%00%45%C6%0C%03'.hexEncode($url, '%').
'%00%11%03'.hexEncode($si_id,
'%').'%00%07%01%03'.hexEncode($subject, '%').'%00%01%01';
Hope this helps.
On 9/21/11 3:02 AM, christopher serumola wrote:
Yes, these are single lines on the php script. Its only that i use
a dell mini netbook with a small screen size which tends to wrap the
text to the next line when it is long. could that be the cause of the
problem?
On Tue, Sep 20, 2011 at 11:16 PM, Juan Nin jua...@gmail.com
mailto:jua...@gmail.com wrote:
Do you have these lines that on your email look like more than 1
line each as 1 line or more than 1 line? (should be 1)
'!DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP
1.0//EN'.\r\n.
'address address-value=WAPPUSH=
+'.$country_code.$phone.'/TYPE=p...@ppg.nokia.com
mailto:p...@ppg.nokia.com/'.\r\n\t.
'quality-of-service delivery-method=unconfirmed
network-required=true network=GSM bearer-required=true
bearer=SMS/'.
'?xml version=1.0?'.\r\n.
'!DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//EN'.\r
\n.
'indication action=signal-high si-id='.$wap_push_id.' href='.
$push_url .''.$text.'/indication'.\r\n.
X-Kannel-SMSC: $smsc_id\r\n.'Content-Type: multipart/related;
boundary=multipart-boundary; type=application/xml'.\r\n.
On 9/20/11 4:38 PM, chris wrote:
I have installed kannel 1.5.0 on ubuntu 10.0.4 and configured
bearerbox,smsbox and wapbox. All are working well except that
i can't
send wap pushes through ppg from the php sample script posted
in the
mailing lists named wappush.conf. i have checked all the related
postings on the matter and implemented the suggestions without
success.So i need help. The error message i get from the
browser is;
This XML file does not appear to have any style information
associated
with it. The document tree is shown below.
-
pap
badmessage-response code=2000 desc=Not understood due to
malformed
syntax bad-message-fragment=No MIME content/
/pap
The wappush.php script(with corrected line feeds and
indentation) used
is as below;
?php
$country_code = 'xxx';
$phone = '';
$push_url = http://m.yahoo.com http://m.yahoo.com/;
$text = 'Test yahoo wap';
$smsc_id = 'mysmsc-id';
$out = send_wap_push($smsc_id, $country_code, $phone, $push_url,
$text);
echo $out;
function send_wap_push($smsc_id, $country_code, $phone, $push_url,
$text)
{
$host = 'localhost';
$port = '8080';
$url = http://$host:$port;;
$ppg_user = 'push';
$ppg_pass = 'push';
$wap_push_id = get_rand_numbers(5);
$body = --multipart-boundary\r\n.
Content-type: application/xml\r\n\r\n
php Wap push help
); $num = mt_rand(27,36); $rand_id .= assign_rand_value($num); } } return $rand_id; } ? and from the wap log file; 2011-09-20 21:02:23 [1833] [14] INFO: PPG: Accept request /wappush.php from 127.0.0.1 2011-09-20 21:02:23 [1833] [14] WARNING: PPG: No MIME content received, the request unacceptable 2011-09-20 21:02:23 [1833] [14] DEBUG: PPG: send_bad_message_response: telling pi 2011-09-20 21:02:23 [1833] [14] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'. 2011-09-20 21:02:23 [1833] [11] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'. 2011-09-20 21:02:23 [1833] [11] DEBUG: HTTP: Created HTTPClient area 0x99ec880. 2011-09-20 21:02:24 [1833] [14] ERROR: Request /favicon.ico from 127.0.0.1: service not found 2011-09-20 21:02:24 [1833] [14] DEBUG: your configuration uses /wappush.php 2011-09-20 21:02:24 [1833] [14] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'. 2011-09-20 21:03:23 [1833] [10] DEBUG: HTTP: Destroying HTTPClient area 0x99ec880. 2011-09-20 21:03:23 [1833] [10] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'. and my kannel configuration file; group = core admin-port = 13050 smsbox-port = 13051 wapbox-port= 13052 admin-password= chris dlr-storage = mysql wdp-interface-name=* log-file = /var/log/kannel/bearerbox.log log-level=0 box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 group=smsc smsc-id=mysmsc-id port=13053 smsc=at modemtype=huawei device=/dev/ttyUSB0 #speed=115200 my-number=xx validityperiod=167 pin=7172 sim-buffering=true #keepalive=5 sms-center=+xx group=modems id=huawei name=huawei E230 detect-string=huawei init-string=ATZ init-string=AT+CNMI=2,1,2,2,0 enable-hwhs=false message-storage=SM message-start=0 #speed=115200 group=smsbox #smsbox-id=smsbox1 bearerbox-host=127.0.0.1 sendsms-port=13054 global-sender=xxx sendsms-chars=0123456789+- log-file = /var/log/kannel/smsbox.log log-level=0 group=sendsms-user username=kannel password=kannel concatenation=true max-messages=10 #Receive MO sms and direct to specified url group=sms-service keyword=default get-url=http://localhost/receivesms.php?sender=%ptext=%b; #accept-x-kannel-headers=true #accepted-smsc=smsbox1 max-messages=1 catch-all=true #Set up wap pushes group=wapbox bearerbox-host=127.0.0.1 log-file = /var/log/kannel/wapbox.log access-log=/var/log/kannel/wapacess.log log-level=0 syslog-level=none group=ppg ppg-url=/wappush.php ppg-port=8080 concurrent-pushes=100 global-sender=xxx users=1024 ppg-allow-ip=127.0.0.1 trusted-pi=true group=wap-push-user wap-push-user=wappusher ppg-username=push ppg-password=push allow-ip=*.*.*.* #Use mysql database for storing delivery reports for MT sms group=mysql-connection id=mydlr host=localhost username=root password= database=dlr max-connections=1 group=dlr-db id=mydlr table=dlr field-smsc=smsc field-timestamp=ts field-destination=destination field-source=source field-service=service field-url=url field-mask=mask field-status=status field-boxc-id=boxc #group = sqlbox #id = sqlbox-db #smsbox-id = smsbox #bearerbox-host = 127.0.0.1 #bearerbox-port = 13003 #smsbox-port = 13005 #log-file = “/var/log/kannel/sqlbox.log” #log-level = 0 # Example MYSQL Connection #group = mysql-connection #id = sqlbox-db #host = localhost #username = root #password = #database = dlr i would really appreciate as comprehensive help as possible.
Re: php Wap push help
;
case 23:
$rand_value = w;
break;
case 24:
$rand_value = x;
break;
case 25:
$rand_value = y;
break;
case 26:
$rand_value = z;
break;
case 27:
$rand_value = 0;
break;
case 28:
$rand_value = 1;
break;
case 29:
$rand_value = 2;
break;
case 30:
$rand_value = 3;
break;
case 31:
$rand_value = 4;
break;
case 32:
$rand_value = 5;
break;
case 33:
$rand_value = 6;
break;
case 34:
$rand_value = 7;
break;
case 35:
$rand_value = 8;
break;
case 36:
$rand_value = 9;
break;
}
return $rand_value;
}
function get_rand_numbers($length)
{
if($length0)
{
$rand_id=;
for($i=1; $i=$length; $i++)
{
mt_srand((double)microtime() * 100);
$num = mt_rand(27,36);
$rand_id .= assign_rand_value($num);
}
}
return $rand_id;
}
?
and from the wap log file;
2011-09-20 21:02:23 [1833] [14] INFO: PPG: Accept request/wappush.php
from127.0.0.1
2011-09-20 21:02:23 [1833] [14] WARNING: PPG: No MIME content received,
the request unacceptable
2011-09-20 21:02:23 [1833] [14] DEBUG: PPG: send_bad_message_response:
telling pi
2011-09-20 21:02:23 [1833] [14] DEBUG: HTTP: Resetting HTTPClient for
`127.0.0.1'.
2011-09-20 21:02:23 [1833] [11] DEBUG: HTTP: Creating HTTPClient for
`127.0.0.1'.
2011-09-20 21:02:23 [1833] [11] DEBUG: HTTP: Created HTTPClient area
0x99ec880.
2011-09-20 21:02:24 [1833] [14] ERROR: Request/favicon.ico from
127.0.0.1: service not found
2011-09-20 21:02:24 [1833] [14] DEBUG: your configuration
uses /wappush.php
2011-09-20 21:02:24 [1833] [14] DEBUG: HTTP: Resetting HTTPClient for
`127.0.0.1'.
2011-09-20 21:03:23 [1833] [10] DEBUG: HTTP: Destroying HTTPClient area
0x99ec880.
2011-09-20 21:03:23 [1833] [10] DEBUG: HTTP: Destroying HTTPClient for
`127.0.0.1'.
and my kannel configuration file;
group = core
admin-port = 13050
smsbox-port = 13051
wapbox-port= 13052
admin-password= chris
dlr-storage = mysql
wdp-interface-name=*
log-file = /var/log/kannel/bearerbox.log
log-level=0
box-deny-ip = *.*.*.*
box-allow-ip = 127.0.0.1
group=smsc
smsc-id=mysmsc-id
port=13053
smsc=at
modemtype=huawei
device=/dev/ttyUSB0
#speed=115200
my-number=xx
validityperiod=167
pin=7172
sim-buffering=true
#keepalive=5
sms-center=+xx
group=modems
id=huawei
name=huawei E230
detect-string=huawei
init-string=ATZ
init-string=AT+CNMI=2,1,2,2,0
enable-hwhs=false
message-storage=SM
message-start=0
#speed=115200
group=smsbox
#smsbox-id=smsbox1
bearerbox-host=127.0.0.1
sendsms-port=13054
global-sender=xxx
sendsms-chars=0123456789+-
log-file = /var/log/kannel/smsbox.log
log-level=0
group=sendsms-user
username=kannel
password=kannel
concatenation=true
max-messages=10
#Receive MO sms and direct to specified url
group=sms-service
keyword=default
get-url=http://localhost/receivesms.php?sender=%ptext=%b;
#accept-x-kannel-headers=true
#accepted-smsc=smsbox1
max-messages=1
catch-all=true
#Set up wap pushes
group=wapbox
bearerbox-host=127.0.0.1
log-file = /var/log/kannel/wapbox.log
access-log=/var/log/kannel/wapacess.log
log-level=0
syslog-level=none
group=ppg
ppg-url=/wappush.php
ppg-port=8080
concurrent-pushes=100
global-sender=xxx
users=1024
ppg-allow-ip=127.0.0.1
trusted-pi=true
group=wap-push-user
wap-push-user=wappusher
ppg-username=push
ppg-password=push
allow-ip=*.*.*.*
#Use mysql database for storing delivery reports for MT sms
group=mysql-connection
id=mydlr
host=localhost
username=root
password=
database=dlr
max-connections=1
group=dlr-db
id=mydlr
table=dlr
field-smsc=smsc
field-timestamp=ts
field-destination=destination
field-source=source
field-service=service
field-url=url
field-mask=mask
field-status=status
field-boxc-id=boxc
#group = sqlbox
#id = sqlbox-db
#smsbox-id = smsbox
#bearerbox-host = 127.0.0.1
#bearerbox-port = 13003
#smsbox-port = 13005
#log-file = “/var/log/kannel/sqlbox.log”
#log-level = 0
# Example MYSQL Connection
#group = mysql-connection
#id = sqlbox-db
#host = localhost
#username = root
#password =
#database = dlr
i would really appreciate as comprehensive help as possible.
Send WAP PUSH SMS
hii, How to send WAP push sms using kannel server 1.4.3. http://127.0.0.1:13013/cgi-bin/sendsms?username=kannelpassword=from=TESTto=919Xsmsc=testdemodlr-mask=23udh=%06%05%04%C3%4F%00%00text=%http:/ /google.com
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
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
Wap Push : global-sender parameter for multiple SMSCs
Hi User List Im trying to configure Kannel to allow WAP Pushes to two different SMSCs. My problem is - they each require a different originating number (global-sender parameter in the ppg group). Is there a way of specifying the originating number for each WAP Push (similar to the 'from' parameter in sendsms)? This is my config file ... group = core admin-port = ... admin-password = aaa status-password = aaa admin-deny-ip = *.*.*.* admin-allow-ip = 127.0.0.1 smsbox-port = 13001 wapbox-port = 13002 box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 wdp-interface-name = * log-file = /var/log/kannel/bearerbox.log log-level = 0 group = smsc smsc = smpp host = ... port = ... transceiver-mode = true smsc-username = aaa smsc-password = aaa system-type = 'VMA' address-range = msg-id-type = 0 throughput = 30 smsc-id = smsc1 allowed-smsc-id = smsc1 log-file = /var/log/kannel/smsc1.log log-level = 0 group = smsc smsc = smpp host = ... port = ... transceiver-mode = true smsc-username = aaa smsc-password = aaa system-type = 'VMA' address-range = msg-id-type = 0 throughput = 30 smsc-id = smsc2 allowed-smsc-id = smsc2 log-file = /var/log/kannel/smsc2.log log-level = 0 group = wapbox bearerbox-host = 127.0.0.1 log-file = /var/log/kannel/wapbox.log log-level = 0 syslog-level = none group = smsbox smsbox-id = smsbox1 bearerbox-host = localhost sendsms-port = 13131 sendsms-chars = 0123456789 access-log = /var/log/kannel/access.log log-file = /var/log/kannel/smsbox.log log-level = 0 group = smsbox-route smsbox-id = smsbox1 smsc-ids = smsc1;smsc2 group = ppg ppg-url = /wappush ppg-port = 8080 service-name = ppg ppg-smsbox-id = smsbox1 concurrent-pushes = 100 users = 1024 global-sender = 12345 trusted-pi = false ppg-allow-ip = ... group = wap-push-user wap-push-user = pushtest ppg-username = zzz ppg-password = zzz allow-ip = ... group = sms-service keyword = default max-messages = 0 get-url = http://.; group = sendsms-user username = xxx password = xxx forced-smsc = smsc1 group = sendsms-user username = yyy password = yyy forced-smsc = smsc2
Antwort: Wap Push : global-sender parameter for multiple SMSCs
I think you can use my-number = 123456 in each smsc section (group = smsc) Stefan Von:Nick Mee nicholas@gmail.com An: us...@vm1.kannel.org Datum: 13.04.2011 09:35 Betreff:Wap Push : global-sender parameter for multiple SMSCs Gesendet von: users-boun...@vm1.kannel.org Hi User List Im trying to configure Kannel to allow WAP Pushes to two different SMSCs. My problem is - they each require a different originating number (global-sender parameter in the ppg group). Is there a way of specifying the originating number for each WAP Push (similar to the 'from' parameter in sendsms)? This is my config file ... group = core admin-port = ... admin-password = aaa status-password = aaa admin-deny-ip = *.*.*.* admin-allow-ip = 127.0.0.1 smsbox-port = 13001 wapbox-port = 13002 box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 wdp-interface-name = * log-file = /var/log/kannel/bearerbox.log log-level = 0 group = smsc smsc = smpp host = ... port = ... transceiver-mode = true smsc-username = aaa smsc-password = aaa system-type = 'VMA' address-range = msg-id-type = 0 throughput = 30 smsc-id = smsc1 allowed-smsc-id = smsc1 log-file = /var/log/kannel/smsc1.log log-level = 0 group = smsc smsc = smpp host = ... port = ... transceiver-mode = true smsc-username = aaa smsc-password = aaa system-type = 'VMA' address-range = msg-id-type = 0 throughput = 30 smsc-id = smsc2 allowed-smsc-id = smsc2 log-file = /var/log/kannel/smsc2.log log-level = 0 group = wapbox bearerbox-host = 127.0.0.1 log-file = /var/log/kannel/wapbox.log log-level = 0 syslog-level = none group = smsbox smsbox-id = smsbox1 bearerbox-host = localhost sendsms-port = 13131 sendsms-chars = 0123456789 access-log = /var/log/kannel/access.log log-file = /var/log/kannel/smsbox.log log-level = 0 group = smsbox-route smsbox-id = smsbox1 smsc-ids = smsc1;smsc2 group = ppg ppg-url = /wappush ppg-port = 8080 service-name = ppg ppg-smsbox-id = smsbox1 concurrent-pushes = 100 users = 1024 global-sender = 12345 trusted-pi = false ppg-allow-ip = ... group = wap-push-user wap-push-user = pushtest ppg-username = zzz ppg-password = zzz allow-ip = ... group = sms-service keyword = default max-messages = 0 get-url = http://.; group = sendsms-user username = xxx password = xxx forced-smsc = smsc1 group = sendsms-user username = yyy password = yyy forced-smsc = smsc2 -- Der Inhalt dieses E-Mails ist streng vertraulich und möglicherweise gesetzlich besonders geschützt. Dieses E-Mail ist nur für den Adressaten bestimmt. Wenn Sie nicht der beabsichtigte Empfänger sind, ist es Ihnen nicht gestattet und stellt möglicherweise einen Gesetzesverstoss dar, dieses E-Mail zu kopieren, zu verbreiten oder anderweitig zu verwenden. In diesem Fall sollten Sie uns so schnell wie möglich benachrichtigen und dieses E-Mail löschen. Le contenu de ce courriel est strictement confidentiel et probablement légalement protégé. Il n'est adressé qu'aux destinataires mentionnés. Si vous n'en faites pas partie, vous n'avez pas l'autorisation de le copier, ni de le diffuser, ni même de le destiner à un autre usage - ce qui dans chaque cas peut en effet constituer une infraction à la loi. Dans ce cas, vous devriez nous en informer immédiatement et effacer ce courriel. Il contenuto del presente messaggio elettronico è da considerare di massima riservatezza e possibilmente è protetto in modo particolare dalla legge. La presente e-mail è riservata alla sola attenzione della persona destinataria. Se lei non è la persona che avrebbe dovuto ricevere la e-mail, non le è permesso e possibilmente rappresenta una violazione della legge, copiare la presente e-mail, diffonderla o utilizzarla in qualsiasi altro modo. In questo caso lei dovrebbe informarci al più presto possibile e cancellare la presente e-mail.
Re: Antwort: Wap Push : global-sender parameter for multiple SMSCs
my-number might work. You could also start 2 wapbox instances, each one with a different global sender. Lastly there is a push-response element in PAP specification, where you specify sender address and name, but I am not sure if wapbox supports it. Try them, and let us know. BR, Nikos - Original Message - From: stefan.allem...@css.ch To: Nick Mee Cc: us...@vm1.kannel.org ; users-boun...@vm1.kannel.org Sent: Wednesday, April 13, 2011 10:56 AM Subject: Antwort: Wap Push : global-sender parameter for multiple SMSCs I think you can use my-number = 123456 in each smsc section (group = smsc) Stefan Von:Nick Mee nicholas@gmail.com An:us...@vm1.kannel.org Datum:13.04.2011 09:35 Betreff:Wap Push : global-sender parameter for multiple SMSCs Gesendet von:users-boun...@vm1.kannel.org Hi User List Im trying to configure Kannel to allow WAP Pushes to two different SMSCs. My problem is - they each require a different originating number (global-sender parameter in the ppg group). Is there a way of specifying the originating number for each WAP Push (similar to the 'from' parameter in sendsms)? This is my config file ... group = core admin-port = ... admin-password = aaa status-password = aaa admin-deny-ip = *.*.*.* admin-allow-ip = 127.0.0.1 smsbox-port = 13001 wapbox-port = 13002 box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 wdp-interface-name = * log-file = /var/log/kannel/bearerbox.log log-level = 0 group = smsc smsc = smpp host = ... port = ... transceiver-mode = true smsc-username = aaa smsc-password = aaa system-type = 'VMA' address-range = msg-id-type = 0 throughput = 30 smsc-id = smsc1 allowed-smsc-id = smsc1 log-file = /var/log/kannel/smsc1.log log-level = 0 group = smsc smsc = smpp host = ... port = ... transceiver-mode = true smsc-username = aaa smsc-password = aaa system-type = 'VMA' address-range = msg-id-type = 0 throughput = 30 smsc-id = smsc2 allowed-smsc-id = smsc2 log-file = /var/log/kannel/smsc2.log log-level = 0 group = wapbox bearerbox-host = 127.0.0.1 log-file = /var/log/kannel/wapbox.log log-level = 0 syslog-level = none group = smsbox smsbox-id = smsbox1 bearerbox-host = localhost sendsms-port = 13131 sendsms-chars = 0123456789 access-log = /var/log/kannel/access.log log-file = /var/log/kannel/smsbox.log log-level = 0 group = smsbox-route smsbox-id = smsbox1 smsc-ids = smsc1;smsc2 group = ppg ppg-url = /wappush ppg-port = 8080 service-name = ppg ppg-smsbox-id = smsbox1 concurrent-pushes = 100 users = 1024 global-sender = 12345 trusted-pi = false ppg-allow-ip = ... group = wap-push-user wap-push-user = pushtest ppg-username = zzz ppg-password = zzz allow-ip = ... group = sms-service keyword = default max-messages = 0 get-url = http://.; group = sendsms-user username = xxx password = xxx forced-smsc = smsc1 group = sendsms-user username = yyy password = yyy forced-smsc = smsc2 -- Der Inhalt dieses E-Mails ist streng vertraulich und moglicherweise gesetzlich besonders geschutzt. Dieses E-Mail ist nur fur den Adressaten bestimmt. Wenn Sie nicht der beabsichtigte Empfanger sind, ist es Ihnen nicht gestattet und stellt moglicherweise einen Gesetzesverstoss dar, dieses E-Mail zu kopieren, zu verbreiten oder anderweitig zu verwenden. In diesem Fall sollten Sie uns so schnell wie moglich benachrichtigen und dieses E-Mail loschen. Le contenu de ce courriel est strictement confidentiel et probablement legalement protege. Il n'est adresse qu'aux destinataires mentionnes. Si vous n'en faites pas partie, vous n'avez pas l'autorisation de le copier, ni de le diffuser, ni meme de le destiner a un autre usage - ce qui dans chaque cas peut en effet constituer une infraction a la loi. Dans ce cas, vous devriez nous en informer immediatement et effacer ce courriel. Il contenuto del presente messaggio elettronico e da considerare di massima riservatezza e possibilmente e protetto in modo particolare dalla legge. La presente e-mail e riservata alla sola attenzione della persona destinataria. Se lei non e la persona che avrebbe dovuto ricevere la e-mail, non le e permesso e possibilmente rappresenta una violazione della legge, copiare la presente e-mail, diffonderla o utilizzarla in qualsiasi altro modo. In questo caso lei dovrebbe informarci al piu presto possibile e cancellare la presente e-mail.
Re: Antwort: Wap Push : global-sender parameter for multiple SMSCs
Sorry for the spam, forgot to give the reference for the pap spec: http://www.wapforum.org/DTD/pap_2.0.dtd BR, Nikos - Original Message - From: Nikos Balkanas nbalka...@gmail.com To: Nick Mee nicholas@gmail.com; stefan.allem...@css.ch Cc: users@kannel.org Sent: Wednesday, April 13, 2011 11:05 AM Subject: Re: Antwort: Wap Push : global-sender parameter for multiple SMSCs my-number might work. You could also start 2 wapbox instances, each one with a different global sender. Lastly there is a push-response element in PAP specification, where you specify sender address and name, but I am not sure if wapbox supports it. Try them, and let us know. BR, Nikos - Original Message - From: stefan.allem...@css.ch To: Nick Mee Cc: us...@vm1.kannel.org ; users-boun...@vm1.kannel.org Sent: Wednesday, April 13, 2011 10:56 AM Subject: Antwort: Wap Push : global-sender parameter for multiple SMSCs I think you can use my-number = 123456 in each smsc section (group = smsc) Stefan Von:Nick Mee nicholas@gmail.com An:us...@vm1.kannel.org Datum:13.04.2011 09:35 Betreff:Wap Push : global-sender parameter for multiple SMSCs Gesendet von:users-boun...@vm1.kannel.org Hi User List Im trying to configure Kannel to allow WAP Pushes to two different SMSCs. My problem is - they each require a different originating number (global-sender parameter in the ppg group). Is there a way of specifying the originating number for each WAP Push (similar to the 'from' parameter in sendsms)? This is my config file ... group = core admin-port = ... admin-password = aaa status-password = aaa admin-deny-ip = *.*.*.* admin-allow-ip = 127.0.0.1 smsbox-port = 13001 wapbox-port = 13002 box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 wdp-interface-name = * log-file = /var/log/kannel/bearerbox.log log-level = 0 group = smsc smsc = smpp host = ... port = ... transceiver-mode = true smsc-username = aaa smsc-password = aaa system-type = 'VMA' address-range = msg-id-type = 0 throughput = 30 smsc-id = smsc1 allowed-smsc-id = smsc1 log-file = /var/log/kannel/smsc1.log log-level = 0 group = smsc smsc = smpp host = ... port = ... transceiver-mode = true smsc-username = aaa smsc-password = aaa system-type = 'VMA' address-range = msg-id-type = 0 throughput = 30 smsc-id = smsc2 allowed-smsc-id = smsc2 log-file = /var/log/kannel/smsc2.log log-level = 0 group = wapbox bearerbox-host = 127.0.0.1 log-file = /var/log/kannel/wapbox.log log-level = 0 syslog-level = none group = smsbox smsbox-id = smsbox1 bearerbox-host = localhost sendsms-port = 13131 sendsms-chars = 0123456789 access-log = /var/log/kannel/access.log log-file = /var/log/kannel/smsbox.log log-level = 0 group = smsbox-route smsbox-id = smsbox1 smsc-ids = smsc1;smsc2 group = ppg ppg-url = /wappush ppg-port = 8080 service-name = ppg ppg-smsbox-id = smsbox1 concurrent-pushes = 100 users = 1024 global-sender = 12345 trusted-pi = false ppg-allow-ip = ... group = wap-push-user wap-push-user = pushtest ppg-username = zzz ppg-password = zzz allow-ip = ... group = sms-service keyword = default max-messages = 0 get-url = http://.; group = sendsms-user username = xxx password = xxx forced-smsc = smsc1 group = sendsms-user username = yyy password = yyy forced-smsc = smsc2 -- Der Inhalt dieses E-Mails ist streng vertraulich und moglicherweise gesetzlich besonders geschutzt. Dieses E-Mail ist nur fur den Adressaten bestimmt. Wenn Sie nicht der beabsichtigte Empfanger sind, ist es Ihnen nicht gestattet und stellt moglicherweise einen Gesetzesverstoss dar, dieses E-Mail zu kopieren, zu verbreiten oder anderweitig zu verwenden. In diesem Fall sollten Sie uns so schnell wie moglich benachrichtigen und dieses E-Mail loschen. Le contenu de ce courriel est strictement confidentiel et probablement legalement protege. Il n'est adresse qu'aux destinataires mentionnes. Si vous n'en faites pas partie, vous n'avez pas l'autorisation de le copier, ni de le diffuser, ni meme de le destiner a un autre usage - ce qui dans chaque cas peut en effet constituer une infraction a la loi. Dans ce cas, vous devriez nous en informer immediatement et effacer ce courriel. Il contenuto del presente messaggio elettronico e da considerare di massima riservatezza e possibilmente e protetto in modo particolare dalla legge. La presente e-mail e riservata alla sola attenzione della persona destinataria. Se lei non e la persona che avrebbe dovuto ricevere la e-mail, non le e permesso e possibilmente rappresenta una violazione della legge, copiare la presente e-mail, diffonderla o utilizzarla in qualsiasi altro modo. In questo caso lei dovrebbe informarci al piu presto possibile e cancellare la presente e-mail.
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 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: replacing WAP Push on mobile phone
I was able to replace the reached SMS on the phone using pid. 2011/2/14 Nikos Balkanas nbalka...@gmail.com You cannot replace an SMS once it has reached the mobile. You just send a new one. You could replace an SMS at the SMSc, before reaching the mobile, but kannel doesn't support that issue. BR, Nikos - Original Message - From: Latitude Berlin To: users Sent: Monday, February 14, 2011 4:39 PM Subject: replacing WAP Push on mobile phone Hi Everyone, How can I replace a WAP Push message sent via Kannel on a mobile phone? I can do this for plain SMS by using 'pid' in the HTTP send request. Regards.
Re: replacing WAP Push on mobile phone
You should be able to produce the same result if you encode your wap push by hand and send via sendsms specifying text (user data), udh and binary encoding. I know my operation uses the pid replace functionality when sending out notifications from their voice mail system. However I suspect that support for this depends on the handset receiving the message. /Jacob On Tue, 2011-02-15 at 13:19 +0100, Latitude Berlin wrote: I was able to replace the reached SMS on the phone using pid. 2011/2/14 Nikos Balkanas nbalka...@gmail.com You cannot replace an SMS once it has reached the mobile. You just send a new one. You could replace an SMS at the SMSc, before reaching the mobile, but kannel doesn't support that issue. BR, Nikos - Original Message - From: Latitude Berlin To: users Sent: Monday, February 14, 2011 4:39 PM Subject: replacing WAP Push on mobile phone Hi Everyone, How can I replace a WAP Push message sent via Kannel on a mobile phone? I can do this for plain SMS by using 'pid' in the HTTP send request. Regards.
replacing WAP Push on mobile phone
Hi Everyone, How can I replace a WAP Push message sent via Kannel on a mobile phone? I can do this for plain SMS by using 'pid' in the HTTP send request. Regards.
Re: replacing WAP Push on mobile phone
You cannot replace an SMS once it has reached the mobile. You just send a new one. You could replace an SMS at the SMSc, before reaching the mobile, but kannel doesn't support that issue. BR, Nikos - Original Message - From: Latitude Berlin To: users Sent: Monday, February 14, 2011 4:39 PM Subject: replacing WAP Push on mobile phone Hi Everyone, How can I replace a WAP Push message sent via Kannel on a mobile phone? I can do this for plain SMS by using 'pid' in the HTTP send request. Regards.
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 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
Question on WAP PUSH
Hi all. I need a little help with WAP PUSH (I think). let me describe the use case: we need to download a java application (packaged as a .jad file) to a large number of phones. in the past, when we did not have a kannel installation, we used to do it this way: we would give our mobile provider a list of phone numbers, and he would send a special SMS (I think a WAP PUSH SMS), containing the URL of our distribution server, which contained the application image. upon receipt of this SMS, a human operator would open this message, as a result of which, the phone would (after confirmation) proceed to download and install the application. we need to do same, but this time, we have changed our corporate mobile operator, and the new one is reluctant to do this for us. instead, they have provided us with a connection to their smsc, and they ask us to send wap Push SMS ourselves. I am not sure on how to do this with kannel. I have succesfully set up the connection to the smsc (SMPP), and I can send messages just fine. however, when it comes to sending WAP PUSH messages, I am clueless, and the documentation is rather terse on this, and assumes you know what you are doing, which I don't... The operator told me that they support wap push and that I have to set DCS to 245. period. could somebody that has done this before, help me with this, please ?
Re: Question on WAP PUSH
Hi, I have done some wap-push in my days, although not recently. There are 2 ways to about it: 1) wapbox. Advantage more options. Disadvantage more difficult. 2) smsbox. Advantage simple. Disadvantage can only push a URL to amobile using standard settings. (1) is detailed in UG. You need to to post a mime-encoded file which consists of 2 xml parts: PAP and SI. (2) You send a binary SMS with the URL with the sendsms interface. You need special UDH headers, and wbxml encoded URL. If you search the archives you will find a php script by Alex G who does just that. BR, Nikos - Original Message - From: Cariotoglou Mike m...@singular.gr To: users@kannel.org Sent: Tuesday, September 21, 2010 5:36 PM Subject: Question on WAP PUSH Hi all. I need a little help with WAP PUSH (I think). let me describe the use case: we need to download a java application (packaged as a .jad file) to a large number of phones. in the past, when we did not have a kannel installation, we used to do it this way: we would give our mobile provider a list of phone numbers, and he would send a special SMS (I think a WAP PUSH SMS), containing the URL of our distribution server, which contained the application image. upon receipt of this SMS, a human operator would open this message, as a result of which, the phone would (after confirmation) proceed to download and install the application. we need to do same, but this time, we have changed our corporate mobile operator, and the new one is reluctant to do this for us. instead, they have provided us with a connection to their smsc, and they ask us to send wap Push SMS ourselves. I am not sure on how to do this with kannel. I have succesfully set up the connection to the smsc (SMPP), and I can send messages just fine. however, when it comes to sending WAP PUSH messages, I am clueless, and the documentation is rather terse on this, and assumes you know what you are doing, which I don't... The operator told me that they support wap push and that I have to set DCS to 245. period. could somebody that has done this before, help me with this, please ?
Re: Question on WAP PUSH
and wbxml encoded URL. Sorry, I was not clear on this. I mean, wbxml encoded content, which in this case is the URL you are sending to the mobile. BR, Nikos - Original Message - From: Nikos Balkanas nbalka...@gmail.com To: Cariotoglou Mike m...@singular.gr; users@kannel.org Sent: Tuesday, September 21, 2010 6:04 PM Subject: Re: Question on WAP PUSH Hi, I have done some wap-push in my days, although not recently. There are 2 ways to about it: 1) wapbox. Advantage more options. Disadvantage more difficult. 2) smsbox. Advantage simple. Disadvantage can only push a URL to amobile using standard settings. (1) is detailed in UG. You need to to post a mime-encoded file which consists of 2 xml parts: PAP and SI. (2) You send a binary SMS with the URL with the sendsms interface. You need special UDH headers, and wbxml encoded URL. If you search the archives you will find a php script by Alex G who does just that. BR, Nikos - Original Message - From: Cariotoglou Mike m...@singular.gr To: users@kannel.org Sent: Tuesday, September 21, 2010 5:36 PM Subject: Question on WAP PUSH Hi all. I need a little help with WAP PUSH (I think). let me describe the use case: we need to download a java application (packaged as a .jad file) to a large number of phones. in the past, when we did not have a kannel installation, we used to do it this way: we would give our mobile provider a list of phone numbers, and he would send a special SMS (I think a WAP PUSH SMS), containing the URL of our distribution server, which contained the application image. upon receipt of this SMS, a human operator would open this message, as a result of which, the phone would (after confirmation) proceed to download and install the application. we need to do same, but this time, we have changed our corporate mobile operator, and the new one is reluctant to do this for us. instead, they have provided us with a connection to their smsc, and they ask us to send wap Push SMS ourselves. I am not sure on how to do this with kannel. I have succesfully set up the connection to the smsc (SMPP), and I can send messages just fine. however, when it comes to sending WAP PUSH messages, I am clueless, and the documentation is rather terse on this, and assumes you know what you are doing, which I don't... The operator told me that they support wap push and that I have to set DCS to 245. period. could somebody that has done this before, help me with this, please ?
RE: Question on WAP PUSH
ok, I will try (2) first. where does the DCS value specified by the smsc (vodafone) come into play ? they said I had to use 245. where do I put this ? also, I found the php script you mentioned, and I am curious as to what are all the magic numbers. for example: $fields[udh] = '%06%05%04%0B%84%23%F0'; $fields[text] = '%1B%06%01%AE%02%05%6A%00%45%C6%0C%03'. hex_encode($fields['link'], '%'). '%00%01%03'. hex_encode($fields['title'], '%'). '%00%01%01'; a lot of binary numbers here, do you know what they do, and whether they are standard, ie will they work with greek vodafone ? -Original Message- From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: Tuesday, September 21, 2010 6:05 PM To: Cariotoglou Mike; users@kannel.org Subject: Re: Question on WAP PUSH Hi, I have done some wap-push in my days, although not recently. There are 2 ways to about it: 1) wapbox. Advantage more options. Disadvantage more difficult. 2) smsbox. Advantage simple. Disadvantage can only push a URL to amobile using standard settings. (1) is detailed in UG. You need to to post a mime-encoded file which consists of 2 xml parts: PAP and SI. (2) You send a binary SMS with the URL with the sendsms interface. You need special UDH headers, and wbxml encoded URL. If you search the archives you will find a php script by Alex G who does just that. BR, Nikos - Original Message - From: Cariotoglou Mike m...@singular.gr To: users@kannel.org Sent: Tuesday, September 21, 2010 5:36 PM Subject: Question on WAP PUSH Hi all. I need a little help with WAP PUSH (I think). let me describe the use case: we need to download a java application (packaged as a .jad file) to a large number of phones. in the past, when we did not have a kannel installation, we used to do it this way: we would give our mobile provider a list of phone numbers, and he would send a special SMS (I think a WAP PUSH SMS), containing the URL of our distribution server, which contained the application image. upon receipt of this SMS, a human operator would open this message, as a result of which, the phone would (after confirmation) proceed to download and install the application. we need to do same, but this time, we have changed our corporate mobile operator, and the new one is reluctant to do this for us. instead, they have provided us with a connection to their smsc, and they ask us to send wap Push SMS ourselves. I am not sure on how to do this with kannel. I have succesfully set up the connection to the smsc (SMPP), and I can send messages just fine. however, when it comes to sending WAP PUSH messages, I am clueless, and the documentation is rather terse on this, and assumes you know what you are doing, which I don't... The operator told me that they support wap push and that I have to set DCS to 245. period. could somebody that has done this before, help me with this, please ?
Re: Question on WAP PUSH
Hi, Since you chose to go ahead with (2) the dcs value is specified same as in regular sms. Remember this is binary SMS, so coding should be 1. The binary characters you see is the text part (aka URL), wbxml (binary xml) encoded for wap. BR, Nikos - Original Message - From: Cariotoglou Mike m...@singular.gr To: users@kannel.org Sent: Tuesday, September 21, 2010 8:47 PM Subject: RE: Question on WAP PUSH ok, I will try (2) first. where does the DCS value specified by the smsc (vodafone) come into play ? they said I had to use 245. where do I put this ? also, I found the php script you mentioned, and I am curious as to what are all the magic numbers. for example: $fields[udh] = '%06%05%04%0B%84%23%F0'; $fields[text] = '%1B%06%01%AE%02%05%6A%00%45%C6%0C%03'. hex_encode($fields['link'], '%'). '%00%01%03'. hex_encode($fields['title'], '%'). '%00%01%01'; a lot of binary numbers here, do you know what they do, and whether they are standard, ie will they work with greek vodafone ? -Original Message- From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: Tuesday, September 21, 2010 6:05 PM To: Cariotoglou Mike; users@kannel.org Subject: Re: Question on WAP PUSH Hi, I have done some wap-push in my days, although not recently. There are 2 ways to about it: 1) wapbox. Advantage more options. Disadvantage more difficult. 2) smsbox. Advantage simple. Disadvantage can only push a URL to amobile using standard settings. (1) is detailed in UG. You need to to post a mime-encoded file which consists of 2 xml parts: PAP and SI. (2) You send a binary SMS with the URL with the sendsms interface. You need special UDH headers, and wbxml encoded URL. If you search the archives you will find a php script by Alex G who does just that. BR, Nikos - Original Message - From: Cariotoglou Mike m...@singular.gr To: users@kannel.org Sent: Tuesday, September 21, 2010 5:36 PM Subject: Question on WAP PUSH Hi all. I need a little help with WAP PUSH (I think). let me describe the use case: we need to download a java application (packaged as a .jad file) to a large number of phones. in the past, when we did not have a kannel installation, we used to do it this way: we would give our mobile provider a list of phone numbers, and he would send a special SMS (I think a WAP PUSH SMS), containing the URL of our distribution server, which contained the application image. upon receipt of this SMS, a human operator would open this message, as a result of which, the phone would (after confirmation) proceed to download and install the application. we need to do same, but this time, we have changed our corporate mobile operator, and the new one is reluctant to do this for us. instead, they have provided us with a connection to their smsc, and they ask us to send wap Push SMS ourselves. I am not sure on how to do this with kannel. I have succesfully set up the connection to the smsc (SMPP), and I can send messages just fine. however, when it comes to sending WAP PUSH messages, I am clueless, and the documentation is rather terse on this, and assumes you know what you are doing, which I don't... The operator told me that they support wap push and that I have to set DCS to 245. period. could somebody that has done this before, help me with this, please ?
Re: Question on WAP PUSH
Yes, they are standard and should work. Here you can read a bit about them to understand it a bit more: http://mobiforge.com/developing/story/binary-sms-sending-rich-content-devices-using-sms The example provided on that article includes a bit more things than Alex's version. On Tue, Sep 21, 2010 at 2:47 PM, Cariotoglou Mike m...@singular.gr wrote: ok, I will try (2) first. where does the DCS value specified by the smsc (vodafone) come into play ? they said I had to use 245. where do I put this ? also, I found the php script you mentioned, and I am curious as to what are all the magic numbers. for example: $fields[udh] = '%06%05%04%0B%84%23%F0'; $fields[text] = '%1B%06%01%AE%02%05%6A%00%45%C6%0C%03'. hex_encode($fields['link'], '%'). '%00%01%03'. hex_encode($fields['title'], '%'). '%00%01%01'; a lot of binary numbers here, do you know what they do, and whether they are standard, ie will they work with greek vodafone ? -Original Message- From: Nikos Balkanas [mailto:nbalka...@gmail.com] Sent: Tuesday, September 21, 2010 6:05 PM To: Cariotoglou Mike; users@kannel.org Subject: Re: Question on WAP PUSH Hi, I have done some wap-push in my days, although not recently. There are 2 ways to about it: 1) wapbox. Advantage more options. Disadvantage more difficult. 2) smsbox. Advantage simple. Disadvantage can only push a URL to amobile using standard settings. (1) is detailed in UG. You need to to post a mime-encoded file which consists of 2 xml parts: PAP and SI. (2) You send a binary SMS with the URL with the sendsms interface. You need special UDH headers, and wbxml encoded URL. If you search the archives you will find a php script by Alex G who does just that. BR, Nikos - Original Message - From: Cariotoglou Mike m...@singular.gr To: users@kannel.org Sent: Tuesday, September 21, 2010 5:36 PM Subject: Question on WAP PUSH Hi all. I need a little help with WAP PUSH (I think). let me describe the use case: we need to download a java application (packaged as a .jad file) to a large number of phones. in the past, when we did not have a kannel installation, we used to do it this way: we would give our mobile provider a list of phone numbers, and he would send a special SMS (I think a WAP PUSH SMS), containing the URL of our distribution server, which contained the application image. upon receipt of this SMS, a human operator would open this message, as a result of which, the phone would (after confirmation) proceed to download and install the application. we need to do same, but this time, we have changed our corporate mobile operator, and the new one is reluctant to do this for us. instead, they have provided us with a connection to their smsc, and they ask us to send wap Push SMS ourselves. I am not sure on how to do this with kannel. I have succesfully set up the connection to the smsc (SMPP), and I can send messages just fine. however, when it comes to sending WAP PUSH messages, I am clueless, and the documentation is rather terse on this, and assumes you know what you are doing, which I don't... The operator told me that they support wap push and that I have to set DCS to 245. period. could somebody that has done this before, help me with this, please ?
WAP Push
Hi, Can any body give me sample of WAP Push Link. Its really helpful for me. -- Regards Sapna
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
WTA Send WAP Push with SQLBox
Hi List, I've searched the archives to find solution on how to send WAP Push with SQLBox, tried all suggested but none work. Is there someone who is sucessfully send WAP Push with SQLBox? Thanks. sangprabv sangpr...@gmail.com
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:] [from
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
] DEBUG: re-queing SMS not-yet-to-be resent 2010-06-12 10:54:19 [20160] [7] DEBUG: sms_router: time to sleep 30.00 secs. ... -- ---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 my-number = +49157 log-file = /var/log/kannel/smsc.log log-level = 0 keepalive = 20 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 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 --- 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
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.
WAP-Push with Nokia 6210
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: Destroying HTTPClient for `127.0.0.1'. bearerbox: .. 2010-06-12 02:24:53 [23967] [7] DEBUG: sms_router: gwlist_len = 1 2010-06-12 02:24:53 [23967] [7] DEBUG: sms_router: handling message (0x1598d10 vs 0x1598d10) 2010-06-12 02:24:53 [23967] [7] DEBUG: re-queing SMS not-yet-to-be resent 2010-06-12 02:24:53 [23967] [7] DEBUG: sms_router: handling message (0x1598d10 vs 0x1598d10) 2010-06-12 02:24:53 [23967] [7] DEBUG: re-queing SMS not-yet-to-be resent 2010-06-12 02:24:53 [23967] [7] DEBUG
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
WAP-Push with Nokia 6210 as SMSC
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 = AT+CNMI=1,2,0,1,0 keepalive-cmd = AT+CBC;+CSQ enable-mms = true 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 signature.asc Description: Digital signature
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 = AT+CNMI
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
WAP Push messages don't reach receiver
Kannel-Version: 1.4.3 Handset (SMSC): Motorola RAZR V3 OS: Debian / Linux 2.6.33.3 #1 SMP x86_64 GNU/Linux Hi together, if I try to send a WAP push I get the following logs. I can see the message in the store-status, but kannel won't send it to the receiver phone. As sender I see '1234' instead of the global sender value in the store status. My kannel.conf and the script triggerd by myself to send a push is below, too. I use a Motorola RAZR V3 as SMSC mobile phone. I can send and receive normal SMS. The receiver handset is configured to accept WAP push. An other issue is that after a restart of kannel the phone is no longer accessible, until i put it out of the USB-Port and plug it in again. Thx in advance Thomas SMSC: [9936] [6] DEBUG: AT2[SMSC_01]: detecting modem speed. [9936] [6] INFO: AT2[SMSC_01]: opening device [9936] [6] DEBUG: AT2[SMSC_01]: device opened. Telnet mode = 0 [9936] [6] DEBUG: AT2[SMSC_01]: device opened [9936] [6] INFO: AT2[SMSC_01]: speed set to 115200 [9936] [6] DEBUG: AT2[SMSC_01]: -- ^M [9936] [6] DEBUG: AT2[SMSC_01]: -- AT^M [9936] [6] DEBUG: AT2[SMSC_01]: -- AT [9936] [6] DEBUG: AT2[SMSC_01]: -- OK [9936] [6] INFO: AT2[SMSC_01]: Closing device [9936] [6] INFO: AT2[SMSC_01]: detect speed is 115200 [9936] [6] DEBUG: AT2[SMSC_01]: detecting modem type [9936] [6] INFO: AT2[SMSC_01]: opening device [9936] [6] DEBUG: AT2[SMSC_01]: device opened. Telnet mode = 0 [9936] [6] DEBUG: AT2[SMSC_01]: device opened [9936] [6] INFO: AT2[SMSC_01]: speed set to 115200 [9936] [6] DEBUG: AT2[SMSC_01]: -- ^M [9936] [6] DEBUG: AT2[SMSC_01]: -- AT^M [9936] [6] DEBUG: AT2[SMSC_01]: -- AT [9936] [6] DEBUG: AT2[SMSC_01]: -- OK [9936] [6] DEBUG: AT2[SMSC_01]: -- ATF^M [9936] [6] DEBUG: AT2[SMSC_01]: -- ATF [9936] [6] DEBUG: AT2[SMSC_01]: -- OK [9936] [6] DEBUG: AT2[SMSC_01]: -- ATE0^M [9936] [6] DEBUG: AT2[SMSC_01]: -- ATE0 [9936] [6] DEBUG: AT2[SMSC_01]: -- OK [9936] [6] DEBUG: AT2[SMSC_01]: -- ATI^M [9936] [6] DEBUG: AT2[SMSC_01]: -- 144 [9936] [6] DEBUG: AT2[SMSC_01]: -- OK [9936] [6] DEBUG: AT2[SMSC_01]: Cannot detect modem, using generic [9936] [6] DEBUG: AT2[SMSC_01]: Reading modem definitions from /etc/kannel/kannel.conf [9936] [6] DEBUG: AT2[SMSC_01]: Found 1 modems in config [9936] [6] DEBUG: AT2[SMSC_01]: -- AT+CSMS=?^M [9936] [6] DEBUG: AT2[SMSC_01]: -- +CSMS: (128) [9936] [6] DEBUG: AT2[SMSC_01]: -- OK [9936] [6] INFO: AT2[SMSC_01]: Closing device [9936] [6] INFO: AT2[SMSC_01]: opening device [9936] [6] DEBUG: AT2[SMSC_01]: device opened. Telnet mode = 0 [9936] [6] DEBUG: AT2[SMSC_01]: device opened [9936] [6] INFO: AT2[SMSC_01]: Logging in [9936] [6] INFO: AT2[SMSC_01]: init device [9936] [6] INFO: AT2[SMSC_01]: speed set to 115200 [9936] [6] DEBUG: AT2[SMSC_01]: -- ATZ^M [9936] [6] DEBUG: AT2[SMSC_01]: -- OK [9936] [6] DEBUG: AT2[SMSC_01]: -- AT^M [9936] [6] DEBUG: AT2[SMSC_01]: -- AT [9936] [6] DEBUG: AT2[SMSC_01]: -- OK [9936] [6] DEBUG: AT2[SMSC_01]: -- ATF^M [9936] [6] DEBUG: AT2[SMSC_01]: -- ATF [9936] [6] DEBUG: AT2[SMSC_01]: -- OK [9936] [6] DEBUG: AT2[SMSC_01]: -- ATE0^M [9936] [6] DEBUG: AT2[SMSC_01]: -- ATE0 [9936] [6] DEBUG: AT2[SMSC_01]: -- OK [9936] [6] DEBUG: AT2[SMSC_01]: -- AT+IFC=2,2^M [9936] [6] DEBUG: AT2[SMSC_01]: -- OK [9936] [6] DEBUG: AT2[SMSC_01]: -- AT+CPIN?^M [9936] [6] DEBUG: AT2[SMSC_01]: -- +CPIN: READY [9936] [6] DEBUG: AT2[SMSC_01]: -- OK [9936] [6] DEBUG: AT2[SMSC_01]: -- AT+CSCA=+49177061^M [9936] [6] DEBUG: AT2[SMSC_01]: -- OK [9936] [6] DEBUG: AT2[SMSC_01]: -- AT+CMGF=0^M [9936] [6] DEBUG: AT2[SMSC_01]: -- OK [9936] [6] DEBUG: AT2[SMSC_01]: -- AT+CSMS=?^M [9936] [6] DEBUG: AT2[SMSC_01]: -- +CSMS: (128) [9936] [6] DEBUG: AT2[SMSC_01]: -- OK [9936] [6] DEBUG: AT2[SMSC_01]: -- AT+CMEE=2;+CNMI=3,1,0,0,0^M [9936] [6] DEBUG: AT2[SMSC_01]: -- OK [9936] [6] INFO: AT2[SMSC_01]: AT SMSC successfully opened. [9936] [6] DEBUG: AT2[SMSC_01]: TP-Validity-Period: 24.0 hours [9936] [6] DEBUG: AT2[SMSC_01]: -- AT+CMGS=93^M [9936] [6] DEBUG: AT2[SMSC_01]: -- [9936] [6] DEBUG: AT2[SMSC_01]: send command status: 1 [9936] [6] DEBUG: AT2[SMSC_01]: -- 0051000C91947199??0004A74F0 605040B8423F605AE8DC0C39302056A0045C608110331323733353137393432 000C037761702E676F6F676C652E636F6D000103546869732069732061206675636 B696E672074657374000101 [9936] [6] DEBUG: AT2[SMSC_01]: -- ^Z [9936] [6] DEBUG: AT2[SMSC_01]: send command status: -1 WAP Box: = [10043] [0] INFO: Added logfile `/var/log/kannel/wapbox.log' with level `0'. [10043] [0] INFO: Starting to log to file /var/log/kannel/wapbox.log level 0 [10043] [0] DEBUG: syslog parameter is none [10043] [0] INFO: Logging accesses to '/var/log/kannel/wap-access.log'. [10043] [0] INFO: Started access logfile `/var/log/kannel/wap-access.log'. [10043] [0] INFO: [10043] [0] INFO: Kannel wapbox version 1.4.3 starting up. [10043] [0] DEBUG
Re: Can't change coding for wap-push
You're sending 67 (0x43) because you need to patch kannel to change the default esm_class. Here's how to do it: On gw/smsc/smsc_smpp.c, search for this line: pdu-u.submit_sm.esm_class = ESM_CLASS_SUBMIT_STORE_AND_FORWARD_MODE; (Should be around line 868) and change it to look like this: pdu-u.submit_sm.esm_class = ESM_CLASS_SUBMIT_DEFAULT_SMSC_MODE; Recompile, reinstall, and that will get you 0x40 instead of 0x43. Regarding the data_coding, first of all, the only presence of an udh field forces kannel to use 8 BIT. Try adding this parameter to your send-sms url: alt-dcs=1 and re-post the pdu dump. You should have at least 0xF0 with this setting. Hope it helps, Alex 2010/5/2 Nikos Balkanas nbalka...@gmail.com Hi, 1) You cannot configure esm_class in kannel. It is hard-coded. 2) You don't want to use 7bit encoding for wap-push. It is binary sms, therefore it has to be 8bit encoding. Your text is 8bit, therefore just skip the coding variable. 3) The reason you are getting it as SMS is that you use wrong udh header. Google for the correct for wappush. 4) Make sure that your coding is correct wbxml. BR, Nikos - Original Message - *From:* Alejandro Woywood awoyw...@gmail.com *To:* users@kannel.org *Sent:* Sunday, May 02, 2010 3:17 AM *Subject:* Can't change coding for wap-push Hi, please help! We have been trying to set up Kannel to work with an SMPP for sending wap-push. We could send sms, but when trying to send wap-push it is received as a sms in the phone. The operator told us to use 7 bit encoding and these settings: esm_class: 64 (0x0040) Data_coding: 245 (0xf5), (or 0x05, or 0x0f) Charset: ISO 8859-1 How can we force those settings in kannel? We tried adding “esm_class=40” to the config, but then kannel doesn’t start... This is our current config: group = smsc smsc = smpp smsc-id = xxx host = port = 3000 transceiver-mode = false receive-port = 3000 smsc-username = xxx smsc-password = system-type = smpp interface-version = 34 source-addr-ton = 1 source-addr-npi = 1 source-addr-autodetect = no dest-addr-ton = 1 dest-addr-npi = 1 bind-addr-ton = 1 bind-addr-npi = 1 alt-charset = ISO-8859-1 This is the wap-push we’re trying to send: http://localhost:13013/cgi-bin/sendsms?user=xxxpass=xxxfrom=1072to=+xxxudh=%06%05%04%0B%84%23%F0text=%1B%06%01%AE%02%05%6A%00%45%C6% 0C%03%67%6F%6F%67%6C%65%2E%6D%6F%62%69%00%01%03%67%6F%74%6F%00%01%01coding=0 This is the bearerbox log 2010-05-01 17:40:42 [15270] [19] DEBUG: boxc_receiver: sms received 2010-05-01 17:40:42 [15270] [19] DEBUG: send_msg: sending msg to box: 127.0.0.1 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP[send_xxx]: Manually forced source addr ton = 1, source add npi = 1 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP[send_xxx]: Manually forced dest addr ton = 1, dest add npi = 1 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP[send_xxx]: Sending PDU: 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP PDU 0x16e29b0 dump: 2010-05-01 17:40:42 [15270] [6] DEBUG: type_name: submit_sm 2010-05-01 17:40:42 [15270] [6] DEBUG: command_id: 4 = 0x0004 2010-05-01 17:40:42 [15270] [6] DEBUG: command_status: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: sequence_number: 35 = 0x0023 2010-05-01 17:40:42 [15270] [6] DEBUG: service_type: NULL 2010-05-01 17:40:42 [15270] [6] DEBUG: source_addr_ton: 1 = 0x0001 2010-05-01 17:40:42 [15270] [6] DEBUG: source_addr_npi: 1 = 0x0001 2010-05-01 17:40:42 [15270] [6] DEBUG: source_addr: 1072 2010-05-01 17:40:42 [15270] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2010-05-01 17:40:42 [15270] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2010-05-01 17:40:42 [15270] [6] DEBUG: destination_addr: 569xxx 2010-05-01 17:40:42 [15270] [6] DEBUG: esm_class: 67 = 0x0043 2010-05-01 17:40:42 [15270] [6] DEBUG: protocol_id: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: priority_flag: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: schedule_delivery_time: NULL 2010-05-01 17:40:42 [15270] [6] DEBUG: validity_period: NULL 2010-05-01 17:40:42 [15270] [6] DEBUG: registered_delivery: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: replace_if_present_flag: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: data_coding: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: sm_default_msg_id: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: sm_length: 39 = 0x0027 2010-05-01 17:40:42 [15270] [6] DEBUG: short_message: 2010-05-01 17:40:42 [15270] [6] DEBUG:Octet string at 0x16dad80: 2010-05-01 17:40:42 [15270] [6] DEBUG: len: 39 2010-05-01 17:40:42 [15270] [6] DEBUG: size: 1024 2010-05-01 17:40:42 [15270] [6] DEBUG: immutable: 0 2010-05-01 17:40:42 [15270] [6] DEBUG: data: 06 05 04 0b 84 23 f0 3f 3f 3f 3f 3f 3f 6a 3f 45 .#.??j?E
Re: Can't change coding for wap-push
Thanks a lot, Alejandro's instructions works. =) Now we can send wappush with kannel, through a 7 bit enable SMSC. On Sun, May 2, 2010 at 6:40 AM, Alejandro Guerrieri alejandro.guerri...@gmail.com wrote: You're sending 67 (0x43) because you need to patch kannel to change the default esm_class. Here's how to do it: On gw/smsc/smsc_smpp.c, search for this line: pdu-u.submit_sm.esm_class = ESM_CLASS_SUBMIT_STORE_AND_FORWARD_MODE; (Should be around line 868) and change it to look like this: pdu-u.submit_sm.esm_class = ESM_CLASS_SUBMIT_DEFAULT_SMSC_MODE; Recompile, reinstall, and that will get you 0x40 instead of 0x43. Regarding the data_coding, first of all, the only presence of an udh field forces kannel to use 8 BIT. Try adding this parameter to your send-sms url: alt-dcs=1 and re-post the pdu dump. You should have at least 0xF0 with this setting. Hope it helps, Alex 2010/5/2 Nikos Balkanas nbalka...@gmail.com Hi, 1) You cannot configure esm_class in kannel. It is hard-coded. 2) You don't want to use 7bit encoding for wap-push. It is binary sms, therefore it has to be 8bit encoding. Your text is 8bit, therefore just skip the coding variable. 3) The reason you are getting it as SMS is that you use wrong udh header. Google for the correct for wappush. 4) Make sure that your coding is correct wbxml. BR, Nikos - Original Message - *From:* Alejandro Woywood awoyw...@gmail.com *To:* users@kannel.org *Sent:* Sunday, May 02, 2010 3:17 AM *Subject:* Can't change coding for wap-push Hi, please help! We have been trying to set up Kannel to work with an SMPP for sending wap-push. We could send sms, but when trying to send wap-push it is received as a sms in the phone. The operator told us to use 7 bit encoding and these settings: esm_class: 64 (0x0040) Data_coding: 245 (0xf5), (or 0x05, or 0x0f) Charset: ISO 8859-1 How can we force those settings in kannel? We tried adding “esm_class=40” to the config, but then kannel doesn’t start... This is our current config: group = smsc smsc = smpp smsc-id = xxx host = port = 3000 transceiver-mode = false receive-port = 3000 smsc-username = xxx smsc-password = system-type = smpp interface-version = 34 source-addr-ton = 1 source-addr-npi = 1 source-addr-autodetect = no dest-addr-ton = 1 dest-addr-npi = 1 bind-addr-ton = 1 bind-addr-npi = 1 alt-charset = ISO-8859-1 This is the wap-push we’re trying to send: http://localhost:13013/cgi-bin/sendsms?user=xxxpass=xxxfrom=1072to=+xxxudh=%06%05%04%0B%84%23%F0text=%1B%06%01%AE%02%05%6A%00%45%C6% 0C%03%67%6F%6F%67%6C%65%2E%6D%6F%62%69%00%01%03%67%6F%74%6F%00%01%01coding=0 This is the bearerbox log 2010-05-01 17:40:42 [15270] [19] DEBUG: boxc_receiver: sms received 2010-05-01 17:40:42 [15270] [19] DEBUG: send_msg: sending msg to box: 127.0.0.1 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP[send_xxx]: Manually forced source addr ton = 1, source add npi = 1 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP[send_xxx]: Manually forced dest addr ton = 1, dest add npi = 1 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP[send_xxx]: Sending PDU: 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP PDU 0x16e29b0 dump: 2010-05-01 17:40:42 [15270] [6] DEBUG: type_name: submit_sm 2010-05-01 17:40:42 [15270] [6] DEBUG: command_id: 4 = 0x0004 2010-05-01 17:40:42 [15270] [6] DEBUG: command_status: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: sequence_number: 35 = 0x0023 2010-05-01 17:40:42 [15270] [6] DEBUG: service_type: NULL 2010-05-01 17:40:42 [15270] [6] DEBUG: source_addr_ton: 1 = 0x0001 2010-05-01 17:40:42 [15270] [6] DEBUG: source_addr_npi: 1 = 0x0001 2010-05-01 17:40:42 [15270] [6] DEBUG: source_addr: 1072 2010-05-01 17:40:42 [15270] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2010-05-01 17:40:42 [15270] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2010-05-01 17:40:42 [15270] [6] DEBUG: destination_addr: 569xxx 2010-05-01 17:40:42 [15270] [6] DEBUG: esm_class: 67 = 0x0043 2010-05-01 17:40:42 [15270] [6] DEBUG: protocol_id: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: priority_flag: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: schedule_delivery_time: NULL 2010-05-01 17:40:42 [15270] [6] DEBUG: validity_period: NULL 2010-05-01 17:40:42 [15270] [6] DEBUG: registered_delivery: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: replace_if_present_flag: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: data_coding: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: sm_default_msg_id: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: sm_length: 39 = 0x0027 2010-05-01 17:40:42 [15270] [6] DEBUG: short_message: 2010-05-01 17:40:42 [15270] [6] DEBUG:Octet string at 0x16dad80: 2010-05-01 17:40:42 [15270] [6] DEBUG: len: 39 2010-05-01 17
Re: Can't change coding for wap-push
I'm glad it worked :) Regards, Alex On Sun, May 2, 2010 at 11:41 PM, Gonzalo Vergara grverg...@gmail.comwrote: Thanks a lot, Alejandro's instructions works. =) Now we can send wappush with kannel, through a 7 bit enable SMSC. On Sun, May 2, 2010 at 6:40 AM, Alejandro Guerrieri alejandro.guerri...@gmail.com wrote: You're sending 67 (0x43) because you need to patch kannel to change the default esm_class. Here's how to do it: On gw/smsc/smsc_smpp.c, search for this line: pdu-u.submit_sm.esm_class = ESM_CLASS_SUBMIT_STORE_AND_FORWARD_MODE; (Should be around line 868) and change it to look like this: pdu-u.submit_sm.esm_class = ESM_CLASS_SUBMIT_DEFAULT_SMSC_MODE; Recompile, reinstall, and that will get you 0x40 instead of 0x43. Regarding the data_coding, first of all, the only presence of an udh field forces kannel to use 8 BIT. Try adding this parameter to your send-sms url: alt-dcs=1 and re-post the pdu dump. You should have at least 0xF0 with this setting. Hope it helps, Alex 2010/5/2 Nikos Balkanas nbalka...@gmail.com Hi, 1) You cannot configure esm_class in kannel. It is hard-coded. 2) You don't want to use 7bit encoding for wap-push. It is binary sms, therefore it has to be 8bit encoding. Your text is 8bit, therefore just skip the coding variable. 3) The reason you are getting it as SMS is that you use wrong udh header. Google for the correct for wappush. 4) Make sure that your coding is correct wbxml. BR, Nikos - Original Message - *From:* Alejandro Woywood awoyw...@gmail.com *To:* users@kannel.org *Sent:* Sunday, May 02, 2010 3:17 AM *Subject:* Can't change coding for wap-push Hi, please help! We have been trying to set up Kannel to work with an SMPP for sending wap-push. We could send sms, but when trying to send wap-push it is received as a sms in the phone. The operator told us to use 7 bit encoding and these settings: esm_class: 64 (0x0040) Data_coding: 245 (0xf5), (or 0x05, or 0x0f) Charset: ISO 8859-1 How can we force those settings in kannel? We tried adding “esm_class=40” to the config, but then kannel doesn’t start... This is our current config: group = smsc smsc = smpp smsc-id = xxx host = port = 3000 transceiver-mode = false receive-port = 3000 smsc-username = xxx smsc-password = system-type = smpp interface-version = 34 source-addr-ton = 1 source-addr-npi = 1 source-addr-autodetect = no dest-addr-ton = 1 dest-addr-npi = 1 bind-addr-ton = 1 bind-addr-npi = 1 alt-charset = ISO-8859-1 This is the wap-push we’re trying to send: http://localhost:13013/cgi-bin/sendsms?user=xxxpass=xxxfrom=1072to=+xxxudh=%06%05%04%0B%84%23%F0text=%1B%06%01%AE%02%05%6A%00%45%C6% 0C%03%67%6F%6F%67%6C%65%2E%6D%6F%62%69%00%01%03%67%6F%74%6F%00%01%01coding=0 This is the bearerbox log 2010-05-01 17:40:42 [15270] [19] DEBUG: boxc_receiver: sms received 2010-05-01 17:40:42 [15270] [19] DEBUG: send_msg: sending msg to box: 127.0.0.1 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP[send_xxx]: Manually forced source addr ton = 1, source add npi = 1 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP[send_xxx]: Manually forced dest addr ton = 1, dest add npi = 1 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP[send_xxx]: Sending PDU: 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP PDU 0x16e29b0 dump: 2010-05-01 17:40:42 [15270] [6] DEBUG: type_name: submit_sm 2010-05-01 17:40:42 [15270] [6] DEBUG: command_id: 4 = 0x0004 2010-05-01 17:40:42 [15270] [6] DEBUG: command_status: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: sequence_number: 35 = 0x0023 2010-05-01 17:40:42 [15270] [6] DEBUG: service_type: NULL 2010-05-01 17:40:42 [15270] [6] DEBUG: source_addr_ton: 1 = 0x0001 2010-05-01 17:40:42 [15270] [6] DEBUG: source_addr_npi: 1 = 0x0001 2010-05-01 17:40:42 [15270] [6] DEBUG: source_addr: 1072 2010-05-01 17:40:42 [15270] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2010-05-01 17:40:42 [15270] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2010-05-01 17:40:42 [15270] [6] DEBUG: destination_addr: 569xxx 2010-05-01 17:40:42 [15270] [6] DEBUG: esm_class: 67 = 0x0043 2010-05-01 17:40:42 [15270] [6] DEBUG: protocol_id: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: priority_flag: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: schedule_delivery_time: NULL 2010-05-01 17:40:42 [15270] [6] DEBUG: validity_period: NULL 2010-05-01 17:40:42 [15270] [6] DEBUG: registered_delivery: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: replace_if_present_flag: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: data_coding: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: sm_default_msg_id: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: sm_length: 39 = 0x0027 2010-05-01 17:40:42 [15270] [6] DEBUG: short_message: 2010-05-01 17:40
Can't change coding for wap-push
Hi, please help! We have been trying to set up Kannel to work with an SMPP for sending wap-push. We could send sms, but when trying to send wap-push it is received as a sms in the phone. The operator told us to use 7 bit encoding and these settings: esm_class: 64 (0x0040) Data_coding: 245 (0xf5), (or 0x05, or 0x0f) Charset: ISO 8859-1 How can we force those settings in kannel? We tried adding esm_class=40 to the config, but then kannel doesn't start... This is our current config: group = smsc smsc = smpp smsc-id = xxx host = port = 3000 transceiver-mode = false receive-port = 3000 smsc-username = xxx smsc-password = system-type = smpp interface-version = 34 source-addr-ton = 1 source-addr-npi = 1 source-addr-autodetect = no dest-addr-ton = 1 dest-addr-npi = 1 bind-addr-ton = 1 bind-addr-npi = 1 alt-charset = ISO-8859-1 This is the wap-push we're trying to send: http://localhost:13013/cgi-bin/sendsms?user=xxxpass=xxx from=1072to=+xxxudh=%06%05%04%0B%84%23%F0text=%1B%06%01%AE%02%05%6A%00%4 5%C6% 0C%03%67%6F%6F%67%6C%65%2E%6D%6F%62%69%00%01%03%67%6F%74%6F%00%01%01coding= 0 This is the bearerbox log 2010-05-01 17:40:42 [15270] [19] DEBUG: boxc_receiver: sms received 2010-05-01 17:40:42 [15270] [19] DEBUG: send_msg: sending msg to box: 127.0.0.1 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP[send_xxx]: Manually forced source addr ton = 1, source add npi = 1 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP[send_xxx]: Manually forced dest addr ton = 1, dest add npi = 1 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP[send_xxx]: Sending PDU: 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP PDU 0x16e29b0 dump: 2010-05-01 17:40:42 [15270] [6] DEBUG: type_name: submit_sm 2010-05-01 17:40:42 [15270] [6] DEBUG: command_id: 4 = 0x0004 2010-05-01 17:40:42 [15270] [6] DEBUG: command_status: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: sequence_number: 35 = 0x0023 2010-05-01 17:40:42 [15270] [6] DEBUG: service_type: NULL 2010-05-01 17:40:42 [15270] [6] DEBUG: source_addr_ton: 1 = 0x0001 2010-05-01 17:40:42 [15270] [6] DEBUG: source_addr_npi: 1 = 0x0001 2010-05-01 17:40:42 [15270] [6] DEBUG: source_addr: 1072 2010-05-01 17:40:42 [15270] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2010-05-01 17:40:42 [15270] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2010-05-01 17:40:42 [15270] [6] DEBUG: destination_addr: 569xxx 2010-05-01 17:40:42 [15270] [6] DEBUG: esm_class: 67 = 0x0043 2010-05-01 17:40:42 [15270] [6] DEBUG: protocol_id: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: priority_flag: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: schedule_delivery_time: NULL 2010-05-01 17:40:42 [15270] [6] DEBUG: validity_period: NULL 2010-05-01 17:40:42 [15270] [6] DEBUG: registered_delivery: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: replace_if_present_flag: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: data_coding: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: sm_default_msg_id: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: sm_length: 39 = 0x0027 2010-05-01 17:40:42 [15270] [6] DEBUG: short_message: 2010-05-01 17:40:42 [15270] [6] DEBUG:Octet string at 0x16dad80: 2010-05-01 17:40:42 [15270] [6] DEBUG: len: 39 2010-05-01 17:40:42 [15270] [6] DEBUG: size: 1024 2010-05-01 17:40:42 [15270] [6] DEBUG: immutable: 0 2010-05-01 17:40:42 [15270] [6] DEBUG: data: 06 05 04 0b 84 23 f0 3f 3f 3f 3f 3f 3f 6a 3f 45 .#.??j?E 2010-05-01 17:40:42 [15270] [6] DEBUG: data: 3f 3f 67 6f 6f 67 6c 65 2e 6d 6f 62 69 3f 3f 3f ??google.mobi??? 2010-05-01 17:40:42 [15270] [6] DEBUG: data: 67 6f 74 6f 3f 3f 3f goto??? 2010-05-01 17:40:42 [15270] [6] DEBUG:Octet string dump ends. 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP PDU dump ends. 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP[send_xxx]: Got PDU: 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP PDU 0x16e29b0 dump: 2010-05-01 17:40:42 [15270] [6] DEBUG: type_name: submit_sm_resp 2010-05-01 17:40:42 [15270] [6] DEBUG: command_id: 2147483652 = 0x8004 2010-05-01 17:40:42 [15270] [6] DEBUG: command_status: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: sequence_number: 35 = 0x0023 2010-05-01 17:40:42 [15270] [6] DEBUG: message_id: 6f83f702 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP PDU dump ends. I'm a bit desperated so I tried downloading nowSMS. It has an option Encode long messages with 7-bit packed encoding. When activating it, the wap-push is received as a wap-push in the phone! So, it's not the fault of the operator, it has to be a configuration problem in kannel, which we haven't been able to solve. Please help! Thanks in advance, Alejandro Woywood. _ From: Gonzalo Vergara [mailto:grverg...@gmail.com] Sent: Jueves, 29 de Abril de 2010 17:18 To: us...@vm1.kannel.org
Re: Can't change coding for wap-push
Hi, 1) You cannot configure esm_class in kannel. It is hard-coded. 2) You don't want to use 7bit encoding for wap-push. It is binary sms, therefore it has to be 8bit encoding. Your text is 8bit, therefore just skip the coding variable. 3) The reason you are getting it as SMS is that you use wrong udh header. Google for the correct for wappush. 4) Make sure that your coding is correct wbxml. BR, Nikos - Original Message - From: Alejandro Woywood To: users@kannel.org Sent: Sunday, May 02, 2010 3:17 AM Subject: Can't change coding for wap-push Hi, please help! We have been trying to set up Kannel to work with an SMPP for sending wap-push. We could send sms, but when trying to send wap-push it is received as a sms in the phone. The operator told us to use 7 bit encoding and these settings: esm_class: 64 (0x0040) Data_coding: 245 (0xf5), (or 0x05, or 0x0f) Charset: ISO 8859-1 How can we force those settings in kannel? We tried adding “esm_class=40” to the config, but then kannel doesn’t start... This is our current config: group = smsc smsc = smpp smsc-id = xxx host = port = 3000 transceiver-mode = false receive-port = 3000 smsc-username = xxx smsc-password = system-type = smpp interface-version = 34 source-addr-ton = 1 source-addr-npi = 1 source-addr-autodetect = no dest-addr-ton = 1 dest-addr-npi = 1 bind-addr-ton = 1 bind-addr-npi = 1 alt-charset = ISO-8859-1 This is the wap-push we’re trying to send: http://localhost:13013/cgi-bin/sendsms?user=xxxpass=xxx from=1072to=+xxxudh=%06%05%04%0B%84%23%F0text=%1B%06%01%AE%02%05%6A%00%45%C6% 0C%03%67%6F%6F%67%6C%65%2E%6D%6F%62%69%00%01%03%67%6F%74%6F%00%01%01coding=0 This is the bearerbox log 2010-05-01 17:40:42 [15270] [19] DEBUG: boxc_receiver: sms received 2010-05-01 17:40:42 [15270] [19] DEBUG: send_msg: sending msg to box: 127.0.0.1 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP[send_xxx]: Manually forced source addr ton = 1, source add npi = 1 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP[send_xxx]: Manually forced dest addr ton = 1, dest add npi = 1 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP[send_xxx]: Sending PDU: 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP PDU 0x16e29b0 dump: 2010-05-01 17:40:42 [15270] [6] DEBUG: type_name: submit_sm 2010-05-01 17:40:42 [15270] [6] DEBUG: command_id: 4 = 0x0004 2010-05-01 17:40:42 [15270] [6] DEBUG: command_status: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: sequence_number: 35 = 0x0023 2010-05-01 17:40:42 [15270] [6] DEBUG: service_type: NULL 2010-05-01 17:40:42 [15270] [6] DEBUG: source_addr_ton: 1 = 0x0001 2010-05-01 17:40:42 [15270] [6] DEBUG: source_addr_npi: 1 = 0x0001 2010-05-01 17:40:42 [15270] [6] DEBUG: source_addr: 1072 2010-05-01 17:40:42 [15270] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2010-05-01 17:40:42 [15270] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2010-05-01 17:40:42 [15270] [6] DEBUG: destination_addr: 569xxx 2010-05-01 17:40:42 [15270] [6] DEBUG: esm_class: 67 = 0x0043 2010-05-01 17:40:42 [15270] [6] DEBUG: protocol_id: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: priority_flag: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: schedule_delivery_time: NULL 2010-05-01 17:40:42 [15270] [6] DEBUG: validity_period: NULL 2010-05-01 17:40:42 [15270] [6] DEBUG: registered_delivery: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: replace_if_present_flag: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: data_coding: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: sm_default_msg_id: 0 = 0x 2010-05-01 17:40:42 [15270] [6] DEBUG: sm_length: 39 = 0x0027 2010-05-01 17:40:42 [15270] [6] DEBUG: short_message: 2010-05-01 17:40:42 [15270] [6] DEBUG:Octet string at 0x16dad80: 2010-05-01 17:40:42 [15270] [6] DEBUG: len: 39 2010-05-01 17:40:42 [15270] [6] DEBUG: size: 1024 2010-05-01 17:40:42 [15270] [6] DEBUG: immutable: 0 2010-05-01 17:40:42 [15270] [6] DEBUG: data: 06 05 04 0b 84 23 f0 3f 3f 3f 3f 3f 3f 6a 3f 45 .#.??j?E 2010-05-01 17:40:42 [15270] [6] DEBUG: data: 3f 3f 67 6f 6f 67 6c 65 2e 6d 6f 62 69 3f 3f 3f ??google.mobi??? 2010-05-01 17:40:42 [15270] [6] DEBUG: data: 67 6f 74 6f 3f 3f 3f goto??? 2010-05-01 17:40:42 [15270] [6] DEBUG:Octet string dump ends. 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP PDU dump ends. 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP[send_xxx]: Got PDU: 2010-05-01 17:40:42 [15270] [6] DEBUG: SMPP PDU 0x16e29b0 dump: 2010-05-01 17:40:42 [15270] [6] DEBUG: type_name: submit_sm_resp 2010-05-01 17:40:42 [15270] [6] DEBUG: command_id: 2147483652 = 0x8004 2010
Wap-push received as SMS
Hello there. I need help with a strange problem I configured kannel to work with a telco's SMSC SMPP, and I was able to send SMS successfully. But when I send wap-push, I only receive SMS (with garbage) in the phone. I tried doing it with manually: http://localhost:13013/cgi-bin/sendsms?user=foopass=barto=+XXXudh=%06%05%04%0B%84%23%F0text=%1B%06%01%AE%02%05%6A%00%45%C6%0C%03%67%6F%6F%67%6C%65%2E%6D%6F%62%69%00%01%03%67%6F%74%6F%00%01%01coding=0 and also with PPG: /usr/lib/kannel/test/test_ppg http://localhost:13031/wappush?username=foopassword=bar; si.xml pap.xml The documents from the telco says their SMSC only allows 7 bit coding. I also check the logs and see these errors: bearerbox.log.1:2010-04-23 20:40:55 [9555] [6] ERROR: Failed to convert string from UTF-8 to ASCII, errno was 84 bearerbox.log.1:2010-04-23 20:40:55 [9555] [6] ERROR: Failed to convert msgdata from charset UTF-8 to ASCII, will send as is.
Re: sqlbox and wap push
Wap push is sent as binary sms. Wouldn't hurt to try. Provide a select from the DB to verify that you have inserted the correct msgtext. The INSERT statement you have provided is not a log, therefore no verification that what you think was actually sent. Not really necessary to resend bb logs. - Original Message - From: Sam To: Nikos Balkanas ; Alejandro Guerrieri Cc: users@kannel.org Sent: Monday, January 25, 2010 12:45 AM Subject: Re: sqlbox and wap push Hi, Am sending a wap push. Without even specifying coding=2 charset=utf in the send-url, all WORK FINE. So i don think this is the problem. The problem is when i try to use SQLBOX for the same message. One thing that i noticed is that when i insert into the DB, the message data get truncated on 0x00 as you would also see in the log. I guess this is where the problem is and i will be grateful if you can help provide information on how to resolve this. Thank you. 2010/1/24 Nikos Balkanas n...@amdtelecom.net Hi, Well, I am sure you understand that no one enjoys long mails each day on weekends in their box. When sending binary SMS, you have to specify coding=2 charset=utf in your send-url. I assume your text is UTF. BR, Nikos - Original Message - From: Sam To: Nikos Balkanas ; Alejandro Guerrieri Cc: users@kannel.org Sent: Monday, January 25, 2010 12:20 AM Subject: Re: sqlbox and wap push Hi, Come on Nikos, I appreciate your effort to offer assistance but you really do not have to insult. Kind words are sufficient and professional ! Anyways, I have changed the field to binary as advised by Alex. Plus i am sure the issue if not from PHP. I am using direct copy of the URL into the browser (works fine) and also direct INSERT in to the DB. See the logs below. One thing that i noticed however is that when i insert into the DB, the message data get truncated on 0x00 as you would also see in the log. I guess this is where the problem is and i will be grateful if you can help provide information on how to resolve this. Thank you. --Sam ## SENDING OVER HTTP ### http://www.hostname.com:13290/cgi-bin/sendsms?user=kannelpass=rL4y90udh=%06%05%04%0B%84%23%F0text=%1B%06%01%AE%02%05%6A%00%45%C6%0C%03%77%77%77%2E%63%6F%79%6E%61%6D%65%2E%63%6F%6D%2F%69%6D%61%67%65%2E%6A%70%67%00%01%03%57%61%70%00%01%01dlr-mask=31from=coyNameto= 2010-01-24 22:47:49 [32012] [6] DEBUG: SMPP[nuSMSC]: Sending PDU: 2010-01-24 22:47:49 [32012] [6] DEBUG: SMPP PDU 0xb0513a80 dump: 2010-01-24 22:47:49 [32012] [6] DEBUG: type_name: submit_sm 2010-01-24 22:47:49 [32012] [6] DEBUG: command_id: 4 = 0x0004 2010-01-24 22:47:49 [32012] [6] DEBUG: command_status: 0 = 0x 2010-01-24 22:47:49 [32012] [6] DEBUG: sequence_number: 45807 = 0xb2ef 2010-01-24 22:47:49 [32012] [6] DEBUG: service_type: NULL 2010-01-24 22:47:49 [32012] [6] DEBUG: source_addr_ton: 5 = 0x0005 2010-01-24 22:47:49 [32012] [6] DEBUG: source_addr_npi: 0 = 0x 2010-01-24 22:47:49 [32012] [6] DEBUG: source_addr: coyName 2010-01-24 22:47:49 [32012] [6] DEBUG: dest_addr_ton: 2 = 0x0002 2010-01-24 22:47:49 [32012] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2010-01-24 22:47:49 [32012] [6] DEBUG: destination_addr: 2010-01-24 22:47:49 [32012] [6] DEBUG: esm_class: 67 = 0x0043 2010-01-24 22:47:49 [32012] [6] DEBUG: protocol_id: 0 = 0x 2010-01-24 22:47:49 [32012] [6] DEBUG: priority_flag: 0 = 0x 2010-01-24 22:47:49 [32012] [6] DEBUG: schedule_delivery_time: NULL 2010-01-24 22:47:49 [32012] [6] DEBUG: validity_period: NULL 2010-01-24 22:47:49 [32012] [6] DEBUG: registered_delivery: 1 = 0x0001 2010-01-24 22:47:49 [32012] [6] DEBUG: replace_if_present_flag: 0 = 0x 2010-01-24 22:47:49 [32012] [6] DEBUG: data_coding: 4 = 0x0004 2010-01-24 22:47:49 [32012] [6] DEBUG: sm_default_msg_id: 0 = 0x 2010-01-24 22:47:49 [32012] [6] DEBUG: sm_length: 53 = 0x0035 2010-01-24 22:47:49 [32012] [6] DEBUG: short_message: 2010-01-24 22:47:49 [32012] [6] DEBUG:Octet string at 0xb0513a20: 2010-01-24 22:47:49 [32012] [6] DEBUG: len: 53 2010-01-24 22:47:49 [32012] [6] DEBUG: size: 1024 2010-01-24 22:47:49 [32012] [6] DEBUG: immutable: 0 2010-01-24 22:47:49 [32012] [6] DEBUG: data: 06 05 04 0b 84 23 f0 1b 06 01 ae 02 05 6a 00 45 .#...j.E 2010-01-24 22:47:49 [32012] [6] DEBUG: data: c6 0c 03 77 77 77 2e 63 6f 79 6e 61 6d 65 2e 63 ...www.coyname.c 2010-01-24 22:47:49 [32012] [6] DEBUG: data: 6f 6d 2f 69 6d 61 67 65 2e
Re: sqlbox and wap push
From the DB. # `momt`, `sender`, `receiver`, `udhdata` , `msgdata`, 'MT', 'coyName', '0', 0x0605040b8423f0, 0x1b0601ae02056a, # 2010/1/25 Nikos Balkanas n...@amdtelecom.net Wap push is sent as binary sms. Wouldn't hurt to try. Provide a select from the DB to verify that you have inserted the correct msgtext. The INSERT statement you have provided is not a log, therefore no verification that what you think was actually sent. Not really necessary to resend bb logs. - Original Message - *From:* Sam nu.e...@gmail.com *To:* Nikos Balkanas n...@amdtelecom.net ; Alejandro Guerrierialejandro.guerri...@gmail.com *Cc:* users@kannel.org *Sent:* Monday, January 25, 2010 12:45 AM *Subject:* Re: sqlbox and wap push Hi, Am sending a wap push. Without even specifying coding=2 charset=utf in the send-url, all WORK FINE. So i don think this is the problem. The problem is when i try to use SQLBOX for the same message. One thing that i noticed is that when i insert into the DB, the message data get truncated on 0x00 as you would also see in the log. I guess this is where the problem is and i will be grateful if you can help provide information on how to resolve this. Thank you. 2010/1/24 Nikos Balkanas n...@amdtelecom.net Hi, Well, I am sure you understand that no one enjoys long mails each day on weekends in their box. When sending binary SMS, you have to specify coding=2 charset=utf in your send-url. I assume your text is UTF. BR, Nikos - Original Message - *From:* Sam nu.e...@gmail.com *To:* Nikos Balkanas nbalka...@gmail.com ; Alejandro Guerrierialejandro.guerri...@gmail.com *Cc:* users@kannel.org *Sent:* Monday, January 25, 2010 12:20 AM *Subject:* Re: sqlbox and wap push Hi, Come on Nikos, I appreciate your effort to offer assistance but you really do not have to insult. Kind words are sufficient and professional ! Anyways, I have changed the field to binary as advised by Alex. Plus i am sure the issue if not from PHP. I am using direct copy of the URL into the browser (works fine) and also direct INSERT in to the DB. See the logs below. One thing that i noticed however is that when i insert into the DB, the message data get truncated on 0x00 as you would also see in the log. I guess this is where the problem is and i will be grateful if you can help provide information on how to resolve this. Thank you. --Sam ## SENDING OVER HTTP ### http://www.hostname.com:13290/cgi-bin/sendsms?user=kannelpass=rL4y90udh=%06%05%04%0B%84%23%F0text=%1B%06%01%AE%02%05%6A%00%45%C6%0C%03%77%77%77%2E%63%6F%79%6E%61%6D%65%2E%63%6F%6D%2F%69%6D%61%67%65%2E%6A%70%67%00%01%03%57%61%70%00%01%01dlr-mask=31from=coyNameto= 2010-01-24 22:47:49 [32012] [6] DEBUG: SMPP[nuSMSC]: Sending PDU: 2010-01-24 22:47:49 [32012] [6] DEBUG: SMPP PDU 0xb0513a80 dump: 2010-01-24 22:47:49 [32012] [6] DEBUG: type_name: submit_sm 2010-01-24 22:47:49 [32012] [6] DEBUG: command_id: 4 = 0x0004 2010-01-24 22:47:49 [32012] [6] DEBUG: command_status: 0 = 0x 2010-01-24 22:47:49 [32012] [6] DEBUG: sequence_number: 45807 = 0xb2ef 2010-01-24 22:47:49 [32012] [6] DEBUG: service_type: NULL 2010-01-24 22:47:49 [32012] [6] DEBUG: source_addr_ton: 5 = 0x0005 2010-01-24 22:47:49 [32012] [6] DEBUG: source_addr_npi: 0 = 0x 2010-01-24 22:47:49 [32012] [6] DEBUG: source_addr: coyName 2010-01-24 22:47:49 [32012] [6] DEBUG: dest_addr_ton: 2 = 0x0002 2010-01-24 22:47:49 [32012] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2010-01-24 22:47:49 [32012] [6] DEBUG: destination_addr: 2010-01-24 22:47:49 [32012] [6] DEBUG: esm_class: 67 = 0x0043 2010-01-24 22:47:49 [32012] [6] DEBUG: protocol_id: 0 = 0x 2010-01-24 22:47:49 [32012] [6] DEBUG: priority_flag: 0 = 0x 2010-01-24 22:47:49 [32012] [6] DEBUG: schedule_delivery_time: NULL 2010-01-24 22:47:49 [32012] [6] DEBUG: validity_period: NULL 2010-01-24 22:47:49 [32012] [6] DEBUG: registered_delivery: 1 = 0x0001 2010-01-24 22:47:49 [32012] [6] DEBUG: replace_if_present_flag: 0 = 0x 2010-01-24 22:47:49 [32012] [6] DEBUG: data_coding: 4 = 0x0004 2010-01-24 22:47:49 [32012] [6] DEBUG: sm_default_msg_id: 0 = 0x 2010-01-24 22:47:49 [32012] [6] DEBUG: sm_length: 53 = 0x0035 2010-01-24 22:47:49 [32012] [6] DEBUG: short_message: 2010-01-24 22:47:49 [32012] [6] DEBUG:Octet string at 0xb0513a20: 2010-01-24 22:47:49 [32012] [6] DEBUG: len: 53 2010-01-24 22:47:49 [32012] [6] DEBUG: size: 1024 2010-01-24 22:47:49 [32012] [6] DEBUG: immutable: 0 2010-01-24 22:47:49 [32012] [6] DEBUG: data: 06 05 04 0b 84 23 f0 1b 06 01 ae 02 05 6a 00 45 .#...j.E 2010-01-24 22:47:49 [32012] [6] DEBUG: data: c6 0c 03 77 77 77 2e 63 6f 79
Re: sqlbox and wap push
Can someone please unsubscribe me from this list please? I have sent emails to users@ with unsubscribe in the subject and body... Can someone help me get removed. Thanks On 1/24/2010 4:22 PM, Sam wrote: From the DB. # `momt`, `sender`, `receiver`, `udhdata` , `msgdata`, 'MT', 'coyName', '0', 0x0605040b8423f0, 0x1b0601ae02056a, # 2010/1/25 Nikos Balkanas n...@amdtelecom.net mailto:n...@amdtelecom.net Wap push is sent as binary sms. Wouldn't hurt to try. Provide a select from the DB to verify that you have inserted the correct msgtext. The INSERT statement you have provided is not a log, therefore no verification that what you think was actually sent. Not really necessary to resend bb logs. - Original Message - *From:* Sam mailto:nu.e...@gmail.com *To:* Nikos Balkanas mailto:n...@amdtelecom.net ; Alejandro Guerrieri mailto:alejandro.guerri...@gmail.com *Cc:* users@kannel.org mailto:users@kannel.org *Sent:* Monday, January 25, 2010 12:45 AM *Subject:* Re: sqlbox and wap push Hi, Am sending a wap push. Without even specifying coding=2 charset=utf in the send-url, all WORK FINE. So i don think this is the problem. The problem is when i try to use SQLBOX for the same message. One thing that i noticed is that when i insert into the DB, the message data get truncated on 0x00 as you would also see in the log. I guess this is where the problem is and i will be grateful if you can help provide information on how to resolve this. Thank you. 2010/1/24 Nikos Balkanas n...@amdtelecom.net mailto:n...@amdtelecom.net Hi, Well, I am sure you understand that no one enjoys long mails each day on weekends in their box. When sending binary SMS, you have to specify coding=2 charset=utf in your send-url. I assume your text is UTF. BR, Nikos - Original Message - *From:* Sam mailto:nu.e...@gmail.com *To:* Nikos Balkanas mailto:nbalka...@gmail.com ; Alejandro Guerrieri mailto:alejandro.guerri...@gmail.com *Cc:* users@kannel.org mailto:users@kannel.org *Sent:* Monday, January 25, 2010 12:20 AM *Subject:* Re: sqlbox and wap push Hi, Come on Nikos, I appreciate your effort to offer assistance but you really do not have to insult. Kind words are sufficient and professional ! Anyways, I have changed the field to binary as advised by Alex. Plus i am sure the issue if not from PHP. I am using direct copy of the URL into the browser (works fine) and also direct INSERT in to the DB. See the logs below. One thing that i noticed however is that when i insert into the DB, the message data get truncated on 0x00 as you would also see in the log. I guess this is where the problem is and i will be grateful if you can help provide information on how to resolve this. Thank you. --Sam ## SENDING OVER HTTP ### http://www.hostname.com:13290/cgi-bin/sendsms?user=kannelpass=rL4y90udh=%06%05%04%0B%84%23%F0text=%1B%06%01%AE%02%05%6A%00%45%C6%0C%03%77%77%77%2E%63%6F%79%6E%61%6D%65%2E%63%6F%6D%2F%69%6D%61%67%65%2E%6A%70%67%00%01%03%57%61%70%00%01%01dlr-mask=31from=coyNameto= http://www.hostname.com:13290/cgi-bin/sendsms?user=kannelpass=rL4y90udh=%06%05%04%0B%84%23%F0text=%1B%06%01%AE%02%05%6A%00%45%C6%0C%03%77%77%77%2E%63%6F%79%6E%61%6D%65%2E%63%6F%6D%2F%69%6D%61%67%65%2E%6A%70%67%00%01%03%57%61%70%00%01%01dlr-mask=31from=coyNameto= 2010-01-24 22:47:49 [32012] [6] DEBUG: SMPP[nuSMSC]: Sending PDU: 2010-01-24 22:47:49 [32012] [6] DEBUG: SMPP PDU 0xb0513a80 dump: 2010-01-24 22:47:49 [32012] [6] DEBUG: type_name: submit_sm 2010-01-24 22:47:49 [32012] [6] DEBUG: command_id: 4 = 0x0004 2010-01-24 22:47:49 [32012] [6] DEBUG: command_status: 0 = 0x 2010-01-24 22:47:49 [32012] [6] DEBUG: sequence_number: 45807 = 0xb2ef 2010-01-24 22:47:49 [32012] [6] DEBUG: service_type: NULL 2010-01-24 22:47:49 [32012] [6] DEBUG: source_addr_ton: 5 = 0x0005 2010-01-24 22:47:49 [32012
Re: sqlbox and wap push
Only you can unsubscribe yourself. either from the site, www.kannel.org, or get the correct list from the monthly kannel reminders. Nikos - Original Message - From: Hans Guth To: Sam Cc: Nikos Balkanas ; Alejandro Guerrieri ; us...@vm1.kannel.org Sent: Monday, January 25, 2010 1:25 AM Subject: Re: sqlbox and wap push Can someone please unsubscribe me from this list please?Β I have sent emails to users@ with unsubscribe in the subject and body...Β Can someone help me get removed. Thanks
Re: sqlbox and wap push
Hi, Well, as you can see this is not an SQLbox or kannel issue. Assuming that you already converted your msgdata to binary, it seems to be an insert problem from your php. My initial response was not to insult, but to jolt your thinking. You spent time doing the hard thing (convert msgdata to 0x01) instead of looking the most straightforward, i.e. verify the data in the database. BR, Nikos - Original Message - From: Sam To: Nikos Balkanas ; Alejandro Guerrieri Cc: users@kannel.org Sent: Monday, January 25, 2010 1:22 AM Subject: Re: sqlbox and wap push From the DB. # `momt`, `sender`, `receiver`, `udhdata` , `msgdata`, 'MT', 'coyName', '0', 0x0605040b8423f0, 0x1b0601ae02056a, # 2010/1/25 Nikos Balkanas n...@amdtelecom.net Wap push is sent as binary sms. Wouldn't hurt to try. Provide a select from the DB to verify that you have inserted the correct msgtext. The INSERT statement you have provided is not a log, therefore no verification that what you think was actually sent. Not really necessary to resend bb logs. - Original Message - From: Sam To: Nikos Balkanas ; Alejandro Guerrieri Cc: users@kannel.org Sent: Monday, January 25, 2010 12:45 AM Subject: Re: sqlbox and wap push Hi, Am sending a wap push. Without even specifying coding=2 charset=utf in the send-url, all WORK FINE. So i don think this is the problem. The problem is when i try to use SQLBOX for the same message. One thing that i noticed is that when i insert into the DB, the message data get truncated on 0x00 as you would also see in the log. I guess this is where the problem is and i will be grateful if you can help provide information on how to resolve this. Thank you. 2010/1/24 Nikos Balkanas n...@amdtelecom.net Hi, Well, I am sure you understand that no one enjoys long mails each day on weekends in their box. When sending binary SMS, you have to specify coding=2 charset=utf in your send-url. I assume your text is UTF. BR, Nikos - Original Message - From: Sam To: Nikos Balkanas ; Alejandro Guerrieri Cc: users@kannel.org Sent: Monday, January 25, 2010 12:20 AM Subject: Re: sqlbox and wap push Hi, Come on Nikos, I appreciate your effort to offer assistance but you really do not have to insult. Kind words are sufficient and professional ! Anyways, I have changed the field to binary as advised by Alex. Plus i am sure the issue if not from PHP. I am using direct copy of the URL into the browser (works fine) and also direct INSERT in to the DB. See the logs below. One thing that i noticed however is that when i insert into the DB, the message data get truncated on 0x00 as you would also see in the log. I guess this is where the problem is and i will be grateful if you can help provide information on how to resolve this. Thank you. --Sam ## SENDING OVER HTTP ### http://www.hostname.com:13290/cgi-bin/sendsms?user=kannelpass=rL4y90udh=%06%05%04%0B%84%23%F0text=%1B%06%01%AE%02%05%6A%00%45%C6%0C%03%77%77%77%2E%63%6F%79%6E%61%6D%65%2E%63%6F%6D%2F%69%6D%61%67%65%2E%6A%70%67%00%01%03%57%61%70%00%01%01dlr-mask=31from=coyNameto= 2010-01-24 22:47:49 [32012] [6] DEBUG: SMPP[nuSMSC]: Sending PDU: 2010-01-24 22:47:49 [32012] [6] DEBUG: SMPP PDU 0xb0513a80 dump: 2010-01-24 22:47:49 [32012] [6] DEBUG: type_name: submit_sm 2010-01-24 22:47:49 [32012] [6] DEBUG: command_id: 4 = 0x0004 2010-01-24 22:47:49 [32012] [6] DEBUG: command_status: 0 = 0x 2010-01-24 22:47:49 [32012] [6] DEBUG: sequence_number: 45807 = 0xb2ef 2010-01-24 22:47:49 [32012] [6] DEBUG: service_type: NULL 2010-01-24 22:47:49 [32012] [6] DEBUG: source_addr_ton: 5 = 0x0005 2010-01-24 22:47:49 [32012] [6] DEBUG: source_addr_npi: 0 = 0x 2010-01-24 22:47:49 [32012] [6] DEBUG: source_addr: coyName 2010-01-24 22:47:49 [32012] [6] DEBUG: dest_addr_ton: 2 = 0x0002 2010-01-24 22:47:49 [32012] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2010-01-24 22:47:49 [32012] [6] DEBUG: destination_addr: 2010-01-24 22:47:49 [32012] [6] DEBUG: esm_class: 67 = 0x0043 2010-01-24 22:47:49 [32012] [6] DEBUG: protocol_id: 0 = 0x 2010-01-24 22:47:49 [32012] [6] DEBUG: priority_flag: 0 = 0x 2010-01-24 22:47:49 [32012] [6] DEBUG: schedule_delivery_time: NULL 2010-01-24 22:47:49 [32012] [6] DEBUG: validity_period: NULL 2010-01
Re: sqlbox and wap push
Thank you for the info.. Interesting enough am not using php at this point. I am running the insert directly on MySQL and yet the msgdata is truncated on 0x00 --Sam 2010/1/25 Nikos Balkanas n...@amdtelecom.net Hi, Well, as you can see this is not an SQLbox or kannel issue. Assuming that you already converted your msgdata to binary, it seems to be an insert problem from your php. My initial response was not to insult, but to jolt your thinking. You spent time doing the hard thing (convert msgdata to 0x01) instead of looking the most straightforward, i.e. verify the data in the database. BR, Nikos - Original Message - *From:* Sam nu.e...@gmail.com *To:* Nikos Balkanas n...@amdtelecom.net ; Alejandro Guerrierialejandro.guerri...@gmail.com *Cc:* users@kannel.org *Sent:* Monday, January 25, 2010 1:22 AM *Subject:* Re: sqlbox and wap push From the DB. # `momt`, `sender`, `receiver`, `udhdata` , `msgdata`, 'MT', 'coyName', '0', 0x0605040b8423f0, 0x1b0601ae02056a, # 2010/1/25 Nikos Balkanas n...@amdtelecom.net Wap push is sent as binary sms. Wouldn't hurt to try. Provide a select from the DB to verify that you have inserted the correct msgtext. The INSERT statement you have provided is not a log, therefore no verification that what you think was actually sent. Not really necessary to resend bb logs. - Original Message - *From:* Sam nu.e...@gmail.com *To:* Nikos Balkanas n...@amdtelecom.net ; Alejandro Guerrierialejandro.guerri...@gmail.com *Cc:* users@kannel.org *Sent:* Monday, January 25, 2010 12:45 AM *Subject:* Re: sqlbox and wap push Hi, Am sending a wap push. Without even specifying coding=2 charset=utf in the send-url, all WORK FINE. So i don think this is the problem. The problem is when i try to use SQLBOX for the same message. One thing that i noticed is that when i insert into the DB, the message data get truncated on 0x00 as you would also see in the log. I guess this is where the problem is and i will be grateful if you can help provide information on how to resolve this. Thank you. 2010/1/24 Nikos Balkanas n...@amdtelecom.net Hi, Well, I am sure you understand that no one enjoys long mails each day on weekends in their box. When sending binary SMS, you have to specify coding=2 charset=utf in your send-url. I assume your text is UTF. BR, Nikos - Original Message - *From:* Sam nu.e...@gmail.com *To:* Nikos Balkanas nbalka...@gmail.com ; Alejandro Guerrierialejandro.guerri...@gmail.com *Cc:* users@kannel.org *Sent:* Monday, January 25, 2010 12:20 AM *Subject:* Re: sqlbox and wap push Hi, Come on Nikos, I appreciate your effort to offer assistance but you really do not have to insult. Kind words are sufficient and professional ! Anyways, I have changed the field to binary as advised by Alex. Plus i am sure the issue if not from PHP. I am using direct copy of the URL into the browser (works fine) and also direct INSERT in to the DB. See the logs below. One thing that i noticed however is that when i insert into the DB, the message data get truncated on 0x00 as you would also see in the log. I guess this is where the problem is and i will be grateful if you can help provide information on how to resolve this. Thank you. --Sam ## SENDING OVER HTTP ### http://www.hostname.com:13290/cgi-bin/sendsms?user=kannelpass=rL4y90udh=%06%05%04%0B%84%23%F0text=%1B%06%01%AE%02%05%6A%00%45%C6%0C%03%77%77%77%2E%63%6F%79%6E%61%6D%65%2E%63%6F%6D%2F%69%6D%61%67%65%2E%6A%70%67%00%01%03%57%61%70%00%01%01dlr-mask=31from=coyNameto= 2010-01-24 22:47:49 [32012] [6] DEBUG: SMPP[nuSMSC]: Sending PDU: 2010-01-24 22:47:49 [32012] [6] DEBUG: SMPP PDU 0xb0513a80 dump: 2010-01-24 22:47:49 [32012] [6] DEBUG: type_name: submit_sm 2010-01-24 22:47:49 [32012] [6] DEBUG: command_id: 4 = 0x0004 2010-01-24 22:47:49 [32012] [6] DEBUG: command_status: 0 = 0x 2010-01-24 22:47:49 [32012] [6] DEBUG: sequence_number: 45807 = 0xb2ef 2010-01-24 22:47:49 [32012] [6] DEBUG: service_type: NULL 2010-01-24 22:47:49 [32012] [6] DEBUG: source_addr_ton: 5 = 0x0005 2010-01-24 22:47:49 [32012] [6] DEBUG: source_addr_npi: 0 = 0x 2010-01-24 22:47:49 [32012] [6] DEBUG: source_addr: coyName 2010-01-24 22:47:49 [32012] [6] DEBUG: dest_addr_ton: 2 = 0x0002 2010-01-24 22:47:49 [32012] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2010-01-24 22:47:49 [32012] [6] DEBUG: destination_addr: 2010-01-24 22:47:49 [32012] [6] DEBUG: esm_class: 67 = 0x0043 2010-01-24 22:47:49 [32012] [6] DEBUG: protocol_id: 0 = 0x 2010-01-24 22:47:49 [32012] [6] DEBUG: priority_flag: 0 = 0x 2010-01-24 22:47:49 [32012] [6] DEBUG: schedule_delivery_time: NULL 2010-01-24 22:47:49 [32012] [6] DEBUG
Re: sqlbox and wap push
] [6] DEBUG:Octet string at 0x92523e8:
2010-01-09 01:33:08 [32012] [6] DEBUG: len: 214
2010-01-09 01:33:08 [32012] [6] DEBUG: size: 1024
2010-01-09 01:33:08 [32012] [6] DEBUG: immutable: 0
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 06 05 04 0b 84 23 f0
25 31 42 25 30 36 25 30 31 .#.%1B%06%01
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 41 45 25 30 32 25
30 35 25 36 41 25 30 30 25 %AE%02%05%6A%00%
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 34 35 25 43 36 25 30
43 25 30 33 25 36 38 25 37 45%C6%0C%03%68%7
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 34 25 37 34 25 37 30
25 33 41 25 32 46 25 32 46 4%74%70%3A%2F%2F
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 36 45 25 36 31 25
36 44 25 36 35 25 36 45 25 %6E%61%6D%65%6E%
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 36 31 25 36 44 25 36
35 25 37 33 25 32 45 25 36 61%6D%65%73%2E%6
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 33 25 36 46 25 36 44
25 32 46 25 37 36 25 36 46 3%6F%6D%2F%76%6F
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 36 39 25 36 33 25
36 35 25 32 46 25 36 35 25 %69%63%65%2F%65%
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 36 33 25 36 46 25 37
33 25 37 33 25 36 35 25 32 63%6F%73%73%65%2
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 45 25 36 41 25 37 30
25 36 37 25 30 30 25 30 31 E%6A%70%67%00%01
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 30 33 25 35 34 25
36 38 25 36 35 25 32 30 25 %03%54%68%65%20%
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 36 39 25 36 44 25 36
31 25 36 37 25 36 35 25 32 69%6D%61%67%65%2
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 30 25 36 38 25 36 35
25 37 32 25 36 35 25 30 30 0%68%65%72%65%00
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 30 31 25 30 31
%01%01
2010-01-09 01:33:08 [32012] [6] DEBUG:Octet string dump ends.
2010-01-09 01:33:08 [32012] [6] DEBUG: SMPP PDU dump ends.
##
On Mon, Jan 4, 2010 at 11:21 AM, Alejandro Guerrieri
aguerri...@kannel.org wrote:
Have you checked the logs? You need to put the _binary_ data on the
udh field, not the %XX stuff, btw.
Compare the logs when sending from sendsms and sqlbox, you'll probably
find differences.
Regards,
Alex
--
Alejandro Guerrieri
aguerri...@kannel.org
On 03/01/2010, at 23:23, Sam wrote:
Hi,
Yes, I have used the full url.
$fields[udh] into `udhdata`
$fields[text] into `msgdata`
and other relevant fields.
Yet message does not come to the phone or phone does not understand
it. However, if i past the URL directly on the sendsms http interface,
the
message get delivered right.
Am worried if i was supposed to insert $fields[text] into `msgdata`
directly.
On Sun, Jan 3, 2010 at 11:15 PM, Alejandro Guerrieri
alejandro.guerri...@gmail.com wrote:
Wap push uses udh data, try using the full url my code generates.
Regards,
Alex
On Sun, Jan 3, 2010 at 10:45 PM, Sam nu.e...@gmail.com wrote:
Hi,
I have tried to use Alex php code here http://www.blogalex.com/wp-
content/uploads/2008/09/send_wap_push.php.txt
by inserting the content of $fields[text] into `msgdata` field of
the SQLbox table but this is not working.
?php
$fields = array (
'from' = '9912345678',
'to' = '9987654321',
'smsc' = 'mysmsc',
'link' = 'www.my-funny-link.com/myfile.mid',
'title' = 'Hi, look at this'
);
$kannel = array (
'host' = 'localhost',
'port' = 13013,
'user' = 'foo',
'pass' = 'bar'
);
$result = sendwappush ( $fields, $kannel );
print SENTbr$resultbr;
/*
sendwappush function.
Copyleft 2004 by Alejandro Guerrieri
This code is open source and GPL licensed
*/
function send_wap_push ( $fields, $kannel ) {
$fields[udh] = '%06%05%04%0B%84%23%F0';
$fields[text] = '%1B%06%01%AE%02%05%6A%00%45%C6%0C%03'.
hex_encode($fields['link'], '%').
'%00%01%03'.
hex_encode($fields['title'], '%').
'%00%01%01';
unset ( $fields['title'], $fields['link'] );
while(list($k,$v) = each($fields)) {
if ( $v != ) {
$string .= $k=$v;
}
}
$request = 'http://'.$kannel['host'].':'.$kannel[port].
'/cgi-bin/sendsms'.
'?user='.$kannel['user'].
'pass='.$kannel['pass'].
$string;
$result = @file( $request );
return 'ok';
}
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;
}
?
2010/1/3 Nikos Balkanas nbalka...@gmail.com
Hi,
With SQLbox you'll have to push it like sms. For a php example for
simple pushes please search archives for Alejandro Guerrieri's code.
BR,
Nikos
- Original Message -
*From:* Sam nu.e
Re: sqlbox and wap push
[32012] [6] DEBUG: data: 06 05 04 0b 84 23 f0
25 31 42 25 30 36 25 30 31 .#.%1B%06%01
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 41 45 25 30 32 25
30 35 25 36 41 25 30 30 25 %AE%02%05%6A%00%
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 34 35 25 43 36 25 30
43 25 30 33 25 36 38 25 37 45%C6%0C%03%68%7
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 34 25 37 34 25 37 30
25 33 41 25 32 46 25 32 46 4%74%70%3A%2F%2F
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 36 45 25 36 31 25
36 44 25 36 35 25 36 45 25 %6E%61%6D%65%6E%
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 36 31 25 36 44 25 36
35 25 37 33 25 32 45 25 36 61%6D%65%73%2E%6
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 33 25 36 46 25 36 44
25 32 46 25 37 36 25 36 46 3%6F%6D%2F%76%6F
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 36 39 25 36 33 25
36 35 25 32 46 25 36 35 25 %69%63%65%2F%65%
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 36 33 25 36 46 25 37
33 25 37 33 25 36 35 25 32 63%6F%73%73%65%2
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 45 25 36 41 25 37 30
25 36 37 25 30 30 25 30 31 E%6A%70%67%00%01
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 30 33 25 35 34 25
36 38 25 36 35 25 32 30 25 %03%54%68%65%20%
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 36 39 25 36 44 25 36
31 25 36 37 25 36 35 25 32 69%6D%61%67%65%2
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 30 25 36 38 25 36 35
25 37 32 25 36 35 25 30 30 0%68%65%72%65%00
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 30 31 25 30 31
%01%01
2010-01-09 01:33:08 [32012] [6] DEBUG:Octet string dump ends.
2010-01-09 01:33:08 [32012] [6] DEBUG: SMPP PDU dump ends.
##
On Mon, Jan 4, 2010 at 11:21 AM, Alejandro Guerrieri
aguerri...@kannel.org wrote:
Have you checked the logs? You need to put the _binary_ data on the
udh field, not the %XX stuff, btw.
Compare the logs when sending from sendsms and sqlbox, you'll probably
find differences.
Regards,
Alex
--
Alejandro Guerrieri
aguerri...@kannel.org
On 03/01/2010, at 23:23, Sam wrote:
Hi,
Yes, I have used the full url.
$fields[udh] into `udhdata`
$fields[text] into `msgdata`
and other relevant fields.
Yet message does not come to the phone or phone does not understand it.
However, if i past the URL directly on the sendsms http interface, the
message get delivered right.
Am worried if i was supposed to insert $fields[text] into `msgdata`
directly.
On Sun, Jan 3, 2010 at 11:15 PM, Alejandro Guerrieri
alejandro.guerri...@gmail.com wrote:
Wap push uses udh data, try using the full url my code generates.
Regards,
Alex
On Sun, Jan 3, 2010 at 10:45 PM, Sam nu.e...@gmail.com wrote:
Hi,
I have tried to use Alex php code here http://www.blogalex.com/wp-
content/uploads/2008/09/send_wap_push.php.txt
by inserting the content of $fields[text] into `msgdata` field of
the SQLbox table but this is not working.
?php
$fields = array (
'from' = '9912345678',
'to' = '9987654321',
'smsc' = 'mysmsc',
'link' = 'www.my-funny-link.com/myfile.mid',
'title' = 'Hi, look at this'
);
$kannel = array (
'host' = 'localhost',
'port' = 13013,
'user' = 'foo',
'pass' = 'bar'
);
$result = sendwappush ( $fields, $kannel );
print SENTbr$resultbr;
/*
sendwappush function.
Copyleft 2004 by Alejandro Guerrieri
This code is open source and GPL licensed
*/
function send_wap_push ( $fields, $kannel ) {
$fields[udh] = '%06%05%04%0B%84%23%F0';
$fields[text] = '%1B%06%01%AE%02%05%6A%00%45%C6%0C%03'.
hex_encode($fields['link'], '%').
'%00%01%03'.
hex_encode($fields['title'], '%').
'%00%01%01';
unset ( $fields['title'], $fields['link'] );
while(list($k,$v) = each($fields)) {
if ( $v != ) {
$string .= $k=$v;
}
}
$request = 'http://'.$kannel['host'].':'.$kannel[port].
'/cgi-bin/sendsms'.
'?user='.$kannel['user'].
'pass='.$kannel['pass'].
$string;
$result = @file( $request );
return 'ok';
}
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;
}
?
2010/1/3 Nikos Balkanas nbalka...@gmail.com
Hi,
With SQLbox you'll have to push it like sms. For a php example for
simple pushes please search archives for Alejandro Guerrieri's code.
BR,
Nikos
- Original Message -
*From:* Sam nu.e...@gmail.com
*To:* users@kannel.org
*Sent:* Sunday, January 03, 2010 11:23 PM
*Subject:* Re: sqlbox and wap push
Hi,
Please how do i make SQLBOX to handle a simple Service Load Wap push
like the following to a mobile?
?xml version
Re: sqlbox and wap push
%6E%
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 36 31 25 36 44 25 36 35
25 37 33 25 32 45 25 36 61%6D%65%73%2E%6
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 33 25 36 46 25 36 44 25
32 46 25 37 36 25 36 46 3%6F%6D%2F%76%6F
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 36 39 25 36 33 25 36
35 25 32 46 25 36 35 25 %69%63%65%2F%65%
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 36 33 25 36 46 25 37 33
25 37 33 25 36 35 25 32 63%6F%73%73%65%2
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 45 25 36 41 25 37 30 25
36 37 25 30 30 25 30 31 E%6A%70%67%00%01
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 30 33 25 35 34 25 36
38 25 36 35 25 32 30 25 %03%54%68%65%20%
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 36 39 25 36 44 25 36 31
25 36 37 25 36 35 25 32 69%6D%61%67%65%2
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 30 25 36 38 25 36 35 25
37 32 25 36 35 25 30 30 0%68%65%72%65%00
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 30 31 25 30 31
%01%01
2010-01-09 01:33:08 [32012] [6] DEBUG:Octet string dump ends.
2010-01-09 01:33:08 [32012] [6] DEBUG: SMPP PDU dump ends.
##
On Mon, Jan 4, 2010 at 11:21 AM, Alejandro Guerrieri
aguerri...@kannel.org wrote:
Have you checked the logs? You need to put the _binary_ data on the udh
field, not the %XX stuff, btw.
Compare the logs when sending from sendsms and sqlbox, you'll probably
find differences.
Regards,
Alex
--
Alejandro Guerrieri
aguerri...@kannel.org
On 03/01/2010, at 23:23, Sam wrote:
Hi,
Yes, I have used the full url.
$fields[udh] into `udhdata`
$fields[text] into `msgdata`
and other relevant fields.
Yet message does not come to the phone or phone does not understand it.
However, if i past the URL directly on the sendsms http interface, the
message get delivered right.
Am worried if i was supposed to insert $fields[text] into `msgdata`
directly.
On Sun, Jan 3, 2010 at 11:15 PM, Alejandro Guerrieri
alejandro.guerri...@gmail.com wrote:
Wap push uses udh data, try using the full url my code generates.
Regards,
Alex
On Sun, Jan 3, 2010 at 10:45 PM, Sam nu.e...@gmail.com wrote:
Hi,
I have tried to use Alex php code here http://www.blogalex.com/wp-
content/uploads/2008/09/send_wap_push.php.txt
by inserting the content of $fields[text] into `msgdata` field of the
SQLbox table but this is not working.
?php
$fields = array (
'from' = '9912345678',
'to' = '9987654321',
'smsc' = 'mysmsc',
'link' = 'www.my-funny-link.com/myfile.mid',
'title' = 'Hi, look at this'
);
$kannel = array (
'host' = 'localhost',
'port' = 13013,
'user' = 'foo',
'pass' = 'bar'
);
$result = sendwappush ( $fields, $kannel );
print SENTbr$resultbr;
/*
sendwappush function.
Copyleft 2004 by Alejandro Guerrieri
This code is open source and GPL licensed
*/
function send_wap_push ( $fields, $kannel ) {
$fields[udh] = '%06%05%04%0B%84%23%F0';
$fields[text] = '%1B%06%01%AE%02%05%6A%00%45%C6%0C%03'.
hex_encode($fields['link'], '%').
'%00%01%03'.
hex_encode($fields['title'], '%').
'%00%01%01';
unset ( $fields['title'], $fields['link'] );
while(list($k,$v) = each($fields)) {
if ( $v != ) {
$string .= $k=$v;
}
}
$request = 'http://'.$kannel['host'].':'.$kannel[port].
'/cgi-bin/sendsms'.
'?user='.$kannel['user'].
'pass='.$kannel['pass'].
$string;
$result = @file( $request );
return 'ok';
}
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;
}
?
2010/1/3 Nikos Balkanas nbalka...@gmail.com
Hi,
With SQLbox you'll have to push it like sms. For a php example for
simple pushes please search archives for Alejandro Guerrieri's code.
BR,
Nikos
- Original Message -
*From:* Sam nu.e...@gmail.com
*To:* users@kannel.org
*Sent:* Sunday, January 03, 2010 11:23 PM
*Subject:* Re: sqlbox and wap push
Hi,
Please how do i make SQLBOX to handle a simple Service Load Wap push
like the following to a mobile?
?xml version=1.0?
!DOCTYPE sl PUBLIC -//WAPFORUM//DTD SL 1.0//EN
www.wapforum.org/DTD/sl.dtd
sl href=http://domain.com/images2.jpg/
N.B. Giving that the the appropriate UDH has been defined.
TIA
--Sam.
2009/12/9 Nikos Balkanas nbalka...@gmail.com
I don't have an example. Use Alex's link. And don't spam. 1 email
is plenth.
BR,
Nikos
- Original Message -
*From:* Sam nu.e...@gmail.com
*To:* Nikos Balkanas n...@amdtelecom.net
*Cc:* users@kannel.org
*Sent:* Wednesday, December 09, 2009 11:10 AM
*Subject:* Re: sqlbox
Re: sqlbox and wap push
[32012] [6] DEBUG: data: 34 25 37 34 25 37 30 25
33 41 25 32 46 25 32 46 4%74%70%3A%2F%2F
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 36 45 25 36 31 25 36
44 25 36 35 25 36 45 25 %6E%61%6D%65%6E%
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 36 31 25 36 44 25 36 35
25 37 33 25 32 45 25 36 61%6D%65%73%2E%6
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 33 25 36 46 25 36 44 25
32 46 25 37 36 25 36 46 3%6F%6D%2F%76%6F
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 36 39 25 36 33 25 36
35 25 32 46 25 36 35 25 %69%63%65%2F%65%
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 36 33 25 36 46 25 37 33
25 37 33 25 36 35 25 32 63%6F%73%73%65%2
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 45 25 36 41 25 37 30 25
36 37 25 30 30 25 30 31 E%6A%70%67%00%01
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 30 33 25 35 34 25 36
38 25 36 35 25 32 30 25 %03%54%68%65%20%
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 36 39 25 36 44 25 36 31
25 36 37 25 36 35 25 32 69%6D%61%67%65%2
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 30 25 36 38 25 36 35 25
37 32 25 36 35 25 30 30 0%68%65%72%65%00
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 30 31 25 30 31
%01%01
2010-01-09 01:33:08 [32012] [6] DEBUG:Octet string dump ends.
2010-01-09 01:33:08 [32012] [6] DEBUG: SMPP PDU dump ends.
##
On Mon, Jan 4, 2010 at 11:21 AM, Alejandro Guerrieri
aguerri...@kannel.org wrote:
Have you checked the logs? You need to put the _binary_ data on the
udh field, not the %XX stuff, btw.
Compare the logs when sending from sendsms and sqlbox, you'll probably
find differences.
Regards,
Alex
--
Alejandro Guerrieri
aguerri...@kannel.org
On 03/01/2010, at 23:23, Sam wrote:
Hi,
Yes, I have used the full url.
$fields[udh] into `udhdata`
$fields[text] into `msgdata`
and other relevant fields.
Yet message does not come to the phone or phone does not understand it.
However, if i past the URL directly on the sendsms http interface, the
message get delivered right.
Am worried if i was supposed to insert $fields[text] into `msgdata`
directly.
On Sun, Jan 3, 2010 at 11:15 PM, Alejandro Guerrieri
alejandro.guerri...@gmail.com wrote:
Wap push uses udh data, try using the full url my code generates.
Regards,
Alex
On Sun, Jan 3, 2010 at 10:45 PM, Sam nu.e...@gmail.com wrote:
Hi,
I have tried to use Alex php code here http://www.blogalex.com/wp-
content/uploads/2008/09/send_wap_push.php.txt
by inserting the content of $fields[text] into `msgdata` field of the
SQLbox table but this is not working.
?php
$fields = array (
'from' = '9912345678',
'to' = '9987654321',
'smsc' = 'mysmsc',
'link' = 'www.my-funny-link.com/myfile.mid',
'title' = 'Hi, look at this'
);
$kannel = array (
'host' = 'localhost',
'port' = 13013,
'user' = 'foo',
'pass' = 'bar'
);
$result = sendwappush ( $fields, $kannel );
print SENTbr$resultbr;
/*
sendwappush function.
Copyleft 2004 by Alejandro Guerrieri
This code is open source and GPL licensed
*/
function send_wap_push ( $fields, $kannel ) {
$fields[udh] = '%06%05%04%0B%84%23%F0';
$fields[text] = '%1B%06%01%AE%02%05%6A%00%45%C6%0C%03'.
hex_encode($fields['link'], '%').
'%00%01%03'.
hex_encode($fields['title'], '%').
'%00%01%01';
unset ( $fields['title'], $fields['link'] );
while(list($k,$v) = each($fields)) {
if ( $v != ) {
$string .= $k=$v;
}
}
$request = 'http://'.$kannel['host'].':'.$kannel[port].
'/cgi-bin/sendsms'.
'?user='.$kannel['user'].
'pass='.$kannel['pass'].
$string;
$result = @file( $request );
return 'ok';
}
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;
}
?
2010/1/3 Nikos Balkanas nbalka...@gmail.com
Hi,
With SQLbox you'll have to push it like sms. For a php example for
simple pushes please search archives for Alejandro Guerrieri's code.
BR,
Nikos
- Original Message -
*From:* Sam nu.e...@gmail.com
*To:* users@kannel.org
*Sent:* Sunday, January 03, 2010 11:23 PM
*Subject:* Re: sqlbox and wap push
Hi,
Please how do i make SQLBOX to handle a simple Service Load Wap push
like the following to a mobile?
?xml version=1.0?
!DOCTYPE sl PUBLIC -//WAPFORUM//DTD SL 1.0//EN
www.wapforum.org/DTD/sl.dtd
sl href=http://domain.com/images2.jpg/
N.B. Giving that the the appropriate UDH has been defined.
TIA
--Sam.
2009/12/9 Nikos Balkanas nbalka...@gmail.com
I don't have an example. Use Alex's link. And don't spam. 1 email
is plenth.
BR
Re: sqlbox and wap push
[32012] [6] DEBUG: source_addr_npi: 0 = 0x 2010-01-09 01:33:08 [32012] [6] DEBUG: source_addr: sender 2010-01-09 01:33:08 [32012] [6] DEBUG: dest_addr_ton: 2 = 0x0002 2010-01-09 01:33:08 [32012] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2010-01-09 01:33:08 [32012] [6] DEBUG: destination_addr: 0 2010-01-09 01:33:08 [32012] [6] DEBUG: esm_class: 67 = 0x0043 2010-01-09 01:33:08 [32012] [6] DEBUG: protocol_id: 0 = 0x 2010-01-09 01:33:08 [32012] [6] DEBUG: priority_flag: 0 = 0x 2010-01-09 01:33:08 [32012] [6] DEBUG: schedule_delivery_time: NULL 2010-01-09 01:33:08 [32012] [6] DEBUG: validity_period: NULL 2010-01-09 01:33:08 [32012] [6] DEBUG: registered_delivery: 1 = 0x0001 2010-01-09 01:33:08 [32012] [6] DEBUG: replace_if_present_flag: 0 = 0x 2010-01-09 01:33:08 [32012] [6] DEBUG: data_coding: 4 = 0x0004 2010-01-09 01:33:08 [32012] [6] DEBUG: sm_default_msg_id: 0 = 0x 2010-01-09 01:33:08 [32012] [6] DEBUG: sm_length: 214 = 0x00d6 2010-01-09 01:33:08 [32012] [6] DEBUG: short_message: 2010-01-09 01:33:08 [32012] [6] DEBUG:Octet string at 0x92523e8: 2010-01-09 01:33:08 [32012] [6] DEBUG: len: 214 2010-01-09 01:33:08 [32012] [6] DEBUG: size: 1024 2010-01-09 01:33:08 [32012] [6] DEBUG: immutable: 0 2010-01-09 01:33:08 [32012] [6] DEBUG: data: 06 05 04 0b 84 23 f0 25 31 42 25 30 36 25 30 31 .#.%1B%06%01 2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 41 45 25 30 32 25 30 35 25 36 41 25 30 30 25 %AE%02%05%6A%00% 2010-01-09 01:33:08 [32012] [6] DEBUG: data: 34 35 25 43 36 25 30 43 25 30 33 25 36 38 25 37 45%C6%0C%03%68%7 2010-01-09 01:33:08 [32012] [6] DEBUG: data: 34 25 37 34 25 37 30 25 33 41 25 32 46 25 32 46 4%74%70%3A%2F%2F 2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 36 45 25 36 31 25 36 44 25 36 35 25 36 45 25 %6E%61%6D%65%6E% 2010-01-09 01:33:08 [32012] [6] DEBUG: data: 36 31 25 36 44 25 36 35 25 37 33 25 32 45 25 36 61%6D%65%73%2E%6 2010-01-09 01:33:08 [32012] [6] DEBUG: data: 33 25 36 46 25 36 44 25 32 46 25 37 36 25 36 46 3%6F%6D%2F%76%6F 2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 36 39 25 36 33 25 36 35 25 32 46 25 36 35 25 %69%63%65%2F%65% 2010-01-09 01:33:08 [32012] [6] DEBUG: data: 36 33 25 36 46 25 37 33 25 37 33 25 36 35 25 32 63%6F%73%73%65%2 2010-01-09 01:33:08 [32012] [6] DEBUG: data: 45 25 36 41 25 37 30 25 36 37 25 30 30 25 30 31 E%6A%70%67%00%01 2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 30 33 25 35 34 25 36 38 25 36 35 25 32 30 25 %03%54%68%65%20% 2010-01-09 01:33:08 [32012] [6] DEBUG: data: 36 39 25 36 44 25 36 31 25 36 37 25 36 35 25 32 69%6D%61%67%65%2 2010-01-09 01:33:08 [32012] [6] DEBUG: data: 30 25 36 38 25 36 35 25 37 32 25 36 35 25 30 30 0%68%65%72%65%00 2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 30 31 25 30 31 %01%01 2010-01-09 01:33:08 [32012] [6] DEBUG:Octet string dump ends. 2010-01-09 01:33:08 [32012] [6] DEBUG: SMPP PDU dump ends. ## On Mon, Jan 4, 2010 at 11:21 AM, Alejandro Guerrieri aguerri...@kannel.org wrote: Have you checked the logs? You need to put the _binary_ data on the udh field, not the %XX stuff, btw. Compare the logs when sending from sendsms and sqlbox, you'll probably find differences. Regards, Alex -- Alejandro Guerrieri aguerri...@kannel.org On 03/01/2010, at 23:23, Sam wrote: Hi, Yes, I have used the full url. $fields[udh] into `udhdata` $fields[text] into `msgdata` and other relevant fields. Yet message does not come to the phone or phone does not understand it. However, if i past the URL directly on the sendsms http interface, the message get delivered right. Am worried if i was supposed to insert $fields[text] into `msgdata` directly. On Sun, Jan 3, 2010 at 11:15 PM, Alejandro Guerrieri alejandro.guerri...@gmail.com wrote: Wap push uses udh data, try using the full url my code generates. Regards, Alex On Sun, Jan 3, 2010 at 10:45 PM, Sam nu.e...@gmail.com wrote: Hi, I have tried to use Alex php code here http://www.blogalex.com/wp- content/uploads/2008/09/send_wap_push.php.txt by inserting the content of $fields[text] into `msgdata` field of the SQLbox table but this is not working. ?php $fields = array ( 'from' = '9912345678', 'to' = '9987654321', 'smsc' = 'mysmsc', 'link' = 'www.my-funny-link.com/myfile.mid', 'title' = 'Hi, look at this' ); $kannel = array ( 'host' = 'localhost', 'port' = 13013, 'user' = 'foo', 'pass' = 'bar' ); $result = sendwappush ( $fields, $kannel ); print SENTbr$resultbr; /* sendwappush function. Copyleft 2004 by Alejandro Guerrieri This code is open source and GPL licensed
Re: sqlbox and wap push
: 0
2010-01-09 01:33:08 [32012] [6] DEBUG: esm_class: 67 = 0x0043
2010-01-09 01:33:08 [32012] [6] DEBUG: protocol_id: 0 = 0x
2010-01-09 01:33:08 [32012] [6] DEBUG: priority_flag: 0 = 0x
2010-01-09 01:33:08 [32012] [6] DEBUG: schedule_delivery_time: NULL
2010-01-09 01:33:08 [32012] [6] DEBUG: validity_period: NULL
2010-01-09 01:33:08 [32012] [6] DEBUG: registered_delivery: 1 = 0x0001
2010-01-09 01:33:08 [32012] [6] DEBUG: replace_if_present_flag: 0 =
0x
2010-01-09 01:33:08 [32012] [6] DEBUG: data_coding: 4 = 0x0004
2010-01-09 01:33:08 [32012] [6] DEBUG: sm_default_msg_id: 0 = 0x
2010-01-09 01:33:08 [32012] [6] DEBUG: sm_length: 214 = 0x00d6
2010-01-09 01:33:08 [32012] [6] DEBUG: short_message:
2010-01-09 01:33:08 [32012] [6] DEBUG:Octet string at 0x92523e8:
2010-01-09 01:33:08 [32012] [6] DEBUG: len: 214
2010-01-09 01:33:08 [32012] [6] DEBUG: size: 1024
2010-01-09 01:33:08 [32012] [6] DEBUG: immutable: 0
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 06 05 04 0b 84 23 f0 25 31
42 25 30 36 25 30 31 .#.%1B%06%01
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 41 45 25 30 32 25 30 35
25 36 41 25 30 30 25 %AE%02%05%6A%00%
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 34 35 25 43 36 25 30 43 25
30 33 25 36 38 25 37 45%C6%0C%03%68%7
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 34 25 37 34 25 37 30 25 33
41 25 32 46 25 32 46 4%74%70%3A%2F%2F
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 36 45 25 36 31 25 36 44
25 36 35 25 36 45 25 %6E%61%6D%65%6E%
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 36 31 25 36 44 25 36 35 25
37 33 25 32 45 25 36 61%6D%65%73%2E%6
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 33 25 36 46 25 36 44 25 32
46 25 37 36 25 36 46 3%6F%6D%2F%76%6F
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 36 39 25 36 33 25 36 35
25 32 46 25 36 35 25 %69%63%65%2F%65%
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 36 33 25 36 46 25 37 33 25
37 33 25 36 35 25 32 63%6F%73%73%65%2
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 45 25 36 41 25 37 30 25 36
37 25 30 30 25 30 31 E%6A%70%67%00%01
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 30 33 25 35 34 25 36 38
25 36 35 25 32 30 25 %03%54%68%65%20%
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 36 39 25 36 44 25 36 31 25
36 37 25 36 35 25 32 69%6D%61%67%65%2
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 30 25 36 38 25 36 35 25 37
32 25 36 35 25 30 30 0%68%65%72%65%00
2010-01-09 01:33:08 [32012] [6] DEBUG: data: 25 30 31 25 30 31
%01%01
2010-01-09 01:33:08 [32012] [6] DEBUG:Octet string dump ends.
2010-01-09 01:33:08 [32012] [6] DEBUG: SMPP PDU dump ends.
##
On Mon, Jan 4, 2010 at 11:21 AM, Alejandro Guerrieri
aguerri...@kannel.orgwrote:
Have you checked the logs? You need to put the _binary_ data on the udh
field, not the %XX stuff, btw.
Compare the logs when sending from sendsms and sqlbox, you'll probably find
differences.
Regards,
Alex
--
Alejandro Guerrieri
aguerri...@kannel.org
On 03/01/2010, at 23:23, Sam wrote:
Hi,
Yes, I have used the full url.
$fields[udh] into `udhdata`
$fields[text] into `msgdata`
and other relevant fields.
Yet message does not come to the phone or phone does not understand it.
However, if i past the URL directly on the sendsms http interface, the
message get delivered right.
Am worried if i was supposed to insert $fields[text] into `msgdata`
directly.
On Sun, Jan 3, 2010 at 11:15 PM, Alejandro Guerrieri
alejandro.guerri...@gmail.com wrote:
Wap push uses udh data, try using the full url my code generates.
Regards,
Alex
On Sun, Jan 3, 2010 at 10:45 PM, Sam nu.e...@gmail.com wrote:
Hi,
I have tried to use Alex php code here http://www.blogalex.com/wp-
content/uploads/2008/09/send_wap_push.php.txt
by inserting the content of $fields[text] into `msgdata` field of the
SQLbox table but this is not working.
?php
$fields = array (
'from' = '9912345678',
'to' = '9987654321',
'smsc' = 'mysmsc',
'link' = 'www.my-funny-link.com/myfile.mid',
'title' = 'Hi, look at this'
);
$kannel = array (
'host' = 'localhost',
'port' = 13013,
'user' = 'foo',
'pass' = 'bar'
);
$result = sendwappush ( $fields, $kannel );
print SENTbr$resultbr;
/*
sendwappush function.
Copyleft 2004 by Alejandro Guerrieri
This code is open source and GPL licensed
*/
function send_wap_push ( $fields, $kannel ) {
$fields[udh] = '%06%05%04%0B%84%23%F0';
$fields[text] = '%1B%06%01%AE%02%05%6A%00%45%C6%0C%03'.
hex_encode($fields['link'], '%').
'%00%01%03'.
hex_encode($fields['title'], '%').
'%00%01%01';
unset ( $fields['title'], $fields['link'] );
while(list($k,$v) = each($fields)) {
if ( $v
Re: sqlbox and wap push
Hi, Please how do i make SQLBOX to handle a simple Service Load Wap push like the following to a mobile? ?xml version=1.0? !DOCTYPE sl PUBLIC -//WAPFORUM//DTD SL 1.0//EN www.wapforum.org/DTD/sl.dtd sl href=http://domain.com/images2.jpg/ N.B. Giving that the the appropriate UDH has been defined. TIA --Sam. 2009/12/9 Nikos Balkanas nbalka...@gmail.com I don't have an example. Use Alex's link. And don't spam. 1 email is plenth. BR, Nikos - Original Message - *From:* Sam nu.e...@gmail.com *To:* Nikos Balkanas n...@amdtelecom.net *Cc:* users@kannel.org *Sent:* Wednesday, December 09, 2009 11:10 AM *Subject:* Re: sqlbox and wap push The goal is to make it work with sqlbox. Thus i would need to convert to wbxml. This is where i need your example. 2009/12/9 Nikos Balkanas n...@amdtelecom.net Hi, Use Alex's link. Otherwise it is too lengthy to describe the protocol. If you are interested the spec is: WAP-249-PPGService-20010713-a An example would be meaningless. It is different for each message. Wapbox will do the same thing for you, but it doesn't work with SQLbox. BR, Nikos - Original Message - *From:* Sam nu.e...@gmail.com *To:* Nikos Balkanas nbalka...@gmail.com *Cc:* users@kannel.org *Sent:* Wednesday, December 09, 2009 10:39 AM *Subject:* Re: sqlbox and wap push Thanks Nikos, I understand the UDH stuff, however how do i convert to wbxml? Please could you do me an example? Also, would this code ( http://www.blogalex.com/wp-content/uploads/2008/09/send_wap_push.php.txt) help in anyway? Thanks in advance. --Sam 2009/12/9 Nikos Balkanas nbalka...@gmail.com Yes. You will have to do some work, though. 1) Use the appropriate udh for wap-push: udh=%06%05%04%0B%84%23%F0 in your sendsms url (url-encoded) 2) You have to convert your text first to wbxml and then urlencode it as well in your URL. BR, Nikos - Original Message - *From:* Sam nu.e...@gmail.com *To:* users@kannel.org *Sent:* Wednesday, December 09, 2009 9:43 AM *Subject:* sqlbox and wap push Hi, Please can i use sqlbox for wap push? --Sam
Re: sqlbox and wap push
Hi, With SQLbox you'll have to push it like sms. For a php example for simple pushes please search archives for Alejandro Guerrieri's code. BR, Nikos - Original Message - From: Sam To: users@kannel.org Sent: Sunday, January 03, 2010 11:23 PM Subject: Re: sqlbox and wap push Hi, Please how do i make SQLBOX to handle a simple Service Load Wap push like the following to a mobile? ?xml version=1.0? !DOCTYPE sl PUBLIC -//WAPFORUM//DTD SL 1.0//EN www.wapforum.org/DTD/sl.dtd sl href=http://domain.com/images2.jpg/ N.B. Giving that the the appropriate UDH has been defined. TIA --Sam. 2009/12/9 Nikos Balkanas nbalka...@gmail.com I don't have an example. Use Alex's link. And don't spam. 1 email is plenth. BR, Nikos - Original Message - From: Sam To: Nikos Balkanas Cc: users@kannel.org Sent: Wednesday, December 09, 2009 11:10 AM Subject: Re: sqlbox and wap push The goal is to make it work with sqlbox. Thus i would need to convert to wbxml. This is where i need your example. 2009/12/9 Nikos Balkanas n...@amdtelecom.net Hi, Use Alex's link. Otherwise it is too lengthy to describe the protocol. If you are interested the spec is: WAP-249-PPGService-20010713-a An example would be meaningless. It is different for each message. Wapbox will do the same thing for you, but it doesn't work with SQLbox. BR, Nikos - Original Message - From: Sam To: Nikos Balkanas Cc: users@kannel.org Sent: Wednesday, December 09, 2009 10:39 AM Subject: Re: sqlbox and wap push Thanks Nikos, I understand the UDH stuff, however how do i convert to wbxml? Please could you do me an example? Also, would this code (http://www.blogalex.com/wp-content/uploads/2008/09/send_wap_push.php.txt) help in anyway? Thanks in advance. --Sam 2009/12/9 Nikos Balkanas nbalka...@gmail.com Yes. You will have to do some work, though. 1) Use the appropriate udh for wap-push: udh=%06%05%04%0B%84%23%F0 in your sendsms url (url-encoded) 2) You have to convert your text first to wbxml and then urlencode it as well in your URL. BR, Nikos - Original Message - From: Sam To: users@kannel.org Sent: Wednesday, December 09, 2009 9:43 AM Subject: sqlbox and wap push Hi, Please can i use sqlbox for wap push? --Sam
Re: sqlbox and wap push
Hi,
I have tried to use Alex php code here http://www.blogalex.com/wp-
content/uploads/2008/09/send_wap_push.php.txt
by inserting the content of $fields[text] into `msgdata` field of the SQLbox
table but this is not working.
?php
$fields = array (
'from' = '9912345678',
'to' = '9987654321',
'smsc' = 'mysmsc',
'link' = 'www.my-funny-link.com/myfile.mid',
'title' = 'Hi, look at this'
);
$kannel = array (
'host' = 'localhost',
'port' = 13013,
'user' = 'foo',
'pass' = 'bar'
);
$result = sendwappush ( $fields, $kannel );
print SENTbr$resultbr;
/*
sendwappush function.
Copyleft 2004 by Alejandro Guerrieri
This code is open source and GPL licensed
*/
function send_wap_push ( $fields, $kannel ) {
$fields[udh] = '%06%05%04%0B%84%23%F0';
$fields[text] = '%1B%06%01%AE%02%05%6A%00%45%C6%0C%03'.
hex_encode($fields['link'], '%').
'%00%01%03'.
hex_encode($fields['title'], '%').
'%00%01%01';
unset ( $fields['title'], $fields['link'] );
while(list($k,$v) = each($fields)) {
if ( $v != ) {
$string .= $k=$v;
}
}
$request = 'http://'.$kannel['host'].':'.$kannel[port].
'/cgi-bin/sendsms'.
'?user='.$kannel['user'].
'pass='.$kannel['pass'].
$string;
$result = @file( $request );
return 'ok';
}
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;
}
?
2010/1/3 Nikos Balkanas nbalka...@gmail.com
Hi,
With SQLbox you'll have to push it like sms. For a php example for simple
pushes please search archives for Alejandro Guerrieri's code.
BR,
Nikos
- Original Message -
*From:* Sam nu.e...@gmail.com
*To:* users@kannel.org
*Sent:* Sunday, January 03, 2010 11:23 PM
*Subject:* Re: sqlbox and wap push
Hi,
Please how do i make SQLBOX to handle a simple Service Load Wap push like
the following to a mobile?
?xml version=1.0?
!DOCTYPE sl PUBLIC -//WAPFORUM//DTD SL 1.0//EN
www.wapforum.org/DTD/sl.dtd
sl href=http://domain.com/images2.jpg/
N.B. Giving that the the appropriate UDH has been defined.
TIA
--Sam.
2009/12/9 Nikos Balkanas nbalka...@gmail.com
I don't have an example. Use Alex's link. And don't spam. 1 email is
plenth.
BR,
Nikos
- Original Message -
*From:* Sam nu.e...@gmail.com
*To:* Nikos Balkanas n...@amdtelecom.net
*Cc:* users@kannel.org
*Sent:* Wednesday, December 09, 2009 11:10 AM
*Subject:* Re: sqlbox and wap push
The goal is to make it work with sqlbox. Thus i would need to convert
to wbxml. This is where i need your example.
2009/12/9 Nikos Balkanas n...@amdtelecom.net
Hi,
Use Alex's link. Otherwise it is too lengthy to describe the protocol. If
you are interested the spec is:
WAP-249-PPGService-20010713-a
An example would be meaningless. It is different for each message. Wapbox
will do the same thing for you, but it doesn't work with SQLbox.
BR,
Nikos
- Original Message -
*From:* Sam nu.e...@gmail.com
*To:* Nikos Balkanas nbalka...@gmail.com
*Cc:* users@kannel.org
*Sent:* Wednesday, December 09, 2009 10:39 AM
*Subject:* Re: sqlbox and wap push
Thanks Nikos,
I understand the UDH stuff, however how do i convert to wbxml? Please
could you do me an example?
Also, would this code (
http://www.blogalex.com/wp-content/uploads/2008/09/send_wap_push.php.txt)
help in anyway?
Thanks in advance.
--Sam
2009/12/9 Nikos Balkanas nbalka...@gmail.com
Yes.
You will have to do some work, though.
1) Use the appropriate udh for wap-push:
udh=%06%05%04%0B%84%23%F0
in your sendsms url (url-encoded)
2) You have to convert your text first to wbxml and then urlencode it as
well in your URL.
BR,
Nikos
- Original Message -
*From:* Sam nu.e...@gmail.com
*To:* users@kannel.org
*Sent:* Wednesday, December 09, 2009 9:43 AM
*Subject:* sqlbox and wap push
Hi,
Please can i use sqlbox for wap push?
--Sam
Re: sqlbox and wap push
Wap push uses udh data, try using the full url my code generates.
Regards,
Alex
On Sun, Jan 3, 2010 at 10:45 PM, Sam nu.e...@gmail.com wrote:
Hi,
I have tried to use Alex php code here http://www.blogalex.com/wp-
content/uploads/2008/09/send_wap_push.php.txt
by inserting the content of $fields[text] into `msgdata` field of the
SQLbox table but this is not working.
?php
$fields = array (
'from' = '9912345678',
'to' = '9987654321',
'smsc' = 'mysmsc',
'link' = 'www.my-funny-link.com/myfile.mid',
'title' = 'Hi, look at this'
);
$kannel = array (
'host' = 'localhost',
'port' = 13013,
'user' = 'foo',
'pass' = 'bar'
);
$result = sendwappush ( $fields, $kannel );
print SENTbr$resultbr;
/*
sendwappush function.
Copyleft 2004 by Alejandro Guerrieri
This code is open source and GPL licensed
*/
function send_wap_push ( $fields, $kannel ) {
$fields[udh] = '%06%05%04%0B%84%23%F0';
$fields[text] = '%1B%06%01%AE%02%05%6A%00%45%C6%0C%03'.
hex_encode($fields['link'], '%').
'%00%01%03'.
hex_encode($fields['title'], '%').
'%00%01%01';
unset ( $fields['title'], $fields['link'] );
while(list($k,$v) = each($fields)) {
if ( $v != ) {
$string .= $k=$v;
}
}
$request = 'http://'.$kannel['host'].':'.$kannel[port].
'/cgi-bin/sendsms'.
'?user='.$kannel['user'].
'pass='.$kannel['pass'].
$string;
$result = @file( $request );
return 'ok';
}
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;
}
?
2010/1/3 Nikos Balkanas nbalka...@gmail.com
Hi,
With SQLbox you'll have to push it like sms. For a php example for simple
pushes please search archives for Alejandro Guerrieri's code.
BR,
Nikos
- Original Message -
*From:* Sam nu.e...@gmail.com
*To:* users@kannel.org
*Sent:* Sunday, January 03, 2010 11:23 PM
*Subject:* Re: sqlbox and wap push
Hi,
Please how do i make SQLBOX to handle a simple Service Load Wap push like
the following to a mobile?
?xml version=1.0?
!DOCTYPE sl PUBLIC -//WAPFORUM//DTD SL 1.0//EN
www.wapforum.org/DTD/sl.dtd
sl href=http://domain.com/images2.jpg/
N.B. Giving that the the appropriate UDH has been defined.
TIA
--Sam.
2009/12/9 Nikos Balkanas nbalka...@gmail.com
I don't have an example. Use Alex's link. And don't spam. 1 email is
plenth.
BR,
Nikos
- Original Message -
*From:* Sam nu.e...@gmail.com
*To:* Nikos Balkanas n...@amdtelecom.net
*Cc:* users@kannel.org
*Sent:* Wednesday, December 09, 2009 11:10 AM
*Subject:* Re: sqlbox and wap push
The goal is to make it work with sqlbox. Thus i would need to convert
to wbxml. This is where i need your example.
2009/12/9 Nikos Balkanas n...@amdtelecom.net
Hi,
Use Alex's link. Otherwise it is too lengthy to describe the protocol.
If you are interested the spec is:
WAP-249-PPGService-20010713-a
An example would be meaningless. It is different for each message.
Wapbox will do the same thing for you, but it doesn't work with SQLbox.
BR,
Nikos
- Original Message -
*From:* Sam nu.e...@gmail.com
*To:* Nikos Balkanas nbalka...@gmail.com
*Cc:* users@kannel.org
*Sent:* Wednesday, December 09, 2009 10:39 AM
*Subject:* Re: sqlbox and wap push
Thanks Nikos,
I understand the UDH stuff, however how do i convert to wbxml? Please
could you do me an example?
Also, would this code (
http://www.blogalex.com/wp-content/uploads/2008/09/send_wap_push.php.txt)
help in anyway?
Thanks in advance.
--Sam
2009/12/9 Nikos Balkanas nbalka...@gmail.com
Yes.
You will have to do some work, though.
1) Use the appropriate udh for wap-push:
udh=%06%05%04%0B%84%23%F0
in your sendsms url (url-encoded)
2) You have to convert your text first to wbxml and then urlencode it
as well in your URL.
BR,
Nikos
- Original Message -
*From:* Sam nu.e...@gmail.com
*To:* users@kannel.org
*Sent:* Wednesday, December 09, 2009 9:43 AM
*Subject:* sqlbox and wap push
Hi,
Please can i use sqlbox for wap push?
--Sam
Sms-service, WAP Push and PPG
Hello, After having successfully implemented wapbox, ppg and send a wappush on ppg HTTP interface using: lynx -dump http://localhost/test/sms-wap-push-2.php?num=XX; I try now to use it through sms-service without success, I always get on the mobile the POST or GET content URL in text and not in push sms: I tested with post-url and get_url but same result ie URL displayed on the mobile as text Do I miss something ? *2009-12-28 18:45:48 Receive SMS [SMSC:nokia6230] [SVC:] [ACT:] [BINF:] [FID:] [from:+687773502] [to:1234] [flags:-1:0:-1:0:-1] [msg:6:ecosse] [udh:0:] 2009-12-28 18:45:48 SMS HTTP-request sender:+X request: 'POST /wappush HTTP/1.1 Host: localhost:8080 X-Kannel-SMSC: nokia6230 Content-Type: multipart/related; boundary=multipart-boundary; type=application/xml Content-Length: 922 --multipart-boundary Content-type: application/xml --multipart-boundary Content-type: text/vnd.wap.si Test Google URL --multipart-boundary-- HTTP/1.1 202 Accepted Server: Kannel/1.4.3 Date: Mon, 28 Dec 2009 07:45:48 GMT Content-Length: 971 Content-Type: application/xml' url: ' http://localhost/test/sms-wap-push-2.php?num=%2BX' reply: 200 ' successful ' 2009-12-28 18:45:58 Sent SMS [SMSC:nokia6230] [SVC:^[ ]*(ecosse)[ ]*] [ACT:] [BINF:] [FID:] [from:+X] [to:+X] [flags:-1:0:-1:-1:-1] [msg:160:POST /wappush HTTP/1.1 .Host: localhost:8080 .X-Kannel-SMSC: nokia6230 .Content-Type: multipart/related; boundary=multipart-boundary; type=application/xml .Co] [udh:0:] * My config: group = sms-service keyword = ecosse get-url = http://localhost/test/sms-wap-push-2.php?num=%p; BR, -- Emmanuel
Re: Sms-service, WAP Push and PPG
Hi, As discussed in another thread in this list, you can use sms-service only with MO SMS, not for push (ppg or SMS). MO means Mobile Originated. With PPG you can push any text or URL you want, why then would you like to do an extra request to sms-service? Just send what you want from the beginning. BR, Nikos - Original Message - From: Emmanuel CHANSON To: users Sent: Monday, December 28, 2009 10:45 AM Subject: Sms-service, WAP Push and PPG Hello, After having successfully implemented wapbox, ppg and send a wappush on ppg HTTP interface using: lynx -dump http://localhost/test/sms-wap-push-2.php?num=XX; I try now to use it through sms-service without success, I always get on the mobile the POST or GET content URL in text and not in push sms: I tested with post-url and get_url but same result ie URL displayed on the mobile as text Do I miss something ? 2009-12-28 18:45:48 Receive SMS [SMSC:nokia6230] [SVC:] [ACT:] [BINF:] [FID:] [from:+687773502] [to:1234] [flags:-1:0:-1:0:-1] [msg:6:ecosse] [udh:0:] 2009-12-28 18:45:48 SMS HTTP-request sender:+X request: 'POST /wappush HTTP/1.1 Host: localhost:8080 X-Kannel-SMSC: nokia6230 Content-Type: multipart/related; boundary=multipart-boundary; type=application/xml Content-Length: 922 --multipart-boundary Content-type: application/xml --multipart-boundary Content-type: text/vnd.wap.si Test Google URL --multipart-boundary-- HTTP/1.1 202 Accepted Server: Kannel/1.4.3 Date: Mon, 28 Dec 2009 07:45:48 GMT Content-Length: 971 Content-Type: application/xml' url: 'http://localhost/test/sms-wap-push-2.php?num=%2BX' reply: 200 ' successful ' 2009-12-28 18:45:58 Sent SMS [SMSC:nokia6230] [SVC:^[ ]*(ecosse)[ ]*] [ACT:] [BINF:] [FID:] [from:+X] [to:+X] [flags:-1:0:-1:-1:-1] [msg:160:POST /wappush HTTP/1.1 .Host: localhost:8080 .X-Kannel-SMSC: nokia6230 .Content-Type: multipart/related; boundary=multipart-boundary; type=application/xml .Co] [udh:0:] My config: group = sms-service keyword = ecosse get-url = http://localhost/test/sms-wap-push-2.php?num=%p; BR, -- Emmanuel
Re: Sms-service, WAP Push and PPG
My call flow is the following: MO - keyword - Kannel sms-service match the keyword - get_url = php script that send a corresponding wap push sms to the original sender in order to fetch an url and retrieve a content (image, ...) I am just looking for a way to retrieve a content through wap triggered by a keyword sms Is that you were thinking? BR, Emmanuel 2009/12/28 Nikos Balkanas nbalka...@gmail.com Hi, As discussed in another thread in this list, you can use sms-service only with MO SMS, not for push (ppg or SMS). MO means Mobile Originated. With PPG you can push any text or URL you want, why then would you like to do an extra request to sms-service? Just send what you want from the beginning. BR, Nikos - Original Message - *From:* Emmanuel CHANSON emmanuelchan...@gmail.com *To:* users users@kannel.org *Sent:* Monday, December 28, 2009 10:45 AM *Subject:* Sms-service, WAP Push and PPG Hello, After having successfully implemented wapbox, ppg and send a wappush on ppg HTTP interface using: lynx -dump http://localhost/test/sms-wap-push-2.php?num=XX; I try now to use it through sms-service without success, I always get on the mobile the POST or GET content URL in text and not in push sms: I tested with post-url and get_url but same result ie URL displayed on the mobile as text Do I miss something ? *2009-12-28 18:45:48 Receive SMS [SMSC:nokia6230] [SVC:] [ACT:] [BINF:] [FID:] [from:+687773502] [to:1234] [flags:-1:0:-1:0:-1] [msg:6:ecosse] [udh:0:] 2009-12-28 18:45:48 SMS HTTP-request sender:+X request: 'POST /wappush HTTP/1.1 Host: localhost:8080 X-Kannel-SMSC: nokia6230 Content-Type: multipart/related; boundary=multipart-boundary; type=application/xml Content-Length: 922 --multipart-boundary Content-type: application/xml --multipart-boundary Content-type: text/vnd.wap.si Test Google URL --multipart-boundary-- HTTP/1.1 202 Accepted Server: Kannel/1.4.3 Date: Mon, 28 Dec 2009 07:45:48 GMT Content-Length: 971 Content-Type: application/xml' url: ' http://localhost/test/sms-wap-push-2.php?num=%2BX' reply: 200 ' successful ' 2009-12-28 18:45:58 Sent SMS [SMSC:nokia6230] [SVC:^[ ]*(ecosse)[ ]*] [ACT:] [BINF:] [FID:] [from:+X] [to:+X] [flags:-1:0:-1:-1:-1] [msg:160:POST /wappush HTTP/1.1 .Host: localhost:8080 .X-Kannel-SMSC: nokia6230 .Content-Type: multipart/related; boundary=multipart-boundary; type=application/xml .Co] [udh:0:] * My config: group = sms-service keyword = ecosse get-url = http://localhost/test/sms-wap-push-2.php?num=%p; BR, -- Emmanuel -- Emmanuel CHANSON Emmanuel Mobile Nouvelle-Calédonie: +687.77.35.02 Mobile France: +33 (0) 6.68.03.89.56 @email : emmanuelchan...@gmail.com
Re: Sms-service, WAP Push and PPG
You are right Nikos, The issue is solved by adding: max-messages = 0 I have already used Mbuni and it works for me using mm1 :), I would just test using wap-push Many thanks, Emmanuel 2009/12/28 Nikos Balkanas n...@amdtelecom.net That should work. You need to pass MSISDN to ppg, and set max-messages to 0. However, since mobile needs to have wap enabled (and suitable SIM) to get the URL, this could be a wap call (map-url) from the start (i.e. no SMS-PPG). Or you can play MMS with mbuni. BR, Nikos - Original Message - *From:* Emmanuel CHANSON emmanuelchan...@gmail.com *To:* Nikos Balkanas nbalka...@gmail.com *Cc:* users users@kannel.org *Sent:* Monday, December 28, 2009 10:38 PM *Subject:* Re: Sms-service, WAP Push and PPG My call flow is the following: MO - keyword - Kannel sms-service match the keyword - get_url = php script that send a corresponding wap push sms to the original sender in order to fetch an url and retrieve a content (image, ...) I am just looking for a way to retrieve a content through wap triggered by a keyword sms Is that you were thinking? BR, Emmanuel 2009/12/28 Nikos Balkanas nbalka...@gmail.com Hi, As discussed in another thread in this list, you can use sms-service only with MO SMS, not for push (ppg or SMS). MO means Mobile Originated. With PPG you can push any text or URL you want, why then would you like to do an extra request to sms-service? Just send what you want from the beginning. BR, Nikos - Original Message - *From:* Emmanuel CHANSON emmanuelchan...@gmail.com *To:* users users@kannel.org *Sent:* Monday, December 28, 2009 10:45 AM *Subject:* Sms-service, WAP Push and PPG Hello, After having successfully implemented wapbox, ppg and send a wappush on ppg HTTP interface using: lynx -dump http://localhost/test/sms-wap-push-2.php?num=XX; I try now to use it through sms-service without success, I always get on the mobile the POST or GET content URL in text and not in push sms: I tested with post-url and get_url but same result ie URL displayed on the mobile as text Do I miss something ? *2009-12-28 18:45:48 Receive SMS [SMSC:nokia6230] [SVC:] [ACT:] [BINF:] [FID:] [from:+687773502] [to:1234] [flags:-1:0:-1:0:-1] [msg:6:ecosse] [udh:0:] 2009-12-28 18:45:48 SMS HTTP-request sender:+X request: 'POST /wappush HTTP/1.1 Host: localhost:8080 X-Kannel-SMSC: nokia6230 Content-Type: multipart/related; boundary=multipart-boundary; type=application/xml Content-Length: 922 --multipart-boundary Content-type: application/xml --multipart-boundary Content-type: text/vnd.wap.si Test Google URL --multipart-boundary-- HTTP/1.1 202 Accepted Server: Kannel/1.4.3 Date: Mon, 28 Dec 2009 07:45:48 GMT Content-Length: 971 Content-Type: application/xml' url: ' http://localhost/test/sms-wap-push-2.php?num=%2BX' reply: 200 ' successful ' 2009-12-28 18:45:58 Sent SMS [SMSC:nokia6230] [SVC:^[ ]*(ecosse)[ ]*] [ACT:] [BINF:] [FID:] [from:+X] [to:+X] [flags:-1:0:-1:-1:-1] [msg:160:POST /wappush HTTP/1.1 .Host: localhost:8080 .X-Kannel-SMSC: nokia6230 .Content-Type: multipart/related; boundary=multipart-boundary; type=application/xml .Co] [udh:0:] * My config: group = sms-service keyword = ecosse get-url = http://localhost/test/sms-wap-push-2.php?num=%p; BR, -- Emmanuel -- Emmanuel CHANSON Emmanuel Mobile Nouvelle-Calιdonie: +687.77.35.02 Mobile France: +33 (0) 6.68.03.89.56 @email : emmanuelchan...@gmail.com -- Emmanuel CHANSON Emmanuel Mobile Nouvelle-Calédonie: +687.77.35.02 Mobile France: +33 (0) 6.68.03.89.56 @email : emmanuelchan...@gmail.com
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
wap push to midlet
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.
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
