SIP and call handling
Choose the question you need to answer before opening a configuration or logging reference.
Choose a starting point
On narrow screens, scroll the diagram horizontally to read it.
For trunks, pools and number assignments, use Configure SIP routing. For reusable header changes, use Configure SIP header rules. For a failure, start with SIP diagnostics, then follow its configuration or termination-reference links as the evidence requires. This diagram maps documentation tasks, not the network path of a call.
Find the right instructions
Start with the rebuilt task guide. Historical guides remain available for material still under review.
| Your question | Task area | Published guide |
|---|---|---|
| How do I configure inbound trunk identification and authentication? | Administer | Inbound trunk controls |
| How do I configure outbound routing? | Administer | Outbound selection and resources |
| Where are transfer, hangup, and DTMF flow controls described? | Use Delphi | Flow Designer nodes |
| Where are transfer and SIP header policies described? | Administer | Call transfer behavior |
| How do I inspect signaling and interpret capture data? | Operate | SIP signaling reference |
| How do I inspect trunk health? | Operate | SIP trunk log reference |
For rule fields, matching conditions, save/activation and scope limits, use SIP header rules.
Routing, causes, and diagnostic headers
Start with Check SIP routing configuration to distinguish trunk identification from authentication, and number routing from literal SIP URI routing.
The SIP termination reference defines the platform cause mapping and default optional-header limits. A SIP cause inside a Reason header is distinct from the response status of the carrying message.
For an incident, follow SIP diagnostics: identify the responding component, inspect the relevant routing or termination evidence, return to the appropriate configuration, and verify the resulting call behavior.
Interoperability requirements and limits
A signaling capture reference does not establish a complete support matrix. The consolidated customer-facing reference is still under review, including SIP methods and errors, RFC support, TLS and cipher suites, certificate validation, codecs and transcoding, DTMF, headers, number formats, SDP, RTCP, NAT behavior, transfers, and known limitations.
This preview does not assert support or lack of support for an item simply because it is absent from a guide. Confirm the requirements for the deployed release before relying on an interoperability claim.
For a new peer connection, use the SIP signaling and media reference to distinguish configured transport/media behavior from the tests needed for your integration.
Move from diagnosis to configuration
If an inbound call is associated with an unexpected trunk, consult the inbound configuration guide before changing capture settings. For an outbound routing question, consult the egress guide. Return to the signaling reference to interpret the relevant call evidence.
If the behavior instead concerns an action during a flow, continue with Use Delphi.
For keypad input that completes too early, times out or leaves an old value, read DTMF collection in SIP flows and its linked diagnosis procedure.