|
|
Joined: Jan 2009
Posts: 840 Likes: 1
Member
|
OP
Member
Joined: Jan 2009
Posts: 840 Likes: 1 |
Never considered this before, but a customer asked me this.
They have (20) 9608 IP phones on an IP Office. The phones are set to use vlan 2 and their data is on vlan 1.
From their computers, they can ping the IP address of a phone, even though it is in a separate vlan/network. The only way I can think that this is happening, is the WAN (LAN2) port of the IP Office is the DHCP server for the phones and the LAN port is on their data network so that it can be reached using Manager and so it can communicate with the VM Pro server.
In my mind, the IP Office is somehow bridging that connection from the data vlan to the voice vlan. How can I isolate the traffic? Customer thinks that they should be totally separate. Although they have never complained about any phone issues and I haven't noticed any call/voice issues either.
|
|
|
Avaya IP Office Service in Canada
Atcom provides quick and affordable service for your Avaya IP Office business phone system!
Our expert technicians have years of experience installing, upgrading, and troubleshooting IP 500v2 and IPO Server Edition systems.
Proudly serving Canada from coast to coast.
|
|
|
Joined: Aug 2003
Posts: 268
Member
|
Member
Joined: Aug 2003
Posts: 268 |
How far apart are the vlan segments?
|
|
|
|
Joined: Jan 2009
Posts: 840 Likes: 1
Member
|
OP
Member
Joined: Jan 2009
Posts: 840 Likes: 1 |
I guess I'm not sure what you mean by how far apart the VLAN segments are.
VLAN 1 (data) is 192.168.1.xxx VLAN 2 (voice) is 192.168.2.xxx
|
|
|
|
Joined: May 2004
Posts: 1,653 Likes: 4
Moderator-Avaya
|
Moderator-Avaya
Joined: May 2004
Posts: 1,653 Likes: 4 |
If you do a trace route, that will show the IP addresses and VLANS it is hitting...
|
|
|
|
Joined: Jan 2009
Posts: 840 Likes: 1
Member
|
OP
Member
Joined: Jan 2009
Posts: 840 Likes: 1 |
Update...
Went back to customer today to do this traceroute, and I could no longer ping a phone IP from the computer. I was told that the network guy found something. My guess is something was plugged in wrong somewhere or they had a static route built somewhere that is now gone.
Customer is happy and all is good.
Thank you for the responses and suggestions.
|
|
|
|
Joined: Aug 2003
Posts: 268
Member
|
Member
Joined: Aug 2003
Posts: 268 |
My thought was that the subnet mask was set to 255.255.255.0, which would only allow you to see 255 IPs on the native segment. A mask of 255.255.254.0 would allow traffic from 192.168.1.x to see 192.168.2.x.
|
|
|
Forums84
Topics94,161
Posts638,205
Members49,736
|
Most Online5,661 May 23rd, 2018
|
|
1 members (nortelvoip),
93
guests, and
37
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|