配置CMS Edge示例

下載選項

  • PDF     (620.3 KB)
    在多種裝置上使用 Adobe Reader 檢視
已更新: 2024 年 3 月 22 日
文件 ID:221729

無偏見用語

本產品的文件集力求使用無偏見用語。針對本文件集的目的，無偏見係定義為未根據年齡、身心障礙、性別、種族身分、民族身分、性別傾向、社會經濟地位及交織性表示歧視的用語。由於本產品軟體使用者介面中硬式編碼的語言、根據 RFP 文件使用的語言，或引用第三方產品的語言，因此本文件中可能會出現例外狀況。深入瞭解思科如何使用包容性用語。

關於此翻譯

思科已使用電腦和人工技術翻譯本文件，讓全世界的使用者能夠以自己的語言理解支援內容。請注意，即使是最佳機器翻譯，也不如專業譯者翻譯的內容準確。Cisco Systems, Inc. 對這些翻譯的準確度概不負責，並建議一律查看原始英文文件（提供連結）。

    簡介

    本文檔介紹如何配置思科Meeting Server (CMS)邊緣。

    必要條件

    需求

    思科建議您瞭解以下CMS 3.X元件：

    • Webbridge 3
    • 呼叫
    • C2W
    • 防火牆
    • Turn伺服器

    採用元件

    本文中的資訊係根據以下軟體和硬體版本：

    • CMS3.X開放式虛擬裝置(OVA)
    • Chrome瀏覽器122.0.6261.112
    • Firefox瀏覽器123.0.1 (20240304104836)

    本文中的資訊是根據特定實驗室環境內的裝置所建立。文中使用到的所有裝置皆從已清除（預設）的組態來啟動。如果您的網路運作中，請確保您瞭解任何指令可能造成的影響。

    設定

    預先設定

    1. 配置網路時間協定(NTP)伺服器：

    最好在CMS Edge和核心伺服器上配置相同的NTP伺服器。

    2. 配置域名伺服器(DNS)：

    1. 為CMS Core伺服器配置內部DNS（內部DNS CMS Edge A記錄指向CMS Edge內部IP地址；如果不可能，則必須配置兩個CMS Edge A記錄，一個指向CMS內部IP地址，另一個指向外部IP地址）。
    2. 為CMS邊緣伺服器配置外部DNS。外部DNS A CMS記錄指向CMS邊緣的外部IP地址。

    3. CMS Core使用內部CMS Edge A記錄進行連線。

    4. 公共使用者透過公共IP地址訪問CMS Edge。

    5. 使用者域：cms.demo：

    a. CMS Edge的記錄：

    • edge.cms.demo (internal user login with this A record)
    • edge.cms.demo (public user also use same A record from internet, you could specify the different external A record)

      •

    b. CMS Core之紀錄：

    core.cms.demo

    6. 取得CMS核心與邊緣伺服器認證：

    a.製作認證

    • cmscore-fullchain.cer （所有服務都涉及實驗中的全鏈證書，您也可以涉及伺服器證書）
    • cmsedge-fullchain.cer （所有服務都涉及實驗中的全鏈證書，您也可以涉及伺服器證書）
      •

    b.產生兩台伺服器的全鏈式認證。

    • cmscore-fullchain.cer （此憑證包含根憑證）
    • cmsedge-fullchain.cer （此憑證包含根憑證）
      •

    網路圖表

    CMS功能

    CMS元件

    CMS核心和邊緣配置

    1. 啟用CMS核心伺服器相關服務。

    a.配置訊號網路。

    啟用網路介面：

    ipv4 a add 10.124.56.224/24 10.124.56.1

    b.啟用Callbridge元件。

    callbridge listen a
    callbridge certs core.key cmscore-fullchain.cer
    callbridge trust c2w cmsedge-fullchain.cer (if not, which result in WebRTC failed)
    callbridge enable

    2. 啟用CMS Edge伺服器相關服務：

    a.配置兩個網路介面。

    附註圖示

    注意： 'b'是公共網路介面，a是內部網路介面。
    • 啟動網路a、b
    • 配置預設網關為b（它是公共網路介面）
    • 配置內部網關a
         
      •  
    ipv4 a add 10.124.144.80/24 10.124.144.1
    ipv4 b add 10.124.42.112/24 10.124.42.1
    ipv4 b default

    b.啟動車削元件。

    turn certs edge.key cmsedge-fullchain.cer
    turn listen a b
    turn credentials <username> <password> <cms.demo> (cms.demo is actual domain deployment)
    turn public-ip x.x.x.x
    turn tls 447
    turn enable
    附註圖示

    附註： 

    1. x.x.x.x 是NAT對映公有IP地址；如果沒有NAT對映，則不需要配置此步驟。
    2. 埠可以自行定義，請參閱相關CMS指南。
      3.

    c.啟用webbridge3元件。

    webbridge3 https certs cmsedge.key cmsedge-fullchain.crt (cmsedge-fullchain.crt ,please refer to CMS fullchain document)
    webbridge3 https listen b:445 (b is public network interface , this step just provide public users WebRTC service)
    webbridge3 https listen a:445 b:445 (this step could provide both internal and external WebRTC service, but need to edge.cms.demo has two A records on internal/external DNS servers.)
    webbridge3 c2w certs edge.key cmsedge-fullchain.crt
    webbridge3 c2w listen a:6000 (a is internal network interface, 6000 is self-defined port which need to keep the same with the below Webbridge URL)
    webbridge3 c2w trust cmscore-fullchain.cer (if no this step, result in WebRTC failed)
    webbridge3 enable

    3. 建立相關元件之間的通訊。

    a. Callbridge <—> Turn（公共媒體服務）
    b. Callbridge <—> WebBridge3（WebRTC服務） 

    在CMS核心上配置turn和webbridge3：
    a.配置Callbridge和Turn之間的連線，並啟用公共媒體服務。
    登入Webadmin GUI，導航至Configuration > General。

    TURN的配置

    b.配置Callbridge和Webbridge3之間的連線，並啟用WebRTC服務。
    透過CMS上的API建立Webbridge，然後增加C2W連線，例如c2w://edge.cms.demo:6000(埠必須與Webbridge3服務配置保持一致)。

    C2W配置

    restart Callbridge component and apply all configuration
    callbridge restart (go to CLI)

    4. 啟用防火牆功能並停用公共22埠(ssh)。

    firewall a default allow ( a is the external/public network interface)
    firewall a deny 22
    firewall a enable

    驗證

    1. 驗證所有服務是否在CMS Core和Edge上運行：

    CMS核心服務狀態：

    CMS> webadmin Enabled : true TLS listening interface : a TLS listening port : 443 Key file : core.key Certificate file : cmscore-fullchain.cer HTTP redirect : Disabled STATUS : webadmin running CMS> callbridge Listening interfaces : a Preferred interface : none Key file : core.key Certificate file : cmscore-fullchain.cer Address : none C2W trusted certs : cmsedge-fullchain.cer Callbridge cluster trusted certs : none Callbridge trust branding certs : none UCM trusted certs : none UCM verification mode : disabled IMPS trusted certs : none IMPS verification mode : disabled WC3 JWT Expiry in hours : 24

    CMS Edge服務狀態：

    CMS> webbridge3 Enabled : true HTTPS listening ports and interfaces : a:445 b:445 HTTPS Key file : edge.key HTTPS Full chain certificate file : cmsedge-fullchain.cer HTTPS Frame-Ancestors : none HTTP redirect : Disabled C2W listening ports and interfaces : a:6000 C2W Key file : edge.key C2W Full chain certificate file : cmsedge-fullchain.cer C2W Trust bundle : cmscore-fullchain.cer Meetingapps address : none Meetingapps port : none Audio priority flag : Enabled Beta options : none CMS> turn Enabled : true Username : admin Password : Cisco.123 Short term credentials : disabled Shared secret : none Realm : cms.demo Public IP : none High Capacity Mode : enabled Relay address : 10.124.144.80 TLS port : 447 TLS cert : cmsedge-fullchain.cer TLS key : edge.key TLS bundle : none Listen interface a Listen interface b

    2. 驗證webrtc登入狀態並加入會議：

    Webrtc應用登入網頁

    Webrtc應用參與者已加入呼叫

    疑難排解

    1. CMS Edge：您可以看到webrtc參與者「Thomas」加入呼叫。參與者ID：fcfe42f4-ac94-4ab2-a14a-f4165ec960a7。

    可在CMS核心日誌檔案中找到此參與者ID。

    Feb 23 09:02:21.588 local0.info CMS client_backend: INFO : WebApp Audit : Session: a77d94b1-ba12-4e4e-8f3e-86b3e9c1de8f : Participant Thomas performed action of join call
    Feb 23 09:02:21.599 local7.info CMS 3b8086e0e5a0 wb3_frontend: [Join call:fcfe42f4-ac94-4ab2-a14a-f4165ec960a7] 10.140.248.52 - - [23/Feb/2024:09:02:21 +0000] status 200 "POST /api/join HTTP/1.1" bytes_sent 1003 http_referer "https://edge.cms.demo:445/" http_user_agent "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:122.0) Gecko/20100101 Firefox/122.0" toupstream 192.0.2.2:9000: upstream_response_time 0.008 request_time 0.007 msec 1708678941.598 upstream_response_length 1027 200
    Feb 23 09:02:21.633 user.info CMS client_backend: INFO : WebSocket : Got authenticated JWT for guest1573064743 callbridge 320d02c3-7af5-4e4f-b51c-9a7a4dc0b8b9 call 04704220-95a8-4d36-a6ec-3d4d789d9250 participant fcfe42f4-ac94-4ab2-a14a-f4165ec960a7 tracing 0

    Webrtc參與者離開呼叫：

    Feb 23 09:02:37.982 local0.info CMS client_backend: INFO : WebApp Audit : Session: a77d94b1-ba12-4e4e-8f3e-86b3e9c1de8f : Participant Thomas(fcfe42f4-ac94-4ab2-a14a-f4165ec960a7) performed action of leave call

    2. CMS核心：紫線是會議ID，當其他參與者加入此會議時，有相同的會議ID。藍線是特定的使用者ID：guest1573064743。

    Feb 23 09:02:21.594 user.info CMS host:server: INFO : guest login request 1450660605: resolution in progress
    Feb 23 09:02:21.594 user.info CMS host:server: INFO : guest login request 1450660605: call ID lookup scheduled
    Feb 23 09:02:21.594 user.info CMS host:server: INFO : guest login request 1450660605: resolution in progress
    Feb 23 09:02:21.597 user.info CMS host:server: INFO : guest login request 1450660605: credential storage scheduled (queue length: 1)
    Feb 23 09:02:21.597 user.info CMS host:server: INFO : created guest account with user ID "guest1573064743"
    Feb 23 09:02:21.597 user.info CMS host:server: INFO : guest login request 1450660605: credential storage executed
    Feb 23 09:02:21.597 user.info CMS host:server: INFO : guest login request 1450660605: credential storage in progress
    Feb 23 09:02:21.598 user.info CMS host:server: INFO : guest login request 1450660605: successfully stored credentials
    Feb 23 09:02:21.598 user.info CMS host:server: INFO : instantiating user "guest1573064743"
    Feb 23 09:02:21.598 user.info CMS host:server: INFO : conference db0fafc3-ad47-43bd-bcbd-47886416451b: locked due to lack of lock consensus
    Feb 23 09:02:21.598 user.info CMS host:server: INFO : conference db0fafc3-ad47-43bd-bcbd-47886416451b: lock state has changed to locked
    Feb 23 09:02:21.598 user.info CMS host:server: INFO : API "9999" Space GUID: 58ef98d1-5181-4e63-a386-4b60597be7e4 <--> Call Correlator GUID: 5d031ae1-1c94-44ec-afd4-fa0e76230e3f<--> Internal GUID: db0fafc3-ad47-43bd-bcbd-47886416451b
    Feb 23 09:02:21.598 user.info CMS host:server: INFO : unable to apply logo (space '9999') -- no license
    Feb 23 09:02:21.599 user.info CMS host:server: INFO : conference db0fafc3-ad47-43bd-bcbd-47886416451b: lock state has changed to unlocked
    Feb 23 09:02:21.599 user.info CMS host:server: INFO : API call leg fcfe42f4-ac94-4ab2-a14a-f4165ec960a7 in call db0fafc3-ad47-43bd-bcbd-47886416451b (API call 04704220-95a8-4d36-a6ec-3d4d789d9250)
    Feb 23 09:02:21.599 user.info CMS host:server: INFO : conference db0fafc3-ad47-43bd-bcbd-47886416451b has control/media GUID: bf286660-6e5d-403f-8926-514d385dad3c
    Feb 23 09:02:21.599 user.info CMS host:server: INFO : conference db0fafc3-ad47-43bd-bcbd-47886416451b named "9999"
    Feb 23 09:02:21.601 user.info CMS host:server: INFO : new session created for user "guest1573064743"
    Feb 23 09:02:21.603 local0.info CMS postgres[54639]: [6-1] 2024-02-23 09:02:21.603 UTC [54639] LOG: could not send data to client: Broken pipe
    Feb 23 09:02:21.603 local0.err CMS postgres[54639]: [7-1] 2024-02-23 09:02:21.603 UTC [54639] FATAL: connection to client lost
    Feb 23 09:02:21.768 user.info CMS host:server: INFO : call 11: allocated for guest1573064743 / "Thomas" conference participation (Firefox)
    Feb 23 09:02:21.768 user.info CMS host:server: INFO : call 11: configured - API call leg fcfe42f4-ac94-4ab2-a14a-f4165ec960a7
    Feb 23 09:02:21.768 user.info CMS host:server: INFO : call 11: ActiveControlState change, unknown -> unknown
    Feb 23 09:02:21.769 user.info CMS host:server: INFO : call 11: setting up combined RTP session for DTLS (combined media and control)
    Feb 23 09:02:21.770 user.info CMS host:server: INFO : call 11: ActiveControlState change, unknown -> inactive
    Feb 23 09:02:21.770 user.info CMS host:server: INFO : call 11: ActiveControlState finality change (inactive, final=1)
    Feb 23 09:02:21.770 local0.info CMS host:server: INFO : participant "guest1573064743" joined space 58ef98d1-5181-4e63-a386-4b60597be7e4 (9999)
    Feb 23 09:02:21.770 user.info CMS host:server: INFO : participant "guest1573064743" (fcfe42f4-ac94-4ab2-a14a-f4165ec960a7) joined conference db0fafc3-ad47-43bd-bcbd-47886416451bvia WB3
    Feb 23 09:02:21.772 user.info CMS host:server: INFO : call 11: starting DTLS combined media negotiation (as initiator)

    Webrtc使用者離開呼叫：guest1573064743「保留空間ID」：58ef98d1-5181-4e63-a386-4b60597be7e4 (9999)。

    Feb 23 09:02:37.943 user.info CMS host:server: INFO : user "guest1573064743": deactivating due to session resource teardown
    Feb 23 09:02:37.943 user.info CMS host:server: INFO : call 11: tearing down ("guest1573064743" conference media)
    Feb 23 09:02:37.943 user.info CMS host:server: INFO : call 11: destroying API call leg fcfe42f4-ac94-4ab2-a14a-f4165ec960a7
    Feb 23 09:02:37.943 local0.info CMS host:server: INFO : participant "guest1573064743" left space 58ef98d1-5181-4e63-a386-4b60597be7e4 (9999)
    Feb 23 09:02:37.943 user.info CMS host:server: INFO : removing guest account 'guest1573064743' (name 'Thomas') on call drop
    Feb 23 09:02:37.943 user.info CMS host:server: INFO : destroying guest account with user ID "guest1573064743"
    Feb 23 09:02:37.944 user.info CMS host:server: INFO : conference bf286660-6e5d-403f-8926-514d385dad3c destroyed

    相關資訊

    修訂記錄

    修訂 發佈日期 意見
    1.0
    22-Mar-2024
    初始版本
    TAC Authored

    由思科工程師貢獻

    • Thomas Dong
      Cisco TAC Engineer
    • Foster Song
      Cisco TAC Engineer

    這份文件是否有所幫助？

    Feedback意見

    讓思科協助您

    本文件適用於這些產品