EMEA Tech to Tech February 2016 Polycom Global Services

©

Polycom, Inc. All rights reserved.

Agenda • Polycom® RealPresence Debut™:

Andy Skellon

− Cloud Mode − Provisioning: − − − − −

Polycom® RealPresence® Cloud-enabled services Polycom® Zero Touch Provisioning (ZTP) solution Polycom® RealPresence® Resource Manager BroadSoft DMS FTP/FTPS server

• Polycom® RealPresence Trio™ 8800 and RealPresence Trio™ Visual+ − Configuration and troubleshooting for Skype for Business /

Microsoft®

Vikash Seesaha

Lync®

• Analysis of Polycom® RealConnect™ and ContentConnect™ call flows

Malcolm Jones

− Call flow between key elements of Polycom® RealConnect and ContentConnect infrastructure and Skype for Business/Microsoft Lync; showing major events in the log files and fault finding

• General Technical Update, including latest hot fixes, known issues etc. ©

Polycom, Inc. All rights reserved.

2

Graeme Arnott

The Admin Guide Refers to ‘Real Presence Cloud Mode’ – What is it?

©

Polycom, Inc. All rights reserved.

3

©

Polycom, Inc. All rights reserved.

4

Debut is enabled by Serial Number

©

Polycom, Inc. All rights reserved.

5

Enterprise grade cloud-based Video as a Service offer, gives many of the benefits of Video Collaboration without the onpremises setup, deployment and operational costs

• Delivers a set of visual collaboration capabilities for both the individual user as well as groups of users through person-to-person calling or virtual meeting rooms (VMRs) that connect a variety of video and audio endpoints together through a cloud-based service model • Per VMR tiered pricing plans • Customer portal with conference control, instructions, documentation, reporting and FAQs for customers • Free software clients including RealPresence® Desktop, RealPresence® Mobile and web access via Web RTC, any standards based endpoint and Microsoft Lync/Skype for Business Clients

©

Polycom, Inc. All rights reserved.

6

• A cloud solution works well for: •

Customers wanting to introduce high quality video collaboration to their organizations at a lower up-front cost

•

Customers with RealPresence® Platform already deployed that are looking to extend their capacity via a subscription plan Per VMR tiered pricing plans

• Key benefits include:

©

•

OPEX model with no upfront costs

•

Frequent software upgrades with additional features and new functionality

•

IT prioritization – the ability for IT to focus on core business requirements

•

Ease of use – faster time to adoption

•

Investment protection – seamless integration into existing UC environments like Microsoft Lync

•

Interoperable with standards based endpoints

Polycom, Inc. All rights reserved.

7

©

Polycom, Inc. All rights reserved.

8

©

Polycom, Inc. All rights reserved.

9

©

Polycom, Inc. All rights reserved.

10

©

Polycom, Inc. All rights reserved.

11

©

Polycom, Inc. All rights reserved.

12

©

Polycom, Inc. All rights reserved.

13

Polycom® RealPresence Debut™ Provisioning Services

©

Polycom, Inc. All rights reserved.

Provisioning Services • Polycom® RealPresence® Cloud • Polycom® Zero Touch Provisioning • Polycom® RealPresence® Resource Manager • BroadSoft BroadWorks® Device Management System (DMS) • FTP/FTPS Server

©

Polycom, Inc. All rights reserved.

15

How does Polycom RealPresence Debut know where the provisioning server is? • If RealPresence Debut is in Cloud Mode, the address of Provisioning Service is hard coded in the software • In Enterprise Mode configured for Auto, if RealPresence Debut is unable to detect a provisioning service through DHCP, the RealPresence Debut automatically tries to connect to the Polycom Zero-Touch Provisioning Server @ ztp.polycom.com to provision the system • DHCP Option 66 (default – can be manually defined) • Provisioning Server Address Format − Polycom RealPresence Resource Manager https://:@ip_address or https://ip_address − BroadSoft BroadWorks DeviceManagement System (DMS) https://:@ip_address − FTP/FTPS ftp://:@ip_address or ftps://:@ip_address ©

Polycom, Inc. All rights reserved.

16

©

