CCIE VOICE WORKBOOK - 3.0 - File3

Chapter 8 - Media Resource Management
8STMGWMRGPYHIHMRXLMWGLETXIV
A. Conference bridge software and hardware
B. Transcoder
C. MTP
D. MOH
8EWOWXSEGGSQTPMWL
l. Configure conferencing for the HQ site to use hardware
based resources in the the HQ gateway first then
hardware resources in the BRl gateway.
2. Configure conferencing for the BRl site to use
hardware based resources in the the BRl gateway first
then hardware resources in the HQ gateway.
3. Configure transcoding for the HQ site to use hardware
based resources in the the HQ gateway first then
hardware resources in the BRl gateway.
4. Configure transcoding for the BRl site to use hardware
based resources in the the BRl gateway first then
hardware resources in the HQ gateway.
5. Configure MOH for HQ site based on unicast and
streamed from the publisher CallManager.
6. Configure multicast MOH for BRl, based on G729 codec
from the subscriber, and streamed from the BRl
gateway.
7. Allow l0 simultaneous meet me conferences for the HQ
users, in the numbers of l20l~l2l0. Every meet me
conference should allow a maximum of five
participants.
Chapter 8 Media Resource Management
CCBOOTCAMP`s CCIE Voice Lab Technology Workbook 2009 103
8. Make sure that when the initiator of an Ad~Hoc
conference hangs up, the conference is terminated.
7SPYXMSRW
Use the following for tasks l ~ 4:
In order to utilize hardware based resources in the
gateways we need to enable several key services on the
gateway and add the resources to CallManager.
The services that need to be enabled on the gateway are the
DSP services for DSPFARMS, the DSPFARM profiles, and the
SCCP application service{repeat for HQ and BRl|:
Enable DSPFARM services:
Enable DSPFARM profiles:
Enable SCCP Applications services:
TIP: Note the name "HQTRANS" and "HQCONF" in the associate
profile command above. This is the device name we will need
in CallManager to register these resources. For PVDM2
resources we will select "IOS Enhanced" in CallManager.
These are case sensitive and must match exactly.
Now we can add the resources in CallManager{repeat for HQ
and BRl|:
At this stage we have previously defined the media resource
groups for the software resources and a media resource list
for each site. We will need to add two groups for the new
resources based on site and then add them in the proper
order in the site media resource list:
Now for the media resource group lists:
5. For this we need to separate the MOH into two groups, one
for the subscriber and one for the publisher. The
publisher will be used to provide MOH for the HQ site. We
also need to enable G729 for the "Cisco IP Voice Media
Streaming App" service:
The previously created software groups included the MOH for
each server. We will want remove this from the current
media resource group and move each MOH server to its own
media resource group:
We will then want to enable the sample audio source for
multicasting:
Click the "Allow Multicasting" checkbox:
We will now need to turn multicast on for the MOH server by
checking the "Enable Multicast Audio Sources on the MOH
Server" checkbox and setting the "Max Hops" to "l" so we
don't send the stream across the WAN:
Next we will need to enable the media resource group for
the subscriber MOH server, created in previous step, for
multicasting by checking the "Use Multicast for MOH Audio"
in the media resource group page:
Now we will need to add these newly created media resource
groups for MOH to the media resource list for HQ and BRl.
The HQ site will get the "Pub~MOH" group and the BRl site
will get the "Sub~MOH" group:
6. This should cover the MOH for the HQ site. However we
still need to allow BRl access to the multicast stream even
though we are not allowing multicast across the WAN. This
is accomplished by utilizing the MOH settings in the SRST
configuration:
You will notice the port number used is "l6386" and not the
default of "l6384". This is due to the fact that we are
telling the phone to listen to G729 audio stream and not
the default G7llulaw. Also, we told the MOH server to count
by port and not be IP address.
Since the audio stream list the order for the codecs as
G7llulaw, G7llalaw, and then G729 we would need to
increment the port by 2 to "l6386". If told to do it by IP
address we would then have used 239.l.l.3 with the default
port of "l6384".
We also need to support multicast by adding the global
configuration command "ip multicast~routing" on the BRl
gateway and adding the "ip pim dense~mode" on interface
where we are streaming the MOH.
7. In order to setup the Meet~Me conference bridges we need
to first define a partition for "HQ~Meet" and then the
requested numbers under the Call Routing~>Meet~Me Number/
Pattern:
In order to limit the number of participants we need to go
to the CallManager service parameters:
We would then to to go back to every HQ Calling Search
Space and add in the new "HQ~Meet" partition except for the
AAR CSS{repeat for all HQ CSS|:
8. You can change the Ad~Hoc conference limitations from
the CallManager service page:
8VSYFPIWLSSXMRKXMTW
Learn useful IOS command like "show sccp" and "show
dspfarm"
You may need to reset the device pools and MOH server
in order for changes to take effect. If you notice
something is not working you should reset the services
before trying to make changes.
Chapter 9 - QoS Considerations
A. L2/L3 classifications and policing
B. Queuing mechanisms
C. LFI
D. Catalyst switch QOS
8EWOWXSEGGSQTPMWL
l. Make sure that SCCP is set to DSCP CS3 and that it is
maintained while traversing HQ and BR2. Marking should
be done by the endpoint when possible.
2. Limit SCCP traffic in the BR2 to 30k per endpoint,
overloads should be marked down to AFll.
3. Configure the frame relay link between HQ and BRl as
if it is 384k in bandwidth, make sure you enable MLP
LFI on it.
VoIP signaling should have 5% of the line as
guarantied bandwidth.
VoIP barrier should have 30% of the line as priority
bandwidth.
All other traffic should be weighted fair queued.
4. Configure the frame relay link between HQ and BR2 as
if it is l200k in bandwidth.
VoIP signaling should have 60k of the line reserved
bandwidth.
Chapter 9 QOS Considerations
VoIP barrier should have 360k of the line priority
bandwidth.
All other traffic should be weighted fair queued.
5. The BRl gateway should send the signaling and RTP
traffic marked as CS3 and EF.
7SPYXMSRW
l. First let's set the marking for our endpoints, which
are the IP phones and the CallManagers.
Under CallManager enterprise parameters you will find
all DSCP related settings, as shown:
As you can see, in version 7.0, the default marking is
set to CS3 and therefore it is not necessary to change
anything. The HQ 3750 will need to be configured to
trust the ports with IP Phones on them and the COS~
DSCP map modified to put CS3 {24| into the proper
queue.
First we need to enable the MLS QoS:
HQ~3750{config|#mls qos
The we need to set the proper interfaces to trust the
IP Phones:
HQ~3750{config~if|#auto qos voip cisco~phone
We can the modify the default COS~DSCP map to the
following{default map is 0 8 l6 26 32 46 48 56|:
HQ~3750{config|#mls qos map cos~dscp 0 8 l6 24 32 46 48 56
As for BR2, since we can't define the exact marking of
DSCP in CME, you will need to mark the SCCP traffic as
CS3 when it enters the HWIC.
This can be done by creating a policy map and
attaching it to the ports that have IP Phones behind
them:
Use an access list to match SCCP traffic:
Class and policy map that will mark the SCCP to CS3:
And then assign it to a port as inbound service
policy:
2. On the BR2 gateway we need to modify the policy
created in task l so it will do the two requested
tasks:
The assignment to the ports shouldn't change.
3. This task will require creating MLP LFI link between
HQ and BRl.
Although the task can be accomplished using frame
relay traffic shaping, in here we request something
else.
First let's create the class and policy map for the
requested specifications:
TIP: These commands are common to both routers and
should be copied to notepad for time saving purpose.
Then create the frame relay traffic shaping class:
Now create the virtual template for BRl:
And for HQ:
Until now all the commands are equal in both routers
except from the IP address which is unique to every
router.
Now let's assign it to the routers interface, first to
the HQ:
And then to the BRl:
You can verify that it is configured by issuing the
following commands:
For more reference please use the QOS SRND at:
http://www.cisco.com/go/srnd
4. Here you need to create regular frame relay traffic
shaping with LLQ but no MLP or FRF, this is because
the link between HQ and BR2 is more then 768k
bandwidth.
You would start by creating policy map with the
required bandwidth values {the class map created in
task 3 is good for here as well, so no need for
another class map|.
Then create a frame relay map class and assign the
policy map to it, as shown:
Finally assign the frame relay class to the relevant
interface, for HQ it would be:
Complete BR2 side as well, remember the frame relay
traffic shaping on the base interface.
TIP: you can also save precious time by reusing the
policy~map and the map~class in the BR2 router.
You would use almost the same verification commands:
show policy~map interface
show policy~map
5. For BRl, you need to put in the following commands
under the dial~peers that would send traffic across
the WAN{media is already sent with DSCP EF|:
8VSYFPIWLSSXMRKXMTW
Always verify using the "show policy~map interface"
command.
Make sure you don't mix the 'bandwidth' from the
'priority' commands in the policy map.
Don't forget the class~default.
Chapter 10 - Unity Connections
A. Unity Connections Voicemail Integration
B. Unity Connections Administration
8EWOWXSEGGSQTPMWL
l. Configure voicemail for HQ and BRl based on the Unity
server using the following parameters:
Pilot ll70, port ll7l~ll74, MWI on ll80, MWI off
ll8l.
2. Make sure you prevent Unity Connections from calling
to itself and creating call loops which consume the
available ports.
3. Configure voicemail box for IP Phones l and 2 in HQ
and BRl, use phone password of l47369 for all users.
4. Configure auto attendant for HQ with DN l000. It
should have a customized greeting that allows dialing
an extension and walking through the users directory
by pressing l. When users press 0 they should be
forwarded to extension l00l. During closed times,
assume normal weekday schedule, it should take a
message and store it in HQ Phone l mailbox.
Chapter 10 Unity Connections
5. Set on BRl Phone 2 second line with extension *2002,
the call coming to the primary line should go to this
line if the primary is busy. The user should be able
to use this line for voicemail access. Do not use any
alternate extensions.
6. Configure BR2 CME to use the local Unity Express as a
voicemail, using the following parameters:
Pilot 3l80, port 3l9l~3l94, MWI on 3l90, MWI off
3l9l.
7. Create voicemail for BR2 IP Phone l and 2. Use blank
phone password for all users.
8. Create an auto attendant for BR2 that will work when
DN 3000 is dialed.
9. Make sure that calls from HQ can go via IP and hit the
AA in BR2.
7SPYXMSRW
l. Start by setting the required definitions on the
CallManager, e.g. voicemail ports, pilot, profile,
line group and hunt list and message waiting numbers.
Start by creating the voicemail ports using the "Cisco
Voice Mail Port Wizard", as shown:
Keep the proposed name and click next:
Then the correct number of ports {which is four|, as
shown:
Then set the required settings for the ports and click
next:
Set the starting directory number, external phone
number mask, Etc...:
Now select yes to add the ports to a line group:
Click next to accept the default line group name:
You will then see the following summary screen. Click
next to continue:
You have now added the voicemail ports and line group.
Click the link to add the line group to a hunt list:
TIP: Typical voicemail issues with things like MWI are
normally derived from improper voicemail port
configuration. Make sure you select the correct
settings when configuring your voicemail ports and
pilots.
Now we can add a new hunt list called "Voicemail":
We can now add the line group created by the voicemail
port wizard to the newly created hunt list:
Now we need to create the hunt pilot and point it to
our hunt list:
We can now modify our "Default" voicemail pilot with
our new hunt pilot:
We should also check our default voicemail profile
ust to make sure all the changes have taken affect:
TIP: by marking the check box "Make this the default
Voice Mail Pilot for the system", you will save the
time required to configure the voicemail profile.
Now you should define the MWI on and MWI off as shown:
We now need to create a user group with AXL user
rights. We start by creating the user group:
Now that we have created the user group we can now
assign the AXL role to this user group:
Click the "Assign Role to Group" button:
Select the "Standard AXL API Access" and click "Add
Selected":
We now have a user group with AXL rights:
Next we need to create a user account and assign it to
the AXL user group we ust created:
You will now need to create each user that needs voice
mail and associate their phone to their user within
CallManager. You will also need to set their "Primary
Extension" field and allow them "Standard CCM End
User" access:
Now you are ready to configure the Unity Connections
server:
First off lets activate all the required services
through the "Serviceability" site:
Click on the "Telephony Integrations" then on "Port".
Click "Add New" ports and the select the desired
number of ports and click "Save":
Next you will need to go to the "Port Groups" sections
and edit the default port group. Enter the MWI on and
MWI off number that were previously defined in
CallManager and click "Save":
Now we need to edit the port group "Servers" through
the Edit~Servers screen and add in the second
CallManager:
We can now go to the "Phone System" section and edit
the default phone system:
2. To prevent loops check the "Enable for Forwarded
Message Notification Calls" checkbox:
We can now set the AXL configuration in the following
screen:
3. This should allow us to now set the default password
in the user template and then import all the users
we previous defined in CallManager:
TIP: This completes task 3 and you can check the
configuration by accessing voicemail from any phone
and logging in with the default password.
4. We now need to create an auto attendant {call
handler| with extension l000:
Click the "Add New" button to create a new call
handler and fill in the required information:
We can now set the extension and schedule for our call
handler and click save:
We can now edit the caller input to match our
requirements:
When "0" is pressed we should attempt a transfer for
extension l00l:
When "l" is pressed we should be send the directory
call handler:
We should now see the following for caller input:
We need to now enable the closed greeting and set the
action to take a message:
We now need to set the message recipient to be HQ
Phone l {Edit Message Settings|:
We now need to define a CTI route point in CallManager
for extension l000 and forward all calls to this
extension to voicemail:
Set all the required settings for a HQ device:
Now set the line parameters per the requirements:
We can now test calls to extension l000 and make sure
we can transfer out to extension l00l by pressing "0".
Also, we can test that we get the directory handler by
pressing "l" and then being transfered to the
extension after selecting a user from the directory.
5. First we need to create a voice mail profile that
strips the "*" from the extension when entering
voicemail{remember we can't use alternate
extensions|:
We can then change the call forward settings on line l
of BRl Phone 2:
Once this is accomplished we need to create the send
extension of "*2002" on BRl Phone 2 and set the
special voicemail profile on the line:
We should now be able to test our configuration by
selecting BRl Phone 2, on line 2, and pressing the
voicemail button.
6. Our first step is to define some the of the needed
CME configuration for CUE. This includes the
voicemail number under "telephony~services", the MWI
On and MWI Off extension, and the dial~peer for
accessing CUE. You should also enable the ability to
manage CME from CUE by defining a web admin user and
enable DN and Time web editing. You should also
create users under each ephone that will have a
voicemail box:
Next we will need to initialize CUE for configuration
by first setting up IP access through the CLI on the
BR2 router:
We should now be able to session to the CUE module
using the "service~module Service~Engine l/0 session"
command. We can now initialize the CUE module:
The CUE module is now ready for access. You can access
the CUE module by going to the IP address of the CUE
in a web browser.
Once we have accessed the interface we will need to
login with the username and password we specified
during the previous step:
You should see the following:
Select the "Run Initialization Wizard" and fill in the
required information:
Make sure you select to import both users as well as
create a mailbox and set their call forward settings:
Make sure you select the "Blank password" and "Blank
PIN" options:
Make sure you select "Outcalling" as the SIP MWI
Notification Mechanism:
You can now commit all the settings by check the box
at the bottom and clicking the "Finish" button:
You will see the following screen indicating that your
configuration was successful.
7. You should now be able to access voicemail from the
BR2 IP Phones.
8. In order to route DN 3000 to CUE we need to create
another dial~peer and send it to the CUE module:
We then need to add the Auto Attendant in CUE:
We can modify the default Auto Attendant since we are
not asked to create a custom scripts:
Set the extension on the Auto Attendant and click
"Apply":
9. This requires creating a transcoding mechanism on
the CME since CUE only support G.7ll and the VoIP
calls would be G.729. In order to allow transcoding
you should define the following on BR2:
This should allow the calls to go from HQ, over IP, to
the CUE AA script. Make sure you allow the H323 to
SIP!
8VSYFPIWLSSXMRKXMTW
l. You should also know how to perform a password
recovery on the CUE as well as set the configuration
back to default.
2. Use the "show sccp" and "show dspfarm profile" command
to verify your transcoder is registered and ready for
use.
3. You may also need to enable supplementary services
depending on what you are asked to do. Know what these
are and how they work.

CCIE VOICE WORKBOOK - 3.0 - File3

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CCIE VOICE WORKBOOK - 3.0 - File3

Uploaded by

Copyright:

Available Formats

Chapter 8 - Media Resource Management

You might also like