brkvvt-2022 cl09 v05 Web

Understanding Cisco
Unified Communications Manager

Media Resources
BRKVVT-2022
Presentation_ID © 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 1
Cisco Unified CM Media Resources
Speaker Intro
Brett Wiggins, CCIE R&S

Technical Marketing Engineer,
Voice Systems Engineering
Where Is the UC SRND?

http://www.cisco.com/go/designzone 
Design Zone for Unified Communications
Agenda
 Media Resource Types

 Media Resource Providers
 Unified CM Resource Selection
 Design Considerations
Conferencing
Transcoding
Media Termination Points
Music on Hold
Annunciator
Five Types of Media Resources discussed in
this presentation
 Conference Bridges
Audio (CFB)
Video (VCB)
 Transcoder
(XCODE)
 Media Termination Point

(MTP)
 Music on Hold
(MOH)
 Annunciator
(ANN)
Media Resource Considerations
 Media Resources
• Hardware-based
• Software-based
 Deployment Models
• Centralized:
Media flows to the central site over company WAN increasing
BW requirements put perhaps save in hardware costs by
aggregation.
• Distributed:
Save in WAN BW by local media services but perhaps at a
higher cost.
Media Resources NOT covered
 Media Resources we are NOT going to cover

in this presentation.
Trusted Relay Point (TRP)
RSVP Agent
 IPv6 Media Resources

IPv6-specific UC SRND due out on CCO shortly and
will be located here:
http://www.cisco.com/go/designzone
Agenda

Conferencing
Transcoding
Music on Hold
Annunciator
Acronyms
DSP = Digital Signal Processor ( DSPs take real-time analog voice signals, and
digitize them for traversal on the IP Network)
IPVMSA = IP Voice Media Streaming Application
ISR = Integrated Services Router (Cisco 18XX, 28XX, 38XX Series Routers)
HDV2 = High Density Voice module rev2 (module for ISR Series)
PVDM2 = 2nd Generation Packet Voice DSP Module (DSP SIMMs for
HDV2 module and ISR motherboard)
CMM = Cisco Media Module (‗Router on a blade‘)

ACT = Advanced Conferencing and Transcoding module (DSP card for
CMM)
MCU = Media Control Unit (Cisco 35XX Video Conferencing series)

EMP = Enhanced Media Processors
MPE-VT = MeetingPlace Express Video Telephony (Server based Video

Conferencing – done in software)
Media Resources
Hardware-based and Software-based
 Hardware-based  Software-based
ISR + PVDM2 IPVMSA
HDV2 + PVDM2 MPE-VT
VGD-1T3 + PVDM2 Cisco IOS® software-based
resources
MCU + EMP
End-Of-Sale hardware-based options available in Unified CM

version 7.1(2):
• CMM + ACT
• Cisco Catalyst® WS-X6608-T1 and WS-X6608-E1
• HDV + PVDM
Integrated Services Routers Hardware-based
 ISR Series can provide:

• Audio Conferencing (Secure and non-Secure)
• Transcoding
• Media Termination Point
• MoH from flash
 Can be deployed centrally or at remote sites.

 Performance of these services is minimally impacted by
load – conferencing and transcoding done in hardware
(PVDM2)
 PVDM2 configured in Unified CM Administration as
―Cisco IOS Enhanced‖ (CFB/MTP/XCODE)
 Communicates with Unified CM using SCCP.
PVDM2 DSPs Hardware-based
More Information:
BRKVVT-2010: Designing
 Installed on: UC Gateways and DSP
Engineering in Enterprise
1) ISR motherboard Networks
2) NM-HDV2, in an ISR Network Module slot
 Different flavors of PVDM2 depending on how many physical

DSPs it contains.
PVDM2-8, PVDM2-16, PVDM2-32, PVDM2-48, PVDM2-64
PVDM2-32 (2 DSPs)
NM-HDV2-2T1/E1 PVDM2-64 (4 DSPs)
VGD-1T3 + PVDM2 Hardware-based
 As of Cisco IOS 12.2(24)T can be used for Conferencing,

Transcoding, & MTP
 Would be deployed centrally.
 Performance of these services is minimally impacted by load –
conferencing and transcoding done in hardware (PVDM2)
 PVDM2 configured in Unified CM Administration as ―Cisco IOS
Enhanced‖ (CFB/MTP/XCODE)
 Communicates with Unified CM using SCCP.
VGD-1T3 VGD-FC
AS5X-PVDM2-64
How Many DSPs Do I Require? Reference
DSP Calculator Tool
http://www.cisco.com/cgi-
bin/Support/DSP/cisco_dsp_calc.pl
Configure Router Configure Options Results

Cards and Voice Conf, Xcod, MTP, Analog DSP Cards and # DSPs
Termination channels Reservation, IP SLA
Cisco 35xx Videoconferencing Series Hardware-based
 3515 and 3545 MCU

 The MCU provides the following media services:
Video conferencing
Audio conferencing
 The Video MCU can be configured as a media resource
for Unified CM
The MCU is only able to register with Unified CM as an ad-hoc
video resource using SCCP
IP Voice Media Streaming App Software-based
(IPVMSA)
 Service can be enabled per

Unified CM Subscriber node.
 Service not enabled by default.
 All functions are performed in
software.
 Provides:
1) CFB
2) MTP
3) MoH
4) ANN
IPVMSA Software-based
Default Devices
CFB
MTP
MOH
ANN
Meeting Place Express – Software-based
Video Telephony (MPE-VT)
 Software Installed on Media Convergence
Server (MCS)
 Provides the following media services:
Video conferencing
Audio conferencing
 Configured as a media resource for Unified
CM
MPE-VT is only able to register with Unified CM as an
ad-hoc video resource using SCCP
 Licenses dictate the difference between an
MPE install and a MPE-VT install
Media Resources
Deployment Options
Cisco
Unified CM
Cluster
PSTN
Conf Conf
IP WAN
Central Site Remote Site
 NM-HDV2 + PVDM2  NM-HDV2 + PVDM2

 VGD-1T3 + PVDM2  ISR + PVDM2
 MCU + EMP  MPE-VT
 IPVMSA
 MPE-VT
