Using I2050 through VPN problems

[johnatbarr]

My I2050 works fine on my Lan, but not at home through VPN.

I'm running 3.0 on a 61C with a Sig Server.
Laptop is XPpro on a 1.5 DSL with Netgear router.

While at home I VPN into my office and the phone comes up fine. When I try to dial out I get a dial tone and here it ringing. But as soon as someone answers I can no longer here. On some occasions they can here me but I can never hear them.

I did notice on I2050 diagnostics there was "No Value Assigned" in the Receive Stream.

Any help on where to start would be great.

 

[StanleySteamer]

I think it could be a NAT issue with your router.
I'm using an ITG card with version 3.1 so I'm a little older than you're setup. The newer software apparently has improvements for NAT operation.
Anyway, my i2050 works at home with my router port forwarding set to forward these ports to the static IP address of my PC.
4100
5100
5200 to 5247
One of those ports is for the voice receive.
Steamer

 

[I2007]

I'm sure this is a NAT issue as StanleySteamer said. NAT issues has been improved, but not befoure SS 4.0 software and rel.4.00 on the pbx. Allthough it has been improved in 4.0 there are still factors that has to be corrected in firewalls in order to make it work, and theese factors are almost the same for fixing the problem with 3.0 software.

i2007

 

[muttsnuts]

How is your IPSEC tunnel established? Is a client on the PC or is it the Netgear that's doing it? As previously mentioned it could be NAT. Some NAT impementations are a tad simplistic and are not necessarily H.323 aware. Firewall rulesets can also cause problems if they are not application savvy. Assuming your ipsec tunnel originates from your PC does it work if you establish the tunnel whilst connected to the corpaorate LAN? If it does. I'd try it again using a dial-up connection to an ISP (if they still exist!) as the address they'll assign (providing it's not AOL) will hopefully be a public one with no NAT. This way you'll be able to establish whether it's NAT that's causing you an issue or not. Assuming it works then NAT is causing you a problem, if it does it's a border security issue with your corporate VPN gateway/firewall. If it thinks endpoints are trying to establish UDP streams for no apparent reason ie. it doesn't understand H.245 signalling, then speech paths will not be established (this includes ringtones).

 

[muttsnuts]

Oops should read

snip.....

if it doesn't it's a border security issue with your corporate VPN gateway/firewall.

Apologies

 

[spanton]

I am having the same issue will the following changes. I am running Succession 1000m muti group, release 3.0. I have a user that is using the Contivity client on his laptop to connect back to the office via a contivity 1100. Sometimes he is able to hold a two way conversation fine and then two or three calls later the person he calls can hear him but he cannot hear them or both cannot hear each other. What could be causing this problem?

 

[MG2005]

half duplex converstaions or one way communication is almost always an IP routing issue