qos issues

[phonetech2012]

We have about 50 remote ip users and some of them complain that they have qos issues.We have the pbx elan going into a regular 8 port hub. We also have the remote users in zone 1 which is set up for BQ intra and BQ inter, I think I should change inter to BB..? I copied a few errors we recived the other day if anyone can let me know where I should go next would be great. I am pretty sure we need to change out the hub for a layer 2 or 3 switch and change the zone to BB, or is the problem more on the user's end? Also, if I change the zone to BB, can I just do it during the day?
Thanks


% QOS019 QoS unacceptable packet loss: [45.3] % in

zone [1]
%
% QOS013 QoS warning jitter:[37.9] % in zone [1]
%
% QOS015 QoS warning R factor:[33.3] % in zone [1]
%
%
%
% QOS008 Unac latency :[PL:0.2 LT:104 JIT:2 R:93]
% Near [172.16.123.125:5000],TN[160 0 03

01],NZ[1:1]
% Far [172.16.123.142:5200] TN[160 0 02 01],

VPNI:Zone[1:1]
%
% QOS008 Unac latency :[PL:0.2 LT:104 JIT:1 R:93]
% Near [172.16.123.142:5000],TN[160 0 02

01],NZ[1:1]
% Far [172.16.123.125:5200] TN[160 0 03 01],

VPNI:Zone[1:1]
%
% QOS002 Warning latency :[99 ms]
% Near [172.16.123.125:5000] TN[160 0 03

01],NZ[1:1]
% Far [172.16.123.142:5200] TN[160 0 02 01],

VPNI:Zone[1:1]
%
% QOS002 Warning latency :[99 ms]
% Near [172.16.123.142:5000] TN[160 0 02

01],NZ[1:1]
% Far [172.16.123.125:5200] TN[160 0 03 01],

VPNI:Zone[1:1]
%
% QOS008 Unac latency :[PL:0.2 LT:102 JIT:2 R:93]
% Near [172.16.123.125:5000],TN[160 0 03

01],NZ[1:1]
% Far [172.16.123.142:5200] TN[160 0 02 01],

VPNI:Zone[1:1]
%
% AUD000
%
% QOS008 Unac latency :[PL:0.2 LT:102 JIT:2 R:93]
% Near [172.16.123.125:5000],TN[160 0 03

01],NZ[1:1]
% Far [172.16.123.142:5200] TN[160 0 02 01],

VPNI:Zone[1:1]
%
% QOS008 Unac latency :[PL:0.2 LT:100 JIT:1 R:93]
% Near [172.16.123.142:5000],TN[160 0 02

01],NZ[1:1]
% Far [172.16.123.125:5200] TN[160 0 03 01],

VPNI:Zone[1:1]
%
% QOS008 Unac latency :[PL:0.2 LT:104 JIT:6 R:93]
% Near [172.16.123.142:5000],TN[160 0 02

01],NZ[1:1]
% Far [172.16.123.125:5200] TN[160 0 03 01],

VPNI:Zone[1:1]
%
% QOS008 Unac latency :[PL:0.1 LT:102 JIT:2 R:93]
% Near [172.16.123.125:5000],TN[160 0 03

01],NZ[1:1]
% Far [172.16.123.142:5200] TN[160 0 02 01],

VPNI:Zone[1:1]
%
% QOS008 Unac latency :[PL:0.2 LT:102 JIT:0 R:93]
% Near [172.16.123.142:5000],TN[160 0 02

01],NZ[1:1]
% Far [172.16.123.125:5200] TN[160 0 03 01],

VPNI:Zone[1:1]
%
%
% QOS008 Unac latency :[PL:0.1 LT:102 JIT:2 R:93]
% Near [172.16.123.125:5000],TN[160 0 03

01],NZ[1:1]
% Far [172.16.123.142:5200] TN[160 0 02 01],

VPNI:Zone[1:1]
%
% QOS008 Unac latency :[PL:0.2 LT:102 JIT:1 R:93]
% Near [172.16.123.142:5000],TN[160 0 02

01],NZ[1:1]
% Far [172.16.123.125:5200] TN[160 0 03 01],

VPNI:Zone[1:1]
%
% QOS008 Unac latency :[PL:0.1 LT:102 JIT:1 R:93]
% Near [172.16.123.125:5000],TN[160 0 03

01],NZ[1:1]
% Far [172.16.123.142:5200] TN[160 0 02 01],

