1. Unified Communications Starface Ucc Client For Mac

Unified Communication and Collaboration Unified Communication and Collaboration This section describes the Unified Communication and Collaboration (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.0 Starting from ArubaOS 8.0, UCM runs as a loadable service module on Mobility Master. UCC supports various applications like Apple FaceTime, Alcatel-Lucent New Office Environment (NOE), Microsoft® Lync/Skype for Business, Cisco Jabber, Cisco Skinny Call Control Protocol (SCCP), SpectraLink Voice Priority (SVP), SIP, H.323, Vocera, and Wi-Fi Calling.

UCC application on Mobility Master implements the VoIP Application Layer Gateway (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 controller. 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.

Compatible with all major Unified Communications platforms and desk. 1 From Cisco Jabber version 11, Sennheiser headsets and speakerphones have fully integrated call control functionality. Starface UCC v6.0.2.12 or higher. Mitel MiCollab Client. Sennheiser Softphone Compatibility Guide (Mac).

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/Skype for Business SDN API. In ArubaOS 6.x, Lync/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.

• Ity in your business communications. To that end, STARFACE combines telephony with Unified Communication & Collaboration (UCC), providing all the bene˚ ts of a universal and user. STARFACE Mac Client STARFACE interconnection STARFACE initial configuration.
• This session will include a solution overview including how Jabber clients connect over the edge and register to Unified CM, the evolution of Expressway firewall traversal, options for IM & Presence services, and also how remote TelePresence endpoints can now register to Unified CM through Expressway.

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/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 Changes from ArubaOS 6.x The following is a list of UCC changes from ArubaOS 6.x to ArubaOS 8.0:  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.0, VoIP ALGs do not run from 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.  UCC running on Mobility Master uses OpenFlow infrastructure to receive signaling packets on Mobility Master, parse them, open sessions in the firewall, and prioritizes them.

 Visibility for all supported UCC applications are provided from the centralized Mobility Master dashboard.  ArubaOS 8.0 supports Cisco Jabber and Wi-Fi Calling.  Unlike ArubaOS 6.X, where ALGs use Wi-Fi Multimedia-Differentiated Services Code Point (WMM-DSCP) mappings in the WLAN SSID profile to set the Type of Service (ToS) for Real-time Transport Protocol (RTP) and Real-time Transport Control Protocol (RTCP), Mobility Master has ALG-specific Quality of Service (QoS) configurations. UCC Features Deprecated in ArubaOS 8.0 The following are the features deprecated in ArubaOS 8.0:  Basic Service Set (BSS) transition and force BSS transition.  Call count, bandwidth, and Traffic Specification (TSPEC)-based call admission control.  Classify media action in ACL for media classification – Microsoft® Lync/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 under the Configuration System Profiles All Profiles UCC profile.

 Lync/Skype for Business traffic control profile.  Web Server port configuration for Lync/Skype for Business SDN API. The Mobility Master 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 and managed devices. You must enable this in the /mm node hierarchy.

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.

In All Profiles, expand Controller Profile. Select openflow-controller. In openflow-controller, select the ofc-state check box. Click Pending Changes. 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.

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. In All Profiles, expand Controller Profile. Select Openflow-profile. In Openflow-profile, select the State check box.

In controller-ip, enter the Mobility Master IP address and port number. In bind-vlan, enter the user VLAN to the current list. Click Pending Changes. 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 (host) ^md(Openflow-profile) #bind-vlan (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 /md node hierarchy. 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. In the Roles tab, select an existing role. In the Roles section, click Show Advanced View. Under More, expand Network. In the Open flow drop-down list, select Enabled. Click Submit.

Navigate to Configuration System Profiles. In All Profiles, expand Wireless LAN  Virtual AP. Select the default profile.

This example uses the default profile. In Virtual AP profile, expand Advanced. Select the Openflow Enable check box. Click Pending Changes. 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 (host) ^md (config-submode)#openflow-enable (host) ^md (config-submode)#!

(host) ^md (config) #wlan virtual-ap (host) ^md (Virtual AP profile ') #openflow-enable (host) ^md (Virtual AP profile ') #write memory Management Server Profile Configuration Configure the management server profile. This enables AMON feeds to be sent to Mobility Master 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.

In All Profiles, expand Controller Profile. Select Mgmt Config. In Mgmt Config profile, click the + icon.

In the Profile name field, enter the name of the management server profile. Select the following check boxes: n Stats n Sessions n Monitored Info - Add/Update n Monitored Info - Deletion n Monitored Info - Periodic Snapshot 6. Navigate to Configuration System More. In MON Receivers, click the + icon. In New MON Receivers, enter the following details: a.

In the Server field, enter the Mobility Master IP address. In the Profile list drop-down list, select the newly created management server profile. Click Submit. Click Pending Changes. 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 (host) ^md (Mgmt Config profile ') #stats-enable (host) ^md (Mgmt Config profile ') #sessions-enable (host) ^md (Mgmt Config profile ') #monitored-info-enable (host) ^md (Mgmt Config profile ') #monitored-info-del-enable (host) ^md (Mgmt Config profile ') #monitored-info-snapshot-enable (host) ^md (Mgmt Config profile ') #!

(host) ^md (config) #mgmt-server primary-server profile (host) ^md (config) #write memory Deep Packet Inspection Configuration Enable Deep Packet Inspection (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. Expand Global Settings. In the Enable deep packet inspection drop-down list, select Enabled. Click Submit. Click Pending Changes.

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/RTCP traffic or an app-based ACL to permit media traffic. For more information, see.

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.

Unified Communications Starface Ucc Client For Mac

Expand Global Settings. In the Enable firewall visibility drop-down list, select Enabled.

Click Submit. Click Pending Changes. 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.0, 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. SpectraLink Voice Priority (SVP) 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. Expand UCC to configure various ALGs as described in.

Click Pending Changes. 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/Skype for Business ALG. The ALG is enabled by default. You can set the Lync/Skype for Business SDN listen protocol over HTTP or HTTPS.

The default Lync/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/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?