cisco meeting server, quick reference guide to using ......cisco meeting server, quick reference...

CiscoMeeting ServerQuick Reference GuideUsing ActiveControl in Meeting Server conferences

May 15, 2019

Cisco Systems, Inc. www.cisco.com

http://www.cisco.com/

Quick Reference Guide : Active Control for Cisco Meeting Server 2

Contents

1 Introduction 11.1 About theActiveControl Feature 1

2 Supported Endpoints 32.1 Cisco Endpoints 3

2.1.1 List of features supported with software version CE9.6.2 32.2 Cisco Jabber 42.3 Features supported with Jabber 12.5 5

3 Call Control and Trunks 63.1 Cisco Unified CommunicationsManager 6

3.1.1 Enabling or verifying theSIP Profile iXmedia setting 63.1.2 Encryption Considerations 73.1.3 MRAConsiderations 7

3.2 Cisco Expressway and Cisco TelePresenceVideo Communication Server 73.2.1 Verifying the iX Filter setting for Expressway 83.2.2 Encryption Considerations 9

3.3 Cisco Meeting Server Configuration 93.3.1 ActiveControl Features as of Cisco Meeting Server 2.5 9

3.4 Cisco Meeting Server Profiles 103.5 Other Relevant Dependencies 11

3.5.1 Recording/Streaming 113.5.2 Add Participant 113.5.3 Encrypted iX 11

4 ActiveControl FeatureMatrix 12

5 Cisco Meeting App controls 145.1 Comparison of Meeting controls 16

6 Example: EnableActiveControl Permissions inMeeting Server 18

7 ActiveControl Troubleshooting 207.1 General ActiveControl limitations: 207.2 Verifying ActiveControl negotiation inMeeting Server 20

7.2.1 Meeting Encryption Status 207.3 Disabling iX inMeeting Server 20


7.4 iX troubleshooting 21

Cisco Legal Information 22

Cisco Trademark 24


1 IntroductionCiscoMeeting Server offersmeeting participants the ability to control their meetingexperience directly from their conferencing endpoint through a feature calledActiveControl.

ActiveControl enables run-timemeeting features for users, such as, meeting rosters(participant list), muting participants, dropping participants, changing video layout andmore, directly from their endpoint.

To useActiveControl requires the following in your deployment:

l The endpoint supports ActiveControl

l The call path between the endpoint and Meeting Server supports iXmedia end to end

l Appropriate permissions to be enabled inMeeting Server

This guide covers the configuration and dependencies for ActiveControl with CiscoMeeting Server.

In addition toActiveControl, theCiscoMeeting App has a set ofmeeting and spacecontrols that are similar, but separate from theActiveControl functionality inMeetingServer. Meeting App’s functionality is described in the section, CiscoMeeting Appcontrols of this guide.

1.1 About the ActiveControl FeatureActiveControl is a set of features negotiated between theCall Bridge and Ciscoendpoints to enable users to control their meeting experiencewithout the need forexternal applications or operators. ActiveControl utilizes the iXmedia protocol in Ciscodevices and is negotiated as part of SIPmessaging of the call.

ActiveControl was originally launched for theCiscoTelePresenceServer but has sincebeen reworked for newer platforms such asCiscoMeeting Server (Meeting Server) andWebexMeetings. The specific functionality and configuration depend on themeetingservice in use. This guidewill focus only on theActiveControl implementation forMeeting Server. For information on using ActiveControl withWebexMeetings, refer tothis article.

As of CiscoMeeting Server version 2.5, themain features enabled byActiveControlwithMeeting Server are as follows:

1 Introduction

https://help.webex.com/en-us/qbe7udb/Improve-the-Cloud-and-Premises-Meeting-Experience-with-ActiveControl


l Viewing a list of all participants (known as roster list or participant list) connected to themeeting

l Muting or unmuting other participants

l Adding or removing another participant from themeeting

l Starting or Stopping Recording of a meeting

l Making a participant important

l Indicator for the participant who is the active speaker in themeeting

