Table Of Contents
Media Processing Command Reference
action
application accessNumber
application scheduledResources
application totalResources
application-profile (dial-peer media-service)
application-profile (media service media-processing)
app-mux
attribute h264
bandwidth (stream profile)
calling-party-info
clear ctsman statistics
codec-profile (media service media-processing)
codec-profile (stream profile)
codec-type
ctsman enable
ctsman hostname
ctsman ip
ctsman leg-limit
ctsman password
ctsman port
ctsman server-port
ctsman ssl-hostname-check
ctsman username
custom
default-telepresence-media-prof
default-vc-media-profile
description (dial-peer media-service)
destination-pattern
dial-peer media-service
level-idc
listen-port
max-fs
max-mbps
max-trans-bandwidth (media-profile)
max-trans-bandwidth (stream-profile)
media-profile (dial-peer media-service)
media-profile (media service media-processing)
media service media-processing
mode
packetization-mode
packet-time
payload-number
preference
quality (stream-profile)
resolution-profile (media service media-processing)
session-bandwidth (media profile)
session-protocol (dial-peer media-service)
session-target (dial-peer media-service)
show application
show call-detail
show call-summary
show ctsman conference
show ctsman config
show ctsman statistics
show dial-peer media-service
show media-processing
show media-statistics
shutdown (interface)
shutdown (sip)
sip
stream-profile (media profile)
stream-profile (media service stream-processing)
stream-type
transport
Media Processing Command Reference
Revised: September 2011
This chapter includes the Cisco MXE-OS commands used for configuring media-processing features.
action
To configure how an application-profile responds to calls, use the action command. To remove this configuration use the no form of this command.
action {query}
no action {query}
Syntax Description
query
|
Specifies that the application determines what to do with the call.
|
Defaults
Query
Command Modes
Application profile
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
None
Examples
This example shows how to configure application-profile 1's call response action:
mxe(config)# media service media-processing
mxe(config-media-serv)# application-profile 1
mxe(config-media-serv-application-pro)# action query
Related Commands
application accessNumber
To configure the access number or trunk that Cisco MXE-OS uses to receive calls, use the application accessNumber command.
application accessNumber number
Syntax Description
number
|
Specifies the access number that Cisco MXE-OS uses to receive scheduled video interoperability calls. Typically, this is the number that the CTS Manager uses to route calls to the Cisco MXE-OS device.
Maximum size is 80 characters.
|
Note
Although visible in the command-line help strings, the directive keyword is not supported.
Defaults
None
Command Modes
Global configuration
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.1
|
This command was introduced.
|
Usage Guidelines
None
Examples
This example shows how to configure 11055 as the access number used by Cisco MXE-OS to receive calls from videoconferencing endpoints:
mxe(config)# application accessNumber 11055
Related Commands
application scheduledResources
To configure the number of resources that are allocated for scheduled calls, use the application scheduledResources command.
application scheduledResources number
Syntax Description
number
|
Specifies the number of resources that Cisco MXE-OS allocates for scheduled calls for an application server, such as the Cisco TelePresence System Manager. Range varies by the number of installed port licenses.
|
Note
Although visible in the command-line help strings, the directive keyword is not supported.
Defaults
None
Command Modes
Global configuration
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.1
|
This command was introduced.
|
Usage Guidelines
Cisco MXE-OS enforces resource limits regardless of port availability. Before configuring, you should confirm the requirements for scheduled resources.
Examples
This example shows how to configure a maximum of 15 resources for scheduled calls:
mxe(config)# application scheduledResources 15
Related Commands
application totalResources
To configure the maximum number of resources that the Cisco MXE-OS allocates for media-processing features, use the application totalResources command for devices running Cisco MXE-OS Release 1.1. This command was deprecated in Cisco MXE-OS Release 1.1.1.
application totalResources number
Syntax Description
number
|
Specifies the number of resources that Cisco MXE-OS allocates for media-processing features, such as mxe-interop. Range varies by the number of installed port licenses.
|
Defaults
None
Command Modes
Global configuration
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.1
|
This command was introduced.
|
1.1.1
|
This command was deprecated.
|
Usage Guidelines
Cisco MXE-OS supports scheduled and ad-hoc calls. You can allocate the Cisco MXE-OS resources to manage the maximum number of scheduled and ad-hoc calls.
•
To allow only scheduled calls, set the same value for these commands: application totalResources, application scheduledResources, and ctsman leg-limit.
To allow ad-hoc calls, lower the application scheduledResources and the ctsman leg-limit values by an amount equal to the resources required to fulfill these calls. Typically by two resources per participant when not using WebEx, and one extra resource when using WebEx.
You can adjust the resources based on the requirement. If the Cisco MXE-OS is not used for any scheduled calls, set the application scheduledResources and the ctsman leg-limit values to zero.
•
If you find that a Cisco MXE-OS has underutilized scheduled call capacity, you can dynamically lower the leg-limit value and reregister with the CTS Manager. To do this, change the ctsman leg-limit value and then execute the no ctsman enable and the ctsman enable commands. Next, change the application scheduledResources to a lower value to add more ad-hoc call capacity.
•
The application totalResources command defines the total number of Cisco MXE-OS resources. The resources are defined as number of ports, similar to licensing ports. The total capacity is 30 ports. This value cannot exceed the port license count. If a you specify a higher value, the port license count is used as the application totalResources value.
•
For Cisco MXE-OS Release 1.1 we recommend specifying an even number of resources for all application resource values.
Examples
This example shows how to configure a total of 30 resources for media-processing features:
mxe(config)# application totalResources 30
Related Commands
application-profile (dial-peer media-service)
To associate an application-profile with a dial peer, use the application-profile command. To remove an application profile, use the no form of this command.
application-profile {profile-id}
no application-profile
Syntax Description
Defaults
None
Command Modes
Dial-peer media-service
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
For information about application profiles, see the Configuration Guide for Cisco MXE-OS.
Examples
This example shows how to associate an application profile with a dial peer.
mxe(config)# dial-peer media-service 1
mxe(config-dial-peer)# application-profile 1
Related Commands
application-profile (media service media-processing)
To create or modify an application profile and enter the application-profile configuration mode, use the application-profile command. To remove an application profile, use the no form of this command.
application-profile {profile-id}
no application-profile
Syntax Description
profile-id
|
Unique identifier. Up to 80 alphanumeric characters are allowed.
|
Defaults
None
Command Modes
Media service media-processing
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
For information about application profiles, see the Configuration Guide for Cisco MXE-OS.
Examples
This example shows how to create an application profile:
mxe(config)# media service media-processing
mxe(config-media-serv)# application-profile 1
mxe(config-media-serv-application-pro)#
Related Commands
app-mux
To enable app-mux protocol support for a stream profile, use the app-mux command. To remove this configuration, use the no form of this command.
app-mux
no app-mux
Syntax Description
This command has no keywords or arguments.
Defaults
Disabled
Command Modes
Stream profile
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
A stream profile must first be created with the stream-profile (media service stream-processing) command.
Examples
This example shows how to enable app-mux protocol support for stream-profile 1:
mxe(config)# media service media-processing
mxe(config-media-serv)# stream-profile 1
mxe(config-media-serv-stream-profile)# app-mux
Related Commands
attribute h264
To configure a codec profile as H.264 and enter the codec-profile attribute H.264 configuration mode, use the attribute h264 command. To remove attributes, use the no form of this command.
attribute h264
Syntax Description
None
Defaults
None
Command Modes
Codec profile
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
A codec profile must first be created with the codec-profile (media service media-processing) command.
Examples
This example shows how to configure H.264 attributes for codec profile 1 and enter the codec-profit attribute H.264 configuration mode:
mxe(config)# media service media-processing
mxe(config-media-serv)# codec-profile 1
mxe(config-media-serv-codec-profile)# attribute h264
mxe(config-media-serv-codec-profile-attr-h264)#
Related Commands
bandwidth (stream profile)
To configure the amount of bandwidth used by media in a stream profile, use the bandwidth command. To remove the configuration, use the no form of this command.
bandwidth {value}
no bandwidth {value}
Syntax Description
value
|
Bandwidth in bits per second (b/s). The range is from 64000 to 32000000 b/s.
|
Defaults
128000 b/s (audio default)
Command Modes
Stream profile configuration
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
A stream profile must first be created with the stream-profile (media service stream-processing) command.
Examples
This example shows how to configure a bandwidth of 64000 b/s for stream profile 1:
mxe(config)# media service media-processing
mxe(config-media-serv)# stream-profile 1
mxe(config-media-serv-stream-profile)# bandwidth 64000
Related Commands
calling-party-info
To configure the pattern for which a media-service dial-peer will match inbound dial peers, use the calling-party-info command. To remove a defined pattern, use the no form of this command.
calling-party-info {id | name} inbound-match-pattern
no calling-party-info {id | name} inbound-match-pattern
Syntax Description
id
|
Specifies that the dial peer uses caller ID as a matching key pattern.
|
name
|
Specifies that the dial peer uses the display name of the endpoint as a matching key pattern.
|
inbound-match-pattern
|
Perl-compatible regular expression (PCRE). Up to 80 characters are allowed.
|
Defaults
None
Command Modes
Dial-peer media service
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
The name keyword matches the user portion of the Session Initiation Protocol (SIP) Uniform Resource Identifier (URI) of the Remote-Party-ID Header and the From Header.
The inbound-match-pattern argument is in the form of a regular expression against which the value of the corresponding header field is matched.
Before using this command, you must first create a media-service dial peer with the dial-peer media-service command.
Examples
This example shows how to define calling party information:
mxe(config)# dial-peer media-service 2
mxe(config-dial-peer)# calling-party-info id ^10
Related Commands
clear ctsman statistics
To clear Cisco Telepresence Manager (CTS Manager) statistics, use the clear ctsman statistics command.
clear ctsman statistics
Syntax Description
This command has no keywords or arguments.
Defaults
None
Command Modes
EXEC
Supported User Roles
network-admin
network-operator
Command History
Release
|
Modification
|
1.1
|
This command was introduced.
|
Usage Guidelines
None
Examples
The following example shows how to clear CTS Manager statistics:
mxe# clear ctsman statistics
codec-profile (media service media-processing)
To create or modify a codec profile, use the codec-profile command. To remove a codec profile, use the no form of this command.
codec-profile {profile-id}
no codec-profile {profile-id}
Syntax Description
profile-id
|
Unique identifier for the codec profile. The valid range is from 1 to 65535.
|
Defaults
None
Command Modes
Media service media-processing
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
None
Examples
This example shows how to configure a codec-profile:
mxe(config)# media service media-processing
mxe(config-media-serv)# codec-profile 1
Related Commands
codec-profile (stream profile)
To apply a codec profile to a stream-profile, use the codec-profile command. To remove a codec profile, use the no form of this command.
codec-profile {profile-id} [preference value]
no codec-profile {profile-id}
Syntax Description
profile-id
|
The ID of a codec-profile configured with the codec-profile (media-service) command.
|
preference
|
(Optional) Specifies the order of the codecs when multiple codec-profiles are applied to a stream-profile.
|
value
|
(Optional) The value range is from 1 to 10.
|
Defaults
10
Command Modes
Stream profile
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
A codec profile must first be configured with the codec-profile (media service media-processing) command.
For information about codec profiles, see the Configuration Guide for Cisco MXE-OS.
Examples
This example shows how to configure stream profile 1 with codec profiles 1 and 2 and their preference orders:
mxe(config)# media service media-processing
mxe(config-media-serv)# stream-profile 1
mxe(config-media-serv-stream-profile)# codec-profile 1 preference 1
mxe(config-media-serv-stream-profile)# codec-profile 2 preference 2
Related Commands
codec-type
To specify the type of codec to be used for a codec profile, use the codec-type command. To remove the codec type configuration, use the no form of this command.
codec-type {aac | g711-ulaw | g711-alaw | g722 | h264}
no codec-type {aac | g711-ulaw | g711-alaw | g722 | h264}
Syntax Description
aac
|
Specifies the AAC codec.
|
g711-ulaw
|
Specifies the G.711 µ-law codec.
|
g711-alaw
|
Specifies the G.711 a-law codec.
|
g722
|
Specifies the G.722 codec.
|
h264
|
Specifies the H.264 codec.
|
Defaults
None
Command Modes
Codec profile
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
A codec profile must first be configured with the codec-profile (media service media-processing) command.
Examples
This example shows how to specify a codec type for codec profile 1:
mxe(config)# media service media-processing
mxe(config-media-serv)# codec-profile 1
mxe(config-media-serv-codec-profile)# codec-type h264
Related Commands
ctsman enable
To enable Cisco MXE-OS communications with a Cisco Telepresence Manager (CTS Manager), use the ctsman enable command. To disable communications with the CTS Manager, use the no form of this command. This command was deprecated in Cisco MXE-OS Release 1.2.
ctsman enable
no ctsman enable
Syntax Description
This command has no keywords or arguments
Defaults
None
Command Modes
Global configuration
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.1
|
This command was introduced.
|
1.2
|
This command was deprecated.
|
Usage Guidelines
If you execute the no ctsman enable command, even though the active HTTP/SOAP communications are disabled, you can continue configuring ctsman related parameters.
Examples
The following shows how to enable communications with a CTS Manager:
mxe(config) ctsman enable
Related Commands
Command
|
Description
|
show ctsman config
|
Displays the CTS Manager configuration information.
|
ctsman hostname
To enable or disable Cisco Telepresence Manager (CTS Manager) OpenSSL hostname checking, use the ctsman hostname command for devices running Cisco MXE-OS Release 1.1.
This command was deprecated in Cisco MXE-OS Release 1.2. See the ctsman ssl-hostname-check command.
ctsman hostname {enable | disable}
Syntax Description
enable
|
Enables CTS Manager OpenSSL hostname checking.
|
disable
|
Disables CTS Manager OpenSSL hostname checking.
|
Defaults
None
Command Modes
Global configuration
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.1
|
This command was introduced.
|
1.2
|
This command was deprecated.
|
Usage Guidelines
Cisco MXE-OS validates the hostname against the security certificate of the CTS Manager during secured communications. The ctsman hostname command is active only when the ctsman server-port is 443 or 8443.
Examples
The following example shows how to enable CTS Manager OpenSSL hostname checking:
mxe(config)# ctsman hostname enable
Related Commands
ctsman ip
To configure the IP address and port number of the Cisco Telepresence Manager (CTS Manager), use the ctsman ip command. To remove the configuration, use the no form of this command.
ctsman ip ipv4-address port-number
no ctsman ip ipv4-address port-number
Syntax Description
ipv4-address
|
Specify the IPv4 address of the CTS Manager. Use the A.B.C.D format.
|
port-number
|
Specify the port number used by the CTS Manager registration requests. The port-number is a TCP/IP port number. The range is 1 to 65535.
|
Defaults
None
Command Modes
Global configuration
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.1
|
This command was introduced.
|
1.2
|
The port-number value was added.
|
Usage Guidelines
None
Examples
The following example shows how to configure the CTS Manager IPv4 address and port number:
mxe(config) ctsman ip 10.1.1.1 80
Related Commands
Command
|
Description
|
ctsman password
|
Configures the password for CTS Manager communications.
|
ctsman username
|
Configures the username for CTS Manager communications.
|
ctsman leg-limit
To configure the maximum number of Cisco MXE-OS device resources that the Cisco Telepresence Manager (CTS Manager) allocates for scheduled calls, use the ctsman leg-limit command. To return to the default setting, use the no form of this command.
ctsman leg-limit value
no ctsman leg-limit value
Syntax Description
value
|
Specifies the maximum number of Cisco MXE-OS device resources.
|
Defaults
None
Command Modes
Global configuration
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.1
|
This command was introduced.
|
Usage Guidelines
The leg-limit value represents the maximum number of Cisco MXE-OS device resources that the CTS Manager can allocate for scheduled calls. The value should be less than or equal to the number of installed port licenses.
The leg-limit value cannot exceed the number of scheduled resources that are specified by using the application scheduledResources command.
Examples
The following example shows how to configure 20 as the maximum number of Cisco MXE-OS device resources that the CTS Manager allocates for scheduled calls:
mxe(config) ctsman leg-limit 20
Related Commands
ctsman password
To configure the password for Cisco Telepresence Manager (CTS Manager) communication, use the ctsman password command. To remove the password, use the no form of this command.
ctsman password password
no ctsman password
Syntax Description
password
|
Specifies the password that the Cisco MXE-OS uses for communication with the CTS Manager. Up to 80 characters are allowed.
|
Defaults
None
Command Modes
Global configuration
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.1
|
This command was introduced.
|
Usage Guidelines
The password must match the CTS Manager password defined in the CTS Manager Bridge configuration dialog window. The password displays as clear text.
Examples
The following example shows how to configure a CTS Manager password:
mxe(config) ctsman password admin1pw
Related Commands
Command
|
Description
|
ctsman username
|
Configures the username for CTS Manager communications.
|
ctsman port
To configure the Cisco Telepresence Manager (CTS Manager) port for incoming Simple Object Access Protocol (SOAP) messages from the Cisco MXE-OS device, use the ctsman port command for devices running Cisco MXE-OS Release 1.1. To remove the configuration, use the no form of this command.
This command was deprecated in Cisco MXE-OS Release 1.2.
ctsman port port-number
no ctsman port
Syntax Description
port-number
|
Specifies the CTS Manager port for incoming SOAP messages from the Cisco MXE-OS device. The range is from 1 to 65535.
|
Defaults
None
Command Modes
Global configuration
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.1
|
This command was introduced.
|
1.2
|
This command was deprecated.
|
Usage Guidelines
None
Examples
The following example shows how to configure the CTS Manager port to 80:
mxe(config) ctsman port 80
Related Commands
Command
|
Description
|
ctsman ip
|
Configures the CTS Manager IP address.
|
ctsman server-port
To configure the Cisco MXE-OS device port for incoming Simple Object Access Protocol (SOAP) messages from the Cisco Telepresence Manager (CTS Manager), use the ctsman server-port command. To remove the current configuration, use the no form of this command.
ctsman server-port port-number
no ctsman server-port
Syntax Description
port-number
|
The Cisco MXE-OS port number for incoming SOAP messages from the CTS Manager. The range is 1 to 65535.
|
Defaults
None
Command Modes
Global configuration
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.1
|
This command was introduced.
|
Usage Guidelines
If you enter a value of 443 or 8443, OpenSSL is used for communications.
Examples
The following example shows how to configure the Cisco MXE-OS server port to 8443:
mxe(config) ctsman server-port 8443
Related Commands
ctsman ssl-hostname-check
To enable or disable Cisco Telepresence Manager (CTS Manager) OpenSSL hostname checking, use the ctsman ssl-hostname-check command.
ctsman ssl-hostname-check {enable | disable}
Syntax Description
enable
|
Enables CTS Manager OpenSSL hostname checking.
|
disable
|
Disables CTS Manager OpenSSL hostname checking.
|
Defaults
None
Command Modes
Global configuration
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.2
|
This command was introduced.
|
Usage Guidelines
The ctsman ssl-hostname-check command controls how the OpenSSL implementation manages hostname checking during secure communications initialization. When the command is enabled, the Cisco MXE-OS validates the X.509 commonName and systemAltName portions of the certificates used by the CTS Manager for authentication and encryption.
If the ctsman server-port port-number is not 443 or 8443, the parameter value is ignored.
Examples
The following example shows how to enable CTS Manager OpenSSL hostname checking:
mxe(config)# ctsman ssl-hostname-check enable
Related Commands
ctsman username
To configure the username that Cisco MXE-OS uses for Cisco Telepresence Manager (CTS Manager) communication, use the ctsman username command. To remove the username, use the no form of this command.
ctsman username username
no ctsman username username
Syntax Description
username
|
CTS Manager username. Up to 80 characters are allowed.
|
Defaults
None
Command Modes
Global configuration
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.1
|
This command was introduced.
|
Usage Guidelines
The username must match the CTS Manager username defined in the CTS Manager Bridge configuration dialog window. The username is clear text.
Examples
The following example shows how to configure a CTS Manager username:
mxe(config) ctsman username admin1
Related Commands
Command
|
Description
|
ctsman password
|
Configures the password for CTS Manager communications.
|
custom
To configure a custom name and value for an H.264 attribute, use the custom command. To remove this configuration, use the no form of this command.
custom name [value]
no custom name [value]
Syntax Description
name
|
Up to 80 characters are allowed.
|
value
|
Up to 80 characters are allowed.
|
Defaults
None
Command Modes
Codec-profile attribute H.264
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
A codec profile must first be configured with the codec-profile (media service media-processing) command.
Examples
This example shows how to configure a custom attribute:
mxe(config)# media service media-processing
mxe(config-media-serv)# codec-profile 1
mxe(config-media-serv-codec-profile)# attribute h264
mxe(config-media-serv-codec-profile-attr-h264)# custom level-asymmetry-allowed value 1
Related Commands
default-telepresence-media-prof
To configure a default media profile for an application profile to use for outbound dial-peers when TelePresence media capabilities are required, use the default-telepresence-media-prof command. To remove a default media profile, use the no form of this command.
default-telepresence-media-prof profile-id
no default-telepresence-media-prof profile-id
Syntax Description
Defaults
None
Command Modes
Application profile
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
Before using this command, you must first create an application profile with the application-profile (media service media-processing) command and a media profile with the media-profile (media service media-processing) command.
Examples
This example shows how to configure application profile 1 with media profile 1 as the default:
mxe(config)# media service media-processing
mxe(config-media-serv)# application-profile 1
mxe(config-media-serv-application-pro)# default-telepresence-media-prof 1
Related Commands
default-vc-media-profile
To configure a default media profile for an application-profile to use for outbound dial-peers when videoconferencing media capabilities are required, use the default-vc-media-profile command. To remove a default media profile, use the no form of this command.
default-telepresence-media-profile {profile-id}
no default-telepresence-media-profile {profile-id}
Syntax Description
Defaults
Query
Command Modes
Application profile
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
Before using this command, you must first create an application profile with the application-profile (media service media-processing) command and a media profile with the media-profile (media service media-processing) command.
Examples
This example shows how to configure application-profile 1 with a default media-profile 1:
mxe(config)# media service media-processing
mxe(config-media-serv)# application-profile 1
mxe(config-media-serv-application-pro)# default-vc-media-profile 1
Related Commands
description (dial-peer media-service)
To add a description to a dial peer, use the description command. To remove the description, use the no form of this command.
description {description}
no description
Syntax Description
description
|
Text string up to 80 alphanumeric characters.
|
Defaults
None
Command Modes
Dial-peer media-service
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
Before using this command, you must first create a media-service dial peer with the dial-peer media-service command.
Examples
This example shows how to configure a description for a dial peer 1:
mxe(config)# dial-peer media-service 1
mxe(config-dial-peer)# description Cisco TelePresence Endpoint
Related Commands
destination-pattern
To configure the pattern that a dial peer uses for outbound dial-peer matching, use the destination-pattern command. To remove a destination pattern, use the no form of this command.
destination-pattern outbound-match-pattern
no destination-pattern outbound-match-pattern
Syntax Description
outbound-match-pattern
|
Perl-compatible regular expression (PCRE). Up to 80 characters are allowed.
|
Defaults
None
Command Modes
Dial-peer media-service
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
This command specifies the value in the user portion of the Request Uniform Resource Identifier (URI) header used to match the dial peer.
The outbound-match-pattern argument is in the form of a regular expression against which the value of the Request URI is matched.
Before using this command, you must first create a media-service dial peer with the dial-peer media-service command.
Examples
This example shows how to create a destination pattern for media-service dial peer 1:
mxe(config)# dial-peer media-service 1
mxe(config-dial-peer)# destination-pattern ^((1011)|(1017))
Related Commands
dial-peer media-service
To create a media-service dial peer and enter the dial-peer configuration mode, use the dial-peer media-service command. To remove a defined dial peer, use the no form of this command.
dial-peer media-service dial-peer-id
no dial-peer media-service dial-peer-id
Syntax Description
dial-peer-id
|
Unique identifier. The range is from 1 to 65535.
|
Defaults
None
Command Modes
Global configuration
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
None
Examples
This example shows how to define dial peer 1:
mxe(config)# dial-peer media-service 1
Related Commands
level-idc
To specify a profile level for an H.264 attribute, use the level-idc command. To remove this configuration, use the no form of this command.
level-idc profile-level
no level-idc profile-level
Syntax Description
profile-level
|
A value ranging from 10 to 40.
|
Defaults
31
Command Modes
Codec-profile attribute H.264
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
A codec profile must first be configured with the codec-profile (media service media-processing) command.
Examples
This example shows how to configure an H.264 attribute profile level of 10 for codec-profile 1:
mxe(config)# media service media-processing
mxe(config-media-serv)# codec-profile 1
mxe(config-media-serv-codec-profile)# attribute h264
mxe(config-media-serv-codec-profile-attr-h264)# level-idc 10
Related Commands
listen-port
To assign the listen port for Session Initiation Protocol (SIP) communications through Transit Control Protocol (TCP), use the listen-port command. To remove the listen port, use the no form of this command.
listen-port {non-secure port-number}
no listen-port {non-secure port-number}
Syntax Description
non-secure
|
Configures a non-secure port.
|
port-number
|
Port number. The range from 1024 to 65535.
|
Defaults
The default port number is 5060 for non-secure communications.
Command Modes
Media service SIP
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
None
Examples
This example shows how to configure the listen port for SIP communications:
mxe(config)# media service media-processing
mxe(config-media-serv)# sip
mxe(config-media-serv-sip)# listen-port non-secure 5060
max-fs
To specify the maximum frame size of an H.264 attribute, use the max-fs command. To remove this configuration, use the no form of this command.
max-fs frame-size
no max-fs frame-size
Syntax Description
frame-size
|
Maximum frame size in macroblocks, ranging from 99 to 8192.
|
s
Defaults
3600
Command Modes
Codec-profile attribute H.264
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
A codec profile must first be configured with the codec-profile (media service media-processing) command.
Examples
This example shows how to configure the maximum frame size of 998 for codec profile 1:
mxe(config)# media service media-processing
mxe(config-media-serv)# codec-profile 1
mxe(config-media-serv-codec-profile)# attribute h264
mxe(config-media-serv-codec-profile-attr-h264)# max-fs 998
Related Commands
max-mbps
To configure the maximum number of macroblocks per second (mbps) of an H.264 attribute, use the max-mbps command. To remove this configuration, use the no form of this command.
max-mbps value
no max-mbps value
Syntax Description
value
|
Maximum number of macroblocks per second, ranging from 1485 to 245760.
|
Defaults
108000
Command Modes
Codec-profile attribute H.264
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
Before using this command, a codec profile must first be configured with the codec-profile (media service media-processing) command.
Examples
This example shows how to configure a maximum of 245760 macroblocks per second for codec profile 1:
mxe(config)# media service media-processing
mxe(config-media-serv)# codec-profile 1
mxe(config-media-serv-codec-profile)# attribute h264
mxe(config-media-serv-codec-profile-attr-h264)# max-mbps 245760
Related Commands
max-trans-bandwidth (media-profile)
To configure the maximum transmit bandwidth within a media profile, use the max-trans-bandwidth (media-profile) command. To remove the configuration, use the no form of this command.
max-trans-bandwidth value
no max-trans-bandwidth value
Syntax Description
value
|
Specifies the maximum transmit bandwidth available for the media session. The range is 0 to 32000000 b/s.
|
Defaults
None
Command Modes
Media profile configuration
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.3
|
This command was introduced.
|
Usage Guidelines
A media profile must first be created by using the media-profile (media service media-processing) command.
The max-trans-banwidth command controls the maximum bandwidth used for all the media streams (represented by stream profiles ) within the media profile.
The effective trasmit bandwidth is the lower value of the configured value and negotiated bandwidth. If the maximum transmit bandwidth is not configured, the negotiated session bandwidth is used.
Examples
This example shows how to configure a maximum of 32000000 b/s for media profile 1:
mxe(config)# media service media-processing
mxe(config-media-serv)# media-profile 1
mxe(config-media-serv-media-profile)# max-trans-bandwidth 32000000
Related Commands
max-trans-bandwidth (stream-profile)
To configure the maximum transmit bandwidth within a stream profile, use the max-trans-bandwidth command. To remove the configuration, use the no form of this command.
max-trans-bandwidth value
no max-trans-bandwidth value
Syntax Description
value
|
Specifies the maximum transmit bandwidth available for the stream profile. The range is 0 to 32000000 b/s.
|
Defaults
None
Command Modes
Media service stream-processing
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.3
|
This command was introduced.
|
Usage Guidelines
A stream profile must first be created by using the stream-profile (media service stream-processing) command.
The max-trans-bandwidth command at the stream-profile level controls the maximum bandwidth used for encoding the individual stream.
The effective bandwidth used is the lower value of the configured value and the negotiated value in the Session Description Protocol (SDP). If the maximum transmit bandwidth is not configured, the negotiated stream bandwidth is used.
Examples
This example shows how to configure a maximum of 32000000 b/s for stream profile 1:
mxe(config)# media service media-processing
mxe(config-media-serv)# stream-profile 1
mxe(config-media-serv-stream-profile)# max-trans-bandwidth 32000000
Related Commands
media-profile (dial-peer media-service)
To apply a media profile to a dial peer, use the media-profile command. To remove a media-profile, use the no form of this command.
media-profile {profile-id}
no media-profile {profile-id}
Syntax Description
Defaults
None
Command Modes
Dial-peer media-service
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
Before using this command, a media profile must first be configured with the media-profile (media service media-processing) command.
For information about media profiles, see the Configuration Guide for Cisco MXE-OS.
Examples
This example shows apply media-profile 1 to dial-peer 1:
mxe(config)# dial-peer media-service 1
mxe(config-dial-peer)# media-profile 1
Related Commands
media-profile (media service media-processing)
To create or modify a media profile and enter the media-profile configuration mode, use the media-profile command. To remove a media-profile, use the no form of this command.
media-profile {profile-id}
no media-profile {profile-id}
Syntax Description
profile-id
|
New or existing numeric ID. The valid range is from 1 to 65535.
|
Defaults
None
Command Modes
Media service media -processing
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
None
Examples
This example shows how to configure media-profile 1:
mxe(config)# media service media-processing
mxe(config-media-serv)# media-profile 1
mxe(config-media-serv-media-profile)#
Related Commands
media service media-processing
To enter the media service media-processing mode, use the media service media-processing command.
media service media-processing
Syntax Description
None
Defaults
None
Command Modes
Global configuration
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
None
Examples
This example shows how to enter the media service media-processing mode:
mxe(config)# media service media-processing
mode
To specify the call control mode for the media in a stream profile, use the mode command. To remove this configuration, use the no form of this command.
mode {sendrecv | sendonly | recvonly} [forced]
no mode {sendrecv | sendonly | recvonly} [forced]
Syntax Description
sendrecv
|
Specifies send and receive.
|
sendonly
|
Specifies send only.
|
recvonly
|
Specifies receive only.
|
forced
|
(Optional) Specifies that the mode will be used regardless of an offer from the other side of a call.
|
s
Defaults
Send and receive.
Command Modes
Stream profile
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
None
Examples
This example shows how to configure the call control mode for a stream-profile 1
mxe(config)# media service media-processing
mxe(config-media-serv)# stream-profile 1
mxe(config-media-serv-stream-profile)# mode recvonly forced
Related Commands
packetization-mode
To specify the packetization mode of an H.264 attribute, use the packetization-mode command. To remove this configuration, use the no form of this command.
packetization-mode value
no packetization-mode value
Syntax Description
value
|
Specifies one of the following:
• 0—single Network Abstract Layer (NAL) mode
• 1—non-interleaved mode
|
Defaults
0
Command Modes
Codec-profile attribute H.264
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
A codec profile must first be configured with the codec-profile (media service media-processing) command.
Examples
This example shows how to configure the packetization mode of codec profile 1:
mxe(config)# media service media-processing
mxe(config-media-serv)# codec-profile 1
mxe(config-media-serv-codec-profile)# attribute h264
mxe(config-media-serv-codec-profile-attr-h264)# packetization-mode 1
Related Commands
packet-time
To specify the packet time for the stream-profile, use the packet-time command. To remove this configuration, use the no form of this command
packet-time value
no packet-tim value
Syntax Description
value
|
Specifies one of the following:
• 10 ms
• 20 ms
|
Defaults
Audio default is 20 ms.
Command Modes
Stream profile
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
A stream profile must first be configured with the stream-profile (media service stream-processing) command.
Examples
This example shows how to configure the packet time for a stream-profile 1:
mxe(config)# media service media-processing
mxe(config-media-serv)# stream-profile 1
mxe(config-media-serv-stream-profile)# packet-time 10
Related Commands
payload-number
To specify the payload used in Real Time Protocol (RTP) packets for a codec type, use the payload-number command. To remove payload configuration, use the no form of this command.
payload-number value
no payload-number value
Syntax Description
value
|
Payload number. The valid range is from 0 to 127.
|
Defaults
None
Command Modes
Codec profile
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
A codec profile must first be configured with the codec-profile (media service media-processing) command.
Examples
This example shows how to specify a payload number:
mxe(config)# media service media-processing
mxe(config-media-serv)# codec-profile profile-id
mxe(config-media-serv-codec-profile)# payload-number 123
Related Commands
preference
To configure a dial-peer preference value, use the preference command. To remove the configuration, use the no form of this command.
preference value
no preference value
Syntax Description
value
|
The range is from 0 to 255.
|
Defaults
255
Command Modes
Dial-peer media-service
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
1.3
|
The command name was corrected.
|
Usage Guidelines
Before using this command, you must first create a media-service dial peer with the dial-peer media-service command.
Examples
This example shows how to configure a preference value of 10 for dial-peer 1:
mxe(config)# dial-peer media-service 1
mxe(config-dial-peer)# preference 10
Related Commands
quality (stream-profile)
To configure the quality preference for a stream profile, use the quailty command. To remove this configuration, use the no form of this command.
quality {motion | sharpness}
no quality {motion | sharpness}
Syntax Description
motion
|
Specifies preference for a higher frame rate.
|
sharpness
|
Specifies preference for a higher resolution.
|
Defaults
The default is sharpness.
Command Modes
Media service stream-processing
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.3
|
This command was introduced.
|
Usage Guidelines
A stream profile must first be created by using the stream-profile (media service stream-processing) command.
To configure the Cisco MXE-OS device to transmit the highest possible resolution at a lower frame rate, use the quality sharpness command. To configure the device to transmit the highest possible frame rate at a lower resolution, use the quality motion command.
Examples
This example shows how to configure a higher frame rate preference for stream profile 1:
mxe(config)# media service media-processing
mxe(config-media-serv)# stream-profile 1
mxe(config-media-serv-stream-profile)# quality motion
Related Commands
resolution-profile (media service media-processing)
To create or modify a resolution profile and enter the resolution-profile configuration mode, use the resolution-profile command. To remove a resolution-profile, use the no form of this command.
resolution-profile {profile-id}
no resolution-profile {profile-id}
Syntax Description
profile-id
|
Specifies a new or existing numeric ID. The valid range is from 1 to 65535.
Configure the resolutions for the profile:
• 180p—Select 180p (320 x 180)
• 360p—Select 360p (640 x 360)
• 4cif—Select 4cig (704 x 576)
• 4sif—Select 4sif (704 x 480)
• 720p—Select 720p (1280 x 720)
• cif—Select CIF (352 x 288)
• sif—Select SIF (352 x 240)
• w288p—Select w288p (512 x 288)
• w448p—Select w448p (768 x 448)
• w576p—Select w576p (1024 x 576)
• xga—Select XGA (1024 x 768)
|
Defaults
None
Command Modes
Media service media-processing
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.3
|
This command was introduced.
|
Usage Guidelines
You need to associate the resolution profile with a codec profile. For more information, see the Configuration Guide for Cisco MXE-OS.
If you do not configure a resolution profile, these are the default resolutions:
•
Outgoing main video stream to Cisco TelePresence System (CTS) endpoints: 720p
•
Outgoing main video stream for videoconferencing endpoints will be one of these resolutions depending on the negotiated bandwidth and the quality setting in the corresponding stream profile: 720p, w576p, w448p, 360p, w288p, 180p
•
Outgoing presentation stream to CTS endpoints: XGA
•
Outgoing presentation stream to videoconferencing endpoints will be one of these resolutions depending on the negotiated bandwidth and the quality setting in corresponding steam-profile: XGA, 4SIF, SIF, 4CIF, CIF
Examples
This example shows how to configure resolution-profile 1 to limit the resolutions transmitted to w576p and w488p:
mxe(config)# media service media-processing
mxe(config-media-serv)# resolution-profile 1
mxe(config-media-serv-resolution-profile)# w448p
mxe(config-media-serv-resolution-profile)# w576p
Related Commands
session-bandwidth (media profile)
To configure the amount of session bandwidth used by all media in a media profile, use the session-bandwidth command. To remove the configuration, use the no form of the command.
session-bandwidth {value}
no session-bandwidth {value}
Syntax Description
value
|
Session bandwidth in bits per second (b/s). The range is 64000 to 32000000 b/s.
|
Defaults
None
Command Modes
Media profile configuration
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.2
|
This command was introduced.
|
Usage Guidelines
A media profile must first be created with the media-profile (media service media-processing) command.
It is common for videoconferencing endpoints to allocate session bandwidth as a bandwidth limit that is shared among all the streams within a session. For example, a session with audio, video, and content sharing (presentation) might have a 2 MB session bandwidth limit. When content sharing is not active, the video stream can use all the bandwidth except that required for audio. When content sharing is active, the bandwidth is shared between the video and the content sharing streams.
Examples
This example shows how to configure a session bandwidth of 3000000 b/s for media profile 1:
mxe(config)# media service media-processing
mxe(config-media-serv)# media-profile 1
mxe(config-media-serv-media-profile)# session-bandwidth 3000000
Related Commands
session-protocol (dial-peer media-service)
To configure the signaling protocol for a dial peer, use the session-protocol command. To remove payload configuration, use the no form of this command.
session-protocol {sipv2}
no session-protocol {sipv2}
Syntax Description
sipv2
|
Specifies Session Initiation Protocol (SIP) Version 2.
|
Defaults
SIP Version 2
Command Modes
Dial-peer media-service
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
Before using this command, you must first create a media-service dial peer with the dial-peer media-service command.
Examples
This example shows how to configure the signalling protocol for a dial peer:
mxe(config)# dial-peer media-service 1
mxe(config-dial-peer)# session-protocol sipv2
Related Commands
session-target (dial-peer media-service)
To configure the destination address for a dial peer, use the session-target command. To remove the configuration, use the no form of this command.
session-target {ipv4:destination-address}
no session-target {ipv4:destination-address}
Syntax Description
ipv4:destination-address
|
Specifies the IPv4 destination address.
|
Defaults
None
Command Modes
Dial-peer media-service
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.2
|
This command was introduced.
|
Usage Guidelines
Before using this command, you must first create a media-service dial peer with the dial-peer media-service command.
The session target destination address specifies the gateway for the outgoing call.
Examples
This example shows how to configure the session target destination address for a dial peer:
mxe(config)# dial-peer media-service 1
mxe(config-dial-peer)# session-target ipv4:10.194.58.41:5060
Related Commands
show application
To display the Cisco MXE-OS device resource allocation configuration, use the show application command.
show application {all {configuration | history {value {minutes | hours | days} | active} |
interfaces}} | {{mxe-interop {configuration | history {value {minutes | hours | days} | active}
| interfaces}}
Syntax Description
all
|
Display all known applications within the Cisco MXE-OS. The optional keywords have these meanings along with any available configuration information:
• configuration—Show application configuration
• history—Show call detail history information
– value—Enter a value for the number of days, hours, or minutes
– active—Show call history information for all active calls
• interfaces—Show application interfaces that are registered with the Cisco MXE-OS device
|
mxe-interop
|
Display information relevant to the call and media processing interoperability application. The optional keywords have these meanings:
• configuration—Show application configuration
• history—Show call history information
– value—Enter a value for the number of days, hours, or minutes
– active—Show call history information for all active calls
• interfaces—Show application interfaces that are registered with the Cisco MXE-OS device
|
Defaults
None
Command Modes
EXEC
Supported User Roles
network-admin
network-operator
Command History
Release
|
Modification
|
1.1
|
This command was introduced.
|
1.2
|
The configuration and interfaces keywords were added.
|
1.3
|
The all and history keywords, and the mxe-interop application name were added.
|
Usage Guidelines
The show application history command provides a brief summary of Cisco MXE-OS call activity. The level of detail is useful during testing and deployment for determining general call processing and call termination activity.
Examples
This example shows how to display all Cisco MXE-OS information about services, applications, and service-related infrastructure:
mxe# show application all
application accessNumber 69
application scheduledResources 4
ctsman ip 10.194.60.34 80
ctsman ssl-hostname-check enable
No calls have been recently traced
McuRegistrationService is operational
URL is http://10.194.60.34:80/discovery/services/McuRegistrationService
CTSManConferenceServer is operational
URL is http://10.194.60.64:80/mcu/services/McuService
This example shows how to display the Cisco MXE-OS resource allocation configuration:
mxe# show application configuration
application accessNumber 69
application scheduledResources 10
This example shows how to display information about recent calls:
mxe# show application history
Call from 4184565962 to 5084565862 started 3 minutes ago
Call from 4184565961 to 3084565892 started 6 minutes ago and ran
Call from 4184565979 to 4084565892 started 13 minutes ago and ran 1 minute
Call from 4184565998 to 5084565892 started 13 minutes ago and ran 1 minute
Call from 4184565977 to 6084565892 started 14 minutes ago and ran 1 minute
Call from 4184565996 to 7084565892 started 14 minutes ago and ran
Call from 4184565975 to 8084565892 started 17 minutes ago and ran
Call from 4184565994 to 9084565892 started 17 minutes ago and ran 1 minute
Call from 4184565993 to 8084565892 started 1 hour 9 minutes ago and ran
Call from 4184565972 to 4084565892 started 1 hour 10 minutes ago and ran 1 minute
This example shows how to display the application interfaces registered with the Cisco MXE-OS:
mxe# show application interfaces
CTSManConferenceServer http://10.10.1.1:80/mcu/services/McuService
Related Commands
show call-detail
To display detailed information about an individual call that has used the Cisco MXE 5600, use the show call-detail command.
show call-detail call-id
Syntax Description
call-id
|
The range is from 1 to 65535.
|
Defaults
None
Command Modes
EXEC
Supported User Roles
network-admin
network-operator
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
To view all of the configured call ID numbers, use the show call-summary command.
Examples
This example displays the detail information regarding Call ID 73:
Call Start Time : Thu Apr 29 02:11:31 2010
VC_CTS_INTEROP_APP.00000011
Audio App Mux Time : Thu Apr 29 02:11:32 2010
Video App Mux Time : Thu Apr 29 02:11:32Call-ID : 73
Call Start Time : Thu Apr 29 02:11:31 2010
Application SessionID : VC_CTS_INTEROP_APP.00000011
Audio App Mux Time : Thu Apr 29 02:11:32 2010
Video App Mux Time : Thu Apr 29 02:11:32 2010
--- Calling Party : 1058 ---
SIP Call-ID : 859e5100-bd81ead3-b3ad-293ac20a@10.194.58.41
----------- Local Audio ------------------
IP Addr : 10.194.60.67:16464
---------- Local Video -----------------
IP Addr : 10.194.60.67:16466
IDR Send Time : Thu Apr 29 02:11:31 2010
----------- Remote Audio -----------------
IP Addr : 10.194.60.205:50322
----------- Remote Video ---------------
IP Addr : 10.194.60.205:50324
IDR Request Time : Thu Apr 29 02:11:35 2010
--- Called Party : 3002 ---
SIP Call-ID : 2770772368-22090
----------- Local Audio ------------------
IP Addr : 10.194.60.67:16468
---------- Local Video -----------------
IP Addr : 10.194.60.67:16470
----------- Remote Audio -----------------
----------- Remote Video ---------------
Related Commands
Command
|
Description
|
show call-summary
|
Displays summary information regarding calls that have used the Cisco MXE 5600.
|
show call-summary
To display summary information about calls that have used the Cisco MXE 5600, use the show call-summary command.
show call-summary
Syntax Description
None
Defaults
None
Command Modes
EXEC
Supported User Roles
network-admin
network-operator
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
For detailed information regarding individual call IDs, use the show call-detail command.
Examples
This example displays the summary information regarding calls:
CallID CallingParty CalledParty State Start Time
------------------------------------------------------------------------
48 1018 3001 ESTABLISHED Thu Apr 29 02:09:19 2010
65 1066 3001 ESTABLISHED Thu Apr 29 02:08:15 2010
73 1058 3002 ESTABLISHED Thu Apr 29 02:11:31 2010
Related Commands02:11:31 2010
Command
|
Description
|
show call-detail
|
Displays detailed information about an individual call that has used the Cisco MXE 5600.
|
show ctsman conference
To display Cisco Telepresence Manager (CTS Manager) conference information, use the show ctsman conference command.
show ctsman conference {[accessNumber | conferenceID | meetingID | active | all | detailed]}
Syntax Description
accessNumber
|
Displays information about all conferences for the specified access number.
|
conferenceID
|
Displays information about the specified conference ID.
|
meetingID
|
Displays information about the specified meeting ID.
|
active
|
Displays information about all active conferences.
|
all
|
Displays summary information about all scheduled conferences.
|
detailed
|
Displays detailed information about all scheduled conferences.
|
Defaults
None
Command Modes
EXEC
Supported User Roles
network-admin
network-operator
Command History
Release
|
Modification
|
1.1
|
This command was introduced.
|
Usage Guidelines
None
Examples
This example shows how to display information about all conference information:
mxe# show ctsman conference all
Meeting ID Start time End time Access Type
4100192427 Fri Mar 26 18:00 PDT Fri Mar 26 18:30 PDT 11055
Sat Mar 27 18:00 PDT Sat Mar 27 18:30 PDT 11055
Mon Mar 29 18:00 PDT Mon Mar 29 18:30 PDT 11055
Wed Mar 31 18:00 PDT Wed Mar 31 18:30 PDT 11055
Thu Apr 01 18:00 PDT Thu Apr 01 18:30 PDT 11055
Fri Apr 02 18:00 PDT Fri Apr 02 18:30 PDT 11055
Sat Apr 03 18:00 PDT Sat Apr 03 18:30 PDT 11055
Mon Apr 05 18:00 PDT Mon Apr 05 18:30 PDT 11055
Wed Apr 07 18:00 PDT Wed Apr 07 18:30 PDT 11055
Thu Apr 08 18:00 PDT Thu Apr 08 18:30 PDT 11055
6100140281 Fri Mar 26 12:00 PDT Fri Mar 26 12:30 PDT 11055
7100186109 Fri Mar 26 10:00 PDT Fri Mar 26 10:30 PDT 11055
Sun Mar 28 10:00 PDT Sun Mar 28 10:30 PDT 11055
Tue Mar 30 10:00 PDT Tue Mar 30 10:30 PDT 11055
Related Commands
show ctsman config
To display the Cisco Telepresence Manager (CTS Manager) configuration, use the show ctsman config command.
show ctsman config
Syntax Description
This command has no keywords or arguments.
Defaults
None
Command Modes
EXEC
Supported User Roles
network-admin
network-operator
Command History
Release
|
Modification
|
1.1
|
This command was introduced.
|
Usage Guidelines
None
Examples
This example shows how to display the CTS Manager configuration:
Related Commands
show ctsman statistics
To display Cisco Telepresence Manager (CTS Manager) statistics, use the show ctsman statistics command.
show ctsman statistics
Syntax Description
This command has no keywords or arguments.
Defaults
None
Command Modes
EXEC
Supported User Roles
network-admin
network-operator
Command History
Release
|
Modification
|
1.1
|
This command was introduced.
|
Usage Guidelines
None
Examples
This example shows how to display CTS Manager statistics:
mxe# show ctsman statistics
=================== Ctsman Legacy Gateway ===================
Registration Triggers Received : 164
Registrations that were successful : 388
Registrations that failed : 4513
Registrations that became stale due to heartbeat silence : 0
=================== CTSMan Legacy Interface===================
Heartbeat Messages : 7361
Conference Messages : 396
Heartbeat Last Message : Thu Jul 08 18:44 UTC
show dial-peer media-service
To display configuration information for one or all dial peers, use the show dial-peer media-service command.
show dial-peer media-service {summary | id dialpeer-id}
Syntax Description
summary
|
Specifies tabular output of all dial peers
|
id
|
Specifies a selected dial peer.
|
dialpeer-id
|
The range is from 1 to 65535.
|
Defaults
None
Command Modes
EXEC
Supported User Roles
network-admin
network-operator
Command History
Release
|
Modification
|
1.0
|
This command was introduced
|
Usage Guidelines
For the dialpeer-id argument use a dial peer ID created with the dial-peer media-service command.
Examples
These examples show how to display all dial peers and a selected dial peer:
mxe56# show dial-peer media-service summary
Id MediaProfileId ApplicationProfile
---------------------------------------------------------
mxe# show dial-peer media-service id 1
ApplicationProfile = mxe-interop,
Description = CTS calling and called dial-peer when VC connected to CUC
DeviceProfilePtOptimization = false,
StreamProfilesID(s) = 2,1,
CodecProfilesID(s) = 2,4,
profile-level-id = 42001f,
Related Commands
show media-processing
To display media-processing profiles, use the show media-processing command.
show media-processing {application-profile | codec-profile | media-profile | resolution-profile |
stream-profile} {profile-id | summary}
Syntax Description
application-profile
|
Shows the application-profile configuration.
|
codec-profile
|
Shows the codec-profile configuration.
|
media-profile
|
Shows the media-profile configuration.
|
resolution-profile
|
Shows the resolution-profile configuration
|
stream-profile
|
Shows the stream-profile configuration.
|
profile-id
|
Application-, codec-, media-, or stream-profile ID.
|
summary
|
Shows summary configuration information for the selected profile.
|
Defaults
None
Command Modes
EXEC
Supported User Roles
network-admin
network-operator
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
1.3
|
The resolution-profile keyword was added.
|
Usage Guidelines
None
Examples
These examples show how to display configurations for an application-profile summary and application-profile ID mxe-interop:
mxe# show media-processing application-profile summary
AppProfiles Id Action DeviceProfilePtOpti CTSMediaProfId VCMediaProfId
--------------------------------------------------------------------------------
mxe-interop Query false 1 2
mxe-interop-vcs Query false 3 4
mxe# show media-processing application-profile summary
AppProfiles
ID Action CTSMedia ProfId VCMediaProfID
mxe-interop Query 1 2
mxe# show media-processing application-profile mxe-interop
These examples show how to display configurations for a codec-profile summary and codec-profile ID 1:
mxe# show media-processing codec-profile summary
id CodecType PayloadNumber Frequency
mxe# show media-processing codec-profile id 1
These examples show how to display configurations for a media-profile summary and media-profile ID 1:
mxe# show media-processing media-profile summary
ID Stream ProfilesCount StreamProfilesId(s)
mxe# show media-processing media-profile id 1
StreamProfileID(s) = 1, 2,
These examples show how to display configurations for a resolution-profile summary and resolution-profile ID 3:
mxe# show media-processing resolution-profile summary
--------------------------------------
mxe# show media-processing resolution-profile id 3
Resolutions = w576p,720p,w448p,
These examples show how to display configurations for a stream-profile summary and stream-profile ID 1:
mxe# show media-processing stream-profile summary
Id Appmux Stream Type Codec profileID(s) Pref
mxe# show media-processing stream-profile id 1
Related Commands
show media-statistics
To display media statistics for an application session or endpoint, use the show media-statistics command.
show media-statistics {application-session-id} [endpoint-id audio | video]
Syntax Description
application-session-id
|
Specify the application session ID for the call.
|
endpoint-id
|
(Optional) Specify an endpoint.
|
audio
|
(Optional) Specify the endpoint media type.
|
video
|
(Optional) Specify the endpoint media type.
|
Defaults
None
Command Modes
EXEC
Supported User Roles
network-admin
network-operator
Command History
Release
|
Modification
|
1.2
|
This command was introduced.
|
Usage Guidelines
Use the show call-summary command to display the call ID, and the show call-detail call-id command to obtain the application-session-id. Then use the show media-statistics command to request live statistics for a specific application session.
When using the show media-statistics command to troubleshoot call setup, call failure, and call quality, check for these indicators:
•
Are the counters are increasing?
•
Is there packet loss?
•
Are there partial frames?
•
Check the bit rate for the audio and video streams on a per-endpoint basis to see the actual bit rate transmitted and received. This can help to troubleshoot low video quality issues.
See Table 5-1 for the field descriptions used in the following examples.
This example shows a summary of statistics for a point-to-point call between a videoconferencing endpoint (ID-1038) and a Cisco TelePresence System (CTS) (ID-2103).
In this example, the videoconferencing endpoint resolution is 360p (transmit) and 720p (receive). The CTS resolution is 720p (transmit and receive).
mxe# show media-statistics VC_CTS_INTEROP_APP.00000006
Statistics Parameters Transmit Receive
----------------------------------------------------------------------
Local : 10.194.60.75:16444 Remote : 10.194.60.49:51810
Local : 10.194.60.75:16446 Remote : 10.194.60.49:50960
Statistics Parameters Transmit Receive
----------------------------------------------------------------------
Local : 10.194.60.75:16452 Remote : 10.194.60.230:20774
Local : 10.194.60.75:16454 Remote : 10.194.60.230:22704
The '---' in the display indicates either the Stats Param type is not valid or stream is
not present in that direction.
For example 'Frames Lost' does not apply in the Tx direction.
Auxiliary audio stream is only received from CTS, not transmitted to it.
This example shows a summary of statistics for a point-to-point call between a videoconferencing endpoint (ID-1038) that is sharing content with a CTS (ID-2103).
In this example, the videoconferencing endpoint resolution is 360p (transmit) and 720p (receive) for main video. The CTS resolution is 720p (transmit and receive) for main video. For content sharing, the Cisco MXE-OS receives 720p from the videoconferencing endpoint and transmits XGA to the CTS (auxiliary stream).
The auxiliary field is the content sharing (presentation) stream to/from the CTS endpoint. Because the videoconferencing endpoint is presenting to the CTS endpoint, the Cisco MXE-OS only transmits to the CTS on the auxiliary video stream. It does not receive any auxiliary stream traffic from the CTS. This is reversed when the CTS endpoint is presenting to the videoconferencing endpoint.
mxe# show media-statistics VC_CTS_INTEROP_APP.00000006
Statistics Parameters Transmit Receive
----------------------------------------------------------------------
Local : 10.194.60.75:16444 Remote : 10.194.60.49:51810
Local : 10.194.60.75:16446 Remote : 10.194.60.49:50960
Local : 10.194.60.75:16448 Remote : 10.194.60.49:50478
Statistics Parameters Transmit Receive
----------------------------------------------------------------------
Local : 10.194.60.75:16452 Remote : 10.194.60.230:20774
Local : 10.194.60.75:16454 Remote : 10.194.60.230:22704
This example shows a summary of statistics for a point-to-point call between a CTS (ID-2103) that is sharing content with a videoconferencing endpoint (ID-1038).
In this example, the videoconferencing endpoint resolution is 360p (transmit) and 720p (receive) for main video. The CTS resolution is 720p (transmit and receive) for main video. For content sharing, the Cisco MXE-OS receives XGA from the CTS (auxiliary stream) and transmits 4CIF to the videoconferencing endpoint.
The auxiliary field is the content sharing (presentation) stream to/from the CTS endpoint. Because the CTS is presenting to the videoconferencing endpoint, the Cisco MXE-OS only receives from the CTS on the auxiliary video stream. The Cisco MXE-OS does not transmit any auxiliary stream traffic to the CTS. This is reversed when the videoconferencing endpoint is presenting to the CTS.
mxe# show media-statistics VC_CTS_INTEROP_APP.00000006
Statistics Parameters Transmit Receive
----------------------------------------------------------------------
Local : 10.194.60.75:16444 Remote : 10.194.60.49:51810
Local : 10.194.60.75:16446 Remote : 10.194.60.49:50960
Local : 10.194.60.75:16448 Remote : 10.194.60.49:50478
Statistics Parameters Transmit Receive
----------------------------------------------------------------------
Local : 10.194.60.75:16452 Remote : 10.194.60.230:20774
Local : 10.194.60.75:16454 Remote : 10.194.60.230:22704
Table 5-1 shows the media-statistic fields and their descriptions:
Table 5-1 Show Media-Statistics Field Descriptions
Statistic Parameters
|
Description
|
Audio
|
Statistics for the audio portion of call.
|
Video
|
Statistics for the video/content sharing portion of call.
|
Local
|
IPv4 address and RTP port on the Cisco MXE 5600.
|
Remote
|
IPv4 address and port of the remote endpoint.
|
Resolution
|
The endpoint transmit and receive video resolution.
|
Codec, frames, frame rate, frames lost, packets, and bytes (center | right | left | auxiliary)
|
Left and right audio stream data only appears for CTS or Cisco TelePresence Multipoint Switch (CTMS) endpoints.
|
IDR (center | auxiliary | legacyMix) stream
|
Instantaneous decoder refresh (IDR) frames.
The legacyMix audio stream only appears for CTMS endpoints for a WebEx-enabled CTMS conference.
|
---
|
Indicates that either the statistic parameter type is invalid or stream is not present in that direction.
|
Related Commands
shutdown (interface)
To disable an IP interface so that no packets can go through it, use the shutdown command. To enable the interface, use the no form of this command.
shutdown
no shutdown
Syntax Description
None
Defaults
None
Command Modes
Interface configuration
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
If this command is issued during a Telnet or Secure Shell Protocol (SSH) session, it will disconnect calls on the management interface and drop calls on the Ethernet interface
Examples
This example shows how to disable the MGT1 interface:
mxe(config)# interface mgt1
This example shows how to enable the Ethernet 1/1:
mxe(config)# interface ethernet 1/1
mxe(config-if)# no shutdown
Related Commands
Command
|
Description
|
interface
|
Configures the Ethernet or management interface.
|
shutdown (sip)
To disable the Session Initiation Protocol (SIP) interface so that no packets can go through it, use the shutdown command. To enable the interface, use the no form of this command.
shutdown [forced]
no shutdown [forced]
Syntax Description
forced
|
(Optional) Terminates all in-progress or established SIP calls automatically.
|
s
Defaults
None
Command Modes
Media service media-processing SIP configuration
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
None
Examples
This example shows how to disable the SIP interface:
mxe(config)# media service media-processing
mxe(config-media-service)# sip
mxe(config-media-service-sip)# shutdown
Related Commands
sip
To configure the SIP interface and enter the SIP configuration mode, use the sip command. To remove the SIP interface, use the no form of this command.
sip
no sip
Syntax Description
This command has no keywords or arguments.
Defaults
None
Command Modes
Media service media-processing
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
None
Examples
This example shows how to configure the SIP interface:
mxe(config)# media service media-processing
mxe(config-media-serv)# sip
mxe(config-media-serv-sip)#
Related Commands
stream-profile (media profile)
To apply a stream profile to media profile, use the stream-profile command. To remove this configuration, use the no form of this command.
stream-profile profile-id
no stream-profile profile-id
Syntax Description
Defaults
None
Command Modes
Media profile
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
Before using this command, you must configure a stream profile with the stream-profile (media service stream-processing) command.
For information about stream profiles, see the Configuration Guide for Cisco MXE-OS.
Examples
This example shows how to apply stream-profile 1 to media-profile 1:
mxe(config)# media service stream-processing
mxe(config-media-serv)# media-profile 1
mxe(config-media-serv-media-profile)# stream-profile 1
Related Commands
stream-profile (media service stream-processing)
To create or modify a stream profile and enter the stream-profile configuration mode, use the stream-profile command. To remove this configuration, use the no form of this command.
stream-profile profile-id
no stream-profile profile-id
Syntax Description
profile-id
|
Numeric identifier. The range is from 1 to 65535.
|
Defaults
None
Command Modes
Media service stream-processing
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
For information about stream profiles, see the Configuration Guide for Cisco MXE-OS.
Examples
This example shows how to configure a stream profile:
mxe(config)# media service stream-processing
mxe(config-media-serv)# stream-profile 1
mxe(config-media-serv-stream-profile)#
Related Commands
stream-type
To specify the stream type for a stream-profile, use the stream-type command. To remove this configuration and revert to the default, use the no form of this command.
stream-type {audio | video | presentation | bfcp}
no stream-type {audio | video | presentation | bfcp}
Syntax Description
audio
|
Configures the stream type as audio.
|
video
|
Configures the stream type as video.
|
presentation
|
Configures the stream type as presentation (for content sharing).
|
bfcp
|
Configures the stream type as Binary Floor Control Protocol (BFCP).
|
Defaults
Audio
Command Modes
Stream-profile
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
1.2
|
The presentation and bfcp keywords were added.
|
Usage Guidelines
Before using this command, you must first create a stream profile with the stream-profile (media service stream-processing) command.
A media profile can include 0 or 1 presentation streams, and 0 or 1 BFCP streams. When you configure a presentation stream, you must also configure a BFCP stream. A presentation stream is subject to all the same options and constraints as a video stream.
Examples
This example shows how to configure the stream type for a stream-profile 1:
mxe(config)# media service media-processing
mxe(config-media-serv)# stream-profile 1
mxe(config-media-serv-stream-profile)# stream-type video
Related Commands
transport
To configure the transport for a stream-profile's media, use the transport command. To remove this configuration, use the no form of this command.
transport {rtp-avp}
no transport {rtp-avp}
Syntax Description
rtp-avp
|
Configures Real Time Protocol (RTP) audio video profile (AVP).
|
Defaults
RTP/AVP
Command Modes
Stream-profile
Supported User Roles
network-admin
Command History
Release
|
Modification
|
1.0
|
This command was introduced.
|
Usage Guidelines
Before using this command, you must first create a stream profile with the stream-profile (media service stream-processing) command.
Examples
This example shows how to configure the transport for a stream-profile 1:
mxe(config)# media service media-processing
mxe(config-media-serv)# stream-profile 1
mxe(config-media-serv-stream-profile)# transport rtp-avp
Related Commands