Re: Dissectors for SMS over 3GPP IMS Network

[rajeev <i.rarsh () gmail com>]

Hi Anders,
Thanks a lot for the quick response. I tried to check the same with SVN
build
32080 for an outgoing message(RP DATA, MS->N), and wireshark was able to
dissect the RP information as well as the TPDU itself.

Thanks.

Regards,
Rajeev

On Mon, Mar 1, 2010 at 4:18 PM, rajeev <i.rarsh () gmail com> wrote:

> Hi,
> Is there a way to dissect the 3GPP SMS, contained in the message body of
> SIP MESSAGE method, as per the 3GPP standard *3GPP TS 24.341*?
>
> A typical example of the MESSAGE from MO (3GPP TS 24.341[Table B.5-1]) is
>
> *MESSAGE sip:sc.home1.net SIP/2.0
> Via: SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp;
> branch=z9hG4bKnashds7
> Max-Forwards: 70
> Route: <sip:pcscf1.visited1.net:7531;lr;comp=sigcomp>, <
> sip:orig () scscf1 home1 net <sip%3Aorig () scscf1 home1 net>;lr>
> P-Preferred-Identity: "John Doe" <sip:user1_public1 () home1 net<sip%3Auser1_public1 () home1 net>
> >
> From: <sip:user1_public1 () home1 net <sip%3Auser1_public1 () home1 net>>;
> tag=171828
> To: <sip:sc.home1.net.net>
> Call-ID: cb03a0s09a2sdfglkj490333
> Cseq: 666 MESSAGE
> Content-Type: application/vnd.3gpp.sms
> Content-Length: (…)*
>
> The payload includes an RP-DATA message (as per 3GPP TS 24.011 [8]). It
> includes:
> - Address of the originating UE: this field includes the length indicator
> only, 3GPP
> - Address of the destination SC, which is configured in the UE; and
> - RP-User-Data (3GPP TS 23.040 [3]), which includes SMS-SUBMIT as type
> indicator.
>
> Regards,
> Rajeev
___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request () wireshark org?subject=unsubscribe