fuctionalitywinscpiphone

CiscoMeetingServerCiscoMeetingServerRelease2.
5.
4ReleaseNotesOctober16,2019CiscoSystems,Inc.
www.
cisco.
comCiscoMeetingServerRelease2.
5.
4:ReleaseNotes2ContentsWhat'schanged41Introduction51.
1InteroperabilitywithotherCiscoproducts61.
2CiscoMeetingServerplatformmaintenance61.
2.
1CiscoMeetingServer1000andothervirtualizedplatforms61.
2.
2CiscoMeetingServer200061.
3InteractiveAPIReferenceTool61.
4EndOfSoftwareMaintenance71.
5UsingtheCiscoExpressway-EastheedgedeviceinMeetingServerdeployments71.
6UsingtheCiscoExpressway-CwiththeMeetingServerinthecorenetwork101.
6.
1UsingtheCiscoExpresswayH.
323gatewaycomponent112NewFeatures/Changesinversion2.
5122.
1Newfeaturesintroducedinversion2.
5.
4122.
1.
1BetasupportforYandexbrowserinWebRTCapp122.
1.
2JoiningoptionswithnomicrophoneorcameraforWebRTCapp122.
2Newfeaturesintroducedinversion2.
5.
3132.
2.
1AdditionalbrowsersupportforWebRTCapp132.
3Newfeaturesintroducedinversion2.
5.
2132.
3.
1AdditionalbrowsersupportforWebRTCapp132.
4Newfeaturesintroducedinversion2.
5.
1142.
4.
1AdditionalbrowsersupportforWebRTCapp142.
4.
2Importantnoteaboutaudioandvideosourceselection142.
4.
3NewMediaModuleStatusfieldintheWebAdmininterface142.
5Hostingbrandingfileslocally152.
5.
1WebRTCAppCustomization152.
5.
2IVRMessage,SIP/LyncCallMessageandInvitationTextCustomization162.
5.
3Limitations172.
5.
4Removinglocallyhostedbrandingfiles172.
5.
5Changingfromwebserver(ordefault)brandingtolocallyhostedbranding182.
5.
6Changingfromlocallyhostedtowebserverbranding:182.
5.
7Mixinglocallyhostedandwebservercustomization192.
5.
8Testingcustomizedinvitation_template.
txt192.
6WebRTCAppsupportusingSafarioniOSandMicrosoftEdge192.
6.
1ComparingfeaturesbetweentheCiscoMeetingApps20CiscoMeetingServerRelease2.
5.
4:ReleaseNotes32.
7Newserviceabilityfeatures202.
8SummaryofMMPadditions212.
9SummaryofAPIAdditions&Changes212.
10SummaryofCDRChanges212.
11SummaryofAdditionsandChangestoEvents213Upgrading,downgradinganddeployingCiscoMeetingServersoftwareversion2.
5223.
1UpgradingtoRelease2.
5223.
2Downgrading243.
3CiscoMeetingServer2.
5Deployments253.
3.
1Deploymentsusingasinglehostserver253.
3.
2DeploymentsusingasinglesplitserverhostedonaCoreserverandanEdgeserver263.
3.
3Deploymentsforscalabilityandresilience264Bugsearchtool,resolvedandopenissues274.
1Resolvedissues274.
2Openissues31CiscoLegalInformation34CiscoTrademark35CiscoMeetingServerRelease2.
5.
4:ReleaseNotes4What'schangedVersionChange2.
5.
4"Resolvedin2.
5.
4"sectionupdated.
(Oct16,2019)2.
5.
4"Resolvedin2.
5.
4"sectionupdated.
(Oct1,2019)2.
5.
4BetasupportforYandexandnewmeetingjoinoptionsintroduced.
(Sept30,2019)Addedsection"Resolvedin2.
5.
4".
Hashesupdated.
2.
5.
3AdditionalbrowsersupportforWebRTCappintroduced(April25,2019)Addedsection"Resolvedin2.
5.
3".
Hashesupdated.
2.
5.
2Secondmaintenancerelease.
(March6,2019)SupportforGoogleChrome73introduced.
Addedsection"Resolvedin2.
5.
2".
Hashesupdated.
2.
5.
1Noteaddedonaudiosourceselectioninbrowsers.
(February18,2019)2.
5.
1Section4.
1andSection4.
2updated.
(January28,2019)2.
5.
1Firstmaintenancerelease.
(January22,2019)SupportforGoogleChrome72introduced.
NewMediaModulestatusfieldintroducedintheWebAdmin.
Addedsection"Resolvedin2.
5.
1".
Hashesupdated.
2.
5.
0Minorcorrectionstoupgradesection.
(January18,2019)2.
5.
0AddedhyperlinktoFeatureComparisonMatricesmentionedinSection2.
6.
1.
(December13,2018)2.
5.
0NewreleaseofCiscoMeetingServersoftware.
(December12,2018)What'schangedCiscoMeetingServerRelease2.
5.
4:ReleaseNotes51IntroductionThesereleasenotesdescribethenewfeatures,improvementsandchangesin2.
5.
4oftheCiscoMeetingServersoftware.
TheCiscoMeetingServersoftwarecanbehostedon:ntheCiscoMeetingServer2000,aUCS5108chassiswith8B200bladesandtheMeetingServersoftwarepre-installedasthesoleapplication.
ntheCiscoMeetingServer1000,aCiscoUCSserverpreconfiguredwithVMwareandtheCiscoMeetingServerinstalledasaVMdeployment.
ntheAcanoX-Serieshardware.
noronaspecification-basedVMserver.
Note:Fromversion2.
4,theMeetingServersoftwarenolongersupportsMicrosoftHyper-V.
Throughouttheremainderofthesereleasenotes,theCiscoMeetingServersoftwareisreferredtoastheMeetingServer.
Ifyouareupgradingfromapreviousversion,youareadvisedtotakeaconfigurationbackupusingthebackupsnapshotcommand,andsavethebackupsafelyonadifferentdevice.
SeetheMMPCommandReferencedocumentforfulldetails.
Noteaboutcertificatevalidation:Fromversion2.
4,theWebBridgecorrectlyvalidatestheXMPPServer'sTLScertificate.
IfWebRTCappusershavedifficultylogginginafteryouupgradetheMeetingServer,thencheckthattheuploadedXMPPcertificatefollowstheadviceintheCertificateGuidelines.
Specifically,thattheSANfieldholdsthedomainnameoftheXMPPserver.
Priortoversion2.
4therewereissuesinXMPPcertificatevalidation.
NoteaboutMicrosoftRTVideo:supportforMicrosoftRTVideoandconsequentlyLync2010onWindowsandLync2011onMacOS,willberemovedinafutureversionoftheMeetingServersoftware.
Noteaboutincomingcalls:Bydefaultincomingcallsarenotallowed.
ToallowincomingcallstoCiscoMeetingAppusers,setparametercanReceiveCalls=trueforAPIobject/user/profiles/.
Noteaboutchatmessageboard:Forexistingdeploymentsthatusechatmessageboards,chatwillremainenabledwhenyouupgradeto2.
5.
Otherwise,youwillneedtousetheAPItocreateacallProfilewithparametermessageBoardEnabledsettotrue.
1IntroductionCiscoMeetingServerRelease2.
5.
4:ReleaseNotes61.
1InteroperabilitywithotherCiscoproductsInteroperabilitytestresultsforthisproductarepostedtohttp://www.
cisco.
com/go/tp-interop,whereyoucanalsofindinteroperabilitytestresultsforotherCiscoconferencingproducts.
1.
2CiscoMeetingServerplatformmaintenanceItisimportantthattheplatformthattheCiscoMeetingServersoftwarerunsonismaintainedandpatchedwiththelatestupdates.
1.
2.
1CiscoMeetingServer1000andothervirtualizedplatformsTheCiscoMeetingServersoftwarerunsasavirtualizeddeploymentonthefollowingplatforms:nCiscoMeetingServer1000nspecification-basedVMplatforms.
Note:Fromversion2.
4,CiscoMeetingServersoftwarenolongersupportsMicrosoftHyper-Vvirtualizeddeployments.
CAUTION:IrrespectiveofwhichvirtualizedplatformisrunningtheCiscoMeetingServersoftware,ensuretheplatformisuptodatewiththelatestpatches.
FailuretomaintaintheplatformmaycompromisethesecurityofyourCiscoMeetingServer.
1.
2.
2CiscoMeetingServer2000TheCiscoMeetingServer2000isbasedonCiscoUCStechnologyrunningCiscoMeetingServersoftwareasaphysicaldeployment,notasavirtualizeddeployment.
CAUTION:Ensuretheplatform(UCSchassisandmodulesmanagedbyUCSManager)isuptodatewiththelatestpatches,followtheinstructionsintheCiscoUCSManagerFirmwareManagementGuide.
FailuretomaintaintheplatformmaycompromisethesecurityofyourCiscoMeetingServer.
1.
3InteractiveAPIReferenceToolWerecentlyintroducedanewinteractiveAPIreferencetoolenablingyoutoseeahighlevelviewoftheAPIobjectsanddrilldowntolowerlevelsforthedetail.
Therearealsolearninglabstohelpyougetstarted,thesewillbeaddedtoovertime.
Weencourageyoutotryoutthistool;sometimeinthefuturewewilldiscontinuepublishingthepdfversionoftheAPIReferenceGuide.
https://developer.
cisco.
com/cisco-meeting-server/Stepstousethetool:1IntroductionCiscoMeetingServerRelease2.
5.
4:ReleaseNotes71.
ClickViewthedocs2.
Selectacategoryfromthelistintheleftpane.
Forexample:CallRelatedMethods.
3.
ClickonanymethodtoseeURI:GET/POST/PUT.
Refertothetableofparametersandresponseelementswithdescriptions.
Forexample:GEThttps://ciscocms.
docs.
apiary.
io/api/v1/callsNote:IfyouareusingaPOST/PUTmethods,therelated'Attributes'withdescriptionsappearontheright-handpanewhenyouselectthemethod.
Learninglabshttps://learninglabs.
cisco.
com/modules/cisco-meeting-serverThelearninglabsareintendedasastartingpoint,coveringabroadcross-sectionofwhatispossiblewiththeCiscoMeetingServerAPI.
Everylearninglabisastep-by-steptutorialwhichtakesyouthroughthestepstocompletethetaskfromstarttofinish.
Example:The'SettinguphostandguestaccesswithCiscoMeetingServerAPI'providesinstructionstoconfigurewaysinwhichuserscanjoinmeetingsinaspacewithdifferentoptions.
1.
4EndOfSoftwareMaintenanceOnreleaseofCiscoMeetingServersoftwareversion2.
5,CiscoannouncedthetimelinefortheendofsoftwaremaintenanceforthesoftwareinTable1.
Table1:TimelineforEndOfSoftwareMaintenanceforversionsofCiscoMeetingServerandCiscoMeetingAppsoftwareCiscoMeetingServersoftwareversionEndofSoftwareMaintenancenoticeperiodCiscoMeetingServerversion2.
3.
x4monthsafterfirstreleaseofCiscoMeetingServerver-sion2.
5(12thApril2019)CiscoMeetingAppversion1.
10.
x4monthsafterfirstreleaseofCiscoMeetingServerver-sion2.
5(12thApril2019)FormoreinformationonCisco'sEndofSoftwareMaintenancepolicyforCiscoMeetingServerclickhere.
1.
5UsingtheCiscoExpressway-EastheedgedeviceinMeetingServerdeploymentsOverthepreviousfewreleasesofCiscoExpresswaysoftware,edgefeatureshavebeendevelopedtoenabletheCiscoExpressway-EtobeusedastheedgedeviceinMeetingServerdeployments.
UsetheTURNservercapabilitiesinCiscoExpressway-Etoconnect:1IntroductionCiscoMeetingServerRelease2.
5.
4:ReleaseNotes8nparticipantsusingtheWebRTCapptoconferenceshostedontheMeetingServer,nremoteLyncandSkypeforBusinessclientstoconferenceshostedontheMeetingServer.
Inaddition,theCiscoExpressway-EcanbeusedasaSIPRegistrartoregisterSIPendpointsortoproxyregistrationstotheinternalcallcontrolplatform(CiscoUnifiedCommunicationsManagerorCiscoExpressway-C).
Table1belowindicatestheconfigurationdocumentationthatcoverssettingupCiscoExpressway-Etoperformthesefunctions.
Table3belowshowstheintroductionofthefeaturesbyrelease.
Note:CiscoExpressway-EcannotbeusedtoconnectremoteCiscoMeetingAppthickclients(Windows/MacdesktoporiOS)toconferenceshostedontheMeetingServer.
NorcantheCiscoExpressway-EbeusedbetweenonpremisesMicrosoftinfrastructureandtheMeetingServer.
Indeploymentswithon-premisesMicrosoftinfrastructureandtheMeetingServer,theMeetingServermustusetheMicrosoftEdgeservertotraverseMicrosoftcallsintoandoutoftheorganization.
Note:Ifyouareconfiguringdualhomedconferencingbetweenon-premisesMeetingServerandon-premisesMicrosoftSkypeforBusinessinfrastructure,thentheMeetingServerautomaticallyusestheTURNservicesoftheSkypeforBusinessEdge.
EdgefeatureConfigurationcoveredinthisguideConnectremoteWebRTCappsCiscoExpresswayWebProxyforCiscoMeetingServerDeploymentGuideConnectremoteLyncandSkypeforBusinessclientsCiscoMeetingServerwithCiscoExpresswayDeploy-mentGuideSIPRegistrarortoproxyregistrationstotheinternalcallcontrolplatformCiscoExpressway-EandExpressway-CBasicCon-figuration(X8.
11)Table2:DocumentationcoveringCiscoExpresswayastheedgedevicefortheMeetingServer1IntroductionCiscoMeetingServerRelease2.
5.
4:ReleaseNotes9CiscoExpressway-EversionEdgefeatureMeetingServerversionX8.
11Supported:-loadbalancingofclusteredMeetingServers,-MicrosoftclientsonLyncorSkypeforBusinessinfrastructureinotherorganizations,orSkypeforBusinessclientsonOffice365(not"consumer"versionsofSkype).
-interoperabilitybetweenon-premiseMicrosoftinfrastructureandon-premiseMeetingServer,wherenoMicrosoftcallstraverseintooroutoftheorganization.
-standardsbasedSIPendpoints.
-standardsbasedH.
323endpoints.
-CiscoMeetingAppthinclient(WebRTCapp)usingTCPport443.
Notsupported:-offpremiseCiscoMeetingAppthickclients(Windows/MacdesktoporiOS).
-interoperabilitybetweenon-premiseMicrosoftinfrastructureandon-premiseMeetingServerwhereMicrosoftcallstraverseintooroutoftheorganization,inthisscenario,theMeetingServermustusetheMicrosoftEdgeservertotraverseMicrosoftcallsintoandoutoftheorganization.
SeeCiscoMeetingServerwithCiscoExpresswayDeploymentGuide(2.
4/X8.
11.
4).
2.
4X8.
10Supported:-MicrosoftclientsonLyncorSkypeforBusinessinfrastructureinotherorganizations,orSkypeforBusinessclientsonOffice365(not"consumer"versionsofSkype),-standardsbasedSIPendpoints,-CiscoMeetingAppthinclient(WebRTCapp)usingUDPport3478toconnecttotheMeetingServerviatheExpresswayreversewebproxy.
Notsupported:-loadbalancingofclusteredMeetingServers,-offpremiseCiscoMeetingAppthickclients(Windows/MacdesktoporiOS)orCiscoMeetingAppthinclient(WebRTCapp)usingTCPport443,-interoperabilitybetweenonpremisesMicrosoftinfrastructureandMeetingServer;inthisscenario,theMeetingServermustusetheMicrosoftEdgeservertotraverseMicrosoftcallsintoandoutoftheorganization.
SeeCiscoExpresswayWebProxyforCiscoMeetingServer2.
3Table3:ExpresswayedgesupportfortheMeetingServer1IntroductionCiscoMeetingServerRelease2.
5.
4:ReleaseNotes10CiscoExpressway-EversionEdgefeatureMeetingServerversionX8.
9Supported:-MicrosoftclientsonLyncorSkypeforBusinessinfrastructureinotherorganizations,orSkypeforBusinessclientsonOffice365(not"consumer"versionsofSkype),-standardsbasedSIPendpoints.
Notsupported:-loadbalancingofclusteredMeetingServers,,-off-premiseCiscoMeetingAppthickclients(Windows/MacdesktoporiOS)andCiscoMeetingAppthinclient(WebRTCapp),-interoperabilitybetweenonpremisesMicrosoftinfrastructureandMeetingServer;inthisscenario,theMeetingServermustusetheMicrosoftEdgeservertotraverseMicrosoftcallsintoandoutoftheorganizationSeeCiscoExpresswayOptionswithMeetingServerand/orMicrosoftInfrastructure2.
2YouareencouragedtomigrateyourMeetingServerdeploymentsfromusingtheMeetingServeredgecomponentstousingtheExpresswayX8.
11(orlater)TURNserver.
TheSIPedge,TURNserver,internalFirewallandH.
323gatewaycomponentswillberemovedfromtheMeetingServersoftwareatsomepointinthefuture1.
6UsingtheCiscoExpressway-CwiththeMeetingServerinthecorenetworkInadditiontodeployingCiscoExpressway-Eattheedgeofthenetwork,CiscoExpressway-CcanbedeployedinthecorenetworkwiththeMeetingServer.
IfdeployedbetweentheMeetingServerandanon-premisesMicrosoftSkypeforBusinessinfrastructure,theCiscoExpressway-CcanprovideIM&Pandvideointegration.
InadditiontheCiscoExpressway-Ccanprovidethefollowingfuctionality:naSIPRegistrar,nanH.
323Gatekeeper,ncallcontrolinMeetingServerdeploymentswithCallBridgegroupsconfiguredtoloadbalanceconferencesacrossMeetingServernodes.
FeatureConfigurationcoveredinthisguideCallcontroldevicetoloadbalanceclusteredMeetingServersCiscoMeetingServer2.
4+,LoadBalancingCallsAcrossCiscoMeetingServersSIPRegistrarCiscoExpressway-EandExpressway-CBasicConfiguration(X8.
11)Table4:AdditionaldocumentationcoveringCiscoExpressway-CandtheMeetingServer1IntroductionCiscoMeetingServerRelease2.
5.
4:ReleaseNotes11FeatureConfigurationcoveredinthisguideH.
323GatekeeperCiscoExpressway-EandExpressway-CBasicConfiguration(X8.
11)Note:WhenplanningthedialplanonExpressway,eachMeetingServerinaclusterrequiresitsownneighbourzoneontheCiscoExpressway.
FormoreinformationseeAppendixAinthewhitepaperLoadBalancingCallsAcrossCiscoMeetingServers.
1.
6.
1UsingtheCiscoExpresswayH.
323gatewaycomponentInlinewithCisco'sgoalofasingleEdgesolutionacrosstheCiscoMeetingServerandCiscoExpressway,CiscoplanstoendoflifetheMeetingServerH.
323Gatewaycomponent.
Fromversion2.
4oftheMeetingServersoftware,therewillbenofurtherbugfixesfortheH.
323Gatewaycomponent.
TheH.
323componentwillberemovedfromtheMeetingServersoftwareinafuturerelease.
CustomersareencouragedtostartevaluationofthemorematureH.
323GatewaycomponentintheCiscoExpressway,andplantheirmigrationover.
AnyH.
323endpointsregisteredtoExpressway-EorExpressway-CwillnotconsumeRichMediaSession(RMS)licenseswhencallingintotheCiscoMeetingServerfromExpresswayversionX8.
10onwards.
1IntroductionCiscoMeetingServerRelease2.
5.
4:ReleaseNotes122NewFeatures/Changesinversion2.
5Version2.
5oftheMeetingServersoftwareaddsthefollowing:nhostbrandingfileslocallyontheMeetingServer,ratherthanusingaseparatewebserver,nadditionalbrowsersupportfortheWebRTCapp,nacoupleoffeaturesimprovingserviceabilitywhichwillhelpCiscoSupportindiagnosingMeetingServerissues,nanewMMPcommandthatallowsspecificpre-releasefeaturestobeswitchedonandoff.
Inaddition,supportformorevideostreamsoverdistributionlinks,firstpreviewedinversion2.
3,isstillapreviewfeature.
Thefeaturecreatesamoreconsistentvideoexperiencefromremotesingle,dualandthreescreenendpointsystemsYouareadvisednottousebeta(orpreview)featuresinaproductionenvironment.
Onlyusetheminatestenvironmentuntiltheyarefullyreleased.
Note:Ciscodoesnotguaranteethatabetaorpreviewfeaturewillbecomeafullysupportedfeatureinthefuture.
Betafeaturesaresubjecttochangebasedonfeedback,andfunctionalitymaychangeorberemovedinthefuture.
Note:ThetermspacesisusedthroughoutthedocumentationapartfromtheAPIguidewhichstillusestheoldterminologyofcoSpaces.
2.
1Newfeaturesintroducedinversion2.
5.
42.
1.
1BetasupportforYandexbrowserinWebRTCappVersion2.
5.
4introducesBetasupportforCiscoMeetingAppforWebRTCusingYandexbrowsersonWindows.
Thisisbetaqualityincurrentversion.
2.
1.
2JoiningoptionswithnomicrophoneorcameraforWebRTCappVersion2.
5.
4introducessomenewjoiningcalloptions.
Whilejoiningameeting,youcannowchoose'nocamera'or'nomicrophone'fromtheJoiningoptionsscreen.
Thiscanbeusefulifyouhaveafaultycameraormicrophoneandyoucanseeandhearotherparticipantsinthecall,butotherparticipantscannotseeorhearyou.
Note:Wedonotrecommendchangingoptionsduringameeting.
Toaddacameraoramicrophonewhilstyouareinameeting:2NewFeatures/Changesinversion2.
5CiscoMeetingServerRelease2.
5.
4:ReleaseNotes131.
ClickBacktonavigatetothemainscreen.
Youwillstillbeinthemeeting.
2.
ClickontoopentheSettingsscreen.
Selectacameraandmicrophonefromtheoptionsshown.
3.
ClickReturntomeetingtoreturntothein-meetingscreenandcontinueyourmeetingwiththenewoptionsselected.
2.
2Newfeaturesintroducedinversion2.
5.
32.
2.
1AdditionalbrowsersupportforWebRTCappVersion2.
5.
3introducessupportforCiscoMeetingAppforWebRTCusing:lAppleSafarioniOS12.
3lAppleSafari12.
2onmacOSlMozillaFirefox68Allthesebrowsersarecurrentlyinbeta(attimeoffirstpublication).
SeeCiscoMeetingAppWebRTCImportantInformationforthelatestbrowsersupportdetails.
2.
3Newfeaturesintroducedinversion2.
5.
22.
3.
1AdditionalbrowsersupportforWebRTCappVersion2.
5.
2introducessupportforCiscoMeetingAppforWebRTCusingGoogleChromeversion73.
TheexpectedreleasedateforthisversionofChromeisMarch12th,2019.
MeetingServermustbeupgradedtoversion2.
5.
2otherwisesharingpresentationonWebRTCcallsonMeetingServerusingGoogleChrome,asdescribedbelow,willnotworkafterupdatingChrometoversion73orabove,ifthecamerapermissionsarenotgranted.
Formoreinformation,seetheSoftwareAdvisorynoticehereandtheBugSearchdetailsforCSCvo51143.
CiscoMeetingServersoftwareversionValidatedGoogleChromeversions2.
5.
272and73betaTable5:CiscoMeetingServersupportforGoogleChrome2NewFeatures/Changesinversion2.
5CiscoMeetingServerRelease2.
5.
4:ReleaseNotes14ImpactofChrome73onversionsearlierthanMeetingServer2.
5.
2lWhenusingtheWebRTCapponChromebrowserversion73,joiningameeting/callcanfailifusedinthe'ManagementandPresentation'mode,andlIfauserhaspreviouslyblockedtheCameraandMicrophonepermissions,orcannotgrantthem,theywillbeimpactedifusingChrome73.
However,iftheuserhaspreviouslygrantedpermissiontothebrowserwhilstusingtheWebRTCapptousetheCameraandMicrophone,theywillnotbeimpactedbyChrome73.
TheWebRTCapppromptsforthesepermissionsthefirsttimeausertriestojoinameetingexceptincaseswheretheychosetojoinusingthe'ManagementandPresentation'mode.
2.
4Newfeaturesintroducedinversion2.
5.
12.
4.
1AdditionalbrowsersupportforWebRTCappVersion2.
5.
1introducessupportfortheWebRTCappusingGoogleChromeversion72.
TheexpectedreleasedateforthisversionofChromeisJanuary29th,2019.
MeetingServermustbeupgradedtoversion2.
5.
1otherwiseChromeuserswillnotbeabletousetheWebRTCapponceversion72isreleased.
CiscoMeetingServersoftwareversionValidatedGoogleChromeversions2.
5.
171and72betaTable6:CiscoMeetingServersupportforGoogleChrome2.
4.
2ImportantnoteaboutaudioandvideosourceselectionCameraandmicrophoneselectioninthebrowsersisnotveryreliable,sowerecommendusingtheOperatingSystem'saudiosourceselectioninsteadofthebrowser's.
Wealsorecommendchangingoptionsbeforeacallratherthanduringthecall.
Toensurereliability,speakerselectionviathebrowserwasremovedfromWebRTCappinMeetingServerversion2.
5.
1.
2.
4.
3NewMediaModuleStatusfieldintheWebAdmininterfaceVersion2.
5.
1introducesanewfieldforMediamodulestatusontheStatuspage(System>General).
ThisfieldshowsthenumberandstatusofmediamodulesthatareoperationalontheMeetingServer.
Forexample:lVM:1/1lX-seriesX1:1/1lX-seriesX2:5/52NewFeatures/Changesinversion2.
5CiscoMeetingServerRelease2.
5.
4:ReleaseNotes15lX-seriesX3:11/11lCMS2K:7/72.
5HostingbrandingfileslocallyNote:HostingbrandingfileslocallyonAcanoXSeriesserversisbetaqualityin2.
5.
x.
Priortoversion2.
5,usingbrandingfilesfortheMeetingServerrequiredyoutoconfigureaseparatewebservertoholdthebrandingfiles(voicepromptsandlobbyscreenbrandingassets).
Fromversion2.
5onesetofbrandingfilescanbeheldlocallyontheMeetingServer.
TheselocallyhostedbrandingfilesareavailabletotheCallBridgeandWebBridgeoncetheMeetingServerisoperational,removingtheriskofdelaysinapplyingcustomizationduetoproblemswiththewebserver.
TheimagesandaudiopromptsreplacetheequivalentfilesbuiltintotheMeetingServersoftware;duringstartup,thesebrandingfilesaredetectedandusedinsteadofthedefaultfiles.
Locallyhostedbrandingfilesareoverriddenbyanyremotebrandingfromawebserver.
YoucanchangetheselocallyhostedfilessimplybyuploadinganewerversionofthefilesandrestartingtheCallBridgeandWebBridge.
Ifyouremovethelocallyhostedfiles,theMeetingServerwillreverttousingthebuilt-in(USEnglish)brandingfilesaftertheCallBridgeandWebBridgehavebeenrestarted,providingawebserverhasnotbeensetuptoprovidethebrandingfiles.
Note:Tousemultiplesetsofbrandingfiles,youstillneedtouseanexternalwebserver.
2.
5.
1WebRTCAppCustomizationThebrandingfilesfortheWebRTCappareheldwithinanarchive(zip)file,fromversion2.
5thiszipfilecanbelocallyhostedontheMeetingServer.
IfyouarechangingfromusingawebservertohostingthefileslocallythenfollowtheguidanceinSection2.
5.
7beforefollowingthestepsbelow.
Thefollowingstepsprovideanoverviewofthecustomizationprocedure,foradetailedprocedurerefertotheCustomizationGuidelines.
Note:Thecommandsinthefollowingstepsareforconsole/terminalenvironments(i.
e.
commandpromptorterminal)andnotforSFTPclientssuchasWinSCP.
1.
Createaziparchivefilenamedweb_branding.
zipcontainingthesefiles:lsign_in_settings.
jsonlsign_in_logo.
png2NewFeatures/Changesinversion2.
5CiscoMeetingServerRelease2.
5.
4:ReleaseNotes16lsign_in_background.
jpgNote:Thiszipfilemustbenamedweb_branding.
zip,itcannothaveadifferentfilename.
2.
ForeachMeetingServerwithanenabledWebBridgewhichwilllocallyhostthisziparchive:a.
ConnectyourSFTPclienttotheIPaddressoftheMMP.
b.
LoginusingthecredentialsoftheMMPadminuser.
c.
Uploadthezipfileweb_branding.
zip.
Forexample:PUTweb_branding.
zipd.
ConnectyourSSHclienttotheIPaddressoftheMMP.
e.
LoginusingthecredentialsoftheMMPadminuser.
f.
RestarttheWebBridgewebbridgerestartThenewbrandingwillbepickedupaftertherestart.
TheWebBridgeretrievesthelocallyhostedbrandingfilefortheWebRTCapp,ratherthanrelyingontheCallBridgetopassthefile.
Note:Forbrandingfilesheldonawebserver,thereisnochangeinhowthebrandingfilesarehandled;theCallBridgewillcontinuetoretrievethearchivefilefromthewebserverandpushittotheWebBridge.
2.
5.
2IVRMessage,SIP/LyncCallMessageandInvitationTextCustomizationIfyouarechangingfromusingawebservertohostingthefileslocallythenfollowtheguidanceinSection2.
5.
7beforefollowingthestepsbelow.
TolocallyhosttheIVRmessages,SIP/LynccallmessagesandinvitationtextyouneedtocreateaCallBridgebrandingzipfile.
Thefollowingstepsprovideanoverviewofthecustomizationprocedure,foradetailedprocedurerefertotheCustomizationGuidelines.
1.
Createthecallbrandingzipfile,thisfilemustbenamedcall_branding.
ziptoensureitisprocessedcorrectly.
a.
CreateasinglefolderwiththefileslistedinChapter3oftheCustomizationGuidelines,thesearethesamefilesthatareusedifawebserverisdeployed.
Note:Inlocallyhostedbranding,onlybackground.
jpgwillbeusedforthecallbackgroundandivrbackgroundimages;passcode_background.
jpg,passcode_or_blank_required_background.
jpg,passcode_or_blank_timeout_background.
jpg,deactivated_background.
jpgandivr_background.
jpgareignored.
2NewFeatures/Changesinversion2.
5CiscoMeetingServerRelease2.
5.
4:ReleaseNotes17b.
Addthefileinvitation_template.
txtcontainingtheinvitationtexttothefolder,asdescribedinChapter4oftheguidelines.
Note:Forthiscallbrandingzipfile,youmustusethefilenameinvitation_template.
txtevenifyouarealreadyusingadifferentfilenameonawebserver.
c.
Zipupthefilesinthefolder,allfilesshouldbeatthetoplevelofthezipfile(nofoldersnestedinthezipfile),thefilenamemustbecall_branding.
zip.
2.
InstalltheIVR,callandinvitationcustomizationoneveryCallBridge.
ForeachMeetingServer:a.
ConnectyourSFTPclienttotheIPaddressoftheMMP.
b.
LoginusingthecredentialsoftheMMPadminuser.
c.
Uploadthezipfilecall_branding.
zip.
Forexample:PUTcall_branding.
zipd.
ConnectyourSSHclienttotheIPaddressoftheMMP.
e.
LoginusingthecredentialsoftheMMPadminuser.
f.
RestarttheCallBridgecallbridgerestartThenewbrandingwillbepickedupaftertherestart.
2.
5.
3LimitationsnOnlyonebackgroundimagefile,background.
jpg,isusedinlocallyhostedbranding,otherimagefileswillbeignored.
nIfyouwantdifferentimagebackgroundsindifferentsituations,forexampleduringpasscodeentryorIVR,theonlywayistouseawebserverforcustomizationasdescribedintheCustomizationGuidelines.
nTousemultiplesetsofbrandingfiles,youstillneedtouseanexternalwebserver.
Note:Iffilesaretoolarge,missingorotherwiseinvalidthentheywillbetreatedinthesamewayastheirwebserverequivalentsandwillnotbeused.
Therewillbenoattempttofallbacktodefaultresources.
Anymissingaudiopromptsaresimplynotplayed,andaninvalidoromittedbackground.
jpgfileisreplacedwithasolidblackbackground.
2.
5.
4RemovinglocallyhostedbrandingfilesFollowthesestepsforeachMeetingServerhostinglocalbrandingfiles.
2NewFeatures/Changesinversion2.
5CiscoMeetingServerRelease2.
5.
4:ReleaseNotes181.
ConnectyourSFTPclienttotheIPaddressoftheMMP.
2.
LoginusingthecredentialsoftheMMPadminuser.
3.
RemovethelocallyhostedbrandingfilesfromtheWebBridgeRMweb_branding.
zip4.
RemovethelocallyhostedbrandingfilesfromtheCallBridgeRMcall_branding.
zip5.
ConnectyourSSHclienttotheIPaddressoftheMMP.
6.
LoginusingthecredentialsoftheMMPadminuser.
7.
RestarttheWebBridgewebbridgerestart8.
RestarttheCallBridgecallbridgerestart2.
5.
5Changingfromwebserver(ordefault)brandingtolocallyhostedbrandingIfchangingfromwebserver(ordefault)brandingtolocallyhostedbranding,followtheserecommendations:nnforeveryCallBridgeensure:otheresourceLocationparameterfortheIVRmessagesisnotset;useaPUTmethodtosettheresourceLocationparameterasblankon/ivrBrandingProfile/,otheresourceLocationparameterforthecallmessagesisnotset;useaPUTmethodtosettheresourceLocationparameterasblankon/callBrandingProfile/,otheinvitationTemplateparameterforthecallmessagesisnotset;useaPUTmethodtosettheinvitationTemplateparameterasblankon/callBrandingProfile/.
nforeveryCallBridgewhichhasaconfiguredWebBridge,makesuretheresourceArchivefieldisnotsetinthatconfiguration;usethePUTmethodtosettheresourceArchiveparameterasblankonAPIobject/webBridges/.
nstopusingwebserverURLsinscriptsandconfigurationsofcalllegprofiles,nconfigurecall_branding.
zipfilesoneveryCallBridge,asdescribedabove,nconfigureweb_branding.
zipfilesoneveryWebBridge,asdescribedabove.
2.
5.
6Changingfromlocallyhostedtowebserverbranding:Ifchangingfromlocallyhostedtowebserverbranding,thenfollowtheserecommendations:2NewFeatures/Changesinversion2.
5CiscoMeetingServerRelease2.
5.
4:ReleaseNotes19nremovelocallyhostedcall_branding.
zipfilesfromeveryCallBridgeasdescribedabove,nremovelocallyhostedweb_branding.
zipfilesfromeveryWebBridgeasdescribedabove,nchangeallyourscriptsandconfigurationstousehttp://mywebserver/.
.
.
asdocumentedintheCustomizationGuidelines.
2.
5.
7MixinglocallyhostedandwebservercustomizationIfyouinstallbrandingzipfilesonyourMeetingServers,butalsodeployawebserveranduseittoservebrandingresourcefiles,thennotethefollowing:ForIVR,callandinvitationcustomization:ncustomizationusingthewebserverwilloverridethelocallyhostedfiles,nleavingtheAPIfieldsblankorunsetwillcausethelocallyhostedfilestobeused.
ForWebRTCcustomization:ncustomizationusingthewebserverwilloverridethelocallyhostedfilesnitispossibletoconfigurethesameWebBridgeintheconfigurationofmorethanoneCallBridge.
Inthiscase,aconfiguredresourcearchivefromaCallBridgeonanotherMeetingServermayoverridethelocallyhostedbrandingfileforaWebBridge.
Becausethismightbeunexpected,werecommendNOTmixingthetwoconfigurations.
2.
5.
8Testingcustomizedinvitation_template.
txtTheinvitationtemplateisdeliveredfromtheMeetingServertoCiscoMeetingAppclientsandcachedlocally,soaftercustomizationontheMeetingServertheremaybeadelaybeforeclientsbegintousethenewtext.
Loggingtheclientoutandinagainshouldfetchthenewversionimmediately,butanyclientswhichstayloggedinwillnotseethenewtextuntiltheircachetimesout.
Fromversion2.
5,thisdelayhasbeenreducedtoatmost1hour.
ForclientswhichhavecachedtextfromaMeetingServerrunninganolderversion,thedelaycouldbeasmuchas24hoursintheworstcase.
2.
6WebRTCAppsupportusingSafarioniOSandMicrosoftEdgePriortoversion2.
5,theonlysupportedbrowsersfortheWebRTCappforCiscoMeetingAppwere:nGoogleChrome(Windows,macOSandAndroid)version66orlater,nMozillaFirefox(WindowsandmacOS)version60orlater.
nAppleSafariformacOSversion11.
1orlater.
TheWebRTCappenablesusersto:2NewFeatures/Changesinversion2.
5CiscoMeetingServerRelease2.
5.
4:ReleaseNotes20nparticipateinvideoandaudioconferenceshostedonaMeetingServerorindualhomedconferences,npairwithSIPendpoints,nreceiveandshareapresentation.
Version2.
5supportsadditionalbrowsers,theseare:nSafarioniOSforiPads,runningthelatestversionofiOS(recommended).
iOS11.
0istheminimumsupportedrelease.
nSafarioniOSforiPhones,runningthelatestversionofiOS(recommended).
iOS11.
0istheminimumsupportedrelease.
(Thisisbetaqualityinversion2.
5.
x).
Note:WehavetestedtheWebRTCappusingtheSafaribrowseroniPadAir2andiPadPro12.
9inch(2ndgeneration)withiOS11.
4.
1,iPad(6thgeneration)withiOS12.
0.
1,iPhone6oniOS12,iPhone7oniOS12and12.
1,iPhone8PlusoniOS12and12.
1,andiPhoneXoniOS11.
4.
1.
nthelatestversionofMicrosoftEdge(MicrosoftEdge42/MicrosoftEdgeHTML17)onMicrosoftWindows10(thisisbetaqualityinversion2.
5.
x).
Note:TherearelimitationsusingtheWebRTCappwithMicrosoftEdgeandMozillaFireFoxbrowsers:lUsingtheWebRTCappwithMicrosoftEdgewillnotworkifusingtheTURNserverinCiscoExpresswayorusingtheMeetingServerTURNwithTCP.
lUsingtheWebRTCappwithFirefoxwillnotworkifusingtheTURNserverinCiscoExpresswaywithTCP,butwillworkwiththeMeetingServerTURNwithTCP.
SeeCiscoMeetingAppWebRTCImportantInformationforfurtherdetailsontheseandotherlimitations.
2.
6.
1ComparingfeaturesbetweentheCiscoMeetingAppsTherearetwoFeatureComparisonMatrix,oneforCiscoMeetingAppversion1.
11comparingthefeaturesavailableacrosstheDesktop(WindowsandmacOS),iOSandWebRTCplatforms,theotherfortheWebRTCappforCiscoMeetingAppcomparingfeaturesacrosssupportedwebbrowsers.
2.
7NewserviceabilityfeaturesTheseserviceabilityfeatureswillhelpCiscoSupportindiagnosingMeetingServerissues.
Theimprovementsinclude:2NewFeatures/Changesinversion2.
5CiscoMeetingServerRelease2.
5.
4:ReleaseNotes21namechanismforidentifyingwhichsyslogmessagesbelongtothesameSIPconnection.
Theidentificationcanbeundertakenmanuallyorbywritingascript.
namethodtoeasilydeterminewhichlogmessagebelongstowhichcall/conference.
Neitheroftheseserviceabilityfeaturesareintendedforusebycustomers,howeverCiscoSupportmayrequestsyslogsfromacustomer,andwillusethesenewfeaturestodetermineanyissues.
2.
8SummaryofMMPadditionsTheseadditionalMMPcommandsinversion2.
5shouldnotbeusedunlessunderinstructionfromCiscoSupportorCiscoEFT,nofeaturesinversion2.
5.
4requireswitchingon.
CommandDescriptionwebbridgeoptionsSwitchesonthespecifiedfeatures,ifmorethanonefeatureistobeenabledthenseparatethefeature_nameswithaspace.
OnlyusethiscommandunderinstructionfromCiscoSupportorCiscoEFT.
Thesefeaturesarenotsuitableforproductionuse.
Thefeatureswillremainenabledacrossreboots,butwillbeautomaticallyclearedwhenusingtheupgradecommandwebbridgeoptionsnoneSwitchesoffallfeaturesthatwerepreviouslyswitchedonusingthewebbridgeoptionscom-mand.
OnlyuseunderinstructionfromCiscoSupportorCiscoEFT.
2.
9SummaryofAPIAdditions&ChangesTherearenonewadditionsorchangestotheAPIobjectsorparametersforversion2.
5.
2.
10SummaryofCDRChangesTherearenonewCDRrecordsorparametersforversion2.
5.
2.
11SummaryofAdditionsandChangestoEventsTherearenonewadditionsorchangestotheEventsforversion2.
5.
2NewFeatures/Changesinversion2.
5CiscoMeetingServerRelease2.
5.
4:ReleaseNotes223Upgrading,downgradinganddeployingCiscoMeetingServersoftwareversion2.
5ThissectionassumesthatyouareupgradingfromCiscoMeetingServersoftwareversion2.
4.
Ifyouareupgradingfromanearlierversion,thenCiscorecommendsthatyouupgradeto2.
4firstfollowingtheinstructionsinthe2.
4.
xreleasenotes,beforefollowinganyinstructionsintheseCiscoMeetingServer2.
5ReleaseNotes.
ThisisparticularlyimportantifyouhaveaCiscoExpresswayconnectedtotheMeetingServer.
Note:Ciscohasnottestedupgradingfromasoftwarereleaseearlierthan2.
4.
TocheckwhichversionofCiscoMeetingServersoftwareisinstalledonaCiscoMeetingServer2000,CiscoMeetingServer1000,orpreviouslyconfiguredVMdeployment,usetheMMPcommandversion.
IfyouareconfiguringaVMforthefirsttimethenfollowtheinstructionsintheCiscoMeetingServerInstallationGuideforVirtualizedDeployments.
3.
1UpgradingtoRelease2.
5TheinstructionsinthissectionapplytoMeetingServerdeploymentswhicharenotclustered.
FordeploymentswithclustereddatabasesreadtheinstructionsinthisFAQ,beforeupgradingclusteredservers.
CAUTION:BeforeupgradingordowngradingMeetingServeryoumusttakeaconfigurationbackupusingthebackupsnapshotcommandandsavethebackupfilesafelyonadifferentdevice.
SeetheMMPCommandReferencedocumentforfulldetails.
Donotrelyontheautomaticbackupfilegeneratedbytheupgrade/downgradeprocessasitmaybeinaccessibleintheeventofafailedupgrade/downgrade.
Upgradingthefirmwareisatwo-stageprocess:first,uploadtheupgradedfirmwareimage;thenissuetheupgradecommand.
Thisrestartstheserver:therestartprocessinterruptsallactivecallsrunningontheserver;therefore,thisstageshouldbedoneatasuitabletimesoasnottoimpactusersorusersshouldbewarnedinadvance.
Toinstallthelatestfirmwareontheserverfollowthesesteps:1.
ObtaintheappropriateupgradefilefromthesoftwaredownloadpagesoftheCiscowebsite:Cisco_Meeting_Server_2_5_4_CMS2000.
zip3Upgrading,downgradinganddeployingCiscoMeetingServersoftwareversion2.
5CiscoMeetingServerRelease2.
5.
4:ReleaseNotes23Thisfilerequiresunzippingtoasingleupgrade.
imgfilebeforeuploadingtotheserver.
UsethisfiletoupgradeCiscoMeetingServer2000servers.
Hash(SHA-256)forupgrade.
imgfile:f6cca939e556796eca0ca333d4236c09a188b13fd48899cca1ae76155c45a973Cisco_Meeting_Server_2_5_4_vm-upgrade.
zipThisfilerequiresunzippingtoasingleupgrade.
imgfilebeforeuploadingtotheserver.
UsethisfiletoupgradeaCiscoMeetingServervirtualmachinedeployment.
Hash(SHA-256)forupgrade.
imgfile:fd129757f954d9d76c08dbd6f042d7d0c648bc790b1add9cd03ba6198ec9de28Cisco_Meeting_Server_2_5_4_x-series.
zipThisfilerequiresunzippingtoasingleupgrade.
imgfilebeforeuploadingtotheserver.
UsethisfiletoupgradeAcanoX-seriesservers.
Hash(SHA-256)forupgrade.
imgfile:695ce0f2654cbe6dbd49289dbd5f321b21bcced9896c834ef1efcb3e4af50f31Cisco_Meeting_Server_2_5_4.
ovaUsethisfiletodeployanewvirtualmachineviaVMware.
ForvSphere6,hash(SHA-512)forCisco_Meeting_Server_2_5_4_vSphere-6_0.
ovafile:a096b89396f90a4e18becb77f0882949bd4836b1744444572b0f6e22db1058816d944e1fadd821ea62a483603053c1ee1dfe93d45950f771a54a300440a6eba3ForvSphere6.
5andhigher,hash(SHA-512)forCisco_Meeting_Server_2_5_4_vSphere-6_5.
ovafile:774a5a492fd2d8f3d2cc45d905f6550bec7139f6f7f8fcb5563eecffecf379334ead00caa9fdc0dd1773a05887cce1b9b22b352f28cd437cb4988667d3b27a312.
TovalidatetheOVAfile,thechecksumforthe2.
5.
4releaseisshowninapopupboxthatappearswhenyouhoveroverthedescriptionforthedownload.
Inaddition,youcanchecktheintegrityofthedownloadusingtheSHA-512hashvaluelistedabove.
3.
UsinganSFTPclient,logintotheMMPusingitsIPaddress.
ThelogincredentialswillbetheonessetfortheMMPadminaccount.
IfyouareusingWindows,werecommendusingtheWinSCPtool.
Note:IfyouareusingWinSCPforthefiletransfer,ensurethattheTransferSettingsoptionis'binary'not'text'.
Usingtheincorrectsettingresultsinthetransferredfilebeingslightlysmallerthantheoriginalandthispreventssuccessfulupgrade.
Note:a)YoucanfindtheIPaddressoftheMMP'sinterfacewiththeifaceaMMPcommand.
b)TheSFTPserverrunsonthestandardport,22.
4.
CopythesoftwaretotheServer/virtualizedserver.
5.
Tovalidatetheupgradefile,issuetheupgradelistcommand.
3Upgrading,downgradinganddeployingCiscoMeetingServersoftwareversion2.
5CiscoMeetingServerRelease2.
5.
4:ReleaseNotes24a.
EstablishanSSHconnectiontotheMMPandlogin.
b.
Outputtheavailableupgradeimagesandtheirchecksumsbyexecutingtheupgradelistcommand.
upgradelistc.
Checkthatthischecksummatchesthechecksumshownabove.
6.
Toapplytheupgrade,usetheSSHconnectiontotheMMPfromthepreviousstepandinitiatetheupgradebyexecutingtheupgradecommand.
a.
Initiatetheupgradebyexecutingtheupgradecommand.
upgradeb.
TheServer/virtualizedserverrestartsautomatically:allow10minutesfortheprocesstocomplete.
7.
VerifythattheMeetingServerisrunningtheupgradedimagebyre-establishingtheSSHconnectiontotheMMPandtyping:version8.
Updatethecustomizationarchivefilewhenavailable.
9.
IfyouaredeployingascaledorresilientdeploymentreadtheScalabilityandResilienceDeploymentGuideandplantherestofyourdeploymentorderandconfiguration.
10.
Ifyouhavedeployedadatabasecluster,besuretorunthedatabaseclusterupgrade_schemacommandafterupgrading.
ForinstructionsonupgradingthedatabaseschemarefertotheScalabilityandResilienceDeploymentGuide.
11.
Youhavecompletedtheupgrade.
3.
2DowngradingIfanythingunexpectedoccursduringoraftertheupgradeprocessyoucanreturntothepreviousversionoftheMeetingServersoftware.
Usetheregularupgradeprocedureto"downgrade"theMeetingServertotherequiredversionusingtheMMPupgradecommand.
1.
CopythesoftwaretotheServer/virtualizedserver.
2.
Toapplythedowngrade,usetheSSHconnectiontotheMMPandstartthedowngradebyexecutingtheupgradecommand.
TheServer/virtualizedserverwillrestartautomatically—allow10-12minutesfortheprocesstocompleteandfortheWebAdmintobeavailableafterdowngradingtheserver.
3.
LogintotheWebAdminandgotoStatus>GeneralandverifythenewversionisshowingunderSystemstatus.
4.
UsetheMMPcommandfactory_resetappontheserverandwaitforittorebootfromthefactoryreset.
3Upgrading,downgradinganddeployingCiscoMeetingServersoftwareversion2.
5CiscoMeetingServerRelease2.
5.
4:ReleaseNotes255.
Restoretheconfigurationbackupfortheolderversion,usingtheMMPcommandbackuprollbackcommand.
Note:Thebackuprollbackcommandoverwritestheexistingconfigurationaswellasthelicense.
datfileandallcertificatesandprivatekeysonthesystem,andrebootstheMeetingServer.
Thereforeitshouldbeusedwithcaution.
Makesureyoucopyyourexistingcms.
licfileandcertificatesbeforehandbecausetheywillbeoverwrittenduringthebackuprollbackprocess.
The.
JSONfilewillnotbeoverwrittenanddoesnotneedtobere-uploaded.
TheMeetingServerwillreboottoapplythebackupfile.
Foraclustereddeployment,repeatsteps1-5foreachnodeinthecluster.
6.
InthecaseofXMPPclustering,youneedtore-clusterXMPP:a.
PickonenodeastheXMPPmaster,initializeXMPPonthisnodeb.
OncetheXMPPmasterhasbeenenabled,joininganyotherXMPPnodestoit.
c.
Providingyourestoreusingthebackupfilethatwascreatedfromthesameserver,theXMPPlicensefilesandcertificateswillmatchandcontinuetofunction.
7.
Finally,checkthat:ltheWebAdmininterfaceoneachCallBridgecandisplaythelistofcoSpaces.
ldialplansareintact,lXMPPserviceisconnectedlnofaultconditionsarereportedontheWebAdminandlogfiles.
lyoucanconnectusingSIPandCiscoMeetingApps(aswellasWebBridgeifthatissupported).
ThedowngradeofyourMeetingServerdeploymentisnowcomplete.
3.
3CiscoMeetingServer2.
5DeploymentsTosimplifyexplaininghowtodeploytheMeetingServer,deploymentsaredescribedintermsofthreemodels:thesinglecombinedMeetingServer,thesinglesplitMeetingServerandthedeploymentforscalabilityandresilience.
Allthreedifferentmodelsmaywellbeusedindifferentpartsofaproductionnetwork.
3.
3.
1DeploymentsusingasinglehostserverIfyouaredeployingtheMeetingServerasasinglehostserver(a"combined"deployment),werecommendthatyoureadandfollowthedocumentationinthefollowingorder:3Upgrading,downgradinganddeployingCiscoMeetingServersoftwareversion2.
5CiscoMeetingServerRelease2.
5.
4:ReleaseNotes261.
AppropriateInstallationGuideforyourCiscoMeetingServer(CiscoMeetingServer2000,CiscoMeetingServer1000andvirtualizeddeployments,ortheinstallationguideforAcanoX-SeriesServer).
2.
TheSingleCombinedMeetingServerDeploymentGuideenablingallthesolutioncomponentsonthesinglehost.
ThisguidereferstotheCertificateGuidelinesforSingleCombinedServerDeploymentsfordetailsonobtainingandinstallingcertificatesforthisdeployment.
Note:TheCiscoMeetingServer2000onlyhastheCallBridge,WebBridge,XMPPserveranddatabasecomponents.
Itcanbedeployedasasingleserveronaninternalnetwork,butifadeploymentrequiresfirewalltraversalsupportforexternalCiscoMeetingAppclients,thenTURNserverandLoadBalanceredgecomponentsneedtobedeployedonaseparateCiscoMeetingServer1000orspecification-basedVMserver-seethe"singlesplit"deploymentbelow.
3.
3.
2DeploymentsusingasinglesplitserverhostedonaCoreserverandanEdgeserverIfyouaredeployingtheMeetingServerinasplitservermodel,werecommendthatyoudeploytheXMPPserverontheCoreserver,anddeploytheLoadBalancerontheEdgeserver.
Readandfollowthedocumentationinthefollowingorder:1.
AppropriateInstallationGuideforyourCiscoMeetingServer2.
TheSingleSplitMeetingServerDeploymentGuide.
ThisguidereferstotheCertificateGuidelinesforSingleSplitServerDeploymentsfordetailsonobtainingandinstallingcertificatesforthisdeployment.
3.
3.
3DeploymentsforscalabilityandresilienceIfyouareinstallingtheMeetingServerforscalabilityandresilienceusingmultiplehostservers,werecommendthatyoudeploytheXMPPserveronCoreservers,anddeployLoadBalancersontheEdgeserver.
Readandfollowthedocumentationinthefollowingorder:1.
AppropriateInstallationGuideforyourCiscoMeetingServer2.
TheScalabilityandResilienceDeploymentGuide.
ThisguidereferstotheCertificateGuidelinesforScalableandResilientServerDeploymentsfordetailsonobtainingandinstallingcertificatesforthisdeployment.
3Upgrading,downgradinganddeployingCiscoMeetingServersoftwareversion2.
5CiscoMeetingServerRelease2.
5.
4:ReleaseNotes274Bugsearchtool,resolvedandopenissuesYoucannowusetheCiscoBugSearchTooltofindinformationonopenandresolvedissuesfortheCiscoMeetingServer,includingdescriptionsoftheproblemsandavailableworkarounds.
Theidentifierslistedinthesereleasenoteswilltakeyoudirectlytoadescriptionofeachissue.
1.
Usingawebbrowser,gototheBugSearchTool.
2.
Signinwithacisco.
comregisteredusernameandpassword.
Tolookforinformationaboutaspecificproblemmentionedinthisdocument:1.
EnterthebugidentifierintheSearchfieldandclickSearch.
Tolookforinformationwhenyoudonotknowtheidentifier:1.
TypetheproductnameintheSearchfieldandclickSearchor,intheProductfieldselectSeries/ModelandstarttypingCiscoMeetingServer,thenintheReleasesfieldselectFixedintheseReleasesandtypethereleasestosearchforexample2.
5.
4.
2.
Fromthelistofbugsthatappears,filterthelistusingtheModifiedDate,Status,Severity,Ratingdropdownlists.
TheBugSearchToolhelppageshavefurtherinformationonusingtheBugSearchTool.
4.
1ResolvedissuesIssuesseeninpreviousversionsthatarefixedin2.
5.
4CiscoidentifierSummaryCSCvq19622ThisissuehasbeenfiledtoevaluatetheproductagainstthevulnerabilityreleasedbytheNetflixonJune17thaffectingFreeBSDandLinuxkernels,identifiedbyCVEIDs:-CVE-2019-11477:SACKPanic-CVE-2019-11478:SACKSlownessorExcessResourceUsage-CVE-2019-11479:ExcessResourceConsumptionDuetoLowMSSValuesCiscohasreviewedthisproductandconcludedthatitisaffectedbythisvulnerabilityasitcontainsavulnerableversionofLinuxKernel.
CSCvq24159OnMeetingServer2000,somemediamodulesarefailingafterareboot/upgradeorcallbridgerestart.
CSCvq30379Callsintoaconferencefeaturingnootherlocalparticipantsdonotresultindistributionlinksbeingcreatedtoothercallbridgesthatdohaveactiveparticipantsforthecon-ferenceinotherregions.
4Bugsearchtool,resolvedandopenissuesCiscoMeetingServerRelease2.
5.
4:ReleaseNotes28CiscoidentifierSummaryCSCvp06073WhenapresentationissharedfromWebRTCwhenusingthe'ManagementandPresentation'joiningmethod,thenegotiatedbandwidthforthepresentationstreamiscappedwhichleadstopoorqualitybeingseenbythereceivers.
CSCvo91844DegradedaudiomayoccuronafullyloadedMeetingServerwithmanyaudiopar-ticipants.
CSCvo10678Inadistributedcallwithrecordingstarted,wheneverthedistributedcallisdropped,therecording/streamingisstopped,eventhoughthereareparticipantsremainingintheconference.
CSCvq11136WhencrosslaunchingtoanativeMeetingAppclient(desktoporiOS)whenalanguageotherthanEnglishisset,themessage"Youarenolongerinthemeeting"equivalentisdisplayedinthebrowser.
CSCvq39444Whenaguestuserjoinsandthedefaultcameraisnotworkingtheusergetsredirectedtoa'Couldnotjoinmeeting'pageandthenbacktothewebbridgelandingpageshortlyafter.
CSCvq84608Asplashscreenmomentarilydisplays(ispendingdestroy.
Performingpartialdetach.
.
.
"Issuesseeninpreviousversionsthatarefixedin2.
5.
1CiscoidentifierSummaryCSCvn81865SupportfortheWebRTCappusingGoogleChromeversion72.
SeeNewfeaturesintroducedin2.
5.
1forfurtherinformation.
CSCvo02066CiscoMeetingAppusersexperienceintermittentfailureswhenauthenticatingwithCiscoMeetingServer.
CSCvn14138The"mediamodulestatus"lineinthelogsisnotfollowedbytheusualnumberstoindicatethehealthofthemediaframeworkonCiscoMeetingServer2000.
CSCvn37841Novideo/audioreceivedfromaremoteparticipantinadistributedcallonclusteredCiscoMeetingServer2000.
CSCvm95156WhenrunningatrunkdebugonMeetingServer2000itreturnsanerrorthatthefileisnotfound.
CSCvk67533Whenrecordingasessionitstopsafter1-3hoursofrecordingduetoarecorder"keepalivefailure".
4Bugsearchtool,resolvedandopenissuesCiscoMeetingServerRelease2.
5.
4:ReleaseNotes31CiscoidentifierSummaryCSCvj13390InclusteredenvironmentswithmultipleTURNServersconfigured,ifoneTURNserverisbecomingunavailable,thewebbridgedoesnotcorrectlydetectthisinordertofail-overtotheotheravailableTURNservers-itcontinuestoadvertisethenonavailableonetoWebRTCclients.
CSCvn04352WhencrosslaunchingMeetingAppclientthroughIEbrowseritconnectsas"guest"whenusingthehostpasscodeforameeting.
Issuesseeninpreviousversionsthatarefixedin2.
5.
0CiscoidentifierSummaryCSCvn59240IfyoujoinacallusingtheSafaribrowsertoopentheWebRTCapp,butthenopenanothertabinthebrowserwithanotherwebpagedisplayed,Safariwillstopsendingvideototheotherparticipantsintheconference.
SendingvideoisresumedifyouswitchbacktothetabcontainingtheWebRTCapp.
CSCvn16684IftheXMPPcomponentdrops,thenCiscoMeetingAppuserspairedtoSIPendpointsareloggedoutandremovedfromthemeeting.
CSCvm38925CallstoCTSendpointsfailduetotheMeetingServersendingoutboundSIPcallswithoutcisco-tiporx-cisco-multiple-screeninthecontactheader,whenconnectingusingTCPorTLS.
CSCvk067078JoiningaconferenceonaMeetingServerusingJabberforWindows(deskphonemode),afterplacingthecallonHoldthevideoqualityisdegradedtoalowerres-ultion/frameratewhenitisResumed.
CSCvk03337SomeTIPcallsfailwithTIPnegotiationtimeout.
CSCvn26366Whentheuploaderisenabled,thesessiontimeoutisnotextendedproperlyanditmaycauseloginfailuresfromMeetingServertoVBrickRev.
4.
2OpenissuesThefollowingareknownissuesinthisrelease.
IfyourequiremoredetailsentertheCiscoidentifierintotheSearchfieldoftheBugSearchTool.
CiscoidentifierSummaryCSCvr16426The"Participantadd"ActiveControloptioncanbeseenonActiveControl-compatibleendpointsthataremembersofaDualHomemeeting,eventhoughthefunctionisnotsupportedandwillnotworkcorrectly.
CSCvo66473MicrophoneselectiononCiscoMeetingAppforWebRTCdoesn'tworkonSafarionMac.
UseGoogleChromeifyouneedtousemicrophoneselectionordisabletheextramicrophonespriortojoiningaMeetingAppmeeting.
4Bugsearchtool,resolvedandopenissuesCiscoMeetingServerRelease2.
5.
4:ReleaseNotes32CiscoidentifierSummaryCSCvn65208IfCallBridgeGroupsareinuseandtheAPIparametersloadBalanceOutgoingCallsandloadBalanceUserCallsaresettotrue,ifaWebRTCappattemptstomakeacallusingthe"Usemyphoneforaudio"optionandthiscalllandsonadifferentCallBridgetotheonethattheCiscoMeetingAppuserisinstantiatedon,thentheWebBridgewilllosecommunicationwithothercomponentsordevices.
ExistingWebRTCappsessionswillceasetoworkandnonewWebRTCapploginsarepossible.
RestartingtheWebBridgefromtheMMPinterfacewillrestorefunctionality.
CSCvn65112Forlocallyhostedbranding,iftheaudiopromptfilesareomittedthenthedefaultbuilt-inpromptsareusedinstead.
Tosuppressallaudiopromptsuseazero-bytefile,ratherthannofileatall.
CSCvn63172LowqualityaudioandvideoexperiencedonTIPendpointsthatjoinconferenceshostedonMeetingServer2000withaheavyconferenceload.
CSCvm56734Inadualhomedconference,thevideodoesnotrestartaftertheattendeeunmutesthevideo.
CSCvj49594ActiveControldoesnotworkafterahold/resumewhenacalltraversesCiscoUnifiedCommunicationsManagerandCiscoExpressway.
CSCvh23039TheUploadercomponentdoesnotworkontenantedrecordingsheldontheNFS.
CSCvh23036DTLS1.
2,whichisthedefaultDTLSsettingforMeetingServer2.
4,isnotsupportedbyCiscoendpointsrunningCE9.
1.
x.
ActiveControlwillonlybeestablishedbetweenMeet-ingServer2.
4andtheendpoints,ifDTLSischangedto1.
1usingtheMMPcommandtls-min-dtls-version1.
0.
CSCvh23028ChangingtheinterfacethattheWebBridgelistensonorreceivingaDHCPleaseexpire,willcausetheWebBridgetorestart.
WebRTCAppusersmayhavetologinagain.
CSCvg62497IftheNFSissetorbecomesReadOnly,thentheUploadercomponentwillcontinuouslyuploadthesamevideorecordingtoVbrick.
ThisisaresultoftheUploaderbeingunabletomarkthefileasuploadcomplete.
Toavoidthis,ensurethattheNFShasread/writeaccess.
CSCve64225CiscoUCSManagerforCiscoMeetingServer2000shouldbeupdatedto3.
1(3a)tofixOpenSSLCVEissues.
CSCve60309CiscoUCSManager3.
1(3a)reports'DIMMA1onserver1/1hasaninvalidFRU'astheCMS2000DIMMsarenotlistedinthe3.
2(3e)Tcatalog.
CSCve37087butrelatedtoCSCvd91302OneofthemediabladesoftheCiscoMeetingServer2000occasionallyfailstobootcor-rectly.
Workaround:ReboottheFabricInterconnectmodules.
Inadditionthereisthefollowinglimitation:CAUTION:ThemaximumnumberofconcurrentXMPPclientssupportedbythecurrentMeetingServersoftwareis500.
Thismaximumisatotalnumberofalldifferentclients(CiscoMeetingApp,WebRTCSign-inandWebRTCGuestclients)registeredatthesametimetoclustered4Bugsearchtool,resolvedandopenissuesCiscoMeetingServerRelease2.
5.
4:ReleaseNotes33MeetingServers.
IfthenumberofconcurrentXMPPregistrationsexceeds500sessions,someunexpectedproblemswithsigninmayoccuroritmayleadtoasituationwhereallcurrentlyregisteredusersneedtore-signin,thiscancauseadenialofservicewhenalluserstrytosigninatthesametime.
Note:Theincreasedcallcapacityof700HD(720p30)or350fullHD(1080p30)callsonaCiscoMeetingServer2000onlyappliestoasingleMeetingServerorclusterofMeetingServers.
TheHDcallcapacityofMeetingServerswithinaCallBridgegroupremainsat500.
Note:TherearelimitationsusingtheWebRTCappwithEdgeandFireFoxbrowsers.
UsingtheWebRTCappwithEdgewillnotworkifusingtheTURNserverinCiscoExpresswayorusingtheMeetingServerTURNwithTCP.
UsingtheWebRTCappwithFirefoxwillnotworkifusingtheTURNserverinCiscoExpresswaywithTCP,butwillworkwiththeMeetingServerTURNwithTCP.
RefertotheCiscoMeetingApp(WebRTC)2.
5.
xReleaseNotesforfurtherdetailsontheseandotherlimitationsifusingtheWebRTCapp.
4Bugsearchtool,resolvedandopenissuesCiscoMeetingServerRelease2.
5.
4:ReleaseNotes34CiscoLegalInformationTHESPECIFICATIONSANDINFORMATIONREGARDINGTHEPRODUCTSINTHISMANUALARESUBJECTTOCHANGEWITHOUTNOTICE.
ALLSTATEMENTS,INFORMATION,ANDRECOMMENDATIONSINTHISMANUALAREBELIEVEDTOBEACCURATEBUTAREPRESENTEDWITHOUTWARRANTYOFANYKIND,EXPRESSORIMPLIED.
USERSMUSTTAKEFULLRESPONSIBILITYFORTHEIRAPPLICATIONOFANYPRODUCTS.
THESOFTWARELICENSEANDLIMITEDWARRANTYFORTHEACCOMPANYINGPRODUCTARESETFORTHINTHEINFORMATIONPACKETTHATSHIPPEDWITHTHEPRODUCTANDAREINCORPORATEDHEREINBYTHISREFERENCE.
IFYOUAREUNABLETOLOCATETHESOFTWARELICENSEORLIMITEDWARRANTY,CONTACTYOURCISCOREPRESENTATIVEFORACOPY.
TheCiscoimplementationofTCPheadercompressionisanadaptationofaprogramdevelopedbytheUniversityofCalifornia,Berkeley(UCB)aspartofUCB'spublicdomainversionoftheUNIXoperatingsystem.
Allrightsreserved.
Copyright1981,RegentsoftheUniversityofCalifornia.
NOTWITHSTANDINGANYOTHERWARRANTYHEREIN,ALLDOCUMENTFILESANDSOFTWAREOFTHESESUPPLIERSAREPROVIDED"ASIS"WITHALLFAULTS.
CISCOANDTHEABOVE-NAMEDSUPPLIERSDISCLAIMALLWARRANTIES,EXPRESSEDORIMPLIED,INCLUDING,WITHOUTLIMITATION,THOSEOFMERCHANTABILITY,FITNESSFORAPARTICULARPURPOSEANDNONINFRINGEMENTORARISINGFROMACOURSEOFDEALING,USAGE,ORTRADEPRACTICE.
INNOEVENTSHALLCISCOORITSSUPPLIERSBELIABLEFORANYINDIRECT,SPECIAL,CONSEQUENTIAL,ORINCIDENTALDAMAGES,INCLUDING,WITHOUTLIMITATION,LOSTPROFITSORLOSSORDAMAGETODATAARISINGOUTOFTHEUSEORINABILITYTOUSETHISMANUAL,EVENIFCISCOORITSSUPPLIERSHAVEBEENADVISEDOFTHEPOSSIBILITYOFSUCHDAMAGES.
AnyInternetProtocol(IP)addressesandphonenumbersusedinthisdocumentarenotintendedtobeactualaddressesandphonenumbers.
Anyexamples,commanddisplayoutput,networktopologydiagrams,andotherfiguresincludedinthedocumentareshownforillustrativepurposesonly.
AnyuseofactualIPaddressesorphonenumbersinillustrativecontentisunintentionalandcoincidental.
Allprintedcopiesandduplicatesoftcopiesofthisdocumentareconsidereduncontrolled.
Seethecurrentonlineversionforthelatestversion.
Ciscohasmorethan200officesworldwide.
AddressesandphonenumbersarelistedontheCiscowebsiteatwww.
cisco.
com/go/offices.
2018-2019CiscoSystems,Inc.
Allrightsreserved.
CiscoLegalInformationCiscoMeetingServerRelease2.
5.
4:ReleaseNotes35CiscoTrademarkCiscoandtheCiscologoaretrademarksorregisteredtrademarksofCiscoand/oritsaffiliatesintheU.
S.
andothercountries.
ToviewalistofCiscotrademarks,gotothisURL:www.
cisco.
com/go/trademarks.
Third-partytrademarksmentionedarethepropertyoftheirrespectiveowners.
TheuseofthewordpartnerdoesnotimplyapartnershiprelationshipbetweenCiscoandanyothercompany.
(1721R)CiscoTrademark