Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Jitter, packets lost.. Cisco with Avaya Ip Office

Status
Not open for further replies.

VoIPchic

Technical User
Jul 21, 2011
42
MX
Hi everyone
I just read a similiar thread that was already closed.
My problem is that system status display a lot of alarms in qos, Jitter and packets lost.
Is a small network, with 12 ip phones, 2 analog and 10 pc's.
I just did the things of the other thread with no luck.
I have a cisco esw500 with qos, with no vlans, only the default. I changed to half duplex and 100 in the switch port and I tested with auto too. Change system from g729 to g711, each voip extention to g711, with direct media path.
I have no idea what to do.
Any help would be appreciate..
thnks in advance
 
You need to build vlans for data and voice.
Then your problems will go away.

BAZINGA!

I'm not insane, my mother had me tested!
 
Is it just SSA with alarm values not possible at all, like several hours of delay? Or do they really have some problems?

In such a small network with just one switch and a few phones and PC's, you should not have real problems. Just turn on DSCP on the Cisco to have priority for voice traffic.
What I want to say is, that in such a mall and simple setup it will be hard to produce so much traffic that the switch cannot handle it. Your traffic is just switched, not routed. Do you have PC's behind plugged behind the phones?
IPO and the IP-Phones use 'Auto', so don't fix these settings on the switch. they must be the same.
 
Albus, i have seen those alarms disappear when VLAN's being used.
You probably will not notice it all the time but it really helps.


BAZINGA!

I'm not insane, my mother had me tested!
 
The Golden Rule for QoS alarms in SSA is "They are Bullsh1t" just ignore them, as you say they are often impossible numbers. Unless you are getting actual issues with your voice forget it :)

NTE-wave-logo-for-a4-header.jpg
 
thnks for your responses
But I dont want to make vlans, ´cuz we have ccr, contact store, vmpro and also I have like 5 pc's connected to phones.
I set again to auto on both. I chged the ipo port like smart port in sw, but issue persists. So I reset to default to start oveer, chged the ip and that's all.
Albus2, I checked the DSCP on sw, but I don´t understand to much how can I turn on, cuz I have dscp mapping like this

DSCP In DSCP Out
0 0
1 1
...63 ...63

And the SSA is still showing qos several alarms:

21/07/2011 06:02:16 PM 10 Extentión 6223 192.168.1.60 192.168.1.55 Jitter: 5,212.6ms
21/07/2011 06:08:54 PM 23 Line 13 192.168.1.55 192.168.1.70 39.4%
21/07/2011 06:08:55 PM 23 Extentión 6217 192.168.1.70 192.168.1.55 67.1%
22/07/2011 10:06:23 AM 57 Line 13 192.168.1.55 192.168.1.70 8.9%
22/07/2011 10:06:23 AM 57 Extentión 6217 192.168.1.70 192.168.1.55 11.3%
22/07/2011 10:10:30 AM 61 Line 13 192.168.1.55 192.168.1.70 10.9%
22/07/2011 10:10:30 AM 61 Extentión 6217 192.168.1.70 192.168.1.55 11.3%


 
and amriddle01, I disagree with you, the alarms show for a reason and of course, I have voice problems, and dropped calls.
 
Then program VLAN's!!!

Your amount of phones and applications are NOT a reason for not doing it!

The IPO has two Lan ports which can put in a data and in a voice VLAN (the easy way)


BAZINGA!

I'm not insane, my mother had me tested!
 
I agree with amriddle01. We use VLAN's on all of our customers but still see crazy QOS errors like 6637566746527746374734637ms delay. The numbers just don't make sense especially when you take into account that the users have no noticable issues. I dismiss most of what I see in QOS alarms.


APSS - ACIS - ACSS
 
ok, lets suppose that we can make vlans.
here is the thing, some pc's connected to ip phones needs to see the cctv software.
I'll need a data, voice and video vlan.
I think the problem is in the qos of the sw, because by default all the 24 ports appears like (ip phone+deskphone), ip phone is in 100 vlan voice and data is on 1. If I remove this cisco vlan-voice, that I think is for cisco ip phones, the phones have no qos.
And the sw only has GUI, not CLI.
 
Check the DSCP values in the switch and the IP Office.
I can remember something that the Cisco uses different settings then the IP Office has by default.



BAZINGA!

I'm not insane, my mother had me tested!
 
DSCP values are for layer 3 they will not be considered by the switch on the VLAN's you need to check/set the CoS value the handsets are using if any, this is in the 46xx settings file :)

