Expressway E and C Setup - MRA

Mobile and Remote access System Configuration

Expressway MRA use for registering your remote endpoints registering with CUCM without using VPN

Few Points

* If your are deploying over WAN, minimum recommended latency is 80ms

* Remote devices will be communicating with Edge initially using the Public IP, E Usually deploy in DMZ. C takes care of LAN side communication towards CUCM

* There will be two interface for Edge. Internal and External.

* Remote devices will be registered over Core, on CUCM you could find the registered device IP as C

* If you have redundancy, Then both C act as Active - Active

---------------------DNS Records-----------------

1 -  Create PTR DNS Record for each Xpressway C host

2 -  Create Expressway Cluster DNS for Cluster C

3 - Create PTR DNS Record for each Xpressway E host

4 -  Create Expressway Cluster DNS for Cluster E

5 -  Create SRV Records

create 2 Recors for Expressway E [ port number 8443]

service : _collab-edge

Protocol: _tls

---------------------Installation MRA with Expressway-----------------

** Install Both E and C. Following are the basic config

1- Add your NTP server on C and Expressway

2- Change your root CLI password

 Default User Name - root Default Password TANDBERG

command to change password 'passwd'

3- Add Options key on Both C and E. Once you add Expressway series key system will show as whether its Core or Edge

4- Add DNS server IP'series

5- Configure Clustering on C and E

->enter the Cluster Name and then add the peer 1 and 2 host name/IP address

->Reboot both E and C. Once it rebooted check your clustering is Active

6- Configure Unified Communication 

-> Go to Configuration-> Unified Communications -> Choose Mobile and remote access

7- Configure Domain > Add your Domain

8- Add a link between C and  CUCM 

configuration -> Unified Communications -> Unified  CM Servers -> Enter FQDN or IP or Pub

enter AXL details. Once its added CM cluster will be auto added

9- Add CA Certificate and Root Certificates 

On C go to Maintenance -> Security Certificates->  Trusted CA Certificates -> Browse and add rootCA certificate

Enable GingerCannot connect to Ginger Check your internet connection
or reload the browserDisable in this text fieldEditEdit in GingerEdit in Ginger×

Reinstalling CUC and UCCX Subscriber

We had UCS C220, recently UCS upgraded to C240 M4SX. All the secondary UC servers were running on 220. This new UCS racked in service provider managed DC. So the IP details were different. I have re-installed the subscriber and added to existing cluster. procedure is simple, steps given below

Note - During the installation you would require to enter the Web-security details (CN,OU etc)

use 'show web-security' to get the details from CLI. you would require to enter the OS admin password as well

UCCX Installation:

1.  Login CCX Administration -> Go to System -> Servers -> and delete the subscriber node -> Restart the Publisher
2. Once publisher is restarted check System -> Servers. Make sure Subscriber is removed from the cluster
3. Start the installation, during the installation choose that this node as subscriber and enter the publisher details. Once installation completed check the cluster and DB replication. New subscriber will be part of cluster now 

CUC  Installation:

1.  Login CUC Administration -> Go to System Settings -> Cluster -> Click Find -> Choose the Subscriber node -> Delete it -> Restart the Publisher
2. Once publisher is restarted, make sure Subscriber is removed from the cluster
3. Start the installation, during the installation choose that this node as subscriber and enter the publisher details. Once installation completed check the cluster and DB replication. New subscriber will be part of cluster now