Inbound SIP Trunk Requirements

These are the requirements to create an inbound SIP trunk (FROM Customer equipment TO Sharpen).

*For SIP calls made from Sharpen to customer endpoints see Outbound SIP Trunk Requirements

1. SIP endpoints (e.g. SBC or gateway)

   1. Customer provides between 1-3 publicly accessible IP addresses that Sharpen will accept inbound SIP calls from.

   2. Sharpen Inbound Gateway IP’s.  Where customers should send SIP calls - contact Strategic Services if you are unsure which IP list pertains to your company

      1. Main (reach out to devops team for up-to-date list)

         • FQDN (auto load balances) - http://us1-byo-inbound.sipvbx.com/

         • If you need or prefer to load the IP’s manually

           • 107.23.194.169

           • 107.23.101.107

           • 107.23.195.119

      2. Condo IZ1 (reach out to devops team for up-to-date list)

         • FQDN (auto load balances) - http://us1-byo-inbound.iz1.sharpen.cx/

         • If you need or prefer to load the IP’s manually

           • 18.204.61.135

           • 184.73.214.192

           • 54.157.9.182

2. Authentication

   1. Sharpen will whitelist the customer IP’s in step 1 on our inbound SBC’s

   2. Customer should whitelist the Sharpen IP’s from step 1 above

   3. (Contact Strategic Services if you wish to use PSK)

3. Ports opened on these IP addresses

   1. Customer should provide ports for their SIP and RTP traffic to Strategic Services also (if different from Sharpen default ports listed in point #3)

   2. Customer should provide expected max and avg call concurrency estimates to Sharpen

   3. Sharpen will use these ports for SIP to the customer

      1. TCP/UDP 5060 for SIP signalling (TLS not supported at this time)

      2. 10000-20000 UDP for voice traffic

4. Sharpen will accept voice in the G.711 codec (additional codec support like G.729, Opus, etc, are future roadmap items)

5. Customer owned phone number(s) provided to Sharpen

   1. Inbound Numbers from the customer SIP trunk will be manually configured by Sharpen in the “admin>inbound routes” container.  Customer will provide 10 digit numbers that will be sent in the SIP headers and that they wish to be routed via Sharpen Inbound Routes

   2. Customer should pass standard SIP information in their headers:

      1. Calling Party Number (CID/ ANI/Caller ID)

      2. DNIS (called number)

6. Routing Strategy

   1. Customer routing - Sharpen will accept inbound SIP calls from any of the customer IP’s listed in step 1, in any routing strategy (e.g. all calls from 1 active IP, or calls coming in any order from all IP’s)

   2. Sharpen side routing - Sharpen will accept SIP calls on all 3 Sharpen IP’s listed in step 1, in any order.

7. Routing of numbers will be controlled in Inbound Routes.  When new numbers are configured by Sharpen, they will appear in the customers inbound routes page and can be routed like Sharpen native VOICE lines.

   Open

   

Additional Inbound Notes:

• SIP trunks only accept inbound voice calls.  SMS/MMS and fax are not supported over SIP trunks.  For native functionality, consider having Sharpen port the numbers into your Sharpen account

• Certain functionality, like Q omnichannel SMS/MMS is not fully supported when using SIP trunks for voice. Limitations of SIP, customer configuration and customer telco vendors will affect native Sharpen functions. 

• In active/backup mode, if a remote IP fails, the caller will hear silence until the next backup IP is connected.  Once marked “offline” the previous active IP is not tried and calls proceed normally

• Changes to Trunk Groups (add, remove, re-order) can take a maximum of 15 minutes to take effect.  For expediency on normal calls, SIP trunk configurations are cached, with a refresh every 15m (based on when a call first hits the SIP trunk).  Depending on when during the cycle the change was saved, it will take effect from a few seconds to 15m.