Many Different Providers Reference
Functionality Provided by:

ISR + PVDM2
CFB HDV2 + PVDM2
VGD-1T3 + PVDM2
IPVMSA
MCU + EMP
VCB MPE-VT
ISR + PVDM2
XCODE HDV2 + PVDM2
VGD-1T3 + PVDM2
ISR + PVDM2
HDV2 + PVDM2
MTP VGD-1T3 + PVDM2
IPVMSA
IPVMSA
MOH ISR
ANN IPVMSA
Not recommended
Agenda

Conferencing
Transcoding
Music on Hold
Annunciator
Selection of a resource
 Media Resource Group (MRG)
 Media Resource Group List

(MRGL)
MRG defines a pool of resources
 Available resources are administratively selected for each MRG
 Devices inside the MRG are not ordered by priority
 Multiple types of Media Resources can be placed into the same
MRG
 A resource may be listed in multiple MRG‘s.
 Devices that are not listed in any MRG are left in a general pool.
MRGL’s are a list of MRG’s
 Top down order of the MRG‘s

indicates priority
 Arrows on right allow order to be
adjusted
 MRG‘s can be added to multiple
MRGL‘s
 MRGL is defined for: Phones,
Trunks, Gateways, Etc.
 MRGL can be defined at:
Line
Device
Device Pool
System Default
(Most specific has precedence)
Unified CM Resource Selection
Media Resource Group Lists and Media Resource Groups
User Needs
Media
Media Resource
Resource
Manager
Configuration Order
Media Assigned to Device
Resource Directly or via
Group List Device Pool
(MRGL)
1st 2nd
Choice Choice
Media Media
Resource Resource
Group Group
(MRG) (MRG)
1st 2nd 1st 2nd
Choice Choice Choice Choice
Media Media Media Media

Resource Resource Resource Resource
1 2 3 1
Device Selection Within an MRG
 MRM will walk through the MRG in this order: MRG-A first, if
resource in MRG-A is exhausted then MRG-B, if resource in
MRG-B is exhausted then MRG-C
 The resource in each MRG is round robin based on the most
available capacity of each device
XCOD, MTP, MOH, ANN, selection tracks individual sessions active on
a resource.
CFB Selection tracks the number of conferences active rather than total
number of participants.
 Secure Conferencing: Pick a secure CFB first if the initiating device
is secure. Skip through / over MRGs to do this.
 Video Conferencing – more on this later …
Group Resources by Type
Resource_List I Would Like to Conference to

“Phone C”. Is There Any
Conference Resource
Software MRG Available?
MTP1
1 MTP2
SW-CONF1 A B
SWCONF2
RTP
Hardware MRG
XCODE1
2 XCODE2
HW-CONF1
HW-CONF2
Result C
MOH MRG Use All Software Conference
3 MOH1
Resources First, then Hardware
MOH2
Conference Resources
Group Resources by Location
Dallas_List SanJose_List
Dallas MRG SanJose_MRG

XCODE1 XCODE2
1 HW-CONF1 1 HW-CONF2
MOH2 MOH3
Hub_MRG Hub_MRG
MTP1 MTP1
MTP2 MTP2
2 MOH1 2 MOH1
SW-CONF1 SW-CONF1
SW-CONF2 SW-CONF2
SanJose_MRG Result Dallas MRG

XCODE2 Devices Use XCODE1
3 HW-CONF2 3 HW-CONF1
MOH3 Resources at Their MOH2
Location First
Restrict Access to Conference
Resources
Resource_List NO_CONF_List
MTP MRG MTP MRG

1 MTP1 1 MTP1
MTP2 MTP2
CONF MRG
MOH MRG
SW-CONF1
2 SWCONF2 2 MOH1
MOH2
HW-CONF1
HW-CONF2 Result
XCODE MRG Device Cannot Use
MOH MRG 3 XCODE1 Any Conference
3 MOH1 XCODE2
Resources
MOH2
XCODE MRG
4 XCODE1
XCODE2
Agenda

Conferencing
Transcoding
Music on Hold
Annunciator
Conferencing
 How Are They Invoked?

 Conferencing Design Hints
 Secure Conferencing Considerations
 Video Conferencing Considerations
Four ways to invoke Ad-hoc conference
1) Using the button

2) Using the and buttons
3) Initiate a conference
4) Using Barge functionality
1) Using the button:

With initial call established, hit button
Dial a third party, then hit again (after or before they answer)
2) Using the and buttons

See the following steps:
1. Place or receive a call 2. Place or receive a 2nd call 3. Highlight #2, press (Select) 4. Highlight #1, press (Join)
Invoke a Meet Me conference
3) Initiate a conference
The MeetMe pattern or directory number must be
administratively configured in Unified CM
MeetMe conferences are created by going off-hook then

pressing and dialing your MeetMe pattern
4) A) Using Barge functionality: BARGE
392-5555
C PSTN
392-5555
SHARED LINE
 A phone with the Barge softkey can join a call that is active on
another phone on a line shared between them.
 Note: No Media Resources used! The conference is performed
locally on the IP Phone that had the active call.
 This conference capability is only for the barge functionality.
4) B) Using Barge functionality: cBARGE
392-5555
PSTN
C
392-5555
SHARED LINE
 A phone with the cBarge key can join a call that is active on another phone
that shares that line. (Display indicates: ―Remote In Use‖)
 The conference is performed by a regular conferencing Media Resource
external to the phone.
 The phone that had the original call acts as a ―conference initiator‖.
 The conference thereafter behaves like a regular conference.
 Secure phones must use cBarge rather than Barge
Conference Chaining
Linked Conference Operation
 Conferences are not combined – an RTP stream is set up between

the different conferences. This feature allows one conference to be
a participant in another conference.
 Not enabled by default (see next slide).
 A conference shows up as ―Conference‖ in the participant list.
 Introduced in Unified CM Release 4.2(3) / 6.0.
