|
All,
Thanks a lot!
Now I understand UDH. WDP is formated using UDH
framework. Both GSM and 3gpp adopt UDH as WAP bearer.
Now another question:
WDP supports multiple segments and SMPP also
supports multiple segments. kannel only supports WDP segment. Why?
Best Regards, Guanghua Hou UTStarCom BJR&D
----- Original Message -----
Sent: Sunday, June 22, 2003 7:50 PM
Subject: Re: SMPP header
Kannel does implement *generic* SMS port (and segmentation) UDH
, otherwise push would not work. It does not implement any smpp specific
wap parameters because these would not work with other protocols.
UDH
is not a protocol parameter, optional or otherwise, it is part of the user
message. Port udh tells what port should handle the message. Because phone
push application is listening at that port, the push would be
handled properly. (If there is no UDH present, the phone assumes that it
got a plain sm)
For implementing WAP over SMS wapforum (currently open
mobile alliance) specs WAP-200-WDP-20000219-a.pdf. Url is
http://www.wapforum.org/what/technical_1_2_1.htm.
Note again that
Kannel implement this document, not smpp specific one.
Aarno
On
Tuesday, June 24, 2003, at 05:05 AM, ghhou wrote:
Dear sir,/smaller>/fontfamily> Thank
you very much!/smaller>/fontfamily> According
to what you said, kannel doesn't implement the UDH header now. Do you have a
plan?/smaller>/fontfamily> and
would you pls tell me which optional parameters in submit_sm are UDH header?
and which protocol depicts the UDH?/smaller>/fontfamily> Best
Regards, Guanghua Hou UTStarCom
BJR&D/smaller>/fontfamily>
----- Original Message
----- From: Andreas Fink/color> To: ghhou/color> Sent: Sunday,
June 22, 2003 6:56 PM Subject: Re: SMPP header
On
Dienstag, Juni 24, 2003, at 04:44 Uhr, ghhou wrote:
Dear
sir, How to explain the optional parameters(source_port,
destination port) in submit_sm of SMPP. SMPPv3.4 page62 says
"This parameter should be present for WAP applications." But kannel
doesn't implement these optional parameters.
esm_class
in bearerbox is given the value
"0x43".
x x x x x x 1 1 Store and Forward mode
x x 0 0 0 0 x x Default message Type (i.e. normal
message)
0 1 x x x x x x
UDHI Indicator (only relevant for MT short messages)
Right. UDH
indicator must be set to tell the handset that there is a user data header
present. the user data header is prepended to the
payload.
This value doesn't indicate this short message is WAP
push .
It does not. SMSC's are there to transport SMS, not wap
data. an SMSC is not a wap gateway of any sort. So it doesn't have to
know anything about wap push but still can transport the WAP push
PDU. Check out the GSM specs for SMS-PDU's in the GSM networks. There is
nothing in there about WAP. WAP was invented far after SMS so SMSC's don't
have to know if this is a wap push. Handsets do. Thats why there is a UDH
header indicating WAP ports.
Andreas Fink Global
Networks Switzerland
AG
------------------------------------------------------------------ Tel:
+41-61-6666333 Fax: +41-61-6666334 Mobile: +41-79-2457333 Global
Networks, Inc. Clarastrasse 3, 4058 Basel, Switzerland Web:
http://www.global-networks.ch/
[EMAIL PROTECTED] ------------------------------------------------------------------
/bigger>
|