H323 IP Phone Registration

[SupportDude]

Hello,
Does anybody know, or even better have a capture, of an H323 IP Phone starting up and registering to the IP Office.
I would like to know exactly what the process should look like when bringing an H323 set online.
Using monitor I can see the .txt file downloaded and the f/w file loaded, but that's where it stops.


I have a site running 8.1.63 on the IPO.
No IP Phones local to the IPO network.

Customer has a remote site with 9611G sets.
The sets are configured statically with all the correct information.
Each site has a SonicWall (tz190 at the remote and tz200 at the main).
The SonicWalls have a nailed up site-to-site VPN tunnel between the two.
The following ports are open on the SonicWalls:
1718 UDP
1719 UDP
1720 UDP
5005 UDP
49152 - 53247 RTP/RTCP

I'm assuming we have end-to-end connectivity since the phones loads the .txt file and firmware, but stalls at "Discovering" the IP Office. I'm pretty sure it is an issue with the SonicWalls, but I would like to know how the H323 and IPO step through the registration process to assist in troubleshooting.


Any help appreciated!
TIA ...

-SD-

http://www.mysupportguy.net

 

[tlpeter]

Do you have an IProute in the IPO pointing to the remote network?


BAZINGA!

I'm not insane, my mother had me tested!

 

[SupportDude]

Thanks for the response!

I do not have a route pointing specifically to the remote network.
I do have a default route to locate the default gateway.

-SD-

http://www.mysupportguy.net

 

[SupportDude]

Another question came to mind ....
Since there is a VPN tunnel established between the sites via the SonicWalls, would I need to setup the 9611 as a VPN phone or a regular H323 phone?

Dazed and confused!

-SD-

http://www.mysupportguy.net

 

[rosenbaaron]

You should try permitting all traffic between the two tunnels. I have two sites that connect via site to site vpn and they can register just fine. Can you ping the Avaya system? It only needs to be a vpn phone if it is making its own vpn tunnel.

 

[SupportDude]

Thank-you rosenbaaron,
Yes, I can ping to the IP Office from the remote site.
I had assumed exactly what you explained about the VPN, but based on other posts I've read during my research I became a bit confused.

I'm in the process of reviewing the SonicWall configurations now.
They were installed and maintained by a different company.

-SD-

http://www.mysupportguy.net

 

[tlpeter]

When you have a site to site VPN then your phones should be normal H.323 phones.
You need to have an IProute to the remote network.

Exmaple

Site A

192.168.42.1 (IPO)
255.255.255.0 (Mask)
192.168.42.254 (Gateway)

Site B

192.168.43.x (phones)
255.255.255.0 (Mask)
192.168.43.254 (Gateway)

The IProute you need to have is:

192.168.43.0
255.255.255.0
192.168.42.254
Lan 1 or 2 (depends which one is used)

BAZINGA!

I'm not insane, my mother had me tested!

 

[SupportDude]

ISSUE SOLVED:

FYI ....
While reviewing the SonicWall at the remote site I was able to determine the packets from the 9611 phones to the IP Office were being dropped. I believe the drop code was 36 and the module ID was 21. Based on some documentation I found (thank God for Google!) I translated the code 36 to "based on a rule" and the module ID to "firewall module".
The firewall rules table did not contain any entries to block the discovery or registration ports.
But, on the Firewall>Advanced screen I found a checkbox, that was checked, named "Drop Source Routed IP Packets".
I cleared the checkbox and applied the change.
The H323 sets passed the discovery process and requested the extension and password.
The sets are now online and working great.

Hope this helps somebody in the future.

Thanks to all who posted tips!

@tlpeter - I did not have to add an additional route on the IPO. It appears to work fine with the default route I built.
0.0.0.0
0.0.0.0
192.168.42.254 (default gateway for IPO subnet)
Use LAN 1

If I notice any connectivity issues in the future, I'll keep this in mind as a possible necessary step.
Thank-you!

-SD-

http://www.mysupportguy.net

 

[tlpeter]

SupportDude, when you have 0.0.0.0 0.0.0.0 192.168.42.254 then you are OK indeed.
Nice problem solving by the way.


BAZINGA!

I'm not insane, my mother had me tested!