Administrator
发布于 2026-11-17 / 4 阅读
0
0

Where to Look When a FreeSWITCH Outbound Call Gets SIP 422

English
中文

An outbound contact-center call can receive SIP 422 from the trunk before the customer’s phone rings. Start with two values: the session interval proposed in the INVITE and the minimum returned with the response. Then look for a new transaction and check what changed. This walkthrough follows RFC 4028 and FreeSWITCH v1.11.3.

Find the leg that received the rejection

Organize the INVITE and its responses separately for the agent-facing and trunk-facing legs. In a typical bridge, FreeSWITCH handles separate SIP dialogs. Match the legs using timestamps, channel UUIDs, or an existing bridge association. Use Call-ID and CSeq within each leg.

A packet’s source shows which adjacent peer forwarded the 422. If that peer is an SBC, check its upstream trace to distinguish a locally generated response from a rejection it relayed. If FreeSWITCH generated the response toward the agent, identify the actual Sofia profile that accepted the request. The v1.11.3 implementation checks an incoming INVITE that has a Session-Expires value. When that value is below the configured minimum-session-expires, it returns 422 with a Min-SE header.

Make sure the retry was a new request

Consider a hypothetical INVITE with Session-Expires: 120 and a 422 carrying Min-SE: 300. Both values are in seconds. The 422 is a final response for that request. The originating side can retry. If a new INVITE appears, check that it belongs to the same call, carries a Min-SE of at least 300, and proposes a Session-Expires at least as large as its own Min-SE. Before a dialog exists, the retry uses the largest minimum received in 422 responses for that Call-ID.

If two INVITEs have the same CSeq, compare the branch in the top Via header. A retransmission of the same transaction does not demonstrate that the timer parameters were updated. If a new transaction offers enough time and still gets rejected, inspect the new Min-SE and compare the headers on either side of the SBC. If no new transaction appears, confirm you have the complete trace and check the behavior of the originating side.

Verify a refresh after the call connects

Check the agreed settings for that carrier connection before changing a profile. In FreeSWITCH, session-timeout controls the interval setting and minimum-session-expires represents the local minimum accepted. Raising the local inbound minimum alone does not establish that the next outbound INVITE meets the remote peer’s minimum. For deployments with several carrier routes, record the agreed values per route and test with the corresponding profile and a test number.

After a retry succeeds, check that leg’s 200 OK for the final Session-Expires and refresher. The uac and uas values identify who refreshes the session on that leg. Observe one expected UPDATE or re-INVITE and its successful response. A call that connects and later drops near the negotiated interval can be checked against that timeline. Treat RTP and two-way audio as separate observations. The 120 and 300 above are illustrative; use the agreed settings and your own trace.

References


评论