Re: [OSL | CCIE_Voice] Lab strategy

[Somphol Boonjing]

Thanks, Bill for great information.

BTW, if I could ask about your thought on the VNC-only workstation.   I
don't really understand the logic behind making and RDP available for
Windows-based UCCX server, and only supply the VNC session for another
utility host.  (I was in a rush to such an extent that I couldn't even have
time nor effort to spend on finding the password to access the "VNC
session", I know it is right there somewhere obvious.  Sigh.  Hope I do
better next time.)

Regards,
--Somphol.


--Somphol


On Thu, Jun 6, 2013 at 10:04 AM, Bill Lake  wrote:

> Where are you taking your lab?  That has to play into your plan in taking
> the lab.
>
> I took my lab at RTP, my plan was to use the device base approach.
>
> 1)  I reviewed the outline of the lab, looking for very specific things
> throughout the lab that required early planning.  An example of this would
> be a System wide parameter that I would need to configure early on.
>
> 2) quickly notepad the items I would need throughout the lab
>
>
> 3) rough scope of the lab, my device based approach and dial plan page
>
> This took about 20 minutes to complete and in my opinion you should not
> spend more than 30 and your goal should be 15.
>
> At this point I started my device based approach and for me this was my
> order
>1) HQ switch
>2) do base to get CUE started and start CUE
>3) HQ Router
>4) SB router
>5) Check on CUE, do anything I thought I needed and could then reboot it
>6) SC router
>7) finish CUE
>8) base CUCM
>9) dial-plan with testing as I go all calls in round robin so I am
> using every phone to make calls (try to complete to this point)
>
> when 5 minutes before archive or back up all configs you can just incase
>
> Lunch
>
>10) finish CUCM
>11) CUC
> 12) CUPS
> 13) UCCX
> 14) Test everything you can
>
> Make sure you do not get stuck on one thing, spend 10 minutes and move on,
> circle back and try to complete it but keep moving.  I know it sounds
> simple but you will be amazed how long you might spend on a 2-3 point item
> you know you can do when it is costing you other points you could be
> scoring.
>
> During your testing focus on being the proctor and thinking how he might
> find fault in what you did.  Almost working perfectly won't get you the
> points.
>
> Bill
>
>
>
> On Wed, Jun 5, 2013 at 11:17 AM, Martin Sloan wrote:
>
>> Let me say, I've never sat the lab so I'm just commenting on my own study
>> experience.
>>
>>  - Points 3 & 4 are probably consuming too much time.  Documenting IP's
>> is good but I don't currently go through and check configs.  I figure i'll
>> get to it when it's time to configure that piece and if there are issues
>> I'll do my troubleshooting then.
>>  - 1.5hrs for Br2 seems like a long time.  I think you can get quicker
>> with that part and do it in 45min or less, depending on the complexity.
>>
>> Just with those savings you're getting closer to your 6 hour goal.  I use
>> notepad for anything that can be repeated like dial-peers, translation
>> rules/patterns, dspfarm, QoS, etc.  I think its MUCH faster than manually
>> typing the configs each time.  I always configure BR1 first so most of the
>> time I'm just tweaking some settings and pasting into BR2.
>>
>> Just my input based on my own studies.  I'm sure there are veterans out
>> there who have a better insight into saving time.  I'm interested to hear
>> their take as well.
>>
>> Marty
>>
>>
>> On Wed, Jun 5, 2013 at 10:58 AM, singh  wrote:
>>
>>>
>>> hi Everyone,
>>>
>>> I need your inputs here. I have been trying to complete mock and
>>> practice labs in 8 hours . However their I am unable to finish or I finish
>>> with lab with a lot of mistakes with no time for testing.
>>>
>>> I also realize that I lose thing in the first half and speed up during
>>> the end . Generally I take...
>>>
>>> 1) 10 mins to test if all equipment is working fine ( 10 mins)
>>> 2) read the workbook questions for the next 15 mins
>>> 3) Make note of the ip addresses and router configuration per site in 25
>>> mins
>>> 4) Make note of all cucm configuration , cups , unity connection , uccx
>>> and cue for another & dial plan 20 mins
>>> 5) Now from point 5 - I start with lab configurations from Branch 2 (
>>> site c - which is a mgcp gateway and srst setup) this generally takes me
>>> about 1 and a half hour to just complete all configuration ( 1 hour and 30
>>> mins)
>>> 6) Then I move to Branch 1 ( site B - which is a H323 gateway with srst)
>>> this ge nerally takes about 45 - 50 mins
>>> 7) I then move to HQ ( R1 - which is MGCP gateway with srst ) this
>>> generally takes 20 mins .
>>> 8) Basic setup of DP , css, aar, NTP , service parameters and enterprise
>>> para , vlans , dhcp and ip phone registration takes 50 mins
>>> 9) CUC integ and other config including recording takes 20 mins
>>> 10 ) CUE integration and trafer setup takes 20 mins
>>> 11) UCCX integration , One button , script and re

