AGENDA 1. CMR(Collaboration Meeting Room) 아키텍처이해 2. 텔레프레즌스구축형컨퍼런스아키텍처이해 - 텔레프레즌스서버 - Conductor - 스케줄링아키텍처 3. 컨퍼런스패키지라이선스 4. 맺음말 2

텔레프레즌스아키텍처고급디자인 이덕주부장 djl@cisco.com Cisco Systems, Collaboration CSE

1. CMR 아키텍처

CMR 이란? Cisco Collaboration Meeting Rooms (CMR) 이란고객에게어떤표준기반의비디오단말장비군과시스코웹엑스솔루션을가상의미팅룸형태로제공되는검증받은플랫폼통칭 구성형태는구축타입, 클라우드타입, 하이브리드타입으로분류 단일미팅단일경험어디서나누구에게

CMR 의구성품 CMR 구축형 CMR 하이브리드 CMR 클라우드 On Premise bridges On Premise bridges Bridging in the cloud WebEx Integration WebEx Integration WebEx Integration Personal Meeting Rooms Personal Meeting Rooms Unified Roster List on WebEx Non-Scheduled Scheduled (via PT, Smart Scheduler, TMS) Non-Scheduled & Scheduled (via PT, WebEx Portal) 5

CMR 구축형아키텍처 Unified CM Requirements: TMS 14.6 TMSPE 1.4 Conductor XC3.0 TS 4.1 Conductor TMS and TMSPE installed On same server TMS TMSPE TMS, TMSPE, Conductor 필수 TMSPE 는 CMR 프로비저닝을위한웹포털역할 Conductor 를통한회의실구성 API 연동 각 CMR 번호는비디오단말번호형태로저장 (DN or URI) 비디오주소는 Conductor 와연동하기위해서 Unified CM 의다이얼플랜과연동 Permanent/Rendezvous 타입회의가능 Bridge Resources Pool 6

CMR 구축형아키텍처 Deployment 1 2 3 4 관리자 TMS 사용자 사용자 회의사용자를 import 함 최대 100,000 사용자 자동으로사용자 import 구성템플릿설정 기존 import 된사용자에게 TMS 가메일을전송 관리자가사용자에게메일을전송 셀프서비스포털의링크로이동해 CMR 세칭 개인배너 비밀번호설정 PIN 개인레이아웃설정 기타회의설정 자신의 CMR 번호를다른사용자와공유해회의진행 7

CMR 구축형아키텍처 Step 1 TMS 와 Conductor 연결 8

CMR 구축형아키텍처 Step 2 TMS 에서 Conductor 템플릿설정 9

CMR 구축형아키텍처 Step 3 각사용자가사용자포털에서설정 Collaboration Meeting Room Setup your Collaboration Meeting Room Collaboration Meeting Room 10

CMR 구축형아키텍처 Step 3 각사용자가사용자포털에서설정 11

CMR 구축형아키텍처 Step 4 스마트스케줄러로스케줄링 Smart Scheduler 12

CMR 하이브리드아키텍처 High Level Unified CM VCS-C or Expressway-C VCS-E Expressway E WebEx Client TS / MCU All others 99xx H.323 Endpoints Audio, Video, and Presentation over SIP TMS TMSXE OBTP EX, MX, SX, C series CTS / TX Scheduling in Outlook with WebEx PT, WebEx mailbox or via TMS Smart Scheduler or admin booking SIP SIP TLS H.323 Media 13

CMR 하이브리드아키텍처 High Level Unified CM VCS-C VCS-E WebEx Client 1 720p capable, Recvs 360p Sends 720p WebEx Client 2 360p capable, Recvs 360p Sends 360p WebEx Client 3 90p (recvg) 360p 수신 360p 수신 ok@ 90p from WX TS / MCU TP Server 나 MCU 는 H.264 AVC 트랜스코딩, 각단말이서로다른밴드위스와비트레이트로연결이가능 WebEx 는 SVC 스위칭기반의솔루션 WebEx 는트랜스코드하지않으므로, WebEx 클라이언트중비디오를못받는경우존재 SIP SIP TLS H.323 Media 14

CMR 하이브리드아키텍처 High Level Unified CM TS / MCU VCS-E B) WebEx Client 720p sent SIP Media A) WebEx Client 720p capable 360p recv d 기본비디오는 UDP 로그다음 TCP TCP 는패킷로스발생시단말들이비디오를받지못하는경우생성 고객의방화벽이 UDP 패킷이흘러갈수있도록유도 C) WebEx Client 360p recv d D) WebEx Client 90p recv d (from WX only) 15

