SIP Peers for 911 Service


Molly Katolas


Details are available in the Bandwidth 911 Implementation Guide


SIP Peers

Bandwidth supports the provisioning of SIP Peers with IP addresses only at this time. Ranges must be separated out, and DNS entries aren't supported. There is currently no limit on the amount of IPs that may be used to send 911 traffic. Provisioning of SIP Peers is completed by the Account Manager during the implementation process, and by the customer via the dashboard or my.bandwidth portal after implementation is complete.


Using Ports with SIP Peers

All 911 calls should be sent to Bandwidth via port 5060. The call may be sent from any port.


Using Trunk IDs with SIP Peers

In rare cases where there is the need to support one IP address across multiple accounts we require the use of trunk IDs or prefixes. This means every 911 SIP INVITE Bandwidth receives from the customer must be prefixed with a distinct alphanumeric sequence. We recommend 10 characters or less but any length is supported.

The preferred way to indicate a trunk id to Bandwidth is in the proprietary SIP header "X-Account-Id". An example with a trunk id of "abc123" would be:

INVITE sip:911@ SIP/2.0

From: <sip:3032288888@X.X.X.X:5060>;tag=9098.A419

...other SIP headers...

X-Account-Id: abc123

Alternatively, you can prepend the trunk ID to the SIP Request URI. An example INVITE for a 911 call with a trunk id of "abc123" would be:

INVITE sip:abc123911@ SIP/2.0

Article is closed for comments.