PDF(1.5 MB) View with Adobe Reader on a variety of devices
ePub(1.7 MB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(1.0 MB) View on Kindle device or Kindle app on multiple devices
Updated:May 31, 2021
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The information in this document is based on Cisco Meeting Server.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
This document is intended as guidance in case you already have a CMS 2.9.x (or earlier) deployment, regardless if single combined, or resilient, and when you plan to upgrade to CMS 3.0. The information in this document pertains to all models of CMS.
Note: X-series cannot be upgraded to CMS 3.0. You need to plan to replace your X-series servers as soon as possible.
Important information about upgrades
The only supported method for upgrading CMS is a stepped upgrade. At the time of writing this, CMS 3.5 has been released. If you are on CMS 2.9, you must upgrade in a stepped fashion (2.9 --> 3.0 --> 3.1 --> 3.2 --> 3.3 --> 3.4 --> 3.5 (Note upgrade process has changes as of CMS 3.5, so read the release notes carefully!!)
If you do not perform a stepped upgrade, and are experiencing unusual behavior, TAC could request you downgrade and start over.
Also, as of CMS 3.4, CMS MUST use Smart Licensing. You can not upgrade to CMS 3.4 or newer and still use traditional licenses. Do not upgrade to CMS 3.4 or newer unless you have set up Smart Licensing.
Summary of things to consider
Use these questions to navigate to the sections that pertain to your own situation. Each consideration refers to a hyperlink to more detailed description presented in this document.
Do you have enough Personal MultiParty (PMP) / Shared MultiParty (SMP) licenses on your servers before the upgrade?
In 3.0 the PMP licenses are allocated, even if the user is not signed in. For example, if you have imported 10000 users through LDAP, but you have only 100 PMP licenses, this puts you out of compliance as soon as you upgrade to 3.0. For this use case, make sure to certainly check for tenants who have userProfile set and/or system/profiles to see if a userProfile with hasLicense with a value of true is set.
How to check the userProfile on API and see if you have hasLicense=true set (meaning PMP licensed users), is covered up in more detail in this section.
Do you have PMP/SMP lienses in your current cms.lic file?
Due to a license behavior changes in 3.0 onwards, you must confirm if you have enough PMP/SMP licenses before performing the upgrade. This is described in more detail in this section.
Do you have Cisco Meeting Manager (CMM) deployed?
CMS 3.0 requires CMM 3.0 due to changes in how licenses are handled. It is recommended to deploy CMM 2.9 before you perform an upgrade of your environment to 3.0 as you can check your 90 day report for license consumption for the past 90 days. This is described in more detail in this section.
Do you have Smart Licensing?
CMS 3.0 requires CMM 3.0 due to changes in how licenses are handled. So if you are using Smart Licensing through CMM already, ensure you have PMP and SMP licenses associated to your cluster.
Webbridge (WebRTC and CMA client)
Do you use WebRTC in CMS 2.9?
Webbridge has changed in CMS 3.0 significantly. For guidance on the migration from webbridge2 to webbridge3 and the use of web app, the information is found in this section.
Do your users use the CMA thick client?
As these clients are XMPP based, these clients can not be used anymore after the upgrade as the XMPP server has been removed. If this applies for your use case, you can find more information in this section.
Do you use Chat in WebRTC?
The chat functionality is removed from web app in 3.0. In CMS 3.2, chat is re-introduced, but it is not persistent. You can find more information on this feature in this section.
Do your users perform Point to Point calls from WebRTC to devices?
In CMS 3.0, a web app user can not dial directly to another device anymore. Now you must join a meeting space, and have the permission to add participants to the meeting to perform on the same action. You can find more information on this part in this section.
Do your users create their own coSpaces from WebRTC?
In 3.0, in order for web app users to be able to create their own spaces from the client, a coSpaceTemplate needs to be created in API and assigned to the user. This can be manual or automatic during LDAP import. CanCreateCoSpaces is removed from UserProfile. You can find more information on this feature in this section.
Web GUI Changes
Do you have webBridge settings configured in the web admin GUI?
The webBridge settings are removed from the GUI in 3.0, so you must configure the webbridges in the API and note what your current settings are in the GUI so you can configure the webBridgeProfiles in the API accordingly. You can find more information on this change in this section.
Do you have External Settings configured in the web admin GUI?
The External Settings have been removed from the GUI in CMS 3.1. If you have either Webbridge URL or IVR configured in your CMS 3.0 or older web admin GUI (Configuration --> General --> External Settings), these have been removed from the web page and now need to be configured in the API. The previous settings prior to upgrading to 3.1 do NOT get added into API, and must be done manually. You can find more information on this change in this section.
Recorders / Streamers
Do you currently use any CMS recorder(s) and/or streamer(s)?
The CMS recorder and streamer component are now SIP based instead of XMPP based. Therefore as the XMPP is being removed, these need to be tweaked after the upgrade. You can find more information on this change in this section.
Cisco Expressway Considerations
What is your current Cisco Expressway version if you are using Expressway to proxy WebRTC?
CMS 3.0 requires Expressway 12.6 or newer. You can find more information on this WebRTC proxy feature in this section.
Do you currently have a CMS Edge in your environment?
CMS Edge is re-introduced on CMS 3.1 with higher scalability for external connections. You can find more information on this part in this section.
CMS (Acano) X-Series
Do you currently have x-series servers in your environment?
These server can not be upgraded to CMS 3.0 and you must be looking at replacing these soon (move to a virtual machine or CMS appliance before upgrading to 3.0). You can find the end of life notice about these servers in this link.
Do you currently use SIP Edge in your environment?
Sip Edge is fully deprecated as of CMS 3.0. You need to use Cisco Expressway to bring SIP calls into your CMS. Please contact your Cisco Account representative on how to get Expressways for your organization.
Licensing - Check licenses before upgrade
Out of compliance license status is the most impactful issue when you upgrade to 3.0 or higher from a 2.x version. This section describes how to determine the amount of PMP/SMP licenses you need for a smooth upgrade.
Before you upgrade your deployment to 3.0, deploy CMM 2.9 and check the 90 day report under Licenses tab to see if the license usage stayed under your current allocated license amount on the CMS nodes:
If you use Traditional licensing (cms.lic file is installed locally on your CMS nodes), check the CMS license file for the quantities of personal and shared licenses (100 / 100 as per the image here) on each of the CMS nodes (download through WinSCP from each callBridge node).
If you already use Smart Licensing, check how many PMP/SMP licenses are assigned in the Cisco Software Smart portal for the CMS servers.
Open the 90 day report (Zip file is named license-data.zip) and open the file named daily-peaks.csv.
On Excel, sort the PMP column by Z to A to get the higher values to the top and then perform the same for the SMP column. Are the values you see in this file lower than the licenses available in the CMS license file? If yes, then you are fine and fully in compliance. If not, then this create warnings and/or errors as indicated on Figure 6 on section 1.7.3 of the CMS deployment guide for which you can find more information as well on section 1.7.4.
As per the image as example, there were 2.1667 SMP licenses used and no PMP licenses as per the peak during the past 90 days. The cms.lic file indicated 100 units of each type of license so this setup is fully compliant. Therefore there are no issues with licensing when this setup upgrades to CMS 3.0. However there can still be an issue when on the setup 10,000 users through LDAP would have been imported. As then you only have 100 PMP licenses, but you allocate 10000 (with userProfile with hasLicense set to True) so in this case you are out of compliance as soon as you upgrade to 3.0. More on this in the next section.
Determine how many users are assigned a PMP license once you upgrade
All users who are imported and use a userProfile with hasLicense=true are automatically assigned a PMP license in CMS 3.0.
In the API, check how many userProfiles you have and check if any of them has "hasLicense=true" set. If they do, you need to check where those userProfiles are assigned.
The userProfiles can be assigned at any of these levels:
Check all 3 locations for assigned userProfiles that have hasLicense=true.
For each ldapSource that is using a tenant or a userProfile, users imported with that ldapSource are be assigned a PMP license when the hasLicense parameter is set to True. If there is a tenant, you need to click on the tenant ID to see if it has a userProfile assigned, and then check if that userProfile is configured with 'hasLicense=true'. If there is no tenant, but there is a userProfile set, click it to see if it has 'hasLicense=true'. If either way has 'hasLicense=true', you can verify how many users were imported by performing a GET for 'api/v1/users' and filtering for the domain used for the jidMapping on the ldapmapping associated to the ldapSource for example.
Note: This can be more complex in other situations in which case you need to check this with the ActiveDirectory mappings and filters you created.
Step 1. Find the mapping ID from the ldapSource.
Step 2. Look up ldapMappings to find jidMapping.
Step 3. Search in api/v1/users for the domain used in the jidMapping.
Step 4. Add up the users found from each ldapSource. This is how many LDAP imported users need PMP licenses.
If a userProfile is set at the system/profiles level, and that userProfile has "hasLicense=true" then any user imported into CMS is be assigned a PMP license when the server is upgraded. If you imported 10,000 users but you only have 100 PMPs, this results in you being out of compliance when you upgrade to CMS 3.0, and can cause a 30 second on screen message to appear and audio prompt at the start of calls.
If the userProfile at the system level indicates users are to get a PMP, go to api/v1/users to see how many users there are in total:
If you had previously imported all users from your ldap, but realize now that you only need a certain subset from from that list, create a better filter in your ldapSource so it imports just the users you want to be assigned PMP licenses. Revise your filter on ldapSource and then perform a new LDAP sync in api/v1/ldapsync. This results in only your desired users being imported, and all others from this previous import removed.
Note: If you do this correctly and the new import only removes unwanted users, remaining users coSpace CallIDs and secrets do not change, but if you do make a mistake, this can result in all callIds and secrets changing. Make a backup of your database nodes before attempting this if you are concerned about this!
Do you have enough SMP licenses?
When you were looking at your daily peaks from the CMM 90 Day Report, do you have enough SMP licenses already to cover what your peak was? SMP licenses are used when the owner of the meeting has not been assigned a PMP license (either as coSpace owner / ad-hoc meeting / TMS scheduled meeting). If you are intentionally using SMP and have enough to cover your peak times, then this is all OK. If you check the 90 day peak for SMP and it is unclear why these are consumed, here are some things to check.
1. Ad hoc calls (as escalated from CUCM) use an SMP license if the device used to merge is not associated to a user who has been assigned a PMP license in CMS through the userProfile. CUCM provides the GUID of the user escalating the meeting. If that GUID corresponds to a Meeting Server imported LDAP user with an assigned PMP license, the license of that user is be used.
2. If a coSpace owner has not been assigned a PMP license, calls to those particular coSpaces use a SMP license.
3. If the meeting was scheduled in TMS version 15.6 or newer, the meeting owner is sent to CMS and if that user was not assigned a PMP license, that meeting uses a SMP license.
As from CMS 3.0, CMM 3.0 is required for CMS to function properly. CMM is responsible for the licensing of CMS, so if you plan to upgrade CMS to 3.0, you must have a CMM server. It is recommended to deploy CMM 2.9 while you are on CMS 2.9 so you can check your license consumption before upgrading.
CMM checks all added callBridges for SMP and PMP licenses and the callBridge license. It uses the number that is the highest accross the various devices within the cluster.
For example, if CMS1 has 20 PMP and 10 SMP licenses, and CMS2 has 40 PMP and 5 SMP licenses in traditional licensing, the CMM reports that you have 40 PMP and 10 SMP licenses to use.
If you have more PMP licenses than imported users, you do not have any issues related to PMP (or SMP) licenses but if you check that 90 day peak and you find that you used more than available, you can still upgrade to CMS 3.0 and use the 90 day Trial License on CMM to sort things out with your licensing, or take action before the upgrade.
Configure Webbridge (WebRTC And CMA client)
CMS 3.0 removes the XMPP server component, and with that, removes webBridge and the ability to use the CMA thick client. WebBridge3 is what is used now to connect web app users (formerly referred to as WebRTC users) to meetings using the browser. When you upgrade to 3.0, you need to configure webbridge3.
Note: CMA thick client does not work after upgrading to CMS 3.0!
This video does walk you through the process on how to create the webbridge 3 certificates.
Prior to the upgrade to 3.0, customers must plan on how to configure Webbridge3. The most important steps are highlighted here.
1. You do need a key and cert chain for webbridge3. The old webbridge cert can be used if the cert contains all CMS server FQDNs or IP addresses as Subject Alternative Name (SAN)/ Common Name (CN) that are running webbridge3, and if either of the these are met:
a. Certificate has no Enhanced Key Usage (meaning it can be used either as Client or server).
b. Certificate has both Client and Server Authentication. HTTPs cert only really needs Server Authentication, while C2W certificate requires both server and client).
If you want to create a new certificate for the "webbridge3 https" cert, it is recommended to be publicly signed (to avoid certificate warnings on client when using web app). This same cert can be used for the "webbridge3 c2w cert", and the cert must have the FQDN of the webbrige servers in the SAN/CN.
CallBridges need to communicate with the new webbridge3 using a port that is configured in webbridge3 c2w listen command. This can be any available port, such as 449. Users need to be sure the callbridges can talk to webbridge3 on this port, and have any firewall changes made in advance, if necessary. It cannot be the same port used by "webbridge https" to listen on.
Before the CMS upgrade to 3.0, it is recommended to take a backup using 'backup snapshot <servername_date>', and then log into the webadmin page on your callbridge nodes to remove all XMPP Settings and Webbridge Settings. Then connect to the MMP on your servers, and perform these steps on all Core servers that have xmpp and webbridge over a SSH connection:
xmpp certs none
xmpp domain none
webbridge listen none
webbridge certs none
webbridge trust none
Once you upgrade to 3.0, begin by configuring webbridge3 on all servers that previously ran webbridge. You must do this because there are already DNS records out there that point to these servers, so in that way you ensure that if a user gets sent to a webbridge3, it is prepared to handle the request.
Webbridge3 Configuration (all over SSH connection)
Step 1. Configure webbridge3 http listening port.
Webbridge3 https listen a:443
Step 2. Configure certificates for webbridge3 for browser connections. This is the certificate sent to browsers and needs to be signed by a public Certificate Authority (CA) and containing the FQDN used in the browser for the browser to trust the connection.
Webbridge3 https certs wb3.key wb3trust.cer (This needs to be a trust chain: make a trust cert that has end entity on top, followed by Intermediate CAs in order, finishing with RootCA).
Step 3. Configure port to use to listen for callBridge to webbridge (c2w) connections. Since 443 is used for the webbridge3 https listen port, this config must be a different, available port like for example 449.
Webbridge3 c2w listen a:449
4. Configure certificates that webbridge sends to callbridge for the c2w trust
Webbridge3 c2w certs wb3.key wb3trust.cer
5. Configure the trust store WB3 uses to trust the callBridge certificate. This needs to be the same as the certificate used on the callbridge CA bundle (and must be a bundle of intermediate certificates on top, and Root CA at the end, followed by a single carriage return).
Webbridge3 c2w trust rootca.cer
6. Enable webbridge3
CallBridge config changes (all over SSH connection)
Step 1. Configure the callBridge trust with the CA cert/bundle that signed the webbridge3 c2w certificate.
Callbridge trust c2w rootca.cer
Step 2. Restart the callBridge to get the new trust to take effect. This drops all calls on this particular callBridge so use this with caution.
API configuration for callBridges to connect to webBridge3
1. Create a new webBridge object using POST in the API and give it a URL value using FQDN and port configured on webbridge c2w interface white list (step 3 in the webbridge3 config)
At this point, Webbridge3 works again, and you can join spaces as guest or if you have previously imported users, they must be able to sign in.
Web app user space creation permissions
Are your users used to being able to create their own spaces in WebRTC? As of CMS 3.0, web app users cannot create their own coSpaces unless they have a cospace template assigned to them allowing for this.
Even with a coSpaceTemplate assigned, this does not create a space that others can dial into (no URI, no Call ID or passcode), but if the coSpace has a callLegProfile with ‘addParticipantAllowed’, then they can dial out from the space.
In the API, create coSpaceTemplate(s) and then create an accessMethodTemplate(s) and assign the coSpaceTemplate to the ldapUserCoSpaceTemplateSources or you can manually assign a coSpaceTemplate to a user in api/v1/users.
Name: Any name you want to give the coSpaceTemplate.
Description: Brief Description if desired.
callProfile: White callProfile do you want any Spaces created with this template to use? If not provided, it uses what is set at the system/profile level.
calllegPrrofile: Which calllegProfile do you want any spaces created with this template to use? If not provided, it uses what is set at the system/profile level.
dialInSecurityProfile: Which dialInSecurityProfile do you want any spaces created with this template to use? If not provided, it uses what is set at the system/profile level.
AccessMethodTemplate (API config)
Name: Any name you want to give the coSpaceTemplate.
uriGenerator: The expression to be used to generate URI values for this access method template; the allowed set of characters are 'a' to 'z', 'A' to 'Z', '0' to '9', '.', '-', '_' and '$'; if non empty it must contain exactly one '$' character. Example of this is $.space wich uses the name provided by user when creating the space and append ".space" to it. "Team Meeting" creates the url 'Team.Meeting.space@domain'.
callLegProfile: Which calllegProfile do you want any accessMethods created with this template to use? If not provided, it uses what is set CoSpaceTemplate level and if none there, use what is at the system/profile level.
generateUniqueCallId: Whether to generate a unique numeric ID for this access method which overrides the global one for the cospace.
dialInSecurityProfile: Which dialInSecurityProfile do you want any accessmethods created with this template to use? If not provided, it uses what is set CoSpaceTemplate level and if none there, use what is at the system/profile level.
CMS 3.0 removed the persistent chat function, but in CMS 3.2 the non-persistent chat within spaces returned. Chat is available to web app users and is not stored anywhere. Once CMS 3.2 is installed, web app users are by default able to message eachother during meetings. These messages are only available during the meeting, and only messages exchanged after joining are seen. You can not join late and scroll back to see previous messages.
WebRTC point to point calls
On CMS 2.9.x, WebRTC participants were able to dial from their client directly to other contacts. Starting in CMS 3.0, this is no longer possible. Now users must sign in and join a space. From there, if they have permission in the callLegProfile (addParticipants parameter set to True), they are able to add other contacts. This causes CMS to dial out to the participant and they meet on a space in CMS.
Notable webBridge settings changes
CMS 3.0 and 3.1 has removed or relocated some of the webbridge settings from the GUI and they need to be configured in the API to keep the consistent experience for users. On 3.x, use api/v1/webBridges and api/v1/webBridgeProfiles.
Check what you currently have configured so when you upgrade to 3.0, you can configure the webbridge and webbridge Profiles in API accordingly.
In 3.0, Web bridge settings were removed on the GUI, then in CMS 3.1, the External access fields have been removed as well.
Web bridge settings in GUI
Guest account client URI - this was used by the callBridge to find the webBridge. If you had multiple webBridges in your deployment for WebRTC, this field must already be blank, and you must have unique URLs in api/v1/webbridges for each webBridge that the callBridge needs to connect to. Delete anything in this field and make sure you have the webBridges configured in the API.
Guest Account Jid Domain - this is not used anymore in CMS 3.0 and you can delete this.
Guest Access Via ID and Passcode - removed and not replaced in CMS 3.0.
Guest Access Via Hyper Links - now configurable under webBridgeProfiles in API in setting "AllowSecrets".
Notice in CMS 3.0, serveral fields have been removed from api/v1/webBridges.
resourceArchive - now in webbridgeProfiles.
idEntryMode - now deprecated.
allowWeblinkAccess - now in webBridgeProfiles as allowSecrets.
showSignin - now in webBridgeProfiles as userPortalEnabled.
resolveCoSpaceCallIds- now in webbridgeProfiles.
resolveLyncConferenceIDs - now in webbridgeProfiles.
resourceArchive - if you use custom backgrounds and your resource archive is stored on a web server, enter the URL here.
allowPasscodes - if false, users do not have an option to join meetings as guests. They can only sign in or use a URL containing the space info and secret
userPortalEnabled - if this is set to false, the web app portal landing page does not show the sign in option. It only displays the fields for entering the Call ID/Meeting ID/URI and PIN/Passcode if one is configured.
allowUnauthenticatedGuests - if set to False, guests cannot join any meetings - even with the full URL that contains the meeting ID and secret. When False, only users who can sign in can join a meetings. Example. User2 is trying to use the URL for User1's meeting. After entering the URL, User2 must sign in to continue to User1's meeting.
resolveCoSpaceCallIds - if set to False, guests can only join meetings by entering the URI and PIN/Passcode if used. Call ID/Meeting ID/Numeric ID are not accepted.
resolveCoSpaceUris - 3 possible settings: off, domainSuggestionDisabled, and domainSuggestionEnabled. Whether or not this webBridge accepts coSpace and coSpace accessMethod SIP URIs for the purpose of allowing visitors to join cospace meetings.
- When set to 'off' join by URI is disabled.
- When set to 'domainSuggestionDisabled' join by URI is enabled but the domain of the URI is not autocompleted or verified on webBridges using this webBridgeProfile.
- When set to 'domainSuggestionEnabled' join by URI is enabled and the domain of the URI can be autocompleted and verified on webBridges using this webBridgeProfile.
External Access section removed from Web GUI
In CMS 3.1, the External Access section has been removed from the web GUI. If you had these configured prior to the upgrade, then you need to reconfigure them in the API under webbbridgeProfiles.
First, you need to create a webbridgeProfile as described in the previous section. Once you have created a webbridgeProfile, then you can create a IVR Number and/or Web Bridge URI via the links available in API under the newly created webBridgeProfile.
You can create up to 32 IVR numbers or 32 webbridgeAddresses per webBridgeProfile
If you have recorder or streamer configured in 2.9.x, you need to reconfigure the settings in MMP and API so that these continue to work after the upgrade.
Before the CMS upgrade to 3.0, it is recommended to take a backup using 'backup snapshot <servername_date>', and then log into the webadmin page on your callbridge nodes to remove all XMPP Settings. Then connect to the MMP on your servers, and perform the these steps on all Core servers that have xmpp over a SSH connection:
xmpp certs none
xmpp domain none
The Figures show an example of the configurations seen on CMS 2.9.1 when recorder was configured, and how it looks immediately after the upgrade to 3.0.
After the upgrade, you must reconfigure the recorder:
Step 1. Configure the SIP listening interface.
recorder sip listen a 5060 5061 (The interface and ports that SIP recorder is set up to listen on for TCP and TLS, respectfully. If you do not want to use TLS, you can use 'recorder sip listen a 5060 none')
Step 2. Configure the certificates the recorder uses if you are using a TLS connection.
recorder sip certs <key-file> <crt-file> [crt-bundle] (Without these certificates, the tls service does not start on the recorder. The recorder uses the crt-bundle to verify the callBridge certificate.)
Step 3. Configure the call limit.
recorder limit <0-500|none> (Sets the limit for the number of simultaneous recordings the server can serve. This table is in our documentation and the recorder limit must align with the resources on the server.)
On api/v1/callProfiles, you need to configure the sipRecorderUri. This is the URI that the callBridge dials when it has to start a recording. The domain of this URI needs to be added to your outbound rules table and point to the recorder (or call control) as the SIP Proxy to Use.
This Figure shows a direct dial to the recorder component on the outbound rules found on Configuration > Outbound Calls.
This Figure shows a call to the recorder component via a call control (like for example Cisco Unified Communications Manager (CUCM) or Expressway).
Note: If you configured the recorder to use SIP TLS and if calls are failing, check your callBridge node in MMP to see if you have TLS SIP verification enabled. The MMP command is 'tls sip'. Calls could fail because the recorder certificate is not trusted by the callBridge. You can test this by disabling this on the callBridge using 'tls sip verify disable'.
Configure each one as explained, and adjust your outbound rules accordingly. If you use a direct to recorder method, change the existing outbound to recorder rule to behavior "Continue" and add a new outbound rule beneath the previous one with the priority one less than the first one. When the first recorder has reached its call limit, it sends a 488 Unacceptable here back to callBridge, and the callBridge moves to the next rule.
If you want to load balance your recorders, use a call control and adjust your call control routing so it is able to place calls to multiple recorders.
After the upgrade from 2.9.x to 3.0, you need to reconfigure streamer.
Step 1. Configure the SIP listening interface.
streamer sip listen a 6000 6001 (The interface and ports that SIP streamer is set up to listen on for TCP and TLS, respectfully. If you do not want to use TLS, you can use 'streamer sip listen a 6000 none')
Step 2. Configure the certificates the streamer uses if you are using a TLS connection.
streamer sip certs <key-file> <crt-file> [crt-bundle] (Without these certificates, the tls service does not start on the streamer. The streamer uses the crt-bundle to verify the callBridge certificate.)
Step 3. Configure the call limit
streamer limit <0-500|none> (Sets the limit for the number of simultaneous streams the server can serve. This table is in our documentation and the streamer limit must align with the resources on the server.)
On api/v1/callProfiles, you need to configure the sipStreamUri. This is the URI that the callBridge dials when it has to start streaming. The domain of this URI needs to be added to your outbound rules table and point to the streamer (or call control) as the SIP Proxy to Use.
This Figure shows a direct dial to the streamer component on the outbound rules found on Configuration > Outbound Calls.
This Figure shows a call to the recorder component via a call control (like for example Cisco Unified Communications Manager (CUCM) or Expressway).
Note: If you configured the streamer to use SIP TLS and if calls are failing, check your callBridge node in MMP to see if you have TLS SIP verification enabled. The MMP command is 'tls sip'. Calls could fail because the streamer certificate is not trusted by the callBridge. You can test this by disabling this on the callBridge using 'tls sip verify disable'.
Configure each one as explained, and adjust your outbound rules accordingly. If you use a direct to streamer method, change the existing outbound to recorder rule to behavior "Continue" and add a new outbound rule beneath the previous one with the priority one less than the first one. When the first streamer has reached its call limit, it sends a 488 Unacceptable here back to callBridge, and the callBridge moves to the next rule.
If you want to load balance your streamers, use a call control and adjust your call control routing so it is able to place calls to multiple streamers.
If you use Cisco Expressway for Web Proxy, you must ensure your Expressway is running at least X12.6 before the CMS upgrade. This is required by CMS 3.0 for web proxy to work and to be supported.
The capacity for web app participants has increased over Expressways when used with CMS 3.0. For a large OVA Expressway, the expected capactiy is 150 Full HD calls (1080p30) or 200 Other type calls (for example 720p30). You can increase this capacity by clustering Expressways, up to 6 nodes (where 4 is used for scaling and 2 for redundancy, so up to a maximum of 600 Full HD calls, or 800 Other type calls).
CMS Edge is re-introduced in CMS 3.1 as that offers higher capacities than the Expressway for external web app sessions. There are two recommended configurations.
Small Edge Specs
4 GB RAM, 4 vCPUs, 1Gbps network interface
This VM Edge spec has sufficient power to cover a single CMS1000 audio and video load capacity which is 48 x 1080p, 96 x 720p, 192 x 480p, and 1000 audio calls.
For the deployment it is recommended to have 1 small edge server per CMS1000 or 4 small edge servers per CMS2000.
Large Edge Specs
8 GB RAM, 16 vCPUs, 10Gbps network interface
This VM Edge spec has sufficient power to cover a single CMS2000 audio and video capacity which is 350 x 1080p, 700 x 720p, 1000 x 480p, and 3000 x audio calls.
For the deployment it is recommended to have 1 large edge server per CMS2000, or per 4 CMS1000.