Greetings and welcome to the this instructorial. My goal here is two-fold. To help my aging brain remember the things I should do when verifying call functionality and help others who are not sure what they should be testing. When you do software upgrades on Cisco Unified Communications Manager, firmware upgrades on phones, IOS upgrades on Cisco ISRs, or have made any type of configuration change that could affect calls it is always best to test! This is especially useful for testing after a port or SIP turn up. There is an old saying,"If you didn't test then you didn't finish....." Listed below are the various numbers and test plans that I do for the various collaboration applications.
Total Time Needed: 30 Minutes
1 - Record a message and play it back. You can stop the recording with #
The local dialing depends upon the specific configuration on your system. The first thing to discover is the access code. What digit do they have to dial first to dial out? This is usually 9 but I have seen 8, 7, or no access code. So what number do you dial? When I am traveling and do not have a local number on me I simply go to google maps and lookup the closest Walgreens. I then dial the local Walgreens number to verify local outbound dialing is working.
If your calls are going through a Cisco Unified Border Element or an ISR I recommend grabbing a debug for each call as well. It is always nice to have a reference for what good looks like when stuff hits the fan later. If you document good now then you have a reference for the bad that may come later.
Step 2 : Enter the HowTo Schema description and add a relevant image
Enter the HowTo Description with a relevant image to your description.
Step 3 : Configure the Advanced settings. ie Total Time, Estimated Cost, Materials, Tools
Enter Total Time, Estimated Cost, Tools & Materials
Step 4 : Enter the Steps for your HowTo Schema
Steps for your HowTo Schema instructions. It can be a single step (text, document or video) or an ordered list of steps (itemList) of HowTo Step.