I've been the proud owner of two IP Offices for about two years. I"ve spent a great deal of money buying them and a small fortune trying to make them work. That being said -- they do not function properly 80% of the time.
There are two primary problems:
1. We have a series of about 40 Avaya 5601 IP telephones at remote sites. Each site has one, possibly two phones (most have one). Periodically, these phones lock down -- that is they simply stop functioning -- like they have lost their connection to the IP Office. The VPN between the sites is functioning perfectly and the low latency queue (QOS) between the sites reveals no tail drop or other comparable issues.
Sometimes a phone will lock down after being up only a few minutes, sometimes a phone will be up for days or weeks and then lock down. A small portion of the phones that do lock down are rendered permanently unusable. That is they are never again able to connect to an IP Office even when they are local to the IP office, even after a RESET command is performed on the phone.
The VPN tunnels between the sites continue to function properly and other data traveling between the sites appears unimpacted.
2. Our second problem pertains to the Small Community Networking connection between the two IP Offices. We have SCN configured between the two sites and it is properly licensed. However, at one site the SCN status in manager always shows as "Enabled" and at the other it always shows as "Up". Obviously they should both show "Enabled". We have checked the ports between the two sites and confirmed that the VPN tunnel between the sites is open. The two sites are unable to communicate using SCN -- the only way to currently route calls between sites is using short codes pointed to the IP lines, which is very restrictive.
Any help that anyone could povide on either of these issues is very helpful. I"m sure you'll want more information, just ask and I'll tell you anything I can. As I mentioned above I'm very frustrated with the entire process and the fact that we're two years into the process and we're still having the same two problems that we've been working on since day one.
Richard
There are two primary problems:
1. We have a series of about 40 Avaya 5601 IP telephones at remote sites. Each site has one, possibly two phones (most have one). Periodically, these phones lock down -- that is they simply stop functioning -- like they have lost their connection to the IP Office. The VPN between the sites is functioning perfectly and the low latency queue (QOS) between the sites reveals no tail drop or other comparable issues.
Sometimes a phone will lock down after being up only a few minutes, sometimes a phone will be up for days or weeks and then lock down. A small portion of the phones that do lock down are rendered permanently unusable. That is they are never again able to connect to an IP Office even when they are local to the IP office, even after a RESET command is performed on the phone.
The VPN tunnels between the sites continue to function properly and other data traveling between the sites appears unimpacted.
2. Our second problem pertains to the Small Community Networking connection between the two IP Offices. We have SCN configured between the two sites and it is properly licensed. However, at one site the SCN status in manager always shows as "Enabled" and at the other it always shows as "Up". Obviously they should both show "Enabled". We have checked the ports between the two sites and confirmed that the VPN tunnel between the sites is open. The two sites are unable to communicate using SCN -- the only way to currently route calls between sites is using short codes pointed to the IP lines, which is very restrictive.
Any help that anyone could povide on either of these issues is very helpful. I"m sure you'll want more information, just ask and I'll tell you anything I can. As I mentioned above I'm very frustrated with the entire process and the fact that we're two years into the process and we're still having the same two problems that we've been working on since day one.
Richard
