Skip to content

Meeting Domain

Eureka

Plugin: Meeting Zone

  • Zone Type: Meeting Zone
  • Server Type: Meeting CB servers
  • Target: CB
  • Sample cluster: ib
  • Cases: 1. Test server is MZM server 1. MCT ping MZM to get CB server address. if got return CB server address, test pass. 2. Test server is CB server 1. MCT get the smac key from J2EE Web server 3. MCT creates conference on CB server. 4. MCT creates sessions on CB server. 5. Verify conference 6. Close the meeting.
  • Wiki is HERE
  • FAQ is HERE

Plugin: Sub Meeting Zone

  • Zone Type: Sub Meeting Zone
  • Server Type: Sub Meeting CB Server
  • Target: CB
  • Smaple cluster: ED1_NAM_GDM
  • Cases: 1. MCT get the smac key from Web server. 2. Get CB server address from MZM 1. MCT ping Top MZM to get Top CB server address 2. MCT ping Sub MZM to get Sub CB server address. 3. MCT call Sub CB server join conference. 4. Close the meeting.
  • Wiki is HERE
  • FAQ is HERE

Monitor.exe: Remote Agent Zone

  • Zone Type: Remote Agent Zone
  • Server Type: RA Server
  • Target: RA Server
  • Sample cluster: ib
  • Cases: 1. register a host on site 2. get ticket from site 3. establish with agent server
  • Wiki is HERE

Moniotor.exe: TP Gateway Zone

  • Zone Type: TP Gateway Zone
  • Server Type: TP Gateway Server
  • Test Case: 1. MCT get smac and audio ticket for SIS or KM (T30 web server provide one api for MCT calling to get the Smac or ticket). 2. According appoint MZMList/MCC construct URL 3. Visit this URL and check the result

Plugin: Web Zone

  • Zone Type: Web Zone
  • Server Type: WWP Server
  • Sample: TSJ100
  • Case: 1. Connectivity check on WWP server 2. if backup WWP server configured, check as well 3. Call WWP API to add confid to WebDB 4. Start meeting/join meetig 5. Get ConfID from WWP server 6. Delete ConfID from WWP 7. Stop meeting
  • Wiki is HERE

Health Check (CB)

  • Target Server Type: CB servers
  • Sample URL: http://eabcb382.webex.com:8081/?cmd=CheckHealth&parameter=km

Health Check (WWP)

  • Target Server Type: WWP
  • Sample URL: http://eabwwp101.webex.com:8081/?cmd=CheckHealth

Port Check (CB)

  • Target Server Type: CB VIPs
  • Test Type: - port: 443 - port: 80

MMP

Plugin: MMP

  • Zone Type: mmp
  • test type: session creation
  • target: mcs
  • Test cases: 1. generate security key by j2ee 2. Visit MCS server IP based on existing MCT server IP configuration 3. Start 3 type sessions(processes) at same time (VOIP or Hybrid) 4. AS/VOIP Session Monitoring 1. AS(High FPS) join session 2. VOIP(Voice over Internet Protocol) join session 5. AB/Hybrid VoIP Session Monitoring 1. Start a Telephony Meeting 2. AB(Audio Broadcasting) join session check (by default every 4 times to test) 3. Hybrid VOIP(PSTN + VoIP) join session check 6. wait at most 2 mins for responses in different ports for all sessions.

Health Check (MCS)

  • Target Server Type: MCS
  • Sample URL: http://{mcs_server_ip/hostname}:8081/?cmd=CheckHealth

Health Check (MCC)

  • Target Server Type: MCC
  • Sample URL: http://{mcc_server_ip/hostname}:8081/?cmd=Status

Port Check (MCS)

  • Target Server Type: MCS
  • Test Types: - port 443 - Cert Expiration(15 days ahead by default) - TCP Port 5004 (optional)
  • Cases: 1. MCT API/GPI return server list under PoolName/ClusterName 2. Check all servers on specified ports
  • Tips: PortMonitor is only for telnet on individual servers.
  • TODO: PoolPortCheck MCSPoolPortCheck if deprecated, pending on PAPV verification.

CME

Plugin: UCREMonitoring

  • Zone Type:
  • Cases: 1. MCT Caller send a test call to a special Huron Number to a suitable UCRE i-Cusp address; 2. The test call travels through UCRE(i-Cusp, cube, e-Cusp) and reach appropriate PSTN SP / Carrier; 3. PSTN SP Trunk identifies the call should go to Huron, then send the call back to UCRE e-Cusp; 4. The test call travels through UCRE(e-Cusp, cube) and reach i-Cusp; 5. UCRE i-Cusp identifies this special Huron number a MCT test number, and send the call to MCT callee; 6. MCT Callee got the call, answer it and call signal loop established;

    7. MCT Caller send some testing media content after it received 200 OK from i-Cusp, and then BYE; 8. MCT Callee write the call information into a distinguished disk location after it received BYE from i-Cusp; 9. After a while, MCT Caller sends a http/get request of a distinguished location to retrieve the test call information; 10. MCT Caller check the test call information by comparing "Carrier IC", "Call Direction", "Cisco Srvc Code". - Wiki is HERE