Enabling Conference Chaining
 To enable Conference Chaining, you must set the
cluster-wide Unified CM service parameter ―Advanced
Ad-Hoc Conference Enabled‖ to ―True‖.
 By default a maximum of two conferences can be
added to a conference. This is referred to as linear
conference chaining.
Conferencing

Centralized Conferencing Resources
Cisco
X Unified CM
PSTN cluster
A
IP WAN
B Central
Conf Site
Remote Site
 External caller X calls A – note: no voice across WAN

 A conferences B in
 Three voice streams across WAN
 No media survivability if WAN goes down

Distributed Conferencing Resources
Cisco
MRGL Unified CM MRGL
Cluster 1. HQ1
1. Br1 X 2. HQ2
2. HQ1 PSTN
3. HQ2
A
A
IP WAN
B
B
Device Device
Conf Conf
Pool Conf Pool
MRG=Br1 Conf Conf
Branch
MRG=HQ1 MRG=HQ2 HQ
 Conference between A, B, and
X – No voice across WAN
 Requires extra hardware
at branch MRG = Media Resource Group
MRGL = Media Resource Group List
 Media survivability during
WAN failure
Presentation_ID © 2009 Cisco Systems, Inc. All rights reserved. 40
Cisco Public
Conference Resource Placement
Unified CM
Centralized DSPs Cluster
• High-speed
X
PSTN
WAN links
A
• Remote sites are
limited to the
amount of IP WAN
bandwidth Central
Site
provisioned for B Branch
Conf
MRG
conferencing
Bandwidth vs. Hardware Unified CM
Cluster
Distributed DSPs X PSTN
• Distribute CFBs A
and VCBs to large
sites
• Endpoints use IP WAN
their local resource
• Single site calls
B Conf
Conf Conf
stay local Branch MRG Conf Conf

Central
MRG MRG Site
Conferencing Providers

ISR + PVDM2
CFB HDV2 + PVDM2
VGD-1T3 + PVDM2
IPVMSA
Not recommended
PVDM2 CFB Codec Support
 The ISR with PVDMs can support conferencing with:
G.711u and a-law variants, G.722-64
G.729 – All variants, iLBC
 PVDM2s select and mix the three loudest speakers.
 Mixed Mode conferences (any codec) do not require
transcoding resources, however capacity is decreased.
More Information:
PVDM2 CFB Scalability BRKVVT-2010: Designing
UC Gateways and DSP
 Number of conferences (sessions) per DSP depends Networks
on ―maximum conference-participants‖ and ―codec‖ configuration:
Max G711 Only G722-64 G729 iLBC

Participants Sessions Sessions Sessions Sessions
32 2 n/a n/a n/a
16 4 1 1 n/a
8 8 2 2 1
 Each DSP is treated individually – PVDM2 boundaries are irrelevant

 No CLI/manual control over individual DSP allocation
 Conf/Xcod DSP availability checked at configuration time
 Example:
Conferencing: Four DSPs
PVDM2-64 (4 DSPs)
• Up to 32 G.711 Conferences/Sessions
with 8 participants each (32*8 = 256
participants total), or
• Up to 8 G.711/G.729A Conferences (8*8
= 64 participants total)
IPVMSA CFB Codec Support
Functionality Supported Default
Wideband Wideband
CFB G.711a / G.711µ G.711a / G.711µ
 No support for G.722.

Note: ―Wideband‖ refers to Cisco Wideband (proprietary) and
does not refer to G.722.
 Can perform mixed mode conferences
 Typically not recommended for CFB
 Capacity controlled via IPVMSA CFB Service Parameter
―Call Count‖. This parameter specifies the maximum number
of conference participants that the conference bridge will
support.
Reference
Conferencing Operation and Design
• To offload central software conference bridge servers
When
• To keep conferences between participants at a remote site from
Necessary
crossing bandwidth-constrained (WAN) links
• Conf participants at same site – Local
Where Located
• Conf participants at different sites – Depends on network arch.
Selection • Based on the location of the initiator of the conference except for
Algorithm cBarge
• Single-mode: Conf participants all use same Codec (usually G.711)

• Mixed-mode: CFB receives multiple codecs at once
Codecs • Codec chosen for a call leg between an endpoint and a conference
bridge is determined by the regions configuration in Unified CM
• Unified CM will engage transcoder for codec mismatches
• Densities vary: Router/Device model, CPU and DSP vintage
• With hardware, Conferencing requires dedicated DSPs
Other • No HW conference in Survivable Remote Site Telephony (SRST)
Considerations (only three-party SW conference)
• Ad-hoc vs. MeetMe traffic patterns are different
• Two-party conf maintains DSP for MeetMe; releases for Ad-hoc
Conferencing

Secure Conferencing Requirements
 Secure Conferencing is available as of Unified CM 6.0

 Secure Conferencing is only supported using PVDM2
Hardware.
 Cisco IOS 12.4(11)XW or later, Advanced IP Services
or Advanced Enterprise Feature Sets
Secure Conference Operation
Benefits
 Secure Conferencing allows for both encrypted media and
signaling between Unified CM, the conference hardware and IP
phones.
 Secure Conferencing supports Conference Chaining.
 Each participant joined to the conference has an independently
keyed RTP Stream. Not everyone has to be secure.
 Works with Ad-Hoc and Meet-Me Conferences as well as those
created during a cBarge operation.
 For Meet-Me patterns you are now able to set a Minimum security
level.
Drawbacks
 Decreases the number of conferences you can support. One per
DSP.
 Can be challenging to configure if you are not familiar with the
Cisco IOS command syntax or loading certificates into Unified CM.
Conference Security Levels
Secure Conferencing
 Each participant in a
conference has a security
level independent of other
participants.
 One conferee may have a
phone whose security level
is authenticated while
another participant is
Encrypted.
 The Security level for a