CMR 클라우드아키텍처 High Level CUCM SIP Trunk Traversal Zone RTP/SRTP to the cloud SIP + BFCP H.323 + H.239 Expressway-E DX 80 SIP Expressway-C CMR Cloud SX 20 H.323 VCS Control VCS Expressway PSTN Audio TSP Audio WebEx Audio 비디오단말 인프라 DMZ Audio Options

CMR 클라우드아키텍처 (SIP 호 ) 시스코 CMR 클라우드인프라 Cisco Endpoint Expressway-C Well-defined DMZ/NAT/FW Expressway-E Cisco Endpoint DNS UC Manager TURN Internet CMR 클라우드엣지 다자간인프라풀 시스코인프라를가지고있고 DNS SRV 를기반으로한 SIP URI 다이얼링을함 CMR 클라우드엣지가클라우드에있는다자간인프라풀로연결을해줌 17

CMR 클라우드아키텍처 (H.323 호 ) CustomerA.com Cisco H.323 Endpoint VCS Control Well-defined DMZ/NAT/FW VCS Expressway Customer B.com Cisco H.323 endpoint Arbitrary NAT/FW DNS Customer C.com VCS Control VCS Expressway Internet CMR Cloud E dge Multipoint Infr astructure Cisco Collaboration Cloud 3rd Party H.323 Endpoint 고객 A / 시스코비디오단말군이 VCS 에등록해서 DNS SRV 를통한 URI 다이얼링 ( 가장이상적인구조 ) 고객 B / 시스코 H.323 단말은 3 rd 파티에지솔루션및방화벽투과를연동한 URI 콜 고객 C / 3 rd 파티단말장비군이 Cisco VCS 등록하고 VCS-E 를통해연동해 DNS SRV 를통한콜가능 18

CMR 클라우드아키텍처 (H.323 호 ) DNS Customer C.com VCS Control VCS Expressway Internet CMR Cloud E dge Multipoint Infr astructure Cisco Collaboration Cloud 3rd Party H.323 Endpoint Customer D.com Well-defined NAT/FW 3rd Party Endpoint 3rd Party Edge Solution 3rd Party Call Control Customer E.com 3rd Party H.323 endpoint Arbitrary NAT/FW 고객 D / 3 rd 파티단말군이 3 rd 파티호제어및방화벽투과솔루션에연동에 DNS SRV 를통한 URI 다이얼링호출 고객 E / 3 rd 파티단말군이어떤인프라도없고 DNS 를통한 URI 호출이가능한상태라면 meetingid@h323.s ite.webex.com 나 userid@h323.site.webex.com 형태로콜가능 ( 단말상황과네트워크상황에따른 Ad-hoc) 19

2. 텔레프레즌스구축형컨퍼런스아키텍처이해

텔레프레즌스아키텍처 OverView 본사 Prime Collaboration TMS Unified CM Expressway-C Expressway-E CUBE Management Conductor Call Control Edge Internet Mobile Worker ISR ISR TS MPLS WAN TS TS Other UC Ap plications Unity Conne ction IM and Pr esence Conferencing UC Applications Gateway PSTN / ISDN Remote Site Endpoints SIP Trunk(s) 21

구축형컨퍼런스핵심제품군 Headquarters Prime Collaboration TMS Expressway-C Expressway-E Unified CM CUBE Management Conductor Call Control Edge Internet Mobile Worker ISR ISR TS MPLS WAN TS TS Other UC Applica tions Unity Connection IM and Prese nce Conferencing UC Applications Gateway PSTN / ISDN Remote Site Endpoints SIP Trunk(s) 22

TelePresence Server 플랫폼 VMWare 기반의 TP 서버 (specs based) Vmware 서버어플라이언스 하드웨어 Appliances 블레이드 8-core 310 1 to 12 ports at 720p 1 to 10 ports at 720p 400v 320 8710 30vCPU 1 to 36 ports at 720p 1 to 24 ports at 720p 1 to 24 ports at 720p 1 to 20 ports at 720p 24

TelePresence Server 제품군 TelePresence Server on Virtual Machine (vts) vts 의세가지버전 : Multiparty Media 400v 특정 UCS 플랫폼에서적용가능 최대 18 스크린라이센스 (36 HD ports) Co-residency 지원하지않음 (ships as dedicat ed UCS box) 8-core vts 3.1 소프트웨어버전에서지원 최대 5 스크린라이선스지원 (10 HD ports) BE6K, BE7K, 스펙 Based 서버에서지원 다른소프트웨어와동시에사용가능 30vCPU High Density VM 4.1 이전버전에서 16-core 에서구성 최대 10 스크린라이센스 (20 HD ports) BE6K, BE7K, 스펙 Based 서버에서지원 다른소프트웨어와동시에사용불가 25