Plugin: tp-meeting/sip-proxy

  • Zone Type: tp-meeting
  • Server Type: sip-proxy
  • Cases: 1. creating a tp-meeting by meeting centre web api 2. get meeting information by meeting centre web api 3. according meeting info to communication with CUSP, setup audio session and slides video session by sip protocol 4. if the audio and slides video setup ok, then receive rtp packets one minute 5. judge the session setup result and rtp received ratio(not less than 95%)
  • Wiki is HERE
  • FAQ is HERE

Plugin: tp-meeting/vmr-sip(lync)-proxy

  • Zone Type: tp-meeting
  • Server Type: vmr-sip-proxy

Plugin: tp-meeting/cmr-connective

  • Zone Type: tp-meeting
  • Server Type: cmr-connective
  • Cases: 1. Query DNS SRV 2. Start to schedule meeting and get meeting info 3. Start to simulate TP start the meeting 4. Check conference and host status : ConfStatus:ConfOpen, HostStatus:HostJoined. if not these status , start meeting failed
    5. Start to simulate Phone join the meeting 6. According send attendee id and in 30 seconds no terminate to judge join success or not(attend id is hostkey?) 7. Start test audio connective between TP and Phone 8. TP send test audio data and receive in one minutes 9. Phone send test audio data and receive in one minutes 10. Check TP and Phone receive valid RTP data percent , less than 95% will alert 11. Terminate TP and Phone call
  • Wiki is HERE

Plugin: CMRPresence

  • Zone Type: SparkCallInCMR
  • Server Type: SparkJoinMeeting
  • Cases: 1. Call site URLAPI to schedule meeting and get meeting info(docshow2.0). 2. Simulate webex client host meeting. 3. Simulate spark client join meeting. 4. Wait 60 seconds to check spark client still is join conference, this is to avoid spark client joined and auto leave conference shortly. 5. Start to expel spark client from meeting. 6. Check spark client is LEFT conference or conference is INACTIVE in spark.
  • Wiki is HERE

Plugin: SparkCallinCMR

  • Cases: 1. Scheduling test meeting from given CMR meeting site; 2. Creating test user, get user token by visiting CI site; 3. Register test user into spark by visiting spark user api; 4. Register test device into spark by visiting spark wdm api; 5. Join CMR test meeting by visiting spark locus api, and sending host-key by that; 6. Checking media QoS/packet loss rate by calculating received RTP packets from spark Linus server; 7. Checking test meeting status from given CMR meeting site; 8. End the test meeting by spark locus service;

Plugin: sip-healthcheck

  • Zone Type: sip-healthcheck
  • Server Type: option-ping
  • Cases: 1. send sip option message without UA-ID to the target sip server or sip proxy server 2. check the target sip server or sip proxy server response message, if received "200 OK" response, test OK, else test failed. 3. support test target sip server or sip proxy server by UDP、TCP、TLS or there compose method . ? Test different protocol one by one? 4. for TLS protocol, add check certification expires date.
  • Wiki is HERE

Plugin: H323Healthcheck

  • Zone Type: h323
  • Server Type: healthcheck
  • Cases: 1. send GRQ message to test H323 service and waiting GCF response. 2. if no GCF response, test failed 3. if call port test selected. will send Q31-H225 setup to call port, waiting "call proceeding" response 4. if no "call proceeding" response, test failed. Else waiting "releaseComplete" message 5. if no "releaseComplete" message coming in, test failed. Else check error info. 6. if error info is "invalid number", test succeed, else test failed.
  • Wiki is HERE

Tahoe

Plugin: Telephone Number Zone

  • Zone Type: Telephone Number Zone
  • Server Type: Telephone Number Server
  • Sample: TSJ100
  • Case: 1. Open tele conf with TS address in zone 2. Dial out 3. Number received and answer the call 4. Drop the call.
  • Wiki is HERE

Plugin: Tel Zone

  • Zone Type: Tel Zone
  • Server Type: Java Telephony Server
  • Cases: - Basic Workflow: 1. create conference on TS server. 2. check if DTConfEvt_ConfOpenCfm received. - Workflow when enable NBR: 1. create conference on TS server. 2. check if DTConfEvt_ConfOpenCfm received. 3. callin by GIVR. 4. check if callin successfully. 5. start NBR recording. 6. check if NBR recording successfully(receive DTApp_SSREvent_NotifyFileInfo).
  • Zone Type: Tel Zone
  • Server Type: TSP Telephony Server
  • Cases: - Monitor TSP capacity 1. MCT send request to MPEmulator(64.68.122.191:8080) 2. MPEmulator simulate a MP adaptor which is configured to site: mct-tspmp-ai, the adaptorURL is mct.webex.com 3. this simulates MP adaptor will connect the VIP 62.109.210.20 TSP pool, port is 443 4. connect success then query status, if TSP response"capacity is heavy", tools will reconnection and the max try count is 18 5. return the TSP status to MCT - Monitor TSP open conference 1. create conference on TS server. 2. check if DTConfEvt_ConfOpenCfm received.
  • Wiki is HERE

Plugin: mpc

  • Zone Type: mpc
  • Server Type: mpc-mon
  • Cases 1. call sipp to set up the VOIP session to the monitor mpc. 2. according to the sip response to judge setup result. 3. check the return and transform to MCT plugin format return value
  • Wiki is HERE and HERE