Polycom, Inc. All rights reserved.

17

©

Polycom, Inc. All rights reserved.

18

Associate a Profile (which can contain an XML format txt file) with a particular MAC address

©

Polycom, Inc. All rights reserved.

19

©

Polycom, Inc. All rights reserved.

20

©

Polycom, Inc. All rights reserved.

21

©

Polycom, Inc. All rights reserved.

22

©

Polycom, Inc. All rights reserved.

23

©

Polycom, Inc. All rights reserved.

24

RealPresence Debut does not support enabling both H.323 and SIP protocols If both protocols are enabled by a provisioning service during system provisioning, the SIP protocol has higher priority than the H.323 protocol and will be used when making calls. ©

Polycom, Inc. All rights reserved.

25

Pre-requisite • UCS 5.4.0AA is required for Microsoft Lync 2013 on-premises and Online • UCS 5.4.1AA is required for Microsoft Skype Business 2015 on-premises and Online • RealPresence Trio 8800 with a Microsoft Lync based profile and feature license • Polycom device with Microsoft Lync SKU is shipped with a Microsoft Lync based profile, a feature license and the Microsoft Lync qualified UC software

• Microsoft Lync 2013 with latest Cumulative Updates 5.0.8308.941 (December 2015) • Microsoft Skype for Business Server 2015 with latest Cumulative Updates 6.0.9319.102 (November 2015)

©

Polycom, Inc. All rights reserved.

26

Basic Call Flow Overview

Lync/SfB Front-End /AVMCU

Lync/SfB Client

Trio 8800

Visual +

INVITE 200 OK ACK INVITE 100 TRYING API VMR 200 OK

ACK

AUDIO STREAM

VIDEO STREAM

CONTENT STREAM (RDP)

©

Polycom, Inc. All rights reserved.

27

Create a Microsoft Lync/Skype for Business Room System Account 1. A Microsoft Lync/Skype for Business Room System or CsMeetingRoom account is recommended to maximize the benefits of the RDP content sharing with the RealPresence Trio 2. Microsoft Lync/Skype for Business System prompts content presenters to mute the microphone and speaker to avoid audio feedback 3. Use Credentials that never expire 4. Sets the mail processing rules to enable the Auto Accept Agent for the mailbox and control how the meetings will be displayed on the LRS screen

©

Polycom, Inc. All rights reserved.

28

Create a Microsoft Lync/Skype for Business Room System Account •

Use the Exchange Management Shell to set the following commands. New-Mailbox -Name "Trio Room01" -Alias "Trio.Room01" -UserPrincipalName "[email protected]" -sAMAccountN ame "Trio.Room01" -FirstName "Trio" -LastName "Room01" -OrganizationalUnit "ou=Skype fo Business Users,dc=voice,dc=lab"

[PS] C:\>Set-CalendarProcessing -Identity Trio.Room01 -AutomateProcessing AutoAccept -AddOrganizerToSubject $false -Remo vePrivateProperty $false -DeleteSubject $false

Set-Mailbox -Identity [email protected] MailTip "This room is equipped with a Polycom RealPresence Trio 8800, please make it a Lync Meeting to take advantage of the enhanced meeting experience.”

©

Polycom, Inc. All rights reserved.

29

Create a Microsoft Lync/Skype for Business Room System Account •

Use the Skype for Business Management Shell to set the following commands. Set-ADAccountPassword -Identity Trio.Room01

Enabled-ADAccount -Identity Trio.Room01

Enable-CsMeetingRoom -SipAddress "sip:[email protected]" -DomainController ls13dc01.voice.lab -RegistrarPool sfbpool01.plcmlabs.com -Identity Trio.Room01

Set-CsMeetingRoom -Identity "Trio.Room01" -EnterpriseVoiceEnabled $true -LineURI "tel:+441753431653;ext=31623" -DomainController "ls13dc01.voice.lab"

©

Polycom, Inc. All rights reserved.

30

Configure the Polycom Trio for Skype for Business Server 1. Users can sign in or out of the phone in one of two ways - Login Credentials - Use this to sign in with user credentials on the Lync Sign In screen. - PIN Authentication - Use this to sign in after a phone restart or reboot or when using DHCP Option 43

