UCC

This section describes the UCC feature. The Unified Communications Manager (UCM) is the core solution component of this feature. UCC addresses the onslaught of mobile devices that use voice, video, and collaboration applications. UCC solution reduces the cost of infrastructure for enterprise communication and collaboration.

UCC continues to support most of the existing functionality offered by ArubaOS 6.x. This section includes the following topics:

UCC Application in ArubaOS 8.x

UCC Value Additions in Mobility Master

UCC in Master Controller Mode

UCC Changes from ArubaOS 6.x

UCC Features Deprecated in ArubaOS 8.x

Prerequisites to Enable UCC

Multi-ALG Support

UCC ALG Configuration

View UCC Information

Intelligent Call Handling

RTP Analysis

AppRF Integration with ALGs and User Role

Microsoft® Lync or Skype for Business

Cisco Jabber

Wi-Fi Calling

UCC Dashboard

UCC-AirWave Integration

UCC Limitations

Upgrade UCM Loadable Service Module

UCC Application in ArubaOS 8.x

Starting from ArubaOS 8.x, UCM runs as a loadable service module on Mobility Master. UCC supports various applications like Apple FaceTime, Alcatel-Lucent NOE, Microsoft® Lync or Skype for Business, Cisco Jabber, Cisco skinny call control protocol, SpectraLink voice priority, SIP, H.323, Vocera, and Wi-Fi Calling. UCC application on Mobility Master implements the VoIP ALG to support both encrypted and non-encrypted VoIP protocols. UCC application uses the OpenFlow infrastructure to receive the signaling messages from the managed devices and also install and delete flows on the managed devices for calls made.

In addition, UCC is supported on a stand-alone and master controller. In master controller mode, UCM and VoIP ALGs run on the managed devices.

UCC Value Additions in Mobility Master

The following is a list of UCC value additions in Mobility Master:

Enables VoIP ALGs to run as a service on Mobility Master and managed devices need not run the same. This results in better scalability.

Enables real-time analysis of VoIP calls in upstream direction. This is the real-time analysis and UCC call quality statistics calculated based on VoIP stream captured at the managed device.

Supports Loadable Service Module. UCM is a Loadable Service Module. ALGs are completely decoupled from the managed devices. This enables faster innovation of VoIP services such as introduction of new ALGs and enhancements to existing features as they will become independent of the ArubaOS release version.

Provides a solution to the fanout problem in Lync or Skype for Business SDN API. In ArubaOS 6.x, Lync or Skype for Business SDN Manager sent call information messages to every local controller in the network, regardless of whether the local controller is involved in the call or not. This additional processing is an unnecessary overhead on the local controller. In addition, the bandwidth utilization between the data center and remote location is not efficient. With the Mobility Master deployment, Lync or Skype for Business SDN Manager sends the call information messages to Mobility Master only.

Provides aggregation of statistical information of call-related data at a centralized entity.

UCC in Master Controller Mode

ArubaOS 8.x.1.0 supports 7200 Series controllers to run as a master controller. UCC is supported in master controller mode. In master controller mode, UCM and VoIP ALGs run on the managed device. The ALGs should be configured on the managed device. OpenFlow infrastructure is not supported in master controller mode. Centralized visibility of UCC statistics is not available in this mode. To view the UCC statistics, you should log in to the respective managed device.

UCC Changes from ArubaOS 6.x

The following is a list of UCC changes from ArubaOS 6.x to ArubaOS 8.x:

In ArubaOS 6.x, VoIP ALGs run on the respective local controllers that parse the signaling messages, dynamically opens sessions in firewall, prioritizes traffic, and provide visibility. In ArubaOS 8.x, VoIP ALGs do not run on the managed devices. They run as an application on Mobility Master. In a stand-alone controller deployment, the VoIP ALGs run on the stand-alone controller itself. In master controller mode, the VoIP ALGs run on respective managed devices.

UCC running on Mobility Master uses OpenFlow infrastructure to receive signaling packets on Mobility Master, parse, open sessions in the firewall, and prioritize them. In master controller mode, OpenFlow infrastructure is not supported.

Visibility for all supported UCC applications are provided from the centralized Mobility Master dashboard. Centralized dashboard and visibility are not available in master controller mode. You should login to individual managed device to view dashboard information.

ArubaOS 8.x supports Cisco Jabber and Wi-Fi Calling.

Unlike ArubaOS 6.X, where ALGs use WMM-DSCP mappings in the WLAN SSID profile to set the ToS for RTP and RTCP, Mobility Master has ALG-specific QoS configurations.

UCC Features Deprecated in ArubaOS 8.x

The following are the features deprecated in ArubaOS 8.x:

BSS transition and force BSS transition.

Call count, bandwidth, and TSPEC-based call admission control.

Classify media action in ACL for media classification – Microsoft® Lync or Skype for Business calls will automatically get prioritized without the need for classify media ACLs.

SIP session timer.

SIP dial plans.

WMM-DSCP override setting in the SSID profile.

Stateful ALG settings in global firewall options. These settings are now available in Mobility Master and master controller under the Configuration > System > Profiles > All Profiles > UCC profile.

Lync or Skype for Business traffic control profile.

Web Server port configuration for Lync or Skype for Business SDN API. The Mobility Master and master controller uses 32000 as the default port now.

The Monitoring tab in the WebUI.

The show voice commands.

sip-authentication-role parameter in AAA profile.

voice-aware parameter in AAA authentication 802.1X profile.

Prerequisites to Enable UCC

OpenFlow Controller Configuration

Enable OpenFlow on Mobility Master. You must enable this in the /mm node hierarchy.

 

OpenFlow controller is not a prerequisite in master controller mode.

In the WebUI

The following procedure configures OpenFlow on Mobility Master using the WebUI:

1. In the Mobility Master node hierarchy, navigate to Configuration > System > Profiles.
2. In All Profiles, expand Controller Profile. Select openflow-controller.
3. In openflow-controller, select the ofc-state check box.
4. Click Submit.
5. Click Pending Changes.
6. In the Pending Changes window, select the check box and click Deploy changes.

In the CLI

The following commands configure OpenFlow on Mobility Master using the CLI:

(host) [mm] (config) #openflow-controller

(host) ^[mm] (openflow-controller) #openflow-controller-enable

(host) ^[mm] (openflow-controller) #write memory

OpenFlow Profile Configuration on Managed Devices

Bind the user VLANs to the OpenFlow profile on the managed devices. You must bind this in the /md node hierarchy.

 

OpenFlow profile is not a prerequisite in master controller mode.

In the WebUI

The following procedure binds the user VLANs to the OpenFlow profile on the managed devices using the WebUI:

1. In the Managed Network node hierarchy, navigate to Configuration > System > Profiles.
2. In All Profiles, expand Controller Profile. Select Openflow-profile.
3. In Openflow-profile, select the State check box.
4. In controller-ip, enter the Mobility Master IP address and port number.
5. In bind-vlan, enter the user VLAN to the current list.
6. Click Submit.
7. Click Pending Changes.
8. In the Pending Changes window, select the check box and click Deploy changes.

In the CLI

The following commands bind the user VLANs to the OpenFlow profile on the managed devices using the CLI:

(host) [md](config) #openflow-profile

(host) ^[md](Openflow-profile) #openflow-enable

(host) ^[md](Openflow-profile) #controller-ip <MM-ip> <port>

(host) ^[md](Openflow-profile) #bind-vlan <list of user vlans>

(host) ^[md](Openflow-profile) #write memory

OpenFlow in User Role and Virtual AP Configuration

Enable OpenFlow in the user-role and the virtual AP profile. You must enable this in the /md node hierarchy.

 

OpenFlow in user role and virtual AP is not a prerequisite in master controller mode.

In the WebUI

The following procedure enables OpenFlow in the user-role and virtual AP using the WebUI:

1. In the Managed Network node hierarchy, navigate to Configuration > Roles & Policies.
2. In the Roles tab, select an existing role.
3. In the Roles > <custom-role> section, click Show Advanced View.
4. Under More, expand Network.
5. Select the Open flow check box.
6. Click Submit.
7. Navigate to Configuration > System > Profiles.
8. In All Profiles, expand Wireless LAN > Virtual AP. Select the default profile.

This example uses the default profile.
9. In Virtual AP profile, expand Advanced.
10. Select the Openflow Enable check box.
11. Click Submit.
12. Click Pending Changes.
13. In the Pending Changes window, select the check box and click Deploy changes.

In the CLI

The following commands enable OpenFlow in the user-role and virtual AP using the CLI:

(host) [md] (config) #user-role <user-role>

(host) ^[md] (config-submode)#openflow-enable

(host) ^[md] (config-submode)#!

(host) ^[md] (config) #wlan virtual-ap <virtual-ap>

(host) ^[md] (Virtual AP profile "<virtual-ap>") #openflow-enable

(host) ^[md] (Virtual AP profile "<virtual-ap>") #write memory

Management Server Profile Configuration

Configure the management server profile. This enables AMON feeds to be sent to Mobility Master or master controller for various statistics. You must configure this in the /md node hierarchy or the sub-nodes of /md.

In the WebUI

The following procedure configures management server profile using the WebUI:

1. In the Managed Network node hierarchy, navigate to Configuration > System > Profiles.
2. In All Profiles, expand Controller Profile. Select Mgmt Config.
3. In Mgmt Config profile, click the + icon.
4. In the Profile name field, enter the name of the management server profile.
5. Select the following check boxes:

Stats

Sessions

Monitored Info - Add/Update

Monitored Info - Deletion

Monitored Info - Periodic Snapshot

6. Click Submit.
7. Navigate to Configuration > System > More.
8. Expand General and in MON Receivers, click the + icon.
9. In New MON Receiver, enter the following details:
a. In the Server field, enter the Mobility Master or master controller IP address.
b. In the Profile list drop-down list, select the newly created management server profile.
10. Click Submit.
11. Click Pending Changes.
12. In the Pending Changes window, select the check box and click Deploy changes.

In the CLI

The following commands configure management server profile using the CLI:

(host) [md] (config) #mgmt-server profile <profile-name>

(host) ^[md] (Mgmt Config profile "<profile-name>") #stats-enable

(host) ^[md] (Mgmt Config profile "<profile-name>") #sessions-enable

(host) ^[md] (Mgmt Config profile "<profile-name>") #monitored-info-enable

(host) ^[md] (Mgmt Config profile "<profile-name>") #monitored-info-del-enable

(host) ^[md] (Mgmt Config profile "<profile-name>") #monitored-info-snapshot-enable

(host) ^[md] (Mgmt Config profile "<profile-name>") #!

(host) ^[md] (config) #mgmt-server primary-server <MM-IP> profile <profile-name>

(host) ^[md] (config) #write memory

Deep Packet Inspection Configuration

Enable DPI on the managed devices if your deployment has Cisco Jabber clients. You must enable this in the /md node hierarchy.

In the WebUI

The following procedure enables DPI on the managed devices using the WebUI:

1. In the Managed Network node hierarchy, navigate to Configuration > Services > Firewall.
2. Expand Global Settings.
3. Select the Enable deep packet inspection check box.
4. Click Submit.
5. Click Pending Changes.
6. In the Pending Changes window, select the check box and click Deploy changes.

