A student's open lab: learning and sharing, free for everyone.

SIP UniverseFree University

Home / Cloud voice and CCaaS SIP / Teams Direct Routing signaling

Teams Direct Routing signaling

Direct Routing uses the pstnhub proxies on 5061, a certified SBC, and a verified domain. Contact must be an FQDN.

Learn in 5 minutes

  1. Name the three signaling FQDNs and port 5061
  2. Require a verified domain and an FQDN Contact
  3. Remember that connection aliasing is unsupported

Visual

INVITE to the primary proxy · study drawing · cyphermonkeylabs.com SBCsip.pstnhub.microsoft.com INVITE 100 180 200

SVG HTML PNG

Checked against the plan and protocol articles.

Worked example

Check Contact and the proxy host Dissect the Direct Routing INVITE. Which host is in Contact?

    Vendor menus, ports, and license names change. Confirm before relying on a sentence that is not an RFC.

    Fault

    The proxy answers 403 Forbidden. The INVITE was sent to sip.pstnhub.microsoft.com on 5061 with Contact sip:sbc@203.0.113.20.

    The protocol article returns 403 when Contact is not an FQDN.

    Quiz

    Direct Routing signaling FQDNs include


    The signaling port is


    TLS for Direct Routing is


    A tenant domain for the trunk must be


    RFC 5923 connection aliasing on the Teams SIP proxy is


    An IP address in Contact produces


    Ecosystem

    Glossary, sister systems, and the integration seam for this room.

    Workforce management WFM forecasts volume and builds schedules. It consumes contact-center events. It does not parse Via headers. When a forecast is wrong, the SIP symptom is usually queue delay and 480 or carrier congestion, not a broken dialog ID.

    Glossary · Ecosystem map · Ports · Troubleshooting

    Sources and go deeper