READ Free Dumps For Cisco- 400-051
| Question ID 12973 | Which Call Admission Control mechanism is supported for the Cisco Extension Mobility
Cross Cluster solution?
|
| Option A | Location CAC
|
| Option B | RSVP CAC
|
| Option C | H.323 gatekeeper
|
| Option D | intercluster Enhanced Location CAC
|
| Option E | visiting cluster's LBM hub
|
| Correct Answer | B |
Explanation Explanation: Configuring extension mobility cross cluster (EMCC) is nothing you should take lightly. EMCC requires a lot of configuration parameters including the exporting and importing of each neighbor clusters X.509v3 digital certificates. EMCC is supported over SIP trunks only. Presence is another feature thats only supported over SIP trunks. If you want to be able to perform scalable Call Admission Control (CAC) in a distributed multi-cluster call processing model, you will need to point an H.225 or Gatekeeper controlled trunk to an H.323 Gatekeeper for CAC but if you want to support presence and EMCC between clusters and maintain CAC.
| Question ID 12974 | Which statement about what happens to incoming calls to a Cisco Unified Communications
Manager native call queue when no hunt members are logged in or registered is true?
|
| Option A | Calls are handled according to the Forward Hunt No Answer settings on the Hunt Pilot configuration page.
|
| Option B | Calls are handled according to the Not Available Hunt Option settings on the Line Group Configuration page.
|
| Option C | Calls are handled according to the Forward Hunt Busy settings on the Hunt Pilot configuration page.
|
| Option D | Calls are forward to the Forward Busy Calls To destination if configured; otherwise the calls are disconnected.
|
| Option E | Calls are handled according to the correspondent parameters under the Queuing section on the Hunt Pilot Configuration page
|
| Correct Answer | E |
Explanation Explanation: There are three main scenarios where alternate numbers are used: ✑ When queue is full ✑ When maximum wait time is met ✑ When no hunt members are logged in or registered When queue is full Call Queuing allows up to 100 callers to be queued per hunt pilot (the maximum number of callers allowed in queue on a hunt pilot page). Once this limit for new callers been reached on a particular hunt pilot, subsequent calls can be routed to an alternate number. This alternate number can be configured through the Hunt Pilot configuration page (through the Destination When Queue is Full settings). When maximum wait time is met Each caller can be queued for up to 3600 seconds per hunt pilot (the maximum wait time in queue). Once this limit is reached, that caller is routed to an alternate number. This alternate number can be configured through the Hunt Pilot configuration page (through the Maximum wait time in queue settings). When no hunt members are logged in or registered In a scenario where none of the members of the hunt pilot are available or registered at the time of the call, hunt pilot configuration provides an alternate number field (through the When no hunt members are logged in or registered settings) where calls can be routed. For Call Queuing, a hunt pilot member is considered available if that member has both deactivated do not disturb (DND) and logged into the hunt group. In all other cases, the line member is considered unavailable or logged off. Reference: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/9_0_1/ccmfeat/CUCM_ BK_CEF0C471_00_cucm-features-services-guide-90/CUCM_BK_CEF0C471_00_cucm- features-and-services-guide_chapter_0111.html