In the CLI

The following commands enable DPI on the managed devices using the CLI:

(host) [md] (config) #firewall

(host) ^[md] (config-submode)#dpi

(host) ^[md] (config) #write memory

 

If DPI is enabled, either there should be an explicit ACL to permit RTP or RTCP traffic or an app-based ACL to permit media traffic. For more information, see AppRF Integration with ALGs and User Role.

Firewall Visibility Configuration

Enable firewall visibility on the managed devices. This is an optional setting. Enable this setting to view traffic analysis on the Mobility Master dashboard. You must enable this in the /md node hierarchy.

In the WebUI

The following procedure enables firewall visibility on the managed devices using the WebUI:

1. In the Managed Network node hierarchy, navigate to Configuration > Services > Firewall.
2. Expand Global Settings.
3. Select the Enable firewall visibility check box.
4. Click Submit.
5. Click Pending Changes.
6. In the Pending Changes window, select the check box and click Deploy changes.

In the CLI

The following command enables firewall visibility on the managed devices using the CLI:

(host) [md] (config) #firewall-visibility

(host) ^[md] (config) #write memory

Multi-ALG Support

In ArubaOS 8.x, multiple applications running simultaneously on the same client device can be identified and prioritized. A maximum of 10 applications running simultaneously on client device is supported. The multi-ALG feature is enabled by default on Mobility Master.

UCC ALG Configuration

The UCC ALGs must be configured from the /mm node hierarchy of Mobility Master. All the ALGs are enabled by default.

 

In master controller mode, UCC ALGs must be configured from the /md node hierarchy of the master controller. All the ALGs are enabled by default.

 

SpectraLink voice priority ALG is enabled by default. ArubaOS does not have a separate configuration setting for this ALG.

In the WebUI

The following procedure configures the ALGs using the WebUI:

1. In the Mobility Master node hierarchy, navigate to Configuration > System > Profiles > All Profiles.
2. Expand UCC to configure various ALGs as described in Table 1.
3. Click Submit.
4. Click Pending Changes.
5. In the Pending Changes window, select the check box and click Deploy changes.

Table 1: ALG Configurations

ALG

Description

FaceTime ALG Configuration

Configures the Apple FaceTime ALG. The ALG is enabled by default. The range is 0-63. The DSCP value for the video session is 34 by default.

H323 ALG Configuration

Configures the H.323 ALG. The ALG is enabled by default. The range is 0-63. The DSCP value for the voice session is 46 by default.

Intelligent Call Handling Configuration

Configures the Intelligent Call Handling. The setting is enabled by default. The range is 50-95. The Channel Utilization Threshold is 90 by default.

Jabber ALG Configuration

Configures the Cisco Jabber ALG. The ALG is enabled by default. Enter the Cisco Unified Communication Manager IM & Presence server IP. The range is 0-63. The DSCP values for the voice, video, and app-sharing sessions are 46, 34, and 34, respectively, by default.

NOE ALG Configuration

Configures the Alcatel-Lucent NOE ALG. The ALG is enabled by default. The range is 0-63. The DSCP value for the voice session is 46 by default.

Real-Time Analysis Configuration

Configures the real-time analysis of VoIP calls including upstream real-time analysis. The setting is enabled by default.

SCCP ALG Configuration

Configures the Cisco SCCP ALG. The ALG is enabled by default. The range is 0-63. The DSCP value for the voice session is 46 by default.

SIP ALG Configuration

Configures the SIP ALG. The ALG is enabled by default. You can enable the SIP Midcall request timeout and RTCP inactivity settings. The range is 0-63. The DSCP values for the voice and video sessions are 46 and 34, respectively, by default.

Skybe4B ALG Configuration

Configures the Microsoft® Lync or Skype for Business ALG. The ALG is enabled by default. You can set the Lync or Skype for Business SDN listen protocol over HTTP or HTTPS. The default Lync or Skype for Business SDN API listen port is 32000. Based on the SDN listen protocol configuration, Mobility Master accepts either HTTP or HTTPS messages from the Lync or Skype for Business SDN Manager. The DSCP values for the voice, video, and app-sharing sessions are 46, 34, and 34, respectively, by default. The range is 0-63.

UCC Session Idle Timeout Configuration

Configures the UCC session idle timeout. On configuring this parameter, if the voice session is idle for the configured period, UCM aborts the session on the managed device due to inactivity. The range is 35-250. The default value is 35.

Vocera ALG Configuration

Configure the Vocera ALG. The ALG is enabled by default. The range is 0-63. The DSCP value for the voice session is 46 by default.

Wi-Fi Calling Configuration

Configures the Wi-Fi Calling. Wi-Fi Calling is enabled by default. The range is 0-62. The DSCP value for the voice session is 46 by default.

dns-pattern–Configure the DNS pattern for the carrier. A maximum of 10 DNS patterns can be configured.

DNS patterns for known carriers are configured by default. Default built-in patterns are:

3 HK - wlan.three.com.hk

ATT - epdg.epc.att.net

Rogers - epdg.epc.mnc720.mcc302.pub.3gppnetwork.org

SmarTone - epdg.epc.mnc006.mcc454.pub.3gppnetwork.org

Sprint - primgw.vowifi2.spcsdns.net

T-Mobile - ss.epdg.epc.mnc260.mcc310.pub.3gppnetwork.org

Verizon - wo.vzwwo.com

If the ePDG FQDN of the carrier does not match with the default patterns, use this option to configure the DNS pattern for the carrier.

NOTE: The DNS IP address that Mobility Master learns for Wi-Fi Calling age out automatically, if there was no DNS query or response matching that IP for more than seven days.

service-provider–Add the service provider name for enhanced visibility.

In the CLI

The following command configures the ALGs using the CLI:

(host) [mm] (config) #ucc ?

facetime Configure the FaceTime ALG Configuration

h323 Configure the H323 ALG Configuration

ich Configure the Intelligent Call Handling Configuration

jabber Configure the Jabber ALG Configuration

noe Configure the NOE ALG Configuration

rtpa-config Configure the Real-Time Analysis Configuration

sccp Configure the SCCP ALG Configuration

session-idle-timeout Configure the UCC Session Idle Timeout Configuration

sip Configure the SIP ALG Configuration

skype4b Configure the Skype4B ALG Configuration

vocera Configure the Vocera ALG Configuration

wificalling Configure the WiFiCalling Configuration

For more information, see the ucc command in the ArubaOS Command-Line Interface Reference Guide.

View UCC Information

 

In master controller mode, you must login to the managed device to view the UCC configurations and statistics.

The following commands are available to view UCC client and call information using the CLI:

(host) [mm] #show ucc ?

call-info Show ucc call detailed records (CDRs)

client-info Show ucc client status and record

dns-ip-learning DNS ip learning

facetime Show the FaceTime ALG Configuration

h323 Show the H323 ALG Configuration

ich Show the Intelligent Call Handling Configuration

internal-state UCC internal-state information

jabber Show the Jabber ALG Configuration

noe Show the NOE ALG Configuration

rtpa-config Show the Real-Time Analysis Configuration

rtpa-report Show Real-Time Analysis report

sccp Show the SCCP ALG Configuration

session-idle-timeout Show the UCC Session Idle Timeout Configuration

sip Show the SIP ALG Configuration

skype4b Show the Skype4B ALG Configuration

statistics UCC statistics

trace-buffer Show call trace buffer

vocera Show the Vocera ALG Configuration

wificalling Show the WiFiCalling Configuration

For more information, see the show ucc commands in the ArubaOS Command-Line Interface Reference Guide.

Intelligent Call Handling

ArubaOS 8.x replaces Call Admission Control with Intelligent Call Handling (ICH). ICH monitors the channel utilization of all radios of the APs on the managed device. If the channel utilization exceeds beyond a configurable threshold on a radio, new UCC calls are not prioritized. This is to ensure that existing calls on the radio are not penalized due to a new call when channel utilization is very high. ICH is enabled by default and applies to all ALGs supported by UCM.

 

In master controller mode, ICH must be configured from the /md node hierarchy of the master controller.

In the WebUI

The following procedure configures ICH using the WebUI:

1. In the Mobility Master node hierarchy, navigate to Configuration > System > Profiles > All Profiles.
2. Expand UCC and click Intelligent Call Handling Configuration.
3. In the Intelligent Call Handling Configuration section, configure the following settings:
a. Select the Intelligent Call Handling check box.
b. In the Channel Utilization Threshold text-box, enter the channel utilization value.
4. Click Submit.
5. Click Pending Changes.
6. In the Pending Changes window, select the check box and click Deploy changes.

In the CLI

The following commands configure ICH using the CLI:

(host) [mm] (config) #ucc ich

(host) ^[mm] (Intelligent Call Handling Configuration) #enable

(host) ^[mm] (Intelligent Call Handling Configuration) #channel-utilization-threshold 90

RTP Analysis

Mobility Master performs RTP analysis for most VoIP ALG calls in both downstream (at AP) and upstream direction (at managed device) and captures the quality metrics. The downstream UCC score measures call quality between the AP and the wireless client in the downstream direction. The upstream UCC score measures call quality over the wired network between the AP and the managed device in the upstream direction. The quality metrics captured is applicable for all the active sessions belonging to the same or different ALG running on that client.

Starting with ArubaOS 8.1.0.0, Mobility Master calculates upstream UCC score for wired clients that are behind the wired port of an AP or Remote AP.

 

In master controller mode, RTP analysis must be configured from the /md node hierarchy of the master controller.

In the WebUI

The following procedure configures RTP analysis using the WebUI:

1. In the Mobility Master node hierarchy, navigate to Configuration > System > Profiles > All Profiles.
2. Expand UCC and click Real-Time Analysis Configuration.
3. In the Real-Time Analysis Configuration section, configure the settings described in Table 2.
4. Click Submit.
5. Click Pending Changes.
6. In the Pending Changes window, select the check box and click Deploy changes.

Table 2: Real-Time Analysis Configuration Parameters

Parameter

Description

Real-Time Analysis of VoIP calls

Enables real-time analysis of VoIP calls.
This is the real-time analysis and UCC statistics calculated based on VoIP stream at the access point.

Upstream Real-Time Analysis of VoIP calls

Enables real-time analysis of upstream VoIP calls.
This is the real-time analysis and UCC statistics calculated based on VoIP stream at the managed device.

In the CLI

The following commands configure real-time analysis using the CLI:

(host) [mm] (config) #ucc rtpa-config

(host) ^[mm] (Real-Time Analysis Configuration) #enable

(host) ^[mm] (Real-Time Analysis Configuration) #upstream

(host) ^[mm] (Real-Time Analysis Configuration) #write memory

 

The upstream and downstream RTP analysis of VoIP calls are enabled by default.

The following command displays the real-time analysis configuration using the CLI:

(host) [mm] #show ucc rtpa-config

 

Real-Time Analysis Configuration

--------------------------------

Parameter Value Set

--------- ----- ---

Real-Time Analysis of VoIP calls Enabled

