Mitel Forums > Mitel MiVoice Business/MCD/3300
3300icp vlan
NewVoIP:
the ip address are in the voice vlan. Any other suggestion why is it that we have so much echo?
bobcheese:
can you post some more info on your hardware? System variant? cards installed? Trunks? number of stations etc? Is this a new install? Has this problem only recentley occured?
NewVoIP:
hello, This is new install. Our setup is
HP switches, 2 vlans (default, vlan30)
(Default vlan for data, consist of MS DHCP, untagged)(vlan30 Voip, priorty 6, Mitel DHCP, tagged)
All ports for Vlan30 are tagged, phones are getting address from Mitel dhcp, options are set below
3 Router 172.168.30.1 IP Address
125 Mitel id:ipphone.mitel.com;sw_tftp=172.168.30.2;call_srv=172.168.30.2;dscp=46v46s26 ASCII String
128 TFTP Server 172.168.30.2 IP Address
129 Call Server 172.168.30.2 IP Address
130 IP Phone Identifier MITEL IP PHONE ASCII String
134 DSCP 46 Numeric
No routing is set
We have been told that we need to set the vlan30 interface port that is trunk to Mitel 3300 to untagged and No to default vlan. Then we will need to set opiton 125, the same as the vlan id 30 and priorty that we have set on the hp switch.
With these changes is should reduce the amount of delay, echo, and jitters that we are having.
ralph:
You never said how many phones you were dealing with here.
If you have a large amount of phones or if you are pumping a lot of data around your network then setting up VLANS should help.
As a side note, do your self a favor and be sure that the Data Switch port connected to your MS DHCP server does not have the voice vlan associated with it. Twice now, I've been brought in to a problem where phones will not boot because that data switch port had both the voice and data vlan tied to it.
Ralph
www.statewide-dental-plans.com
chadmaynard:
Also, 172.16.30.0/24 isn't an rfc1918 network.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version