Table of Content

Table of Contents

1 Report Information 1.1 Report Generation 2 Status 2.1 General Status 2.2 Licensing 3 System 3.1 General Configuration 3.2 Cluster Settings 3.3 Database Settings 3.4 TURN Servers 3.5 Web Bridges 3.6 Recorders 3.7 Streamers 3.8 XMPP Settings 3.9 CDR Receivers 4 Directory 4.1 Active Directory 4.2 Directory Search Locations 4.3 LDAP 4.3.1 LDAP Servers 4.3.2 LDAP Mappings 4.3.3 LDAP Sources 4.3.4 LDAP Syncs 5 Profiles 5.1 Call Branding Profiles 5.2 DTMF Profiles 5.3 Call Profiles 5.4 Call Leg Profiles 5.5 Compatibility Profiles 5.6 IVR Branding Profiles 6 Users 6.1 User Profiles 6.2 CMA User Settings 6.3 Users 7 Tenants and Tenant Groups 7.1 Tenants 7.2 Tenant Groups 8 Spaces 9 Calls 9.1 Call Bridges 9.2 Call Bridges Group 9.3 Call Settings 9.4 Incoming Calls 9.4.1 Incoming Dial Plan Rules 9.4.2 Call Forwarding 9.5 Outbound Calls 9.5.1 Outbound Dial Plan Rules 9.5.2 Dial Transforms 9.6 IVR 10 Command Line Output 10.1 Server 10.1.1 Hostname of CMS 10.1.2 IPv4 Address Port A 10.1.3 IPv6 Address Port A 10.1.4 IPv4 Address Port B 10.1.5 IPv6 Address Port B 10.1.6 ntp server list 10.1.7 Time Zone Configuration 10.1.8 used DNS server to resolve DNS 10.1.9 User List 10.1.10 Syslog Configuration 10.1.11 WebAdmin Configuration 10.1.12 Call Bridge Configuration 10.1.13 Web Bridge Configuration 10.1.14 XMPP Configuration 10.1.15 XMPP Call Bridge Configuration

1 Report Information

Cisco Meeting Server carries on-premise audio, video and web communication. It works with third-party devices and can be integrated with Cisco Communications Manager for adhoc video meetings.

Participants can join the meeting via Cisco or third-party video endpoints, a Cisco Jabber client, Cisco Meeting App, either native or via a WebRTC-compatible browser, or Skype for Business to participate in the meeting.

Cisco Meeting Server, Cisco Meeting App, and Cisco Meeting Management have been optimized to be installed with Cisco Unified Communications Manager, Cisco Expressway or Video Communication Server (VCS) for call control, Cisco Expressway for firewall traversal, and Cisco TelePresence Management Suite for scheduling.

Most configurations of the Cisco Meeting Server are performed through the CMS API via XML requests. The CMS also includes a Web Admin with limited configuration options that include:

1.1 Report Generation

This configuration report for Cisco Meeting Server has the following details:

Report Info
Report Date27-Apr-20 1:37:16 PM
Report generated forCustomer
DescriptionAs-Built Documentation for project
Server Info
CMS version2.9
CMS IP10.5.1.127
Report Settings
Report TypeDirect Report
Visual StyleBlu Dark.css
Report ContentAll objects
Template HTMLCMSreportTemplate.htm
Template WordGears-Blue-universal.doc
Report Tool Info
Report Tool Version12.0.24 / ?? May 2020
Report Tool LicenseLicensed [Ent all]

2 Status

This section contains:

2.1 General Status

The following table shows the system status.

System Status
Uptime3 days, 20 hours, 3 minutes
Build version2.9
Media module status1/1 (full media capacity)
XMPP connectionfailed to connect to due to TCP failure (27 seconds ago)
Authentication serviceno authentication components found
Lync Edge registrations3 configured, 3 in progress
CMA calls0
SIP calls0
Lync calls0
Forwarded calls0
Completed calls0
Activated conferences0
Active Lync subscribers0
Total outgoing media bandwidth0
Total incoming media bandwidth0

2.2 Licensing

You will need activation keys and licenses for the Cisco Meeting Server and Cisco user licenses. The following activation keys or licenses are required to use the Cisco Meeting Server:

The following licenses are present:

