Cisco Expressway
Testing
Collab Edge Testing Tool
Collaboration Solutions Analyzer
Jabber MRA Call Flow - Detailed
Licensing
Calls from registered systems to all other systems will use one RMS license, whenever those calls require the
Expressway to process the media streams. This includes, but is not limited to, the following call types:
— Business to business calls: previously required two RMS licenses, now require one on Expressway-E — Business to consumer calls (Jabber Guest): previously required two RMS licenses, **now require one on the Expressway-E** — Interoperability gateway calls (including Microsoft Lync / Skype for Business and third-part
There are 7 SKU for licensing Expressway.
Register the Expressway server first using the SKU: LIC-SW-EXP-K9
This is the Cisco TelePresence Software Upgrade Release Keys.
Quantity of '1' per server.
Apply this license file as the Expressway release key.
Then reboot and THEN apply the options to make it an expressway C or E with X number of RMS licenses.
For Expressway E register quantity of '1' of the below SKUs on cisco.com/go/license) and apply to the server
LIC-EXP-AN
LIC-EXP-E
LIC-EXP-TURN
For Expressway E & C register quantity of '1' of each of the below and apply to the server
LIC-EXP-SERIES
LIC-EXP-GW
For Expressway E & C you then need to register the required number of RMS licenses which should be split across the Expressway C and Es (apply and reboot expressway) - note this is no longer correct - see above.
LIC-EXP-RMS
Note: the RMS license is the only multiple count license file you need. All others should have quantity of '1' when you register them.
Expressway LAN
Clustering requires you to use LAN 1 NIC and LAN 1 and LAN 2 must use non - opverlappying subnets. Clustering cannot use Static NAT, therefore LAN 2 should be used for your external facing interface.
Packet Capture trace
Below is not relevant any more, as you can capture from the GUI interface.
On expressway, log in as root and type:
mkdir /mnt/harddisk/traces
cd /mnt/harddisk/traces
Then to activate the trace type: Interface 1, max 10 MB file
tcpdump -i 1 -w trace.cap -s 0 -C 10
B2B Blog
Built In Bridge
Reference: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/expressway/config_guide/X12-5/exwy_b_mra-expressway-deployment-guide/exwy_b_mra-expressway-deployment-guide_chapter_01000.html#reference_F246F8721664A45638A98B9E9A9B2919 Built-in-Bridge Recording through MRA
The Expressway supports Built-in-Bridge (BiB) recording over MRA. This feature can help organizations to comply with the phone recording requirements of the European Union's Markets in Financial Instruments Directive (MiFID II).
How it works
- BiB can be used to record the audio portion of calls that are made or received by users working off-premises.
- BiB is always enabled on the Expressway.
- BiB is configurable on Cisco Unified Communications Manager. When BiB is enabled, Unified CM forks the call to and from the endpoint to a media recording server.
Bandwidth and call capacity impacts
- If you plan to use this feature, be aware that it has significant impact on bandwidth and call capacity.
- It requires additional network bandwidth to be provisioned. Details are provided in the Cisco Collaboration System 12.x Solution Reference Network Designs (SRND), section “Capacity Planning for Monitoring and Recording”. Enabling BiB for MRA endpoints typically needs double bandwidth as, assuming both sides of the call are recorded, each BiB-enabled call consumes double the usual bandwidth.
- Enabling BiB on MRA endpoints reduces the overall call capacity of Expressway nodes down to approximately one-third of their original capacity. This is because each call that is being recorded has two additional SIP dialogs associated with it (so essentially equivalent to three calls).
Built-in-Bridge Recording through MRA Prerequisites
- Configure BiB over MRA
- Built-in-Bridge Recording through MRA Prerequisites
- BiB over MRA requires the following components, or later:
Any compatible clients:
- Cisco Jabber for Windows 11.9
- Cisco Jabber for Mac 11.9
- Cisco Jabber for iPhone and iPad 11.9
- Cisco Jabber for Android 11.9
- Cisco IP Phone 7800 Series, Cisco IP Conference Phone 7832, or Cisco IP Phone 8800 Series devices which support MRA (not all these phones are MRA-compatible)
- The phones which currently support MRA are listed in the MRA Requirements section of this guide, or ask your Cisco representative for details.
- Registrar/call control agent: Cisco Unified Communications Manager 11.5(1)SU3 BiB is not supported on Expressway-registered endpoints.
- Edge traversal: Expressway X8.11.1
- Recording server: Out of scope for this document. (Information about configuring recording for Cisco Unified Communications Manager is available in the Feature Configuration Guide for Cisco Unified Communications Manager.)