2. The Web Configuration Utility (WebGUI) is disabled by default in Lync Profile - Web Server can be enabled  Phone Menu  Settings  Advanced  Administration Settings  Web Server Configuration

©

Polycom, Inc. All rights reserved.

31

Configure the Polycom Trio for Skype for Business Server 1. Smart Login determines if a network environment is capable of PIN Authentication 2. When STS-URI is not configured via DHCP Option 43 or manually, Pin Authentication is disabled for the phone or in the Web Configuration Utility

Phone User Interface

Web Configuration Utility

©

Polycom, Inc. All rights reserved.

32

Sign-In with Login Credentials 1. Phone will automatically retrieve the custom Root CA through LDAP services 2. Phone will do a lookup on the AD domain to locate the LDAP server, download and install the certificate

3. Once the certificate has been installed, the phone will Sign-In to the Skype for Business server

©

Polycom, Inc. All rights reserved.

33

Sign-In with Pin Authentication 1. STS-URI should be manually configured or through DHCP 43 for Pin Authentication to work 2. It can be set in the “dhcp.option43.override.stsUri=https://domain-url:443//CertProv/CertProvisioningService.svc” parameter through a configuration file or through the webGUI --> Setting  Provisioning Server  DHCP Menu

3. The LRS Account should be set with a Pin

©

Polycom, Inc. All rights reserved.

34

Sign-In with Pin Authentication 1. Pin Authentication login will be available on the phone and the Web GUI once the STS-URI is set

©

Polycom, Inc. All rights reserved.

35

Calendaring Configuration 1. Users should sign-in with Login Credentials for calendaring to work 2. Phone will locate the Exchange CAS server through autodiscover. This can also be manually configured 3. Exchange Client details are shown on the Lync Status page

4. Mailbox notification appears when meetings are scheduled as below

©

Polycom, Inc. All rights reserved.

36

Troubleshooting 1. Check for DNS configuration when autodiscover is set on the phone. If possible configure the phone statically to rule out any DNS problem 2. Check for Root Certificate installation (i) LDAP services or (ii) DHCP Option 43 3. Use the phone logging to troubleshoot specific problems:(i) SIP, DNS, TLS and WebTicket for registration and connectivity issues (ii) Network Devices loggings for Visual + related issues (iii) Configuration and CURL for provisioning issues 4. Perform a reset to factory if the device is unresponsive or fail to pair with the Visual + 5. For any other problem, please collect the APP logs and the Phone Back UP configuration (PBU) file and contact Polycom Technical Support for investigation

©

Polycom, Inc. All rights reserved.

37

Resources 1. http://supportdocs.polycom.com/PolycomService/support/global/documents/support/setup_maint enance/products/voice/rp_trio_ag.pdf 2. http://supportdocs.polycom.com/PolycomService/support/global/documents/support/setup_maint enance/products/voice/rp_trio_lync_dg.pdf 3. http://supportdocs.polycom.com/PolycomService/support/global/documents/support/setup_maint enance/products/voice/rp_trio_sg.pdf 4. http://supportdocs.polycom.com/PolycomService/support/global/documents/support/setup_maint enance/products/voice/rp_trio_visual_sg.pdf 5. http://community.polycom.com/t5/VoIP/FAQ-VoIP-frequently-asked-questions/td-p/4205

©

Polycom, Inc. All rights reserved.

38

Introduction • RealConnect call flow • ContentConnect call flow • Logs on DMA, RPCS and CCS • Troubleshooting

©

Polycom, Inc. All rights reserved.

39

Basic RealConnect Flow

Lync Client

©

Polycom, Inc. All rights reserved.

Lync Front-End / AVMCU

RMX

40

DMA

Standards-based EP (SIP)

Lync Focus Conference including PSTN Conference ID

Lync Front-End / AVMCU

Lync Client

RMX

Create Meeting (1234)

INVITE 200 OK ACK

©

Polycom, Inc. All rights reserved.

41

DMA

Standards-based EP (SIP)

Standards-based EP calls DMA using Lync conf ID

