ASA & 96XX VPN - Discover IPO Address After Some Time

[jhengel]

Hey guys,

I have followed these threads very closely over the last year or so and some searching again now but I have not found a solid fix for this issue.

We have a handful of customers that use 9620L & 9620C's to connect to ASA 5505 & 5510's. We have a few customers that will have remote phones sporadically lose registration and sit on Discover xxx.xxx.xxx.xxx (IP address of IP Office). Leaving the phone disconnected for 5 minutes and reconnecting will generally get the phone up for a short period of time but they will eventually lose connectivity again.

We follow the Avaya white paper exactly on both the Cisco & Avaya side, using the PSK w/XAuth settings. I have tossed a few million scenarios through my head but haven't found an actual fix.

The two sites that we are currently experiencing issues with are both ASA 5505's on 8.2.5, and both have Comcast static IP's (I have pruned that thread also). One IP office is on 8.0.57 and the other on 8.1.43.

I have a hard time figuring this is an issue on the Avaya side but the anyconnect & legacy vpn clients do not seem to have the same issues. Has anyone found a complete fix for this issue? Is there some timeout or keep alive problem?

Any help would be hugely appreciated.

 

[jhengel]

Am I really the only tek-tipper still chasing down this problem? My head is going numb from pounding it against the desk

 

[Westi]

there is in another thread something you could try

In NoUser source code add REMOTE_H323=1800 This changes the port being used by the handsets and gets round the Cisco's annoying little sniffers.

http://www.tek-tips.com/viewthread.cfm?qid=1715689

seems to have worked for a few people so far

Joe W.

FHandw, ACSS (SME), ACIS (SME)

http://convergednetworks.ca

“This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

 

[tlpeter]

Westi, this are VPN phones. Your suggestion is for remote workers.

BAZINGA!

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

 

[Gunnaro]

Jhengel, have you looked at this document?

https://devconnect.avaya.com/public/download/interop/vpnphon_asa.pdf

Kind regards

Gunnar

________________________________________

Oh, for fox sake!

 

[jhengel]

There is actually a sheet for doing it with IP Office that we follow So, kinda

 

[jhengel]

Does anyone else still have this issue persisting? Both of these customers have Comcast where the ASA is but I am not sure whether that is my issue.

If so - is there something I can reference when calling Comcast support?

 

[Phonetastic]

We have it working on Juniper SSG20's and SSG140's. The only complaint that I would get from one customer is similar, one or two of the three VPN phones at the remote site would lose connection. I would get the service call and try to figure out why, they would unplug the phone and reconnect and everything would work fine. I finally took the drive to the remote location one day and after hours of troubleshooting realized that the internet speed there was super slow. If the network traffic got too heavy the phone would disconnect. I advised them to get an upgrade. I have not heard anything since. Not sure if your problem is specific with ASA but this is the only one I have had with the Juniper product. Seems to work for us......Sorry I know it does not help much.