Re: [OSL | CCIE_Voice] Lab strategy

[Bill Lake]

Ok my last email got sent back
Where are you taking your lab?  That has to play into your plan in taking
the lab.
I took my lab at RTP, my plan was to use the device base approach.

1)  I reviewed the outline of the lab, looking for very specific things
throughout the lab that required early planning.  An example of this would
be a System wide parameter that I would need to configure early on.
2) quickly notepad the items I would need throughout the lab
3) rough scope of the lab, my device based approach and dial plan page

This took about 20 minutes to complete and in my opinion you should not
spend more than 30 and your goal should be 15.

At this point I started my device based approach and for me this was my
order
   1) HQ switch
   2) do base to get CUE started and start CUE
   3) HQ Router
   4) SB router
   5) Check on CUE, do anything I thought I needed and could then reboot it
   6) SC router
   7) finish CUE
   8) base CUCM
   9) dial-plan with testing as I go all calls in round robin so I am using
every phone to make calls (try to complete to this point)

when 5 minutes before archive or back up all configs you can just incase

Lunch

   10) finish CUCM
   11) CUC
12) CUPS
13) UCCX
14) Test everything you can

Make sure you do not get stuck on one thing, spend 10 minutes and move on,
circle back and try to complete it but keep moving.  I know it sounds
simple but you will be amazed how long you might spend on a 2-3 point item
you know you can do when it is costing you other points you could be
scoring.

During your testing focus on being the proctor and thinking how he might
find fault in what you did.  Almost working perfectly won't get you the
points.



On Wed, Jun 5, 2013 at 9:58 AM, singh  wrote:

>
> hi Everyone,
>
> I need your inputs here. I have been trying to complete mock and practice
> labs in 8 hours . However their I am unable to finish or I finish with lab
> with a lot of mistakes with no time for testing.
>
> I also realize that I lose thing in the first half and speed up during the
> end . Generally I take...
>
> 1) 10 mins to test if all equipment is working fine ( 10 mins)
> 2) read the workbook questions for the next 15 mins
> 3) Make note of the ip addresses and router configuration per site in 25
> mins
> 4) Make note of all cucm configuration , cups , unity connection , uccx
> and cue for another & dial plan 20 mins
> 5) Now from point 5 - I start with lab configurations from Branch 2 ( site
> c - which is a mgcp gateway and srst setup) this generally takes me about 1
> and a half hour to just complete all configuration ( 1 hour and 30 mins)
> 6) Then I move to Branch 1 ( site B - which is a H323 gateway with srst)
> this ge nerally takes about 45 - 50 mins
> 7) I then move to HQ ( R1 - which is MGCP gateway with srst ) this
> generally takes 20 mins .
> 8) Basic setup of DP , css, aar, NTP , service parameters and enterprise
> para , vlans , dhcp and ip phone registration takes 50 mins
> 9) CUC integ and other config including recording takes 20 mins
> 10 ) CUE integration and trafer setup takes 20 mins
> 11) UCCX integration , One button , script and recording takes 40 mins
> 12) CUPs integration and client setup takes 20 mins
> 13 )I then come back to callmanger and do the media resource setup ,
> gateways added cucm , other configuration such as MVA , RSVP , + dial ,
> adding trunks , unassigned dn setup to CUC - this takes 50 mins
> 14 ) Then I move to the Route pattern setup on callmanger this I do for 3
> sites - HQ , Site B and Site C with or without redundancy on callmanger
> this takes 25 mins
> 15 ) Then do this such as RTMT log collection and indicating informa tion
> in seperate files , MGCP debugs this takes another 15 mins
> 16 ) Switch and WAN QOS this I plan to do only if time permits as this is
> a complex section
>
>
> Questions :
> ===
>
> 1) I barely am able to finish things in time . I have heard from on this
> forum that there are candidates who finish it is 5 - 6 hours . Would anyone
> be able to share with me as to how they do this ?
>
> 2) Even if the above I complete exercises are complete there are sections
> where I miss out on configurations. How do I make sure all config for all
> sections is done correctly?
>
> 3) I really wish I am able to finish the lab in 6 hours so that I can test
> for another 2 hours . Could someone therefore check the above 16 points and
> let me know about the time I can reduce.
>
> 4) As you can see above the router configurations consume a bit more time
> making ( points 5 , 6 , 7 ) . I have tried with both using a notepad to
> type the configurations and then paste & also with typing on cli but both
> these methods take
> around the same time. Please let me know what best method I can use for
> points 5 , 6 , 7.
>
>
> 5) Other suggestions are most welcome .
>
>
>
> Thanks guys in advance for all your help!
>
> Regards,
> Singh
>
>
>
>
> Get Yourself a cool, short *@in.com* Email ID 

