|
Dear sir,
Thank you very much!
According to what you said, kannel doesn't
implement the UDH header now. Do you have a plan?
and would you pls tell me which optional parameters
in submit_sm are UDH header? and which protocol depicts the UDH?
Best Regards,
Guanghua Hou
UTStarCom
BJR&D
----- Original Message -----
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]
------------------------------------------------------------------
|