TelePresence Server HD 용량 + 28% 30 20 +20% +20% 28 36 TS 4.0 TS 4.1 10 +25% +20% 16 20 20 24 8 10 10 12 8 8-core vts + co-res apps Multiparty Media 310 30 vcpu vts* Multiparty Media 320 Multiparty Media 400v * Known as 16-core vts in TS 4.0 26

TelePresence Server 플랫폼업그레이드 50% 용량상승 업계선도 MM400v MM410v MM410v Blade Server 지금가능 4 월오더예상 4 월오더예상 36 HD ports / server 54 HD ports / server 54 HD ports / blade 432 HD ports / chassis (8 blades) 1 RU 1 RU 6 RU 36 HD ports / RU 54 HD ports / RU 72 HD ports / RU 27

Telepresence Server 의사용자환경 단일스크린환경 멀티스크린환경 Single ActivePresence Prominent Equal 28 28

Telepresence Server 의사용자환경 이름표시 현재발언자 Overflow indicator 오디오사용자아바타녹화표시 29

듀얼스크린장비를위한새로운레이아웃 30

멀티스트리밍 (SVC 소개 ) Scalable Video Codec (SVC) 하나이상의스트리밍을인코딩할수있는표준프로토콜. 각비트스트리밍은낮은 Spatial 해상도 (smaller screen), 낮은 temporal 해상도 (lower frame rate), or 낮은비디오품질의시그널을포함하고있음. 31

멀티스트리밍 (SVC 소개 ) Temporal Scaling 서로다른프레임 7.5 fps 15 fps 30 fps Spatial Scaling 서로다른해상도 180p 360p 720p Quality Scaling Signal to Noise (SNR) ratio 서로다른품질 32

멀티스트리밍 (SVC 소개 ) 다중레이어층을통한멀티소스를인코딩 Base Layer with lowest fidelity Spatial Enhancement Layer to increase resolution Temporal Enhancement Layer to increase frame rate Quality Enhancement Layer to increase bit rate 360p 30Hz 0.5Mb/s 720p 30Hz 1.0Mb/s 720p 60Hz 1.5Mb/s 720p 60Hz 2.0Mb/s 스위칭 vs. 트랜스코딩은다자간서버의확장성과유연성과관련 회선속도의응답성과에러복원기능도추가기능으로제공 단점은인코딩의효율성과단말장비군의호환성의문제 33

기존 Transcoded only 비디오 TS 4.0 and older 4.0 이전버전의경우, 모든콜이트랜스코딩됨 H.264 AVC Decoders TelePresence Server Compositor 각비디오스트리밍은 : Encoder H.264 AVC TS 에의해먼저디코딩되고 필요에따라스케일되며 Scalers 레이아웃형태로제작되고 단일스트리밍으로재인코딩됨 장점 최고의호환성제공 모든단말에가장최선의밴드위스와해상도제공 단점 인코딩 / 디코딩시의복잡도로지연증가 단말자체가레이아웃생성할수없음 34

새로운 Multistream only 비디오 각단말이브리지에멀티비디오스트리밍을보낼기능을탑재 같은스트리밍에, 서로다른해상도를포함하고있음 (1080p, 720p and 360p) H.264 SVC Switching Fabric H.264 SVC 브리지는각단말이요구하는스트리밍으로서로다른해상도로연결 ( 스위칭 ) 각단말은서로다른조합으로이스트리밍을로컬에서재조합할수있음 H.264 SVC 장점 더적은지연, 더좋은비디오품질 (no decode/re-encode) 각단말이조합할수있는다양한레이아웃조합 단점 단말이지원해야함 특정상황에서더많은밴드위스가필요 단말의호환성문제대두 35

하이브리드컨퍼런싱 New 멀티스트리밍과, 트랜스코딩의두가지장점을결합한시스코 TP 서버의기능 단말소프트웨어 TC7.3. 부터테스트모드지원, 다음버전에정식지원 TP 4.1 부터 Multiparty Media 310, 320, 400v, vts 플랫폼지원 SIP 만지원 (not H.323 or TIP) TS remotely managed 모드로지원 (Conductor 필수 ) TS 는기존레거시장비를위한트랜스코딩계속지원, 가능하면하이브리드모드지원 용량의변화는없음 Note: 멀티스트리밍은메인비디오에만적용, 콘텐트는여전히트랜스코딩모드로지원 36