Upstream Real-Time Analysis of VoIP calls Enabled

The following command displays the real-time analysis report using the CLI:

(host) [mm] #show ucc rtpa-report

 

Help: [C] - Metric calculated at the Controller

[A] - Metric calculated at the AP

[E] - Metric calculated End-to-End

 

Real-Time Analysis Call Quality Report

--------------------------------------

Client(IP) Client(MAC) Client(Name) ALG Jitter(usec)[C] Pkt-loss(%)[C] Delay(usec)[C]

---------- ----------- ------------ --- --------------- -------------- --------------

192.168.201.240 f0:7b:cb:3b:65:5c 1002 SIP 23.700 0.000 101.800

192.168.201.246 00:24:d7:40:a8:58 1003 SIP 30.912 0.000 257.140

 

UCC Score[C] Jitter(usec)[A] Pkt-loss(%)[A] Delay(usec)[A] UCC Score[A] Forward mode

------------ --------------- -------------- -------------- ------------ ------------

68.366 0.000 0.499 316.400 84.119 decrypt-tunnel

82.551 0.000 0.000 327.478 85.999 decrypt-tunnel

 

Num Records:2

The following command displays real-time analysis for VoIP clients using the CLI. A session with the Q flag indicates downstream real-time analysis and that with the u flag indicates upstream real-time analysis:

(host) [mm] #show datapath session table 10.16.4.71 | include 10.16.4.80

 

Datapath Session Table Entries ------------------------------

Flags: F - fast age, S - src NAT, N - dest NAT

D - deny, R - redirect, Y - no syn

H - high prio, P - set prio, T - set ToS

C - client, M - mirror, V - VOIP

Q - Real-Time Quality analysis

u - Upstream Real-Time Quality analysis

I - Deep inspect, U - Locally destined

E - Media Deep Inspect, G - media signal

r - Route Nexthop, h - High Value

B - Permanent, O - Openflow

L - Log

 

Source IP Destination IP Prot SPort DPort Cntr Prio ToS Age Destination TAge

--------------- --------------- ---- ----- ----- -------- ---- --- --- ----------- ----

10.16.4.80 10.16.4.71 17 20008 20038 0/0 6 46 0 local 24

 

Packets Bytes Flags

--------- --------- ----------

909 115732 HPTCIQuVBO

RTP Analysis Limitations

In case of split-tunnel forwarding mode, upstream UCC score is not calculated if the calling and called party are behind the same remote AP.

UCC score, jitter, delay, and packet loss is calculated for voice RTP streams only. These metrics are not available for video streams.

Upstream UCC score is not supported for desktop sharing , file transfer, Apple Facetime, Spectralink SVP, Vocera, and Wi-Fi Calling ALGs.

AppRF Integration with ALGs and User Role

The QOSMOS engine does not recognize many of the UCC applications. For the ones it recognizes, it does not maintain the state of the application. Due to this limitation, it cannot provide granular visibility into the UCC applications. To resolve this limitation, in ArubaOS 8.x, voice ALGs identify the application type for supported UCC applications, so that the administrator can now use AppRF rules to deny, permit, apply QoS, or rate limit UCC application traffic. The UCC application identifies all the supported applications listed below. The UCC application identifies the application type corresponding to a media session and programs the datapath with the application ID and the priority values. It is mandatory to add the ACLs to permit specific application traffics if an ACL rule is not present in the user-role to permit RTP or RTCP traffic. Following is a list of UCC applications that can be used to create application ACLs.

Table 3: UCC Application ACLs

UCC Application ACL

alg-facetime

alg-ftp

alg-h323

alg-jabber-audio

alg-jabber-desktop-sharing

alg-jabber-video

alg-noe

alg-rtp

alg-sccp

alg-sip

alg-sip-audio

alg-sip-video

alg-skype4b-app-sharing

alg-skype4b-audio

alg-skype4b-desktop-sharing

alg-skype4b-file-transfer

alg-skype4b-secure

alg-skype4b-video

alg-svp

alg-vocera

alg-wifi-calling

The following pre-defined ACL are available by default. The administrator can either add the entire ACL to the appropriate user-role or selectively use the application IDs in another ACL and add that to the appropriate user-role.

ip access-list session voip-applications-acl

any any app alg-skype4b-audio permit

any any app alg-skype4b-video permit

any any app alg-skype4b-desktop-sharing permit

any any app alg-skype4b-app-sharing permit

any any app alg-sip-audio permit

any any app alg-sip-video permit

any any app alg-sccp permit

any any app alg-vocera permit

any any app alg-noe permit

any any app alg-h323 permit

any any app alg-jabber-audio permit

any any app alg-jabber-video permit

any any app alg-facetime permit

any any app alg-wifi-calling permit

any any app alg-rtp permit

The ordering of the UCC application ACE is not important except for the last ACE – any any app alg-rtp permit. The use of this ACE is to permit RTP traffic. This is important in a deployment having media application that is not identified by the UCC application. In such a case, the UCC application falls back to the alg-rtp ACE as the default application ID. If permitting random RTP traffic is a requirement, this ACE should be included in the ACL. In addition, this ACE should always be the last entry in the ACL.

An example of the ACE entries of voip-applications-acl follows:

(host) [mynode] #show ip access-list voip-applications-acl

 

ip access-list session voip-applications-acl

voip-applications-acl

---------------------

Priority Source Destination Service Application Action TimeRange

-------- ------ ----------- ------- ----------- ------ ---------

1 any any app alg-skype4b-audio permit

2 any any app alg-skype4b-video permit

3 any any app alg-skype4b-desktop-sharing permit

4 any any app alg-skype4b-app-sharing permit

5 any any app alg-sip-audio permit

6 any any app alg-sip-video permit

7 any any app alg-sccp permit

8 any any app alg-vocera permit

9 any any app alg-noe permit

10 any any app alg-h323 permit

11 any any app alg-jabber-audio permit

12 any any app alg-facetime permit

13 any any app alg-wifi-calling permit

14 any any app alg-rtp permit

Log Expired Queue TOS 8021P Blacklist Mirror DisScan IPv4/6 Contract

--- ------- ----- --- ----- --------- ------ ------- ------ --------

Low 4

Low 4

Low 4

Low 4

Low 4

Low 4

Low 4

Low 4

Low 4

Low 4

Low 4

Low 4

Low 4

Low 4

The following example adds an ACL to permit Lync or Skype for Business audio and video traffic and reference it to the user-role:

(host) [mynode] (config) #ip access-list session apprf-skype4b-sacl

(host) ^[mynode] (config-submode)#any any app alg-skype4b-audio permit

(host) ^[mynode] (config-submode)#any any app alg-skype4b-video permit

Other ACL rules like bandwidth contract, deny, 802.1p priority, and ToS can be used along with the ACL application IDs.

Microsoft® Lync or Skype for Business

ArubaOS provides a seamless user experience for Microsoft® Lync or Skype for Business users using voice or video calls, app-sharing, and file-transfer in a wireless environment. Microsoft® Lync or Skype for Business is an enterprise solution for UCC. It provides support for voice, video, app-sharing, and file-transfer. The Lync or Skype for Business SDN API provides an interface to Mobility Master to access Lync or Skype for Business network diagnostic information about voice, video, app-sharing, and file-transfer without having to see into the traffic.

Lync or Skype for Business Media Classification Support in Mobility Master

By default, all the VoIP traffic undergo Media Classification on the managed device whenever RTP Traffic reaches the managed device. UCM in Mobility Master can identify and prioritize calls made using Lync or Skype for Business ALG. UCM also provides visibility for all voice calls made using the Lync or Skype for Business ALG. UCM on Mobility Master dynamically opens firewall ports for voice and video traffic. The user does not have to explicitly define a firewall policy to permit such traffic.

UCC Score for Lync or Skype for Business Media Classification

ArubaOS supports UCC score for Lync or Skype for Business calls prioritized using media classification. As part of this feature, UCM supports the following:

Real-time quality analysis for Lync or Skype for Business voice and video calls (voice RTP streams only)

Real-time computation of UCC score (delay, jitter, and packet loss) for Lync or Skype for Business VoIP calls prioritized using media classification. The UCC score is computed by the AP in the downstream direction and also at the managed device in the upstream direction.

Call Quality vs. Client Health chart in the UCC dashboard of Mobility Master.

 

When VoIP calls are prioritized using media classification, end-to-end call quality metrics such as mean opinion score, delay, jitter, and packet loss are not available.

UCC score computes the quality of voice calls. It takes delay, jitter, and packet loss of Real-time Transport Protocol (RTP) packets into account. UCC score is computed on a scale of 0 to 100. To compute the UCC score, you must enable RTP Analysis on Mobility Master. For more information, see RTP Analysis.

Available Call Quality Metrics

Following call quality metrics are available for Lync or Skype for Business calls prioritized by media classification:

Client IP, Client Mac, ALG, Duration(approximate), Orig time(approximate), Status, Reason, Call Type (voice or video), Client Health, UCC Score, UCC Band, Source port, Destination port, Originated and modified DSCP & WMM values, delay, jitter, and packet loss.

As the RTP packets are encrypted, following call quality metrics are not available for Lync or Skype for Business calls prioritized by media classification:

Client Name, Direction, Called to, MOS, MOS band, End-to-end Delay, jitter and packet loss.

 

File transfer and desktop sharing sessions are not prioritized by media classification. Upstream and downstream delay, jitter, and packet loss are not available for video sessions.

The show ucc commands displays statistics for media classification based Lync or Skype for Business ALG. For more information on the list of commands, see the ArubaOS Command-Line Interface Reference Guide. The UCC dashboard displays statistics for media classification based Lync or Skype for Business ALG. For more information on UCC dashboard, see UCC Dashboard.

Lync or Skype for Business Media Classification Limitations

The media classification logic is applicable only for UDP-based RTP traffic, which applies to real-time voice and video calls.

Lync or Skype for Business app-sharing and file-transfer sessions are not identified and prioritized by media classification.

When using media classification, UCC score, jitter, delay, and packet loss is calculated only for voice RTP streams. These metrics are not available for video streams.

Media classification does not work in split-tunnel forwarding mode.

When VoIP calls are prioritized using media classification, end-to-end call quality metrics such as Mean Opinion Score (MOS), delay, jitter, and packet loss are not available.

Media classification does not work when the managed device is performing a network address translation for media traffic. Media classification continues to work if the media traffic is subjected to Network Address Translation (NAT) beyond the managed device.

Lync or Skype for Business SDN API Support in Mobility Master

To take advantage of UCC Lync or Skype for Business ALG, it is recommended to use the Lync or Skype for Business SDN API. ArubaOS 8.x supports Lync or Skype for Business SDN API 2.0, 2.1.1, 2.2, and 2.4.1. Lync or Skype for Business SDN API works with Microsoft Lync or Skype for Business server to export details about voice or video calls, app-sharing, and file-transfer to Mobility Master. The communication between the Lync or Skype for Business SDN API and Mobility Master occurs over HTTP or HTTPS.

