1. Glaslab
  2. Partners
  3. CLCEI1.0

CLCEI1.0(300-820) New!
Implementing Cisco Collaboration Cloud and Edge Solutions (CLCEI) v1.0

Discovery 2: Deploy Virtualized Cisco Expressway

Perform the Initial Cisco Expressway Series Configuration

Discovery 3: Register Endpoints on Cisco Expressway Series

The Cisco Expressway-C allows you to register many different endpoint using SIP and H.323 protocol. You will configure the minimum configuration to allow registration for H.323 and SIP endpoints and then you will configure interworking and transforms to allow calls between them.

Discovery 4: Call Search History and Registrations

You will explore the Cisco Expressway-C search history and alarms pages to understand what the Cisco Expressway-C does when it receives a call and how to identify an error on the server.

Discovery 5: Troubleshooting Tools

In this lab, you will look at the Cisco Expressway-C troubleshooting tools that can be used to help resolve problems or report issues to the Cisco Technical Assistance Center (TAC).

Discovery 6: Configure Cisco Expressway Series Bandwidth Management and Registration Restrictions

When your environment requires you to limit bandwidth used for video calls, you need to implement bandwidth management to control the amount of bandwidth being used for each call. The Cisco Expressway Series includes bandwidth management restrictions. You will configure subzone restrictions and pipes to manage bandwidth used for video calls.

Discovery 7: Troubleshoot Cisco Expressway Series Endpoint Registration and Local Dial Plan

Cisco Expressway Series has powerful tools to troubleshoot endpoint registrations and local dial plan. You can use event logs to check endpoint registrations and bandwidth management, search history and call history to check call attempts, and check pattern tools to check the digit manipulation rules.

Discovery 8: Configure Cisco Expressway Series Security Features

Usual deployment of the Cisco Expressway Series includes putting the Cisco Expressway-E in the DMZ zone, and allowing public traffic to traverse the Cisco Expressway Series. This can expose your environment, if you do not configure it in a secure manner. Cisco Expressway Series allows you to configure firewall rules, system certificates, and QoS settings for security and efficiency. For resiliency, you can cluster up to 6 peers of each Expressway type.

Discovery 9: Configure Cisco Unified Communications Manager to Connect with Cisco Expressway-C

Cisco Expressway-C and Cisco Unified Communications Manager are already preconfigured with the local endpoint registration, but there is no interconnection between these two call-processing systems. You will configure an interconnection between these systems to enable calls from Cisco Unified Communications Manager to Expressway endpoints and vice versa. Finally, you will configure the call policy, which will allow calls only to trusted domains, to prevent unwanted call attempts.

Discovery 10: Troubleshoot Cisco Unified Communications Manager and Cisco Expressway Series Integration

There are tools available on both systems to troubleshoot the Cisco Unified Communications Manager and Cisco Expressway Series integration. On Cisco Unified Communications Manager, you can use Cisco Unified Communications Manager Dialed Number Analyzer and Cisco Unified RTMT. On Cisco Expressway-C, you can use search history for most call-related issues.

Discovery 11: Configure Cisco Unified Communications Manager and Cisco Expressway Series Integration (Practice)

To allow calls between Cisco Unified Communications Manager and Cisco Expressway, you must configure the integration between these two call-processing systems. You will configure this integration and allow numeric and non-numeric calls between the two systems.

Discovery 12: Implement a B2B Cisco Collaboration Solution

Cisco Unified Communications Manager (Cisco Unified CM) is already interconnected with Cisco Expressway-C, which enables calls from Cisco Unified Communications Manager to a locally registered endpoint on Cisco Expressway-C. When you need to enable B2B calls, you have to configure a traversal zone between Cisco Expressway-C and Cisco Expressway-E and a DNS zone toward the public DNS server. This configuration will cause a public DNS server to get the public IP address of the customer Cisco Expressway-E.

Discovery 13: Troubleshoot B2B Calls on the Cisco Expressway Series

You have tools available on the Cisco Expressway Series to troubleshoot issues with B2B calls. On the Cisco Expressway Series, you can use search history and detailed logging for most of the B2B call-related issues.

Discovery 14: Troubleshoot B2B Calls on the Cisco Expressway Series (Practice Activity)

You will troubleshoot incoming and outgoing B2B calls and will use tools on Cisco Expressway Series with which you are already familiar.

Discovery 15: Secure a B2B Cisco Collaboration Communication

When you are configuring B2B calls, you can configure a firewall traversal connection between Cisco Expressway Series devices for nonsecure traffic using TCP protocol. The same protocol can be used to interconnect Cisco Expressway-C and Cisco Unified Communications Manager. If you want to fully secure B2B calls from Cisco Unified Communications Manager registered endpoints to the Internet, you can install signed certificates on all callprocessing servers and configure trust between them.

Discovery 16: Configure MRA on the Cisco Expressway Series

When you need to allow remote workers to use Cisco Collaboration Solutions from public networks, you can enable MRA. You will need to allow your users to register their clients with Cisco Collaboration Solutions using local networks. Then you need to configure a Cisco Unified Communication traversal zone between Cisco Expressway-C and Cisco Expressway-E with TLS authentication for which you need to exchange certificates between Cisco Expressway systems. To allow remote workers to discover registration information from public networks, you will have to configure public DNS servers appropriately.

Discovery 17: Troubleshoot MRA on the Cisco Expressway Series

There are tools available on the Cisco Expressway Series to troubleshoot issues with MRA. On the Cisco Expressway Series you can look at the Cisco Unified Communications status, where you can see the status of the components that are used for MRA. When the status does not display any errors or warnings, and the MRA does not work, then you can use diagnostic logging to collect traces and investigate the possible causes. When you believe that the issue is not related to the Cisco Expressway Series, you can also collect traces on Cisco Unified Communications Manager.

Discovery 18: Configure MRA with Additional Application Integrations

To configure Cisco MRA, you must configure service discovery on Cisco Expressway-C , which allows access to different services for remote users. You can configure service discovery without TLS verification; however, it is strongly recommended that you enable TLS verify mode, to verify the Cisco UC server's identity. When you enable TLS verify mode, you have to install certificates on all Cisco UC servers that are part of the service discovery, and you also need to configure Cisco Expressway-C to trust those certificates. In addition, the DNS server must be configured to allow resolving FQDN’s of Cisco UC servers to an IP address.