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!

Avaya 9600 phones over VPN with site to site Sonicwalls 1

Status
Not open for further replies.

Gus63

Technical User
Mar 16, 2004
156
US
IPO 500v2 8.1.69

We have a local system (192.168.10.x/24)
We have a Sonicwall 220 setup and working with a tunnel to another tz205 on the other side. (192.168.11.x)/24

All traffic goes through, in that printers, and computers work fine. We plug a phone into the local site (Main) and the phone will get an address (10.x) When we take the phone to the remote site it does get an ip address (11.x) and the phone system will see the phone. However, it will not send the information to the phone. There is no traffic related to the phone systems IP address being blocked, or otherwise dropped by either sonicwall. The logfiles of both sonicwalls do not show any traffic being blocked.

We can ping the LOCAL gateway (10.1) but not the remote gateway FROM the phone system (IP Office System Status program 8.1.69)
IP Route is set to 0.0.0.0 mask 0.0.0.0 gateway 192.168.10.1 destination LAN1
The computer hosting the IP Office can ping the remote gateway.

We have tried different phone cables, and known working drop locations to insure the issue was not a bad cable.

Is there something simple being over looked? Tech support does not have an idea. There must be someone else using a VPN Tunnel for a remote office setup with a 9600 Avaya phone? I only mention the sonicwalls, in case someone knows of a switch or bug with them. I believe the solution would apply to any VPN tunnel.

Here is what system Monitor is showing for H.323:

1043272mS H323Evt: IRCheckTimer: GRQ record deleted (user name=; extn-num=220)
1043272mS H323Evt: IRCheckTimer: GRQ record deleted (user name=; extn-num=220)
1043272mS H323Evt: IRCheckTimer: GRQ record deleted (user name=; extn-num=220)
1043272mS H323Evt: IRCheckTimer: GRQ record deleted (user name=; extn-num=220)
1043272mS H323Evt: IRCheckTimer: GRQ record deleted (user name=; extn-num=220)
1043272mS H323Evt: IRCheckTimer: GRQ record deleted (user name=; extn-num=220)
1043272mS H323Evt: IRCheckTimer: GRQ record deleted (user name=; extn-num=220)
1043272mS H323Evt: IRCheckTimer: GRQ record deleted (user name=; extn-num=220)
1043272mS H323Evt: IRCheckTimer: GRQ record deleted (user name=; extn-num=220)
1043273mS H323Evt: IRCheckTimer: GRQ record deleted (user name=; extn-num=220)
1049965mS H323Evt: Recv GRQ from c0a8194d
1049965mS H323Evt: e_H225_AliasAddress_dialedDigits alias
1049965mS H323Evt: found number <220>
1055372mS H323Evt: Recv GRQ from c0a8194d
1055373mS H323Evt: e_H225_AliasAddress_dialedDigits alias
1055373mS H323Evt: found number <220>

 
This is 100% the Sonicwalls, they are renowned for interfering with such things, that fact the phones work locally and not remote tells you the same, the handsets/system don't know what forms the link to behave any differently :)

 
Be sure H.323 transformations is unticked on both Sonicwalls (VoIP section of configuration). Z
 
I have a similar setup working (albeit with a NSA2400 at main site and Draytek's at remote) but a couple of differences to what you describe.

Firstly, our remote phones are given static IP addresses and then you provide the IP address of the IPO etc.

Secondly, the IP Routes we have are specific to each remote tunnel, so instead of 0.0.0.0/0.0.0.0 you would have 192.168.11.0/255.255.255.0 and then 192.168.10.1 as the gateway.
 
Just to follow up on this. I found that all phones(the ones on the far end 192.168.11.X) on that network needed to be cleared out and the restarted. We had setup the phones here at the office (192.168.10.X) and sent them out to the far end (even thou we put in 0.0.0.0 as address, sub net and router) but the phones kept some info inside them that stopped them from joining that network.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top