conference is the Security
level of the least secure
phone / participant /
conference joined to that
conference.
Reference
Secure Conference Configuration
Secure Conferencing
CFB side configuration tasks Unified CM configuration tasks
 Sync the DSPFarm, CA and
Unified CM to an NTP source
 Configure Trustpoints on the
DSPFarm
 Enroll the Cert with the CA
 Install the DSPFarm‘s Cert in
the Unified CM.*
 Configure the CFB to register
Securely with Unified CM
Conferencing

Conference Resources
What Exactly Is a Video Conference?
 A Video Conference Bridge (VCB) multiplexes a group
of video streams into one lower bandwidth stream and
sends it to participants
 The Multipoint Conference
Unit (MCU) allows you to
choose different layouts
for different conferences
 MPE-VT displays the
currently active speaker
 VCBs can mix audio too
CFB Selection for Video Conferencing
Prior to Unified CM version 7.0
 Unified CM does not pick a CFB / VCB
based on initiating device type. This
decision is based solely on MRG/MRGL
configuration! Device MRGL
Video Resources
 Design Requirement is that we put audio Audio Resources
and video resources into separate media
...
resource groups (MRG) and prioritize the
MRGs in separate voice-first and video-first
MRGLs, and assign them appropriately
based on the device capabilities
Device Pool MRGL
 Audio-only conferences from video Audio Resources
devices will still end up on video resources Video Resources
...
based on the conference initiator
Intelligent Bridge Selection New in
Unified
Video Capable Bridge Selection CM 7.0
User Needs MRGL

Media MRG - A MRG - A
Resource MRG - B Audio Resource
Audio Resource
...
CONF MRG - B
Video Resource
Video capable
Participants >= 2 (Yes)
1. Video Capable phone requests Conference
2. Unified CM checks if Video Capable Participants
3. Needs Video conference
4. Searches MRGs in the MRGL for Video Conference Bridge
If no video conference bridge is available; Unified CM checks if an Audio
conference bridge is available. If Audio conference bridge available it
allocates Audio conference bridge
New in
Intelligent Bridge Selection Unified
Video Capable Bridge Selection CM7.0
User Needs MRGL

Media MRG - A MRG - A
Resource MRG - B Audio Resource
Audio Resource
...
CONF MRG - B
Video Resource
Video capable
Participants >= 2 (No)
1. Video capable phone requests Conference

2. Unified CM checks if Video Capable Participants
3. Needs Audio conference
4. Searches MRGs in MRGL for Audio Conference Bridge
If no Audio conference bridge is available; Unified CM checks if a Video
conference bridge is available. If Video conference bridge is available
allocates Video conference bridge
Reference
Intelligent Bridge Selection
Logic
Conference Initiated
Allocate Video
False
Conference Bridge for Initiator is Secure
Audio (Service endpoint Y
Parameter) Encrypted Audio
True N instead of Video
False (Service Parameter)
MRG Priority Logic A
Number of Video
to select Conference N Capable endpoints > True
resource Service Parameter
value Is there Secure Audio
N Conference Resource
B Y A
B in MRGs in the
N Is there Audio Is there Video Device MRGL
N Conference N Conference Resource
Were Video Y
Resources Resource in MRGs in MRGs in the Device
checked in the Device MRGL MRGL Allocate Secure
Audio
Y Y Y
Conference Bridge
Fail Allocate Audio Allocate Video
No secure
Conference Conference Bridge Conference Bridge resources A
Intelligent Bridge Selection Caveats
 Ad-hoc Conference Calls (―ConFrn‖, ―Join‖, ―CBarge‖) checks the
number of video capable participants at time of conference
creation. A conference bridge is allocated based on the phone
initiating the conference.
 MeetMe conference takes into account the capability of the
conference initiator and thus Intelligent bridge selection is not done.
 VCBs do not support encryption.
 Video Capable Participants:
Unified Video Advantage (USB Camera + Cisco Phone)
Unified Personal Communicator
Cisco IP Phone 7985
SCCP Third party Video Endpoints
H.323/SIP trunk – No MTP (Should be a Video call)
Video Conferencing Providers Reference
MCU + EMP
VCB MPE-VT
 The Cisco Unified Videoconferencing 3545 System is a

modular system that consists of a 3545 chassis and an MCU
module which manages up to four 24-port EMP modules.
 The Cisco Unified Videoconferencing 3515 System supports a
fixed number of ports (two models)
 A single SCCP conference cannot span multiple EMPs. Each
SCCP conference can support up to 24 participants.
 NOTE: Please see the datasheets for capacities. Capacities
vary highly based on Video Formats.
 MPE-VT capacity depends on MCS platform – max of 40
Presentation_ID
concurrent video participants.
© 2009 Cisco Systems, Inc. All rights reserved. Cisco Public 59
Agenda

Conferencing
Transcoding
Music on Hold
Annunciator
Why Transcoders? – Lets Talk Regions First
 Regions are used to filter the list of Codecs two
devices can use to communicate
 A region pair defines the relationship. A region setting
is by definition the max Bandwidth allowed between
two regions.
Remote Region Region1 Region2 Codec
Supports: WB, G.722, G.711, G.729
Atlanta Atlanta WB
Raleigh Atlanta G.722
Remote Atlanta G.729
Allowed:
Wideband, G.722, G.711u,
Raleigh Region G.711a, G.729, etc.
Supports: WB, G.722, G.711, G.729 Allowed: G.729, G.723 Choice Wideband
Choice: G.729
Allowed: G.722, G.711, G.729, iLBC

Choice: G.722 Atlanta Region
Supports: WB, G.722, G.711, G.729
Regions Configuration
 Each codec has a
corresponding BW
value within Unified
CM.
 We can see what a
call from Miami to
Atlanta would use,
but not from Miami
to Raleigh.
Calls between Calls between  The relationships
Raleigh and Atlanta and Miami are Bi-Directional.
Atlanta must use must use G.729 or
G.711 or lower BW lower BW
Unified CM Regions Codec Bandwidth Reference
and Preference Matrix
Payload Type Region BW Preference
 The Region BW is not AAC 256 1
