Link to home
Start Free TrialLog in
Avatar of Tyler Brooks
Tyler BrooksFlag for Canada

asked on

VOIP Setup through a Watchguard BOVPN

We are experimenting with deploying a VOIP system at a secondary office of one of our clients. This office is linked to their main network by a persistent VPN setup between their Watchguard routers. When we put a VOIP phone in place at the secondary office the phone is able to obtain a network address but cannot connect to the virtual PBX on the other side.

The main office is where their server (ad, dhcp, dns etc) is located on the 172.17.17.0 subnet and the secondary office basically consists of 10 or so workstations and a couple of networked printers. We have never had any issues with getting everything connecting across but we are admittedly fairly new to VOIP systems and virtual PBX.
Avatar of ArneLovius
ArneLovius
Flag of United Kingdom of Great Britain and Northern Ireland image

You have mentioned one subnet at the main office, is the VoIP system on the same subnet ? Or is this a hosted VoIP system ?

Are you configuring the phones manually, or from DHCP ?
Avatar of Tyler Brooks

ASKER

The phone is currently getting it's IP DHCP from the router at the secondary site. The VOIP server is on the same subnet as everything else at the the main office.
ASKER CERTIFIED SOLUTION
Avatar of ArneLovius
ArneLovius
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
We had been auto provisioning the system however when I look into the mechanics of how that process work I think that that is likely the culprit. I'll be going onsite tomorrow and will manually provision it to see if that resolves the issue.