Call BridgenoLicense
Call Bridge No EncryptionnoLicense
Web BridgenoLicense
Capacity UnitsnoLicense
Multiparty Licensing
Personal License Limit0
Shared License Limit0
Capacity Unit Limit0
Personal Licenses253
Participants Active0
Calls Active0
Weighted Calls Active0.000
Calls Without Personal License0
Weighted Calls Without Personal License0.000
Capacity Unit Usage0.000
Capacity Unit Usage Without Personal License0.000
Active Personal Licenses
Active Personal Licenses

3 System

The System section contains the following configuration items:

3.1 General Configuration

The menu Configuration > General of the Web Admin interface on the Meeting Server shows a summarized collection of General Configuration settings.

General Configuration
XMPP server settings
Unique Call Bridge nameCallBridge02
Server address10.5.1.166
TURN Server settings
TURN Server address (CMS)
TURN Server address (CMA)
Lync Edge settings
Server address10.5.1.166
Number of registrations3
Web bridge settings
Guest account client URI
Guest account JID domainGuestClientURI
Guest access via ID and passcodedisabled
Guest access via hyperlinksenabled
User sign inenabled
Joining scheduled Lync conferences by IDdisabled
IVR numeric ID888958
Joining scheduled Lync conferences by IDdisabled
External access
Web Bridge
IVR telephone number55518643

3.2 Cluster Settings

This Call Bridge node has the following settings:

Cluster Settings
Unique NameCallBridgeCluster
Peer Link Bit Rate128
Max Peer Video Streams
Participant Limit5
Load Limit10000
New Conference Load Limit Basis Points5000
Existing Conference Load Limit Basis Points4980

3.3 Database Settings

The CallBridge reads from and writes to the database storing the space and configuration information. Database clustering can be disabled or enabled across cluster nodes. If enabled, it contains total nodes and the master name is in the 'Node In Use' setting.

<database clustered="disabled"></database>

3.4 TURN Servers

The TURN server provides firewall traversal technology, allowing the Meeting Server to be deployed behind a Firewall or NAT. To connect to the deployment from external Cisco Meeting Apps, Lync clients or SIP endpoints registered to a SIP or voice call control device, you need to enable the TURN server.

Note: Cisco plans to remove the TURN server component from the Cisco Meeting Server software in a future version.

The following TURN Servers are configured:

TURN Servers
Server Address10.5.1.166
Num Registrations5

3.5 Web Bridges

The Web Bridge is required for Cisco Meeting Apps to look up guest login when using a web browser that does not support WebRTC (for example Internet Explorer). The Web Bridge is used by the WebRTC app. If you are deploying the WebRTC app you need to set the network interface for the Web Bridge and then enable it.

The following Web Bridge elements can be rebranded via the API:

Web Bridges
Resource Archivehttp://localhost
Resolve Co Space Call Idsfalse
Resolve Lync Conference Idsfalse
Tenant Groupf0fdcf04-1ac1-483f-a4c5-13cd8f699ff7
Id Entry Modedisabled
Allow Weblink Accessfalse
Show Sign Intrue
Call Bridgeabf7a694-8a70-430b-be35-b2da6d37cdc2

3.6 Recorders

The Recorder component on the Meeting Server adds the capability of recording meetings and saving the recordings to a document storage such as a network file system (NFS). At the end of recording a meeting, the recording is automatically converted to MP4. The converted file is suitable for placing within a document storage/distribution system,

Only enable the Recorder on the same server as the Call Bridge if you are simply evaluating the feature. For normal deployment enable the Recorder on a different server to the Call Bridge.

Recording is controlled by license keys, where one license allows one simultaneous recording. The license is applied to the server hosting the Call Bridge (core server) which connects to the Recorder, not the server hosting the Recorder.

Call Bridge Group2a50b110-704e-4073-adb4-7b2b3a40dded

3.7 Streamers

The Streamer component adds the capability of streaming meetings held in a space to the URI configured on that space.

An external streaming server needs to be configured to be listening on this URI. The external streaming server can then offer live streaming to users, or it can record the live stream for later playback.

Several standards-based streaming servers are known to work with the Streamer, but Cisco only offers support for VBrick as an external streaming server. One or more licenses for streaming need to be loaded on the Meeting Server hosting the Call Bridge, not the server hosting the Streamer.

Call Bridgeabf7a694-8a70-430b-be35-b2da6d37cdc2

3.8 XMPP Settings