Re: [OSL | CCIE_Voice] Lab strategy

[Bill Lake]

Where are you taking your lab?  That has to play into your plan in taking
the lab.

I took my lab at RTP, my plan was to use the device base approach.

1)  I reviewed the outline of the lab, looking for very specific things
throughout the lab that required early planning.  An example of this would
be a System wide parameter that I would need to configure early on.

2) quickly notepad the items I would need throughout the lab


3) rough scope of the lab, my device based approach and dial plan page

This took about 20 minutes to complete and in my opinion you should not
spend more than 30 and your goal should be 15.

At this point I started my device based approach and for me this was my
order
   1) HQ switch
   2) do base to get CUE started and start CUE
   3) HQ Router
   4) SB router
   5) Check on CUE, do anything I thought I needed and could then reboot it
   6) SC router
   7) finish CUE
   8) base CUCM
   9) dial-plan with testing as I go all calls in round robin so I am using
every phone to make calls (try to complete to this point)

when 5 minutes before archive or back up all configs you can just incase

Lunch

   10) finish CUCM
   11) CUC
12) CUPS
13) UCCX
14) Test everything you can

Make sure you do not get stuck on one thing, spend 10 minutes and move on,
circle back and try to complete it but keep moving.  I know it sounds
simple but you will be amazed how long you might spend on a 2-3 point item
you know you can do when it is costing you other points you could be
scoring.

During your testing focus on being the proctor and thinking how he might
find fault in what you did.  Almost working perfectly won't get you the
points.

Bill



On Wed, Jun 5, 2013 at 11:17 AM, Martin Sloan wrote:

> Let me say, I've never sat the lab so I'm just commenting on my own study
> experience.
>
>  - Points 3 & 4 are probably consuming too much time.  Documenting IP's is
> good but I don't currently go through and check configs.  I figure i'll get
> to it when it's time to configure that piece and if there are issues I'll
> do my troubleshooting then.
>  - 1.5hrs for Br2 seems like a long time.  I think you can get quicker
> with that part and do it in 45min or less, depending on the complexity.
>
> Just with those savings you're getting closer to your 6 hour goal.  I use
> notepad for anything that can be repeated like dial-peers, translation
> rules/patterns, dspfarm, QoS, etc.  I think its MUCH faster than manually
> typing the configs each time.  I always configure BR1 first so most of the
> time I'm just tweaking some settings and pasting into BR2.
>
> Just my input based on my own studies.  I'm sure there are veterans out
> there who have a better insight into saving time.  I'm interested to hear
> their take as well.
>
> Marty
>
>
> On Wed, Jun 5, 2013 at 10:58 AM, singh  wrote:
>
>>
>> hi Everyone,
>>
>> I need your inputs here. I have been trying to complete mock and practice
>> labs in 8 hours . However their I am unable to finish or I finish with lab
>> with a lot of mistakes with no time for testing.
>>
>> I also realize that I lose thing in the first half and speed up during
>> the end . Generally I take...
>>
>> 1) 10 mins to test if all equipment is working fine ( 10 mins)
>> 2) read the workbook questions for the next 15 mins
>> 3) Make note of the ip addresses and router configuration per site in 25
>> mins
>> 4) Make note of all cucm configuration , cups , unity connection , uccx
>> and cue for another & dial plan 20 mins
>> 5) Now from point 5 - I start with lab configurations from Branch 2 (
>> site c - which is a mgcp gateway and srst setup) this generally takes me
>> about 1 and a half hour to just complete all configuration ( 1 hour and 30
>> mins)
>> 6) Then I move to Branch 1 ( site B - which is a H323 gateway with srst)
>> this ge nerally takes about 45 - 50 mins
>> 7) I then move to HQ ( R1 - which is MGCP gateway with srst ) this
>> generally takes 20 mins .
>> 8) Basic setup of DP , css, aar, NTP , service parameters and enterprise
>> para , vlans , dhcp and ip phone registration takes 50 mins
>> 9) CUC integ and other config including recording takes 20 mins
>> 10 ) CUE integration and trafer setup takes 20 mins
>> 11) UCCX integration , One button , script and recording takes 40 mins
>> 12) CUPs integration and client setup takes 20 mins
>> 13 )I then come back to callmanger and do the media resource setup ,
>> gateways added cucm , other configuration such as MVA , RSVP , + dial ,
>> adding trunks , unassigned dn setup to CUC - this takes 50 mins
>> 14 ) Then I move to the Route pattern setup on callmanger this I do for 3
>> sites - HQ , Site B and Site C with or without redundancy on callmanger
>> this takes 25 mins
>> 15 ) Then do this such as RTMT log collection and indicating informa tion
>> in seperate files , MGCP debugs this takes another 15 mins
>> 16 ) Switch and WAN QOS this I plan to do only if time permits as this is
>> a complex section
>>
>>
>> Questions 