l Indicator for the participant who is currently sharing content or presentation in themeeting

l Locking or unlocking of themeeting

Note: The actual features available in your deployment can vary based on endpoint typeand software versions in use.

Note: Participant list is also known as the roster list. It shows the names of all the peoplein the call.

1 Introduction


2 Supported EndpointsActiveControl for CiscoMeeting Server is supported with the following endpoints:

l Cisco DX-Series, SX-Series, Room Kit, Room Kit Pro and all endpoints based on thesecodecs running softwareCE8.3 or later.

l Cisco Jabber release 12.5 and later.

CiscoMeeting App has a set of in-meeting controls which are different toActiveControl. For more information, seeCiscoMeeting App controls.

The following section details the feature support and requirements for the differentendpoints.

2.1 Cisco EndpointsThis section applies to all Cisco Endpoints running CE software version 9.6.2, includingtheDX-Series, SX-Series, Room Kit, Room Kit Pro and all endpoints based on thesecodecs using the Touch10 controller. By default, ActiveControl is enabled in theseendpoints.

To configure this setting from your endpoint, openConfiguration > Conference >ActiveControl Mode.

ActiveControl features are accessed via the Touch10 controller or DX Touchscreeninterface.

Note: The features supported with different versions of endpoint softwaremay varyslightly, Cisco recommends using the latest version of endpoint software for the bestexperience.

2.1.1 List of features supported with software version CE9.6.2

Feature Support Notes

Meeting Roster (Participant list) Yes

Mute Remote Party Audio Yes DTMF option available

Unmute Remote Party Audio Yes DTMF option available

Video Layout Control Yes DTMF option available

2 Supported Endpoints


Add Participant No Available as an exper-imental feature

Drop Participant Yes

Record Meeting Controls Yes DTMF option available

StreamMeeting Controls No DTMF option available

Record/Stream Indicator Yes Icon is displayed onscreen.

Lock/UnLock Meeting No DTMF option available

Set/Unset Importance No

Roster Show Speaker Indicator (Active speaker indic-ator)

Yes

Roster Show Content Contributor (Indicator to showwho is sharing content)

Yes

Participant Count Yes

Local Mute by ActiveControl Yes Server and Local Muteare coupled and followeach other

Local UnMute by ActiveControl No An on screen notificationdisplays when user is nolonger remotely muted.

Encrypted iX media support Yes Requires a TLS securedregistration and call pathend to end

Message Text Yes On screen messagenotifications are shown

Note that availability of a particular featuremay still be limited by theMeeting Server’sconfiguration for a participant. See theCiscoMeeting Server Configuration for moredetails.

2.2 Cisco JabberSupport for ActiveControl in Jabber was introduced in Jabber version 12.5 on allsupported platforms. Jabber requires CiscoUnified CommunicationsManager version10.5 or later for ActiveControl support.

Jabber does not require any configuration on the client-side to enableActiveControl,but iXmedia must be enabled in theSIP profile assigned to the user’s device in CiscoUnified CommunicationsManager.



2.3 Features supported with Jabber 12.5



Mute/Unmute Remote Party Audio Yes DTMF option available


Add Participant Yes



StreamMeeting Controls No DTMF option available

Record/Stream Indicator Yes

Lock/UnLock Meeting Yes DTMF option available

Set/Unset Importance No


Yes


Yes


Local Mute by ActiveControl Yes Server and Local Muteare coupled and followeach other

Local UnMute by ActiveControl Yes Server and Local Muteare coupled and followeach other

Encrypted iX media support Yes

Message Text No Meeting Server embedsas part of video stream

Table 1: List of features supported with Jabber 12.5:

Note that availability of a particular featuremay still be limited by theMeeting Server’sconfiguration for a participant. See theCiscoMeeting Server Configuration for moredetails.



3 Call Control and TrunksTouseActiveControl, the full call path between theMeeting Server and the endpointmust support iXmedia in theSIPmessages. Any proxy, firewall, or back-to-back useragent (B2BUA) in the path that blocks or interfereswith the iXmessaging will causeActiveControl to not negotiate.

