How should the Cisco CallManager Cluster be configured so that the gatekeeper can provide call Admission control and resolve E.164 addresses?

A customer has a legacy H.320 videoconferencing system. The customer recently migrated to a converged network for voice and data and would like to include video. New ISDN gateways have been deployed to connect the legacy H.320 systems to the IP network. How should the Cisco CallManager Cluster be configured so that the gatekeeper can provide call Admission control and resolve E.164 addresses?

A customer has a legacy H.320 videoconferencing system. The customer recently migrated to a converged network for voice and data and would like to include video. New ISDN gateways have been deployed to connect the legacy H.320 systems to the IP network. How should the Cisco CallManager Cluster be configured so that the gatekeeper can provide call Admission control and resolve E.164 addresses?

A.
E,164 Addresses will be managed by the Cisco CallManager Cluster and the gatekeeper will manage the CAC for the LAN and WAN

B.
An intercluster trunk will be configured from the Cisco CallManager cluster to each of the new Video gateways and E.164 addressing and CAC will be managed by the gatekeeper

C.
Each new gateway will be included in the Cisco CallManager configuration through a MRG and an MRGL and use locations-based CAC

D.
A H.225 trunk will be configured between the gatekeeper and the Cisco CallManager cluster, the gatekeeper will resolve the E.164 addresses and manage CAC for the IP WAN



Leave a Reply 0

Your email address will not be published. Required fields are marked *