In ArubaOS 6.x, Lync or Skype for Business SDN Manager sends the call information messages like start of call, interim update, and end of call to all the preconfigured local controllers though the clients are not present on the respective local controller. In ArubaOS 8.x, Lync or Skype for Business SDN Manager sends this information to Mobility Master only and not the managed devices. This reduces the network traffic originating from the Lync or Skype for Business SDN Manager and also relieves the managed devices of processing unwanted call information originating from the Lync or Skype for Business SDN Manager.

In master controller mode, Lync or Skype for Business SDN Manager sends the call information messages like start of call, interim update, and end of call to all the managed devices. The communication between the Lync or Skype for Business SDN API and managed devices occurs over HTTP or HTTPS.

Lync or Skype for Business SDN API Configuration

The Lync or Skype for Business ALG should be configured from the /mm node hierarchy of Mobility Master. The ALG is enabled by default.

 

In master controller mode, Lync or Skype for Business ALG must be configured from the /md node hierarchy of the master controller. The ALG is enabled by default.

In the WebUI

The following procedure configures the Lync or Skype for Business ALG using the WebUI:

1. In the Mobility Master node hierarchy, navigate to Configuration > System > Profiles > All Profiles.
2. Expand UCC and click Skype4B ALG Configuration.
3. In the Skype4B ALG Configuration section, configure the settings described in Table 4.
4. Click Submit.
5. Click Pending Changes.
6. In the Pending Changes window, select the check box and click Deploy changes.

Table 4: Lync or Skype for Business ALG Configuration Parameters

Parameter

Description

Skype4B ALG Support

Enables the Microsoft® Lync or Skype for Business ALG. The ALG is enabled by default.

Skype4B SDN Over http/https

You can set the Lync or Skype for Business SDN listen protocol over HTTP or HTTPS. On configuring this, the Lync diagnostic information will be received over HTTP or HTTPS. The default value is HTTP.

Voice Priority

Configures the DSCP value for the voice session. The default value is 46.

Video Priority

Configures the DSCP value for the video session. The default value is 34.

App-sharing Priority

Configures the DSCP value for the app-sharing session. The default value is 34.

In the CLI

The following commands configure the Lync or Skype for Business ALG using the CLI:

(host) [mm] (config) #ucc skype4b

(host) ^[mm] (Skype4B ALG Configuration) #enable

(host) ^[mm] (Skype4B ALG Configuration) #priority {app-sharing <app-sharing>| video <video>|voice <voice>}

(host) ^[mm] (Skype4B ALG Configuration) #sdn {http|https}

(host) ^[mm] (Skype4B ALG Configuration) #write memory

The following commands display the Lync or Skype for Business ALG configuration using the CLI:

(host) [mynode] #show ucc skype4b

 

Sat Jun 25 03:25:43.429 2016

 

Skype4B ALG Configuration

-------------------------

Parameter Value Set

--------- ----- ---

Skype4B ALG Support Enabled

Skype4B SDN Over http/https https

voice priority 46

video priority 34

app-sharing priority 34

Lync or Skpe for Business SDN Manager Configuration

Lync Dialog Listener must be installed and configured on the Lync front-end server. Lync or Skype for Business SDN Manager must be installed on a separate Windows 2008 or 2012 server (not on the Lync front-end server). If there are multiple front-end servers, Lync Dialog Listener should be installed on each server and configured to point at the Lync or Skype for Business SDN Manager. On Lync SDN Manager, the Mobility Master information needs to be configured.

 

In master controller mode, the managed device information needs to be configured on Lync or Skype for Business SDN Manager.

Depending on the transport mode configured in the Lync or Skype for Business SDN Manager, the same transport mode (HTTP or HTTPS) should be configured in the Configuration > System > Profiles > All Profiles > UCC > Skype4B ALG Configuration page of WebUI. The following configuration is a snippet of the Lync or Skype for Business SDN Manager configuration:

 

Lync/Skype for Business SDN Manager is a third-party product. The following configuration is an example and provided for illustration purposes only. If you plan to use this sample in your environment, ensure that the sample meets your IT guidelines. By running this sample configuration, you acknowledge that Aruba is in no way liable for any loss, damage, or problems arising from running this sample configuration.

 

Read and follow the installation instruction PDF that comes with the SDN API software to install Lync or Skype for Business Dialog Listener and Lync or Skype for Business SDN Manager.

<Configuration Version="2.0" culture="en-US" Kind="Subscriber" Identifier="Aruba" LastModified="2015-10-27T13:06:59.7745572Z">

<parameter key="submituri">http://10.15.16.123:32000</parameter>

<parameter key="outputschema">D</parameter>

<parameter key="clientcertificateid"></parameter>

<parameter key="domainfilters"></parameter>

<parameter key="subnetfilters"></parameter>

As displayed in the above configuration, the Mobility Master IP address is added to the Lync or Skype for Business SDN Manager instead of the managed device IP address and the port number has to be 32000 which is a fixed port and not a configurable parameter on Mobility Master. The general format of the submit Uniform Resource Identifier (URI) is as follows:

http[s]://<Mobility Master-IP or fqdn>:32000

 

In master controller mode, the IP address of the managed device is added to the Lync or Skype for Business SDN Manager.

IP Session ACL and User Role Configuration

The following procedure configures a user-role for Lync or Skype for Business clients. In addition, the procedure provides steps to add an ACL to permit TCP traffic for app-sharing and file-transfer sessions.

In the WebUI

The following procedure configures the IP session ACL to permit TCP traffic for app-sharing and file-transfer sessions using the WebUI:

1. In the Managed Network node hierarchy, navigate to Configuration > Roles & Policies.
2. In the Roles tab, select an existing role.
3. In the Roles > <custom-role> section, click Show Advanced View.
4. In the Policies tab, click the + icon. The Add Policy pop-up window opens.
5. In the Add Policy window, select the Add existing session policy option.
6. In the Policy Name drop-down list, select the skype4b-acl policy.
7. In the Policy type drop-down list, select Session.
8. Click Submit.
9. Repeat steps 4 and 5.
10. In the Policy Name drop-down list, select the voip-application-acl policy.
11. In the Policy type drop-down list, select Session.
12. Click Submit.
13. Click Pending Changes.
14. In the Pending Changes window, select the check box and click Deploy changes.

In the CLI

The following commands configure the IP session ACL to permit TCP traffic for app-sharing and file-transfer sessions using the CLI:

(host) [md] (config) #user-role S4B-role

(host) ^[md] (config-submode) #session-acl skype4b-acl

(host) ^[md] (config-submode) #session-acl voip-applications-acl

(host) ^[md] (config-submode) #write memory

Lync or Skype for Business Troubleshooting

The following section describes the step-by-step procedure to troubleshoot Lync or Skype for Business ALG:

 

In master controller mode, the show commands must be executed on the managed device.

1. Ensure that the global prerequisites to enable UCC in ArubaOS 8.x is configured. For more information, see Prerequisites to Enable UCC.
2. Connect clients to the SSID; launch the Lync 2010 or 2013 or Skype for Business application; and make audio and video calls between them.
3. Make a few calls between clients. Execute the show ucc client-info and show ucc call-info cdrs commands and also access the UCC dashboard on the WebUI to view Lync or Skype for Business call statistics and prioritization.

(host) [mm] #show ucc client-info

 

Client Status:

--------------

Client IP Client MAC Client Name ALG Server(IP) Registration State

--------- ---------- ----------- --- ---------- ------------------

10.16.4.76 00:24:d7:40:c0:a0 Derek Skype4B REGISTERED

10.16.4.71 00:21:6b:9d:f2:74 Allen Skype4B REGISTERED

 

Call Status AP Name Flags Device Type Home_Agent Foreign_Agent

----------- ------- ----- ----------- ---------- -------------

In-Call 2_205 Win 7 10.16.4.9 NA

In-Call 2_205 Win 7 10.16.4.9 NA

 

Total Client Entries:2

Flags: V - Visitor, A - Away, W - Wired, R - Remote, E - External

 

(host) [mm] #show ucc call-info cdrs

 

Help: [C] - Metric calculated at the Controller

[A] - Metric calculated at the AP

CDR:

----

CDR ID UCC Call ID Client IP Client MAC Client Name ALG

------ ----------- --------- ---------- ----------- ---

4 2 10.16.4.71 00:21:6b:9d:f2:74 Derek Skype4B

3 2 10.16.4.76 00:24:d7:40:c0:a0 Allen Skype4B

 

Dir Called to Dur(sec) Orig Time Status Reason Call Type

--- --------- -------- --------- ------ ------ ---------

OG Scott 6 Nov 27 08:44:45 ACTIVE NA Voice

IC Scott 6 Nov 27 08:44:45 ACTIVE NA Voice

 

Client Health UCC Score[C] UCC Score[A] MOS

------------- ------------ ------------ ---

80 70.80/Good 38.50/Fair 4.10/Good

85 77.88/Good 41.53/Fair 4.32/Good

 

Total Entries: 2

4. Execute the show datapath session table command on the managed device to verify if the calls are prioritized. A client with the Q flag indicates real-time analysis and a client with u flag indicates RTP analysis of upstream VoIP calls.

(host-mn) #show datapath session table 10.16.4.67

 

Datapath Session Table Entries

------------------------------

 

Flags: F - fast age, S - src NAT, N - dest NAT

D - deny, R - redirect, Y - no syn

H - high prio, P - set prio, T - set ToS

C - client, M - mirror, V - VOIP

Q - Real-Time Quality analysis

u - Upstream Real-Time Quality analysis

I - Deep inspect, U - Locally destined

E - Media Deep Inspect, G - media signal

r - Route Nexthop, h - High Value

B - Permanent, O - Openflow

L - Log

 

Source IP Destination IP Prot SPort DPort Cntr Prio ToS Age

--------------- --------------- ---- ----- ----- -------- ---- --- ---

10.16.4.72 10.16.4.67 17 20002 20008 0/0 5 40 0

10.16.4.72 10.16.4.67 17 20003 20008 0/0 0 0 1

10.16.4.67 10.16.4.72 17 20012 20039 0/0 6 46 0

 

Destination TAge Packets Bytes Flags

----------- ---- --------- --------- -----------

tunnel 22 24 398 151870 FHPTVQuI

tunnel 10 23 2 252 FCIE

local f2 0 0 FYHPTMCVBO

5. Execute the show ucc client-info command to verify if the Lync or Skype for Business clients are in In-Call state.

(host) [mm] #show ucc client-info

 

Client Status:

--------------

Client IP Client MAC Client Name ALG Server(IP) Registration State

--------- ---------- ----------- --- ---------- ------------------

10.16.4.76 00:24:d7:40:c0:a0 Derek Skype4B REGISTERED

10.16.4.71 00:21:6b:9d:f2:74 Allen Skype4B REGISTERED

 

Call Status AP Name Flags Device Type Home_Agent Foreign_Agent

----------- ------- ----- ----------- ---------- -------------

In-Call 2_205 Win 7 10.16.4.9 NA

In-Call 2_205 Win 7 10.16.4.9 NA

 

Total Client Entries:2

Flags: V - Visitor, A - Away, W - Wired, R - Remote, E - External

