|
If all of your sites are VPN'd together and subnet-to-subnet
communication between sites is transparent over the VPN connection then
there should be no need to be messing with the SIP packets in the
firewall. That document is the framework for a fault resistant sipX setup. While the setup you have outlines will work just fine, if one of your site links goes down then your phones will too. With a redundant setup like the one outlined in the DNS document if a site link goes down users will still be able to perform basic calling scenarios and dial 911, which in most cases is very important. My suggestion is to buy an FXO gateway for each location, set up the emergency dial rule with location based settings for each FXO gateway and see if you can get the local telco to install a 911 only phone line for cheap. In my case I have to pay for a full local line every month per location (upwards of $45 a month) but it has proven worth it's salt to have a secondary server and FXO gateway when there was actually a situation where the network was down to the site and there was a medical emergency. You can still keep the main installation in the datacenter, but I'd recommend putting small inexpensive secondary servers in place for redundancy. Out of curiosity how many extensions are you running at each site, and how much bandwidth do you have between your sites? Nathan Nieblas wrote: Based on that DNS document, my assumption is that I should have a local sipX box at each location rather than a cluster residing in the datacenter? Polycom's are on 3.2.2, I will downgrade them to 3.1.3c and see what happens. All phones are showing up registered. What I mean by SIP inspection is that the firewall is essentially handling the SIP protocol for translation sanity (since it's being NAT'd) and security.-----Original Message----- From: Josh Patten [mailto:[email protected]] Sent: Monday, January 04, 2010 8:21 PM To: Nathan Nieblas Cc: [email protected] Subject: Re: [sipx-users] multi site deployment http://wiki.sipfoundry.org/display/xecsuserV4r0/Setting+up+BIND+with+loc ation+based+views+for+sipX this may be helpful for you to implement as it creates a much more redundant setup As far as the other issues you are experiencing, make sure your Polycom phones are on a firmware revision no later than 3.1.3c. 3.2 and up has known issues with sipX and should be avoided until sipX version 4.2 is released. Also, are all of your phones showing up in the registration table? What do you mean by "SIP injection"? sipX and sipXbridge generally work best when the SIP messaging isn't messed with by a third party product. Nathan Nieblas wrote: |
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
