@janni78 That would be up to my vendor. That is what I was told, 10 years they have not caused me to dis believe them.
@intrigrant I have to agree, but the network is not my sandbox...
It is indeed strange that it only happens when I load the configs into the manager. When I save them it all...
Indeed that is what is believed to be the problem.
However, the system has all the routes properly built and delineated. We are using Lanshark on the port the IP 500 unit is on. We do hope to see what is happening here.
What I do know is that when I open the manager and select any or all of the...
Still working on this. Narrowed it down a bit to the fact that we loose connection between the IP500s in the SCN that are on a different subnet. Cannot ping from one to the other. Network guys are setting up wireshark for some investigation. I will keep updating as we go and am open to...
Thanks!
DHCP contains the 176 SSON with a pointer to the IP500 V2 and the TFTP server for the a and b files etc. and that works fine. We do not currently use VLANS, we do have 13 subnets though. I have tried static addressing with no success with this issue, they react as the DHCP phones do in...
Thanks!
I think routing issue as well but have been assured nothing has been changed. They want an Avaya tech to assure nothing is wrong on the phone system. I am in the process of obtaining some tech time.
Alas it could be, red or otherwise it's beginning to stink! I am going to test it tonight...
In the last few weeks I have suddenly started to have a problem with my IP phones. For no particular reason they all restart and get stuck at Discover:XXX.XXX.XXX.XXX where the xxx is the correct address of the IP500 V2 that they are attached to. Even more bizarrely we think we have it narrowed...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.