Difference between revisions of "SIP Provider"
(8 intermediate revisions by the same user not shown) | |||
Line 11: | Line 11: | ||
=== Configurations on IPitomy's support site: === | === Configurations on IPitomy's support site: === | ||
+ | |||
+ | [[IPitomy SIP Trunk Configuration]] | ||
[http://wiki.ipitomy.com/images/0/0e/AccessLineSIPConfig.pdf Access Line] | [http://wiki.ipitomy.com/images/0/0e/AccessLineSIPConfig.pdf Access Line] | ||
Line 21: | Line 23: | ||
*NOTE Can Reinvite needs to be set to NO if the Cbeyond trunk has one way audio. If the user needs to have additional remote SIP (phones or provider) Cbeyond needs to create an Object Group to allow those alternate SIP entities to pass through the IAD. | *NOTE Can Reinvite needs to be set to NO if the Cbeyond trunk has one way audio. If the user needs to have additional remote SIP (phones or provider) Cbeyond needs to create an Object Group to allow those alternate SIP entities to pass through the IAD. | ||
+ | |||
+ | [[Charter]] | ||
+ | |||
+ | [[Empire Access]] | ||
[[Fathomvoice]] | [[Fathomvoice]] | ||
Line 27: | Line 33: | ||
[[FlowRoute]] | [[FlowRoute]] | ||
+ | |||
+ | [[Nextiva]] | ||
[[Hotwire]] | [[Hotwire]] | ||
Line 41: | Line 49: | ||
[[NexVortex]] | [[NexVortex]] | ||
+ | |||
+ | [[Time Warner]] | ||
[[Unlimitel]] | [[Unlimitel]] |
Latest revision as of 13:08, 9 August 2017
SIP Providers are easy to add and to edit. We have a growing list of providers that we've tested for interoperability and posted the configurations. As we migrate these to the wiki - all new testing will be wiki-posted. All previous posts will remain in their previous location (available here via link). IMPORTANT: see the Access Control List note for all providers
- Need a number to test DTMF, try calling 804-222-1111. It will read back each DTMF digit that you dial.
SIP Provider - Editing and Adding
Providers
Configurations on IPitomy's support site:
IPitomy SIP Trunk Configuration
- NOTE Can Reinvite needs to be set to NO if the Cbeyond trunk has one way audio. If the user needs to have additional remote SIP (phones or provider) Cbeyond needs to create an Object Group to allow those alternate SIP entities to pass through the IAD.
Tech Bulletin 2011-002 Windstream.pdf
Vintalk/ESI IP Bound Config Guide.pdf
- Note: If you do not have a static IP address, you should go to dyndns.org and create a domain that will resolve to the PBX site IP address. Let Vintalk know you will be using a dyndns domain, and in the SIP Provider configuration, set the From Domain to your dyndns domain.
Vintalk/ESI Registration Method
- Note: You may not be able to force Outbound CID via this method. We recommend you use the IP Bound method in the PDF guide above whenever possible.
Access Control List note for all Providers
IPitomy's application includes an Access Control List for lock-down security. This ACL must be open to the Host of the SIP service being deployed. Please follow the instructions below for ALL SIP Providers that are integrated onto the IPitomy. If your implementation of a SIP Provider has failed look into the ACL settings to assure that the provider has not been restricted from access.
NOTE: Using Load Recommended Defaults will overwrite any previously input parameters that are considered unneeded for the primary PBX application. If there are settings in ACL that you wish to retain you should not use the Load Recommended Defaults button.
Steps/Considerations:
- Assuming that the SIP Provider is being added to an existing system, the Local Network and Subnet Masks should already be programmed. If this is a new installation, input these basic network settings as required in PBX Setup / SIP Setup.
- External IP Address at the WAN interface of the router should be known and is likely already set. If not, set it too in PBX Setup / SIP Setup.
- Make sure that all data parameters are set in System / Networking.
- Navigate to System / Access Control - Access Control List (button)
- If there is no Access Control List you can create one easily using the Load Recommended Defaults button (read the warnings on this page)
- If there is no SIP "Service Rule" - there is no SIP service access control. (You can stop here if you don't want to create one... if there is no rule for SIP - all SIP traffic will be allowed.)
- If there is a SIP "Service Rule":
- Confirm that the rule type is Allow or Deny
- An Allow list is indicated under the column header "Rules" as "DROP ALL EXCEPT"
- This means that only those on the list will be allowed all others will be dropped.
- This is the usual format for Access Control Lists and as assumed for the remaining steps
- A Deny list is indicated under the column header "Rules" as "ACCEPT ALL EXCEPT"
- This means that only those listed will be dropped
- If your list is a Deny list and your SIP Provider is not on the list it will be allowed.
- An Allow list is indicated under the column header "Rules" as "DROP ALL EXCEPT"
- (Assuming Allow List) You must add the new SIP Provider Host to the list.
- This can be the DNS or IP Address.
- In the table "Add New Rule", select the Service to which the rule will be applied "SIP"
- Then in the Host box provided input the IP Address of the host
- You may include a qualifier to restrict the range of IP Addresses to only the valid bits of the IP Address using CIDR notation ("x.x.x.x/<cidr>)
- Click the button "Create Rule" to add the new rule to the list.
- Click Apply Changes
- Confirm that the rule type is Allow or Deny
Your SIP Provider is now on the Allow List and will be allowed to connect with the PBX. If all other interface settings in the SIP Provider programming are correct, your SIP service should be functional.
Load Recommended Defaults
Access Control can most easily be accomplished using Load Recommended Defaults. However this IPitomy PBX Wizard takes into account only those data parameters associated to core PBX functionality. It utilizes the data from PBX Setup/SIP Setup - Local Networks and Subnet Masks and External IP to derive the contents necessary for PBX functionality.