The XMPP server handles the signalling and media to and from CMA clients, including the WebRTC client. Extensible Messaging and Presence Protocol (XMPP) is a communication protocol for message-oriented middleware based on XML (Extensible Markup Language). It enables the near-real-time exchange of structured yet extensible data between any two or more network entities. CMS uses XMPP to achieve resiliency when several CMS servers are present.

XMPP servers uses keep-alive messages to monitor each other and to elect a Leader. XMPP messages can be sent to any server. As shown in the preceeding image, messages are forwarded to the Leader XMPP server. The XMPP servers continue to monitor each other, if the Leader fails then a new Leader is elected and the other XMPP servers forward traffic to the new Leader.

XMPP Settings
Unique NameCallBridge02
Server Address Override10.5.1.166

3.9 CDR Receivers

The Meeting Server generates Call Detail Records (CDRs) internally for key call-related events, such as a new SIP connection arriving at the server, or a call being activated or deactivated. It can be configured to send these CDRs to a remote system to be collected and analyzed.

There is no persistent storage of CDRs on Meeting Servers; CDRs are temporarily buffered on the Meeting Server before being streamed to the CDR storage receiver. When they have been sent to the CDR receiver, CDRs are removed from the Meeting Server. The Meeting Server supports up to 4 CDR receivers.

The following CDR receivers are configured:

CDR Receivers
Cdr Receiverhttp://lab.test
Cdr ReceivercdrReceivers1
Cdr ReceivercdrReceivers2

4 Directory

The Directory section contains the following configuration items:

4.1 Active Directory

For users to utilize the Cisco Meeting Apps to connect to the Meeting Server, an LDAP server (currently Microsoft Active Directory or OpenLDAP) must be configured. The Meeting Server imports the User accounts from the LDAP server.

The server uses the concept of filters, rules and templates, which allow you to separate users into groups.

The Web Admin interface on the Meeting Server can only configure one single LDAP server as shown below. However, the Meeting Server supports multiple LDAP servers which can be configured via the API. Those are listed in the following section LDAP.

Active Directory
Active Directory Server Settings
Secure connectionfalse
Corporate Directory Settings
Restrict search to searcher OUfalse
Import Settings
Base distinguished nameDC=lab,DC=test
Field Mapping Expressions
Display name$cn$
Space name$sAMAccountName$.space
Space URI user part
Space secondary URI user part
Space call ID88$telephoneNumber$

4.2 Directory Search Locations

This section shows additional external directory search locations that the Call Bridge will consult when users of Cisco Meeting Apps perform searches.

Directory Search Locations
Ldap Server6d29eb05-4f4b-4bb4-8bd0-025dcc9be3bb
Base Dnusers
Filter Format$1
First Namesn
Last NamegivenName
Display Namecn

4.3 LDAP

The LDAP configuration items relate to the Meeting Server's interaction with one or more LDAP servers (for instance, Active Directory), used to import user accounts to the Meeting Server. Multiple LDAP servers can only be configured via the API. These LDAP settings are shown here. This section contains:

4.3.1 LDAP Servers

One or more LDAP servers should be configured, with each one having associated username and password information for the Meeting Server to use to connect to it, for the purpose of retrieving user account information.

The passwords are not cached on the Meeting Server, a call is made to the LDAP server when a Cisco Meeting App authenticates, and therefore passwords are managed centrally and securely on the LDAP server.

LDAP Servers
Port Number389
Use Paged Resultstrue

4.3.2 LDAP Mappings

LDAP mappings define the form of the user account names which will be added to the system when users are imported from configured LDAP.

The following LDAP mappings are configured:

LDAP Mappings
Jid Mapping$sAMAccountName$@lab.test
Name Mapping$cn$
Cdr Tag Mapping
Co Space Name Mapping
Co Space Uri Mapping
Co Space Secondary Uri Mapping
Co Space Call Id Mapping
Authentication Id Mapping

4.3.3 LDAP Sources

LDAP Sources tie together configured LDAP servers and LDAP mappings, along with parameters of its own, which correspond to the actual import of a set of users. An LDAP source takes an LDAP server and an LDAP mapping combination and imports a filtered set of users from that LDAP server. This filter is determined by the LDAP source's "baseDn" (the node of the LDAP server's tree under which the users can be found) and a filter to ensure that user accounts are only created for LDAP objects that match a specific pattern.

The following LDAP Sources are configured:

No Records

4.3.4 LDAP Syncs

The following LDAP Syncs are pending or in-progress:

No Records

5 Profiles

This chapter lists the Profiles. They include:

