Cisco Implementing Cisco Collaboration Conferencing - 300-825무료 덤프문제 풀어보기
An engineer must configure Cisco Meeting Server integration to Cisco UCM. Which DNS A record must be configured to accomplish this goal?
정답: A
A company wants to keep conferencing resources isolated and local for a new branch. The branch has one administrator for both internal and external traffic. Which Cisco Meeting Server deployment should be used?
정답: D
In a cluster of Cisco Meeting Servers, one of the peer servers has the FQDN CMS1.local, and the web admin is running on 445. Which server address must be configured in the clustered Call Bridges page?
정답: A
Refer to the exhibit.
guest login request 562763450: resolution in progress
guest login request 562763450: call ID lookup scheduled
guest login request 562763450: resolution in progress
guest login request 562763450: credential storage scheduled (queue length: 1) created guest account with user ID "quest487660227" guest login request 562763450: credential storage executed guest login request 562763450: credential storage in progress guest login request 562763450: successfully stored credentials instantiating user "guest487660227" conference f5771a88-0f36-4b58-8dbd-934aaa579ebf: locked due to lack of lock consensus conference f5771a88-0f36-4b58-8dbd-934aaa579ebf: lock state has changed to locked API "3.0 Record Test Space" Space GUID: 71b4f99f-2365-4730-b3d9-d2d61505150c <--> Call Correlator GUID: 334b0c10-6f85-4760-97ab- conference f5771a88-0f36-4b58-8dbd-934aaa579ebf: lock state has changed to unlocked starting automatic recording (space "3.0 Record Test Space") API call leg 121d2c87-6940-4483-8d3d-71ff162947ba in call f5771a88-0f36-4b58b8dbd-934aaa579ebf (API call 5a0a7f49-78f8-46fd-add9-4a conference f5771a88-0f36-4b58-8dbd-934aaa579ebf has control/media GUID:
d7f2d940-c7d9-4421-8f13-7bf94756b08a
conference f5771a88-0f36-4b58-8dbd-934aaa579ebf named "3.0 Record Test Space" unable to start recording - recorder URI not configured new session created for user "guest487660227" call 49: allocated for guest487660227 "Web" conference participation call 49: configured - API call leg 121d2c87-6940-4483-8d3d-8d3d-71ff162947ba call 49: setting up combined RTP session for DTLS (combined media and control) participant "quest487660227" joined space 71b4f99f-2365-4730-b3d9-d2d61505150c (3.0 Record Test Space) participant "quest487660227" (121d2c87-6940-4483-8d3d-71ff162947ba) joined conference f5771a88-0f36-4b58-8dbd-934aaa579ebf via W call 49: starting DTLS combined media negotiation (as initiator) call 49: completed DTLS combined media negotiation invalid API operation - unhandleable URI /api/v1/recorders user "guest487660227": deactivating due to session resource teardown call 49: tearing down ("guest487660227" conference media) call 449: destroying API call leg 121d2c87-6940-4483-8d3d-71ff162947ba An administrator tries to implement a recording with a Cisco Meeting Server version 3.0 deployment. A separate VM is deployed and configured with the recorder service. During testing, it is discovered that the recording is failing, and the administrator collects logs.
Which configuration step should be completed?
guest login request 562763450: resolution in progress
guest login request 562763450: call ID lookup scheduled
guest login request 562763450: resolution in progress
guest login request 562763450: credential storage scheduled (queue length: 1) created guest account with user ID "quest487660227" guest login request 562763450: credential storage executed guest login request 562763450: credential storage in progress guest login request 562763450: successfully stored credentials instantiating user "guest487660227" conference f5771a88-0f36-4b58-8dbd-934aaa579ebf: locked due to lack of lock consensus conference f5771a88-0f36-4b58-8dbd-934aaa579ebf: lock state has changed to locked API "3.0 Record Test Space" Space GUID: 71b4f99f-2365-4730-b3d9-d2d61505150c <--> Call Correlator GUID: 334b0c10-6f85-4760-97ab- conference f5771a88-0f36-4b58-8dbd-934aaa579ebf: lock state has changed to unlocked starting automatic recording (space "3.0 Record Test Space") API call leg 121d2c87-6940-4483-8d3d-71ff162947ba in call f5771a88-0f36-4b58b8dbd-934aaa579ebf (API call 5a0a7f49-78f8-46fd-add9-4a conference f5771a88-0f36-4b58-8dbd-934aaa579ebf has control/media GUID:
d7f2d940-c7d9-4421-8f13-7bf94756b08a
conference f5771a88-0f36-4b58-8dbd-934aaa579ebf named "3.0 Record Test Space" unable to start recording - recorder URI not configured new session created for user "guest487660227" call 49: allocated for guest487660227 "Web" conference participation call 49: configured - API call leg 121d2c87-6940-4483-8d3d-8d3d-71ff162947ba call 49: setting up combined RTP session for DTLS (combined media and control) participant "quest487660227" joined space 71b4f99f-2365-4730-b3d9-d2d61505150c (3.0 Record Test Space) participant "quest487660227" (121d2c87-6940-4483-8d3d-71ff162947ba) joined conference f5771a88-0f36-4b58-8dbd-934aaa579ebf via W call 49: starting DTLS combined media negotiation (as initiator) call 49: completed DTLS combined media negotiation invalid API operation - unhandleable URI /api/v1/recorders user "guest487660227": deactivating due to session resource teardown call 49: tearing down ("guest487660227" conference media) call 449: destroying API call leg 121d2c87-6940-4483-8d3d-71ff162947ba An administrator tries to implement a recording with a Cisco Meeting Server version 3.0 deployment. A separate VM is deployed and configured with the recorder service. During testing, it is discovered that the recording is failing, and the administrator collects logs.
Which configuration step should be completed?
정답: B
Refer to the exhibit.
outgoing SIP TLS data to 10.0.101.111:5061 from 10.0.101.121:43332, size 5430:
BEGINNING OF MESSAGE
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/TLS 10.0.101.121:5061;branch=z9hG4bK6e7932e8ae287a80ee699eb04a6155a2 Call-ID: cf600c54-974c-48e5-92e2-95b1d4b9218f CSeq: 1199885731 INVITE Max-Forwards: 70 Contact: <sip:[email protected];transport=tls>;isFocus To: <sip:[email protected]> From: "CCNP Collaboration" <sip:[email protected]>;tag=73a834a850d8ed13 Replaces: [email protected];to-tag=1769141~ba2cc769-5032-4f8f-a864-9a51 Allow: INVITE, ACK, CANCEL, OPTIONS, INFO, BYE, UPDATE, REFER, SUBSCRIBE, NOTIFY, MESSAGE Supported: timer, X-cisco-callinfo Session-Expires: 1800 Min-SE: 90 User-Agent: Acano CallBridge
<SDP omitted>
END OF MESSAGE
incoming SIP TLS data from 10.0.101.111:5061 to 10.0.101.121:43332, size 402:
BEGINNING OF MESSAGE
SIP/2.0 403 Forbidden
Via: SIP/2.0/TLS 10.0.101.121:5061;branch=z9hG4bK6e7932e8ae287a80ee699eb04a6155a2 From: "CCNP Collaboration" <sip:[email protected]>;tag=73a834a850d8ed13 To: <sip:[email protected]>;tag=252834177 Date: Mon, 30 Nov 2020 18:25:12 GMT Call-ID: cf600c54-974c-48e5-92e2-95b1d4b9218f CSeq: 1199885731 INVITE Allow-Events: presence Server: Cisco-CUCM12.5 Content-Length: 0 END OF MESSAGE Some calls fail to connect after an engineer implements load balancing for a Cisco Meeting Server cluster. The engineer determines that if a call leaves Cisco UCM using the Cisco Meeting Server 1 SIP trunk, but the conference is already hosted on Cisco Meeting Server 2, then the call fails. If the call leaves Cisco UCM using the Cisco Meeting Server 2 SIP trunk, but the conference is already hosted on Cisco Meeting Server 1, then the call fails. What is the cause of the issue?
outgoing SIP TLS data to 10.0.101.111:5061 from 10.0.101.121:43332, size 5430:
BEGINNING OF MESSAGE
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/TLS 10.0.101.121:5061;branch=z9hG4bK6e7932e8ae287a80ee699eb04a6155a2 Call-ID: cf600c54-974c-48e5-92e2-95b1d4b9218f CSeq: 1199885731 INVITE Max-Forwards: 70 Contact: <sip:[email protected];transport=tls>;isFocus To: <sip:[email protected]> From: "CCNP Collaboration" <sip:[email protected]>;tag=73a834a850d8ed13 Replaces: [email protected];to-tag=1769141~ba2cc769-5032-4f8f-a864-9a51 Allow: INVITE, ACK, CANCEL, OPTIONS, INFO, BYE, UPDATE, REFER, SUBSCRIBE, NOTIFY, MESSAGE Supported: timer, X-cisco-callinfo Session-Expires: 1800 Min-SE: 90 User-Agent: Acano CallBridge
<SDP omitted>
END OF MESSAGE
incoming SIP TLS data from 10.0.101.111:5061 to 10.0.101.121:43332, size 402:
BEGINNING OF MESSAGE
SIP/2.0 403 Forbidden
Via: SIP/2.0/TLS 10.0.101.121:5061;branch=z9hG4bK6e7932e8ae287a80ee699eb04a6155a2 From: "CCNP Collaboration" <sip:[email protected]>;tag=73a834a850d8ed13 To: <sip:[email protected]>;tag=252834177 Date: Mon, 30 Nov 2020 18:25:12 GMT Call-ID: cf600c54-974c-48e5-92e2-95b1d4b9218f CSeq: 1199885731 INVITE Allow-Events: presence Server: Cisco-CUCM12.5 Content-Length: 0 END OF MESSAGE Some calls fail to connect after an engineer implements load balancing for a Cisco Meeting Server cluster. The engineer determines that if a call leaves Cisco UCM using the Cisco Meeting Server 1 SIP trunk, but the conference is already hosted on Cisco Meeting Server 2, then the call fails. If the call leaves Cisco UCM using the Cisco Meeting Server 2 SIP trunk, but the conference is already hosted on Cisco Meeting Server 1, then the call fails. What is the cause of the issue?
정답: A
What is one of the ways Cisco TMS redundancy is configured?
정답: B
An administrator configures a Call Bridge to record meetings. Which two configuration elements tell the Call Bridge where to find the recording server? (Choose two.)
정답: A,B