| Bug ID |
8552
|
| Summary |
SIP packet encoding
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.9.x (Experimental)
|
| Hardware |
x86-64
|
| OS |
Windows 8
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Wireshark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 10528 [details]
sip packet
Build Information:
--
I've captured a SIP session, where SIP packet can not be recognized, even after
encoding. At first I though it's caused by source port (5061) and the packet is
tried to be decoded as SIP TLS, even though the destination port is 5060.
However, after repeating the scenario with different source port (packet
generated by sipp) the result was the same.
I thought that it may be caused by error in SIP packet (wrong parsing), but I
have checked it with SIP ABNF and it is correct.
I could not find any logs why this packet can't be decoded as sip.
The attached packet is correctly recognized by asterisk server.
You are receiving this mail because:
- You are watching all bug changes.