5.1 Call Branding Profiles

Call branding profiles can define the experience when dialing into a scheduled conference.

To customize the language, the language files by Cisco were used and made available to the CMS via the IIS web server at the specified domain. The same applies to the customized background picture. At the TMS you will find this directory under C:\inetpub\wwwroot\Branding-CMS.If you want to change these files, you can do this in this directory without having to adjust the configuration of the CMS. For more details, please see the Customization Guidelines by Cisco.

The following Interactive Call Branding Profiles are configured:

Call Branding Profiles
Resource Locationhttp://
Invitation Templatehttp://

5.2 DTMF Profiles

DTMF Profiles can be used to define a number of DTMF sequences that can be used to control audio. The DTMF Profile does not define the ability to perform the actions, it defines the DTMF string that will invoke action. The definition for who has the authority to invoke that action within the coSpace is defined at the callLegProfile level.

The following DTMF Profiles are configured:

DTMF Profiles
Mute Self Audio2200
Unmute Self Audio2201
Toggle Mute Self Audio*6
Lock Call22
Unlock Call23
Mute All Except Self Audio22001
Unmute All Except Self Audio22002
End Call22016
Next Layout2201
Previous Layout2202
Start Recording22003
Stop Recording22004
Start Streaming22005
Stop Streaming22006
Allow All Mute Self22007
Cancel Allow All Mute Self22008
Allow All Presentation Contribution22009
Cancel Allow All Presentation Contribution22010
Mute All New Audio22011
Unmute All New Audio22012
Default Mute All New Audio22013
Mute All New And All Except Self Audio22014
Unmute All New And All Except Self Audio22015
Get Total Participant Count

5.3 Call Profiles

Call Profiles control the maximum number of active simultaneous participants and the in-call experience for SIP calls. Call Profiles can be attached at the system, tenant or coSpace level, with the most specific taking effect.

The following Call Profiles are present:

Call Profiles
Participant Limit
Message Board Enabled
Streaming Mode
Gateway Audio Call Optimization
Lync Conference Mode
Lock Mode
Sip Recorder Uri
Participant Limit5
Message Board Enabledtrue
Streaming Modemanual
Gateway Audio Call Optimizationtrue
Lync Conference ModedualHomeCluster
Lock Modeall
Sip Recorder Uri

5.4 Call Leg Profiles

A Call Leg Profile defines a set of in-call behaviors. A call leg is a logical connection; a voice call compromises two call legs. The values in the Call Leg Profile set for a coSpace would be used for call legs in that coSpace, overriding any values set in the Call Leg Profile specified for the tenant that the coSpace is associated with. CoSpace, coSpaceUser, accessMethod, and tenant objects can optionally have a Call Leg Profile association.

The following Call Leg Profiles are present:

Call Leg Profiles
Presentation Viewing Allowed
Tx Audio Mute
Rx Video Mute
Tx Video Mute
Deactivation Mode
Video Mute Others Allowed
Disconnect Others Allowed
Add Participant Allowed
Presentation Viewing Allowedtrue
Tx Audio Mutefalse
Rx Video Mutefalse
Tx Video Mutetrue
Deactivation Modedeactivate
Video Mute Others Allowedfalse
Disconnect Others Allowedtrue
Add Participant Allowedtrue

5.5 Compatibility Profiles

Compatibility Profiles contain compatibility settings for SIP calls including:

Compatibility Profiles
Sip Udttrue
Sip Multistreamfalse
Sip Media Payload Type Modeauto
H264 CHP Modeauto
Chrome Web Rtc Video CodecavoidH264

5.6 IVR Branding Profiles

IVR branding profiles can define the experience when dialing into an IVR. An Interactive Voice Response (IVR) Branding Profile is assigned to a tenant.

The following Interactive Voice Response (IVR) Branding Profiles are configured:

IVR Branding Profiles
IDResource Location

6 Users

The section Users contains:

6.1 User Profiles

User profiles control the facilities provided to the users in the profile, for instance whether they can create new spaces, create new calls, make phone calls, slave SIP endpoints or be allowed to send and receive chat messages when in a point to point call with another user.

User Profiles
Can Create Co Spacesfalse
Can Create Callstrue
Can Use External Devicestrue
Can Make Phone Callsfalse
User To User Messaging Allowedtrue
Audio Participation Allowedfalse
Video Participation Allowedtrue
Presentation Participation Allowedfalse
Has Licensetrue
Can Receive Callstrue
Can Send Email Invitetrue