Re: [OSL | CCIE_Voice] Lab strategy

[Somphol Boonjing]

Just my personal experience when I failed my first lab attempt.   CUE is at
the forefront of the time waster.   Simply because it requires constant
reboot if mistake is made and every reboots take a long time too.

>> 10 ) CUE integration and trafer setup takes 20 mins

My brain seems to go numb at times too.  Simple stuff becomes a lot harder,
and I still looking back on the day as how on earth I miss that easy fix.
Not saying that without it I would pass, I just think I wouldn't the
thoroughly outclassed by it.

Regards,
--Somphol.


--Somphol


On Thu, Jun 6, 2013 at 2:17 AM, Martin Sloan wrote:

> Let me say, I've never sat the lab so I'm just commenting on my own study
> experience.
>
>  - Points 3 & 4 are probably consuming too much time.  Documenting IP's is
> good but I don't currently go through and check configs.  I figure i'll get
> to it when it's time to configure that piece and if there are issues I'll
> do my troubleshooting then.
>  - 1.5hrs for Br2 seems like a long time.  I think you can get quicker
> with that part and do it in 45min or less, depending on the complexity.
>
> Just with those savings you're getting closer to your 6 hour goal.  I use
> notepad for anything that can be repeated like dial-peers, translation
> rules/patterns, dspfarm, QoS, etc.  I think its MUCH faster than manually
> typing the configs each time.  I always configure BR1 first so most of the
> time I'm just tweaking some settings and pasting into BR2.
>
> Just my input based on my own studies.  I'm sure there are veterans out
> there who have a better insight into saving time.  I'm interested to hear
> their take as well.
>
> Marty
>
>
> On Wed, Jun 5, 2013 at 10:58 AM, singh  wrote:
>
>>
>> hi Everyone,
>>
>> I need your inputs here. I have been trying to complete mock and practice
>> labs in 8 hours . However their I am unable to finish or I finish with lab
>> with a lot of mistakes with no time for testing.
>>
>> I also realize that I lose thing in the first half and speed up during
>> the end . Generally I take...
>>
>> 1) 10 mins to test if all equipment is working fine ( 10 mins)
>> 2) read the workbook questions for the next 15 mins
>> 3) Make note of the ip addresses and router configuration per site in 25
>> mins
>> 4) Make note of all cucm configuration , cups , unity connection , uccx
>> and cue for another & dial plan 20 mins
>> 5) Now from point 5 - I start with lab configurations from Branch 2 (
>> site c - which is a mgcp gateway and srst setup) this generally takes me
>> about 1 and a half hour to just complete all configuration ( 1 hour and 30
>> mins)
>> 6) Then I move to Branch 1 ( site B - which is a H323 gateway with srst)
>> this ge nerally takes about 45 - 50 mins
>> 7) I then move to HQ ( R1 - which is MGCP gateway with srst ) this
>> generally takes 20 mins .
>> 8) Basic setup of DP , css, aar, NTP , service parameters and enterprise
>> para , vlans , dhcp and ip phone registration takes 50 mins
>> 9) CUC integ and other config including recording takes 20 mins
>> 10 ) CUE integration and trafer setup takes 20 mins
>> 11) UCCX integration , One button , script and recording takes 40 mins
>> 12) CUPs integration and client setup takes 20 mins
>> 13 )I then come back to callmanger and do the media resource setup ,
>> gateways added cucm , other configuration such as MVA , RSVP , + dial ,
>> adding trunks , unassigned dn setup to CUC - this takes 50 mins
>> 14 ) Then I move to the Route pattern setup on callmanger this I do for 3
>> sites - HQ , Site B and Site C with or without redundancy on callmanger
>> this takes 25 mins
>> 15 ) Then do this such as RTMT log collection and indicating informa tion
>> in seperate files , MGCP debugs this takes another 15 mins
>> 16 ) Switch and WAN QOS this I plan to do only if time permits as this is
>> a complex section
>>
>>
>> Questions :
>> ===
>>
>> 1) I barely am able to finish things in time . I have heard from on this
>> forum that there are candidates who finish it is 5 - 6 hours . Would anyone
>> be able to share with me as to how they do this ?
>>
>> 2) Even if the above I complete exercises are complete there are sections
>> where I miss out on configurations. How do I make sure all config for all
>> sections is done correctly?
>>
>> 3) I really wish I am able to finish the lab in 6 hours so that I can
>> test for another 2 hours . Could someone therefore check the above 16
>> points and let me know about the time I can reduce.
>>
>> 4) As you can see above the router configurations consume a bit more time
>> making ( points 5 , 6 , 7 ) . I have tried with both using a notepad to
>> type the configurations and then paste & also with typing on cli but both
>> these methods take
>> around the same time. Please let me know what best method I can use for
>> points 5 , 6 , 7.
>>
>>
>> 5) Other suggestions are most welcome .
>>
>>
>>
>> Thanks guys in advance for all your help!
>>
>> Regards,
>> Singh
>>
>>
>>
>>
>> Get Yourse