When enabling ActiveControl in your deployment, verify that the iX protocol issupported on trunks between theMeeting Server and endpoints.

The following sections detail the steps to enableActiveControl for Cisco Expressway,CiscoVCSand CiscoUnified CommunicationsManager. Please review each section asappropriate for your deployment.

3.1 Cisco Unified CommunicationsManagerActiveControl is compatiblewith CiscoUnified CommunicationsManager (UnifiedCM) versions 9.1.2 and later. iX protocol should be filtered or disabled on any trunksrouting to instances running versions older than the supported versions.

The iX protocol may be disabled by default in Unified CM depending on theSIP profilesand Unified CM versions in use. Newer Unified CM versions have the iX protocolenabled by default in SIP profiles labeled for TelePresence use. Common profiles usedfor Jabber may have the setting disabled by default. iXmedia must be enabled in eachof theSIP profiles used by your devices and all trunks that Telepresence calls willtraverse.

Verify all SIP Profiles used by TelePresence Endpoints, Jabber Devices, and SIP trunks.

3.1.1 Enabling or verifying theSIP Profile iXmedia setting

Toenable the iXmedia setting, follow these steps:

1. In theCisco Unified CommunicationsManager Administrationweb interface, ChooseDevice > DeviceSettings > SIP Profile.The Find and List SIP Profileswindow displays.

2. Locate the existing SIP profile in use for the trunk or device in question, enter the searchcriteria and click Find.

3. From the results, click the nameof theSIP profile that youwant to edit. TheSIP ProfileConfigurationwindow displays.

3 Call Control and Trunks


4. Locate theAllow iX ApplicationMedia setting under SDP Information and ensure thecheckbox ismarked/enabled.

5. Click ApplyConfig to save your changes.

Restart any trunks or devices as necessary if changes toSIP profiles have beenmade

To filter or disable iXmedia on a trunk, edit the SIP Profile associated with the trunk andensure theAllow iXApplicationMedia setting is unchecked.

3.1.2 Encryption Considerations

Endpointsmust use a secure SIP security profile to negotiate encrypted iX for calls. Thecall pathmust use TLSend-to-end for encrypted iX to negotiate. When not available,non-encrypted iXmedia can be negotiated.

3.1.3 MRAConsiderations

Endpoints connected via Mobile RemoteAccess (MRA)will not support iXmedia andActiveControl unless theUnified CM is inMixed Mode security, and Unified CM uses aTLSconnection to Expressway.

This limitationwill be addressed in future releases of CiscoUnified CommunicationsManager and CiscoExpressway.

3.2 Cisco Expressway and Cisco TelePresence Video CommunicationServerActiveControl is compatiblewith Cisco Expressway (Expressway) and CiscoTelePresenceVideoCommunication Server (CiscoVCS), version X7.2.3 and later.Support for iX is the sameacross both CiscoVCSand CiscoExpressway productvariations. For simplicity, the term Expressway refers to both Cisco Expressway andCiscoVCS in this document. iX protocol should be filtered/disabled on any trunksrouting to instances running releases older than the supported versions.



In CiscoTelePresenceVideoCommunication Server, the iX protocol is allowed to passthrough neighbor zones by default, unless it has been explicitly configured to be filteredwith theSIP UDP/IX filter setting for the zone.

3.2.1 Verifying the iX Filter setting for Expressway

Toconfigure theCiscoVCS to filter out the iX application line for a neighbor zone thatdoes not support the protocol, the zonemust be configured with a custom zoneprofilethat has theSIP UDP/IX filter mode advanced configuration option set toOn.

To update advanced zone profile option settings:

1. In the Expresswayweb interface, Navigate to Configuration > Zones > Zones.

2. Click on the nameof the zone youwant to view or edit.

3. Under theAdvanced panel, if ZoneProfile is set to Default or Cisco UnifiedCommunicationsManager, the SIP UDP/IX filter mode is assumed off and is not displayed.

4. To enable the filter, change theZoneProfile to Custom to view the advanced settings.