6. If Mobility Master uses Lync or Skype for Business SDN API, you can view the client name, called party, and end to end call quality for every Lync or Skype for Business calls on Mobility Master.
7. Execute the show ucc trace-buffer skype4b command to verify if Mobility Master is receiving and processing call information from the Lync or Skype for Business SDN manager.

(host) [mm] #show ucc trace-buffer skype4B

 

Skype4b Voice Client(s) Message Trace

----------------------------------

Client IP Client MAC Client Name Direction Event Time BSSID

--------- ---------- ----------- --------- ---------- -----

192.0.2.22 00:23:33:41:c8:b8 Alex OG Jan 3 11:24:34 9c:1c:12:8a:b5:50

192.0.2.26 24:77:03:9a:6c:dc John OG Jan 3 11:24:34 9c:1c:12:8a:b5:50

192.0.2.29 00:22:90:ea:9e:f1 Steve OG Jan 3 11:24:08 9c:1c:12:8a:b5:50

 

Called To Media Type AP Name Src Port Dest Port Call Status

--------- ---------- ------- -------- --------- -----------

Joe Voice/Video AP-225 50030/58008 50032/58006 Start of call

Mike Voice/Video AP-225 50032/58006 50030/58008 InCallQuality Update

Ken Voice AP-225 50026 50038 Call Quality Update

 

Num of Rows:3

8. Execute the show datapath session table command on the managed device and look for the O flag indicating if the RTP or RTCP-related flows is installed on the managed device using OpenFlow protocol.

(host-mn) #show datapath session table 10.16.4.67

 

Datapath Session Table Entries

------------------------------

 

Flags: F - fast age, S - src NAT, N - dest NAT

D - deny, R - redirect, Y - no syn

H - high prio, P - set prio, T - set ToS

C - client, M - mirror, V - VOIP

Q - Real-Time Quality analysis

u - Upstream Real-Time Quality analysis

I - Deep inspect, U - Locally destined

E - Media Deep Inspect, G - media signal

r - Route Nexthop, h - High Value

B - Permanent, O - Openflow

L - Log

 

Source IP Destination IP Prot SPort DPort Cntr Prio ToS Age

--------------- --------------- ---- ----- ----- -------- ---- --- ---

10.15.17.207 10.15.17.202 17 20004 20005 0/0 6 46 0

10.15.17.202 10.15.17.207 17 20005 20004 0/0 6 46 0

 

Destination TAge Packets Bytes Flags

----------- ---- --------- --------- -----------

local 1b 325 46131 FHPTCIVBO

local 3 347 41474 FHPTCIVBO

9. Execute the show ucc call-info cdrs to display the Call Detail Record (CDR) information or access the Dashboard > UCC page on the WebUI to verify if the calls are identified and prioritized.

(host) [mm] #show ucc call-info cdrs

 

Help: [C] - Metric calculated at the Controller

[A] - Metric calculated at the AP

CDR:

----

CDR ID UCC Call ID Client IP Client MAC Client Name ALG

------ ----------- --------- ---------- ----------- ---

4 2 10.16.4.71 00:21:6b:9d:f2:74 Derek Skype4B

3 2 10.16.4.76 00:24:d7:40:c0:a0 Allen Skype4B

 

Dir Called to Dur(sec) Orig Time Status Reason Call Type

--- --------- -------- --------- ------ ------ ---------

OG Ian 6 Nov 27 08:44:45 ACTIVE NA Voice

IC Ian 6 Nov 27 08:44:45 ACTIVE NA Voice

 

Client Health UCC Score[C] UCC Score[A] MOS

------------- ------------ ------------ ---

NA NA NA NA

NA NA

 

Total Entries: 2

10. Execute the show ucc statistics counter call client and show ucc statistics counter call global commands to view the different call metrics.

(host) [mm] #show ucc statistics counter call client

 

Per Client Call Counters:

-------------------------

Client IP Client MAC Call Originated Call Terminated Active Success

--------- ---------- --------------- --------------- ------ -------

10.16.4.76 00:24:d7:40:c0:a0 0 1 1 0

10.16.4.71 00:21:6b:9d:f2:74 0 1 1 0

10.16.4.79 00:24:d7:40:ff:a0 0 0 0 0

 

Failed Blocked Aborted Forwarded WMM AC-VI WMM AC-VO WMM-BK WMM-BE

------ ------- ------- --------- --------- --------- ------ ------

0 0 0 0 0 0 0 1

0 0 0 0 0 0 0 1

0 0 0 0 0 0 0 0

 

WMM (VI, VO, BK, BE):total calls with received priority

 

(host) [mynode] #show ucc statistics counter call global

 

System-wide Call Counters:

--------------------------

Call Originated Call Terminated Active Success Failed Blocked Aborted

--------------- --------------- ------ ------- ------ ------- -------

0 2 2 0 0 0 0

 

Forwarded WMM AC-VI WMM AC-VO WMM-BK WMM-BE

--------- --------- --------- ------ ------

0 0 0 0 2

 

Device Type Allocations:

------------------------

Device Type WMM AC-VI WMM AC-VO WMM-BK WMM-BE

----------- --------- --------- ------ ------

Win 7 0 0 0 2

 

WMM (VI, VO, BK, BE):total calls with received priority)

11. If the clients are not seen after executing the show ucc client-info command, verify the output by executing the show gsm debug channel ucc_client, show gsm debug channel ucc_session, and show gsm debug channel ip_user.

(host) [mm] #show gsm debug channel ucc_client

 

ucc_client Channel Table

------------------------

state uc_client_mac uc_client_ip uc_contact_name uc_server_name uc_client_flags

----- ------------- ------------ --------------- -------------- ---------------

ACTV 80:86:f2:40:b3:d4 10.15.88.247 1008 10.15.16.30 1

ACTV 80:86:f2:40:14:9c 10.15.88.245 1007 10.15.16.30 1

 

uc_reg_state uc_alg uc_entry_type uc_role uc_active_call uc_replicatorip

------------ ------ ------------- ------- -------------- ---------------

4 14 1 0 0 10.15.88.100

4 14 1 0 0 10.15.88.100

 

Total Num of Objects :2

Total Num of Active Objects :2

Total Num of Replicated Objects :0

 

(host) [mm] #show gsm debug channel ucc_session

 

ucc_session Channel Table

-------------------------

state uc_client_mac uc_client_ip uc_active_call

----- ------------- ------------ --------------

ACTV 80:86:f2:40:b3:d4 10.15.88.247 0

ACTV 80:86:f2:40:14:9c 10.15.88.245 0

 

Total Num of Objects :2

Total Num of Active Objects :2

Total Num of Replicated Objects :0

 

(host) [mm] #show gsm debug channel ip_user

 

ip_user Channel Table

---------------------

state v_repkey user_ip_address user_uuid ip_user_flags ip_user_timestamp

----- -------- --------------- --------- ------------- -----------------

REPL 3 10.15.88.245 001a1e01b2280000002f0064 0 181193397240

REPL 3 10.15.88.247 001a1e01b2280000002f0065 0 181193397370

 

Total Num of Objects :2

Total Num of Active Objects :0

Total Num of Replicated Objects :2

 

Total number of hosts: 3

12. Execute the show ucc rtpa-report command to view the Real-Time analysis report.

(host) [mm] #show ucc rtpa-report

 

Help: [C] - Metric calculated at the Controller

[A] - Metric calculated at the AP

[E] - Metric calculated End-to-End

 

Real-Time Analysis Call Quality Report

--------------------------------------

Client(IP) Client(MAC) Client(Name) ALG Jitter(usec)[C]

---------- ----------- ------------ --- ---------------

10.16.4.76 00:24:d7:40:c0:a0 Derek Skype4B 308.200

10.16.4.71 00:21:6b:9d:f2:74 Allen Skype4B 1119.080

 

Pkt-loss(%)[C] Delay(usec)[C] UCC Score[C] Jitter(usec)[A] Pkt-loss(%)[A]

-------------- -------------- ------------ --------------- --------------

0.000 118.000 92.346 36.840 0.000

0.000 35.400 76.210 101.679 0.000

 

Delay(usec)[A] UCC Score[A] Forward mode

-------------- ------------ ------------

344.610 40.116 tunnel

581.034 48.956 tunnel

 

Num Records:2

13. Execute the show openflow-controller hosts command to verify if the users are learned as OpenFlow hosts. If a host entry is not present for a user then flow will not be installed and the call will not be prioritized.

 

This command is not supported in master controller mode.

(host) [mm] #show openflow-controller hosts

 

Hosts

-----

IP MAC Wireless Dpid

-- --- -------- ----

10.15.88.245 80:86:f2:40:14:9c True 00:00:00:1a:1e:01:b2:28

10.15.88.235 ac:bc:32:78:33:a1 True 00:00:00:1a:1e:01:b2:28

10.15.19.39 00:0c:29:e4:88:93 false 00:00:00:0c:29:e8:b8:b9

 

Port No Port MAC

------- --------

21 ac:a3:1e:ca:7d:c0

19 d8:c7:c8:c9:23:8b

1 00:0c:29:e8:b8:ba

 

Total number of hosts: 3

14. Execute the show openflow-controller flow-table command on Mobility Master to verify if the flows are installed accurately.

 

This command is not supported in master controller mode.

(host) [mm] #show openflow-controller flow-table

 

Flow-table

----------

Dpid In Port Src Mac Dst Mac Ether Src IP

---- ------- ------- ------- ----- ------

00:00:00:0c:29:a1:de:01 * * * 0x800 222.173.190.239

00:00:00:0b:86:9a:16:77 * * * 0x800 222.173.190.239

 

Dst IP Proto Src Port Dst Port App Name Actions

------ ----- -------- -------- -------- -------

186.173.202.254 17 60000 60000 ucm output=controller

186.173.202.254 17 60000 60000 ucm output=controller

 

Total number of flows: 2

15. Execute the show openflow flow-table command on the managed device to check if the OpenFlows are getting programmed in the managed device.

 

This command is not supported in master controller mode.

(host-mn) #show openflow flow-table

 

Openflow Flow Table

-------------------

In Port Src Mac Dst Mac Ether Src IP Dst IP Proto

------- ------- ------- ----- ------ ------ -----

* * * 0x800 1.1.1.1 2.2.2.2 97

* * * 0x800 192.168.201.251 192.168.201.250 6

* * * 0x800 222.173.190.239 186.173.202.254 17

* * * 0x800 192.168.201.250 192.168.201.251 6

 

Src Port Dst Port Packets Bytes Actions

-------- -------- ------- ----- -------

* * 0 0 (Output:controller)

42017 42008 0 0 ,(Set IP ToS:34),(Set Vlan pcp:5),(Set AppID:2565)(Output:normal),(Write Flag:VH)

60000 60000 0 0 (Output:controller)

42008 42017 0 0 ,(Set IP ToS:34),(Set Vlan pcp:5),(Set AppID:2565)(Output:normal),(Write Flag:VH)

 

Total number of flows: 4

Cisco Jabber

Cisco Jabber is an enterprise collaboration application that supports the following protocols:

Voice call based on SIP signaling and media on RTP protocol

Video call based on SIP signaling and media on RTP protocol

Desktop-sharing based on SIP signaling and Binary Floor Control Protocol (BFCP) and media on RTP protocol

File-transfer based on TCP protocol

Cisco Jabber is an all-in-one application and significant number of customers deploy this application in open SIP mode without encryption. As Cisco Jabber deployment continues to gain a larger foothold in the collaboration space, it is important to ensure QoS for its delay-sensitive applications such that there is no perceptible difference in the user experience between wireless and wired networks.

Cisco Jabber Support in ArubaOS 8.x

ArubaOS 8.x provides QoS and visibility for voice, video calls, and desktop-sharing sessions made using an unencrypted version of the Cisco Jabber client. UCM can uniquely identify and prioritize Cisco jabber voice, video calls, and desktop-sharing sessions.

Open SIP ALG Enhancements

Cisco Jabber is an all-in-one application, enabling a user to perform functions in addition to audio and video calls. The existing SIP ALG is enhanced to support Cisco Jabber.

Parser Logic Enhancement

The current SIP ALG parser is capable of handling audio calls. The same is extended to handle video calls, app-sharing, hold or resume calls, conference calls, and call transfer.

Two additional ports, namely TCP 5222 and TCP 8443 are added to the default jabber-acl IP access list. These ports are required for the clients to register to the server.

(host) [md] (config) #ip access-list session jabber-acl

(host) [md] (config-submode) #any any tcp 5222 permit

(host) [md] (config-submode) #any any tcp 8443 permit

The jabber-acl IP access list is included in the voice user-role by default. If the administrator chooses to use any other custom user-role, the ACL should be added manually to the custom user-role.

Identification of Cisco Jabber Clients

A new configuration setting Jabber Server IP is introduced where an administrator can configure the Cisco Jabber server (Cisco Unified Communication Manager and Cisco Unified Presence Manager) IP address for client identification. You can configure up to 16 such IP addresses.

Cisco Jabber Configuration

You should enable DPI on the managed device for Cisco Jabber to work. For more information on enabling DPI, see Deep Packet Inspection Configuration.

The Cisco Jabber ALG should be configured from the /mm node hierarchy of Mobility Master. The ALG is enabled by default.

 

In master controller mode, Cisco Jabber ALG must be configured from the /md node hierarchy of the master controller. The ALG is enabled by default.

In the WebUI

The following procedure configures the Cisco Jabber ALG using the WebUI:

1. In the Mobility Master node hierarchy, navigate to Configuration > System > Profiles > All Profiles.
2. Expand UCC and click Jabber ALG Configuration.
3. In the Jabber ALG Configuration section, configure the settings described in Table 5.
4. Click Submit.
5. Click Pending Changes.
6. In the Pending Changes window, select the check box and click Deploy changes.

Table 5: Cisco Jabber ALG Configuration Parameters

Parameter

Description

Jabber ALG Support

Enables the Cisco Jabber ALG. The ALG is enabled by default.

Jabber Server IP

Configures the Cisco Jabber server (Cisco Unified Communication Manager and Cisco Unified Presence Server) IP address to uniquely identify Cisco Jabber clients.

NOTE: This is a mandatory configuration setting.

Voice Priority

Configures the DSCP value for the voice session. The default value is 46.

Video Priority

Configures the DSCP value for the video session. The default value is 34.

App-sharing Priority

Configures the DSCP value for the app-sharing session. The default value is 34.

In the CLI

The following commands configure the Cisco Jabber ALG using the CLI:

(host) [mm] (config) #ucc jabber

(host) ^[mm] (Jabber ALG Configuration) #enable

(host) ^[mm] (Jabber ALG Configuration) #priority {app-sharing <app-sharing>| video <video>|voice <voice>}

(host) ^[mm] (Jabber ALG Configuration) #server-ip <server-ip>

(host) ^[mm] (Jabber ALG Configuration) #write memory

The following commands display the Cisco Jabber ALG configuration using the CLI:

(host) [mynode] #show ucc jabber

 

Jabber ALG Configuration

------------------------

Parameter Value Set

--------- ----- ---

Jabber ALG Support Enabled

Jabber server ip 10.15.16.30

Jabber server ip 10.15.16.31

voice priority 46

video priority 34

app-sharing priority 34

Cisco Jabber Troubleshooting

The following section describes the step-by-step procedure to troubleshoot Cisco Jabber ALG:

 

In master controller mode, the show commands must be executed on the managed device.

1. Ensure that the global prerequisites to enable UCC in ArubaOS 8.x is configured. For more information, see Prerequisites to Enable UCC.
2. Ensure that the Cisco Jabber server (Cisco Unified Communication Manager and Cisco Unified Presence Manager) IP addresses are configured under the Cisco Jabber ALG configuration.
3. Connect clients to the SSID.
4. Launch the Cisco Jabber application in the client and log in with the credentials to register with the Cisco Unified Communication Manager and Cisco Unified Presence Manager servers.
5. Execute the show ucc client-info command to verify if the ALG type is Jabber and the registration status is REGISTERED.

(host) [mm] #show ucc client-info

 

Thu Dec 03 08:48:09.077 2015

 

Client Status:

--------------

Client IP Client MAC Client Name ALG Server(IP) Registration State

--------- ---------- ----------- --- ---------- ------------------

10.15.88.235 ac:bc:32:78:33:a1 1019 Jabber 10.15.16.30 REGISTERED

10.15.88.247 80:86:f2:40:b3:d4 1008 Jabber 10.15.16.30 REGISTERED

 

Call Status AP Name Flags Device Type Home_Agent Foreign_Agent

----------- ------- ----- ----------- ---------- -------------

Idle AP-105 OS X 10.15.88.100 NA

In-Call AP-115 Win 7 10.15.88.100 NA

 

Total Client Entries:2

Flags: V - Visitor, A - Away, W - Wired, R - Remote, E - External

6. Start audio, video calls, and app-sharing sessions between Cisco Jabber clients.
7. Execute the show ucc client-info and show ucc call-info cdrs commands or access the Dashboard > UCC page on the WebUI to view Cisco Jabber call statistics and prioritization.

(host) [mm] #show ucc client-info

 

Thu Dec 03 08:48:09.077 2015

 

Client Status:

--------------

Client IP Client MAC Client Name ALG Server(IP) Registration State

--------- ---------- ----------- --- ---------- ------------------

10.15.88.235 ac:bc:32:78:33:a1 1019 Jabber 10.15.16.30 REGISTERED

10.15.88.247 80:86:f2:40:b3:d4 1008 Jabber 10.15.16.30 REGISTERED

 

Call Status AP Name Flags Device Type Home_Agent Foreign_Agent

----------- ------- ----- ----------- ---------- -------------

Idle AP-105 OS X 10.15.88.100 NA

In-Call AP-115 Win 7 10.15.88.100 NA

 

Total Client Entries:2

Flags: V - Visitor, A - Away, W - Wired, R - Remote, E - External

 

(host) [mm] #show ucc call-info cdrs

 

Thu Dec 03 08:48:23.827 2015

 

Help: [C] - Metric calculated at the Controller

[A] - Metric calculated at the AP

CDR:

----

CDR ID UCC Call ID Client IP Client MAC Client Name ALG Dir Called to

------ ----------- --------- ---------- ----------- --- --- ---------

140 53 10.15.88.247 80:86:f2:40:b3:d4 1008 Jabber OG 1019

138 53 10.15.88.247 80:86:f2:40:b3:d4 1008 Jabber OG 1019

 

Dur(sec) Orig Time Status Reason Call Type Client Health

-------- --------- ------ ------ --------- -------------

21164 Dec 3 02:55:39 ACTIVE NA Voice 0

21164 Dec 3 02:55:39 ACTIVE NA Voice 0

 

UCC Score[C] UCC Score[A] MOS

------------ ------------ ---

70.80/Good 38.50/Fair 4.10/Good

77.88/Good 41.53/Fair 4.32/Good

 

Total Entries:2

8. Execute the show ucc client-info command. If the ALG column displays SIP instead of Jabber, ensure that the Cisco Unified Communication Manager and Cisco Unified Presence Server IP addresses are added as part of the Cisco Jabber configuration in Mobility Master. In addition, verify if DPI is enabled on Mobility Master.
9. Execute the show ucc trace-buffer jabber command to verify if call signaling events such as establishing voice, video, desktop sharing, and file transfer are recorded.

(host) [mm] #show ucc trace-buffer jabber

 

Jabber Voice Client(s) Message Trace

------------------------------------

Client IP Client MAC Client Name Direction Event Time BSSID Msg

--------- ---------- ----------- --------- ---------- ----- ---

10.15.88.234 68:17:29:9f:b6:77 3002 Server-To-Client Jul 4 22:48:28 ac:a3:1e:27:dc:00 200_OK

10.15.88.234 68:17:29:9f:b6:77 3002 Server-To-Client Jul 4 22:48:27 ac:a3:1e:27:dc:00 100_TRYING

10.15.88.234 68:17:29:9f:b6:77 3002 Client-To-Server Jul 4 22:48:27 ac:a3:1e:27:dc:00 REGISTER

10.15.88.234 68:17:29:9f:b6:77 3002 Server-To-Client Jul 4 22:46:32 ac:a3:1e:27:dc:00 200_OK

10. If the clients are not seen after executing the show ucc client-info command, verify the output by executing the show gsm debug channel ucc_client, show gsm debug channel ucc_session, show gsm debug channel ip_user, and show openflow-controller hosts.

(host) [mm] #show gsm debug channel ucc_client

 

ucc_client Channel Table

------------------------

state uc_client_mac uc_client_ip uc_contact_name uc_server_name uc_client_flags

----- ------------- ------------ --------------- -------------- ---------------

ACTV 80:86:f2:40:b3:d4 10.15.88.247 1008 10.15.16.30 1

ACTV 80:86:f2:40:14:9c 10.15.88.245 1007 10.15.16.30 1

 

uc_reg_state uc_alg uc_entry_type uc_role uc_active_call uc_replicatorip

------------ ------ ------------- ------- -------------- ---------------

4 14 1 0 0 10.15.88.100

4 14 1 0 0 10.15.88.100

 

Total Num of Objects :2

Total Num of Active Objects :2

Total Num of Replicated Objects :0

 

(host) [mm] #show gsm debug channel ucc_session

 

ucc_session Channel Table

-------------------------

state uc_client_mac uc_client_ip uc_active_call

----- ------------- ------------ --------------

ACTV 80:86:f2:40:b3:d4 10.15.88.247 0

ACTV 80:86:f2:40:14:9c 10.15.88.245 0

 

Total Num of Objects :2

Total Num of Active Objects :2

Total Num of Replicated Objects :0

 

(host) [mm] #show gsm debug channel ip_user

 

ip_user Channel Table

---------------------

state v_repkey user_ip_address user_uuid ip_user_flags ip_user_timestamp

----- -------- --------------- --------- ------------- -----------------

REPL 3 10.15.88.245 001a1e01b2280000002f0064 0 181193397240

