80
#ATM16 Integrating UCC on an Aruba access network Ashutosh Dash, Sr. Technical Marketing Engineer Steven Daugherty, Enterprise Communications Technical Specialist March 09, 2016 @ArubaNetworks |

Integrating Unified Communications and Collaboration on an Aruba Access Network

Embed Size (px)

Citation preview

#ATM16

Integrating UCC on an Aruba access networkAshutosh Dash, Sr. Technical Marketing EngineerSteven Daugherty, Enterprise Communications Technical Specialist 

March 09, 2016 @ArubaNetworks |

2

• UC Trends• UC Challenges• Why QoS is important• UC Apps on Aruba• Demo - Visibility & Troubleshooting• Design Best Practices

Agenda

3

UC Trends and Challenges

4#ATM16

UC Trends

@ArubaNetworks |

• Digital Workplace adoption with Wi-Fi

• Voice as a “standalone application” is going away• SIP, SCCP, SVP, H323, Vocera

• UCC is the “new wave” in IT• Skype for Business, Wi-fi calling, Jabber, FaceTime, Hangout etc.• Device mobility• Application anytime and anywhere

5#ATM16

UC challenges over Wireless

@ArubaNetworks |

• Diversity of Clients

• AV

• App incompatibility

• AP placement

• Channel Capacity

• AP Capacity

• Tx/Rx Characteristics

• Interference

• Mobility

• QoS on wireless• QoS on wire

• Queue overflows/drops

• Routing/path changes

• WAN

• UC server monitoring

6

Why QoS is important

7#ATM16

QoS Challenges

@ArubaNetworks |

– VO/VI traffic is going at lower priority– QoS incompatibility between Wired and Wireless– No End-to-end QoS

8#ATM16

QoS Challenges

@ArubaNetworks |

– VO/VI traffic is going at lower priority– QoS incompatibility between Wired and Wireless– No End-to-end QoS

9#ATM16

VO/VI traffic classified as BE

@ArubaNetworks |

• Lack of visibility to different application traffic types

INTERNET

VO: No DSCPVO: DSCP 56VI: DSCP 40BE: DSCP 24BK: DSCP 8

WMM-AC: BE DSCP 24 DSCP 24

Lack of Traffic Classification

10#ATM16

QoS Challenges

@ArubaNetworks |

– VO/VI traffic is going at lower priority– QoS incompatibility between Wired and Wireless– No End-to-end QoS

11#ATM16

WMM, 802.11p, DSCP

@ArubaNetworks |

• Legacy wired networks have DSCP 46 (EF) defined for VO• If client does upstream tagging of VO packets with DSCP 46, wireless driver on the client will send

the traffic on air as WMM-AC as VI instead of VO• It is recommended to follow DSCP values mandated by WMM standard to have end-to-end QoS

WMM DSCP

AC_VO 48-63

AC_VI 32-47

AC_BE 22-31

AC_BK 0-21

Priority 802.1P Priority

802.1P Designation

WMM Access Category

Lowest 1 BK AC_BK   2 BK

  0 BE AC_BE   3 EE

  4 CL AC_VI   5 VI

  6 VO AC_VO Highest 7 NC

12#ATM16

DSCP 46 (EF) behavior

@ArubaNetworks |

• Client wireless driver converts DSCP 46 to WMM-AC VI• AP sends the packet with DSCP 40 to the Controller• Controller classifies the traffic correctly and assigns DSCP 46 for VO

INTERNET

VO: DSCP 46 VO: DSCP 46VI: DSCP 40

WMM-AC: VI DSCP 40 DSCP 46

13#ATM16

DSCP 46 (EF) recommendation

@ArubaNetworks |

• Configure wireless clients with DSCP 48 – 63 for VO• On the HPE Aruba infrastructure, configure DSCP 46 for VO

INTERNET

VO: DSCP 56

VO: DSCP 46WMM-AC: VO DSCP 46 DSCP 46

14#ATM16

QoS Challenges

@ArubaNetworks |

– VO/VI traffic is going at lower priority– QoS incompatibility between Wired and Wireless– No End-to-end QoS

15#ATM16

End-to-End QoS

@ArubaNetworks |

UpstreamDownstream

INTERNET

Wireless LAN Edge LAN Core

Some clients can apply QoS on upstream direction. Packets are prioritized with WMM-AC over Air.

AP translates between WMM-AC and DSCP on upstream and downstream directions. LAN Edge needs to QoS aware. TOS is outside GRE header.