H.264 AVC Endpoints H.264 SVC Endpoints 하이브리드컨퍼런싱 TS 4.1 and later LD (ex. 180p, 360p) TelePresence Server Switching Fabric Experimental in TC 7.3 H.264 SVC HD (ex. 1080p, 720p) H.264 SVC Decoder Encoder H.264 AVC Decoder Scaler Compositor Encoder 37

하이브리드컨퍼런싱지원단말 Experimental in TC 7.3 SX20/MX200 G2/ MX300 G2 SX80/MX700/800 Max of 4 streams Max of 16 streams Max of 4 streams Max of 16 streams 필요인프라구성 Unified CM 10.5(2) or later Conductor XC3.0 or later TC 7.3 or later (experimental) TelePresence Server 4.1 on 310, 320, 400v, or vts 38

하이브리드컨퍼런싱을위한인프라 CUCM 아래와같이 Allow ix Application Media 가 SIP 프로파일에서활성화되어야함, 각트렁크세팅에적용이되어야함 ( 예를들면 Conductor 트렁크사이드 ) Conductor Conference Template 에서 Enable ix protocol 세팅이 True 로되어있는지확인. 39

기존아키텍처스케줄링 Unified CM Expressway-C Expressway-E Internet Conductor TS for scheduling TMS SIP SIP and API control TS Pool for non-scheduling 41

최신구성스케줄링아키텍처 Unified CM Expressway-C Expressway-E Internet Conductor TMS Requirements: TMS 14.6 TS 4.1 Conductor XC3.0 SIP SIP and API control Shared Pool of TS Resources 42

TMS 스케줄링과 Conductor Overview 최소소프트웨어버전 : TMS 14.6 Conductor XC3.0 TS 4.1 현재 Multiparty Media 310, 320, 400v and 가상 TP 서버가스케줄링가능 (including C MR Hybrid conferences) 스케줄링을위한브리지리소스는전용 (dedicated) 모드거나공용 (shared) 로구성해야함 43

TMS 스케줄링과 Conductor 스케줄링옵션 전용리소스구성 (Dedicated) 공용 (Shared) Conductor TMS Conductor TMS Instant and Permanent Scheduled Instant, Permanent, and Scheduled 기존 TMS 가 TP 서버를직접예약하는방식과동일. 단일 TS, 단일브리지풀, 단일서비스프레퍼런스로구성. T MS 가여러개의우선순위로여러개의서비스프레퍼런스로구성가능. IP Zones 은 Conductor IP Zone 기반으로구성. 가장간단한구성, TP 서버는어떤회의도다양하게구성가능. If 사용률이높다면, 추가 TP 서버를구성할수있음. Optimized Conferencing 구성으로확장가능. 44

TMS 스케줄링과 Conductor High Level Conductor TS 를브리지풀로등록 Service Preference 란에풀우선순위설정 풀설정에서스케줄링옵션설정 회의템플릿에서스케줄링활성화 TMS Conductor 등록 옵션 : TS 를 TMS 에등록 TMS 스케줄링을위한 conference alias 설정 (Regex) Service Preference 용량설정 Conductor 에서 H.323 비활성화 Preferred MCU 설정을 Conductor 로설정 TMS Enabled Disabled Conductor 45

TMS 스케줄링과 Conductor 구축모델 -1 스케줄링회의를위한전용브리지모드 (Dedicated) 구성 단일브리지를단일풀로설정 Conductor 에서이풀을설정 이풀은 TMS 에용량정보를리포팅 장점 회의의가용성이확보 회의브리지가최대가될되까지 TMS 리소스확보가능 단점 이회의브리지는스케줄전용으로사용해야함 Service Preference 1 Conductor TMS Scheduled Pool 46

TMS 스케줄링과 Conductor 구축모델 -2 스케줄링회의를위한전용및백업브리지 구성 2 개의풀과각풀에각브리지로설정 2 번째풀은백업으로구성 첫번째풀만 Conductor 의서비스프레퍼런스를위한스케줄링으로설정 장점 회의의가용성이확보 회의브리지가최대가될되까지 TMS 리소스확보가능 백업브리지를통한백업확보 단점 2 개의브리지가스케줄링에사용, 리소스문제 Service Preference 2 Primary Scheduled Pool Enabled Disabled Conductor TMS Backup Scheduled Pool 47

TMS 스케줄링과 Conductor 구축모델 -3 스케줄링회의를위한전용브리지 / 백업브리지를풀로구성 구성 두개이상의풀로구성하고하나의브리지를스케줄링전용으로사용 다른풀은스케줄링용도와비스케줄링용도의브리지를포함. 장점 회의의가용성이확보 회의브리지가최대가될되까지 TMS 리소스확보가능 백업브리지를통한백업확보 단점 하나의브리지는전용으로스케줄링으로사용 Service Preference 3 Primary Scheduled Pool Conductor TMS Shared Use Pool This shared pool is used by other Service Preferen ces as well 48

