And this last mail I received when I just pressed send. Anyways, thanks for sharing your views.
On Mon, Apr 8, 2013 at 10:47 PM, Justin Carney <justin.s.car...@gmail.com>wrote: > ...looks like I didn't read you email correctly the first time and you > already tried both methods :-) > > My recommendation (may or may not be the way the lab is graded) is that > you should use intra region param. Reason is the grading script might not > connect the call or it will only look at debugs for arq. In this case you > lose points in the brq method. On the other hand, if a call is setup and > the codec is check from the phones, then either method works. I can't > think of a reason where you would want to have a diff bw when setting up > the call than when connected, and why take the chance of losing points > using brq? That said, it wouldn't hurt to use both params, as another > question may require you to turn on brq. I would just recommend against > *only* enabling brq to answer this question. > On Apr 8, 2013 12:56 PM, "Justin Carney" <justin.s.car...@gmail.com> > wrote: > >> The brq parameter does does apply here (ie, won't fix the issue) since a >> brq is sent after a call is already connected and is requesting a *change* >> in bandwidth. >> >> The initial call setup is done with an arq that contains the initial >> bandwidth request. If you debug this issue end to end, you will see site 3 >> router send arq with bandwidth 16 (shown as 160), and gk will send acf to >> site 3 with be 16. The issue is from the go to cucm, I don't recall if the >> go arq is asking cucm for 16 or 128, but I know the acf from cucm to go is >> 128. No where in this call setup is a brq used, and the call is setup at >> 128k and uses g711. >> >> If you have time on your hands, it would certainly be a good exercise to >> try both service params and debug each...or just save yourself the trouble >> and use the intra region SVC param :-) >> On Apr 8, 2013 12:26 PM, "Suresh Bhandari" <bring...@gmail.com> wrote: >> >>> I confirm that I was hitting the bug! >>> >>> Here are my results: >>> >>> 1. When I changed the SP "BRQ Enabled" to "True" I got the bandwidth >>> while ringing state 128K and in connected state 16K. >>> 2. When I changed the Intraregion codec to G729, I got the bandwidth - >>> while ringing and connected - to be 16K. >>> >>> So, it really depends upon the question we face, whether to enable BRQ >>> or set Intraregion codec. >>> >>> So, thank you guys. >>> >>> >>> On Mon, Apr 8, 2013 at 8:46 PM, Suresh Bhandari <bring...@gmail.com>wrote: >>> >>>> Sergey, and all, >>>> >>>> I had hard-coded the G729 codec from UCM side, and when I did the same >>>> for voip dial peer pointing to RAS, it didn't show up, as it is the >>>> default. Tried with voice-class codec as well, but no luck. >>>> >>>> Will check the Bug as well. Thank Ramcharan for the bug id. >>>> >>>> >>>> On Mon, Apr 8, 2013 at 7:58 PM, Sergey Heyphets <ser...@heyphets.com>wrote: >>>> >>>>> Alternatively, you can just set your GK region to use G729 within the >>>>> region and G729 with all the other region (e.g. hardcode on region, rather >>>>> than use system default). >>>>> >>>>> >>>>> >>>>> >>>>> On Mon, Apr 8, 2013 at 9:56 AM, Mohamed Gazzaz <mgaz...@hotmail.com>wrote: >>>>> >>>>>> Hi Suresh, >>>>>> >>>>>> I think you are hitting a known bug . Please go to service parameters >>>>>> --> call manager and change the following to G729 >>>>>> >>>>>> Intraregion Audio Codec Default: G729 >>>>>> >>>>>> Regards, >>>>>> Mohamed Gazzaz >>>>>> >>>>>> ------------------------------ >>>>>> Date: Mon, 8 Apr 2013 19:02:14 +0545 >>>>>> From: bring...@gmail.com >>>>>> To: ccie_voice@onlinestudylist.com >>>>>> Subject: [OSL | CCIE_Voice] CME -> GK -> UCM bandwidth >>>>>> >>>>>> >>>>>> Hello Experts! >>>>>> >>>>>> I have HQ as the GK and CME, CUCM publisher and subscriber are >>>>>> registered to GK in single zone. Further, GK Trunk is in separate >>>>>> region/DP >>>>>> with hard-coded G.729 codec with other regions/itself as well. >>>>>> >>>>>> When I call from HQ to CME side, and check "sh gatek call" it shows >>>>>> that the call is consuming 16K bandwidth, which is expected. >>>>>> >>>>>> The dial-peer to CME has g729r8 as codec (the default one). >>>>>> >>>>>> Even then, the same command displays that the bandwidth consumed is >>>>>> 128K. >>>>>> >>>>>> Any thoughts on what probably I missed? >>>>>> -- >>>>>> Suresh Bhandari >>>>>> >>>>>> _______________________________________________ For more information >>>>>> regarding industry leading CCIE Lab training, please visit >>>>>> www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check >>>>>> out www.PlatinumPlacement.com >>>>>> >>>>>> _______________________________________________ >>>>>> For more information regarding industry leading CCIE Lab training, >>>>>> please visit www.ipexpert.com >>>>>> >>>>>> Are you a CCNP or CCIE and looking for a job? Check out >>>>>> www.PlatinumPlacement.com >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> For more information regarding industry leading CCIE Lab training, >>>>> please visit www.ipexpert.com >>>>> >>>>> Are you a CCNP or CCIE and looking for a job? Check out >>>>> www.PlatinumPlacement.com >>>>> >>>> >>>> >>>> >>>> -- >>>> Suresh Bhandari >>>> >>> >>> >>> >>> -- >>> Suresh Bhandari >>> >>> _______________________________________________ >>> For more information regarding industry leading CCIE Lab training, >>> please visit www.ipexpert.com >>> >>> Are you a CCNP or CCIE and looking for a job? Check out >>> www.PlatinumPlacement.com >>> >> -- Suresh Bhandari
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
