**>From: "Oscar Flores" <[EMAIL PROTECTED]> **>To: <[EMAIL PROTECTED]> **>Subject: RE: OTA info **>In-Reply-To: <[EMAIL PROTECTED]> **>Date: Fri, 15 Aug 2003 09:55:08 -0400 **> **>Hi **> **>Thaks for your answers, we've set the parameters as you indicated bellow **>but, we've been reviewing the GSM 3.40 and also som Gemplus manuals and **>we have to set these parameters. **> **>TP-TPDU (MTI, MMS, SRI, UDHI, Reply Path) **>TP-OA (Originator Address, TON, NPI) **>TP-PID **>TP-DCS **>TP-SCTS **>TP-UDL **>TP-UD **> **>>From the configuration that you give to us we got the TP-PID and TP-DCS **>and we also build the TP-UD (User Data Header + User Data Binary), but **>we still have missed the TP-TPDU, TP-OA, TP-SCTS, TP-UDL Do you know how **>to get this parameters from Kannel? I mean how to get this parameteres **>using kannel settings? **> **>And also, does anyone of you know the SIM Toolkit commands that have to **>go in the TP-UD? **> **>Many Thanks
Are you trying to construct your own OTA from the GEMPlus specs or are you using the OTA generated by the ADE Parser? If you send the binary version of the hex dump generated by the ADE Parser to kannel as an application/octet-stream, then you do not have to deal with the MTI, MMS, and UDHI. Kannel will take care of the OA [TON/NPI]. Kannel will also set UDHI and RP if you tell Kannel to set it. MTI (Message Type Indicator) is set by Kannel as SMS-DELIVER since you are using Kannel to generate an MT SMS to a mobile entity. MMS (More Message to Send) is set by Kannel if, due to size of SM, Kannel had to split up the original SM into multiple 140 octet SM. SRI (Status Report Indicator) is set when you use Kannel's DeLivery Report (DLR) feature. Of course, the operator must be willing to provide you with delivery reports in order for this to work. UDHI (User Data Header Indicator) is set by Kannel if you use the X-Kannel-UDH Header to an HTTP_POST, the udh= of an HTTP_GET, or the <udh></udh> of an XML_POST. RP (Reply Path Indicator) can be set by Kannel if you use the X-Kannel-RPI Header to an HTTP_POST, rpi= of an HTTP_GET, or the <rpi></rpi> of an XML_POST. TP-OA (Originating Address), its Type Of Number (TON), and Number Plan Identifier (NPI) is set by Kannel. The method varies a little from each SMSC handler. Normally, if the OA or Destination Address (DA) is prefixed by an '+' when sent to Kannel's sendsms-user interface, then the TON will be set to xx001xxxx (0x10)--International. If no '+' prefix then the TON is set to xx000xxxx (0x00)-Unknown. The NPI is usually set to xxxxx0001 (0x01)-ISDN/E.164/E.163. Some SMSC handlers can accept a hard-coded TON/NPI (eg SMPP). Consult the Kannel manual for more info on how to force the TON/NPI on the OA and DA. I have no idea how you can set the Service Center Time Stamp (SCTS) since that's not set by the SMS Messaging Entity (SME). If you are using the hex dump from the ADE Parser, then the first octet indicates the User Data Length (UDL) and can be relayed to Kannel via the Content-Length Header of an HTTP_POST. The User Data (UD) is the binary representation of the the hex dump after the UDL. You can relay this to Kannel by: 1) converting the hex dump to binary octets 2) establishing an HTTP_POST to Kannel's sendsms-user service 3) setting all the headers as indicated by my previous email 4) setting the Content-Type Header to be application/octet-stream 5) sending the binary octets to Kannel via the HTTP_POST connection [ ... ] Jeessh....now I finally read your last enquiry. I can better understand the reason why you though you needed to generate all this. You DON'T have or DON'T want to use the ADE Parser to generate the OTA. You are trying to roll your own OTA through the GEMPlus specs. I can't answer you about the contents of the UD. I'm not sure if the current OTA generated by the ADE Parser is 3GPP 23.140 compliant or not (I don't have the time to compare bytecodes). Check out the technical specs for the SIM Toolkit available in the 3GPP tech specs repository. Regards, Davy Chan
