Some other details:
This is a virtual server. NIC1 from the server is our IPO default LAN 1 IP address which plugs into the customer's switch using port 18. The customer's switch has port 27 coming out of the same switch going into our port 1 of the POE. We used to have access with this set...
I'm sorry if I wasn't clear on my first post. This is actually for remote access into the IPO. It was working, but keeps failing now. We had internet access into the IPO until we plugged into the customer's core switch. Not sure if the problem is on the IPO side or the customer's equipment.
We have an IP Office SE running on VM and every time we plug our IPO into the customer's core switch, we lose internet connectivity. Can not figure out why this is happening. Anyone else come across this issue?
We got past the last issue with some help from Avaya. Now we're back to screwing around with the SIP trunks again. Trunks are registered but getting an error when making test calls. Seems like a configuration error on the IPO. Just keeping it exciting today.
Followed all of your collected advice and it paid off. Tried a few things and the SIP trunks have successfully registered. Thank you very much. That's the good news. The bad news is that we had an Avaya Engineer in the system last night (supposedly to help) and I believe he flipped the LAN1...
On site with VTTD1870. We have the same IP address built on our demo unit and the SIP trunks come up right away. Should we still change this .254 address?
As far as the Linux network relation from eth/0 and eth/1 to LAN 1/ LAN 2, do we need to set up the sub interface section in the web portal?
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.