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

getting 4620 IP phones to work over a vpn 2

Status
Not open for further replies.

ldylanfinch

IS-IT--Management
Mar 26, 2007
10
US
I have setup a VPN between two offices using netgear equipment in order to see if I can get a couple of 4620 IP phones to receive calls directed to them and dial other extensions. If I have the phone logging in, but am unable to make calls what is the likely cause? The phone actually acts like one does when there are no VCM's on the IP office unit. The system that I am connecting to works well and the VPN link is solid. Is there specific steps that need to be taken with the phone firmware or within the IP office in order to get this working? Has anyone done this successfully?


Thanks for your help,

Dylan Finch


 
the netgear 318 have a bug where the phones will not registar to the ipo. it will just say discover xxx.xxx.xxx.xxx i am not sure if this is your porbelm or not. also does the system have vcm in it. look in monitor and see if it says vcm=? sometimes if you miss a pin strange things will happen
 
The system has VCMs and it works great with many phones in the local office. That is why I am saying the the phone acts like it has no VCMs. It registers and logs in, but you cannot dial and have no dial tone once logged in. I am using a FVS124g and a FVS318. They both have the latest firmware.

I am wondering if additional settings might be required in the IP412 unit or if there is some other setting on the VPN.

Thanks,

Dylan Finch
I have set things to the specifications set forth in the AVAYA manual for VPN links for netgear.
 
so the settings are the same an all ip versions. make sure that the phone compression is set to a setting that is understood by the phone. i think the ipo lists a bunch of options but only 3 or 4 are supported by the phone.

ACA & ACS IPO Implementation
 
Essentially, my question is: will this realistically work with this hardware? Is it a question of configuration or capacity? I am going to deploy it with a CISCO 1841 and a PIX 506E in the actual site, but wanted to test it with this hardware first. Anyone have any experience doing this with specific boxes and know what steps I might be missing?

Thanks,

Dylan Finch

 
i have an ipo406 and i used sonic walls for my vpn hardware, but what i am essentially saying is that it should work as long as you can pass traffic through your netgears.

i had to enable QoS on my sonic walls for it to work but i do use this same setup for my house vpn.

did you create ip routes in your ip office?

in the ip routes section of manager you have to put in the reverse network of your vpn using the local gateway of where the ip office sits.
so if at home your network is 192.168.42.X/255.255.255.0
and at the office where the ip office unit sits is 10.100.2.X
then the ip route should look like this:
IP ADDRESS = 192.168.42.0
IP MASK = 255.255.255.0
GATEWAY IP = 10.100.2.254 ( or whatever the gateway is for main location )
DESTINATION = LAN1

And on the phone end for the ip settings, the call server should point to the ip office, the file server to the ip office, but the gateway and router are whatever your local addresses are.

and one little annoying feature that i turned off was under system> gatekeeper>
i disabled "auto create extn"

hope this helps, if not please post any other questions back on here, as im always doing remote setups through vpn's.






 
Well, I have followed the instructions exactly and still have the same scenario. A phone that logs in, but that cannot make calls and has no dialtone. I think that I will have to try other hardware. It's always fun diagnosing things like this.

If anyone has any other ideas then I would be much obliged, otherwise I will procure some more hardware in the next few days.

Dylan
 
you did say you use cisco pix ?

you need to do this :

no fixup protocol h323 h225 1720
no fixup protocol h323 ras 1718-1719


______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
Yes - I have just realized that the h323 filtering was my issue. Though I am still using the netgear hardware. This hardware isn't the best, but it is up and working. With the Pix and the 1841 I should have a much more stable connection up and working. Thanks for your help.

Dylan Finch
If anyone needs to know how to disable h323 filtering on the FVS124g let me know. It is kind of a weird method. It is not well documented.

 
I would definitely recommend replacing that FVS318 with an FVS114. The 114 is cheaper, and is stable. The fix Netgear did for the 318 that allows the phone to register is not stable, the phone will randomly unregister, sometimes even during a call. I had to swap out 20 of them, wasn't a fun situation. And I was running the latest firmware, Netgear themselves did the trade outs and acknowledged the issue.
 
Yes, I am noticing that with the 318. Have you had good luck with the 114's at your sites? I am installing cisco 1841's for some criticial sites, but may still want to use Netgear's stuff for some less critical ones if the 114 works well.

Dylan

 
The 114's have been solid for months. And they are smaller and cheaper too, so it works out nicely.
 
Alright, I have the phones working well over the VPN, all but for one thing. When you dial an external number or receive an external call the phones work well. However, when you dial an internal extension you cannot hear the person on the other end, nor can they hear you. An IP route has been set up. Phones at the remote location can call between each other's extensions, just calling the main site's extensions does not work properly. Any suggestions?

Thanks again for you help,

Dylan Finch

 
if direct media path is checked then uncheck it


______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
Dylan, I have the FVS124G at the main office and a FVS114 at a home for a 5610sw. Avaya has a very good white paper on the setup using the FVX538 so I knew I had to disable H323 and Google has your post on the top of the list. In fact, this forum is the only helpful post set I've found on this topic -- Even as a Netgear Partner, they won't give us the commands to do this; they say it is not supported!

To my issue: The VPN is solid & the phones link and login fine, but no dial tone. Netgear's answer was "uncheck the ALG SIP box under rules." Obviously, that ain't it. Did you end up disabling just H323 or also TCP/SIP 5061, 5620 & SIP (like Vonage)?
 
After my last post, I disabled tcpip5061 & 5620, SIP5061 & 5620, SIP & H323 on the FVS124G -- Also unchecked Direct media path. The system has been solid and will auto reconnect following reboots at either end -- thanks all.
Kevin
 
Just fought this battle at a client's office on a 406v2 with 3.1(56). The remote 5410 phone could not register (or work). However, the phone could download the txt and scr files from the VM machine at the main office. I did not see any H323 traffic in the monitor trace. Everything had worked fine when the IP phone was running locally.

In the end, the IT guy did 2 things that made the Netgear and 5610 work. I am unsure which of these fixed the problem:
1) Upgraded firmware on the Netgear routers.
2) Opened port 1719 on the remote Netgear. It seemed to only recognize 1720 as an H323 port.

Good luck,
Frank

Frank Robertshaw
The Phone Guy
Nashville, TN
 
I have a Pix 501 to Pix [525UR at Main] hardware VPN network is up and solid I am having the same issue where the 46xx.scr and .bin files transfer successfully but after I enter Ext and Password the phone displays Discover and the IP of the IPO. I have read thru and have done the no fixup for both h323 ports and SIP ports? Any help or suggestions would be appreciated.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top