a) the port, client port specified for push
b) X-WAP-Application-Id header, telling is the application wlm.ua or mms.ua
In pull, it is the phone that starts the things, so it is more like how server knows
that this is wap (phone knows what port it is using for the request).
Service type wap could be useful implementing wap over sms, but port UDH tells the same thing (and is used by all protocols).
Aarno
On Friday, April 4, 2003, at 11:21 AM, Guanghua Hou wrote:
Hi,
How phone to know the application type? So SMSC should transfer some smpp
headers to phone and the header value is written by Kannel. Now I think the
header is "service_type" and its value is "WAP". But kannel sets this value
as NULL.
According to what you mean, phone will know the message is binary message
and know the message is WDP PDU if received message is binary.
Best Regards,
Guanghua Hou
Hi,
for smsc, pushes are just another binary message. Only the phone know the difference between say ringtone and mms notification.
Aarno
On Friday, April 4, 2003, at 03:44 AM, Guanghua Hou wrote:
Hi,
UDH header is WDP header, not SMPP header. SMSC system will treate WDP
PDU
as a short message and transfer it to mobile terminal transparently.
SMSC
won't parse WDP header. So only SMPP header can be used to distinguish
different application by SMSC.
BR, Guanghua Hou
Guanghua Hou wrote:message
When push message is sent through SMSC. SMPP v3.4 'submit_sm' is used by kannel. Kannel sets 'service_type'as NULL and 'protocol-id' as zero.The short message is WDP/WSP encoded PDU.
When this message is sent to Terminal, how does the terminal distinguish application type of short message? How does the terminal know thismessageis WAP push message? Maybe the terminal treates it as normal shortof ascii.
Stipe wrote:
by the UDH header. Within the UDH header you specify the receiver port
(like a socket port on regular machines).
Check our the UDH headers sequence when pushing a SL or SI document via Kannel's PPG.