Lync Front-End / AVMCU

Lync Client

RMX

Standards-based EP (SIP)

DMA

Create Meeting (1234)

INVITE 200 OK ACK INVITE (w/ SDP)

©

Polycom, Inc. All rights reserved.

42

DMA queries Lync FE for conference ID

Lync Front-End / AVMCU

Lync Client

RMX

Standards-based EP (SIP)

DMA

Create Meeting (1234)

INVITE 200 OK ACK

SERVICE (pstn-meetting-id 1234) 200 OK (w/ focus URI)

©

Polycom, Inc. All rights reserved.

43

INVITE (w/ SDP)

DMA instructs RPCS to create VMR and join Focus

Lync Front-End / AVMCU

Lync Client

Standards-based EP (SIP)

DMA

RMX

Create Meeting (1234)

INVITE 200 OK ACK

SERVICE (pstn-meetting-id 1234) 200 OK (w/ focus URI) API – Create VMR API – Add Party (w/ focus URI)

©

Polycom, Inc. All rights reserved.

44

INVITE (w/ SDP)

Standards-based EP joins VMR

Lync Front-End / AVMCU

Lync Client

Standards-based EP (SIP)

DMA

RMX

Create Meeting (1234)

INVITE 200 OK ACK

SERVICE (pstn-meetting-id 1234) 200 OK (w/ focus URI) API – Create VMR API – Add Party (w/ focus URI) (INVITE w/ SDP) (200 OK w/ SDP)

INVITE (w/ SDP)

200 OK (w/ SDP)

ACK

©

Polycom, Inc. All rights reserved.

45

RPCS joins Focus

Lync Front-End / AVMCU

Lync Client

Standards-based EP (SIP)

DMA

RMX

Create Meeting (1234)

INVITE 200 OK ACK

SERVICE (pstn-meetting-id 1234) 200 OK (w/ focus URI) API – Create VMR API – Add Party (w/ focus URI) (INVITE w/ SDP) (200 OK w/ SDP)

CCCP INVITE 200 OK (w/ XML)

INVITE (w/ SDP)

200 OK (w/ SDP)

ACK

©

Polycom, Inc. All rights reserved.

46

RPCS subscribes for Lync conference information

Lync Front-End / AVMCU

Lync Client

Standards-based EP (SIP)

DMA

RMX

Create Meeting (1234)

INVITE 200 OK ACK

SERVICE (pstn-meetting-id 1234) 200 OK (w/ focus URI) API – Create VMR API – Add Party (w/ focus URI) (INVITE w/ SDP) (200 OK w/ SDP)

CCCP INVITE 200 OK (w/ XML) SUBSCRIBE (w/ XML)

200 OK (w/ XML)

©

Polycom, Inc. All rights reserved.

INVITE (w/ SDP)

200 OK (w/ SDP)

ACK

47

RPCS sends INVITE with SDP to audio-video conference

Lync Front-End / AVMCU

Lync Client

Standards-based EP (SIP)

DMA

RMX

Create Meeting (1234)

INVITE 200 OK ACK

SERVICE (pstn-meetting-id 1234) 200 OK (w/ focus URI) API – Create VMR API – Add Party (w/ focus URI) (INVITE w/ SDP) (200 OK w/ SDP)

CCCP INVITE 200 OK (w/ XML) SUBSCRIBE (w/ XML)

200 OK (w/ XML) INVITE (w/ SDP) 200 OK (w/ SDP)

Polycom, Inc. All rights reserved.

200 OK (w/ SDP)

ACK

ACK

©

INVITE (w/ SDP)

48

Cascade established

Lync Front-End / AVMCU

Lync Client

Standards-based EP (SIP)

DMA

RMX

Create Meeting (1234)

INVITE 200 OK ACK INVITE (w/ SDP)

SERVICE (pstn-meetting-id 1234) 200 OK (w/ focus URI) API – Create VMR API – Add Party (w/ focus URI) (INVITE w/ SDP) (200 OK w/ SDP)

CCCP INVITE 200 OK (w/ XML) SUBSCRIBE (w/ XML)