5. SIP UDP/IX filter mode controls filtering of iXmedia for this zone. Ensure it is set to Off toallow ActiveControl. Set to On if filtering iX to an incompatible neighbor.

If you have changed the profile to custom and are saving changes, review the otherAdvanced Settings for applicability to the zone being edited.

6. Click Save to save the changes.



3.2.2 Encryption Considerations

Endpointsmust register with TLS to negotiate encrypted iX for calls. The call pathmustuse TLSend-to-end for encrypted iX. When not available, non-encrypted iXmedia canbe negotiated.

3.3 Cisco Meeting Server ConfigurationActiveControl is supported in CiscoMeeting Server version 2.1 and later, and isenabled by default. While ActiveControl and negotiation is automatic; features availableon an endpoint are still controlled by settings configured inMeeting Server's profiles.The profiles onMeeting Server must be configured before using ActiveControl features.

3.3.1 ActiveControl Features as of CiscoMeeting Server 2.5



Mute/Unmute Remote Party Audio Yes DTMF option available


Add Participant Yes



StreamMeeting Controls Yes DTMF option available

Record/Stream Indicator Yes When supported, shownby endpoint, otherwise,shown in video stream byCisco Meeting Server.

Lock/UnLock Meeting Yes DTMF option available

Set/Unset Importance Yes


Yes


Yes


Local Mute by ActiveControl Yes

Table 2: List of ActiveControl features for Cisco Meeting Server 2.5



Local UnMute by ActiveControl Yes Endpoint controlled fea-ture

Encrypted iX media support Yes

Message Text Yes When supported, shownby endpoint, otherwise,shown in video stream byCisco Meeting Server.

3.4 Cisco Meeting Server ProfilesBy default, the participant permissions are generally disabled inMeeting Server. Beforean ActiveControl feature is available to participants, the administratorsmust enable thefeature through theAPI of theMeeting Server.

For SIP connected endpoints, permissions are controlled by the callLegProfiles settingin theAPI. A callLegProfile can be applied at the system-wide level, tenant level, spacelevel, member or accessMethod level. The recommended best practice is to set theparticipant permissions youwant as the baseline for your deployment at the systemlevel. For more details on theMeeting Server API and how the object hierarchy is used,refer to theCiscoMeeting Server API reference guide.

The callLegProfile settings relevant to enable all ActiveControl features for SIPconnected endpoints are listed below. To use a feature, the setting must be enabled fora participant. Alternatively, the settings can be applied to a system level callLegProfileso the settings apply by default to all participants.

callLegProfile Setting Valueto set

Notes

changeLayoutAllowed true Grants permission for changing layout for the participant themselves

disconnectOthersAllowed true Grants permission to Drop Participant from roster list (participant list)

addParticipantAllowed true Grants permission to Add Participant for ongoing call

muteOthersAllowed true Grants permission for Mute/Unmute Audio in roster list (participant list)

muteSelfAllowed true Grants permission for Server side mute for themselves

callLockAllowed true Grants permission to lock/unlock the ongoing call

setImportanceAllowed true Grants permission to set/unset Importance for a participant in the roster list(participant list)

recordingControlAllowed true Grants permission for recording controls if recording is available for call

Table 3: ActiveControl callLegProfile settings for SIP Participants


https://www.cisco.com/c/en/us/support/conferencing/meeting-server/products-programming-reference-guides-list.html


streamingControlAllowed True Grants permission for streaming controls if streaming is available for call

3.5 Other Relevant Dependencies

3.5.1 Recording/Streaming

For recording or streaming controls to be available for participants, the followingprerequisitesmust bemet:

l recording or streaming must be configured for theCall Bridge

l the spacemust have an associated callProfilewith the recordingMode set to manual.

3.5.2 Add Participant

ActiveControl can enable a participant to dial out to a new participant for the ongoingcall, but for that call to be successful, theOutbound Call table inMeeting Server mustbe configured correctly with call control that can successfully connect to the requestedURI.

3.5.3 Encrypted iX