Re: [OSL | CCIE_Voice] Lab strategy

[Martin Sloan]

Let me say, I've never sat the lab so I'm just commenting on my own study
experience.

 - Points 3 & 4 are probably consuming too much time.  Documenting IP's is
good but I don't currently go through and check configs.  I figure i'll get
to it when it's time to configure that piece and if there are issues I'll
do my troubleshooting then.
 - 1.5hrs for Br2 seems like a long time.  I think you can get quicker with
that part and do it in 45min or less, depending on the complexity.

Just with those savings you're getting closer to your 6 hour goal.  I use
notepad for anything that can be repeated like dial-peers, translation
rules/patterns, dspfarm, QoS, etc.  I think its MUCH faster than manually
typing the configs each time.  I always configure BR1 first so most of the
time I'm just tweaking some settings and pasting into BR2.

Just my input based on my own studies.  I'm sure there are veterans out
there who have a better insight into saving time.  I'm interested to hear
their take as well.

Marty


On Wed, Jun 5, 2013 at 10:58 AM, singh  wrote:

>
> hi Everyone,
>
> I need your inputs here. I have been trying to complete mock and practice
> labs in 8 hours . However their I am unable to finish or I finish with lab
> with a lot of mistakes with no time for testing.
>
> I also realize that I lose thing in the first half and speed up during the
> end . Generally I take...
>
> 1) 10 mins to test if all equipment is working fine ( 10 mins)
> 2) read the workbook questions for the next 15 mins
> 3) Make note of the ip addresses and router configuration per site in 25
> mins
> 4) Make note of all cucm configuration , cups , unity connection , uccx
> and cue for another & dial plan 20 mins
> 5) Now from point 5 - I start with lab configurations from Branch 2 ( site
> c - which is a mgcp gateway and srst setup) this generally takes me about 1
> and a half hour to just complete all configuration ( 1 hour and 30 mins)
> 6) Then I move to Branch 1 ( site B - which is a H323 gateway with srst)
> this ge nerally takes about 45 - 50 mins
> 7) I then move to HQ ( R1 - which is MGCP gateway with srst ) this
> generally takes 20 mins .
> 8) Basic setup of DP , css, aar, NTP , service parameters and enterprise
> para , vlans , dhcp and ip phone registration takes 50 mins
> 9) CUC integ and other config including recording takes 20 mins
> 10 ) CUE integration and trafer setup takes 20 mins
> 11) UCCX integration , One button , script and recording takes 40 mins
> 12) CUPs integration and client setup takes 20 mins
> 13 )I then come back to callmanger and do the media resource setup ,
> gateways added cucm , other configuration such as MVA , RSVP , + dial ,
> adding trunks , unassigned dn setup to CUC - this takes 50 mins
> 14 ) Then I move to the Route pattern setup on callmanger this I do for 3
> sites - HQ , Site B and Site C with or without redundancy on callmanger
> this takes 25 mins
> 15 ) Then do this such as RTMT log collection and indicating informa tion
> in seperate files , MGCP debugs this takes another 15 mins
> 16 ) Switch and WAN QOS this I plan to do only if time permits as this is
> a complex section
>
>
> Questions :
> ===
>
> 1) I barely am able to finish things in time . I have heard from on this
> forum that there are candidates who finish it is 5 - 6 hours . Would anyone
> be able to share with me as to how they do this ?
>
> 2) Even if the above I complete exercises are complete there are sections
> where I miss out on configurations. How do I make sure all config for all
> sections is done correctly?
>
> 3) I really wish I am able to finish the lab in 6 hours so that I can test
> for another 2 hours . Could someone therefore check the above 16 points and
> let me know about the time I can reduce.
>
> 4) As you can see above the router configurations consume a bit more time
> making ( points 5 , 6 , 7 ) . I have tried with both using a notepad to
> type the configurations and then paste & also with typing on cli but both
> these methods take
> around the same time. Please let me know what best method I can use for
> points 5 , 6 , 7.
>
>
> 5) Other suggestions are most welcome .
>
>
>
> Thanks guys in advance for all your help!
>
> Regards,
> Singh
>
>
>
>
> Get Yourself a cool, short *@in.com* Email ID 
> now!
>
> ___
> 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

