Wap push problem

2010-12-29 Thread Edwin Malo

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

2010-12-29 Thread Edwin Malo

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