Tonegotiate encrypted iXmedia, theMeeting Server must haveSIPMedia encryptionenabled for the participant. When not available, Meeting Server will attempt tonegotiate non-encrypted iXmedia whichmay impact the security status reported for aparticipant or conference.

SIPMedia Encryption can be disabled in theCall Bridge settings from theWeb Admininterface (FromConfiguration > Call Settings), or from the callLeg settings applied to aparticipant. Ensure that theSIPMedia Encryption is not disabled for participants ifencrypted iX is desired.



4 ActiveControl Feature MatrixTable 4 provides a summary of ActiveControl features per device type. For more detailson a device type, refer to the corresponding section in this guide.

DX,SX,RK End-pointsCE9.6.2

CiscoJabber12.5

Meeting Server setting for ActiveControl Notes

Meeting Roster(Participant list)

Yes Yes N/A - Automatic

Mute/UnmuteRemote PartyAudio

Yes Yes muteOthersAllowed DTMFoption avail-able

Video Layout Con-trol

Yes Yes changeLayoutAllowed DTMFoption avail-able

Add Participant No Yes addParticipantAllowed

Drop Participant Yes Yes disconnectOthersAllowed

Record MeetingControls

Yes Yes recordingControlAllowed DTMFoption avail-able

StreamMeetingControls

No No streamingControlAllowed DTMFoption avail-able

Record/StreamIndicator


Lock/UnLock Meet-ing

No Yes callLockAllowed DTMFoption avail-able

Set/Unset Import-ance

No No setImportance

Roster ShowSpeaker Indicator


Roster Show Con-tent Contributor


Participant Count Yes Yes N/A - Automatic

Table 4: ActiveControl feature matrix

4 ActiveControl Feature Matrix


Local Mute by Act-iveControl

Yes Yes muteSelfAllowed

Local UnMute byActiveControl

No Yes N/A - Automatic

Encrypted iX mediasupport


Message Text Yes No N/A - Automatic

4 ActiveControl Feature Matrix


5 Cisco Meeting App controlsCiscoMeeting App is available as a desktop client (macOSandWindows), iOSclient,and also as a browser-based client that leveragesWebRTC for audio and video.Meeting App offers in-meeting controls for participant tomanage their meetings. A fewof themeeting control options are similar to the features provided byActiveControl forSIP. The key differences are as follows:

l Meeting App's features and controls are not managed in the sameway asActiveControlfor SIP participants.

l Meeting App does not use iXmedia for itsmeeting controls.

Thepermissions that govern themeeting features inMeeting App are a combination ofthe following:

l userProfile settings – The profile assigned to a user which controlsmore general userbehaviors.

l spacemember permissions – The permissions assigned to the user within a particularspace.

l callLegProfiles –Permissions applied to the participant as a combination of member,space, tenant, or system profiles.

Feature MeetingServer'sActiveControl setting

MeetingAppequivalent?

Setting to controlMeetingAppbehavior

MeetingAppGuestuser exper-ience

Meeting roster(Participantlist)

N/A - Automatic Yes Automatic

Mute/UnmuteRemote PartyAudio

muteOthersAllowed Yes muteOthersAllowed

Mute/UnmuteRemote PartyVideo

Not Available Yes videoMuteOthersAllowed

Video LayoutControl

changeLayoutAllowed Yes Layout setting is local to Meeting App

Add Par-ticipant

addParticipantAllowed Yes Always available to space members Not avail-able toguestsusers

5 Cisco Meeting App controls


Drop Par-ticipant

disconnectOthersAllowed Yes Always available to space members Not avail-able toguests

Record Meet-ing Controls

recordingControlAllowed Yes recordingControlAllowed

StreamMeet-ing Controls

streamingControlAllowed Yes streamingControlAllowed

Record Meet-ing Indicator

N/A - Automatic Yes N/A - Automatic

Lock/UnLockMeeting

callLockAllowed Yes callLockAllowed

Set/UnsetImportance

setImportance Yes setImportance

Active speaker(Roster ShowSpeaker) Indic-ator


