Re: SMPP header
Guanghua Hou wrote: > > Hi, > To send a push message through SMSC. How to set the application type in > SMPP? Which header will be used? UDH or service_type or protocol_id? > SMSC may support applications such as text, voice mail notification, WAP, > CSSD and etc. My question is how to distinguish these application by > terminal and how to set the application type in SMPP. AFAIR, it's enough when you send the binary message via the &text and &udh HTTP parameters to have the SMSC transport it accordingly to the device. Unfortunatly smsbox has to be abstracted for other SMSC module types, hence you don't have the full potential to set SMPP specific parameters of the submit_sm PDU. What kind of messages are you trying to send? Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: SMPP header
If I send a push message to terminal through SMSC. How does the terminal know this short message is a push message? it goes to the WAP Push port (coded in the UDH) How does SMSC know? it doesnt know and it doesnt have to know. Its just payload to transport from SME to handset for the SMSC. Such push message may include SI/SL, SIR and MMS notofication. correct. So one header in SMPP should be set. But what header? No additional special header is required. UDH is enough. Andreas Fink Global Networks Switzerland AG -- Tel: +41-61-333 Fax: +41-61-334 Mobile: +41-79-2457333 Global Networks, Inc. Clarastrasse 3, 4058 Basel, Switzerland Web: http://www.global-networks.ch/ [EMAIL PROTECTED] --
Re: SMPP header
Dear sir, What value of UDH is used in SMPP? It's one byte value. Please tell me the value. In kannel, it's set as '0'. Thanks Guanghua Hou - Original Message - From: Andreas Fink To: ghhou Cc: [EMAIL PROTECTED] Sent: Saturday, June 21, 2003 10:59 PM Subject: Re: SMPP header If I send a push message to terminal through SMSC. How does the terminalknow this short message is a push message?it goes to the WAP Push port (coded in the UDH) How does SMSC know?it doesnt know and it doesnt have to know. Its just payload to transport from SME to handset for the SMSC. Such push message may include SI/SL, SIR and MMSnotofication.correct. So one header in SMPP should be set. But what header?No additional special header is required. UDH is enough.Andreas FinkGlobal Networks Switzerland AG--Tel: +41-61-333 Fax: +41-61-334 Mobile: +41-79-2457333Global Networks, Inc. Clarastrasse 3, 4058 Basel, SwitzerlandWeb: http://www.global-networks.ch/ [EMAIL PROTECTED]--
Re: SMPP header
You simple use the UDH header to set the source and destination ports (like on machine ports) for identifying the destination application that handles the message. Please see test/test_ppg to see how to send SI/SL documents to an device. Otherwise consult the appropriate WAP Forum specs. The main things is: You don't have to use the special SMPP PDU flagging to tell the SMSC (it simply does not have to know!) or the mobile which message type it is. The mobile device will determine this anyway by comparing the UDH header you are sending. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: SMPP header
Dear sir, Maybe optional parameters are used to indicate the Short message is WAP push message. Two parameters: source_port, destination port. Is it right? Best Regards, Guanghua Hou > You simple use the UDH header to set the source and destination ports > (like on machine ports) for identifying the destination application > that handles the message. > > Please see test/test_ppg to see how to send SI/SL documents to an > device. Otherwise consult the appropriate WAP Forum specs. > > The main things is: You don't have to use the special SMPP PDU > flagging to tell the SMSC (it simply does not have to know!) or the > mobile which message type it is. The mobile device will determine this > anyway by comparing the UDH header you are sending. > > Stipe > > [EMAIL PROTECTED] > --- > Wapme Systems AG > > Vogelsanger Weg 80 > 40470 Düsseldorf > > Tel: +49-211-74845-0 > Fax: +49-211-74845-299 > > E-Mail: [EMAIL PROTECTED] > Internet: http://www.wapme-systems.de > --- > wapme.net - wherever you are >
Re: SMPP header
On Dienstag, Juni 24, 2003, at 04:09 Uhr, ghhou wrote: Dear sir, Maybe optional parameters are used to indicate the Short message is WAP push message. Two parameters: source_port, destination port. Is it right? Those are in the UDH, not in the SMPP packet. Andreas Fink Global Networks Switzerland AG -- Tel: +41-61-333 Fax: +41-61-334 Mobile: +41-79-2457333 Global Networks, Inc. Clarastrasse 3, 4058 Basel, Switzerland Web: http://www.global-networks.ch/ [EMAIL PROTECTED] --
Re: SMPP header
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 HouUTStarCom BJR&D - Original Message - From: Andreas Fink To: ghhou 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 FinkGlobal Networks Switzerland AG--Tel: +41-61-333 Fax: +41-61-334 Mobile: +41-79-2457333Global Networks, Inc. Clarastrasse 3, 4058 Basel, SwitzerlandWeb: http://www.global-networks.ch/ [EMAIL PROTECTED]--
Re: SMPP header
ok, once again: can is *able* to send *any* kind of SMS messages. This includes *all* kind of binary messages (ie. WAP Push document SI, SL, MMS-notification). Kannel has it's own PPG inside and hence deals with those binary messages quite commonly. So if you want to use Kannel as WAP Push Proxy, simply connect to your SMPP provider and use Kannel's PPG to deliver push messages to remote devices. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
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-2219-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, 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 - From: Andreas Fink To: ghhou 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-333 Fax: +41-61-334 Mobile: +41-79-2457333 Global Networks, Inc. Clarastrasse 3, 4058 Basel, Switzerland Web: http://www.global-networks.ch/ [EMAIL PROTECTED] --
Re: SMPP header
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 HouUTStarCom BJR&D - Original Message - From: Aarno Syvänen To: ghhou Cc: [EMAIL PROTECTED] 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 portshould handle the message. Because phone push application is listening at that port, the push would be handledproperly. (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-2219-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.AarnoOn Tuesday, June 24, 2003, at 05:05 AM, ghhou wrote: 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 HouUTStarCom BJR&D- Original Message -From: Andreas FinkTo: ghhouSent: Sunday, June 22, 2003 6:56 PMSubject: Re: SMPP headerOn 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 FinkGlobal Networks Switzerland AG--Tel: +41-61-333 Fax: +41-61-334 Mobile: +41-79-2457333Global Networks, Inc. Clarastrasse 3, 4058 Basel, SwitzerlandWeb: http://www.global-networks.ch/ [EMAIL PROTECTED]--