200 OK (w/ XML) INVITE (w/ SDP) 200 OK (w/ SDP)

ACK

ACK

SVC RTP Media

©

Polycom, Inc. All rights reserved.

200 OK (w/ SDP)

AVC RTP Media

SVC RTP Media

49

ContentConnect Call Flow

Lync Front-End / AVMCU

©

Polycom, Inc. All rights reserved.

DMA

RMX

50

CSS Server

ContentConnect subscribes to DMA for conf notifications

Lync Front-End / AVMCU

DMA

RMX

CSS Server

REST API – Subscribe

©

Polycom, Inc. All rights reserved.

51

Every VMR generates conf notifications to CCS

Lync Front-End / AVMCU

DMA

RMX

CSS Server

REST API – Subscribe conference-notification

©

Polycom, Inc. All rights reserved.

52

If Focus URI is included, CCS joins Focus

Lync Front-End / AVMCU

DMA

RMX

CSS Server

REST API – Subscribe conference-notification INVITE (w/ CCCP xml)

INVITE (w/ CCCP xml) 200 (w/ CCCP xml)

©

Polycom, Inc. All rights reserved.

200 (w/ CCCP xml)

53

CCS joins VMR as SIP participant

Lync Front-End / AVMCU

DMA

RMX

CSS Server

REST API – Subscribe conference-notification INVITE (w/ CCCP xml)

INVITE (w/ CCCP xml) 200 (w/ CCCP xml) INVITE (w/ SDP)

200 (w/ SDP)

©

Polycom, Inc. All rights reserved.

54

200 (w/ CCCP xml) INVITE (w/ SDP)

CCS subscribes to AVMCU for conf info notifications

Lync Front-End / AVMCU

DMA

RMX

CSS Server

REST API – Subscribe conference-notification INVITE (w/ CCCP xml)

INVITE (w/ CCCP xml) 200 (w/ CCCP xml) INVITE (w/ SDP)

200 (w/ CCCP xml) INVITE (w/ SDP)

200 (w/ SDP) SUBSCRIBE (conference-info) 200 (w/ conference-info.xml)

©

Polycom, Inc. All rights reserved.

55

SUBSCRIBE (conference-info)

200 (w/ conference-info.xml)

CCS now receives NOTIFY messages with conf updates

Lync Front-End / AVMCU

DMA

RMX

CSS Server

REST API – Subscribe conference-notification INVITE (w/ CCCP xml)

INVITE (w/ CCCP xml) 200 (w/ CCCP xml) INVITE (w/ SDP)

200 (w/ CCCP xml) INVITE (w/ SDP)

200 (w/ SDP) SUBSCRIBE (conference-info) 200 (w/ conference-info.xml) NOTIFY (w/ conference-info.xml)

©

Polycom, Inc. All rights reserved.

56

SUBSCRIBE (conference-info)

200 (w/ conference-info.xml) NOTIFY (w/ conference-info.xml)

If application sharing has started, CCS joins the ASMCU

Lync Front-End / AVMCU

DMA

RMX

CSS Server

REST API – Subscribe conference-notification INVITE (w/ CCCP xml)

INVITE (w/ CCCP xml) 200 (w/ CCCP xml) INVITE (w/ SDP)

200 (w/ CCCP xml) INVITE (w/ SDP)

200 (w/ SDP) SUBSCRIBE (conference-info) 200 (w/ conference-info.xml) NOTIFY (w/ conference-info.xml)

Polycom, Inc. All rights reserved.

200 (w/ conference-info.xml) NOTIFY (w/ conference-info.xml)

INVITE (w/ SDP)

INVITE (w/ SDP)

200 OK (w/ SDP)

200 OK (w/ SDP) ACK

ACK

©

SUBSCRIBE (conference-info)

57

DMA Call History • DMA sees the following calls in a RealConnect scenario • Standards-based endpoint dialling in to VMR • ContentConnect connecting to VMR • ContentConnect connecting to Lync FE (Focus)

• Each individual ContentConnect sharing session (ASMCU) • We do NOT see the RPCS>AVMCU piece – this is direct with Lync

©

Polycom, Inc. All rights reserved.