Roster ShowContent Con-tributor


ParticipantCount


Local Mute byActiveControl

muteSelfAllowed Yes N/A - Automatic

Local UnMuteby Act-iveControl

N/A - Automatic No N/A – Local unmute controlled by clientonly

Encrypted iXmedia support

N/A - Automatic N/A N/A

Message Text N/A - Automatic No N/A – Meeting App does not supportMessage Text feature

Peer/Slave toExternalDevice

N/A – Not Supported inActiveControl

Yes userProfile settings –canUseExternalDevices

and optional canMakePhoneCalls

No set-tings tocontrol –slave tovideoalways on

Toggle GuestAccess to aspace

N/A – Not Supported inActiveControl

Yes userProfile setting– can-AddRemoveMember and space memberpermission can-ChangeNonMemberAccessAllowed

Not avail-able toguests


5.1 Comparison of Meeting controlsThe following table compares theActiveControl options and settings to themeeting control features available inMeetingApp. Additionally, the table also includes a column for Meeting Server's callLegProfile settings relevant to a meetingfeature, and a column to note any differences for a Meeting App user joining as a guest user (not authenticated or joiningspaces they are notmembers of).

Feature MeetingServer'sActiveControl setting

MeetingAppequivalent?

Setting to controlMeetingAppbehavior

MeetingAppGuestuser exper-ience

Meeting roster (Participant list) N/A - Automatic Yes Automatic

Mute/Unmute Remote PartyAudio

muteOthersAllowed Yes muteOthersAllowed

Mute/Unmute Remote PartyVideo

Not Available Yes videoMuteOthersAllowed

Video Layout Control changeLayoutAllowed Yes Layout setting is local to Meeting App

Add Participant addParticipantAllowed Yes Always available to space members Not avail-able toguestsusers

Drop Participant disconnectOthersAllowed Yes Always available to space members Not avail-able toguests

Record Meeting Controls recordingControlAllowed Yes recordingControlAllowed

StreamMeeting Controls streamingControlAllowed Yes streamingControlAllowed

Record Meeting Indicator N/A - Automatic Yes N/A - Automatic

Table 5: Meeting controls comparison

Active Control for Cisco Meeting Server Page 16


Lock/UnLock Meeting callLockAllowed Yes callLockAllowed

Set/Unset Importance setImportance Yes setImportance

Active speaker (Roster ShowSpeaker) Indicator


Roster Show Content Con-tributor


Participant Count N/A - Automatic Yes N/A - Automatic

Local Mute by ActiveControl muteSelfAllowed Yes N/A - Automatic

Local UnMute by ActiveControl N/A - Automatic No N/A – Local unmute controlled by client only

Encrypted iX media support N/A - Automatic N/A N/A

Message Text N/A - Automatic No N/A – Meeting App does not support Message Text fea-ture

Peer/Slave to External Device N/A – Not Supported in ActiveControl Yes userProfile settings – canUseExternalDevices

and optional canMakePhoneCalls

No set-tings tocontrol –slave tovideoalways on

Toggle Guest Access to aspace

N/A – Not Supported in ActiveControl Yes userProfile setting– canAddRemoveMember and spacemember permission can-ChangeNonMemberAccessAllowed

Not avail-able toguests



6 Example: Enable ActiveControl Permissions in Meeting ServerThe following example provides a step-by-step example of how to configure a system level callLegProfile inMeetingServer which is used to enable all ActiveControl features for participants. This example uses the command line tool curlas installed onmacOS to illustrate the steps, alternatively, you can use any RESTAPI tool.

Note: Make sure you edit the items highlighted in blue to the values thatmatch your deployment.

1. Check if there are any existing callLegProfiles applied at the system level by doing a GET to /api/v1/system/profileson your Meeting Server webadmin instance

curl -k -u admin https://10.10.20.10:445/api/v1/system/profiles | xmllint --format -

