Protocol scope and method
Paste one request or response start line per row. The checker recognizes common registration challenge and media setup sequences, not transaction timing.
Normalize start lines → classify request/response → compare common sequence patterns.
Diagnostic scenario
Paste a redacted chronological SIP exchange for one Call-ID. Check request-response pairing, CSeq methods, dialog tags and expected INVITE, ACK, BYE or MESSAGE transitions, then compare failures with transport retransmission and timeout logs.
How to interpret the result
The checker can identify missing or inconsistent visible steps but cannot infer packets absent from the capture or validate every SIP transaction rule. UDP retransmissions are expected and should not automatically be labeled duplicate business requests.
Input reference
- SIP start lines in order
- Example default: Sample input included
Common mistakes
- Using an unredacted production capture with vehicle, credential or network identifiers.
- Sorting messages by pasted order when capture timestamps differ.
- Treating a successfully parsed sample as standards compliance or interoperability proof.
Before using the result
- Confirm the protocol edition, transport framing and vendor profile before interpreting fields.
- Correlate transactions by branch, CSeq and response class.
- Keep a redacted known-good and known-bad sample as a regression pair.
Questions to check during diagnosis
Does the GB/T 28181 SIP Flow Checker leave my browser?
No application upload is used. Avoid putting sensitive production data in shareable URLs.
Is this a standards compliance test?
No. Confirm the edition and vendor profile with licensed documents and your target platform.
Offline diagnostic aid. Verify fields, version and vendor extensions before production use.