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
| Your question | Task area | Page |
|---|---|---|
| How do I configure inbound trunk identification and authentication? | Administer | Inbound trunk controls |
| How do I stop new calls on one trunk during maintenance? | Administer | Trunk maintenance |
| 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 |
| How do I configure call transfers and their SIP headers? | Use Delphi | Call transfer |
| How do I find signaling captures and trunk health records? | Operate | SIP log reference |
| How do I operate, drain or restart the SIP edge? | Operate | Telephony edge |
| How do I run and troubleshoot the call runtime and media server? | Operate | Voice services |
For rule fields, matching conditions, save/activation and scope limits, use SIP header rules.
Routing, causes, and diagnostic headers
Start with Configure SIP trunks and routing 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. For a new peer connection, use the consolidated SIP signaling and media reference. It states the configured behavior for methods, responses generated by the edge, TLS and certificate checks, timers, codecs and DTMF, SDP and media security, called-number format, NAT addresses and the specifications it relies on.
That reference also lists its limits, such as RTCP port behavior and the negotiated cipher suite, and the call-quality values the reference deployment records. Test the requirements with the actual peer before you rely on them.
Move from diagnosis to configuration
If an inbound call matches an unexpected trunk, check inbound identification before you change capture settings. For an outbound routing question, use outbound trunks and pools. To interpret the call evidence, return to SIP diagnostics.
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.
Related
- SIP signaling and media reference — to agree transport, codec and NAT requirements with a new peer
- Configure SIP trunks and routing — to change the trunk or number configuration behind a call
- Diagnose SIP routing and termination — to trace a failed call back to its cause