Re: [Openbts-discuss] SIP MESSAGE content

[Kurtis H. <khe...@cs...>]

Nope, not that. In the RP-Message from the example
(http://betelco.blogspot.com/2009/10/sms-over-3gpp-ims-network.html):

000000069133010000F019069133010000F011000A9133163254760000AA05F330BB4E07

They repeat the SMSC information (069133010000F0) twice.

000000 !069133010000F0! 19 !069133010000F0! 11000A9133163254760000AA05F330BB4E07

This is NOT done in the OpenBTS messages, so far as I can see. The PDU
parsers I've found online seem to assume the second SMSC portion
should exist, which is why I couldn't parse the OpenBTS packets using
these tools. Is this intentional? Is there a reason why OpenBTS
doesn't need repeat that part of the message?

On Thu, Oct 20, 2011 at 4:54 AM, Alexander Chemeris
<ale...@gm...> wrote:
> Hi Kurtis,
>
> Ok, so you mean TP-Destination-Address in SMS-SUBMIT, right?
> But in your last SMS-SUBMIT example it's not empty: http://pastebin.com/f8jsVduc
>
> On Wed, Oct 19, 2011 at 20:52, Kurtis Heimerl <khe...@cs...> wrote:
>> If you look at your link
>> (http://betelco.blogspot.com/2009/10/sms-over-3gpp-ims-network.html)
>> the SMSC information is stored twice: Once in the RPDU and once in the
>> TPDU, unless I'm reading it wrong.
>>
>> On Wed, Oct 19, 2011 at 7:16 AM, Alexander Chemeris
>> <ale...@gm...> wrote:
>>> Hi Kurtis,
>>>
>>> Sorry for my slow response.
>>> Could you please clarify, which part exactly is missing?
>>> SMSC information (RP-Originator Address and RP-Destination Address)
>>> are stored in RP-Message.
>>>
>>> On Wed, Oct 19, 2011 at 12:22, Kurtis Heimerl <khe...@cs...> wrote:
>>>> Hey Alexander, do you have any idea why OpenBTS isn't including the
>>>> SMSC portion of the TPDU? I assume it's intentional, but most PDU
>>>> parsing libraries I've found assume it exists.
>>>>
>>>> On Mon, Oct 17, 2011 at 12:19 AM, Kurtis Heimerl
>>>> <khe...@cs...> wrote:
>>>>> Hey, just for list benefit, I eventually figured it out by decoding
>>>>> the packet in reverse:
>>>>> http://pastebin.com/f8jsVduc
>>>>>
>>>>> For some reason, the second SMSC portion of the message is simply not
>>>>> present. Past that, the other outstanding question is why the
>>>>> RP-Message Reference isn't 0. Either way, I can now decode the packets
>>>>> pretty easily, and that's nice.
>>>>>
>>>>> On Sun, Oct 16, 2011 at 12:21 AM, Kurtis Heimerl
>>>>> <khe...@cs...> wrote:
>>>>>> Thanks Alexander. I could use a little more direction, as something
>>>>>> seems horribly wrong.
>>>>>>
>>>>>> I took a stab at parsing out one of the SIP-MESSAGE packets coming out
>>>>>> of OpenBTS. Here (http://pastebin.com/Lyu7085K) is the trace and its
>>>>>> analysis. Something is clearly wrong, which means I missed something.
>>>>>>
>>>>>> Firstly, the RP-MESSAGE layer parses perfectly, aside from the message
>>>>>> reference being non-zero for some reason. The TPDU is a total mess. My
>>>>>> parsing of it seems correct, as the parsing utilities online agree
>>>>>> that it's nonsense. What's going on here? What did I miss?
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> On Sat, Oct 15, 2011 at 10:58 AM, Kurtis Heimerl
>>>>>> <khe...@cs...> wrote:
>>>>>>> You're quite right, you definitely directed me here before. My mistake.
>>>>>>>
>>>>>>> On Sat, Oct 15, 2011 at 3:02 AM, Alexander Chemeris
>>>>>>> <ale...@gm...> wrote:
>>>>>>>> Hi Kurtis,
>>>>>>>>
>>>>>>>> This has been discussed a couple of times on this mailing list.
>>>>>>>>
>>>>>>>> Data sent in SIP payload is RP-MESSAGE, which encapsulates TPDU.
>>>>>>>> Refer to this nice write up:
>>>>>>>> http://betelco.blogspot.com/2009/10/sms-over-3gpp-ims-network.html
>>>>>>>>
>>>>>>>> Disappeared images in that post can be still found here:
>>>>>>>> http://doubango.googlecode.com/svn/branches/2.0/doubango/images/sms/
>>>>>>>>
>>>>>>>> On Sat, Oct 15, 2011 at 03:00, Kurtis Heimerl <khe...@cs...> wrote:
>>>>>>>>> What's in one of the SIP MESSAGE bodies? My first guess is a L3 PDU,
>>>>>>>>> but the various PDU decoders on the internet (e.g.,
>>>>>>>>> http://twit88.com/home/utility/sms-pdu-encode-decode) aren't agreeing
>>>>>>>>> with that... I really want this
>>>>>>>>> (http://minimoesfuerzo.org/2010/04/18/python-messaging-sms-encoderdecoder-masses/)
>>>>>>>>> to work so I that I can decode messages in freeswitch. Are there extra
>>>>>>>>> headers included? L2 or L1 stuff?
>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>> All the data continuously generated in your IT infrastructure contains a
>>>>>>>>> definitive record of customers, application performance, security
>>>>>>>>> threats, fraudulent activity and more. Splunk takes this data and makes
>>>>>>>>> sense of it. Business sense. IT sense. Common sense.
>>>>>>>>> http://p.sf.net/sfu/splunk-d2d-oct
>>>>>>>>> _______________________________________________
>>>>>>>>> Openbts-discuss mailing list
>>>>>>>>> Ope...@li...
>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/openbts-discuss
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Regards,
>>>>>>>> Alexander Chemeris.
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Regards,
>>> Alexander Chemeris.
>>>
>>
>
>
>
> --
> Regards,
> Alexander Chemeris.
>