TMS 스케줄링과 Conductor 구축모델 -4 브리지를풀로구성 / 스케줄링과비스케줄링회의동시진행 구성 하나이상의풀과하나이상의브리지를스케줄링과비스케줄링으로사용 모든풀들은일단 Conductor 의서비스 preference 에스케줄링으로설정해 TMS 와연동 장점 텔레프레즌스서버를사용하는가장효율적인방법 모든회의타입은 Optimized Conferencing 기능을사용할수있음 단점 스케줄회의를위한전용리소스는보장받지않음 비스케줄링회의가리소스를사용할수있음 전체적인리소스할당에고려할부분 Service Preference 4 Conductor Shared Use Pool TMS 49

TMS 스케줄링과 Conductor 고려사항 TMS 는 Conductor cluster 를지원하지않음 각 Conductor 는 TMS 에각각별도로등록을해야하며, 각노드는별도로동작하므로사용자의구성에따라달라짐. Conductor Cluster TMS 50

Conductor 기본이해 Conductor 란? Conductor 란? Conductor 란? 회의의가상화다자간회의리소스관리회의솔루션프로비저닝 일관된사용자경험 Ad hoc /Rendezvous Confer ences 환경제공 여유포트의관리 자동브리지선택 자동케스케이딩 회의구성을위한단일프로비저닝 API 엔진 구축형 CMR 을위한메인 API 엔진 52

Conductor 기본이해 기본설정로직의이해 Conductor Virtual IP Address Location Conference Alias Conference Template Service Preference #1 Pool TS/MCU TS/MCU (can be used in multiple SP s) #2 Pool TS/MCU TS/MCU TS/MCU TS/MCU Prioritized 53

Conductor Cascading 디자인 TelePresence Server Cascading 개요 Conductor 는일반 MCU 와같은컨셉의 Cascading 지원 ( 단일스트리밍 Cascading) NOTE: Participant 각단말은각단말에연결된 TP 서버에따라서로다른이미지를볼수있음 발언자 발언자 Cascade Conference Call 54

Conductor Cascading 디자인 Conductor 에서구성하는법 최대 Cascading 링크수설정 ( 결국 primary TP Server 에가용한리소스가있어야함 ) 55

Conductor Cascading 디자인 Conductor 구성하기 Conductor 에아래와같이다중풀과다중브리지가설정이되어야함 56

Conductor Cascading 디자인 Cascading 디자인 모든 cascade 링크는템플릿구성과상관없이최대 720p@30 해상도로연결, 콘텐트해상도는템플릿에활성화된해상도로구성 ( 템플릿에 Content Quality 쪽에리소스할당 ) 마스터슬레이브구조로각서버에서각각리소스할당이필요함 회의중에자료공유는어떤단말에서도가능 각단말은자기가연동된 TP 서버의최대해상도는볼수있음 Call Control Scalable Conference Call Master Cascade over SIP session TelePresence Conductor Cascade over SIP session 57

Conductor Cascading 디자인 구성을위한기본제품군 최소소프트웨어버전 Product TelePresence Conductor Software Version XC2.4 TelePresence Server 4.0(1.57) IMPORTANT: TPS 장비군끼리만 Cascading 가능, MCU TPS 간케스케이딩지원안함 Call Control (UCM/VCS) Scalable Conference Call Cascade over SIP session Master TelePresence Conductor Cascade over SIP session 58

Conductor Cascading 디자인 Cascading 콜플로우 UA-1 UA-2 UA-6 Call Control (VCS as example) TelePresence Conductor Conf. Alias: 175(\d{3})@.* Conf. Name: MTG\1 TPS-1 TPS-2 B2BUA 최초참석자회의참석 INVITE with SDP 175100@ciscotp.com CSeq: 100 INVITE 100 Trying CSeq: 100 INVITE INVITE with SDP 175100@ciscotp.com CSeq: 100 INVITE 100 Trying CSeq: 100 INVITE XML RPC request Method=flex.conference.create Chair URL: 88810039 Guest URL: 888 10040 ConfName: MTG100 59

