IP Office v3.x Qos

[sharpy667]

Just purchased an IP Office 406v2 and will be running in "tdm mode".

Have also purchased VCM5 and 1 ip handset along with BayStack 460 Qos PoE switch for trials.

Q - It is my understanding that the ethernet switch on the 406 and on other models does NOT support Qos. How's that going to work then, even on a LAN with a QoS switch, let alone across a WAN.

It tends to suggest that if you want QoS into the Ip Office box it has to be acomplished via the WAN interface(s).

Any comments would be appreciated

 

[IPGuru]

The IP office DOES add the QOS information to lan trafic but you are correct that the hub/switch on the unit does not proccess this info.
to get reliable VOIP connect 1 of the IP Office ports & everything else to the QOS switch, do not make use of the remaining lan ports on the IPO.

 

[sharpy667]

Running VMPro through the switch could cause a problem then?

Did notice "voice breakup" when access VM from IP Phone even locally.

Will go back to supplier.

 

[MrIPO]

All the IPO does is TAG the RTP(Voice Traffic) and some signalling with a diffserv value that the switches and routers can act on if configured and supported correctly.

If you are experencing issue with you IP Phones I would suggest that you investagte your LAN enviroment. Eg VLANS and COS configured accross them.

Umm anotherprivatebuild !!!

 

[JeSTeROCK]

Go to bed mate, are you sick aswell ?

 

[sizbut]

The 406V2 LAN ports act as a switch so in normal use traffic on the port connected to the VMPro PC shouldn't affect traffic on the other ports.

The previous answers are correct, the IPO applies DiffServ marking to VoIP traffic it originates, ie. coming from the TDM side. IP devices themselves apply their own DiffServ marking (which normally should match those of the IPO)

The WAN port interface however is the only area in which the IP Office actually uses the DiffServ settings to prioritize Voice data traffic over non-voice data traffic.

 

[SuperJenks]

Running VMPro through the switch could cause a problem then?

Did notice "voice breakup" when access VM from IP Phone even locally.

Will go back to supplier."

I have experienced this as well. To fix this:

1. If the vmpro is plugged into a 3rd party switch, make sure you set the nic in the vmpro to 10/100mps full duplex assuming that is what the switch is capable of. If it is a third party hub, set the nic card 10/100 halfduplex. If the port speeds dont match, you will get collisions (Voice breakup). It is recommended to uplink the vmpro directly to the IPO. If you are using a IP403, the lan ports are hub ports 10/100mps half duplex. If you are using a IP406/IP412 the lan ports are switch ports and work at full duplex 10/100mps. The bottom line is to make sure you set the nic card at the appropriate matching settings.

2. If you have anti-virus on the vmpro, make sure your pc has enough memory and processor speed to handle the processes needed for the vmpro to function properly. Your alternative is to stop realtime scan and do scheduled scans on off hours. Otherwise, you will notice the pc lagging and cause voice processing breakup.

Hope this will help someone....

 

[VOiDDude]

Correction:

The 406 & 412 are half duplex, not full. The only ones that are full duplex are the SOE and if I'm not wrong the 406v2.

 

[crashtest1000]

Double check I think you will find the Switch on the SOE, 406V2 and 412 is 10/100 Half duplex

 

[VOiDDude]

Copy from the IPO docs:

- IP401, IP403 and IP406 (V1): Half duplex.
- IP412: Use LAN1 and half duplex.
- Small Office Edition and IP406 (V2): Full duplex.
- All IP Office LAN ports are 10Mbps/100Mbps auto sensing.