[OSL | CCIE_Voice] Lab strategy

[singh]

hi Everyone,I need your inputshere. I have been trying to complete mock and 
practice labs in 8 hours . However their I am unable to finishor I finish with 
lab with a lot of mistakes with no time for testing.I also realize that I lose 
thing in the first half and speed up during the end . Generally I take...1) 10 
mins to test if all equipment is working fine( 10 mins)2) read theworkbook 
questions for the next 15 mins3) Make note of the ip addresses and router 
configurationper site in25 mins4) Make note of all cucm configuration , cups , 
unity connection , uccx and cue for another & dial plan20 mins5) Now from point 
5  I start with lab configurations fromBranch 2( site c which is a mgcp gateway 
and srstsetup)this generally takes me about1 and a half hour to just complete 
allconfiguration ( 1 hour and 30 mins)6) Then I move to Branch 1 ( site B  
which is a H323 gateway with srst)this generally takes about45  50 mins7) I 
then move to HQ ( R1  which is MGCP gateway with srst )this 
 generally takes20 mins .8) Basic setup of DP , css, aar, NTP , service 
parameters and enterprise para, vlans , dhcpand ip phone registration takes 50 
mins9) CUC integ and other configincluding recording takes20mins10 ) CUE 
integration and trafer setuptakes 20 mins11) UCCX integration , One button , 
script and recording takes40 mins12) CUPs integration and client setup takes20 
mins13 )I then come back to callmanger and do the media resource setup , 
gateways added cucm , other configuration such as MVA , RSVP , + dial , adding 
trunks , unassigned dn setupto CUC this takes50 mins14 ) Then I move to the 
Route pattern setup on callmanger this I do for 3 sites  HQ , Site B and Site 
Cwith or without redundancy on callmanger this takes 25 mins15 ) Thendo this 
such as RTMT log collection and indicating information in seperate files , MGCP 
debugsthis takes another 15 mins16 ) Switch and WAN QOS this I plan to doonly 
if time permits as this is a complex sectionQuestions :==
 =1) I barely am able to finish things in time . I have heard from on 
this forum thatthere arecandidates who finish it is 5 6 hours . Would anyone be 
able to share with me as to how they do this ?2) Even if the above I complete 
exercises are complete there are sections where I miss out on configurations. 
How do I make sure all config for all sections is done correctly?3) I really 
wish I am able to finish the lab in 6 hours so that I can test for another 2 
hours . Could someone therefore check the above 16 points and let me know about 
the time I can reduce.4) As you can see above the router configurations consume 
a bit more time making ( points 5 , 6 , 7 ) . I have tried with both using a 
notepad to type the configurations and then paste & also with typing on cli but 
both these methods takearound the same time. Please let me know what best 
method I canuse for points 5 , 6 , 7.5) Other suggestions are most welcome 
.Thanks guys in advance for all your help!Regards,SinghG
 et Yourself a cool, short @in.com Email ID now!
___
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

Re: [OSL | CCIE_Voice] Lab strategy

[ccieforme]

I would not say things are "pretty clear".  I'd say partly cloudy..many 
things are clear but there is plenty that is open to interpretation.I find 
this the case with call routing in particular and srst too
-Original Message-
From: "bkvalent...@gmail.com" bkvalent...@gmail.com
Sender: ccie_voice-boun...@onlinestudylist.com
Date: Fri, 20 May 2011 13:50:59 
To: Emin Guliyev; 
ccie_voice@onlinestudylist.com
Subject: Re: [OSL | CCIE_Voice] Lab strategy

