Avaya 9620L Remote Handset Issues
Currently we have a client with an Avaya IP Office PBX at the corporate office.
We have implemented a segmented VLAN network at the main office in order to keep data and voice traffic separate from one another. The handsets that are local have reported no issues with call quality.
However we also have eighteen users that are utilizing the Avaya Remote VPN feature of their 9260L handsets which terminates at the corporate office Cisco ASA5505.
These users are in different parts of the country, and each office has between eight handsets at the largest location to most having one or two handsets at the same location.
Each remote location is using a Cisco RVS4000 Small Business Router behind the Internet gateway provided by the Internet Service Providers which vary depending on geographical location and include Brighthouse, Comcast, Road Runner and Time Warner.
Each handset once connected to the vpn receives a static ip address associated with their vpn profile. However the local address at most of the locations is assigned by DHCP. The location with eight handsets have each handset assigned to them statically. This location is also in the closest proximity to the main office.
The main office is receiving it's internet connection from three bonded T-1 circuits.
We are currently still experiencing call quality issues at several of the smaller remote offices, and often experience a situation whereby the phones will display VPN failure, Discover xx.xx.xx.xx Most often we need to physically log into the Cisco ASA and logoff the sessions, as a reboot of the phone is not enough. Once the vpn user's session is logged off the phones will normally reconnect.
We have implemented a segmented VLAN network at the main office in order to keep data and voice traffic separate from one another. The handsets that are local have reported no issues with call quality.
However we also have eighteen users that are utilizing the Avaya Remote VPN feature of their 9260L handsets which terminates at the corporate office Cisco ASA5505.
These users are in different parts of the country, and each office has between eight handsets at the largest location to most having one or two handsets at the same location.
Each remote location is using a Cisco RVS4000 Small Business Router behind the Internet gateway provided by the Internet Service Providers which vary depending on geographical location and include Brighthouse, Comcast, Road Runner and Time Warner.
Each handset once connected to the vpn receives a static ip address associated with their vpn profile. However the local address at most of the locations is assigned by DHCP. The location with eight handsets have each handset assigned to them statically. This location is also in the closest proximity to the main office.
The main office is receiving it's internet connection from three bonded T-1 circuits.
We are currently still experiencing call quality issues at several of the smaller remote offices, and often experience a situation whereby the phones will display VPN failure, Discover xx.xx.xx.xx Most often we need to physically log into the Cisco ASA and logoff the sessions, as a reboot of the phone is not enough. Once the vpn user's session is logged off the phones will normally reconnect.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.