Problem: Wap push as a text SMS
Title: Mensaje Hi all, i hope that anyone can help me, we are trying to send a Wap Push, but the phone receives a SMS instead (with a lot of weird characters) Here are the actual details: - We use kannel 1.4.1, downloaded from CVS and installed with the following options in Debian: --with-mysql --enable-pcre --disable-docs --disable-keepalive --disable-ssl --with-sysconfdir=/etc/kannel - Is already connected to the operator's SMSC and we can send and receive normal SMS - The orig and dest TONs and NPI are fixed as 1, as the operator said to us - The posting URL we are using is: http://:/cgi-bin/sendsms?username=&password=&to=&from=<4 number shor code>&udh=%06%05%04%0B%84%23%F0&text=%1B%06%01%AE%02%05%6A%00%45%C6%0C%03%77%61%70%2E%74%6D%6F%76%69%6C%2E%63%6C%2F%74%6D%63%2F%70%6F%72%74%61%6C%2F%77%61%70%2F%6A%75%65%67%6F%73%2F%69%6E%64%65%78%2E%70%68%70%3F%49%44%58%50%3D%26%49%44%42%41%53%45%3D%33%26%49%44%4E%4F%44%4F%3D%33%00%01%03%4D%6F%76%69 - Using this same configuration and post url but for ANOTHER Operator, the wap push is received OK - We have an example (a trace) of a correct wap push, and the differences we see with our trace are in the Data Coding (0xf5 in the correct one, and 0x04 in ours), Header lenght (20 bytes in the correct one and 32 bytes in ours ---may be the 12 extra bytes are the "options", cause our trace names "options: (12 bytes)", and the correct trace does not name it), and a "extra" line inside the tag where the url is (the correct one has 'Title' -- has a "1" after the URL) We know is not an operator's problem cause if we send the packages manually throught a socket connection, the wap push works. How can we solve this? How can we set the DCS in kannel? Please, would be a great help if any of you can guide us Regards -- ___ Joaquín Vera Aguilera Technology Supervisor Mobile: +56 (8) 500 4290 / +56 (9) 675 6727 Phone: +56 (2) 333 1650 Fax: +56 (2) 333 0597 Skype: joaquinatech Email: [EMAIL PROTECTED] URL: http://www.andinatech.com ___ This message and any attachments are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Emails are suceptible to alteration, therefore neither AndinaTech nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified. Este mensaje y sus anexos son confidenciales y deben ser leído solamente por el destinatario. Todo uso no autorizado o reproducción está prohibido. Los correos son susceptibles de alterar, por lo tanto ni AndinaTech ni ninguno de sus subsidiarios o afiliados será responsable si el mensaje es alterado, cambiado o falsificado. Print only if necessary. Each ton of non-used paper is equivalent to 17-20 young eucalyptus trees.
Re: Problem: Wap push as a text SMS
Title: Mensaje Yes, the operator accepts binary messages, as i said previously "we know is not an operator's problem cause if we send the packages manually throught a socket connection, the wap push works" Taking this base, we had to contruct an application to send the wap pushes... so, for now, we receive ans send sms throught kannel, but send the wap push throught this small application; but the final idea is to use kannel for all the services (as we have with the others operators) We already ask the operator about this, and the problem is ours (also, other people connected with this operator, also had to construct an application to send the wap pushes 'cause kannel didnt make it and cant pay for licenced applications) Greetings Joaquin, Are you sure that the operator accepts binary messages? If you're sure that the binary message is ok (and it seems, since it works with other operators) maybe you should ask the operator about it. Maybe he has to configure something to allow you to send binary messages (wap-pushes for example). Hope it helps, Alejandro. On 5/10/07, Joaquin Vera A. <[EMAIL PROTECTED]> wrote: Hi all, i hope that anyone can help me, we are trying to send a Wap Push, but the phone receives a SMS instead (with a lot of weird characters) Here are the actual details: - We use kannel 1.4.1, downloaded from CVS and installed with the following options in Debian: --with-mysql --enable-pcre --disable-docs --disable-keepalive --disable-ssl --with-sysconfdir=/etc/kannel - Is already connected to the operator's SMSC and we can send and receive normal SMS - The orig and dest TONs and NPI are fixed as 1, as the operator said to us - The posting URL we are using is: http://:/cgi-bin/sendsms?username=&password=&to=&from=<4 number shor code>&udh=%06%05%04%0B%84%23%F0&text=%1B%06%01%AE%02%05%6A%00%45%C6%0C%03%77%61%70%2E%74%6D%6F%76%69%6C%2E%63%6C%2F%74%6D%63%2F%70%6F%72%74%61%6C%2F%77%61%70%2F%6A%75%65%67%6F%73%2F%69%6E%64%65%78%2E%70%68%70%3F%49%44%58%50%3D%26%49%44%42%41%53%45%3D%33%26%49%44%4E%4F%44%4F%3D%33%00%01%03%4D%6F%76%69 - Using this same configuration and post url but for ANOTHER Operator, the wap push is received OK - We have an example (a trace) of a correct wap push, and the differences we see with our trace are in the Data Coding (0xf5 in the correct one, and 0x04 in ours), Header lenght (20 bytes in the correct one and 32 bytes in ours ---may be the 12 extra bytes are the "options", cause our trace names "options: (12 bytes)", and the correct trace does not name it), and a "extra" line inside the tag where the url is (the correct one has 'Title' -- has a "1" after the URL) We know is not an operator's problem cause if we send the packages manually throught a socket connection, the wap push works. How can we solve this? How can we set the DCS in kannel? Please, would be a great help if any of you can guide us Regards -- ___ Joaquín Vera Aguilera Technology Supervisor Mobile: +56 (8) 500 4290 / +56 (9) 675 6727 Phone: +56 (2) 333 1650 Fax: +56 (2) 333 0597 Skype: joaquinatech Email: [EMAIL PROTECTED] URL: http://www.andinatech.com ___ This message and any attachments are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Emails are suceptible to alteration, therefore neither AndinaTech nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified. Este mensaje y sus anexos son confidenciales y deben ser leído solamente por el destinatario. Todo uso no autorizado o reproducción está prohibido. Los correos son susceptibles de alterar, por lo tanto ni AndinaTech ni ninguno de sus subsidiarios o afiliados será responsable si el mensaje es alterado, cambiado o falsificado. Print only if necessary. Each ton of non-used paper is equivalent to 17-20 young eucalyptus trees. -- Alejandro Guerrieri Magicom http://www.magicom-bcn.net/ LinkedIn: http://www.linkedin.com/in/aguerrieri No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.467 / Virus Database: 269.6.6/795 - Release Date: 09-05-2007 15:07 -- ___ Joaquín Vera Aguilera Technology Supervisor Mobile: +56 (8) 500 4290 / +56 (9) 675 6727 Phone: +56 (2) 333 1650 Fax: +56 (2) 333 0597 Skype: joaquinatech Email: [EMAIL PROTECTED] URL: http://www.andinatech.com ___
Re: Problem: Wap push as a text SMS
Alejandro, your application does not work for this operator. The
original we have (that works for the other operators) is very similiar
to this one, and as it depends on the actual kannel and smsc
configuration, the problem remains.
We built a small java application that opens a socket to the smsc, it
builds the smpp package as the smpp v.3.4 specifications, it encodes
all the necesary things and send them throught the connection.
As you see, we are not using any kannel libraries nor special stuff, we
only took the ".cap" file the operator gaved us (with their working
example), we splited it, changed some things, and send it. This works
really fine, but as i said in the first time... that is not the final
idea.
Regards
Joaquin,
Yep, I've noticed that right after pushing "send" :P
What are you using to construct the binary message? I've made a small
php function a few years ago to encode a wap push. It's on the list
archives here:
http://osdir.com/ml/mobile.kannel.user/2004-04/msg7.html
Please try encoding the wap-push with it, maybe you have more luck that
way. I'm using it with many operators on many Latin American countries
with no problems.
Kannel can set the DCS by using headers/parameters on the sendsms
interface, but I'm not sure if the SMPP driver supports this.
Hope it helps,
Alejandro.
On 5/10/07, Joaquin Vera A. <[EMAIL PROTECTED]>
wrote:
Yes, the operator accepts
binary messages, as i said previously "we
know is not an operator's problem cause if we send the packages
manually throught a socket connection, the wap push works"
Taking this base, we had to contruct an application to send the wap
pushes... so, for now, we receive ans send sms throught kannel, but
send the wap push throught this small application; but the final idea
is to use kannel for all the services (as we have with the others
operators)
We already ask the operator about this, and the problem is ours (also,
other people connected with this operator, also had to construct an
application to send the wap pushes 'cause kannel didnt make it and cant
pay for licenced applications)
Greetings
Joaquin,
Are you sure that the operator accepts binary messages?
If you're sure that the binary message is ok (and it seems, since it
works with other operators) maybe you should ask the operator about it.
Maybe he has to configure something to allow you to send binary
messages (wap-pushes for example).
Hope it helps,
Alejandro.
On 5/10/07, Joaquin Vera A. <[EMAIL PROTECTED]
>
wrote:
Hi all, i hope that
anyone
can help me, we are trying to send a Wap
Push, but the phone receives a SMS instead
(with a lot of weird characters)
Here are the actual details:
- We use kannel 1.4.1, downloaded from CVS and installed with the
following
options in Debian:
--with-mysql --enable-pcre --disable-docs --disable-keepalive
--disable-ssl --with-sysconfdir=/etc/kannel
- Is already connected to the operator's SMSC and we can send and
receive normal SMS
- The orig and dest TONs and NPI are fixed as 1, as the operator said
to us
- The posting URL we are using is: http://:/cgi-bin/sendsms?username=&password=&to=&from=<4
number shor
code>&udh=%06%05%04%0B%84%23%F0&text=%1B%06%01%AE%02%05%6A%00%45%C6%0C%03%77%61%70%2E%74%6D%6F%76%69%6C%2E%63%6C%2F%74%6D%63%2F%70%6F%72%74%61%6C%2F%77%61%70%2F%6A%75%65%67%6F%73%2F%69%6E%64%65%78%2E%70%68%70%3F%49%44%58%50%3D%26%49%44%42%41%53%45%3D%33%26%49%44%4E%4F%44%4F%3D%33%00%01%03%4D%6F%76%69
- Using this same configuration and post url but for ANOTHER Operator,
the
wap push is received OK
- We have an example (a trace) of a correct wap push, and the
differences we see with our trace are in the Data Coding (0xf5 in the
correct one, and 0x04 in ours), Header lenght (20 bytes in the correct
one and 32 bytes in ours ---may be the 12 extra bytes are the
"options", cause our trace names "options: (12 bytes)", and the correct
trace does not name it), and a "extra" line inside the
tag where the url is (the correct one has
'Title' -- has a "1" after the URL)
We know is not an operator's problem cause if we send the packages
manually throught a socket connection, the wap push works.
How can we solve this?
How can we set the DCS in kannel?
Please, would be a great help if any of you can guide us
Regards
--
___
Joaquín Vera Aguilera
Technology Supervisor
Mobile: +56
(8) 500 4290 / +56 (9)
675 6727
Phone: +56 (2) 333
1650
