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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

9600 Series H323 Remote Extensions

Status
Not open for further replies.

StatusCue

Technical User
Dec 31, 2009
45
US
I'm having problems getting my remote 9611G handset to work. On the IP Office monitor I repeatedly get the following:

1056493mS H323Evt: Recv GRQ from 442d6fbc
1056494mS H323Evt: e_H225_AliasAddress_dialedDigits alias
1056494mS H323Evt: found number <252>

If I look at the traffic monitor on my firewall I notice that the IP Office is trying t communicate with the remote 9611G using its internal address from the users home router. I'll use the following example IP addresses to explain:

9611G Home Router Internal IP: 1.1.1.1
Users Home Router Public IP: 2.2.2.2
IP Office Company Public IP: 3.3.3.3
IP Office Company Internal IP: 4.4.4.4

The firewall shows the following:

2012-10-29 16:36:45 Allow 2.2.2.2 3.3.3.3 1719/udp 46504 1719 2-External-Cable 1-Trusted Allowed 352 56 (AnyIPOffice-00) proc_id="firewall" rc="100" dst_ip_nat="4.4.4.4" Traffic

2012-10-29 16:36:45 Allow 4.4.4.4 1.1.1.1 49305/udp 1719 49305 1-Trusted 2-External-Cable Allowed 137 98 (AnyIPOffice-00) proc_id="firewall" rc="100" Traffic

As you can see, when the IP Office tries to respond back to the phone it is trying to contact it using 1.1.1.1 but it should be using 2.2.2.2.

Any ideas how to get this working? The Firewall being used is a Watchguard XTM505. It appears that all traffic is passing through the firewall just fine but that the IP Office is just unaware of the correct IP address to reach the phone.
 
The watchguard can do h323 alg, turn it off. Add a stun server in the ipo you can use stunserver.org just ping the adrress and fill in the ip addres in the stunserver on lan 1 or 2 of the ipo. Depending on what lan your router is on. Then press the button run stun, wait for 5 min and it should come back with your public ip at the bottom. It should come back with restricted cone or full cone NAT.

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool )
______________________________________
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top