Example output:<?xml version="1.0"?><profiles><callProfile>9afadfa8-7cbe-4d46-949f-6ccc5303ae4f</callProfile><dtmfProfile>d37d4dcd-083e-4e81-9ef4-2d0d219b4d19</dtmfProfile><compatibilityProfile>7ec2c420-8149-480d-9add-fcd47c422e09</compatibilityProfile></profiles>

The output of this example shows nocallLegProfile listed, and hence a new callLegProfile can be created andapplied.

2. Create a new callLegProfilewith required settings using POST to /api/v1/callLegProfiles.The example adds a nameparameter for easier identification later and includes all the permissions outlined in theCiscoMeeting Server Configuration section above.curl -v -k -u admin -X POST https://10.10.20.10:445/api/v1/callLegProfiles -d'name=ActiveControls&changeLayoutAllowed=true&muteOthersAllowed=true&muteSelfAllowed=true&c


6 Example: Enable ActiveControl Permissions in Meeting Server

allLockAllowed=true&recordingControlAllowed=true&disconnectOthersAllowed=true&addParticipantAllowed=true&setImportanceAllowed=true'The-v option is used to see the Location header in the output from the command to easily identify the ID of the new profilecreated.Example snippet from output:< Location: /api/v1/callLegProfiles/b42a2db3-0437-4958-b1c9-02329ded4bba

3. Apply the newly created callLegProfile as a system profile by doing a PUT to /api/v1/system/profiles and using the ID of thenew callLegProfile.curl -k -u admin -X PUT https://10.10.20.10:445/api/v1/system/profiles -d'callLegProfile=b42a2db3-0437-4958-b1c9-02329ded4bba'

4. Confirm the result by checking system profiles again and verifying that the new callLegProfile is listed with the correct ID.curl -k -u admin https://10.10.20.10:445/api/v1/system/profiles | xmllint --format -

The output shows that the callLegProfile is assigned with the new ID.<?xml version="1.0"?><profiles><callLegProfile>b42a2db3-0437-4958-b1c9-02329ded4bba</callLegProfile><callProfile>9afadfa8-7cbe-4d46-949f-6ccc5303ae4f</callProfile><dtmfProfile>d37d4dcd-083e-4e81-9ef4-2d0d219b4d19</dtmfProfile><compatibilityProfile>7ec2c420-8149-480d- 9addd47c422e09</compatibilityProfile></profiles>


6 Example: Enable ActiveControl Permissions in Meeting Server


7 ActiveControl Troubleshooting

7.1 General ActiveControl limitations:Listed below are someActiveControl limitations:

l ActiveControl is a SIP-only protocol and is not supported for inter working scenarios.

l Older SIP devicesmay not handle the iX SIPmessages gracefully and may cause callfailures if seen. Trunks to the following should have iX disabled to avoid interoperabilityissues:

l Trunks to Unified CM servers running releases older than version 9.1.2

l Trunks to VCS/Expressway servers running releases older than X7.2.3

l Trunks to any external network or 3rd party call control devicewhere call failureshave been traced to iX protocol handling

7.2 Verifying ActiveControl negotiation inMeeting ServerIf negotiated, ActiveControl will be shown in the following places:

l The call details of Status/Calls for the participant

l The callLeg API object for the participant

7.2.1 Meeting Encryption Status

When a participant negotiates ActiveControl and if iX is not encrypted, Meeting Serverwill report the participant as unencrypted. This non-encrypted user can lower theencryption status of the conference as seen by other endpoints.

7.3 Disabling iX inMeeting ServerActiveControl uses theUDT transport protocol for certain features, for example sendingroster lists (participant lists) to endpoints, allowing users to disconnect otherparticipantswhile in a call, and inter deployment roster lists (participation lists). UDT isenabled by default. You can disableUDT for diagnostic purposes, for example if yourcall control does not useUDT, and you believe this is the reason the call control does notreceive calls from theMeeting Server.

If necessary, disabling ActiveControl inMeeting Server can be doneby disabling UDT inMeeting Server via theAPI. TodisableUDT, follow these steps:



1. Create a compatibility profilewith the parameter sipUdt set to false using the POSTmethod (or modify an existing with PUT method) to/api/v1/compatibilityProfiles setting sipUdt=false.

