I will be attending this training in Boston and have gone through the training description. However I had a question and would like to know from someone who has attended it before or someone from Cisco.
One of the objective covered is:
Develop complex scripts providing IVR treatment, collecting digits, and performing database lookups ----> Since this is a 2-day training how much focus is on script training? Or how many scripts are given for practice?
I attended the training back in March. I gained a lot from the training. I'd like to take it again or another class building on what I learned. I think the class is beneficial no matter what level of scripting experience you have. I still consider myself a beginner. I recommend the reporting class too. It is important to learn how to script with reporting in mind.
Also, be sure to get the driving directions from your Learning Partner or from Cisco directly. Don't use Mapquest...they'll lead you way off the beaten path.
I went that way when I arrived. You should be fine going that way. It's a little out of the way, but you avoid the tolls. I went to Cisco's site where they are using Mapquest now. It looks like it's been fixed. Mapquest directions use to send you to their back entrance...way out in the country. I would be sure to use the Beaver Brook Road (Site II) directions and not the Mass Ave directions (Site I). As soon as you exit onto 111, it's either one or two traffic lights before you'll need to make a right. If you pass a Holiday Inn, then you went the wrong way at the exit. Then, it's like a mile before you'll turn left onto Beaver Brook Road.
I went a different way to get back to the airport. I had to use tolls, but I think the route was good overall. It was using I-90. You would take I-495 North coming from the airport.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...