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

VPN phones no longer working with Comcast upgrade 1

Status
Not open for further replies.

vz58

Technical User
Jun 26, 2003
12
US
Recently had three 9620L VPN phones (out of a total of 5) that stop responding - getting the discover IP message on the phones, when the remote clients changed their network from Century Link to Comcast. As it turns out this seems to be a Comcast network concern because I can duplicate the same problem in my office using Comcast and the tech company I'm working with has tested the same on various other locations using Comcast. The phones work like they should on Verizon, Lumos, Century Links, etc but not Comcast. Catalyst doesn't have any ideas and haven't had much luck with Comcast yet and unfortunately I don't have the funds in the kitty to escalate to Avaya teir 2, although I might be forced into it to keep the customer. Any rate, two of the phones are working properly from different networks. Also, all VPN phones use the same Cisco ASA, same basic settings, same DHCP pool, and the same gateway. Any one had this or similar problems and if so what resolve? Avaya IPO is 8.0.44, IP 500v2 with all necessary license and correct default routes, etc.

I'm not seeing anything that really piques my interest in monitor, other than the fact that it recognizes the extn and then promptly moves on. Also, the phone passes through the VPN fine and I can ping it from the VM server and from the IPO system status.

Any help would be appreciated immensely.

Thanks,
 
Has anybody heard back on this issue - I am experiencing this with 96xx phones on Avaya CM 6.0 - Juniper VPN concentrators using XAUTH only with Comcast all in one modem/routers on 10.x.x.x home networks. I reached out to Avaya but they said to engage Comcast....any help would be great.
 
I have given up trying to understand the issue...I was able to get all my users moved to an alternate ASA with no problems, then suddenly a single user started experiencing the same issue on the alternate ASA and had to be moved back. I still believe this is Comcast but I've had no luck working with them, if you find anything out please pass it along. Good luck!
 
Go to the user and use wireshark to see what is being send to the router.
Then when you found that go to the office and do the same.
Compare those results and you will know what is going on.


BAZINGA!

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

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top