2. Apply the newly created compatibility profile by setting the newly created profile at thesystem level. UsePUT method with compatibilityProfile=<compatibilityprofile id> to /api/v1/system/profiles.

7.4 iX troubleshooting

Table 6: Call handling summary for calls that contain an iX header

Scenario Outcome

Unified CM 8.x or earlier Calls fail

Unified CM 9.x earlier than 9.1(2) Calls handled normally but no ActiveControl

Unified CM 9.1(2) Calls handled normally plus ActiveControl

Endpoint - no support for iX and no SDP implementation Endpoint may reboot or calls may fail



Cisco Legal InformationTHESPECIFICATIONSAND INFORMATIONREGARDING THEPRODUCTS INTHISMANUAL ARESUBJECTTOCHANGEWITHOUTNOTICE. ALL STATEMENTS,INFORMATION, ANDRECOMMENDATIONS INTHISMANUAL AREBELIEVEDTOBEACCURATEBUTAREPRESENTEDWITHOUTWARRANTYOFANYKIND, EXPRESSORIMPLIED. USERSMUSTTAKE FULL RESPONSIBILITY FORTHEIRAPPLICATIONOFANYPRODUCTS.

THESOFTWARE LICENSEANDLIMITEDWARRANTY FORTHEACCOMPANYINGPRODUCTARESETFORTH INTHE INFORMATIONPACKETTHATSHIPPEDWITHTHEPRODUCTANDARE INCORPORATEDHEREINBY THISREFERENCE. IF YOUAREUNABLE TOLOCATE THESOFTWARE LICENSEORLIMITEDWARRANTY, CONTACTYOURCISCOREPRESENTATIVE FORACOPY.

TheCisco implementation of TCP header compression is an adaptation of a programdeveloped by theUniversity of California, Berkeley (UCB) as part of UCB’s publicdomain version of theUNIX operating system. All rights reserved. Copyright© 1981,Regents of theUniversity of California.

NOTWITHSTANDING ANYOTHERWARRANTYHEREIN, ALL DOCUMENTFILESANDSOFTWAREOF THESESUPPLIERSAREPROVIDED “AS IS”WITHALL FAULTS. CISCOANDTHEABOVE-NAMEDSUPPLIERSDISCLAIM ALLWARRANTIES, EXPRESSEDORIMPLIED, INCLUDING,WITHOUTLIMITATION, THOSEOFMERCHANTABILITY, FITNESSFORAPARTICULARPURPOSEANDNONINFRINGEMENTORARISING FROMACOURSEOFDEALING, USAGE, ORTRADEPRACTICE.

INNOEVENTSHALL CISCOOR ITSSUPPLIERSBE LIABLE FORANY INDIRECT,SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,WITHOUTLIMITATION, LOSTPROFITSORLOSSORDAMAGETODATAARISINGOUTOF THEUSEOR INABILITY TOUSETHISMANUAL, EVEN IF CISCOOR ITSSUPPLIERSHAVEBEENADVISEDOF THEPOSSIBILITYOF SUCHDAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are notintended to be actual addresses and phone numbers. Any examples, commanddisplay output, network topology diagrams, and other figures included in the documentare shown for illustrative purposes only. Any use of actual IP addresses or phonenumbers in illustrative content is unintentional and coincidental.

All printed copies and duplicate soft copies of this document are considereduncontrolled. See the current online version for the latest version.

Cisco Legal Information


Cisco TrademarkCisco and theCisco logo are trademarks or registered trademarks of Cisco and/or itsaffiliates in theU.S. and other countries. To view a list of Cisco trademarks, go to thisURL: www.cisco.com/go/trademarks. Third-party trademarksmentioned are theproperty of their respective owners. The use of theword partner does not imply apartnership relationship betweenCisco and any other company. (1721R)

Cisco Trademark

http://www.cisco.com/go/trademarks

cisco meeting server, quick reference guide to using ......cisco meeting server, quick reference...

Documents