NTE-wave-logo-for-a4-header.jpg
 
You don't know if it is a layer 3 switch and it can also being caused by the router :)
It does not harm checking and or changing it.

BAZINGA!

I'm not insane, my mother had me tested!
 
Hi again
How do I enable the vlan id on ip office?
I thought that was in System>LAN 1>VoIP>Vlan, but only says, "not present" and disable.
By default all cisco ports have 2 vlans:
vlan1: default as untagged, and
vlan100 for Cisco-Voice as tagged.
I entered vlan 100 in ip phone and displayed after reset "*bad router" and never responded.
My calls dropped and you can hear like mmmm a delay during the call.
check out my SSA.. I need help

Date ID DEVICE IP ADDRESS IP ADDRESS JITTER DELAY
27/07/2011 02:53:49 PM 925 Extension 6217 192.168.1.70 192.168.1.55 22.9ms
27/07/2011 02:58:13 PM 930 Extension 6217 192.168.1.70 192.168.1.55 2,892.1ms
27/07/2011 12:28:58 PM 852 Extension 6224 192.168.1.63 192.168.1.55 9,815.6ms
27/07/2011 12:17:36 PM 834 Extension 6224 192.168.1.63 192.168.1.55 23.1ms 27.7%
27/07/2011 04:15:14 PM 981 Line 13 192.168.1.55 192.168.1.62 3.1%
27/07/2011 03:22:12 PM 949 Extension 6217 192.168.1.70 192.168.1.55 4,533.9ms
27/07/2011 03:11:55 PM 940 Extension 6217 192.168.1.70 192.168.1.55 590ms
27/07/2011 05:24:56 PM 1021 Extension 6227 192.168.1.65 192.168.1.55 2,544ms
27/07/2011 04:15:14 PM 981 Extension 6214 192.168.1.62 192.168.1.55 3.9%
27/07/2011 03:32:02 PM 959 Extension 6217 192.168.1.70 192.168.1.55 38.6ms
27/07/2011 05:26:29 PM 1030 Extension 6227 192.168.1.65 192.168.1.55 1,041ms
27/07/2011 11:55:49 AM 825 Line 1 192.168.1.55 192.168.1.70 22.2%
27/07/2011 05:41:08 PM 1068 Extension 6227 192.168.1.65 192.168.1.72 6,669.8ms
27/07/2011 11:55:49 AM 825 Extension 6217 192.168.1.70 192.168.1.55 9.7%
27/07/2011 12:09:26 PM 836 Line 13 192.168.1.55 192.168.1.70 3.9%
27/07/2011 12:37:19 PM 867 Line 13 192.168.1.55 192.168.1.72 9.7%
27/07/2011 12:09:26 PM 836 Extension 6217 192.168.1.70 192.168.1.55 4.2%
27/07/2011 12:37:19 PM 867 Extensin 6226 192.168.1.72 192.168.1.55 10.5%
27/07/2011 12:17:36 PM 834 Line 13 192.168.1.55 192.168.1.63 19.1%
27/07/2011 02:46:09 PM 918 Extension 6217 192.168.1.70 192.168.1.55 117.6ms
 
The system does not need to know about the VLAN and as such there is no setting for it, the systems VLAN is dictated by the port you have it connected to. Handsets need to know the VLAN as they pass through data traffic, if the phone says bad router when in the VLAN 100 then you have routing/VLAN issues, this is not a system or handset issue, but TBH if you don't understand this you should not be touching it, you can make a real mess if you're not careful :)

NTE-wave-logo-for-a4-header.jpg
 
@VoIPchic, Enable QOS helps a bit but it won't solve your problem. The bad thing about QOS or TOS is that it will slow down your normal network traffic. Because it will add a QOS tag to voice and will make voice go first before a data packet. Using VLAN's will make voice and data faster because you have less hardware on the same subnet and there will be no interference between them.

I've used QOS 3 times on all installs i've done for the rest of the installs VLAN'S no issues at all.

Also don't trust the SSA info seen a lot packet/jitter on the SSA and never heard the customer cmoplaining.

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool )
______________________________________
 
If you think there are network issues, for a few handsets, just put your voice network on LAN2 (WAN port) and your data on LAN1 (for CCR / voicemail etc) then all your quality issues will go away, then you dont need to fart around with VLANs / QoS etc.

ACSS - SME
General Geek

CallUsOn.png


1832163.png
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top