58

DMA Call History – Events

Standards-based call CC to VMR

CC to Focus CC sharing session (1)

©

Polycom, Inc. All rights reserved.

59

CC sharing session (2)

Standards-based call initiates RC

RealConnect Dial Rule Focus URI retrieved

©

Polycom, Inc. All rights reserved.

60

Focus URI Retrieval DMA sends SIP SERVICE message to Lync Front End Pool DMA’s Lync service account used as FROM address Requested action is “resolveConference” DMA sends “PSTN” conference ID to Lync

Lync resolves to Focus URI for conference Lync replies 200 OK to DMA and provides Focus URI

©

Polycom, Inc. All rights reserved.

61

DMA server.log – conf ID resolution request •

Service message from DMA to Lync querying PSTN meeting ID

•

Query on the service account configured (here rppserviceacc)

•

Meeting ID

•

©

Polycom, Inc. All rights reserved.

62

DMA server.log – conf ID resolution response • 200 OK response providing Focus URI

©

Polycom, Inc. All rights reserved.

63

Lync FE receives PSTN conference lookup request Request is from the DMA’s Lync service account

Request is to resolve the “PSTN” meeting ID of our conference

©

Polycom, Inc. All rights reserved.

64

Lync FE responds to DMA with Focus URI

200 OK

Focus URI provided to DMA

©

Polycom, Inc. All rights reserved.

65

DMA Logs • DMA logs in Debug mode • Roll Logs prior to reproducing issue • Key events are in the server.log • Useful search terms are the numeric (PSTN) conference ID and the alphanumeric string at the end of the Focus URI (as in bold below) • sip:[email protected];gruu;opaque=app:conf:focus:id:W0CF5Q87

©

Polycom, Inc. All rights reserved.

66

RealPresence Collaboration Server Logs (1) • dmadirectlync is useful keyword to find API VMR set up • Logger File in 8.5, ApacheModule.log in 8.6 or later

• Focus URI should be visible in the XML

©

Polycom, Inc. All rights reserved.

67

RealPresence Collaboration Server Logs (2) • CS logs may be required for signalling issues • Disabled by default and should be disabled again after reproducing issue

©

Polycom, Inc. All rights reserved.

68

RealPresence Collaboration Server Logs (3) • SIP_CS is useful keyword • Logger file in 8.5, ConfParty.log in 8.6 and later • REQ messages are outbound from RPCS, IND messages are inbound

©

Polycom, Inc. All rights reserved.

69

RealPresence Collaboration Server Logs (4) • RPCS Invite to AVMCU

©

Polycom, Inc. All rights reserved.

70

ContentConnect - CCS.log • CCS.log covers events that lead up to gateway establishment • Useful for troubleshooting the API conversation with DMA • Initial conference notifications don’t include Focus URI

• Soon an updated notification should include this:

Gateway session starts:

©

Polycom, Inc. All rights reserved.

71

ContentConnect - Gateway log • Each VMR with associated gateway sessions creates an individual log • Logs are bundled into one archive at the end of the day • All SIP messages related to GW set up in these logs • “Polycom side” messages can be found with plcmsipmsg

• “Lync side” messages can be found with lyncsipmsg

©

Polycom, Inc. All rights reserved.

72

Troubleshooting – DMA Dial Rules Resolve to Lync conference ID rule should be enabled – can be high up the list

Rule for ContentConnect should be further down the list (“greedy” rule), but caution required to avoid possible conflicts with other rules ©

Polycom, Inc. All rights reserved.

73

Troubleshooting – No RealConnect conference launched • What dial rule did DMA apply? It must be the RealConnect one • Use DMA’s Test Dial Rules tool with a valid Lync conference ID

• There is a 2 second timeout for Lync conf ID resolution

• Check for alerts on DMA when the attempt is made (account issue)

©

Polycom, Inc. All rights reserved.

74

Troubleshooting – ContentConnect GW disconnecting and reconnecting in RealConnect conference • Gateway connects to RPCS but drops after 20 seconds • Most common cause is that the Lync-side connection is failing • CCS dials two calls, one to RPCS and one to Lync (both via DMA) • If Lync connection fails, RPCS call will be torn down too

