AK
appkiro.comPaste your SIP message below
v=0 o=alice 2890844526 2890844526 IN IP4 client.example.com s=- c=IN IP4 client.example.com t=0 0 m=audio 49170 RTP/AVP 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv
The SIP Message Parser is a specialized client-side utility built for VoIP engineers, network administrators, and developers working with the Session Initiation Protocol (RFC 3261). When troubleshooting call drops, one-way audio, or registration failures, inspecting raw SIP traffic from a packet capture (PCAP) or debug log is crucial. This tool instantly transforms unreadable blocks of text into structured, searchable data.
When you paste a raw SIP request (like an INVITE) or response (like a 200 OK), the parser categorizes the information into three distinct layers:
Call-ID, CSeq, Via, and Contact to help you trace the dialog path.Because SIP traces often contain sensitive topology information (internal IP addresses, phone numbers, domain names, and authentication hashes), all parsing occurs locally in your browser. No SIP message or payload is ever transmitted over the network or saved to our servers, guaranteeing complete privacy for your diagnostic data.
Yes. If the SIP message contains a body with Content-Type: application/sdp, the parser isolates it. By enabling the "Parse SDP" toggle, it clearly separates the media layer from the signaling layer, making it easier to copy or inspect codec information.
The parser follows RFC specifications for header folding. If a SIP header continues onto the next line (starting with a space or tab), the tool will automatically unfold and concatenate it into a single, valid key-value pair.
SIP strictly requires CRLF (\r\n) as line terminators. However, logs copied from terminals or text editors often convert these to LF (\n). The normalize feature automatically corrects formatting inconsistencies so the message can be parsed flawlessly regardless of its origin.