Conductor Cascading 디자인 Cascading 콜플로우 UA-1 UA-2 UA-6 Call Control (VCS as example) TelePresence Conductor Conf. Alias: 175(\d{3})@.* Conf. Name: MTG\1 TPS-1 Chair URL: 88810039 Guest URL: 88810040 TPS-2 B2BUA INVITE with SDP 88810039@172.16.1.94 CSeq: 100 INVITE 100 Trying CSeq: 100 INVITE Note: 172.16.1.94 is TPS1 IP a ddress 180 Ringing CSeq: 100 INVITE 200 OK with SDP CSeq: 100 INVITE 180 Ringing CSeq: 100 INVITE 200 OK with SDP CSeq: 100 INVITE 180 Ringing CSeq: 100 INVITE 200 OK with SDP CSeq: 100 INVITE ACK CSeq: 100 ACK ACK CSeq: 100 ACK ACK CSeq: 100 ACK Call Established 61

Conductor Cascading 디자인 Cascading 콜플로우 UA-1 UA-2 UA-6 Call Control (VCS as example) TelePresence Conductor Conf. Alias: 175(\d{3})@.* Conf. Name: MTG\1 TPS-1 Chair URL: 88810039 Guest URL: 88810040 TPS-2 B2BUA 두번째참석자참석 INVITE with SDP 175100@ciscotp.com CSeq: 100 INVITE 100 Trying CSeq: 100 INVITE INVITE with SDP 175100@ciscotp.com CSeq: 100 INVITE 100 Trying CSeq: 100 INVITE INVITE with SDP 88810039@172.16.1.94 CSeq: 100 INVITE 100 Trying CSeq: 100 INVITE Note: 172.16.1.94 is TPS1 IP a ddress 180 Ringing CSeq: 100 INVITE 200 OK with SDP CSeq: 100 INVITE 180 Ringing CSeq: 100 INVITE 200 OK with SDP CSeq: 100 INVITE 180 Ringing CSeq: 100 INVITE 200 OK with SDP CSeq: 100 INVITE ACK CSeq: 100 ACK 63

Conductor Cascading 디자인 Cascading 콜플로우 UA-1 UA-2 UA-6 Call Control (VCS as example) TelePresence Conductor Conf. Alias: 175(\d{3})@.* Conf. Name: MTG\1 TPS-1 Chair URL: 88810039 Guest URL: 88810040 TPS-2 B2BUA Resource occupied 추가참석자도참석시도 INVITE with SDP 175100@ciscotp.com CSeq: 100 INVITE 100 Trying CSeq: 100 INVITE INVITE with SDP 175100@ciscotp.com CSeq: 100 INVITE 100 Trying CSeq: 100 INVITE XML RPC request Method=flex.conference.create Chair URL: 88810043 Guest UR L: 88810044 ConfName: MTG100 66

Conductor Cascading 디자인 Cascading 콜플로우 UA-1 UA-2 UA-6 Call Control (VCS as example) TelePresence Conductor Conf. Alias: 175(\d{3})@.* Conf. Name: MTG\1 TPS-1 Chair URL: 88800039 Guest URL: 88800040 TPS-2 Chair URL: 88810043 Guest URL: 88810044 B2BUA Resource occupied XML RPC request Method=flex.participant.create URL: 88810045 cascaderole: cascadeslave Request Response XML RPC request Method=flex.participant.create remoteaddress: 88810045@172.16.1.93 cascaderole: cascademaster Request Response Note: 172.16.1.93 is TPS2 IP a ddress 68

Conductor Cascading 디자인 Cascading 콜플로우 UA-1 UA-2 UA-6 Call Control (VCS as example) TelePresence Conductor Conf. Alias: 175(\d{3})@.* Conf. Name: MTG\1 TPS-1 Chair URL: 88800039 Guest URL: 88800040 TPS-2 Chair URL: 88810043 Guest URL: 88810044 Cascade URL: 88810045 B2BUA Resource occupied XML RPC request Method=flex.participant.create URL: 88810045 cascaderole: cascadeslave Request Response XML RPC request Method=flex.participant.create remoteaddress: 88810045@172.16.1.93 cascaderole: cascademaster Request Response 캐스케이딩링크연결 This call log only available on log from TPS not on diagnostic log fr om TP Conductor INVITE with SDP 88810043@172.16.1.93 CSeq: 1 INVITE 100 Trying CSeq: 1 INVITE 180 Ringing CSeq: 1 INVITE 69