6.2 CMA User Settings

Use the Configuration > CMA user settings page to allow or not allow incoming calls to Cisco Meeting App users.

By default incoming calls to Cisco Meeting Apps are allowed, however this behavior can be changed so that incoming calls are not allowed to users of the Cisco Meeting App.

CMA User Settings
CMA user settings
Allow incoming callsallowed

6.3 Users

If you plan for users to utilise the Cisco Meeting Apps to connect to the Meeting Server, then you must have an LDAP server. User accounts are imported from the LDAP server. You can create user names by importing fields from LDAP as described in LDAP configuration. The passwords are not cached on the Meeting Server, they are managed centrally and securely on the LDAP server. When a Cisco Meeting App authenticates, a call is made to the LDAP server.

Multi-tenancy means that groups of users can be entirely segmented within the solution as required by service provider deployments e.g. users will only be able to meet, assign users to spaces, and search in the directory within the same configured customer groups.

The following users have been imported:

IDUser JidNameEmailcoSpaces
d88e6995-b3c4-465d-bd59-7d3ab46816351300.ORANGE@lab.test1300 [471d5ac9-def8-4d59-bea9-fcec81873bdf]
c01b302a-9bae-4ee3-ab88-04358bb314f5AD2013$@lab.testAD2013 AD2013$.space [60c51ca6-ff16-42c9-bc0d-6f024074e3c5]
bf93ee50-b84d-4d25-892a-67b983aee57aaps_user_template@lab.testAPS UserTemplate  
2642868f-1150-42fa-bfb2-4b2094df5f31Access\20Control\20Assistance\20Operators@lab.testAccess Control Assistance Operators Access Control Assistance [59191a1c-1b41-4697-8e88-fbdd65d16563]
4709696c-2853-4306-a325-f385e085b915Account\20Operators@lab.testAccount Operators Account [31cf969d-c593-4582-84bf-b4ae906297f7] [9f69b6f9-e330-41e9-9943-c9e4f2d95b92]
734c4b63-abc1-4105-87ec-a0f697c252c3Administrators@lab.testAdministrators [8091952b-bacc-449b-b2ca-314052068960]
9687c872-1cee-467a-ab4d-b8eb83fccf72aberg@lab.testAlec Bergaberg2@lab.test 
ccb0203b-7cb1-40a2-bbed-33536523a410Allowed\20RODC\20Password\20Replication\20Group@lab.testAllowed RODC Password Replication Group Allowed RODC Password Replication [19fdaee0-f70d-47e2-be2f-77773a0e6abc]
cbd81a5b-a00f-4467-9747-217243cbd87bajolie@lab.testAngelina Jolieajolie@lab.test 
bead3fb4-7ed6-4359-8522-b5c9475a0e32akutcher@lab.testAshton Kutcherakutcher@lab.test 
603aef48-fab4-43ba-a86b-514b2ca91d2casterix@lab.testAsterix TheGauloisasterix@lab.test 
351b3a43-3f60-4817-8c20-255060072c09Backup\20Operators@lab.testBackup Operators Backup [1b268b22-e5e6-4203-a00b-40b2e51f7b27]
f116a255-1e49-4e70-a879-114e5186a30dbbreu@lab.testBeat Breubbreu@lab.test 
2ef715ab-a3f9-45ff-b3eb-79ccf496c21bbpitt@lab.testBrad Pittbpitt@lab.test 
e01e9ffb-09ef-4cce-856c-9104ee879e54bwayne@lab.testBruce Wayne  
54f7835c-0158-4edc-8020-b4994cec86f9bwillis@lab.testBruce Willisbwillis@lab.test 
409500a8-27b6-4cb2-8bf7-925dbf2dec7bCSAdministrator@lab.testCSAdministrator [3ec47840-4dff-46bf-b035-1d85d30813c4]
d32f90a3-0920-4805-9824-787691170677CSArchivingAdministrator@lab.testCSArchivingAdministrator [f0c56f28-f68e-4140-9efe-857a8dcca408]
6ccdbff5-fe69-4dd9-9786-6e716c701d6aCSHelpDesk@lab.testCSHelpDesk [93c1b456-6f9e-422f-8471-1d2a1bc0405f]

7 Tenants and Tenant Groups

The Meeting Server supports multi-tenancy; this refers to sub-dividing its capacity into a set of islands where each island has all of the functionality of the unit as a whole, but has no access to the resources (for instance users, coSpaces, or active calls) of other tenants. This section contains:

7.1 Tenants

The Meeting Server supports multi-tenancy; this refers to sub-dividing its capacity into a set of islands where each island has all of the functionality of the unit as a whole, but has no access to the resources (for instance users, spaces, or active calls) of other tenants.

The following tenants are configured:

Tenant Groupf0fdcf04-1ac1-483f-a4c5-13cd8f699ff7
Call Leg Profile1341d26e-4938-4185-ad44-e705a62f7609
Dtmf Profilebf120939-8321-4af8-a8c6-c90b54c062f5
User Profile038428bb-ed7f-4ec4-b99a-6833c72bb0a0
Participant Limit5

7.2 Tenant Groups

Multi-tenancy is supported where multiple deployments can be hosted on the same server. This feature is provided by assigning tenants to a tenant group. This provides a mechanism for splitting tenants into separate independent groups. Each group consists of one or more tenants.

Tenant Groups

8 Spaces

Spaces are meeting spaces that are created by users, the API or through CMS Admin. Once a Space is created, users can be invited to join the meeting in that Cisco Meeting Server space. In the API they are referred to as coSpaces.

The following Spaces are configured:

Auto Generatedfalse
Non Member Access
Owner Id
Owner Jid
Auto Generatedtrue
Non Member Accesstrue
Owner Id632baa7b-1b8e-4e28-a113-4fd26d0d9611
Owner Jid$031000-R0MRT8R7O01C@lab.test
Auto Generatedtrue
Non Member Accesstrue
Owner Id5c085574-48dd-4a36-897e-97b5313b2afa
Owner Jid$731000-55PC635I18FI@lab.test
Auto Generatedtrue
Non Member Accesstrue
Owner Idd88e6995-b3c4-465d-bd59-7d3ab4681635
Owner Jid1300.ORANGE@lab.test
Auto Generatedtrue
Non Member Accesstrue
Owner Idc01b302a-9bae-4ee3-ab88-04358bb314f5
Owner JidAD2013$@lab.test
NameAccess Control Assistance
Auto Generatedtrue
Non Member Accesstrue
Owner Id2642868f-1150-42fa-bfb2-4b2094df5f31
Owner JidAccess\20Control\20Assistance\20Operators@lab.test
Auto Generatedtrue
Non Member Accesstrue
Owner Id4709696c-2853-4306-a325-f385e085b915
Owner JidAccount\20Operators@lab.test
Auto Generatedtrue
Non Member Accesstrue
Owner Id73b7ae6d-f43e-45a6-8986-bab08bfff591
Owner JidAdministrator@lab.test
Auto Generatedtrue
Non Member Accesstrue
Owner Id734c4b63-abc1-4105-87ec-a0f697c252c3
Owner JidAdministrators@lab.test
NameAllowed RODC Password Replication
Auto Generatedtrue
Non Member Accesstrue
Owner Idccb0203b-7cb1-40a2-bbed-33536523a410
Owner JidAllowed\20RODC\20Password\20Replication\20Group@lab.test
Auto Generatedtrue
Non Member Accesstrue
Owner Id351b3a43-3f60-4817-8c20-255060072c09
Owner JidBackup\20Operators@lab.test
Auto Generatedtrue
Non Member Accesstrue
Owner Id409500a8-27b6-4cb2-8bf7-925dbf2dec7b
Owner JidCSAdministrator@lab.test
Auto Generatedtrue
Non Member Accesstrue
Owner Idd32f90a3-0920-4805-9824-787691170677
Owner JidCSArchivingAdministrator@lab.test
Auto Generatedtrue
Non Member Accesstrue
Owner Id6ccdbff5-fe69-4dd9-9786-6e716c701d6a
Owner JidCSHelpDesk@lab.test
Auto Generatedtrue
Non Member Accesstrue
Owner Idfa3d161d-a366-4b9a-8fc1-01b487c41758
Owner JidCSLocationAdministrator@lab.test
Auto Generatedtrue
Non Member Accesstrue
Owner Id4a17bee7-0443-42ed-ba2f-2e9735513a7b
Owner JidCSResponseGroupAdministrator@lab.test
Auto Generatedtrue
Non Member Accesstrue
Owner Ida39e8406-d530-4b88-8b59-b6c7011875f6
Owner JidCSResponseGroupManager@lab.test
Auto Generatedtrue
Non Member Accesstrue
Owner Idc31b1144-5abd-4892-a516-286b1f99c4cc
Owner JidCSServerAdministrator@lab.test
Auto Generatedtrue
Non Member Accesstrue
Owner Id3021c78f-f679-4e97-b86f-ea98092151d8
Owner JidCSUserAdministrator@lab.test
Auto Generatedtrue
Non Member Accesstrue
Owner Idf2c6fd77-b780-49e7-a19a-ca29310aee59
Owner JidCSViewOnlyAdministrator@lab.test

