Avaya-6方視頻會議系統(tǒng)

CM6-PartyVideoConferencingOverviewDescriptionVideoconferencesworkjustlikeaudioconferences.Adminconfiguresvideobridgesforad-hocvideoconferencingWhenvideousershittheconferencebutton,CMautomaticallysetsupcallstoavideobridgetosupporttheconference.NoIDs;nosetup;noredial;nothingtoremember.CMconferencefeatureslikeconf-display,far-endmuteworkasnormalTargetmarket:anyonewhousesvideo.CM6-PartyVideoConferencingHowItWorksBehindthescenes,CMmakescallstotheselectedvideobridgeonbehalfofeachendpoint.Oncetheseareup,theendpointsareconnectedtothebridge(“bridge-moved”)Audio-onlyendpointsshareasingleaudio-onlybridgeconnection(mixingdonebyCMmediaprocessor).Newlegsareaddedorremovedaspeoplejoinorleavetheconference.CMwillnothijackscheduledconferencesforthis.AlwaysgetthebestCMhasavailableNohiddenworkaroundsOverviewDescriptionUpto40videobridgesperCMLimitedonlybyvideocallcapacityandlicensedvideobridgecapacity.S8700supports1000simultaneousvideocalls.That’s333x3-personad-hoccalls,ifyouhaveenoughbridgeports.S8300supports150simultaneousvideocalls.That’s50x3-personad-hoccalls,SupportsselectedSIPandH.323videobridgesPolycomRMX,MGC(H.323)AvayaMeetingExchange/MX(SIP)CapacitySolutionView–NetworkTopologyNetworkRegion2NetworkRegion1NetworkRegion3NetworkRegion4SingleCM-MultipleRMX/MGCSolutionView–NetworkTopologyNetworkRegion2NetworkRegion1NetworkRegion3NetworkRegion4SingleMX-MultipleCMsCallTopology–Mergevs.CascadeIfCMcontrolstheconference,thenewpartyjoinsthead-hocconference–invideoasinaudio–amerge.Ifyouconferencetogethertwoexistingad-hocconferences,theybecomeonead-hocconference–amerge.IfCMdoesnotcontroloneorbothconferences,itcannotaddnewmemberstoitormovethemtotheotherconference.Itcreatesalinkline–acascade.Examplesof“non-controlled”conferences:ScheduledconferenceMultipointVSXConferenceonanotherCM.Whathappenswhenyouconferenceinanewparty?CascadedCallNote:scheduledandad-hocconferencesmaybeonthesamebridge!Scheduledconference+ad-hocAliceAliceBobBobCarolCarolDaveDaveScheduledScheduledAd-hocBandwidthManagementVideobridgetakesonnetworkregionofitssignalinggroups(onlyoneregionallowed).NormalbandwidthrestrictionsapplyCMwillattempttofindthebest-connectedMCUforagivenconference,butwillnotmovearoundasparticipantschange(exception:audioisamust)Someotherwisevideo-capableendpointsmayonlygetaudioduetobandwidthlimitationsCMwillneveruseabridgeunlessatleastthreevideoendpointscanconnecttoit,butmaystilluseoneevenifnotallthevideo-capableendpointsgetvideo.(Nobridgeusageunlessthreevideoendpoints)ResourceManagementRMXreportsresourceusage,allowingCMtodynamicallyadjusttootherusesofbridgeandinternalprocessingneedsMXalsoreportsresourceusageandcanthereforebearesourceforseveralCMsatonceMGCdoesnot-CMattemptstotrackbasedonitsownconfiguration,butcannotallowforscheduledconferencesMGCmustthereforebededicatedtoad-hoc.MGCissupported,butnotrecommended-candemovideoconferencingtoacustomerusingtheircurrentMGCNoothervideobridgesaresupported!LoadBalancingCMhasresourceinformationfromallofitsbridges(eitherinternaltrackingordirectreporting)Wheretherearechoices,CMwillchooseleast-loadedvideobridgeUserExperienceOnstartinganewconference(AcallsB,holds;callsC,hitsconference)Longerbreakinaudio(~2seconds,becauseofsetuptimetoMCU)Videocomesupquickerthananexistingconference.CalllegstobridgeareshuffledFromexistingconference(addpartytoexistingconference,orfourth+partyaddsvideoconferencingpermission)ShorteraudiobreakonMCUconnection(<500ms)Videocomesupslower.Noshuffling-sonowidebandPlayatoneineachcasetoindicatethattheconferencehasreachedtheMCU;allowsuserstoanticipateshortbreakinaudio.StartuptimemuchshorteronRMXvs.MGCWhocanuse6-partyvideoconferencing?UserhasvideoifCMadministratorgivesittothemNewCOSentryaddedtocontrolthisPriorityuserscangetspecialtreatmentforad-hocWhoDecidesonUsageIfanyoneonthecallhasvideoconferencingpermitted,ithappensIfsomeonewithvideoconferencingpermittedjoinsorstartsacall,itbecomesvideo-conferencing-capablePrincipleofleastsurprise:DoesnotdependonwhoisconferencedfirstDoesnotdependonwhodoestheconferencingContinuesevenifvideo-permitteduserleavesWhenisvideoconferencingtriggered?Everytimesomeonejoins,CMcheckstoseeiftheycannowhavead-hocvideoconferencingIfthesixthpersontojoinhaspermissions,wewillbridge-movethewholeconferencePreviouslytheconferencemayhavebeenvideo-conferencing-capable,buttheremayhavebeennobridgefree–ifanewcheckshowsanavailablebridge,itwillbeused.Hold-unholdwillalsoresultinacheckonvideobridgeresourcesWhensomeoneleavesandthereareonlytwovideoendpointsleft,CMwillreleasethebridgeandconnectdirectlyWaits30secondsincaseanewpersonjoinsPreservationofaudioIfthebridgerunsoutofresources(e.g.whenascheduledconferencestarts),itwillthrowoutthead-hocusersCMwillreverttoaudioconferencingautomatically.CMinsistsoneveryonegettingaudio(viabridgeorCMresources),evenifthatmeansnovideo.WillgeneratedenialeventswhenforcedtorevertVideoconferencingwillneverresultinworseconnectivity-e.g.IGAR-connectedendpointswillstillgetaudioVideoBridgeAdminAd-hocconferencingportscontrolledbysystem-parametersVideoBridgeAdminMaxports–totalacrossallthead-hocconferencesthisbridgehosts(e.g.18portssupports36-partyconferences)Whenyoufillinatrunk,morefieldsappearbasedonthetrunktypeNotpossibletomixtrunktypes.Weusetheoutgoingtrunkstomakecalls;theincomingtrunksallowustotellwhenthebridgeisinservice.Two-waytrunksdoboth.VideoBridgeAdminResourceinfospecifieswhetherfarendwillprovideupdatesandtrackportusageMustbesupportedbybridge(RMX,MX,notMGC)ChangesfieldsdisplayedbelowitVideoBridgeAdminTocreateaconference,CMsendsafactorynumberoverthetrunk,andsuppliesorrequestsaconferenceIDFactoriesandIDsonlymeaningfultobridgeNeednotbeindialplanNeednotbeuniqueacrossbridges.MustconfigureenoughIDstosupportexpectedconferencesVideoBridgeAdmin(PolycomRMX:H.323)FactoryisanentryqueuenumberontheRMXwhichdynamicallycreatesaconferenceIDsmustbeconfiguredtoallowad-hocconferencecreationonbridge(butCMchooseswhichtouse)PrioritynumberusedwhenapriorityuserstartscallStandardnumberusedotherwiseVideoBridgeAdmin(AvayaMX:SIP)Factorynumbersonly,conferenceIDssetbybridgeSIPfactorycanbelettersordigitsResourceInfoaddressmustbeagreedwithbridgeVideoBridgeAdmin–NoResourceInfoTurnoff“FarEndResourceInfo”fieldCMstopsexpectingresourceupdatesfromfarendMakessimpleassumptionsaboutresources–managementisnotaseffectiveDoesn’tusefactory,justcallsdirecttoconferenceID–eachmustbeconfiguredasanopenconference(meet-me).StatusScreenWhenvideoconferencingnottriggered,firstplacetolook.Ismybridgeinservice?Isitfull?Isitfailing?Findoutifresourceupdateshavenotbeensent.Statuscodes:out-of-service:nosignalinggroupsinservicein-service:OKlow-resources:bridgereportsitisnearlyfullcall-rejected:bridgehasrejectedacallno-resources:bridgehasnotyetsentresourceinfotrunks-busy:alltrunkstobridgearebusied-out.StatusScreenLookatthestatusscreen(previousslide)CheckpermissionsonCOSscreenCheckthetrunksandsignalinggroupswith“statustrunk”and“statussignaling-group”Denialevents2377:Videobridgerejectedcallleg(checkbridgeapp)2386:NosuitableMCUavailable(checksetup,bandwidth)2389:Notenoughtrunkmemberstoconnecttobridge2392:Videobridgedroppedcallleg(checkbridgeapp)Othersinthisrange(2377-2392)aswell.TroubleshootingCheckthatyourbridgeisworking(usingbridge-specificmanagementappsuchasRMXwebinterface)Checkthatyourbridgeisconfiguredproperly(factorynumbers,resourcesubscription,conferenceIDsetc)Configuredirectdialonthetrunk,testit.Ifyouarenotalsousingyourbridgeforscheduledconferences,temporarilysetupasifyouwereForH.323,checksi