Conductor Cascading 디자인 Cascading 콜플로우 UA-1 UA-2 UA-6 Call Control (VCS as example) TelePresence Conductor Conf. Alias: 175(\d{3})@.* Conf. Name: MTG\1 TPS-1 Chair URL: 88800039 Guest URL: 88800040 TPS-2 Chair URL: 88810043 Guest URL: 88810044 Cascade URL: 88810045 B2BUA Resource occupied 200 OK with SDP CSeq: 1 INVITE ACK CSeq: 100 ACK Cascade Call Established Audio/Video Payload 추가참석자는 TPS-2 로연결 180 Ringing CSeq: 100 INVITE 200 OK with SDP CSeq: 100 INVITE 180 Ringing CSeq: 100 INVITE 200 OK with SDP CSeq: 100 INVITE INVITE with SDP 88810043@172.16.1.94 CSeq: 100 INVITE 100 Trying CSeq: 100 INVITE 180 Ringing CSeq: 100 INVITE 200 OK with SDP CSeq: 100 INVITE ACK CSeq: 100 ACK 70

Conductor 와웹엑스연동 구축형 CMR 에웹엑스솔루션연동하기 구축형 CMR 에개인화된 CMR Hybrid 형태링크생성 구축형 CMR 포털에서정의된 API 를호출 최소소프트웨어버전 제품 버전 TelePresence Conductor XC3.0 TelePresence Management Suite 14.6 TMS Provisioning Extension 1.4 76

Conductor 웹엑스스케줄링 구성의이해 ( 사용자가웹엑스연동클릭으로시작 ) 웹엑스가 https://<tms-fqdn>/tmsagnet/tmsportal/<webexid> 링크를통해 TMS 통해 Call WebEx Cloud Corporate Network WebEx Client 1. Call https://<tms-fqdn>/tmsagent/tmsportal/<webexid> TMS DMZ Internet VCS-E VCS-C Conference Bridge TelePresence Conductor 77

Conductor 웹엑스스케줄링 구성의이해 TMS 가웹엑스클라우드로회의요청 WebEx Cloud Corporate Network WebEx Client 2. Instant WebEx Conference Request TMS DMZ Internet VCS-E VCS-C Conference Bridge TelePresence Conductor 78

Conductor 웹엑스스케줄링 구성의이해 웹엑스클라우드서버는새로운회의 ID 를 TMS 로전송 (URL, i.e. 123456789@mydomain.webex.com) WebEx Cloud Corporate Network WebEx Client 3. Response with WebEx conference ID 123456789.mydomain.webex.com TMS DMZ Internet VCS-E VCS-C Conference Bridge TelePresence Conductor 79

Conductor 웹엑스스케줄링 구성의이해 웹엑스클라이언트는리다이렉트를 (302 redirect) 통한호출요청에응답 (i.e. 123456789.mydomain. WebEx Cloud webex.com) Corporate Network WebEx Client 4. 302 Redirect to 123456789.mydomain.webex.com TMS DMZ Internet VCS-E VCS-C Conference Bridge TelePresence Conductor 80