VPNI:Zone[1:1]
%
% QOS008 Unac latency :[PL:0.2 LT:102 JIT:0 R:93]
% Near [172.16.123.142:5000],TN[160 0 02

01],NZ[1:1]
% Far [172.16.123.125:5200] TN[160 0 03 01],

VPNI:Zone[1:1]
%
% QOS008 Unac latency :[PL:0.1 LT:102 JIT:3 R:93]
% Near [172.16.123.125:5000],TN[160 0 03

01],NZ[1:1]
% Far [172.16.123.142:5200] TN[160 0 02 01],

VPNI:Zone[1:1]
%
% QOS008 Unac latency :[PL:0.2 LT:102 JIT:1 R:93]
% Near [172.16.123.142:5000],TN[160 0 02

01],NZ[1:1]
% Far [172.16.123.125:5200] TN[160 0 03 01],

VPNI:Zone[1:1]
%
% QOS008 Unac latency :[PL:0.1 LT:103 JIT:4 R:93]
% Near [172.16.123.125:5000],TN[160 0 03

01],NZ[1:1]
% Far [172.16.123.142:5200] TN[160 0 02 01],

VPNI:Zone[1:1]
%
% QOS008 Unac latency :[PL:0.2 LT:102 JIT:0 R:92]
% Near [172.16.123.142:5000],TN[160 0 02

01],NZ[1:1]
% Far [172.16.123.125:5200] TN[160 0 03 01],

VPNI:Zone[1:1]
%
% QOS008 Unac latency :[PL:0.1 LT:104 JIT:2 R:93]
% Near [172.16.123.125:5000],TN[160 0 03

01],NZ[1:1]
% Far [172.16.123.142:5200] TN[160 0 02 01],

VPNI:Zone[1:1]
%
% QOS008 Unac latency :[PL:0.3 LT:102 JIT:0 R:92]
% Near [172.16.123.142:5000],TN[160 0 02

01],NZ[1:1]
% Far [172.16.123.125:5200] TN[160 0 03 01],

VPNI:Zone[1:1]
%
% QOS008 Unac latency :[PL:0.1 LT:107 JIT:4 R:93]
% Near [172.16.123.125:5000],TN[160 0 03

01],NZ[1:1]
% Far [172.16.123.142:5200] TN[160 0 02 01],

VPNI:Zone[1:1]
%
% QOS008 Unac latency :[PL:0.3 LT:102 JIT:1 R:92]
% Near [172.16.123.142:5000],TN[160 0 02

01],NZ[1:1]
% Far [172.16.123.125:5200] TN[160 0 03 01],

VPNI:Zone[1:1]
%
%
% QOS008 Unac latency :[PL:0.1 LT:104 JIT:2 R:93]
% Near [172.16.123.125:5000],TN[160 0 03

01],NZ[1:1]
% Far [172.16.123.142:5200] TN[160 0 02 01],

VPNI:Zone[1:1]
%
% QOS008 Unac latency :[PL:0.3 LT:104 JIT:1 R:92]
% Near [172.16.123.142:5000],TN[160 0 02

01],NZ[1:1]
% Far [172.16.123.125:5200] TN[160 0 03 01],

VPNI:Zone[1:1]
%
% QOS017 QoS unacceptable latency:[87.5] % in zone

[1]
%
%
% QOS019 QoS unacceptable packet loss: [2.3] % in

zone [1]
%
% QOS002 Warning latency :[99 ms]
% Near [172.16.123.142:5000] TN[160 0 02

01],NZ[1:1]
% Far [172.16.123.100:5200] TN[160 0 00 00],

VPNI:Zone[1:1]
%
% QOS002 Warning latency :[97 ms]
% Near [172.16.123.100:5000] TN[160 0 00

00],NZ[1:1]
% Far [172.16.123.142:5200] TN[160 0 02 01],

VPNI:Zone[1:1]
%
% QOS008 Unac latency :[PL:0.9 LT:102 JIT:0 R:91]
% Near [172.16.123.142:5000],TN[160 0 02

01],NZ[1:1]
% Far [172.16.123.100:5200] TN[160 0 00 00],

VPNI:Zone[1:1]
%
% AUD000
%
% QOS019 QoS unacceptable packet loss: [4.2] % in

zone [1]
%
% QOS008 Unac latency :[PL:0.6 LT:100 JIT:1 R:92]
% Near [172.16.123.100:5000],TN[160 0 00

00],NZ[1:1]
% Far [172.16.123.142:5200] TN[160 0 02 01],

