Link to home
Start Free TrialLog in
Avatar of Rob Williams
Rob WilliamsFlag for Canada

asked on

Avaya IP phone to IP phone

A client of mine has an Avaya IP403 VoIP system. I confess I am not very familiar with the unit, or any VoIP system, however because it has CAT5 cables attached, it seems to fall under IT :-)

There is one central IP403 with about 10 remote sites, each with it's own VPN, subnet, and a single Avaya IP phone. I have configured the VPN's with the supplied Linksys RV042's and the system seems to work fine. Every remote site can call the main office with their IP phone, and they can call any outside phone number without issue. However, no remote IP phone can contact an other IP phone at any of the remote sites. I assume this is a routing issue, but the support from the supplier is non-existent. "IP Routes" have been configured on the Avaya, but no "Logical LANs" or routing. There are also no VLANs, or VLAN or QOS capable switches, present at the main office site. I am told a softphone at one of the remote sites can talk to an IP phone at another site, but I have not verified this.

Can someone point me in the right direction as to why routing between the IP phones is not taking place. Does this need to be configured on the Avaya system, static routes on the local routers, or is it even possible with the existing hardware. I question whether they require routers capable of a hub and spoke VPN configuration, but I am out of my league here.
SOLUTION
Avatar of shepimport
shepimport
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Rob Williams

ASKER

Thanks shepimport, I will look into mesh topology.
--Rob
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks grblades that is a great help. The client has no problem purchasing decent equipment, and has always assumed the supplied Linksys RV042's might have to be replaced, at least at the main site.
Using routing, how many is "too many sites for this to be practical " ? Currently there are 10 and potential to reach 20 but never more than that. Creating all the routes even with 10 to me sounds like a rather large routing table for a Linksys, which shepimport  suggested will result in poor performance.
Looking at Cisco options would the PIX 515E be suitable for the main office with less than 20 sites, if he should I want to go that route?

Thanks,
--Rob
'Too many sites to be practical' depends on how often you add new sites and the maximum number of VPN tunnels the current equipment supports. Oviously if the equipment supports say 10 VPN connections then it can only connect to the main site and 9 other remote sites. If you do create a new site then you will need to reconfigure the RV042's at all the other sites.

For the main site the PIX515E will be fine. For the remote sites I would suggest the PIX506E.
>>"If you do create a new site then you will need to reconfigure the RV042's at all the other sites."
By no means an impossible task, but agree the Cisco is the better alternative to try to improve manageability and performance.
Thanks all. Very much appreciated.
--Rob
Avatar of lukeybaby
lukeybaby

THE IP OFFICE HAS ITS OWN ROUTING TABLE WHICH YOU CAN ROUTE BETWEEN THE ORGINAL VPNS