___
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

Re: [OSL | CCIE_Voice] Lab strategy

[Cristobal Priego]

i'd say do whatever the question says and if doesn't work the way the
question says you don't get the points


2011/5/20 Emin Guliyev 

> Hey guys,
>
>
>
> I will be going for my 1st attempt this month. Wanted to
> verify some minor details. Are we supposed to configure correct
> cadence/locale on endpoints and gateways? Also, do you lose any points for
> mismatching timezones on UC mailboxes? For afterhours mailbox, are we
> supposed to use schedules on UC and use Closed greeting , or just add a new
> call handler or subscriber?
>
>
>
> Regards,
>
>
>
> Emin
>
> ___
> 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

Re: [OSL | CCIE_Voice] Lab strategy

[bkvalent...@gmail.com]

Emin,

You will not have to guess at what they want you to do.  The instructions will 
be pretty clear as to what will earn you points.  Doing things that aren't 
asked for will not help you, unless they are required for you to accomplish the 
task that is asked of you.  

For example, if a question asks you to build a call handler in CUC, you 
obviously will have to build a port group.  Don't think they care about time of 
day routing or time zones if the question doesn't ask for it.  Does that make 
sense?

If you are unclear about what a question is asking you to do, you should ask 
the proctor.  That is why they are there.

Best of luck on your attempt.

- Reply message -
From: "Emin Guliyev" 
Date: Fri, May 20, 2011 1:23 pm
Subject: [OSL | CCIE_Voice] Lab strategy
To: "ccie_voice@onlinestudylist.com" 

Hey guys,

I will be going for my 1st attempt this month. Wanted to verify 
some minor details. Are we supposed to configure correct cadence/locale on 
endpoints and gateways? Also, do you lose any points for mismatching timezones 
on UC mailboxes? For afterhours mailbox, are we supposed to use schedules on UC 
and use Closed greeting , or just add a new call handler or subscriber?

Regards,

Emin
___
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

[OSL | CCIE_Voice] Lab strategy

[Emin Guliyev]

Hey guys,

I will be going for my 1st attempt this month. Wanted to verify 
some minor details. Are we supposed to configure correct cadence/locale on 
endpoints and gateways? Also, do you lose any points for mismatching timezones 
on UC mailboxes? For afterhours mailbox, are we supposed to use schedules on UC 
and use Closed greeting , or just add a new call handler or subscriber?

Regards,

Emin
___
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

Re: [OSL | CCIE_Voice] Lab Strategy Question

[ccieforme]

As a practice even if I don't use them I go ahead and make the following 
partitions and css, one for each site:
hqlcl pt
Hqoffice pt
Hqld pt
Hqinternational pt
Pstn pt

Hq css
Add all the above partitions.

This does not take very long.  as you build your phones for hq just throw the 
css on their too (one less reboot later).  You can still use the null partition 
for everything and all the pts and css is there in case you need it.  Then add 
your route patterns with the corresponding pt as needed too.
If all sites will use the same rp then keep the pt to none or put it in the 
pstn pt.  When it comes time to block calls its faster just to create a css 
with a blockpt in it and put it on the line.

Of course, there could be a situation where the lab says you can't do this but 
I would not bet on it.  

This is what I have been doing and it has been a time saver for me.  Sure it 
takes a few more minutes but its one less place you have to go back to.

I only use the line for blocking calls.


-Original Message-
From: Gregg Malcolm 
Sender: ccie_voice-boun...@onlinestudylist.com
Date: Wed, 23 Mar 2011 12:27:40 
To: IPX
Subject: [OSL | CCIE_Voice] Lab Strategy Question

___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Re: [OSL | CCIE_Voice] Lab Strategy Question

[Miron Kobelski]

Hi,

My solution is to configure each phone with dedicated css in the beginning,
e.g.:
css hqp1 international
css hqp2 ld
css br1p1 local
css br1p2 ld
Later, I assign partitions to these css as needed.

regards
kobel

On Wed, Mar 23, 2011 at 17:27, Gregg Malcolm wrote:

> As I go through the vol 2 labs, I find myself getting wrapped around the
> axle with device (phone) css'es in UCM.  I'm trying to make a least number
> of repeat touches to the same item and with some of the requirements of the
> labs (translations, etc.) I find myself sometimes struggling with COR.
> Since the phones need to get configured relatively early in the day when all
> of the issues regarding COR might not be obvious, I'm wondering if it's not
> just a good idea to use the line/device approach always (unless asked not
> to).  That way, I can get my dial plan working and hit COR (on the lines)
> towards the end when I know everything is working.  I'd re-test obviously.
> Just wondering what has worked for people and any advantage/disadvantages.
>
> Thanks, Gregg
>
> ___
> For more information regarding industry leading CCIE Lab training, please
> visit www.ipexpert.com
>
>
___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Re: [OSL | CCIE_Voice] Lab Strategy Question