necessarily equal to the Wide Band 256k 256 0
codec‘s actual BW G7221 24K 64 4

G7221 32K 64 3
 The highlighted codecs G722 64k 64 2
represent those registered by a G711Ulaw64k 64 1

G711Alaw64k 64 0
by a Unified IP Phone 7975G G722 56k 56 2
on SCCP75.8-3-4SR1S G711Ulaw56k 56 1
G711Alaw56k 56 0
 Unified CM‘s codec selection G722 48k 48 2
chooses the codec with the iLBC 16 1
highest BW that is equal to or G728 16 0
less than the BW allowed by GSM Enhanced Full Rate 13 2

GSM Full Rate 13 1
the region configuration GSM 13 0
 Given multiple codecs with the G729AnnexB 8 3

G729AnnexAwAnnexB 8 2
same BW, the one with the G729 8 1
highest preference number G729AnnexA 8 0
wins G7231 7 1
GSM Half Rate 7 0
Important Concepts –
Region Settings Are Relative To Each Other
Regions and Codecs
 Within Unified CM, you always configure the codec
used between Region_A and Region_B.
 You can not ―set a region to g.729.‖ What codec two
devices use with each other is the product of a setting
between two regions.
When you configure what codec to use ―within this Region,‖ you
are actually configuring a relationship between all the devices
within Region_A.
 Configuring regions explicitly instead of letting Unified
CM ―use the default‖ is likely to save you a call to the
TAC at some point in the future!
Regions Matter More than Once (Example)
Regions and Codecs
 It is important to understand that regions are

considered not just at the beginning of a call when
Unified CM wishes to connect two devices. Regions are
re-considered each time Unified CM plays audio to one
device from another device.
Regions and Codecs
 Let‘s look at this example:

A calls B. B answers. A places B on Hold by hitting
the conference Softkey. A dials C and when C
answers, A hits the (Confrn) softkey again to
complete the conference.
A B C
CFB
XCOD
Regions and Codecs
A B C
 Lets look at when the Region configuration is
consulted in the previous example:
1) At call setup between A & B, Regions associated with A & B
phones.
2) B is placed on Network Hold. The region configuration on the
selected MoH server (via B‘s MRGL) and B determine what
codec is used for MoH.
3) At call setup between A & C, Regions associated with A & C
phones.
4) A hits the Confrn Key and A, B and C are connected to a CFB
chosen from A‘s MRGL. Regions are considered another
three times, between CFB & A, CFB & B, CFB & C.
Transcoding Media Resources
 Transcoders are used by Unified CM to allow two devices without
compatible codecs to exchange audio streams. It converts an
input stream from one codec into an output stream that uses a
different codec.
 It may also connect two streams that utilize the same codec but
with a different sampling rate.
 Typically required when multiple codecs are in use in the system,
and some endpoints only support or are only configured for
G.711.
 The capabilities of a transcoder are generally a superset of an
MTP‘s (discussed next section).
XCOD
X G729 Only
G711 Only
Transcoding Resources Scenarios
 When one side does not have a codec less than or equal to A-to-
B_BW.
Capabilities = wideband, G.722-64k,

G.711u, G.711a, G.722-56k, G.722- Capabilities = G.711
48k, G.729a, G.729b, G.729ab, G.729,
G.723
(filter)
(filter) A-to-B_BW = 24kbps
Capabilities = G.729a, G.729b, G.729ab, Capabilities = None

G.729, G.723
Transcoder necessary on
side B. Use the MRGL
from side B to allocate it.
G729a G711
XCOD
A Region1 Region2 Codec B

B A G.729
Transcoding Resources Scenarios
 When neither side has a codec less than or equal to A-to-B_BW.
Capabilities = wideband, G.711u,

G.711a Capabilities = G.711u
(filter)
(filter) A-to-B_BW = 24kbps
Capabilities = None Transcoder necessary on both Capabilities = None

side A and side B. Use the
MRGL from side A to allocate
it‘s transcoder and from side B
to allocate B‘s.
G711 G729 G711
XCOD XCOD
SW CFB
A Region1 Region2 Codec B

B A G.729
Regions and Codecs
A B C C
 Back to our regions example, what if a
Software CFB was chosen and the region CFB
configuration dictates that only g.729 is
allowed between CFB and C? XCOD
 Unified CM now must invoke a XCODE

device selected from CFB‘s MRGL.
 Region configuration is now additionally
consulted:
5) Between the Transcoder and the CFB to
determine what Codec is used between them.
6) Between the Transcoder and Party C to
determine what codec is used there.
Devices left in Default MRG, potential “issue”
 If a Software CFB is left in the default MRG, when ATL CFB
resources exhausted, it could be selected.
 A conference with Phones A, B & C would result in 3 calls over
the WAN + transcoding resources for each call leg.
Miami
SW CFB
XCOD
C
Raleigh
Region1 Region2 Codec

Atlanta Atlanta WB
CFB
A B
Miami Miami g.711
Miami Atlanta g.729
Raleigh All g.729 Atlanta
Transcoder Providers Reference
ISR + PVDM2
XCODE HDV2 + PVDM2
VGD-1T3 + PVDM2
PVDM2 Transcoding Capabilities
 The ISRs can support transcoding of the following codecs:
g711alaw
g711ulaw
g722-64
g723r53 PVDM2-64 (4x c5510 DSPs)
g723r63
g729abr8
PVDM2-32 (2 DSPs)
g729ar8
g729br8
g729r8
gsmamr-nb
ilbc
pass-through
More Information:
PVDM2 XCODE Scalability BRKVVT-2010: Designing
UC Gateways and DSP
 Number of transcoding sessions per DSP depends on Networks
codecs involved:
G.711a/µlaw ↔ Med G.711a/µlaw ↔ High G.722 ↔ iLBC ↔

Complexity Codecs Complexity Codecs Any Any
8 6 4 3
 Each DSP is treated individually – PVDM2 boundaries are irrelevant

 XCODE, MTP & Voice Termination can share a single DSP‘s resources
 Conf/Xcod DSP availability checked at configuration time
 Example:
Conferencing: Two DSPs
PVDM2-64 (4 DSPs) • Up to 16 G.711 Conferences/Sessions
• Up to 4 G.711/G.729A Conferences
(4*8 = 32 participants)
PVDM2-32 (2 DSPs) Transcoding: Four DSPs
• G.711a/µlaw ↔ G.729A /G.729AB = up to 32
sessions
• G.711a/µlaw ↔ G.729 /G.729B = up to 24 (4*6)
Presentation_ID © 2009 Cisco Systems, Inc. All rights reserved. sessions
Cisco Public 75
PVDM2 DSP Codecs Reference
Complexity and Channel Support per DSP for XCODE,
MTP
Max
Codec Channels
Per DSP
G.711 (µ-law, a-law) 16 Low
Fax/Modem P-through 16 Complexity
Clear-Channel 16 Codecs
G.726 (32K, 24K, 16K) 8
Medium
T.38 and Cisco Fax Relay 8
Complexity
G.729A, G.729AB 8 Codecs
G.722 8
G.729, G.729B 6
G.728 6
G.723.1 (5.3K, 6.3K), High
6 Complexity
G.723.1A (5.3K, 6.3K)
GSM-AMR NB (all rates) 6 Codecs
iLBC 6
Modem Relay 6
Agenda

Conferencing
Transcoding
Music on Hold
Annunciator
MTP
 Terminates media streams (same codec type)

 Transrating of media streams (20ms  30ms)
 H.323 Outbound FastStart (vs. slow start)
 SIP outbound early-offer (vs. delayed-offer)
 DTMF-Relay (when two endpoints do not have a method in
common for sending DTMF between them)
 Transcoder = converts from one codec to another
(transcoding is a subset of MTP)
Codec A Codec B
Xcoder
MTP Resource Configuration/Invocation
 Invoked by ―MTP Required‖ selected on:
Trunks
Phones
H.323 gateways
 H.323 for supplementary services
 SIP Early Offer
 Automatically for RFC 2833
 Automatically RSVP Agent
MTP Allocation for RFC2833 DTMF
Invoking an MTP
 Station supports Out Of Band (OOB) only and Trunk supports only
2833 - RFC 2833 digit received
Capabilities = G.711u, 2833 in-band (PT Capabilities = G.711u
101 used here)
2.
3.
1.
MTP
Capabilities = 4(30), 11(30)

Presentation_ID © 2009 Cisco Systems, Inc. All rights reserved.
Rx 2833 in-band, Pass-Through 2833
Cisco Public 80
MTP Allocation for RFC2833 DTMF
Invoking an MTP
 Station supports Out Of Band (OOB) only and Trunk supports only
2833— RFC 2833 digit sent
Capabilities = G.711u, 2833 in-band (PT Capabilities = G.711u
101 used here)
3. 1.
2.
MTP
Capabilities = 4(30), 11(30)

Presentation_ID © 2009 Cisco Systems, Inc. All rights reserved.
Rx 2833 in-band, Pass-Through 2833
Cisco Public 81
More Information:
BRKVVT-2022: Cisco
MTP Media Resources Unified Communications
Manager Media and
Resource Management
VMail  An MTP anchors

the RTP stream
 Provides
IP
supplementary
MTP
Xcod services for
H.323 Video devices that cannot
Device support ECS
Branch HQ
SP VoIP
 Provides a single
IP address for all
endpoints at the
IP site to an outside
MTP network connection
HQ
Branch
PVDM2 MTP Scalability
 Number of MTP sessions per DSP depends on codecs involved:
More Information:
G.711 Only Medium Complexity High Complexity BRKVVT-2010: Designing
Codecs Codecs UC Gateways and DSP
16 8 6 Networks
 G.729 to G.729 MTP functionality is provided by the IOS Software MTP, which does
not use DSPs
 XCODE, MTP & Voice Termination can share a single DSP‘s resources
 Conf/Xcod/MTP DSP availability checked at configuration time
 Example:
Conferencing: Two DSPs
PVDM2-64 (4 DSPs) • Up to 8 G.711 Conferences/Sessions
• Up to 2 G.711/G.729A Conferences
(2*16 = 32 participants)
PVDM2-32 (2 DSPs) MTP: Four DSPs
• Flex complexity(FC): up to 64 (4*16) G.711-only
sessions, or between 24–64 mixed codec sessions
• Med complexity (MC): up to 32 (4*8) sessions
Presentation_ID © 2009 Cisco Systems, Inc. All rights reserved. • High complexity (HC): up to 24 (4*6) sessions
Cisco Public 83
IPVMSA Codec Support Reference

MTP G.711a / G.711µ G.711a / G.711µ
 Typically not recommended for MTP

 Cisco strongly recommends that you run the IP Voice Media
Streaming Application on a server other than the publisher
or any Unified CM server that provides call processing.
The increase in CPU load for media resources might adversely
impact call processing performance, and security issues can
arise because User Datagram Protocol (UDP) traffic must be
received on the Unified CM server.
MTP Operation and Design
1) Security demarcation – IP address masking
2) RSVP proxy for CAC
3) Anchor point for supplementary services
When
4) Unified CM 4.0 – All SIP trunks; H.323 FastStart Outbound
Necessary
Unified CM 5.x, 6.x – SIP early media; H.323 FastStart
Outbound
5) RFC2833 DTMF translation
• For #1 – 2: collocated at the site
Where Located
• For #3 – 5: anywhere
Selection /
• Based on Device or Trunk that requires the MTP’s features
Algorithm
• SW-MTP: same codec, same packetization
Codecs • HW-MTP: same codec, different packetization
• (Transcoding: different codec, same/different packetization)
• Densities vary: router model, CPU and DSP vintage
Other
• SW MTP requires no DSPs; HW MTP does
Considerations
• RSVP-Agent is a special type of IOS SW MTP
Agenda

