You have change threshold value in the below statement.
mls qos srr-queue output cos-map queue 3 threshold 2 4
all other seeting are correct.So the final config look like below
mls qos srr-queue output cos-map queue 1 threshold 3 5
mls qos srr-queue output cos-map queue 2 threshold 3 3 6 7
You have change threshold value in the below statement.
mls qos srr-queue output cos-map queue 3 threshold 2 4
all other seeting are correct.So the final config look like below
mls qos srr-queue output cos-map queue 1 threshold 3 5
mls qos srr-queue output cos-map queue 2 threshold 3
Dear All,
With regards to the above task... I have followed the WB, checked the PG and
watched the Walk-thro video..
Done everything as per required... But why is my SUB gk-trunk coming in as
_3 when it should be _2
I have taken the gatekeeper and trunk out of CCM and recreated them. Put
Hi Matt,
Yes i'm using my own lab.. thinking about it..the SUB has been rebuilt, due
to an issue with the DB.. So im thinking that the PUB thinks that this is
subscriber 2.. when its actually subscriber 1 rebuilt.. hence giving it an
identifier of _3
Would that make sense..
Thanks
hi,
I always thought that this number results from the order of CCMs in the CUCM
group assigned to the trunk. But if you have only 2 CCMs in the group (have
you checked this? maybe the previous subscriber installation was left there
and is inactive somehow?), then this number is indeed taken from
Did you not delete the Subscriber from CUCM group and re-added it again
before the rebuilt?
Ash
Duncan Hamilton-Walker wrote:
Hi Matt,
Yes im
using my own lab..
thinking about it..the SUB has been rebuilt, due to an issue with the
DB.. So
im thinking that the PUB thinks
OK...
Just noticed that this as well...
Priority 5: - should this not be 10 as per the config on the HQ-RTR
10.10.210.11:1720 gk-trunk_3
zone prefix PL 1... gw-priority 10 gk-trunk_2
From: ccie_voice-boun...@onlinestudylist.com
hi Tom and Joe,
with JF config like this : mls qos queue-set output 2 threshold 2 50 50 100 100
How can this be correct ? maybe I am wrong, pls suggest (they use threshold 3 ,
but above use threshold 2)
mls qos srr-queue output cos-map queue 1 threshold 3 5
mls qos srr-queue output
I believe that the fact that it was rebuilt just explains it all.
Not much to be concerned about here, I would suggest.
On Sun, Jul 4, 2010 at 6:52 AM, Duncan Hamilton-Walker
dun...@rosethorn.plus.com wrote:
Dear All,
With regards to the above task... I have followed the WB, checked the PG
One other thing, about your priority showing as 5 for gk_trunk_3, it
is because the gw default priority is always 5 by default, unless you
specify a different gw default priority for the prefix, or a specific
priority for the gateway.
Eg:
zone prefix PL 1... gw-default-priority 6
On Sun, Jul 4,
Bruce -
Have you ran a debug gatekeeper main 10? Could you include this debug
in this email thread?
My guess is that you have a 1# technology prefix coming into CUCM with
the 5002 (1#5002) and your H.225 trunk is set to ALL for significant
digits. For such a case, you would need to set
Sean -
Did you figure this one out?
*Matthew Berry*
*_Vitals:_*
*GVoice: *+1.612.424.5044
*Gmail*: ciscovoiceg...@gmail.com
*Skype*: ciscovoiceguru
*Twitter*: ciscovoiceguru
On 7/2/2010 11:12 AM, sean hurricane wrote:
Ashar,
I have tried your configuration and it does not
Phil -
The script looks good to me, but I haven't verified it in a lab. I
couldn't determine from your email if there was an actual problem with
the script or not. When you loaded it and ran tests, did you observe
any unexpected behavior?
Thanks!
*Matthew Berry*
*_Vitals:_*
*GVoice:
13 matches
Mail list logo