[George Goglidze]

Hi Gregg,

Here's my approach, which doesn't mean it's the best, but it works for me
the best.

I create PT-INTERNAL
and create the following CSS's:
CSS-INTERNAL   < this will be for incoming calls, gw.
CSS-HQ-FULL
CSS-HQ-LD
CSS-BR1-FULL
CSS-BR1-LD
CSS-BR2-FULL
CSS-BR2-LD

All these initially will contain PT-INTERNAL.

Then per-tasks, I add new PT-PSTN-HQ-LOCAL, PT-PSTN-BR1-LOCAL,
PT-PSTN-BR2-LOCAL and add it to corresponding CSS's.
then if I have two sites in USA (same dial-plan), I add for
LD/INTERNATIONAL: PT-PSTN-NANP-LD, PT-PSTN-NANP-INTERNATIONAL
and add to corresponding CSS's...

and it doesn't really take that long time updating the CSS's, I think it
takes more time if you deploy line/device approach at the end, and start to
re-test everything from the scratch... could take up to 20 minutes with the
tests, and then add whatever time it takes you to fix the problems you
encounter.

But again, it's imho.

Regards,

On Wed, Mar 23, 2011 at 4:27 PM, Gregg Malcolm wrote:

> As I go through the vol 2 labs, I find myself getting wrapped around the
> axle with device (phone) css'es in UCM.  I'm trying to make a least number
> of repeat touches to the same item and with some of the requirements of the
> labs (translations, etc.) I find myself sometimes struggling with COR.
> Since the phones need to get configured relatively early in the day when all
> of the issues regarding COR might not be obvious, I'm wondering if it's not
> just a good idea to use the line/device approach always (unless asked not
> to).  That way, I can get my dial plan working and hit COR (on the lines)
> towards the end when I know everything is working.  I'd re-test obviously.
> Just wondering what has worked for people and any advantage/disadvantages.
>
> Thanks, Gregg
>
> ___
> For more information regarding industry leading CCIE Lab training, please
> visit www.ipexpert.com
>
>
___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Re: [OSL | CCIE_Voice] Lab Strategy Question

[adam compton]

Gregg,
I'm kind of in the same boat as you.  To me it seems like it would be easier
to use the line/device approach.  I was assigning internal css to the line
and all other to the device.  That seems to have sped up my time in working
with CSSs, but I would also like to hear some other opinions.

The one thing that caused a problem for me is when one of the ipexpert
questions asked to display external calling number mask for internal
extensions.  I ended up back tracking a lot to get that to work, though that
may just be the nature of the problem.



On Wed, Mar 23, 2011 at 12:27 PM, Gregg Malcolm wrote:

> As I go through the vol 2 labs, I find myself getting wrapped around the
> axle with device (phone) css'es in UCM.  I'm trying to make a least number
> of repeat touches to the same item and with some of the requirements of the
> labs (translations, etc.) I find myself sometimes struggling with COR.
> Since the phones need to get configured relatively early in the day when all
> of the issues regarding COR might not be obvious, I'm wondering if it's not
> just a good idea to use the line/device approach always (unless asked not
> to).  That way, I can get my dial plan working and hit COR (on the lines)
> towards the end when I know everything is working.  I'd re-test obviously.
> Just wondering what has worked for people and any advantage/disadvantages.
>
> Thanks, Gregg
>
> ___
> For more information regarding industry leading CCIE Lab training, please
> visit www.ipexpert.com
>
>
___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

[OSL | CCIE_Voice] Lab Strategy Question

[Gregg Malcolm]

As I go through the vol 2 labs, I find myself getting wrapped around the
axle with device (phone) css'es in UCM.  I'm trying to make a least number
of repeat touches to the same item and with some of the requirements of the
labs (translations, etc.) I find myself sometimes struggling with COR.
Since the phones need to get configured relatively early in the day when all
of the issues regarding COR might not be obvious, I'm wondering if it's not
just a good idea to use the line/device approach always (unless asked not
to).  That way, I can get my dial plan working and hit COR (on the lines)
towards the end when I know everything is working.  I'd re-test obviously.
Just wondering what has worked for people and any advantage/disadvantages.

Thanks, Gregg
___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com