Hey there my loyal readers. It has been a long time since I last posted. Last spring I wrote about the Microsoft Response Point VoIP PBX. Generally, I have been pretty pleased with the unit. Like any other VoIP, the unit does require a well managed network. I have seen some issues where the network is lacking a professional polish. If the network is very jittery or has a poor design, then voice quality does suffer. Besides these obvious pre-requisites to smooth operations, it has been simple to deploy and has a great feature set.
Back in April at the SMB Summit, the Response Point team from Microsoft indicated that with Service Pack 1 there would be SIP trunking available rather than just a PTSN (copper) gateway for external true VoIP access.
One of my installations with copper lines had decided to relocate. Their phone provider could no longer service their voice needs. I looked at the choices and since they had the Response System already installed and working, it seemed like going SIP was worth looking into. The services offered from the approved list vary quite a bit. NGT seemed to be the most plugged of the Microsoft SIP partners. I went ahead and set up myself as a dealer and had everything signed, sealed, and ready to go. To my dismay, NGT had to back out of the order because they could not provide E911 service to the area my customer was moving to. This happened with only a week left before the move.
Needless to say, I really had to scramble if I was going to make this happen and save face with my customer. Just as if God's was listening, I received an email from the Response Point Team. It mentioned that Bandwidth.com was now certified to work with the Response Point PBX. I gave them a call and they confirmed that they were ready for Response Point and had FCC compliant E911 coverage at the location my client was moving to.
There is a caveat to the hooking up the Response Point or any other VoIP PBX to established SIP providers. They want to see a gateway on your Internet circuit that they know and recommend. There are two reasons they have this requirement. The first is that the SIP providers want to have a demarcation point ahead of your network so they are able to troubleshoot voice quality issues. The second is it is an absolute requirement that a gateway device is doing bandwidth-shaping to give enough dedicated space on the WAN circuit to voice calls. NGT and Bandwidth.com both use and recommend the Edgewater Edgemarc. The device is going to add about $395.00 to the total cost of the project but it allows the SIP providers to look at the device and see MOS scores which are a sure measure on the voice quality of the connection.
The problem most will see right away is that you already have a firewall and do not want another one in line forcing dual NAT. The good news is that there is a simple configuration that works and will keep all your data moving out an existing firewall that does a better job at robust security. The trick is Proxy ARP. It allows you to take a single IP and assign it to your SIP trunk. You can then take the rest of your IP's and proxy them in their public format directly to whatever your primary firewall solution is. The Edgemarc is still the first device in line and it has the ability to shape your data as needed to provide crystal clear voice over the Internet.
Now, let's get back to my recent conversion scenario. The project went pretty smooth and Bandwidth.com did a great job getting the provisioning complete in time. However, I was to be the first live activation of a Response Point PBX for Bandwidth.com and some problems did follow. Many IP PBX's, such as Response Point, use registration as the methodology to notify the SIP provider that the unit is there and ready to receive calls. Bandwidth.com does not depend on registration and the only way to get Bandwidth.com set up as the SIP provider for a Response Point system is to set-up registration. Watch for a future posting that goes into more details on exactly how this works and how it must be setup on both the Response Point and at Bandwidth.com. After activating the SIP trunk, I was not getting consistent voice service. My client called me as I was walking down the jet ramp on my Chicago flight to Seattle for SMB Nation. I was able get the calls forwarded right away before takeoff. Once in Seattle I call my dedicated reseller team and they hooked me up with Shawn Starler. He stayed on the phone with me way past his normal end of shift. He figured out that they had a problem on their end and once the new process for a Response Point was put in place the circuit came right up and worked great. It is so fast you do not even get a ring when you call in the system. It is picked up by the auto-attendant instantly.
I am really happy to see the Response Point system growing as rapidly as it is. It looks like it will soon grow beyond the initial limits of 50 to 75 users. I will be posting more about Response Point soon. We have decided to become Response Point Specialist and go all in on the product for our customers. Stay tuned for more. If you are looking for SIP trunks or more bandwidth, I am highly recommending Bandwidth.com. I encourage any of my readers to contact me for more information on getting setup with Bandwidth.com. I will be glad to help. Again stay tuned for more interesting stuff now that I am back on the wagon and committed to at least a couple of articles a week.
Thanks for visiting!
Posts
No comments:
Post a Comment