The purpose of this document is to provide an overview of what is required prior to configuring the WIN-911 VoIP notifier.
The first 3 minutes discuss SIP and PBX requirements and the remainder of the video discusses the configuration of WIN-911.
The VoIP Configuration Process https://www.youtube.com/watch?v=P5wWUN1Iikg&feature=youtu.be
Will the WIN-911 Technical Support configure my PBX or SIP server for us?
No, the WIN-911 technical support is not responsible for configuring the PBX or SIP Server. WIN-911 acts as a softphone (software phone), and the PBX or SIP server should be fully configured and functional prior to attempting to connect to WIN-911. The configuration of the PBX or SIP server is to be configured by an IT or voice expert.
Who should I involve during the configuration process?
Configuring a VoIP system will require a coordinated effort between the company's voice network experts (often the IT department) and the party responsible for installing WIN-911. It is strongly recommended to engage your voice network experts early in the process.
Network information required and best practices for SQL Server and IIS
When configuring WIN-911, you will need to gather the necessary information to connect to the SIP server. Typically, you will need the SIP account username and password, server address, SIP port (usually 5060), and RTP port range.
The following information should be shared with the IT department or voice experts to understand the security requirements and recommended ports. https://win911na.blob.core.windows.net/files/Products/WIN-911/3.17.5/Security_Best_Practices.pdf
PBX and SIP requirements
WIN-911 functions as a VoIP softphone (software phone) which requires a SIP compatible VoIP server. Before deploying WIN-911 you will need to check on the availability of a SIP compatible VoIP server. Most internal PBX systems support SIP, but you will need to check with the appropriate IT team to confirm compatibility with 3rd party SIP softphones. Your IT team will need to create a SIP endpoint/extension/account for WIN-911. For more information on softphones, please review http://www.voip-sip-sdk.com/p_315-voip-sip-softphone-voip.html
If an internal PBX is not available, there are many internet-based SIP options available. Please know this is not part of WIN-911 but your VoIP provider
Once you have confirmed the availability of a SIP VoIP/PBX server, you will need to confirm WIN-911 will have network access to the server. When using an internal VoIP/PBX server, they're usually located on a dedicated voice network which means the IT team will need to allow access from the WIN-911 system to voice network to facilitate the connection. If you are using an internet-facing SIP service, the IT team will need to allow access to the appropriate SIP server.
What PBX or SIP are supported?
The VoIP system will either a PBX or a SIP provider, some of which were listed on our spec sheet you found. If your system is not listed doesn't mean it won't work, it just means we haven't tested it through QA (since there are so many). If you have a choice in your system, we recommend to customers SIP.US. https://www.sip.us/
WIN-911 System requirements: https://win911na.blob.core.windows.net/files/Products/WIN-911/3.18.17/WIN-911-SystemRequirements.pdf
Will you need to call into the WIN-911 system?
If your operators/users need to call into the WIN-911 system to perform alarm or report request or acknowledgements, be sure to let your IT team know so they can allow for it. Occasionally an account is created with no inbound access for calls into the system. If you are using an internet-facing SIP service, this requires attaching a phone number to your SIP trunk which is typically an add-on feature.
The WIN-911 User Manual will discuss in detail what is required to configure the WIN-911 portion of VoIP.
If further assistance is required, please submit a support ticket using the WIN-911 support portal.