REPL 3 10.15.88.247 001a1e01b2280000002f0065 0 181193397370

 

Total Num of Objects :2

Total Num of Active Objects :0

Total Num of Replicated Objects :2

 

(host) [mm] #show openflow-controller hosts

 

Hosts

-----

IP MAC Wireless

-- --- --------

10.15.88.245 80:86:f2:40:14:9c True

10.15.88.235 ac:bc:32:78:33:a1 True

10.15.19.39 00:0c:29:e4:88:93 false

 

Dpid Port No Port MAC

---- ------- --------

00:00:00:1a:1e:01:b2:28 21 ac:a3:1e:ca:7d:c0

00:00:00:1a:1e:01:b2:28 19 d8:c7:c8:c9:23:8b

00:00:00:0c:29:e8:b8:b9 1 00:0c:29:e8:b8:ba

 

Total number of hosts: 3

11. Execute the show datapath session table command on the managed device to verify if the calls are prioritized. The ToS values should be set for this session, along with other flags like V, H, P, T, O.

(host-mn) #show datapath session dpi table | include V,Age

 

C - client, M - mirror, V - VOIP

r - Route Nexthop, h - High Value

 

Source IP Destination IP Prot SPort DPort Cntr Prio ToS Age Destination TAge Packets

------------ -------------- ---- ----- ----- ---- ---- --- --- ----------- ---- -------

10.15.89.250 10.15.89.231 17 26344 26112 0/0 5 34 0 local 31 173

10.15.89.250 10.15.89.231 17 26345 26113 0/0 5 34 0 local 31 76

10.15.89.250 10.15.89.231 17 23843 16767 0/0 6 46 0 local 31 2

10.15.89.231 10.15.89.250 17 16767 23843 0/0 6 46 0 local 31 5

 

Bytes SIDX AclVer Int-Flag PktsDpi UplnkVlan AppID

------ ----- ------ -------- ------- --------- -----------------------

185458 39b56 1632 2101 0 none alg-jabber-video (2570)

4420 4b952 1632 2101 0 none alg-jabber-video (2570)

220 87e7f 1632 2101 0 none alg-jabber-audio (2569)

624 a5a70 1632 2125 0 none alg-jabber-audio (2569)

 

AceIdx Flags User-MAC DpiTIdx

------ --------- ----------------- -------

0/561 FHPTCVBO 00:00:00:00:00:00 5e

0/561 FHPTMCVBO 00:00:00:00:00:00 84

0/560 FHPTMCVBO 00:00:00:00:00:00 8d

0/560 FHPTMCVBO 00:00:00:00:00:00 c5

Cisco Jabber Limitations

The following are the list of limitations in Cisco Jabber:

Visibility is not available for file transfer and a pure desktop-sharing sessions. In a pure desktop-sharing session, there is no simultaneous voice or video session going on.

In a stand-alone or master controller deployment, visibility is not available for desktop -sharing with or without simultaneous voice or video session.

If eXtensible Messaging and Presence Protocol (XMPP) signaling is not received for any reason before the SIP signaling from the Jabber client, the client will be identified as SIP and not Jabber.

Wi-Fi Calling

Wi-Fi calling service allows cellular users to make or receive calls using a Wi-Fi network instead of using the cellular network of the carrier. Wi-Fi calling allows users to place, receive calls, and text messages even when they are beyond a cellular coverage but having a Wi-Fi network coverage. Major carriers around the world support Wi-Fi calling service.

Wi-Fi Calling Support in ArubaOS 8.x

ArubaOS 8.x provides QoS for voice calls made using Wi-Fi calling. UCM can identify and prioritize calls made using Wi-Fi calling. UCM also provides visibility for all voice calls made using Wi-Fi calling.

Wi-Fi Calling Operation

At a high level, this is how Wi-Fi calling operates:

1. Wi-Fi Calling-capable handset initiates a DNS query to locate the evolved Packet Data Gateway (ePDG) of the carrier.
2. The handset establishes a persistent IPsec tunnel with ePDG.
3. Calls, text, and traffic for other services offered by the carrier are then carried over in this IPsec tunnel.

Some carriers use a standard FQDN format for ePDG that includes their Mobile Network Code (MNC) and Mobile Country Code (MCC). For example, T-Mobile uses ss.epdg.epc.mnc260.mcc310.pub.3gppnetwork.org. Others follow a different standard format. For example, AT&T uses epdg.epc.att.net. For a list of well known carrier DNS patterns, see Table 6.

Wi-Fi Calling Configuration

The Wi-Fi Calling ALG should be configured from the /mm node hierarchy of Mobility Master. This ALG is enabled by default.

 

In master controller mode, Wi-Fi Calling ALG must be configured from the /md node hierarchy of the master controller. The ALG is enabled by default.

In the WebUI

The following procedure configures the Wi-Fi Calling ALG using the WebUI:

1. In the Mobility Master node hierarchy, navigate to Configuration > System > Profiles > All Profiles.
2. Expand UCC and click Wi-Fi Calling ALG Configuration.
3. In the Wi-Fi Calling ALG Configuration section, configure the settings described in Table 6.
4. Click Submit.
5. Click Pending Changes.
6. In the Pending Changes window, select the check box and click Deploy changes.

Table 6: Wi-Fi Calling ALG Configuration Parameters

Parameter

Description

Wi-Fi Calling Support

Enables the Wi-Fi Calling ALG. The ALG is enabled by default.

Voice Priority

Configures the DSCP value for the voice session. The default value is 46.

DNS Pattern

dns-pattern–Configure the DNS pattern for the carrier. A maximum of 10 DNS patterns can be configured.

DNS patterns for known carriers are configured by default. Default built-in patterns are:

3 HK - wlan.three.com.hk

ATT - epdg.epc.att.net

Rogers - epdg.epc.mnc720.mcc302.pub.3gppnetwork.org

SmarTone - epdg.epc.mnc006.mcc454.pub.3gppnetwork.org

Sprint - primgw.vowifi2.spcsdns.net

T-Mobile - ss.epdg.epc.mnc260.mcc310.pub.3gppnetwork.org

Verizon - wo.vzwwo.com

If the ePDG FQDN of the carrier does not match with the default patterns, use this option to configure the DNS pattern for the carrier.

NOTE: The DNS IP address that Mobility Master learns for Wi-Fi Calling age out automatically, if there was no DNS query or response matching that IP for more than seven days.

service-provider–Add the service provider name for enhanced visibility.

In the CLI

The following commands configure the Wi-Fi Calling ALG using the CLI:

(host) [mm] (config) #ucc wificalling

(host) ^[mm] (WiFiCalling Configuration) #enable

(host) ^[mm] (WiFiCalling Configuration) #priority voice <voice>

(host) ^[mm] (WiFiCalling Configuration) #dns-pattern <dns-pattern> service-provider <service-provider>

(host) ^[mm] (WiFiCalling Configuration) #write memory

The following command displays the Wi-Fi Calling ALG configuration using the CLI:

(host) [mm] #show ucc wificalling

 

WiFiCalling Configuration

-------------------------

Parameter Value Set

--------- ----- ---

WiFiCalling Support Enabled

voice priority 46

dns pattern att.net ATT

Wi-Fi Calling Troubleshooting

The following section describes the step-by-step procedure to troubleshoot Wi-Fi Calling ALG:

 

In master controller mode, the show commands must be executed on the managed device.

1. Ensure that the global prerequisites to enable UCC in ArubaOS 8.x is configured. For more information, see Prerequisites to Enable UCC.
2. Connect the 'Wi-Fi Calling'-capable handset to the SSID.
3. Add the default wificalling-acl and voip-applications-acl ACLs to the user-role. By default, these ACLs are included in the voice user-role.
4. When the handset establishes a persistent IPsec tunnel with ePDG, it displays the Wi-Fi Calling icon.
5. Execute the show ucc dns-ip-learning command to verify if the ePDG IP address is learned.

(host) [mynode] #show ucc dns-ip-learning

 

DNS IP Learning:

----------------

IP Address Service Provider

---------- ----------------

208.54.85.108 T-Mobile

208.54.73.77 T-Mobile

208.54.70.110 T-Mobile

208.54.77.253 T-Mobile

208.54.75.2 T-Mobile

208.54.85.64 T-Mobile

208.54.73.76 T-Mobile

208.54.83.96 T-Mobile

208.54.85.111 T-Mobile

 

Total Entries:9

6. If the ePDG IP address is not learned, identify the FQDN of ePDG and add the DNS pattern of the carrier. FQDN may not be matching with any of the default, built-in DNS patterns.
7. Place a few calls and execute the show ucc client-info and show ucc call-info cdrs commands or access the Dashboard > UCC page on the WebUI to view Wi-Fi call statistics and prioritization.

(host) [mynode] #show ucc client-info

 

Client Status:

--------------

Client IP Client MAC Client Name ALG Server(IP) Registration State

--------- ---------- ----------- --- ---------- ------------------

10.15.17.208 fc:c2:de:6c:01:9c Client WiFi-Calling T-Mobile REGISTERED

10.15.17.206 d8:bb:2c:51:16:b2 Client WiFi-Calling T-Mobile REGISTERED

 

Call Status AP Name Flags Device Type Home_Agent Foreign_Agent

----------- ------- ----- ----------- ---------- -------------

In-Call 4-105-2 Android 10.15.16.168 NA

In-Call 2-105-1 Apple 10.15.16.168 NA

 

Total Client Entries:2

Flags: V - Visitor, A - Away, W - Wired, R - Remote, E - External

 

(host) [mynode] #show ucc call-info cdrs

 

Help: [C] - Metric calculated at the Controller

[A] - Metric calculated at the AP

 

CDR:

----

CDR ID UCC Call ID Client IP Client MAC Client Name ALG Dir Called to

------ ----------- --------- ---------- ----------- --- --- ---------

20 NA 10.15.17.206 d8:bb:2c:51:16:b2 NA WiFi-Calling NA NA

19 NA 10.15.17.208 fc:c2:de:6c:01:9c NA WiFi-Calling NA NA

18 NA 10.15.17.208 fc:c2:de:6c:01:9c NA WiFi-Calling NA NA

17 NA 10.15.17.206 d8:bb:2c:51:16:b2 NA WiFi-Calling NA NA

 

Dur(sec) Orig Time Status Reason Call Type Client Health

-------- --------- ------ ------ --------- -------------

82 Nov 24 23:21:31 ACTIVE NA Voice 44

88 Nov 24 23:21:25 ACTIVE NA Voice 78

93 Nov 24 23:16:19 SUCC Terminated Voice 71

228 Nov 24 23:14:32 SUCC Terminated Voice 51

 

UCC Score[C] UCC Score[A] MOS

------------ ------------ ---

NA NA NA

NA NA NA

NA NA NA

NA NA NA

 

Total Entries:4

 

UCC Score and MOS value are not available for Wi-Fi Calling calls.

