Cisco Unified Communications Manager System Guide, Release 9.1(1)
Media Termination Points
Download this chapter
Media Termination PointsMedia Termination Points
Download the complete book
Cisco Unified Communications Manager System Guide, Release 9.1(1)Cisco Unified Communications Manager System Guide, Release 9.1(1) (PDF - 9 MB)
 Feedback

Media Termination Points

This chapter provides information about Media Termination Point (MTP) software devices which allow Cisco Unified Communications Manager to relay calls that are routed through SIP or H.323 endpoints or gateways.


Note

For information on hardware MTP, which act as transcoders, see the Transcoders.

Configure software MTP

A Media Termination Point (MTP) software device allows Cisco Unified Communications Manager to relay calls that are routed through SIP or H.323 endpoints or gateways.

To configure MTP refer to the following steps.

Procedure
    Step 1   Determine the number of MTP resources that are needed and the number of MTP devices that are needed to provide these resources.
    Step 2   Verify that the Cisco IP Voice Media Streaming Application service is activated and running on the server to which you are adding an MTP.
    Step 3   Add and configure the MTPs.
    Step 4   Add the new MTPs to the appropriate media resource groups.
    Step 5   Restart the MTP device.
    Related Information

    Media Termination Points overview

    Media Termination Points extend supplementary services, such as call hold, call transfer, call park, and conferencing, that are otherwise not available when a call is routed to an H.323 endpoint. Some H.323 gateways may require that calls use an MTP to enable supplementary call services, but normally, Cisco IOS gateways do not. For H.323 supplementary services, MTPs are only required for endpoints that do not support Empty Capability Set (ECS) or FastStart. All Cisco endpoints and most other endpoints do support ECS and FastStart, so an MTP is not required for them.

    MTP resources accept two full-duplex G.711 Coder-Decoder (CODEC) stream connections. MTPs bridge the media streams between two connections. The streaming data that is received from the input stream on one connection passes to the output stream on the other connection and vice versa. In addition, the MTP trancodes a-law to mu-law (and vice versa) and adjusts packet sizes as required by the two connections.

    Each MTP belongs to a device pool, which specifies, in priority order, the list of Cisco Unified Communications Managers to which the devices that are members of the device pool should attempt to register. This list represents a Cisco Unified Communications Manager group. The first Cisco Unified Communications Manager in the list specifies a device primary Cisco Unified Communications Manager.

    An MTP device always registers with its primary Cisco Unified Communications Manager if that Cisco Unified Communications Manager is available and informs the Cisco Unified Communications Manager about how many MTP resources it supports. The Cisco Unified Communications Manager controls MTP resources. You can register multiple MTPs with the same Cisco Unified Communications Manager. When more than one MTP is registered with a given Cisco Unified Communications Manager, that Cisco Unified Communications Manager controls the set of resources for each MTP. You can also distribute the MTPs across a networked system as desired.

    For example, consider MTP server 1 as configured for 48 MTP resources, and the MTP server 2 as configured for 24 resources. If both MTPs register with the same Cisco Unified Communications Manager, that Cisco Unified Communications Manager maintains both sets of resources for a total of 72 registered MTP resources.

    When the Cisco Unified Communications Manager determines that a call endpoint requires an MTP, it allocates an MTP resource from the MTP that has the least active streams. That MTP resource gets inserted into the call on behalf of the endpoint. MTP resource use remains invisible to both the users of the system and to the endpoint on whose behalf it was inserted. If an MTP resource is not available when it is needed, the call connects without using an MTP resource, and that call does not have supplementary services.

    Make sure that the Cisco IP Voice Media Streaming application is activated and running on the server on which the MTP device is configured.

    The Cisco IP Voice Media Streaming application, which is common to the MTP, Conference Bridge, annunciator, and Music On Hold applications, runs as a service of Cisco Unified Communications Manager.

    You can add an MTP device in two ways:

    • You automatically add an MTP device when you activate the Cisco IP Voice Media Streaming Application service from Cisco Unified Serviceability.
    • You can manually install the Cisco IP Voice Media Streaming Application on a networked server and configure an MTP device on that server through Cisco Unified Communications Manager Administration.

    Manage MTPs with the Media Resource Manager

    The Media Resource Manager (MRM), a software component in the Cisco Unified Communications Manager system, primarily functions for resource registration and resource reservation. Each MTP device that is defined in the database registers with the MRM. The MRM keeps track of the total available MTP devices in the system and of which devices have available resources.

    During resource reservation, the MRM determines the number of resources, identifies the media resource type (in this case, the MTP), and the location of the registered MTP device.

    The MRM updates its shared resource table with the registration information.

    MRM also supports the coexistence of an MTP and transcoder within a Cisco Unified Communications Manager.

    MTPs and Call Throttling

    The MTP and Transcoder Resource Throttling Percentage service parameter, which supports the Cisco CallManager service, defines a percentage of the configured number of MTP or transcoder resources and allows Cisco Unified Communications Manager to extend the call to an MTP/transcoder that offers the best chance of successfully connecting the call. When the number of active MTP or transcoder resources is equal to or greater than the percentage that is configured for this parameter, Cisco Unified Communications Manager throttles (stops sending) calls to this MTP/transcoder. Cisco Unified Communications Manager hunts through the Media Resource Group List (MRGL) one time to find a MTP/transcoder that uses matching codecs on both sides of the call. If Cisco Unified Communications Manager cannot find an available MTP/transcoder with matching codecs, Cisco Unified Communications Manager returns to the top of the MRGL to repeat the search, which then includes those MTPs/transcoders that are in a throttled state and that match a smaller subset of capabilities for the call. Cisco Unified Communications Manager extends the call to the MTP/transcoder that is the best match for the call when Cisco Unified Communications Manager determines that a resource may be available; the call fails when the MTP/transcoder cannot allocate a resource for the call. In some cases, Cisco Unified Communications Manager perceives that a resource on a hardware MTP/transcoder is available, but the actual port on the hardware is not available.

    For example, if you enter 40 for the Call Count service parameter, which supports the Cisco IP Voice Media Streaming Application service, for a software MTP or transcoder (or for hardware resources, if the maximum sessions is configured at 40, for example), and you set the MTP and Transcoder Resource Throttling Percentage service parameter to 95 percent, Cisco Unified Communications Manager throttles calls to the MTP/transcoder when 38 resources are used on this MTP/transcoder (.95 x 40 = 38). When a new request for an MTP or transcoder arrives, Cisco Unified Communications Manager checks whether the number of resources has dropped to 38 or less, and if so, extends the call to the MTP/transcoder.

    For the maximum, minimum, and default values for this service parameter, click the question mark help in the Service Parameter Configuration window in Cisco Unified Communications Manager Administration.

    MTP types in Cisco Unified Communications Manager administration

    The media termination point types inCisco Unified Communications Manager Administration are as follows.

    Table 1  Media Termination Point Types

    MTP Type

    Description

    Cisco IOS Enhanced Media Termination Point

    This type supports Cisco 2600XM, Cisco 2691, Cisco 3725, Cisco 3745, and Cisco 3660 Access Routers and the following MTP cases:

    • For software-only implementation that does not use DSP but has the same packetization time for devices that support G.711 to G.711 or G.729 to G.729 codecs, this implementation can support up to 500 sessions per gateway.
    • For a hardware-only implementation with DSP for devices that use G.711, G.729a, and G.729b codecs, 200 sessions can occur per NM-HDV2, and 48 sessions can occur per NM-HD.
    Note   

    For more information on using G.729 codecs over SIP trunks, see Session Initiation Protocol

    This type can support Network Address Translation in a service provider environment to hide the private address.

    In Cisco Unified Communications Manager Administration, ensure that you enter the same MTP name that exists in the gateway Command Line Interface (CLI).

    Cisco Media Termination Point Software

    A single MTP provides a default of 48 MTP (user configurable) resources, depending on the speed of the network and the network interface card (NIC). For example, a 100-MB Network/NIC card can support 48 MTP resources, while a 10-MB NIC card cannot.

    For a 10-MB Network/NIC card, approximately 24 MTP resources can be provided; however, the exact number of MTP resources that are available depends on the resources that other applications on that PC are consuming, the speed of the processor, network loading, and various other factors.

    Plan software MTP

    Provisioning represents a crucial aspect that needs consideration when MTP resources are deployed. Provisioning requires attentive analysis of the call load patterns and the network topology.

    Consider the following information when you are planning your MTP configuration:

    • An improper setting can result in undesirable performance if the workload is too high.
    • A single MTP provides a default of 48 MTP (user configurable) streams, and two streams make one resource because you need one stream for each side (send/receive) of the MTP. For a 10-MB Network/NIC card, approximately 24 MTP resources can be provided; however, the exact number of MTP resources that are available depends on the resources that other applications on that PC are consuming, the speed of the processor, network loading, and various other factors. Consider the following formula to determine the approximate number of MTPs that are needed for your system, assuming that your server can handle 48 MTP streams (you can substitute 48 for the correct number of MTP resources that your system supports): A number divided by 48 = number of MTP applications that are needed (n/48 = number of MTP applications). where: n represents the number of devices that require MTP support for H.323 and SIP calls. If a remainder exists, add another server with Cisco IP Voice Streaming Application service with MTP.
    • If one H.323 or SIP endpoint requires an MTP, it consumes one MTP resource. Depending on the originating and terminating device type, a given call might consume more than one MTP resource. The MTP resources that are assigned to the call get released when the call terminates.
    • Use the Serviceability Real-Time Monitoring Tool (RTMT) to monitor the usage of MTP resources. The perfmon counter, Media TermPoints Out of Resources, increments for each H.323 or SIP call that connects without an MTP resource when one was required. This number can assist you in determining how many MTP resources are required for your callers and whether you have adequate coverage.
    • Identical system requirements apply for the Cisco IP Voice Media Streaming Application, the MTP resources, and the Cisco Unified Communications Manager system.
    • To optimize performance of DTMF signaling, use Cisco IOS release 12.4(11)T or later. This Cisco IOS release supports RFC 2833 DTMF MTP Passthrough of digits.

    Software MTP device characteristics

    The Full Streaming Endpoint Duplex Count, a number of MTP resources that a specific MTP supports, represents a device characteristic that is specific to MTP device configuration.

    Avoid call failure

    To prevent call failure or user alert, avoid the following conditions:

    • Although the Cisco IP Voice Media Streaming Application service can run on the same PC as the Cisco Unified Communications Manager, Cisco strongly recommends against this arrangement. If the Cisco IP Voice Media Streaming Application is running on the same PC as the Cisco Unified Communications Manager, it can adversely affect the performance of the Cisco Unified Communications Manager.
    • When you configure the MTP, a prompt asks you to reset MTP before any changes can take effect. This action does not result in disconnection of any calls that are connected to MTP resources. If you choose Reset, as soon as the MTP has no active calls, the changes take effect.

    Note

    When you make updates to the MTP and you choose Restart, all calls that are connected to the MTP get dropped.

    MTP system requirements and limitations

    The following system requirements and limitations apply to software MTP devices:

    • You can activate only one Cisco IP Voice Streaming Application per server. To provide more MTP resources, you can activate the Cisco IP Voice Streaming application on additional networked servers.
    • Each MTP can register with only one Cisco Unified Communications Manager at a time. The system may have multiple MTPs, each of which may be registered to one Cisco Unified Communications Manager, depending on how your system is configured.
    • Cisco strongly recommends that you do not activate the Cisco IP Voice Streaming Media Application on a Cisco Unified Communications Manager with a high call-processing load because it can adversely affect the performance of the Cisco Unified Communications Manager.

    MTP failover and fallback

    This section describes how MTP devices failover and fallback when the Cisco Unified Communications Manager to which they are registered becomes unreachable. This section also explains conditions that can affect calls that are associated with an MTP device, such as MTP reset or restart.

    Active Cisco Unified Communications Manager becomes inactive

    The following description gives the MTP device recovery methods when the MTP is registered to a Cisco Unified Communications Manager that goes inactive:

    • If the primary Cisco Unified Communications Manager fails, the MTP attempts to register with the next available Cisco Unified Communications Manager in the Cisco Unified Communications Manager Group that is specified for the device pool to which the MTP belongs.
    • The MTP device reregisters with the primary Cisco Unified Communications Manager as soon as it becomes available after a failure and is currently not in use.
    • The system maintains the calls or conferences that were active in call preservation mode until all parties disconnect. The system does not make supplementary services available.
    • If an MTP attempts to register with a new Cisco Unified Communications Manager and the register acknowledgment is never received, the MTP registers with the next Cisco Unified Communications Manager.

    Reset registered MTP devices

    The MTP devices will unregister and then disconnect after a hard or soft reset. After the reset completes, the devices reregister with the Cisco Unified Communications Manager.

    Dependency records

    To find what media resource groups a specific media termination point is using, choose Dependency Records from the drop-down list box and click Go from the Cisco Unified Communications Manager Administration Media Termination Point Configuration window. The Dependency Records Summary window displays information about media resource groups that are using the media termination point. To find out more information about the media resource group, click the media resource group, and the Dependency Records Details window displays. If the dependency records are not enabled for the system, the dependency records summary window displays a message.

    Software MTP performance monitoring and troubleshooting

    The Real-Time Monitoring Tool counters for media termination point allow you to monitor the number of media termination points that are currently in use, the number of media termination points that are currently registered with Cisco Unified Communications Manager but are not currently in use, and the number of times that a media termination point was requested for a call, but no resources were available.

    Cisco Unified Communications Manager writes all errors for the media termination point to the Local SysLog. In Cisco Unified Serviceability, you can set traces for the Cisco IP Voice Media Streaming Application service; to troubleshoot most issues, you must choose the Significant or Detailed option for the service, not the Error option. After you troubleshoot the issue, change the Debug Trace Level back to the Error option.

    Cisco Unified Communications Manager generates registration and connection alarms for media termination point in Cisco Unified Serviceability.

    If you need technical assistance, locate and review software MTP logs before you contact your Cisco Unified Communications partner or the Cisco Technical Assistance Center (TAC).

    Use the following CLI commands to access the software MTP logs:

    file list activelog cm/trace/cms/sdi/*.txt

    file get activelog cm/trace/cms/sdi/*.txt

    file view activelog cm/trace/cms/sdi/cms00000000.txt

    file tail activelog cm/trace/cms/sdi/cms00000000.txt