READ Free Dumps For Cisco- 400-051
| Question ID 12939 | Which three requirements must be met to share Enhanced Location Based Call Admission
Control bandwidth usage between clusters? (Choose three.)
|
| Option A | The Cisco Unified Communications Manager version must be 8.6 or higher.
|
| Option B | The location name must be the same on both clusters.
|
| Option C | SIP ICT must use the Shadow location.
|
| Option D | The Location Bandwidth Manager Service should be started on only two servers in each cluster.
|
| Option E | A Location Bandwidth Manager Hub Group must be created for each cluster.
|
| Option F | Links must be created to the Shadow location.
|
| Correct Answer | B,C,E |
Explanation Explanation: Recommendations and Design Considerations for Unified CM Session Management Edition Deployments All leaf clusters that support E-L CAC should be enabled for intercluster E-L CAC with SME. SME can be used as a centralized bootstrap hub for the E-L CAC intercluster hub replication network. See LBM Hub Replication Network, for more information. All trunks to leaf clusters supporting E-L CAC should be SIP trunks placed in the shadow location to enable E-L CAC on the trunk between SME and the leaf clusters supporting E-L CAC. For TelePresence video interoperability, see the section on Call Admission Control Design Recommendations for TelePresence Video Interoperability Architectures. Connectivity from SME to any trunk or device other than a Unified CM that supports E-L CAC (some examples are third-party PBXs, gateways, Unified CM clusters prior to release 9.0 that do not support E-L CAC, voice messaging ports or trunks to conference bridges, Cisco Video Communications Server, and so forth) should be configured in a location other than a phantom or shadow location. The reason for this is that both phantom and shadow locations are non-terminating locations; that is, they relay information about locations and are effectively placeholders for user-defined locations on other clusters. Phantom locations are legacy locations that allow for the transmission of location information in versions of Unified CM prior to 9.0, but they are not supported with Unified CM 9.x Enhanced Locations CAC. Shadow locations are special locations that enable trunks between Unified CM clusters that support E-L CAC to accomplish it end-to-end. SME can be used as a locations and link management cluster
| Question ID 12940 | Which system location is used for intercluster Enhanced Location CAC on Cisco Unified
Communications Manager?
|
| Option A | Hub_None
|
| Option B | Default
|
| Option C | Intercluster
|
| Option D | Phantom
|
| Option E | Shadow
|
| Correct Answer | E |
Explanation Explanation: The shadow location is used to enable a SIP trunk to pass Enhanced Location CAC information such as location name and Video-Traffic-Class (discussed below), among other things, required for Enhanced Location CAC to function between clusters. In order to pass this location information across clusters, the SIP intercluster trunk (ICT) must be assigned to the "shadow" location. The shadow location cannot have a link to other locations, and therefore no bandwidth can be reserved between the shadow location and other locations. Any device other than a SIP ICT that is assigned to the shadow location will be treated as if it was associated to Hub_None. That is important to know because if a device other than a SIP ICT ends up in the shadow location, bandwidth deductions will be made from that device as if it were in Hub_None, and that could have varying effects depending on the location and links configuration.