8. Execute the show datapath session table command on the managed device to ensure that media classification flags (I & E) are set for IPsec session destined to the ePDG IP address.
9. When a Wi-Fi Calling call is identified, the I and E flags are removed from the IPsec session and appropriate ToS and 802.1p values are set for this session, along with other flags like V, H, P, T, O. This occurs on the managed device.
10. When the call ends, ToS and 802.1p values are removed for the IPsec session along with the V, H, P, T, O flags, and the I and E flags are set. For a list of flags, execute the show datapath session table command on the managed device.

Wi-Fi Calling Limitations

The following is a list of limitations in Wi-Fi Calling:

Wi-Fi Calling is not supported for clients in split-tunnel and bridge-forwarding mode.

WLAN and end to end quality metrics are not available for Wi-Fi Calling calls.

Wi-Fi Calling calls may get dropped in the event of a cluster failover.

Wi-Fi Calling calls do not get prioritized when Mobility Master is not reachable. This limitation does not apply for master controller deployment.

If a Wi-Fi Calling client roams from one managed device to another, subsequent calls may not get prioritized until the client does a DNS query for carrier ePDG.

Wi-Fi Calling is not identified and prioritized if NAT is enabled on the user VLAN. Wi-Fi Calling is not identified and prioritized if the corresponding sessions undergo NATting by the managed device.

UCC Dashboard

The UCC dashboard gives a complete view of the UCC deployment in Mobility Master. The UCC dashboard has two levels of displaying statistics:

UCC Dashboard Aggregated Display

UCC Dashboard Per Client Display

 

Centralized visibility of UCC statistics in the wireless network is not available in master controller mode. Log in to each managed device to view the UCC statistics local to logged in managed device.

UCC Dashboard Aggregated Display

The UCC Dashboard Aggregated Display shows an aggregated view of the UCC calls made in Mobility Master. The administrator can see a top-level view of the call quality assessment, and further drill-down into a specific view based on the analysis required.

Chart View

Navigate to Dashboard > UCC. The UCC page displays the overall health (in graphical format) of the UCC deployment in Mobility Master as shown in Figure 1.

Figure 1  UCC Dashboard

Each graphical section of the UCC dashboard is explained as follows:

Call Volume – This graph displays the total number of calls made based on the UCC application type. For example, SIP, Skype4B, SCCP, H.323, NOE, SVP, Vocera, FaceTime, Jabber, and WiFi-Calling. On clicking the APs tab, the graph displays the total number of calls per AP.

Call Quality – This graph displays the AP-to-Client call quality under the WLAN tab and the end-to-end quality including wired and wireless legs of the call under the End-to-End tab. The number of UCC calls are categorized by the following call quality:

Good

Fair

Poor

Not Available – In the WLAN tab, short duration voice calls (less than 60 seconds), video calls, and file-transfer session are categorized as Not Available. In the End-to-End tab, short duration voice calls (less than 60 seconds), video calls, file-transfer, and app-sharing sessions are categorized as Not Available.

The Trend tab displays the call quality over a period of time. The Devices tab categorizes the call quality based on the type of device. The APs tab displays the percentage of poor call quality per AP.

Call Quality vs. Client Health – This graph displays the correlation between the VoIP call quality and the VoIP client health of every UCC call. This graph displays the UCC score under the WLAN tab and MOS under the End-to-End tab.

 

When VoIP calls are prioritized using media classification like Lync or Skype for Business, Apple Facetime and Wi-Fi Calling, the End-to-End call quality is not available. In addition, WLAN-based quality metrics including Call Quality vs. Client Health scatter plot are not available.

Calls Per Device Type – This graph displays the calls made per device type. For example, Windows 7, Mac OS X, iPhone, or Android. On clicking the Table tab, Mobility Master lists the calls per device type in a tabular format. Any call that was made 6+ hours before is not listed here.

Roaming – Roaming status of UCC clients. The status can be:

No – Number of calls where the client did not roam to a new AP during an active call.

Yes – Number of calls where the client has roamed to a new AP during an active call.

QoS Correction – If the DSCP value of the RTP packets sent by the client differs from corresponding priority value configured for the application, Mobility Master corrects this value as per the SSID profile definition and classifies the call as QoS corrected. This graph displays the number of UCC calls where Mobility Master has corrected the WMM-DSCP value for such calls. The QoS correction is categorized as:

No – No WMM-DSCP value correction.

Yes – WMM-DSCP value corrected by Mobility Master.

Not Available – WLAN short duration calls (less than 60 seconds) is categorized as Not Available.

The Devices tab displays the QoS correction based on the type of device.

Call Details View

To display an aggregated list of all the UCC call data metrics in Mobility Master, navigate to the Dashboard > UCC page of the WebUI and click any of the following hyperlinks of the Web page:

Call Volume Details

Call Quality Details

Client Health Details

Device Details

Roaming Details

QoS Details

Figure 2 displays an aggregated list of all the UCC call data metrics on the managed devices.

Figure 2  Wireless Call List

VoIP calls made to or from clients outside Mobility Master are displayed in the External Call List pane. This pane lists all the external and wired client call CDRs. See Figure 3.

 

External call list is available only when Lync or Skype for Business SDN API is configured on Mobility Master.

Figure 3  External Call List

UCC Dashboard Per Client Display

On the Dashboard > Clients page of the WebUI, clicking the client IP hyperlink displays the details page of the client. Click the UCC tab. This tab displays an aggregated list of UCC call data metrics of a client. See Figure 4.

Figure 4  UCC Client Page

Figure 5 displays the statistics of all the VoIP calls made by a particular client. This graph displays the AP-to-Client metrics under the WLAN tab and the end-to-end quality including wired and wireless legs of the call under the End-to-End tab.

 

When VoIP calls are prioritized using media classification like Apple Facetime and Wi-Fi Calling, the End-to-End call quality is not available. In addition, WLAN-based quality metrics including Call Quality vs. Client Health scatter plot are not available.

Figure 5  All Calls

Figure 6 displays the VoIP call summary for a selected call of a client.

Figure 6  Selected Call Summary

Figure 7 displays the VoIP call details for a selected call of a client.

Figure 7  Selected Call Details

On the Dashboard > Usage page of the WebUI, the Call Quality vs. Client Health graph displays the correlation between the VoIP call quality (UCC-Band) and the VoIP client health of every UCC call. Figure 8 displays the Call Quality vs Client Health graph.

Figure 8  Call Quality vs. Client Health

UCC-AirWave Integration

The UCC-AirWave integration provides a multi-managed device visibility into the UCC solution across deployments. The Mobility Master sends raw UCC data using AMON periodically. AMP receives these AMON messages and uses this data to display user-friendly aggregated and per-client UCC statistics in AirWave. This helps the administrator to assess the overall health and troubleshoot UCC deployments in a multi-managed device environment. The UCC dashboard is supported in AirWave 8.0 onwards.

Follow these steps to get UCC data in AirWave from Mobility Master:

Enabling UCC Data Collection in AirWave

To enable UCC data collection in the AirWave WebUI:

1. Navigate to the AMP Setup > General tab of the AirWave WebUI.
2. In the Additional AMP Services section, change the Enable UCC Data Collection option to Yes.

Add AirWave as a Management Server in Mobility Master

You can add the default AirWave management server profile using the WebUI or CLI.

 

In master controller mode, add the default AirWave management server profile in the managed device.

In the WebUI

To add AMP as a management server in Mobility Master:

1. In the Mobility Master node hierarchy, navigate to Configuration > System > Airwave.
2. Click the Connect to airwave toggle switch.
3. In the Airwave IP address text-box, enter the AirWave server IP.
4. In the SNMP version drop-down list, select the appropriate version.
5. In the Community string drop-down list, select an existing community string or enter a new community string.
6. Click Submit.
7. Navigate to Configuration > System > More > General.
8. In MON Receivers, click the newly added AirWave server.
9. In Edit MON Receiver, enter the following detail:
a. In the Profile list drop-down list, select the default-amp profile.
10. Click Submit.
11. Click Pending Changes.
12. In the Pending Changes window, select the check box and click Deploy changes.

In the CLI

Execute the following command in the CLI to add AMP as a management server in Mobility Master:

(host)[mm] (config) #mgmt-server primary-server <primary-server-ip> profile default-amp

Enable UCC Monitoring in Mobility Master

By default, UCC monitoring is disabled in Mobility Master. You can enable this setting using the WebUI or CLI.

 

In master controller mode, enable UCC monitoring in the managed device.

In the WebUI

To enable UCC monitoring in Mobility Master:

1. In the Mobility Master node hierarchy, navigate to Configuration > System > Profiles.
2. In All Profiles, expand Controller Profile > Mgmt Config. Select the default-amp profile.
This example uses the default-amp profile.
3. In the Mgmt Config profile, select the UCC Monitoring check box.
4. Click Submit.
5. Click Pending Changes.
6. In the Pending Changes window, select the check box and click Deploy changes.

In the CLI

Execute the following command in the CLI to enable UCC monitoring:

(host) [mm] (config) #mgmt-server profile default-amp

(host) ^[mm] (Mgmt Config profile “default-amp”)#uccmonitoring-enable

Verify the Configuration

Execute the following command in the CLI to view the management server configuration profile:

 

In master controller mode, the show commands must be executed on the managed device.

(host) [mm] #show mgmt-server profile default-amp

 

Mgmt Config profile "default-amp" (Predefined (changed))

--------------------------------------------------------

Parameter Value

--------- -----

Stats Enabled

Tag Enabled

Sessions Enabled

Monitored Info - Add/Update Disabled

Monitored Info - Deletion Disabled

Monitored Info - Periodic Snapshot Disabled

Wireless IDS Event Info Disabled

Misc Enabled

Location Enabled

UCC Monitoring Enabled

AirGroup Info Disabled

Inline DHCP stats Enabled

Inline AP stats Enabled

Inline Auth stats Enabled

Inline DNS stats Enabled

Execute the following command in the CLI to view the current Mobility Master configuration with respect to the management server configuration profile:

 

In master controller mode, execute this command on the managed device.

(host) [mm] #show running-config | include mgmt-server

Building Configuration...

mgmt-server primary-server 192.0.2.1 profile default-amp

mgmt-server profile "default-ale"

mgmt-server profile "default-amp"

mgmt-server profile "default-controller"

The UCC-AirWave integration is complete.

UCC Limitations

Voice ALGs are not supported when voice clients are behind a NAT device.

Media classification does not work when user VLAN has IP NAT configured.

When using media classification or signaling protocols, UCC score, jitter, delay, and packet loss is calculated only for voice RTP streams. These metrics are not available for video streams.

Media classification does not work in split-tunnel forwarding mode.

When VoIP calls are prioritized using media classification, end-to-end call quality metrics such as Mean Opinion Score (MOS), delay, jitter, and packet loss are not available.

UCC score is calculated for voice calls and desktop-sharing sessions only.

For Lync or Skype for Business calls, MOS is generated only for voice streams. Lync or Skype for Business server does not generate MOS for video streams, desktop-sharing, and file-transfer sessions.

Upgrade UCM Loadable Service Module

Starting from ArubaOS 8.x, UCM runs as a loadable service module on Mobility Master. You can upgrade the UCM service module without rebooting Mobility Master. For more information, see Loadable Service Module.

 

Loadable service module is not supported in master controller mode.