Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Teleworker no audio to second 3300 over vpn connection

Status
Not open for further replies.

southernglove

IS-IT--Management
Feb 16, 2012
1
US
Hey guys i am a newbie on the site and to mitel. Here is some background. My location has a mitel 3300 CXI with intergrated TW server. I have the TW server sitting in the DMZ in server mode. everything works fine. The TW client has two audio for all calls inside and out to the the local 3300. I have a second site that has its on 3300 and we are connected via a sonicwall to sonciwall VPN connection. The 3300's are connected so we can do ext dial between sites and that works fine. Here is the problem... when the TW client dials and ext to the remote site there is only one way audio. He hears them... but they cannot hear him... one way audio.

Any help would be greatly appriciated.
David
 
Does the teleworker server have a route to the other site?

X-way audio is usually a routing issue.

From the CLI: Manage Local Networks > Show local networks.

From the GUI: Security > Local Networks

If the subnet which your phones reside on at the other site is not listed here, the TW server won't know the next hop to send the audio stream from your TW sets. The next gateway IP address would be the private IP of your Sonicwall.

The TW user hears audio because the default gateway is provided to the sets at the other site via DHCP. I assume that GW is the other Sonicwall.
 
I Agree with bribob. Make sure your TW has the remote subnet defined and it knows where to send things.

Also, assuming your sonicwall is a firewall/router, make sure you have routes/policies to allow traffic:

from dmz to local lan where main PBX is at (both ways)
from dmz to remote lan where you have the remote PBX (both ways)

At the remote sonicwall, make sure you have a route and a policy to send/allow traffic from the lan to the dmz subnet on the other sonicwall.

Also, remote PBX needs to have a policy that allows traffic to the internet (at least the voice ports).

Make sure everything can and is allowed to communicate with every possible subnet including the dmz,also to the internet.

It will work, I have a similar scenario with Fortigate Firewalls, tw on the dmz, and 12 other PBXs conected over vpn.

full audio

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top