Conferencing
Transcoding
Music on Hold
Annunciator
MoH Configuration
Audio Source and Server Selection
The MoH Stream that an Endpoint Receives Is
Determined by a Combination of the Following:
The configured User/Network Hold Audio Source

of the endpoint INITIATING the Hold Event
and
The configured Media Resource Group List

of the endpoint being PLACED on Hold
MoH Configuration
Audio Source and Server Selection
MRGL B
MRG B Audio-source1
Audio-source2
♫ Audio-source3
MOH B Audio-source4
MRGL
MRGLAA
MRG A Audio-source1
Audio-source2
♫ Audio-source3
MOH A Audio-source4
Phone A
♫ Phone B
Hold
RTP
User Hold Audio Source = Audio-source4

User Hold Audio Source = Audio-source2
Media Resource Group List = MRGL A
Media Resource Group List = MRGL B
MoH Design Considerations
 Media Resources
• Unified CM cluster only recognizes a Subscriber Node with IPVMSA
enabled as an MoH Server.
• System can be designed to allow an ISR to actually provide the
multicast MoH audio stream to the endpoints.
 Deployment Models
Centralized:
Media flows to the central site over company WAN increasing BW
requirements put perhaps save in hardware costs by aggregation.
• Unicast
• Multicast
Distributed:
Save in WAN BW by using local media services
• Multicast
Centralized MoH
Central MoH Server using Unicast
 Unicast MoH server creates a separate audio stream for each held
party
IP WAN
CC
Centralized MoH
Central MoH Server using Multicast
 Multicast allows us to replicate the audio stream at the most
efficient place in the network
 Network must be multicast ready
IP WAN
CC
Multicast MoH
Special Considerations
 MTP, XCODE, CFB‘s do not support reception of Multicast Hold
Music.
 Multicast MoH supported across Trunks (H323 & SIP) in Unified
CM version 6.1(3) and 7.1(2).
 Regions affect codec selection with MMoH, but a transcoder (or
MTP) can not be invoked if there‘s a mismatch! (Tone on Hold
results)
 Once system is configured for multicast streaming, MoH servers
are generating streams for each enabled codec 100% of the time.
Consider the affect on your network prior to just enabling multicast
on all MoH servers.
 Multicast can be received by MGCP, H323 and SIP gateways for
PSTN callers (SIP support added in 12.4(22)T).
Centralized MoH
Multicast MoH Locations-based CAC Caveat
Phone B
Cisco
Unified CM
Cluster SRST-Enabled
PSTN
Potentially can Router
Oversubscribe WAN
♫ ♫♪
Bandwidth
♫♪ ♫♪
Branch A
IP WAN RTP
♫♪
Phone A
RTP
Phone C
Headquarters Hold
Location Branch B
Bandwidth = 24 Kbps/1 call
Phone D
Branch B
Only Unicast MoH Streams Are Tracked by Locations-Based CAC

If MoH Stream Is Unicast then Location bandwidth is deducted
If MoH Stream Is Multicast then Location bandwidth is NOT deducted
Distributed MoH
Local ISR provides Multicast MoH
 Saves WAN bandwidth
System designed to avoid multicast MoH traversing the WAN
 Requires Unified SRST or Unified CM Express configuration on
local ISR
IP WAN
X
CC
Distributed Multicast MoH
From a Unified SRST or Unified CME Router
 Use the TTL Setting in Unified CM or configure a Multicast ACL on

the WAN Router so that the Multicast stream from the Unified CM
Server is blocked from traversing the WAN.
 Stream multicast MoH from Branch ISR flash or live feed on E&M
or FXO voice interface. Configured under Unified SRST or Unified
CME command syntax.
 Multicast address and port number must line up exactly with
Unified CM MoH Server configuration.
 Endpoint is unaware of multicast MoH source – simply joins the
specified codec multicast stream as directed by Unified CM. We
take advantage of this fact.
 If ISR used as a gateway for PSTN connectivity, multicast stream
from ISR flash/live-feed can be supplied to PSTN callers.
Currently supported on MGCP and H323 gateways only.

Wideband
MOH G.711a / G.711µ G.711µ
G.729a
 IPVMSA does not support G.722 codec. Note: Wideband refers

to ―Cisco Wideband‖ and does not refer to G.722.
 Use Unified CM global service parameter ―Supported MOH
Codecs‖ to enable multiple codecs (use the CTL key to make
multiple selections!)
 ISR can only stream G.711 variants – ensure Region
configuration between Unified CM MoH server and ISR-local
endpoints requires G.711.
IPVMSA MoH Capacity Reference
 Unified CM MoH Subscriber server capacity
MCS Platform # of MoH Sessions

7816, 7825 250
7835, 7845 500
• A multicast MoH stream counts as 1 session
Cisco Unified CM Music On Hold
SRND Chapter
CC
Where Is the SRND?

Agenda

Conferencing
Transcoding
Music on Hold
Annunciator
Annunciator Media Resources
 Annunciator (ANN) Resources play announcements

and tones to users.
 Annunciator plays call progress tones to off-net parties
when we cannot signal those tones out of band.
 Only offered via Unified CM Subscriber server with
IPVMSA enabled.
Your call cannot
 All done via Unicast. be completed as
dialed. Please…
X
CC
The Annunciator Reference
Spoken Feedback
 Annunciator will be invoked when the subscriber‘s MRGL has
access to an ANN resource and any of the following conditions
need to be signaled to a subscriber:
Condition Audible Announcement

An equal or higher precedence Equal or higher precedence calls have prevented the completion of your call.
call is in progress. MLPP Only Please hang up and try again. This is a recording.
A precedence access limitation Precedence access limitation has prevented the completion of your call. Please
exists. MLPP Only hang up and try again. This is a recording.
Someone attempted an The precedence used is not authorized for your line. Please use an authorized
unauthorized precedence level. precedence or ask your operator for assistance. This is a recording.
MLPP or “not authorized” on
Route Pattern
The call appears busy, or the The number you have dialed is busy and not equipped for call waiting or
administrator did not configure preemption. Please hang up and try again. This is a recording.
the directory number for call
waiting or preemption.
The system cannot complete Your call cannot be completed as dialed. Please consult your directory and call
the call. again or ask your operator for assistance. This is a recording.
A service interruption occurred. A service disruption has prevented the completion of your call. In case of
emergency call your operator. This is a recording.
The Annunciator Reference
Ringback and Tones
 Annunciator will be invoked when the device or

