SIP peers for 911 service


Valeriu Senic


Click here to find out if your E911 endpoints are compliant with RAY BAUM’s Act

SIP peers

Currently, Bandwidth supports the provisioning of SIP peers with IP addresses only. Ranges must be separated, and DNS entries aren't supported. Although there's currently no limit on the overall number of IPs you may use to send 911 traffic, you can have a maximum of 128 per account (though there's no limit on the number of accounts you can have with us). To add a new SIP peer, please open a ticket with your Bandwidth Support Team.

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 one IP address needs to be supported across multiple accounts, we require the use of trunk IDs or prefixes. This means every 911 SIP INVITE Bandwidth receives from you 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 by using 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-AccountId: 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

Additional notes

  • Bandwidth doesn't support SIP with more than 6 characters prepended. 
  • If using P-Asserted-Identity, please make sure it's compliant with RFC 3325
  • For more information, please see our 911 integration guide.

Article is closed for comments.