9 Calls

The Calls section contains the following configuration items:

9.1 Call Bridges

The Call Bridge is the component on the Meeting Server that bridges the conference connections, enabling multiple participants to join meetings hosted on the Meeting Server or Lync AVMCUs. The Call Bridge exchanges audio and video streams so that participants can see and hear each other. The Call Bridge license allows the Call Bridge to be used for media calls.

The following Call Bridges are configured:

Call Bridges
Sip DomainSipDom01
Call Bridge Group2a50b110-704e-4073-adb4-7b2b3a40dded

9.2 Call Bridges Group

Deployments with Cisco Unified Communications Manager and clustered Meeting Servers can use the Call Bridge Grouping feature to load balance calls on the Meeting Servers. Load balancing aims to avoid overloading individual Meeting Servers in the cluster. Using Call Bridge groups, a Meeting Server cluster can intelligently load balance calls across the Call Bridges within the same location or across nodes in different locations. The intelligent decision making behind where calls end up is handled by the Meeting Servers.

The call control system needs to be able to handle SIP messages from the Meeting Servers, in order to move calls to the correct location. This functionality has been tested using Cisco Unified Communications Manager as a call control system, which is the only Cisco supported call control system for this functionality.

The following Call Bridge Groups are configured:

Call Bridge Groups
Load Balancing Enabledtrue
Load Balance Lync Callsfalse
Load Balance Outgoing Callstrue
Load Balance User Callstrue
Load Balance Indirect Callsfalse

9.3 Call Settings

Use the Configuration > Call settings page to:

The Call settings page also allows you to change the bandwidth settings for SIP, Cisco Meeting Server (CMA), Server reflexive, Relay, VPN, and Lync content. The settings are measured in bitsper- second, for example, 2000000 is 2Mbps. We dedicate at least 64kbps for audio, and recommend 2Mbps for a 720p30 call, or around 3.5Mbps for a 1080p30 call. More bandwidth would be required for 60fps.

You may need to change some of the bandwidth settings if you allow SIP media encryption, or enable TIP support, for example. In the case of 3 screen TIP calls, the bandwidth numbers seen on the Call settings page get automatically tripled, so you do not need to manually set them to 6Mbps for example. However, we would normally recommend (3x) 4Mbps for most CTS calls.

Call Configuration
Call settings
SIP media encryptionallowed
SIP call participant labelsenabled
Audio packet size preferred20
SIP settings
TIP (Telepresence Interoperability Protocol) callsenabled
Presentation video channel operationsallowed
BFCP mode for presentation videoserverOnly
Resource priority1
UDP signaling for SIPsingleAddress
Lync presence supportenabled
Lync packet pacing modedefault
Bandwidth settings (SIP)
Rx bandwidth2000000
Tx bandwidth2000000
Bandwidth settings (CMA)
Rx bandwidth2000000
Tx bandwidth2000000
Bandwidth settings (Server reflexive)
Rx bandwidth2000000
Tx bandwidth2000000
Bandwidth settings (Relay)
Rx bandwidth2000000
Tx bandwidth2000000
Bandwidth settings (VPN)
Rx bandwidth2000000
Tx bandwidth2000000
Bandwidth settings (Lync content)
LAN bandwidth limit8000000
WAN bandwidth limit2000000

9.4 Incoming Calls

When an incoming SIP call is routed to the Meeting Server, the Call Bridge first looks through the configured Inbound Dial Plan rules and then at the Call Forwarding rules.

This Incoming Calls chapter contains:

9.4.1 Incoming Dial Plan Rules

When an incoming SIP call is routed to the Meeting Server, the Call Bridge looks through the configured Inbound Dial Plan rules first and tries to match the "domain" part of the destination URI "<user>@<domain>" against those rules.

The following Incoming Dial Plan rules are configured:

