Title: Message
Hello,
I'm using ethereal
0.10.7 for monitoring SIP calls. I found a problem in decoding an INVITE
message, in the attachement you can find the "invite_ko.cap" and the
corresponding "invite_ok.txt", I mean the same packet decoded correctly with
another analyzer.
I hope this could be
helpful for improving SIP decoding.
Best
Regards,
Luca
Bianchi
Luca Bianchi
Telecom Italia LAB LAB.TS.S
Via Reiss
Romoli, 274 - 10148 Turin (Italy)
Tel.: +39.011.2287336
Fax.: +39.011.2286813
Mob.: +39 335 1326587
E-mail: luca1.bianchi@xxxxxxxxxxxxxxxx
http://www.telecomitalialab.com
Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A.
====================================================================
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@xxxxxxxxx. Thank you
====================================================================
11:04:29/757.4 1- D4 +D4 DATA UNIT----------------------------------[00608]+
| Protocol: UDP from IP |
| S:163.162.180.150 D:163.162.51.230 |
+-----------------------------------------------------+
D4 UDP (S:05062 D:05060) Len:00574 Chk:3a79 [0566]
D5 SIP [0566]
INVITE sip:__sip-uireq@xxxxxxxxxxxxxx;user=243883 SIP/2.0
Route: <sip:163.162.51.230:5060>
CSeq: 2025723182 INVITE
i: [email protected]
t: <sip:__sip-uireq@xxxxxxxxxxxxxx>
f: <sip:55555@xxxxxx>;tag=10993897120413
l: 0
m: <sip:163.162.180.151:5060>
Max-Forwards: 69
Record-Route: <sip:[email protected];lr>
v: SIP/2.0/UDP 163.162.180.150:5060 ;branch=z9hG4bK.sSsS.a3a2b4a0.3fe1febd9bd
4c828068a210fa25380.465, SIP/2.0/UDP 163.162.180.151:5060 ;branch=z9hG4bK.sSs
S.a3a2b4a1.da910d74d113e1ed53b6766a431f1f0.330
Attachment:
invite_ko.cap
Description: invite_ko.cap