FamousTec

Carrier · Cutover documentation

SIP Carrier Handoff Doc

Generate a clean, carrier-ready SIP handoff document: signaling, codec, DTMF, CLIP/PAI, keepalive, E911 records, cutover test plan. The doc your carrier's engineer will actually thank you for.

Every SIP trunk cutover fights the same back-and-forth: "send us SDP", "what's your PAI?", "is that CUBE behind NAT?". This tool produces the one-pager that answers everything up front.

How to interpret the output

The generated document has standardized sections: network information, SIP signaling, media, DTMF, CLIP/PAI policy, keepalive, DID inventory, E911 ERLs, test plan, and go-live checklist. Copy it into your carrier's order form or attach as PDF.

Deep dive — the handoff that actually works

The two most-debated items on any handoff: CLIP/PAI and keepalive. Most carriers prefer P-Asserted-Identity with From header mirroring for CLID. Keepalive by SIP OPTIONS is universal; REGISTER is only used for provider-registering trunks (common in SMB, rare in enterprise).

Why trust this tool

Template assembled from handoff docs I've sent to every major carrier for the last 10 years.

FAQ

Do I need to send SDP?

Yes — sample SDP is appreciated. The tool includes a placeholder you fill in post-install with a real pcap sample.

What about T.38 fax?

Mention it explicitly. Some carriers disable T.38 by default; others require separate DID blocks for fax.

Worked examples

CUBE behind ASA, Intermedia trunk

SBC public 203.0.113.10, TLS+SRTP, RFC 2833 DTMF, PAI for CLID, OPTIONS keepalive 60s, 3 sites with 100-number blocks each, E911 ERL per floor.

Webex Calling Cloud Connect with Lumen

SBC pair at two regions. Lumen gateway on their side, Webex MME on the other. Doc outlines IP ranges, auth token, and survivability.

References

Want this report by email?