avaya ip 500 v2 on seperate subnets 2

[r_al_sim]

Hi i have a network configured to be on 10.0.0.1 255.255.255.0 on this network i have a windows server and a few linux servers and about 20 windows desktops and the odd linux desktop

I have a router that manages DHCP, local DNS, load balancing the the wan and firewall and ad blocking and service blocking (itunes, play store, windows telemtry data)

windows server handles all the windows 10 updates

I wanted to keep the phone system separate from the windows network but on the same switches

so the PBX was configured with as 192.168.1.250 255.255.0.0 and hosts a DHCP server for thant range. The phones I wanted to have every bodies PC's connected to the avaya phones dumb switch port on the back of the handset to save cabling.

so it all works PC's get there IP address from the DHCP server hosted on the router and phones get there DHCP from the PBX people working on the windows PC's have no idea that there is a phone system on the same network it cant be pinged nor can the phones and everyone's phones work fine and have done for months.

but i have two questions over the past month I see some 20,000 ms roundtrip response times logged in the QC tab under system status between devices randomly and I also see packet loss between handsets and PBX when it has an outbound isdn line making a call and alot of heavy data traffice

SQM is enabled on my switches and is cutting the data packets restricting sqm to wan connections only fix's this.

question 1
the ip 500 v2 is only a half duplex 10/100 switch is this device slowing down my 100/1000 switches

question 2
should i just go fully separate switches ( the reason for this simple separation is so i dont have to create complex routing rules just to hide the devices off the shared network device list but to also save space switch wise and office cabling) and BT also wont let me remove the dhcp server from the PBX

thanks

 

[r_al_sim]

So any PCs using passthrough on the phones will be limited to 10/100 as that is what the phones are."

yep I know they will but was curious about the rest of the network as there are servers and printers and wallscreens does a switch only work as well as its slowest connected device the rest of the network switch to switch and some other devices say they are working at gigabit and seems fine at gigabit to gigabit.

problem with this packet loss and calls dropping has me confused though like janni78 said "If you have an issue at only 4 calls that's about 0.4 mbit of network traffic."

i see on the realtime graph the load raise on the switch during the 4 calls but it doesnt flood the switch its not overloaded.

is it something with my qos settings

 

[gknight1]

packet loss is an indicator of speed and/or duplex mismatch.

double check your phones to make sure they match the switch ports.
double check the switch port that the IPO plugs into matches it

 

[mattKnight]

question 1
the ip 500 v2 is only a half duplex 10/100 switch

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[IPGuru]

It may be time to call in an IP Office maintainer who fully understands the network requirements for VoIP


Do things on the cheap & it will cost you dear

 

[r_al_sim]

so been playing with my router today configuring difserv and its now listening to the packet header dscp 46 hopefuly this fixes my issues and I can see all pc's are using 10/100 and my servers are negotiating at gigabit on the switches. and the switches are negotiating at gigabit to each other and the router just need to keep an eye on the qos now

obviously anyone who is connected through a phone will have a slower connection but all the wireless clients and the 5 desktops that dont have a desk phone will be fine

 

[r_al_sim]

so been monitoring it today and no 20,000ms round trip alarms no jitter and no packet loss no idea what changed on the network traffic wise that.

 

[r_al_sim]

so just an update to let everyone know how to fix, not a single dropped call or a single bit of packet loss recorded on the pbx

it was all down the the dscp headers not being read so if you have similar issues with multiple traffic over you lan configure diffserve to read the headers off the phone packets to prioritise traffic.

 

[qtelcom]

uh huh.... using dscp in a LAN environment... good for you.