Stateful Firewall on the controller inspects the packets and assigns TOS flags. It can override TOS flags if set incorrectly.

LAN Core needs to QoS aware. Any packets going out from LAN core need to have correct QoS markings.

16

QoS Configuration and Troubleshooting on Aruba WLAN

17#ATM16

QoS Configuration on Aruba Controller

@ArubaNetworks |

18#ATM16

Wired QoS (Controller -> AP)

@ArubaNetworks |

19#ATM16

Wireless QoS (AP -> Wireless Client)

@ArubaNetworks |

20#ATM16

Controller Datapath

@ArubaNetworks |

21

UC Apps on Aruba

22#ATM16

UC Apps

@ArubaNetworks |

•Skype for Business•Wi-Fi calling•Jabber•FaceTime•Hangout

23

Skype for Business

24#ATM16@ArubaNetworks |

Types of SfB Deployments

• SfB On-Prem• SfB server farm is hosted on premise

• Hosted SfB• SfB server farm is hosted on a private cloud

• SfB Online• Multitenant SfB hosted in Office 365

25#ATM16@ArubaNetworks |

SfB On-Prem/Hosted Deployment • Benefits from all

SfB Server functionalities

• Maximum flexibility

• Interoperate with other on-premise investments

• Works with Exchange and SharePoint

Lync Federated Partners

Reverse Proxy

Lync Edge Server

Lync FE Server Pool/Lync SDN API Dialog Listener

Exchange Server

QoE Server/Monitoring

Aruba Mobility Controller

Lync SDN Manager

Active Directory

Internet

26#ATM16@ArubaNetworks |

SfB Online• Uptime Assurance• Using corporate

directory• Reduced administration

27#ATM16

Cloud PBX (worldwide)

CLOUD PBX VALUE PROPManage calling features right within Office 365Eliminate separate PBX systems and transition to the cloud

WHAT IS ITCall management features delivered from Office 365Enable call hold, transfer, voice mail, and call forwarding

HOW IS IT DIFFERENTIn the past, delivered through Skype for Business ServerConnected to customer’s on-premises infrastructureTo meet all Skype for Business Server scenarios by 2016At launch, it will meet most knowledge workers’ needs

28#ATM16

PSTN Calling (U.S. first)

PSTN VALUE PROPSubscribe to national and international calling plans from Office 365Use existing phone numbers or get new ones

WHAT IS ITPhone numbers and phone lines from Office 365Assign users new numbers or re-use existing ones

Sign users up for national or international calling plans

HOW IS IT DIFFERENTIn the past, we enabled this via connectivity to 3rd party PSTN providers

29#ATM16

PSTN Conferencing

PSTN CONFERENCING VALUE PROPSingle provider with >50 countries and regional languages supportedFlat rate per user with cumulative usage limits across tenant

WHAT IS ITSkype for Business Online users can schedule meetings with one or more dial-in access numbers and meeting conference IDs that are added in Outlook and Outlook Web App when a meeting is created

HOW IS IT DIFFERENTSkype for Business Online users get reservation-less conference bridges assigned to them that they can use to have audio-only meetings anytime.

30#ATM16

Skype for Business Online Call Flow Primer

31#ATM16

Peer to Peer - connectivity between peers

– Signaling from clients to Office 365

– Media directly between clients

– QoS possible for media traffic

Internet

Sign

allin

g

Office 365

Media

32#ATM16

Peer to Peer – no connectivity between peers

– Both signaling and media to Office 365

– QoS only to Internet perimeter

Internet

Sign

allin

gM

edia

Office 365

X

33#ATM16

On-premises PSTN Connectivity with on-premises client

– Signaling from client to Office 365

– Media from client to CCE

– QoS possible from gateway/SBC and CCE

– QoS between client and CCE

On Premises (no NAT or port filtering)

PSTN Gateway/SBC

Internet

Media

Skype for Business Cloud Conector

Edition

Office 365

PSTN

Con

necti

vity

34#ATM16

On-premises PSTN Connectivity with outside client

– Signaling from client to Office 365

– Media from client to CCE through edge facing interface

– QoS possible from gateway/SBC and CCE to Perimeter

On Premises (no NAT or port filtering)

PSTN Gateway/SBC

Internet

Signalling

Skype for Business Cloud Conector

Edition

Office 365

PSTN

Con

necti

vity

