Administrator
发布于 2026-11-16 / 3 阅读
0
0

Tracing PRACK When FreeSWITCH Keeps Receiving 183

English
中文

An outbound call has no audible announcement, while the carrier repeatedly sends 183 Session Progress. If those responses have the same RSeq and require 100rel, check whether the reliable provisional response was acknowledged. Trace both the carrier and agent legs of FreeSWITCH, starting where the 183 is repeated.

Check whether 183 requires acknowledgment

RFC 3262 uses Require: 100rel and RSeq on a reliable provisional response. Supported: 100rel on INVITE advertises a capability. Check what the responder actually sends. A normal 183 can carry SDP or omit it. The status code and presence of SDP do not establish whether PRACK is required.

On the same leg, match Call-ID and both tags, then compare CSeq and RSeq. A 183 with CSeq: 21 INVITE and RSeq: 310 needs a PRACK with RAck: 310 21 INVITE. PRACK has its own CSeq, whose method is PRACK. A 200 for PRACK confirms receipt of the acknowledgment. Check the final response to the original INVITE for the call result.

Check three points if 183 repeats

  • No PRACK. Verify that the capture covers the receiver. If it received a reliable 183 and sent no PRACK, inspect the active profile and SBC support for 100rel. FreeSWITCH handles signaling separately on each leg. A PRACK on the agent side does not establish that the carrier received one.
  • PRACK with no successful response. Compare RAck with the original RSeq and CSeq and check the destination. If the peer returns 481, verify whether a matching provisional response remains outstanding in that dialog. If 183 is still retransmitted, distinguish a missing PRACK, a mismatch, and a reply that did not get back.
  • Successful PRACK, missing announcement. Check SDP negotiation and whether early RTP reached the side that should hear the announcement. Acknowledgment and audible media require separate checks.

Retest on a carrier test route

Keep a redacted trace of the failed call and repeat it on a test route. Record the first reliable 183, its PRACK, the PRACK response, and the final INVITE response. Note what the caller actually hears. If only one trunk requires 100rel, test that specific route and compare with a working one.

The FreeSWITCH v1.11.3 vanilla internal profile shows enable-100rel commented out and includes a stability note. Before changing a profile, confirm the peer requirement and your package version. Test ring-no-answer, answer, and cancellation in isolation and restore the previous configuration if validation fails. This procedure was checked against the specification and versioned template without a live test.

Sources


评论