Conductor 웹엑스스케줄링 구성의이해 웹엑스클라이언트는자동으로리다이렉트 (ex : https://123456789.mydomain.webex.com) WebEx Cloud Corporate Network WebEx Client 5. Call https://123456789.mydomain.webex.com TMS DMZ Internet VCS-E VCS-C Conference Bridge TelePresence Conductor 81

Conductor 웹엑스스케줄링 구성의이해 TMS 가 Conductor 를통한브리지연결요청 WebEx Cloud Corporate Network WebEx Client 6. Create scheduled conference by sending factory.conferencecreate TMS DMZ Internet VCS-E VCS-C Conference Bridge TelePresence Conductor 82

Conductor 웹엑스스케줄링 구성의이해 Conductor 가회의생성 WebEx Cloud Corporate Network WebEx Client TMS DMZ 7. Create new conference by sending flex. conference.create Internet VCS-E VCS-C Conference Bridge TelePresence Conductor 83

Conductor 웹엑스스케줄링 구성의이해 Conductor 가 TMS 로회의생성에요청에응답 WebEx Cloud Corporate Network WebEx Client 9. Request response TMS DMZ Internet VCS-E VCS-C Conference Bridge TelePresence Conductor 84

Conductor 웹엑스스케줄링 구성의이해 웹엑스연결정보를 Conductor 에전달 WebEx Cloud Corporate Network WebEx Client 10. Send WebEx conference information by sending factory.webex.add TMS DMZ Internet VCS-E VCS-C Conference Bridge TelePresence Conductor 85

Conductor 웹엑스스케줄링 구성의이해 Conductor 가회의브리지에웹엑스연결요청을보냄 WebEx Cloud Corporate Network WebEx Client TMS DMZ 11. Add WebEx as dial-out participant by s ending flex.participant.create Internet VCS-E VCS-C Conference Bridge TelePresence Conductor 86

Conductor 웹엑스스케줄링 구성의이해 회의브리지가 Conductor 에참석자요청에응답 WebEx Cloud Corporate Network WebEx Client TMS DMZ 12. Request response including participan t ID Internet VCS-E VCS-C Conference Bridge TelePresence Conductor 87

Conductor 웹엑스스케줄링 구성의이해 참석자요청을 TMS 에보냄 WebEx Cloud Corporate Network WebEx Client 13. Request response TMS DMZ Internet VCS-E VCS-C Conference Bridge TelePresence Conductor 88

Conductor 웹엑스스케줄링 구성의이해 최소한대의단말이회의브리지로연결 WebEx Cloud Corporate Network WebEx Client TMS DMZ 14. Dial-in Internet VCS-E VCS-C Conference Bridge TelePresence Conductor 89

Conductor 웹엑스스케줄링 구성의이해 웹엑스단말이웹엑스로연결 비디오참석자군이회의실에참가 WebEx Cloud Corporate Network WebEx Client TMS WebEx client on WebEx conference call (Media Route) DMZ Internet VCS-E VCS-C Conference Bridge TelePresence Conducto Dial-in device on conference bridge conference call r (Media Route) 90

Conductor 웹엑스스케줄링 구성의이해 회의브리지가웹엑스로다이얼아웃 123456789@mydomain.webex.com WebEx Cloud Corporate Network WebEx Client TMS DMZ 15. Dial out to WebEx conference, 123456789@my domain.webex.com Internet VCS-E VCS-C Conference Bridge TelePresence Conductor B2BUA 91

Conductor 웹엑스스케줄링 구성의이해 Conductor 를통해모든참석자가한회의실에접속 WebEx Cloud Corporate Network WebEx Client Media Route TMS Media Route DMZ Internet Media Route VCS-E VCS-C Conference Bridge TelePresence Conductor 92

3. 컨퍼런스패키지라이센스

텔레프레즌스서버라이센스 텔레프레즌스서버라이선스구조는포트기반의라이선스 최신소프트웨어에서오디오사용자용량이크게상승 밴드위스별해상도별풀 HD/HD/SD 를같이사용할경우 Optimized Conferencing 지원 (Conductor 필수 ) 94

새로운라이선스패키지 비디오인프라전반에대한번들을 SINGLE SKU 로오더가능 기존라이선스 Personal Multiparty Basic Minimum order: 25 hosts Personal Multiparty Advanced Minimum order: 25 hosts 회의스케줄링별도스크린라이센스 Ad-hoc only Ad-hoc, meet-me and/or Scheduled 최대해상도 Full HD (1080p30) HD (720p30) Single screen units ONLY 최대연결사이즈 Full HD (1080p30) Multiple screens 구매한라이선스수만큼 4 제한없음 ( 일반적인사용량으로계산, 다음 페이지참조 ) 라이선스포함 TelePresence Server TelePresence Server TelePresence Conductor TelePresence Server TelePresence Conductor TMS base Expressway Rich Media Session Expressway Lync Interop License Key 95

Multiparty 라이선스비교 라이선스제공 Personal Multiparty Basic 라이선스포함 : Personal Multiparty Advanced 라이선스포함 : 텔레프레즌스서버 최초 8 스크린라이선스 + 매 30 유저당 1 스크린라이선스제공 최초 11 스크린라이선스제공 + 매 15 유저당 1 스크린라이선스제공 (rounded up) Conductor** 1 Full Conductor License 2 Full Conductor Licenses Lync 연동 Expressway Rich Media Session (RMS E or C) 없음 없음 최초오더시 1 Lync 연동라이선스제공 + 매 300 유저당 1 추가의 Lync 라이선스제공 (rounded up) 최초 5 RMS 라이선스제공 + 매 15 유저당 1 RMS 라이선스제공 (rounded up) TMS 등록단말수 ** 없음최초오더시 25 단말등록라이선스제공 96

Multiparty 라이센스 As Easy as 1, 2, 3 단계 1 단말타입 (Jabber through Immersive) Personal use Shared System 단계 2 + + 라이선스 Personal Multiparty Advanc ed 나 Basic 단계 3 서버종류 Select Number of Servers 97

Summary 시스코의누구나언제어디서어떤단말이든다자간회의를할수있는 CMR(Collaboration Meeting Room) 솔루션지원 다자간회의인텔레프레즌스서버, 인프라오케스트레이션을하는 Conductor 의진화, 스케줄링서비스 TMS 및웹엑스와 CMR 연동까지다양한인프라솔루션을디자인할수있음 다자간회의솔루션을구매하는새로운방식 사용자기반 의라이선스제공 (PMP Advanced) 98

Thank You