subscriber‘s MRGL has access to an ANN resource
and any of the following conditions need to be signaled
to that party:
Tone Played Condition

Ringback Blind transfer of a call established over an H.323 intercluster trunk
*‖Send H225 User Info Message‖ Service Parameter must be set to ―Use ANN
for ringback‖
Ringback Blind transfer of a call established with a SIP client
Ringback Blind transfer of a call established over a SIP trunk
Barge Tone Before a participant joins an Ad-Hoc conference
Ringback Blind transfer of any type of endpoint into a conference call

Wideband Wideband
ANN G.711a / G.711µ G.711a / G.711µ
G.729a G.729a
 IPVMSA does not support G.722 codec. Note: Wideband refers

to ―Cisco Wideband‖ and does not refer to G.722.
Key Take Aways
 The role of MRGLs and

Region configurations in
Unified CM with respect to
Media Resources
 Functions that each type of Media Resource can

provide
 Design Considerations for the various Unified CM
Media Resources
Q&A
Cisco Unified CM Media Resources
References
Where Is the SRND?

References
 Unified CM Maintenance and Operation Guides
http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guid
es_list.html
 SRND – Music on Hold

http://cisco.com/en/US/partner/docs/voice_ip_comm/Unified
CM/srnd/6x/moh.html
 DSP Calculator
http://www.cisco.com/cgi-bin/Support/DSP/cisco_dsp_calc.pl
 Integrated Services Router General Information

http://www.cisco.com/go/isr
 Cisco Enhanced Conferencing and Transcoding for Voice Gateway Routers

http://www.cisco.com/en/US/prod/collateral/modules/ps3115/product_data_sheet
0900aecd801b97a6_ps5855_Products_Data_Sheet.html
 Configuring Secure Conference Resources

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/security/7_0_1/secugd/s
ecuconf.html
 Unified CM Security Overview

http://cisco.com/en/US/partner/docs/voice_ip_comm/UnifiedCM/security/6_0_1/s
ecugd/secuview.html#wpxref60373
Complete Your Online
Session Evaluation
 Give us your feedback and you
could win fabulous prizes.
Winners announced daily.
 Receive 20 Passport points for
each session evaluation you
complete.
 Complete your session
evaluation online now (open a
browser through our wireless
network to access our portal) or
visit one of the Internet stations
throughout the Convention
Don‘t forget to activate your
Center.
Cisco Live Virtual account for access to
all session material, communities, and
on-demand and live activities throughout
the year. Activate your account at the
Cisco booth in the World of Solutions or visit
www.ciscolive.com.
Backup Slides
Intelligent Bridge Selection New in
Unified
Service Parameters CM7.0
Multicast MoH Configuration
 Enable multicast in three
places:
1) =>
2) =>
3) =>
 Multicast MoH (MMoH) can‘t be configured if MoH server is in default MRG.

Unified Communications Core: Media Resources
Music on Hold: Server Configuration
Location of MoH Server;

Required for CAC
Maximum Number of
Streams (Affects Capacity)
Enables Multicast Support

brkvvt-2022 cl09 v05 Web

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

brkvvt-2022 cl09 v05 Web

Hochgeladen von

Copyright:

Verfügbare Formate

Understanding Cisco

Unified Communications Manager

Brett Wiggins, CCIE R&S

Where Is the UC SRND?

 Media Resource Types

 Media Termination Point

 Media Resources we are NOT going to cover

 IPv6 Media Resources

 Media Resource Types

IPVMSA = IP Voice Media Streaming Application

CMM = Cisco Media Module (‗Router on a blade‘)

MCU = Media Control Unit (Cisco 35XX Video Conferencing series)

MPE-VT = MeetingPlace Express Video Telephony (Server based Video

End-Of-Sale hardware-based options available in Unified CM

 ISR Series can provide:

 Can be deployed centrally or at remote sites.

2) NM-HDV2, in an ISR Network Module slot

 Different flavors of PVDM2 depending on how many physical

NM-HDV2-2T1/E1 PVDM2-64 (4 DSPs)

 As of Cisco IOS 12.2(24)T can be used for Conferencing,

Configure Router Configure Options Results

 3515 and 3545 MCU

 Service can be enabled per

Central Site Remote Site

 NM-HDV2 + PVDM2  NM-HDV2 + PVDM2

Functionality Provided by:

 Media Resource Types

 Media Resource Group (MRG)

 Media Resource Group List

 Top down order of the MRG‘s

Media Media Media Media

Resource_List I Would Like to Conference to

Dallas MRG SanJose_MRG

SanJose_MRG Result Dallas MRG

MTP MRG MTP MRG

 Media Resource Types

 How Are They Invoked?

1) Using the button

1) Using the button:

2) Using the and buttons

MeetMe conferences are created by going off-hook then

4) A) Using Barge functionality: BARGE

4) B) Using Barge functionality: cBARGE

 Conferences are not combined – an RTP stream is set up between

 How Are They Invoked?

 External caller X calls A – note: no voice across WAN

 Three voice streams across WAN

 No media survivability if WAN goes down

stay local Branch MRG Conf Conf

Functionality Provided by:

Max G711 Only G722-64 G729 iLBC

 Each DSP is treated individually – PVDM2 boundaries are irrelevant

 No support for G.722.

• Single-mode: Conf participants all use same Codec (usually G.711)

 How Are They Invoked?

 Secure Conferencing is available as of Unified CM 6.0

 How Are They Invoked?

User Needs MRGL

User Needs MRGL

1. Video capable phone requests Conference

Functionality Provided by:

 The Cisco Unified Videoconferencing 3545 System is a