35#ATM16

Microsoft Calling Plans

– Signaling and media from client to Office 365

– QoS possible up to Internet perimeter

InternetOffice 365

36#ATM16

Conferencing

– Both Media and Signaling roundtrip to Office 365

– Up to 5 Audio/Video streams to each client

– QoS respected up to Internet perimeter

InternetOffice 365

37#ATM16

ExpressRoute

– Office 365 Connectivity Through MPLS

– Preservation of QoS Markings from Client to Client

– Preservation of QoS Marking from Client to Server

38#ATM16

Audio codec bandwidth

Audio codec Scenario Audio payload bit rate (KBPS)

Bandwidth audio payload and IP header only (Kbps)

Bandwidth audio payload, IP header, UDP, RTP and SRTP (Kbps)

RTAudio Wideband Peer-to-peer 29.0 45.0 57.0RTAudio Narrowband Peer-to-peer PSTN 11.8 27.8 39.8G.722 Conferencing 64.0 80.0 95.6G.722 Stereo Peer-to-peer Conferencing 128.0 144.0 159.6G.711 PSTN, Conferencing 64.0 80.0 92.0Siren Conferencing 16.0 32.0 47.6SILK Wideband Peer-to-peer 36.0 52.0 64.0SILK Wideband Peer-to-peer 26.0 42.0 54.0SILK Wideband Peer-to-peer 20.0 36.0 48.0SILK wideband/narrowband Peer-to-peer 13.0 29.0 41.0

39#ATM16

Video Codec Bandwidth

Video codec Resolution and aspect ratio Maximum video payload bit rate (Kbps)

Minimum video payload bit rate (Kbps)

H.264 320x180 (16:9)212x160 (4:3) 250 15

