SIP.US offers basic configuration guides for common SIP devices, but cannot offer support for the vast number of devices on the market. SIP.US is also not a managed services provider, so our Support team also cannot provide direct support for configuring customer equipment. If we do not have setup documentation for your PBX or phone, please try to find these configuration settings on your system. Most systems require the basic settings below:
Registration
You will need to configure the SIP REGISTER packet headers to provide us with the credentials to register the SIP trunk to our gateways. Associate the following common terms to our credentials.
“SIP Authentication ID/Username” - Add your SIP.US SIP trunk number to the User ID field in your device interface. To locate the SIP trunk number, go to the customer portal and hover over the SIP Trunking menu and choose the SIP Trunks submenu option. The page will display all SIP trunks on the account.
“SIP Password/Secret/Credentials” - Enter the credentials found in the "Password" field of the SIP.US customer portal into this field in the device interface.
“Outbound Proxy/Domain/Gateway Host/SIP Server” - Enter gw1.sip.us in as the primary gateway and contact SIP.US on port 5060.
You will also need to implement whitelisting for our redundant gateways and ensure the device is able to accept all SIP traffic from our gateways gw1.sip.us, gw2.sip.us, gw4.sip.us, and gw5.sip.us. Review this article on Interconnecting with SIP.US for more information.
Note: See our SIP Trunk Registration Status guide to check your registrations and troubleshoot.
Inbound Routing
Setup procedures vary per device make and model, so SIP.US can only provide how it delivers inbound calls so the device can be configured accordingly. Inbound call INVITE headers are delivered in the following formats by default:
- FROM: 10-digit format (NPANXXXXXX)
- TO: 11-digit format (1NPANXXXXXX)
Note: SIP.US applies an ANI Strip value of 2 to the FROM header for most numbers to deliver a 10-digit format. If you need to modify the FROM header, go to the DID settings of the number you would like to modify and set the ANI Strip to 0. You can find this setting in the customer portal by navigating to the expandable SIP Trunking menu option and choosing Telephone Numbers. This will load a page with all DIDs on your account. Click the pencil edit icon next to the relevant DID and an option table will load with the ANI Strip setting.
Outbound Routing
A basic explanation is provided in this guide. See our separate guide on Setting Up Outbound Calling for additional details.
SIP.US requires that you send 11-digits for all North American outbound calling, starting with the 1 for the country code. International calls should begin with the country code (strip the 011 from what you send in the TO header to SIP.US).
Additionally, you will need to ensure that you program a legitimate CID in the FROM header of the call INVITE to comply with STIR/SHAKEN regulations.
- FROM: 10 or 11-digit format: 1NPANXXXXXX, NPANXXXXXX
Examples: 8005669810, 18005669810
- TO: 11-digit format: 1NPANXXXXXX
Examples: 18005669810 (North American), 442039911100 (International)
After the outbound route is set with a dialing pattern, try calling a number (some systems require a reboot for changes to take effect).
E911 Setup
In order to comply with E911 requirements, you will need to acquire an Enhanced DID from SIP.US and use it as the CID whenever placing outbound calls to emergency services. Once you purchase the Enhanced DID or convert your existing Standard DID to Enhanced, you can click the pencil edit icon to add geolocation address info. If you need to test your E911 setup, dial 933 for the E911 testing service.
Audio Codecs
Ensure that your system uses the G.711-ulaw and the optional g.711-alaw codec.
You also have the option to add the G.729 codec. If your PBX and the receiving destination support it, the codec will be used.
Please open a Support ticket with support@sip.us if you need additional assistance with troubleshooting your device configuration or have further questions about the setup process.
Comments