The ME system and management software uses a license to provide you with the specific features and capacity you requested. When you purchased the ME, you selected the features or bundles of features desired. You were then provided with a license file that enabled those features and set the permissible number of sessions or endpoints.
The features object allows you to modify the session/endpoint values. Note that you can not exceed the value specified in the license. To obtain more capacity, contact Technical Support or your sales representative.
Temporarily modifies your existing ME software license to support a different capacity (either number of sessions or endpoints). You can only set the capacity for a session/endpoint to a value lower than the number allowed by your license. For example, you may have a license that allows 5000 IM sessions. You can use this configuration object to temporarily allow only 3000 sessions. You can also reset the feature to full capacity through this object.
Note that the properties you see at the CLI depend on the software features that your license supports. There are additional ”non-royalty” CODECs that the system supports but that are also not displayed in the CLI. (These field values appear greyed-out when displaying the feature list from the ME Management System). You must obtain a license update to make those feature values configurable. The Properties table provides a complete list of licensable software features in the ME.
The default value for all properties is the maximum capacity permitted by your license.
signaling-sessions: Enables the system to perform stateful, application-level inspection, processing, and routing of SIP signaling streams. To be operational, an ME cluster requires a signaling and/or media processing software license.
media-sessions: Enables the system to anchor and route SIP-associated media streams (audio, video, file transfer, etc.). To be operational, an ME cluster requires a signaling and/or media processing software license. Also, each system media proxy must be controlled by a system signaling proxy, which may be co-resident in the same ME chassis as the signaling proxy or in a different system chassis.
instant-message-and-presence-sessions: Enables the system to perform stateful, application-level inspection, processing, and routing of SIP/SIMPLE-based instant messaging and presence traffic. The IM and presence proxy must be co-resident with a signaling proxy on the same system chassis.
high-availability-sessions: Enables the system to participate in an active-active or active-standby high-availability cluster.
authentication-access-sessions: Validates the identities of users and/or domains cryptographically, preventing unauthorized users from gaining access to network resources. Integrates with existing authentication and credentialing systems via standard protocols (RADIUS, PKI, DIAMETER, etc.).
signaling-encryption-sessions: Encrypts and decrypts SIP signaling message headers and bodies using TLS. This ensures the authenticity, confidentiality, and integrity of SIP signaling streams.
media-encryption-sessions: Encrypts and decrypts SIP-associated media sessions (audio, video, file transfer, etc.) using the Secure Real-time Transport Protocol (SRTP). This ensures the authenticity, confidentiality, and integrity of real-time media information.
media-validation-sessions: Ensures that the media sessions set up by a SIP user agent is the same as the session that was negotiated during the associated signaling dialogs and permitted by media control policies. This prevents both attacks that exploit the independence of SIP signaling and media channels and unauthorized consumption of bandwidth.
dos-protection-sessions: Detects and mitigates brute force (resource exhaustion) DOS attacks. Monitors short-term network, transport, and application-level connection activity, detects abnormal aggregate signaling patterns, and denies resources to sessions that match the attack profile.
session-admission-control-sessions: Limits calling activity based on administratively defined thresholds for session count, total bandwidth, and/or observed quality of service (QOS) metrics. Session admission control policies can be defined on logical and/or physical network interfaces.
media-control-sessions: Enables fine-grained control over SIP-associated media sessions. For example, an administrator could define a policy saying that only people in a particular group or department (as defined in the directory) can do video sessions.
qos-control-sessions: Enables control of the QoS of SIP-based applications by performing policy based L2/L3 QoS marking.
session-routing-control-sessions: Implements intelligent session routing policies such as application-aware load balancing and inbound call routing (e.g., parallel fork, sequential search, presence based routing, and others).
file-transfer-control-sessions: Enables policy-based control over SIP file transfers.
instant-message-content-control-sessions: Enforces acceptable use policies on the content of instant messages. Scans IM content for string patterns matching regular expressions and takes a policy-defined action when it finds a match.
url-control-sessions: Controls propagation of URLs embedded in SIP-based instant messages. This enables enforcement of acceptable use policies and prevents the propagation of blended threats via SIP applications.
session-detail-recording-sessions: Creates detailed records for signaling sessions that traverse the ME. From this you can track the usage of SIP-based services and applications.
qos-detail-recording-sessions: Creates QoS records for media sessions that traverse the system, providing data for network engineering, capacity planning, and troubleshooting.
audio-recording-sessions: Enables policy-based recording of audio session content, demonstrating compliance with electronic communications monitoring policy and regulation.
video-recording-sessions: Enables policy-based recording of video session content, demonstrating compliance with electronic communications monitoring policy and regulation.
file-recording-sessions: Enables policy-based recording of file transfer session content, demonstrating compliance with electronic communications monitoring policy and regulation.
file-mirror-db-size: Enables file mirroring and sets the number of files the system can concurrently mirror.
instant-message-recording-sessions: Enables policy-based recording of IM session content, demonstrating compliance with electronic communications monitoring policy and regulation.
nat-traversal-sessions: Enables SIP-based applications to traverse remote NAT/firewall functions that may not be under the organization's authority or control. This extends SIP-based applications and services to remote endpoints.
directory-integration-sessions: Enables the system to import information from directories with Lightweight Directory Access Protocol (LDAP) interfaces so that administrators can define and enforce directory-based policies.
lcs-sametime-gateway-sessions: Enables presence visibility and messaging connectivity between Microsoft Live Communication Server (LCS) and IBM Lotus Sametime communities.
transcode-sessions: Enables transcoding media types, which is the process of converting media from one CODEC into a different CODEC on output.
provisional-transcode-sessions: Enables provisional transcoding sessions. These sessions are temporary sessions used until the system has established whether a call needs transcoding. If it does require transcoding, the session then uses the transcode-sessions license.
g723 | g728 | g729 | g726-16 | g726-24 | g726-32 g726-40 | gms | gsm-amr | ilbc | g722-1: Sets the maximum number of concurrent CODEC sessions available for encoding/decoding. The limit does not apply to forwarding or recording RTP packets, only to:
Making a transcoded call (see Transcoding Media Types for more information)
Playing recorded announcements
Mixing recorded calls for playback
Playing back of recorded calls
Archiving calls.
Note that if you have the media object music-on-hold property enabled, the ME holds open one license seat for playing the music until the rtp-cache is released (e.g., system reboot or rtp-header action). This applies to each CODEC type used for playing music on hold. For other announcements and DTMF generation (as audio), the system requires one license until the entire announcement or tone is cached, and the seat is released.
The default setting for these properties is the maximum number of allowable licenses. For g723, g729, gsm-amr, and g722-1, the number of available license seats is more restrictive. Contact Technical Support for additional capacity.
monitoring-calls: Sets the maximum number of monitored calls allowed concurrently.
csta-sessions: Sets the maximum number of concurrent CSTA sessions allowed.
h264: Specifies the maximum concurrent number of H264 encoders and decoders for playout, announcements, mixing, or transcoding.
Default: 200000
Values: Min: 0 / Max: 200000
Example: set h264 150000
speex: Specifies the maximum concurrent number of Speex encoders and decoders for playout, announcements, mixing, or transcoding.
Default: 200000
Values: Min: 0 / Max: 200000
Example: set speex 150000
silk: Sets the maximum number of concurrent SILK sessions available for encoding and decoding. The limit does not apply to forwarding or recording RTP packets, only making transcoded calls, playing recorded announcements, mixing recorded calls for playback, playing back recorded calls, and archiving calls.
Default: 200000
Values: Min: 0 / Max: 200000
Example: set silk 150000
amr-wb: Sets the maximum number of concurrent AMR-WB sessions available for encoding and decoding. The limit does not apply to forwarding or recording RTP packets, only to making transcoded calls, playing recorded announcements, mixing recorded calls for playback, playing back recorded calls, and archiving calls.
Default: 200000
Values: Min: 0 / Max: 200000
Example: set amr-wb 100000
control-sessions: Sets the maximum number of control sessions for signaling or web-services.
file-services: Sets the maximum number of sessions for file playback or recording.
Default: 100
Values: Min: 0 / Max: 100
Example: set file-services 75
web-audio: Sets the maximum number of sessions for Flash audio.
web-video: Sets the maximum number of sessions for Flash video.
conferencing: Sets the maximum number of sessions for third-party conferencing.