H.264/RTVideo 424x240 (16:9))320x240 (4:3 350 100

H.264 480x270 (16:9)424x320 (4:3) 450 200

H.264/RTVideo 640x360 (16:9)640x480 (4:3) 800 300

H.264 848x480 (16:9) 1500 400

H.264 960x540 (16:9) 2000 500

H.264/RTVideo 1280x720 (16:9) 2500 700

H.264 1920x1080 (16:9) 4000 1500

H.264/RTVideo 960x144 (20:3) 500 15

H.264 1280x192 (20:3) 1000 250

H.264 1920x288 (20:3) 2000 500

40#ATM16

Skype for Business SDN Support

– SDN Data Stream matches comprehensive Quality of Experience (QoE) Schema

– Key call quality metrics

– Mid-call Data

– Skype for Business Online capabilities are being expanded to include mid-call diagnostics and configuration via SDN

– Microsoft working closely with Aruba on delivering improved SDN capabilities

41#ATM16

Skype for Business SDN Stream Data

42#ATM16

Key call quality metrics

Bandwidth

Packet Loss

Latency

Jitter

Workstation (CPU, OS, etc.)

Microphone/Speaker

VPN Connectivity

Wifi/Wired/Access Point

External/Internal/Region

Conference Call/Point-to-Point

43#ATM16

When mid-call data is generated

. . . . . .Start Call

After Call

Mid Call

State change only (GOOD-POOR-BAD)

Every call(TIMER)

Every call (sometimes

more than one)(Occurs on every desktop client)

44#ATM16

A Poor state change

#TR22TSE210

45#ATM16

A Good state change

#TR22TSE210

46

Skype for Business on Aruba WLAN

47#ATM16@ArubaNetworks |

SfB Classification methods

• Heuristics• SDN API

48#ATM16

SfB Heuristics• Leverages DPI to identify & prioritize real time voice and video

traffic

• Ideal for SfB online deployments• On-prem and hosted deployments without SDN API can leverage heuristics

• AirWave aggregates network wide data for visibility

• SfB clients multiplexes RTCP and RTP packets over the same session. The packets are treated as RTCP packets instead of media packets. This broke original heuristics method.

• For Controllers, SfB Heuristics is supported from AOS v6.4.4 onwards

• For Instant APs, SfB Heuristics support is currently worked on. Heuristics for Lync clients are supported.

49#ATM16

SfB SDN API

• SfB server integrates with mobility controller using SDN API

• Real time call info is shared with mobility controller

• Controller leverages the info to apply QoS

• Ideal for On-Prem SfB deployments

• AirWave aggregates network wide data for visibility

50#ATM16

Call Details via SDN API • CALL START

• Caller/Callee, device, session, BW, time etc.

• PERIODIC INTERVALS• Instantaneous Call quality

• CALL END• Avg. call quality, time, microphone/speaker glitch rate

etc.

51#ATM16

Wi-Fi Call Quality Analysis

• UCC Score• Calculated by analyzing the RTCP/RTP information for related media flows over the wireless link• Delay, jitter and packet loss is also calculated • Computation performed for voice calls only

UCC Score Quality Indication

Greater than 70 Good quality perceived by the network

Between 30 and 70 Fair quality perceived by the network

Less than or equal to 30 Poor quality perceived by the network

52#ATM16

SDN API Evolution and AOS Compatibility MatrixSDN API Version

Backward Compatibility Flag AOS Version

Highlights

    Supported Non Supported  

2.0 TRUE

6.3.1.x, 6.4.1.x, 6.4.2.x , 6.4.3.x,6.4.4.x N/A * SDN API 2.0 can be configured to be compatible with the XML schema used in SDN API 1.2

2.0 FALSE 6.4.3.x,6.4.4.x6.3.1.x, 6.4.1.x, 6.4.2.x

* Configuration replication issue was addressed using LSM (Lync SDN Manager)* FE servers communicated to LSM. LSM sent SDN messages to Aruba controllers.* Call reporting functions were the same as SDN 1.2

2.1 N/A 6.4.3.x,6.4.4.x6.3.1.x, 6.4.1.x, 6.4.2.x

* LSM Cluster to load balance the clients and provide LSM redundancy* Subnet based filtering redirects SDN messages for clients to specific controllers to enhance scalability* In-call quality metrics reporting: call metrics are reported during the call

2.2 Schema C N/A 6.4.3.x, 6.4.4.x6.3.1.x, 6.4.1.x, 6.4.2.x

* Improved filtering of messages for subscribers based on domain name, SIP trunk name etc.* IPv6 support for subscriber filters

2.2 Schema D N/A 6.4.4.x6.3.1.x, 6.4.1.x, 6.4.2.x,6.4.3.x

* Support additional fields such as stream quality etc.

3.0 N/A TBD TBD* Bi-directional communication between Aruba controller and SfB server infrastructure

53#ATM16

Capabilities: Heuristics vs. SDN APIFeature Heuristics SDN API

Tagging and retagging WMM/DSCP values ü üDynamic identification/prioritization of SfB Voice/Video streams ü üPrioritization of Office365 traffic ü

Independent of SfB Infrastructure ü

Real-time call quality analysis using UCC score ü üCo-relation between UCC score and Wi-Fi health metrics on UCC dashboard ü üDynamic identification/prioritization of SfB desktop sharing, file transfer üEnd-to-end call metrics including MOS for diagnostics and troubleshooting üCo-relation between MOS and Wi-Fi health metrics on UCC dashboard üVisibility into dialled numbers and gateway endpoints üVisibility into endpoint speaker and microphone glitch rates üAccurate identification of 100% of all SfB traffic ü

54#ATM16

FAQs – Lync, SfB and SfB OnlineQuestion Comments

Are SfB clients compatible with Lync 2013 Server Yes

Are Lync 2013 clients compatible with SfB Server Yes

Is latest SDN API 2.2 compatible with Lync 2013 server Yes. It works for both Lync 2013 and SfB server infrastructure.

Is SDN API 2.2 compatible with AOS versions prior to v6.4.4Yes. SDN API 2.2 Schema-C is supported with earlier versions and Schema-D is supported with v6.4.4 onwards.

Is SfB online call classification/prioritization supportedYes. it is supported with Heuristics starting AOS v6.4.4 onwards. There is no SDN API support for SfB Online.

When will SDN API support SfB Online Coming soon

Is there any tool to get visibility to CDRs, call quality metrics and network health for a SfB Online deployment Call Quality Dashboard is available to Cloud PBX customers.

55

Wi-Fi calling

56#ATM16@ArubaNetworks |

Resurgence of Wi-Fi Calling

Native phone number Carrier text messaging Response to OTT Improved indoor coverage Roaming avoidance Complements VoLTE / IMS

57#ATM16

Wi-Fi Calling Detection

• Sequence of events • Gateway Learning Phase

• IPSEC Tunnel Establishment

• Media flow and Call Classification based on Heuristics

• Apply QoS on media traffic

Carrier Core Network

IMS (SIP)RTP

ePDG (IPSEC) P-GW

(IP)

Authenticate

DNS discovers ePDG IP address

IKEv2 establishes keys for IPSec tunnel from SIM & AAA

SIP stack on handset registers with SIP server (IMS)

Call setup, RTP media session, call teardown

Inside IPSec tunnel

• Target Support release AOS v6.5

58#ATM16

Global CDRs

59

Jabber

60#ATM16@ArubaNetworks |

What is Jabber

–Enterprise Application that supports IM, Voice, Video, Desktop Sharing & File Transfer– Voice, Video & Desktop Sharing is based on RTP– File Transfer is based on TCP

–Available in two different flavors– Cisco Jabber Enterprise Version (common in

enterprise)– Cisco Jabber Video

–Enterprise version runs on SIP or SIPs

61#ATM16@ArubaNetworks |

Aruba UC solution for Jabber

Wi-Fi optimization to make UC user experience cellular like

1

Resiliency and guaranteed QoS for Jabber in the presence of other traffic

2

Network health (RF, WAN) characterization & Correlation

Network Analytics for proactive trends and patterns

5

4

Built-in real time Visibility3 Reporting, alerts and

triggers 5

62#ATM16

Jabber Aware Aruba WLAN

–Majority of Jabber deployments use open SIP mode

–Existing SIP ALG has been enhanced to support Jabber calls– Special characteristics of Jabber calls

tracked to provide visibility

–Ability to identify Voice, Video and Desktop Sharing

–Ability to apply QoS respectively–Target Support release AOS v8.0

Jabber caller Jabber Callee

Signaling

Media

63#ATM16

Call Detail Records

64

FaceTime

65#ATM16@ArubaNetworks |

Classification and Prioritization

– Built-in FaceTime ALG– Uses heuristics method to classify FaceTime Audio/Video calls– Controller Stateful firewall applies QoS on FaceTime traffic– Visibility and Troubleshooting on UCC Dashboard

66#ATM16@ArubaNetworks |

Configuring FaceTime

ip access-list session facetime  any any svc-http  permit  any any svc-https  permit  any network 17.0.0.0 255.0.0.0 tcp 5223  permit classify-media  any any udp 3478 3498  permit  any any udp 16384 16387  permit  any any udp 16393 16402  permit!

67#ATM16@ArubaNetworks |

Controller Datapath for FaceTime call

68

Hangout

69#ATM16@ArubaNetworks |

Classification and Prioritization

– No built-in ALG for Hangout– Define ACLs to classify and prioritize hangout traffic– No advanced visibility of Hangout CDRs on UCC Dashboard

70#ATM16@ArubaNetworks |

Hangout ACL

ip access-list session hangout any any udp 19302 19309 permit queue high tos 56 dot1p-priority 7

any any tcp 19305 19309 permit queue high tos 56 dot1p-priority 7

!

For additional port details for Hangout go here –

https://support.google.com/a/answer/1279090?hl=en

71

DEMO

UCC Troubleshooting

72#ATM16@ArubaNetworks |

UCC Dashboard

73#ATM16@ArubaNetworks |

Call Detail Records (CDR)

74#ATM16@ArubaNetworks |

Per User Call Records

75#ATM16@ArubaNetworks |

Per User Call Records

76

Deployment Best Practices

78#ATM16

Deployment Recommendations

@ArubaNetworks |

Feature Recommended Value

AP Placement Around 50 ft. apart

Transmit Power (dBm)

Open Office:5 GHz: Min 12/Max 152.4 GHz: Min 6/Max 9Walled office or Classroom:5 GHz: Min 15/Max 182.4 GHz: Min 6 /Max 9

Channels80 MHz channels can be used in green field deployments.U-NII-2 and U-NII-2e (DFS) channels must be used when operating on 80 MHz channels.Remove channel 144 from list.

AirTime Fairness Fair Access

Data Rates802.11 a & g: Basic rates:12,24802.11 a & g transmit rates:12,24,36,48,56

Beacon Rate (Mbps) By default lowest For both 802.11a and gradio use 12 or 24.

Convert Broadcast ARP to Unicast Enable

Drop Broadcast and Multicast Enable

Multicast rate optimization Enable

79#ATM16

Join Aruba’s Titans of Tomorrow force in the fight against network mayhem. Find out what your IT superpower is.

Share your results with friends and receive a free superpower t-shirt.

www.arubatitans.com

Thank [email protected]@microsoft.com