• CC will continue to keep trying because DMA API tells it to • Dial rule for the Lync call is most common cause • Call must match Lync SIP Peer rule

©

Polycom, Inc. All rights reserved.

75

Troubleshooting – no connection at all from CCS • Ensure CCS is running in Gateway mode • Ensure versions are aligned (e.g. CSS 1.4.x / DMA 6.2.x or CCS 1.5.x / DMA 6.3.x) • Check if a Gateway log was created for the call

• Check CCS.log for the Focus URI of Lync conference • If not, check that API notifications from DMA are present in CCS.log (plcmconference-notification) • Verify DMA details and account are valid on Server Configuration page

©

Polycom, Inc. All rights reserved.

76

Agenda • New Products announced • Polycom RealPresence® Clariti™ • Polycom RealPresence® Clariti™ Cloud Burst

• New Software releases and Hotfixes for existing products • Endpoints • RealPresence® Group Series 5.0.2 • HDX 3.1.9

• Real Presence Platform • • • • • • •

©

RMX v8.6.3 DMA v6.3.1.1 Resource Manager v9.0 Access Director v4.2.2 RealPresence® Web Suite v2.0.1 Media Suite v2.5 ContentConnect v1.5.1

Polycom, Inc. All rights reserved.

77

New Product Announcements • Announced last quarter, refer to last Tech to Tech for details: • • • • •

Polycom® RealPresence Debut™ Polycom® RealPresence Centro™ Polycom® RealPresence Trio™ Polycom® RealPresence® MediaLign™ Polycom® Concierge

• Last Tech to Tech link

©

Polycom, Inc. All rights reserved.

78

New Product Announcements • RealPresence Clariti™ • Cloud-ready collaboration infrastructure software • Scalable • Simple to purchase and implement

• Per connection licensing structure • Skype for Business ready.

• RealPresence Clariti™ Cloud Burst • Ad hoc ability to increase capacity by accessing the cloud.

• Announced at TEAM Polycom 2016

©

Polycom, Inc. All rights reserved.

79

Introducing Polycom® RealPresence Clariti™

Simple

Cloud-Ready

• Easy to buy, deploy and operate

• HD voice, video, content and web collaboration

• Exclusive hybrid cloud bursting

• Intuitive collaboration experience

• Any workspace, any device, businesses of all sizes

• Delivery, deployment and purchasing options

• Natural workflows

©

Powerful

Polycom, Inc. All rights reserved.

• Broadest interoperability • Advanced services and collaboration tools 80

• Developer support for custom integrations

RealPresence Clariti: Cloud Burst Clariti Premise Deployment

Clariti Cloud Burst

Cloud Burst License

Pay-per-use; per connection burst per 24hour period Cloud Burst routing start threshold Autoscaling up threshold

Usage

Polycom MCU Customer MCU

Customer MCU

Polycom, Inc. All rights reserved.

Polycom MCU

Customer MCU

Polycom Managed

Customer Managed ©

Usage

81

New Software Versions • Group Series 5.0.2, released January • Full Details in Release notes at support.polycom.com: • Fixes

• Camera • Microsoft Interop • Video

• Group Series Hotfix 5.0.2_02 • GS 500 showed Presence, SIP, Provisioning, Calendar, and MS services as all down. Reboot resolved the issue • GS300 crashes and reboots when placing SIP to PSTN call via GW. Error "Fatal Signal 11 (SIGSEGV)"

• Group Series Hotfix 5.0.2_04 • API 'calendarmeetings info' returns 'dialingnumber' data in a different order between HDX and Group Series • Group Series registering on Lync2013 received the P2P call from Lync client; however Group Series show remote site name with "RMX2000"

©

Polycom, Inc. All rights reserved.

82

New Software Versions • HDX Series 3.1.9, (January 2016) • Fixes • Microsoft Interop: • System

• Notes • 1.15 is companion PTC version

©

Polycom, Inc. All rights reserved.

83