Incoming Dialplan Rules
Resolve To Userstrue
Resolve Toco Spacestrue
Resolve To Ivrstrue
Resolve To Lync Conferencesfalse
Resolve To Lync Simplejoinfalse

9.4.2 Call Forwarding

If the domain part of the destination URI of an incoming SIP call fails to match any of the Incoming Dial Plan rules, the call will be handled according to the rules in the Call Forwarding Dial Plan rules. The rules decide whether to reject the call outright or to forward the call in bridge mode.

The following Call Forwarding rules are configured:

Incoming Dial Transforms
Match Patternlab.test
Caller Id Moderegenerate
Uri Parametersdiscard

9.5 Outbound Calls

When an outgoing SIP call is routed out of the Meeting Server, the Call Bridge looks first through the configured outbound dial plan rules and then at the dial transforms.

This Outbound Calls chapter contains:

9.5.1 Outbound Dial Plan Rules

The configuration of which trunks or proxies to use for outbound calls is based on the domain of the (SIP) destination being called, which is specified in the outgoing dial plan.

All rules added via the Web Admin Interface are global and applied to every Call Bridge in the cluster. You must use the API to specify the call routing for outbound SIP/Lync calls using a specific Call Bridge or Call Bridge group.

The following Outbound Dial Plan Rules are configured:

Outbound Dialplan Rules
Local Contact Domain
Local From Domain
Trunk Typesip
Sip Control Encryptionauto
Sip ProxySIPProxy01
Failure Actionstop
Call Routingdefault

9.5.2 Dial Transforms

When dial transforms are applied to all outbound calls, the Outbound Dial Plan Rules are applied to the transformed number.

You can use the Web Admin Interface Configuration > Outbound Calls page to control how dialed numbers are transformed. However, you need to use the API for Dial Transforms if you use Call Bridge clustering, because the shared coSpace database is a single configuration location for all Call Bridges.

There are three stages to the transform:

The following Dial Transforms are configured:

Outbound Dial Transforms

9.6 IVR

Interactive Voice Response (IVR) is used to manually route to pre-configured calls. Incoming calls can be routed to the IVR where callers are greeted by a prerecorded voice message inviting them to enter the ID number of the call or space that they want to join. Video participants will see a welcome splash screen. After entering the ID, users are routed to the appropriate call or space, or prompted to enter a PIN if the call or space has one.

The following Interactive Voice Responses (IVRs) are configured:

Ivr Branding Profile68854d72-a080-42f7-85df-6fd2665d335e
Resolve Co Space Call Idsfalse
Resolve Lync Conference Idstrue
Tenant Groupf0fdcf04-1ac1-483f-a4c5-13cd8f699ff7

10 Command Line Output

This section contains status and configuration objects obtained via the command line.

10.1 Server

This section contains status and configuration objects obtained via the command line.

10.1.1 Hostname of CMS


10.1.2 IPv4 Address Port A

ipv4 a
IPv4 configuration:
default true
dhcp false
enabled true
macaddress 00:0C:29:24:3B:5A
prefixlen 24
IPv4 observed values
source destination gateway global false false false false true

10.1.3 IPv6 Address Port A

ipv6 a
No configuration data for interface a
IPv6 observed values
Addresses :
Routes :
source destination gateway

10.1.4 IPv4 Address Port B

ipv4 b
No configuration data for interface b
No observed values for interface b

10.1.5 IPv6 Address Port B

ipv6 b
No configuration data for interface b
No observed values for interface b

10.1.6 ntp server list

ntp server list
No NTP servers defined

10.1.7 Time Zone Configuration


10.1.8 used DNS server to resolve DNS

DNS Configuration
"status": "running"

10.1.9 User List

user list
admin admin 2020-Oct-23 yes

10.1.10 Syslog Configuration

Remote server not enabled

10.1.11 WebAdmin Configuration

Enabled : true
TLS listening interface : a
TLS listening port : 443
Key file : .key
Certificate file : .crt
HTTP redirect : Disabled
STATUS : running

10.1.12 Call Bridge Configuration

Server not configured

10.1.13 Web Bridge Configuration

No config

10.1.14 XMPP Configuration

Enabled : false
Clustered : false
Domain : none
Listening interfaces : whitelist is empty
Key file : none
Certificate file : none
Max sessions per user : unlimited
STATUS : XMPP server not enabled

10.1.15 XMPP Call Bridge Configuration

xmpp callbridge list
XMPP must be enabled before configuration

Table of Contents