VPNI:Zone[1:1]
%
% DTC001
%
%
% QOS008 Unac latency :[PL:0.9 LT:102 JIT:2 R:91]
% Near [172.16.123.142:5000],TN[160 0 02

01],NZ[1:1]
% Far [172.16.123.100:5200] TN[160 0 00 00],

VPNI:Zone[1:1]
%
% QOS008 Unac latency :[PL:0.9 LT:101 JIT:1 R:91]
% Near [172.16.123.142:5000],TN[160 0 02

01],NZ[1:1]
% Far [172.16.123.100:5200] TN[160 0 00 00],

VPNI:Zone[1:1]
%
% TIM340 20:00 30/10/2013 CPU 0
%
% QOS008 Unac latency :[PL:0.9 LT:102 JIT:1 R:91]
% Near [172.16.123.142:5000],TN[160 0 02

01],NZ[1:1]
% Far [172.16.123.100:5200] TN[160 0 00 00],

VPNI:Zone[1:1]
%
%
% QOS008 Unac latency :[PL:0.6 LT:101 JIT:2 R:92]
% Near [172.16.123.100:5000],TN[160 0 00

00],NZ[1:1]
% Far [172.16.123.142:5200] TN[160 0 02 01],

VPNI:Zone[1:1]
%
% QOS008 Unac latency :[PL:0.6 LT:101 JIT:1 R:92]
% Near [172.16.123.100:5000],TN[160 0 00

00],NZ[1:1]
% Far [172.16.123.142:5200] TN[160 0 02 01],

VPNI:Zone[1:1]
%
% QOS008 Unac latency :[PL:0.6 LT:101 JIT:1 R:92]
% Near [172.16.123.100:5000],TN[160 0 00

00],NZ[1:1]
% Far [172.16.123.142:5200] TN[160 0 02 01],

VPNI:Zone[1:1]
%
% AUD000
%
% QOS008 Unac latency :[PL:0.9 LT:107 JIT:0 R:91]
% Near [172.16.123.142:5000],TN[160 0 02

01],NZ[1:1]
% Far [172.16.123.100:5200] TN[160 0 00 00],

VPNI:Zone[1:1]
%
% QOS008 Unac latency :[PL:0.6 LT:102 JIT:1 R:92]
% Near [172.16.123.100:5000],TN[160 0 00

00],NZ[1:1]
% Far [172.16.123.142:5200] TN[160 0 02 01],

VPNI:Zone[1:1]
%
% DTC001
%
%
% QOS008 Unac latency :[PL:0.9 LT:102 JIT:1 R:91]
% Near [172.16.123.142:5000],TN[160 0 02

01],NZ[1:1]
% Far [172.16.123.100:5200] TN[160 0 00 00],

VPNI:Zone[1:1]
%
% QOS019 QoS unacceptable packet loss: [3.2] % in

zone [1]
%
% QOS017 QoS unacceptable latency:[26.2] % in zone

[1]
%
% DTC001

 

[Firebird Scrambler]

Nortel / Avaya never advised the use of hubs. You should really swap it out onto a Ethernet Switch.

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[phonetech2012]

Thanks for the reply. I will get that done asap. Any thoughts on changing the Interzone setting from BQ to BB?

 

[Tman45]

I would leave the Interzones the saame. If you still have trouble (after replacing with switch) then look at WAN - wee have had LOTS of WAN issues lately from CenturyLink ...

 

[KCFLHRC]

The ELAN has nothing to do with QOS issues, your TLAN is where all of the voice traffic is carried.

 

[Tman45]

Oh yeah - I think we had a hub installed in our CS1000S and we were getting tons of errors on the ELAN counters and QoS errors on history so we finally moved it to an unmanaged DLink switch and all the problems cleared. I forgot that we did that since it has been fixed for so long - we are even on a SMG now with the same DLink switch.

 

[phonetech2012]

Thanks for the replies. I actually just changed the zone to BB and got qos packet loss errors a few minutes later so that didn't help. (KCFLRHRC) I thougt the voip went over the tlan as well and didn't think the elan hub was really the cause of the qos errors, but I am going to change it anyway.Mopst of these errors seem to come from the same remote users, one especially pops up everyday. I wonder if this is a problem on the users end, maybe something is up with the routers they use at home?