New Software Versions • RPCS (RMX) 8.6.3.29 (8.6.3 HF1) − 8.6.x only applicable to RPCS with MPMRx cards (so not RPCS1500) − Fixes: − RMX 8.6.3 Virtual Edition-IVR "conference_password.wav" message is not played sporadically. − MPM-Rx card rebooted − When the RMX IVR receives the # key before the user type the password, sometimes RMX does not request the password again.

• RPCS (RMX) 8.6.3.480 − Resolves issue with Collaboration Server WebRTC implementation not compatible with Chrome version 48 − This version is now available on support.polycom.com

©

Polycom, Inc. All rights reserved.

84

New Software Versions • DMA v6.3.1 (December 2015) • New Features • Introduces the ability to change a server’s root password, via UI or API • Introduces a number of new API commands.

• Fixes • Polycom RealConnectTM and ContentConnect • Failovers, crashes, performance issues

• DMA v6.3.1.1 or 6.3.1_P1 (February 1st 2016) • Fixes (resolves a couple of issues seen in 6.3.1) • Incorrect memory allocation causing system performance issues on servers with 8GB of memory (including Dell R610 and R220) • The database archive cleanup logic was not being properly executed taking up unnecessary disk space

©

Polycom, Inc. All rights reserved.

85

New Software Versions

• Resource Manager v9.0 • New Features • Support for Polycom Concierge • Support for RealPresence Centro, RealPresence Debut, RealPresence Trio and RealPresence Touch • Support for Monitoring of Web RTC participants • Support for Zero Touch Provisioning for RealPresence Debut • Upgrade of Resource Manager redundant pairs

• Fixes • Upload of server software upgrade package • New user addition causes deletion of users in same group. • Web Access Port dynamic provisioning

• Note VDM does not support v9.0 RM software ©

Polycom, Inc. All rights reserved.

86

New Software Versions

• Access Director v4.2.2 (December 2015) •

Fixes •

ACL and dialbots

•

TIP protocol

•

Web Suite disconnection

• Access Director v4.2.2.0.2 (4.2.2 HF2) • Upgrade from 4.1 to 4.2.2 directly could result in upgrade failing prematurely with lack of access to RPAD UI

• Access Director v4.2.2.0.3 (January 2016) • ©

Registrations fail due to provisioned endpoint across RPAD not being added to RPAD provisioning list if there is fragmentation in the TCP packets

Polycom, Inc. All rights reserved.

87

New Software Versions •

Web Suite v2.0.1 (formerly Cloud Axis) • Enables SVC meetings with Google Chrome

• Fixes •

•

The RealPresence Web Suite Experience Portal disconnects from the meeting when network connectivity is lost

Media Suite v2.5 (formerly Capture Server) • Major release with new Basic, Pro and Platinum features • Fixes

•

•

After upgrade to 2.1, Media Suite unable to send email if SMTP is enabled

•

Media Suite Player timer does not display a live event ongoing time from Internet Explorer

•

User Portal does not support multicast streaming playing

ContentConnect v1.5.1 (formerly Content Sharing Suite) • Support for Skype for Business client with Office 2013 in add-on mode • Fixes

©

•

Security

•

General Bugs

Polycom, Inc. All rights reserved.

88

New Software Versions - Notes • These are a subset of all released fixes • Refer to the release notes at support.polycom.com. • Hotfixes are not full releases of software − Will be rolled in to future full releases − Hotfixes tend to be cumulative i.e. HF 2 includes fixes in HF1

©

Polycom, Inc. All rights reserved.

89

Today We Covered • Polycom® RealPresence Debut™: − Cloud Mode − Provisioning: − − − − −

Polycom® RealPresence® Cloud-enabled services Polycom® Zero Touch Provisioning (ZTP) solution Polycom® RealPresence® Resource Manager BroadSoft DMS FTP/FTPS server

• Polycom® RealPresence Trio™ 8800 and RealPresence Trio™ Visual+ − configuration and troubleshooting for Skype for Business / Microsoft® Lync®

• Analysis of Polycom® RealConnect™ and ContentConnect™ call flows • General Technical Update

©

Polycom, Inc. All rights reserved.

90

Thank You

©

Polycom, Inc. All rights reserved.