46xxVPNphone very picky

[crisponions]

Anyone played much with the vpnphone? We finally got it up and working at the office, but then none of us (accept one) can get it to work at home. For 2 of us the phone refuses to get a DHCP address from our DSL routers (while PC's work fine), another tech got it to work from his wireless\dhcp router but it wouldn't work plugged into his cable modem. What gives? DHCP is a pretty standardized protocol, can't figure out why theses phones are being so picky.

Also statically punched in values to the phone, and it complained I have a bad router. Is this going to be one of those features that only works with XXX brand home router/modems? The 2 times we did get it to work were both cisco routers - high-end cisco dsl router at work and the other tech has a linksys (low-end cisco)

 

[CrossTalkTek]

I have it working just fine!
I'm using RoadRunner/TWC, and it's just like a landline. The only problem that I have noticed so far is that if I'm on a Conference Call for 45 minutes or more, I begin to get some major league echo. I'll just re-dial into the Conference Bridge, and then I'll be fine. But for normal work related calls, I love it.

I HOPE THIS HELPS:
My original issue was getting the actual VPNRemote Phone firmware onto the phone.

The instructions in the .pdf document didn't work for me.
BTW, I'm using a D-Link DI-704P wireless with 4 hardwired ports and Avaya 4621SWIP Phone.
Link to my router:

http://www.dlink.com/products/?pid=63&sec=0

Here's what I did, maybe this will help.

-Using my Home PC, I started a tftp server, and pointed the upload/download directory to the original 46xxH323_081406 firmware.
That computer's IP address is 192.168.0.101.

-Then, when the phone powers up, and press the asterisk key to program, (or *) and I manually applied the following values:

Phone=192.168.0.140 (statically assign first time)
CallSv=xx.xx.xx.xx (whatever your Clan IP is)
CallSvPort=1719
Router=192.168.0.1 (My Home Router)
Mask=255.255.255.0
FileSv=192.168.0.101 (My Home PC/w TFTP Server firmware)
802.1Q=auto (That setting works best for me)
VLAN ID=0
VPN Start Mode:BOOT

HERE IS THE VERY TRICKY PART

After the phone loads the firmware from your TFTP Server then reboots several times, go BACK TO YOUR TFTP SERVER setup, and change the path to the VPNRemote firmware. THEN, very important, perform a copy the 46vpnupgrade.scr AND rename it to 46xxupgrade.scr

PLUS

Copy, 46vpnsetting_avaya.txt, and rename the new file 46xxsettings.txt

Notice the settings file is PLURAL, but the 46vpnsetting_avaya.txt is SINGULAR. IT WILL ONLY WORK IF YOU NAME THE FILES APPROPRIATLY.

Sorry for the cap's, I was just trying to Emphasize the most important steps that I found that worked for me.

Finally, when your phone FINALLY loads the new VPN Firmware from your TFTP Server, and settles down (15 minutes, be patient for sure or you will not be able to go forward), you need to go back into your phone setup, (MUTE ADDR#) and use the following values:

Phone=0.0.0.0 (Now you'll be using DHCP)
CallSv=xx.xx.xx.xx (Your Clan Address-MUST KNOW THIS)
CallSvPort=1719
Router=0.0.0.0 (Now you'll be using DHCP)
Mask=0.0.0.0 (Now you'll be using DHCP)
FileSv=xx.xx.xx.xx (CORPORATE TFTP SERVER-MUST KNOW THIS, or you are out of luck)
802.1Q=auto
VLANID=0
VPN Start Mode: BOOT

Then let the phone ask for your VPN -USERNAME/Password, then will create the VPN Tunnel. Watch the phone, there's some stuff you'll get used to viewing.

You will see the phone create the tunnel, log on, then finally, when you know it is working and it saw your CLAN, it will ask you for your extension and password.

When you get to this point, finish that beer, because you finally made it work! Good job if you got to this point.

If anyone finds this useful, please let me know.

Good Luck out there

 

[crisponions]

Thanks for the advice. My problem seems to be its really picky about the router.

The phone setup works fine, at work we have a dsl line with a cisco router/dsl modem handing out dhcp, if I plug the phone into that it connects and works just fine, also had another coworker plug it into his linksys router at home and it worked just fine.


At home I am using windows 2003 to hand out my dhcp, and I can see it picks up an address, it just hangs at "finding router" then reboots and the cycle goes on.

Myself (and my boss) both have the crappy action-tek dsl modems that qwest provides. Now these routers work just fine for a PC, I can enable dhcp on the router, plug a laptop in and away we go, but the phone doesn't seem to like them. I even statically assigned an IP address in the phone and it came back with the error "bad router?"

Our vision was to be able to set these up and just send them home with non-technical users, and they could just plug and play. But so far its looking like it isnt that simple.