jamvee unified communications administrator guide...and presence communications capabilities in...

Jamvee™ Unified Communications Service

System Administrator Guide

(Customer)

Unified Conferencing Service Version

Issue Date

4.5.1 Aug 2015

V4.5-20140630 Jamvee™ System Administrator Guide (Customer) 2

Microsoft and Lync are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. This document is not affiliated with, nor has it been authorised, sponsored, or otherwise approved by Microsoft Corporation © 2015 Tata Communications Ltd. All rights reserved. Protected under the Berne Convention. TATA COMMUNICATIONS and TATA are trademarks of

Tata Sons Limited in certain countries. Jamvee™ is a trademark of Tata Communications (Bermuda) Limited in certain countries.

Table of Contents

1 Introduction ................................................................................................................................................... 4

1.1 Document objective .............................................................................................................................. 4

1.2 Executive summary .............................................................................................................................. 4

1.2.1 Service summary .............................................................................................................................. 4

1.2.2 Service Enhancements ..................................................................................................................... 7

1.2.2.1 Release 4.5 (incl. sub-releases) ............................................................................................... 7

1.2.2.2 Release 4.4 ............................................................................................................................... 8

1.2.2.3 Release 4.3 ............................................................................................................................... 8

1.2.2.4 Release 4.2 ............................................................................................................................... 9

1.2.2.5 Release 4.1 ............................................................................................................................. 10

1.2.3 Offering components ...................................................................................................................... 11

1.2.4 Offering model ................................................................................................................................ 13

2 Offering description ..................................................................................................................................... 15

2.1 Offering objectives .............................................................................................................................. 15

2.2 Elements of offering ............................................................................................................................ 16

2.2.1 Service platform components ......................................................................................................... 16

2.2.2 Service infrastructure component diagram ..................................................................................... 18

3 Transport access methods ......................................................................................................................... 19

3.1 Access method #1: dedicated MPLS GVPN (private addressing) ..................................................... 19

3.2 Access method #2: IP transit destination QoS (public internet with QoS) - IZO™ ............................. 21

3.3 Access method #3: Federated Microsoft Lync connection over the public internet ........................... 22

3.4 Access method #4: video conference and UC endpoint access over the public internet .................. 23

3.5 Access method #5 and #6: PSTN toll (#5) and toll-free (#6) access for audio-only endpoints .......... 23

3.6 Access method #7: dedicated On-Net SIP trunk for audio-only endpoints ........................................ 25

3.7 Access method #8: On-Net access from other video services ........................................................... 25

3.8 Conference Dial-Out (Host Initiated) .................................................................................................. 26

3.9 Distributed Conferencing .................................................................................................................... 27

3.10 Telepresence Interoperability Protocol (TIP) Support ........................................................................ 30




3.10.1 Behavior of TIP systems in the jamvee™ service - 3 screen and single screen systems ......... 30

3.11 Conference Features/Capabilities ...................................................................................................... 32

4 Microsoft Lync federation to jamvee.com ................................................................................................... 34

4.1 Lync federation and configuration document...................................................................................... 35

5 VNOC helpdesk support services ............................................................................................................... 36

6 Conference access and production ............................................................................................................ 37

6.1 Dialling guides .................................................................................................................................... 41

6.2 Bridge resource allocation .................................................................................................................. 41

6.3 API services ........................................................................................................................................ 41

6.4 Bandwidth “lane” management ........................................................................................................... 41

7 Service security .......................................................................................................................................... 43

7.1 Encrypted federated Lync call flow ..................................................................................................... 45

7.2 Encrypted unified communications client XMPP/HTTPS call flow ..................................................... 46

8 Support for mobile video endpoints ............................................................................................................ 47

9 Pricing, billing/reporting, and service schedule .......................................................................................... 48

9.1 Commercial models for jamvee™ Unified Communications .............................................................. 48

9.2 Commercial Offer Summary ............................................................................................................... 51

10 Appendix A – jamvee™ Unified Communications services supported endpoints list .............................. 52

11 Appendix B – audio-only PSTN access numbers ....................................................................................... 53

12 Appendix C – Enterprise firewall/proxy server guidelines .......................................................................... 54




1 Introduction

1.1 Document objective

This document describes the Jamvee™ Unified Communications Service. It describes the components of the

service and its implementation. The document will be updated throughout the lifetime of the jamvee™ Service

to incorporate any additions or changes resulting from new service releases as they are brought to market and

made available.

1.2 Executive summary

The Jamvee™ Unified Communications Service release is designed as a unified conferencing service based on

next generation soft-MCU technology which provides major enhancement and improvement to the existing

jamvee™ service. The jamvee™ Unified Communications service unites previously incompatible audio, video

and application sharing technologies in a virtual meeting room user paradigm and adds Instant Messaging (IM)

and Presence communications capabilities in order to deliver a truly Unified Communications (UC) experience

that is only limited by the specific capabilities of the user endpoint being used to dial into a jamvee™ conference.

1.2.1 Service summary

The Jamvee™ Unified Communications Service is designed as a major enhancement and improvement to the

existing jamvee™ service that unites previously incompatible audio, video and application sharing technologies

in a ‘virtual meeting rooms’ user paradigm that adds Instant Messaging (IM) and Presence communications

capabilities in order to deliver a truly engaging conferencing experience that is only limited by the specific

capabilities of the user endpoint being used to access the conference. The jamvee™ solution provides even

tighter integration with existing video conference infrastructure, including Cisco and Polycom and provides

significant integration with enterprise deployments of Microsoft Lync. Jamvee™ Unified Communications service

does not require the customer to “rip and replace" thus preserving and enhancing the value of the customers’

existing investments in communications infrastructure, including existing UCC deployments.

The jamvee™ Unified Communications solution delivers voice, video, web (content sharing), IM and Presence

on a single next-generation conferencing platform that is deployed within the Global Meeting Exchange (GMX)

as a cloud-hosted service.




The broad range of endpoints supported by the jamvee™ Unified Communications service are illustrated in

the following figure:

Figure #1: Jamvee™ Unified Communications Service– High Level Overview




The jamvee™ Unified Communications Service provides the following capabilities and benefits:

Jamvee™ Feature/Capability Description Key Benefits

New Edge Registration and Core Conference

Bridge Platform – software-based registration and

MCUs servers that leverage highly scalable Intel

server hardware and MCU software

Single vendor client, edge, and core (MCU) for better E2E integration

Highly scalable soft-MCU for lower conference costs

Edge deployment architecture - closer to end-user to minimize poor public Internet network performance

New Desktop/Mobile Apps – totally new end-user

desktop and mobile clients from the same vendor

as the Core (MCU) Servers

Fully integrated with edge and core MCU

Fewer compatibility issues and close integration between the client and the MCU,

Virtual meeting room user experience

New WebRTC App – jamvee™ unified conference

access without an App or a browser Plug-In

No downloads or plug-in needed

One-click URL access to meeting for participants

Supported for Google Chrome and Mozilla Firefox web-browsers

Ideal for guest user access to a Customer jamvee™ Room

Microsoft Internet Explorer & Apple Safari Plug-In

App – support for non-WebRTC browsers

Broader compatibility with more broadly deployed enterprise web technologies

One push download of free client when IE or a Safari browser is used (i.e. a non-WebRTC browser)

Interoperability with enterprise Microsoft Lync

deployments – federation of enterprise Lync

2010/2013 and Lync 365 deployment

Leverage existing Microsoft Lync clients to access a jamvee™ conference with full video, audio, content sharing, IM and Presence

Minimal user training

No enterprise deployment of additional software clients

Interoperability with single-screen Cisco/Polycom

hard, soft, and immersive endpoints (SIP/H.323) –

standard video conferencing endpoints

One unified conference virtual meeting room

Support for both new endpoints and for legacy endpoints (customer investment protection)

Adds IM/Presence/Conference Control Capabilities

to a jamvee™ conference – ability to chat, see

presence and Host/Moderator control of the

conference

A much richer, unified conference experience with UC&C capabilities

Direct Host/Moderator control of the conference (drop, mute, etc.)

Jamvee™ APIs in development – provide deeper

integration with Wholesale Customer business

applications (e.g. provisioning, end-user

experience apps)

Allows Wholesale Customer/Partner to better control and integrate their user experience

Wholesale Customer/Partner value add

Improved price models – segments pricing levels

and models for audio-only with or without content,

and video + audio + content with IM/Presence

Customer pays for the required functionality based on how they access and use the service

Following pricing models:

- “Pay-as-you-Go”, - Minimum Commitment Usage + Overages - Enterprise Per Seat/Named User (unlimited usage)




1.2.2 Service Enhancements

1.2.2.1 Release 4.5 (incl. sub-releases)

New Endpoint Support: the following additional end-user endpoints are being supported: o Cisco Jabber UCC Support1 – allows an enterprise customer/user that has an enterprise-hosted

Cisco Jabber UCC deployment to connect to a jamvee™ UC conference using their existing Jabber UCC desktop/mobile applications. It supports inbound SIP IP Audio, IP Video and Content Sharing via the SIP-call flows supported by the jamvee™ service. Note: IM/Chat and Presence information from Jabber UCC is not supported.

o Cisco IX-Series – The latest immersive (multi-screen) video conferencing endpoints, the Cisco

IX5000-Series immersive Telepresence endpoints, will be supported in a sub-release of rel 4.5, once the jamvee™ infrastructure has been fully upgraded – estimate end-Aug ‘15.

o Skype and Skype for Business (Audio, Video and Web) Support – Microsoft provides Skype and Skype for Business (aka Office/Lync 365) services and applications within their cloud offering which allows Skype users to call/collaborate with other Lync users using voice, video and content sharing. Leveraging this integration jamvee™ clients can now participate in a jamvee™ UC video meeting with Skype and Skype for Business users, via the standard Lync open-federation already in place between Lync365 and the jamvee™ UC service.

New Access Methods: the following additional access methods are now supported: o Jamvee Audio On-Net Access via Global SIP Connect (GSC) Trunk – this jamvee™

dedicated/private transport access method provides an option for jamvee™ customers to connect their enterprise IPT/IP PBX platform (i.e. their internal digital voice/phone system) to the jamvee™ service for "on-net" audio-only access to a jamvee™ conference using a Closed User Group (CUG) number (i.e. a 5 or 6 digit telephone extension number). Please note that this requires a standard Global SIP Connect (GSC) Trunk from Tata Communications. Once provisioned, any audio-only call using the CUG number will be automatically routed and answered by the jamvee™ UC service.

o QoS Access from jamvee™ UC Client/Lync - UC Port/IZO Public (IP Transit) – this access method provides an option for jamvee™ customers to connect their enterprise deployed jamvee™ UC (audio/video/content/chat/presence), video conferencing equipment and Lync estate together. The "UC Port/IZO Public" Service from Tata Communications allows these endpoints to connect to a jamvee™ conference for high-quality calls, over IP connections with maintained QoS service levels.

o QoS Access from jamvee UC Client - vUTM (MPLS) – The option of a dedicated/private access to connect your enterprise deployed jamvee™ UC (audio/video/content/chat/presence) and VC estate, to a jamvee UC conference over an MPLS GVPN/vUTM/AS6453 connection. The access method leverages Tata Communication’s virtual Unified Threat Management (vUTM) Service (cloud-hosted firewall) to provide a firewall between the customer’s private MPLS GVPN network and the IP Transit Network (AS6453) from Tata Communications.

Dial-In/Dial-Out Provisioning and Billing – provisioning and billing for jamvee™ PSTN access (for both for dial-in and dial-out) is migrating to a different system which allows the ability to integrate it more easily with other voice services, such as dedicated number sets (for dial-in) and CUG on-net access.

1 Please note that this is support for Cisco Jabber UCC Apps, which are different from the Cisco Jabber Video for TP (a.k.a. “Movi” client) which has,

and continues to be, supported.




v1.6 UI support for Mobile Apps and WebRTC (scheduled for r4.5.1) – updates the user interface for the mobile (iOS App) and WebRTC version of the jamvee UC App2 to the same interface as used for the PC and Mac apps.

Basic Usage Reporting – enables customer admins to execute pre-defined, i.e. "canned basic reports", via the jamvee™ portal.

New Pricing Plan Structure and Active-VMR Price Plan – this feature greatly enhances and simplifies the jamvee™ UC Service. It provides the ability to provision VMRs of any type (or service offer) directly by customer admins via the jamvee™ portal and bill for those VMR without an additional Customer Order From (COF). Also introduced is a new, Active-VMR-based Pricing Plan. This price plan allows the a customer or partner admin to provision as many VMRs as required across an enterprise but only pay monthly charges associated with a VMR when that VMR becomes “active”, i.e. when it is used by an end-user to host a conference. This allows the customer to only pay for those VMRs that are actually being actively used by their end-users, while maintaining flexibility of being able to allocate and deploy additional VMRs virtually instantly.

1.2.2.2 Release 4.4

Update PC and Mac App with improved ergonomics and GUI – this feature is an inherent new software feature of the call bridge infrastructure that allows a single conference hosted on a Virtual Meeting Room (VMR) to span multi-conference bridges hosted on different PoPs jamvee™ network (i.e. NY, London, Singapore or Sydney PoPs). This capability allows conference participants from different regions to be connected to the closest jamvee™ call bridge and the conference is then cascaded between the two or more bridges. This maximizes the user’s quality of experience by having each participant connect to the closest bridge to where they are located and reducing the impact of poor network performance (e.g. packet loss, jitter or latency related to the public Internet). For more information please refer to the jamvee™ UC App User Guide (PC & Mac)

Jamvee™ Calendar Plugin for Microsoft Outlook – a new plugin has been developed that is designed to work with Microsoft Outlook. With it a user can associate a particular VMR with the jamvee™ Calendar plugin. When the user then schedules a meeting using the Outlook calendar, once they have set the time, date and attendees, pressing the jamvee™ plugin button will ensure that all the relevant meeting details are pasted into the calendar invite automatically – saving significant time and reducing the “cutting and pasting” of the information. The associated VMR can be changed and configured to a different room

1.2.2.3 Release 4.3

Distributed Conferencing – this feature is an inherent new software feature of the call bridge infrastructure that allows a single conference hosted on a Virtual Meeting Room (VMR) to span multi-conference bridges hosted on different PoPs jamvee™ network (i.e. NY, London, Singapore or Sydney PoPs). This capability allows conference participants from different regions to be connected to the closest jamvee™ call bridge and the conference is then cascaded between the two or more bridges. This maximizes the user’s quality of experience by having each participant connect to the closest bridge

2 Note that the new UI was introduced on the desktop version of the jamvee UC App (Windows/Mac) in jamvee R4.4.

https://enterprise.jamvee.com/partners/enterprise.jamvee.com/resources/jamveeUC_User_Guide_(pc_mac).pdf




to where they are located and reducing the impact of poor network performance (e.g. packet loss, jitter or latency related to the public Internet).

Telepresence Interoperability Protocol (TIP) Support for Telepresence Endpoints – this capability allows users to dial-in to a jamvee conference using immersive telepresence endpoint (single or multi-screen devices) for Cisco and other suppliers that are compatible with the Telepresence Interoperability Protocol (TIP). This increases the types of endpoints that can participate in a jamvee™ conference. A separate user guide has been created to explain the behaviour of telepresence units on a single bridge and when distributed across different call bridges.

AC Keypad Controls: Basic– Audio Conferencing (AC) keypad control allows a jamvee™ user with SIP call flow access to the jamvee™ Service (e.g. via the PSTN and VC endpoint via the public Internet) and control certain aspects of the conference (e.g. mute, unmute, mute all, unmute all, etc.) using the keypad on the endpoint device. The capability is not available via the jamvee™ UC Desktop/Mobile Apps or the Microsoft Lync call flows in this release, only endpoints that connect to the jamvee™ service via a standard SIP call flow.

Dial-Out for H.323 Calls (round robin-solution) – this capability allows the conference host/mediator to dial-out from a VMR to a Video Conference endpoint that support the H.323 protocol (legacy video conferencing endpoints). The call will originate on the jamvee™ bridge and connect over the public Internet access points at each jamvee™ PoP. This capability builds upon the dial-out capability that was introduced in jamvee R4.2.

1.2.2.4 Release 4.2

Host Initiated Conference Dial-Out via the PSTN/Internet Gateways – this feature allows the end-user of a jamvee™ conference (i.e. the Host or owner of the VMR) to on-demand “dial-out” from their provisioned VMR on the jamvee™ UC bridge to another audio/video or audio-only endpoint across a public network. The dial out capability will be supported via:

o Jamvee™ On-Demand Dial-Out to any audio-only endpoints via the jamvee™ PSTN Gateway using a standard public E.164 telephone number. The dial-out E.164 number must be addressable on the Public Switched Telephone Network (PSTN).

o Jamvee™ On-Demand Dial-Out via Internet Access to a supported VC/UC endpoint via the jamvee Internet Gateway using a standard, DNS route-able URI address. The dial-out URI address must be DNS resolved to a jamvee™ supported audio/video endpoint on the Public Internet (i.e. the endpoint must be reachable in the public Internet).

Basic Wholesale Partner HUB Models – this capability allows special, high-volume partners (Wholesale Customers) to deploy the equivalent of a small jamvee™-PoP within their data-centre that is logically an extension of the jamvee™ network and connects that PoP to partner provided network. This capability is primarily designed for partners that are regional Service Provider that would typically connect the Partner HUB Model PoP to their local Internet services, voice services, and/or MPLS services to provide end-user customers with regional access to the local jamvee POP while leveraging the globally distributed jamvee network.

Jamvee IVR Upgrade – the jamvee™ IVR software is being upgraded as part of this release to enhance the DTMF recognition capabilities for calls flows where the IVR is used to enter the Host_CallID or the Participant_CallID to be routed to the proper VMR.

Clear Chat Feature – the jamvee™ UC Desktop/Mobile Apps and the jamvee UC WebRTC App will include a capability that will allow the user to clear their chat window. This clears all message that




present in the chat window so that when new participants join a conference the chat window is devoid of any historical messages from previous conferences. \

Self-Certification - Self-certification enables end-users to test their connectivity to the service by

viewing their outgoing video looped-back to their video conferencing system, computer, tablet or

smartphone.

Please note: at present, self-certification does not verify audio communications. This capability will be

incorporated to a future release.

1.2.2.5 Release 4.1

Client UI Improvements Phase 1 – the jamvee™ UC Desktop/Mobile Apps have been enhanced with user interface changes which improves the operation of the Apps in conjunction with the jamvee R4 service. For a complete list of these changes please see the jamvee R4.1 Release Notes available via the jamvee™ portal http://enterprise.jamvee.com.

Automated Enterprise/User Provisioning via Jamvee Enterprise Portal – the major addition to the jamvee™ unified communications service is the availability of the jamvee™ Enterprise Portal. This portal allows Tata communications, its Wholesale Partners, and/or Partner Enterprise Administrators, and even a single end-user to manage jamvee™ user account(s) and provision Virtual Meeting Rooms (VMRs) within those accounts. This capability allows an enterprise admin to on-board one (via the UI) or more users (via a file-based bulk upload capability) to the service and properly provision those users for service access. The portal support a multi-tiered, multi-tenant architecture and can be Co-Branded or fully White-Labelled for a specific Wholesale Partner.

Jamvee API for Provisioning for Partner’s with own front-end Applications – the jamvee™ Enterprise Portal utilizes the new jamvee™ API for Provisioning which is a jamvee SDP-based Web Services (REST) Application Programming Interface (API) which supports automated back-end provision of the jamvee R4 service.

White-Label (WL) Branding Enhancements for Wholesale Partners for the jamvee Enterprise Portal – in addition to the standard co-branding capabilities (i.e. jamvee neutral branding) of the jamvee Enterprise Portal, with Release 4.1, the portal can also support white-labelled branding for select Wholesale Partners. This implies that the portal will not have any branding except in locations where it is legally required (e.g. copyright notices and other legal notices). NOTE: this capability is not available for just any Wholesale Partner and approval for a partner must be requested and approved.

http://enterprise.jamvee.com/




1.2.3 Offering components

The jamvee™ Unified Communications Service supports:

Standard-based Video Conferencing (VC) endpoint – SIP/H.323 SD and HD endpoints from Cisco/Tandberg and Polycom, etc. with audio, video and content sharing,

Audio-only PSTN endpoints – wired and wireless telephone access over the PSTN for audio only access,

Jamvee™ Unified Communications Desktop/Mobile Apps – new jamvee™ apps (Windows, Mac OS X, iOS, WebRTC, and IE/Safari Plug-Ins) registered to a GMX Edge Server in the DMZ/Extranet for audio, video, content sharing, Instant Messaging, Presence, and

Microsoft Lync 2010/2013 (and Lync via Office365)– new support for standard Microsoft federation for enterprise Lync endpoints access to jamvee™ conferences with audio, video, content sharing, IM and Presence.

This allows for on-demand intra-company conferencing within the same customer and for inter-company

conferencing (B2B) between any two or more managed or unmanaged customers that subscribe to jamvee™

Unified Communications Service or with external guest endpoints via the Internet. The major jamvee™ Unified

Communications service offering components are as follows:

No Offering Component Component Description

Jamvee™ Unified Communications for GMX On-Net Endpoints

1 Un-scheduled (any-time)

Telepresence, VC, Audio, and

Unified Communications

Video Conferencing endpoints Connected to GMX

Audio-only endpoints connected to GMX via aGlobal Voice Network

Jamvee™ unified communications Apps access (Internet and dedicated access)

Microsoft Lync – Internet and dedicated access

Dial-In Virtual Meeting Room (for homogeneous and mixed endpoitns calls)

Host-Pays Model

A single service that support both intra-company and inter-company

Unified Communications using a URI, E.164, or URL dial-in access

mechanism. The calls are always dial-in and terminate on the

host/moderator virtual meeting room. Depending on the endpoint and

access method used to access the jamvee™ Room, the end user

authentication options will vary when dialling into the service. This will

includes:

Host or Participant Call-ID – if the user is using the traditional jamvee™ access method via the Session Manager (all Immersive (when supported), Video Conferencing and Audio-only endpoints) a Call-ID-PIN is required.

Host/Moderator Authenticated Access – if the Host is using the jamvee™ unified communications Desktop/Mobile Apps they can access the jamvee™ Room via a single “click-to-join” button since their client is already authenticated with the service via a user account login/password

Participant Authenticated Access – if the Participant is using the jamvee™ Unified Communications Desktop/Mobile Apps they can access the ‘Room’ via a single “click-to-join” if the Host has included the Participant user account as a member of their jamvee™ ‘Room’. The Participants client App is already authenticated with the service via a user account login/password

Guest Participant Access – if the Participant is a guest they will require to use a Participant Call-ID/PIN (Meeting Room ID)




2 Jamvee™ Pricing Model

Transport Access Charges (for QoS/dedicated access)

PSTN Toll-Free Access Charges

Bridging Charges (Host-Pays Model)

VNOC Site-Certification Charges

The jamvee™ Unified Communications Service conference usage

charges do not include access/transport charges. The jamvee™

access charges that may be included (depending on the access

methods used by attendees) include:

IP Transit Destination QoS Access (public addressing with dedicated QoS packet transport)

MPLS GVPN Dedicated GMX Access (private addressing with CoS2 transport – for VC EP access)

PSTN Toll-Free (ITFS) Rated Access Charges

There are no additional service charges for Direct Internet Access to a

jamvee™ Conference since the end-user is responsible for these

access charges directly to their local Internet Service Provider (ISP).

Jamvee™ Unified Communications Service bridging charges are

either based on:

Model #1: “Pay-as-you-Go” (PAYG) Usage with No Up-Front Commitment,

Model #2: Minimum Commitment Bundle with Overages,

Model #3: Per Seat/Named User with Unlimited Use (Enterprise License per Host/Room) MRC.

In all cases the host pays for all legs of the endpoints on the

conference. All models require a one-time, per enterprise NRC.

You can also select an option for VNOC Site-Certification of their video

endpoints to insure proper access and provisioning of endpoints on the

service. This is charge is a one-time, per endpoint charge to cover EP

certification costs (NRC basis). For all endpoints that are not certified,

technical support is provided on a best effort basis only (limited

support).

3 Service Management Portal

Jamvee™ Enterprise Portal

The jamvee™ Enterprise Portal will not be available until the next

jamvee™ release (scheduled Sept ’14). This document will be updated

with additional detailed information as part of that release. For the

current jamvee™ Unified Communications Service all customer and

end-user provision is accomplished manually using internal service

management tools.

Jamvee™ Unified Communications for Guest Off-Net Endpoints

4 Un-scheduled (any-time)

Telepresence, VC and Unified

Communications

A guest endpoint is considered an Off-Net endpoint if the user typically

does not have a business relation with a jamvee™ unified

communications service provider. These endpoints/users participate




Participant Endpoints only (requires a Host that is a TC customer)

Participant jamvee™ Room Dial-In Instructions are provided by the Host

as guests on a conference call hosted by a user who has a valid

virtual meeting room and Host call-ID

Guest endpoints participate in a call hosted by a registered user when

that Host provides them (via email or attached to a calendar invite) the

Participant Call-ID along with the dial-in instructions (i.e.

URI/E.164/URL and Call-ID required to access the meeting).

A Guest endpoint can join the conference using any supported

endpoint, but is likely to join using a browser (WebRTC capable) or via

a Guest App (if using IE/Safari) using a URL provided by the Host to

access their jamvee™ Room. A guest will always be required to enter

the required meeting credential (Participant Call-ID) depending on

what endpoint they are using to access the conference.

All jamvee™ Unified Communications Service calls are hosted on a bridging platform (Edge and Core Servers)

within GMX and will support mixed-EPs calls and automatically adjust to the best view and video/audio call

quality for each endpoint on the call.

1.2.4 Offering model

PAYG Pricing Model - PAYG with some volume discounting based on monthly revenue

Unified Communications (UC) customers with unknown usage forecast that can tolerate variations in their monthly costs and want to pay only on the overall metered usage with no up-front commitments:

o Unlimited Jamvee™ Rooms across the enterprise

Audio/Web Conferencing (AC) Customers with unknown usage forecast that can tolerate variations in their monthly costs and want to pay only on the overall metered usage with no up-front commitments:

o Unlimited audio with or without content sharing jamvee™ Rooms across the enterprise

Minimum Commitment w/Overage pricing model - with deeper discounts based on committed revenue

Unified Communications (UC) customers with known usage patterns that want more predictable costs and higher discounts for metered usage:

o Unlimited jamvee™ Rooms across the enterprise

Audio/Web Conferencing (AC) Customers with known usage patterns that want more predictable costs and higher discounts for metered usage:

o Unlimited audio with or without content sharing Jamvee™ Rooms across the enterprise

Per Seat/Name User Pricing Model - MRC discounts based on the number of total seats across the enterprise

Ideal for customers with no tolerance for cost variability and require unlimited usage for a specific numbers of enterprise users:

o Limited to one jamvee™ ‘Room’ per Named User (a single seat per user account) o Can manage costs by providing user with different Per Seat Service Offer (i.e. maximum

number of participants based on their needs)




Audio Conference (AC) Customers with no tolerance for cost variability and require unlimited usage for a specific numbers of enterprise users:

o Limited to one ‘Room’ per Named User (a single seat per user account) configured as an Audio with or without Content Sharing

o Can manage costs by providing user with different Per Seat Service Offer (i.e. maximum number of participants based on their needs)

Plus…

Any mix of the above customers that need both Unified Communications and Audio Conferencing




2 Offering description

2.1 Offering objectives

The major objective of the jamvee™ Unified Communications service is to provide a solution that unites

previously incompatible audio, video and application sharing technologies in a virtual meeting room that adds

IM and Presence communications capabilities in order to deliver a truly unified experience. The offering is

intended to compliment an existing enterprise’s Video Conferencing and Unified Communications and

Collaboration (UCC) estate by supporting a cloud-hosted communications platform that unifies both estates into

seamless collaboration between disparate endpoints.

The objectives are to provide:

1. Comprehensive Solution – a solution that allows endpoints from their disparate communications and collaboration infrastructures to participate in a unified, cloud-hosted conference that eliminates the interworking complexity of these environments.

2. Service Simplification – a single unified conference service, with support for various endpoints and multiple global access methods

3. Mixed Endpoint Interoperability Support – access to single cloud conferencing service from a variety of

video conferencing and UCC endpoint types including room systems (Cisco MX200, Polycom HDX, etc.), personal/desktop systems (Cisco EX90, Polycom HDX 4000, Cisco Jabber Video for TP (Movi), jamvee™ unified communications app for Windows/Mac (UCC) and access from mobile devices (Cisco Jabber for the iPad connected to an enterprise call manager, and Microsoft Lync 2010/2013 endpoints etc. Please see Appendix A for a complete endpoint list.

4. Multiple Transport Access Methods – access to the jamvee™ Unified Communications service from

endpoints connected via dedicated IP Transit Destination QoS Access (public addressing with QoS packet transport), MPLS GVPN Dedicated GMX Access (private), endpoints connected via “best-effort” public Internet (SIP/H.323/XMPP), and audio-only endpoints via the PSTN (Circuit Switch and/or Audio SIP Trunks).

5. Federated Microsoft Lync Access – standard Microsoft federation support for seamlessly connecting

enterprise Lync endpoints to the jamvee™ Unified Communications Service directly via the public Internet or via a private QoS based access method using IP Transit.

6. Both Usage-based and Per Seat Pricing Models for Enterprise and Wholesale Customers – the jamvee™ Unified Communications service will support a “Pay-as-you-Go” PAYG Usage with No Up-Front Commitment (Model #1), a Minimum Commitment Bundle with Overages (Model #2), and a Per Seat/Named User with Unlimited Use MRC (Enterprise License per Host/Room- Model #3).




2.2 Elements of offering

The jamvee™ Unified Communications service provides an intra-company and inter-company (B2B) service

that is designed to effectively interoperate with legacy video conferencing and today’s rapidly deploying UCC

platform (e.g. Microsoft Lync).

Currently, this bridging service is hosted in four GMX nodes: New York, London, Singapore, and Sydney (a

recent GMX PoP addition) with transport aggregation in a PoP in Mumbai.

2.2.1 Service platform components

The jamvee™ Unified Communications service components are deployed on the GMX Platform and core

network using Edge Servers and Core Server bridges (MCU) from our solution provider. The jamvee™ service

add new and integrates with some of the existing infrastructure components used for the existing jamvee™ on-

demand video conferencing service and other GMX conferencing services (e.g. Scheduled Conferences). The

use of existing jamvee™ on-demand video conferencing services access methods and call flows provide

continuity for existing jamvee™ customers and leverage the investment in the jamvee™ Session Manager and

other GMX components. The existing jamvee™ access methods and call flows will all support access to the

jamvee™ Unified Communications service via the use of the appropriate access Call- to distinguish between

the legacy and newly deployed bridging platforms. This is automatically handled and is intended to be

transparent to the end-user.

In addition to the existing jamvee™ access methods/call flows, new jamvee™ Unified Communications specific

access methods are also available for the new XMPP-based jamvee™ Unified Communications apps and for

direct federation call-flows for Enterprise/365 Microsoft Lync deployments. Since these access method and call

flows are not traditional video conferencing SIP-based flows, the access methods and clients do not route or

leverage the capabilities of the jamvee™ Session Manager and are completely separate flows.

The jamvee™ Unified Communications service does not distinguish between intra-company and inter-company

conferencing because the conference type depends on who is invited to the call by the host. Once a

participant/guest end-user is provided the Room dial-in information (virtual meeting room access methods) by

the host the participant has all the information they need to access the service independent of whether the user

is an internal or external user assuming that the user endpoint has connectivity to the jamvee™ Unified

Communications service via a supported transport access method.




The jamvee™ Unified Communications service solution incorporates the following essential components:

GMX Platform/Network Infrastructure – provides the global conferencing infrastructure and core backbone network required to support the service including edge and core bridging, Conference Service Provisioning and Management, Microsoft Lync Edge and Front-End Servers (for Lync federation), and call control (Session Manager) for Immersive/VC/Audio call flows. The GMX platform also includes the jamvee™ VC Desktop/Mobile App registration server and the jamvee™ Real-Time Platform (RTP) Server. The new jamvee™ Unified Communications Desktop/Client Apps (XMPP-based) and the jamvee™ WebRTC Apps register to the Edge Server using XMPP and WebRTC protocols.

Transport Access Methods – support for a variety of connectivity options for connecting customer EPs to the service QoS-enabled Transport – transport services through Tata Communications private CoS2 transport

network (MPLS GVPN) for direct SIP-trunk (VC EPs) or XMPP/Federation Trunks (R4.1) or via IP Transit Destination QoS for public access with QoS IP packet transport

Internet Transport Interconnect – access to services for public Internet connected VC EPs, XMPP EPs), or Internet Federated Lync EPs

PSTN Access – for audio-only endpoints

The infrastructure components listed above are deployed in various redundant and scalable fashions across

five (5) globally distributed GMX Core node locations that include3:

New York, USA

London, UK

Mumbai, India (traffic aggregation only)

Singapore

Sydney, Australia

3 Note that not all components are located in each PoP. See Figure #2 for more information.




2.2.2 Service infrastructure component diagram

The following diagram provides the current representation of the overall GMX Platform/Network infrastructure

components for the jamvee™ Unified Communications Service. Please note that in order to simplify the diagram

a) other existing GMX components are not shown and b) component redundancy is also not shown:

Figure #2: Jamvee™ Unified Communications constituent components




3 Transport access methods The jamvee™ Unified Communications Service (jamvee™ R4) include support for various transport access

methods that provide private and public access for endpoints dialling into the jamvee™ conference. These

access method include:

QoS-enabled Transport – transport services through private CoS2 transport network (MPLS GVPN) for direct SIP-trunk (for Telepresence and Video-Conferencing endpoints) or dedicated XMPP access (MPLS GVPN with vUTM), or via IP Transit Destination QoS for public access with QoS IP packet transport, or on-net audio-only access via MPLS GVPN with Global SIP connect trunks

Internet Transport Interconnect – access to services for public Internet connected video conferencing endpoints (including Cisco Jabber), XMPP endpoints (i.e. jamvee™UC desktip/mobile/WebRTC apps), or public Internet Federated Microsoft Lync endpoints.

PSTN Access – for audio-only endpoints

3.1 Access method #1: dedicated MPLS GVPN (private addressing)

In order to provide secure, private transport access between video endpoitns on a self/3rd party managed

video network (e.g. in the case of an unmanaged customer) and the GMX Network, we offer a new GMX

MPLS Access Trunk over MPLS GVPN transport service – with or without a cloud-hosted firewall.

This GMX MPLS Access Trunk can be deployed using either standard private addressing. The GMX MPLS

Access Trunk consists of:

• An MPLS GVPN Layer 3 Transport Connection between your datacenter and the closest

MPLS/GMX PoP Node provisioned with multiple VRFs

• VRF #1 – SIP/H.323 Trunk: a Layer 5 (SIP or H.323 Gatekeeper Trunk) connection between your

Call Control or Session Border Controller and the GMX SBC (for SIP) or VCaaS

Gatekeeper/VCaaS VCS (for H.323) at the closest GMX PoP Node. This connection is required if

you have any Immersive TP and/or VC endpoints with enterprise hosted /Call Control/ that require

direct access to the jamvee™UC service.

• VRF#2 – vUTM Hosted Firewall: using either Direct Internet Access over MPLS and/or

SSOCvirtual Unified Threat Management ( vUTM) hosted firewall accessed over MPLS transport

for private routing of public addresses for apps such as the jamvee™UC Desktop/Mobile App. This

that allows a connection from your Internet Router infrastructure to the GMX DMZ over dedicated

MPLS GVPN CoS2 service and a vUTM firewall connection to an IP Transit (AS6453) network.

• A local loop is also required to connect the customer premise (CE) to the nearest MPLS PoP.




The MPLS GVPN service provides the following benefits for jamvee™ Unified Communications service

customers:

Broad Reach – fully meshed MPLS core transport network covering 55+ global PoP locations that support CoS 2 transport for video connections.

Managed Transport – MPLS managed end-to-end turnkey solution for full service lifecycle support

Converged Network – supports video Class-of-Service prioritizations (e.g. MPLS CoS2) to maintain optimal call quality for real-time video connections to the GMX Core Network

CoS based Service Level Guarantees – includes MPLS benefits for packet loss and jitter as reflected in the jamvee™ Unified Communications Service SLA’s

Redundant Architecture – to maintain highest possible service availability including backup and resiliency options for higher service uptime

Public IP Address Routing – support for customer’s Internet bound traffic over private transport to leverage the CoS 2 capabilities of the TC GVPN Service using the vUTM hosted firewall offering.

This access method is ideal for customer who have an existing MPLS network from a jamvee™ service provider,

or are already using MPLS to access GMX services or require the guarantees benefits and performance offered

by a private MPLS network connection to GMX.

GMX MPLS SIP Trunk Solution (VRF #1) can be used for the following jamvee™ supported endpoints:

Any enterprise-hosted Cisco Immersive telepresence or video-conferencing endpoints (e.g. Cisco CTS/TX/IX or MX/EX-Series endpoints) that are registered to an enterprise-hosted CUCM/SBC

Any enterprise-hosted Polycom video conferencing endpoints (e.g. HDX-series endpoints) that are registered to an enterprise-hosted Gatekeeper (H.323) or a SIP-based Call Manager.

NOTE: jamvee™UC Desktop/Mobile Apps and the Microsoft Lync federation endpoints are not supported via

the GMX SIP/H.323 Trunk type of jamvee™ access method.

TGMX MPLS vUTM Trunk Solution (VRF #2) can be used for the following jamvee™ supported endpoints:

Jamvee™UC Desktop App for MS-Windows and Apple Macintosh connected to the enterprise LAN

Jamvee™UC Mobile App for Apple iOS connected to the enterprise LAN

Jamvee™UC WebRTC App for Goggle Chrome connected to the enterprise LAN

Supported SIP and H.323 Endpoints connected to the enterprise LAN

NOTE: Cisco Immersive telepresence endpoints (e.g. with E.164 dialling) and Microsoft Lync federation

endpoints are not supported via this type of jamvee™ access method.

GMX MPLS vUTM Access Trunk Considerations

Virtual Unified Threat Management (vUTM) Services enable customers to establish a robust security

architecture to improve security posture and reduce overall total cost of ownership and enable high-quality

access to cloud-hosted services that may not be possible over the public Internet. By entrusting security

administration and management via vUTM you can:




Reduce security administration overhead, maximize existing IT infrastructure and resources, and achieve more efficient use of expensive internal staff.

Choose from multiple service levels to best address your unique requirements.

Attain 24/7 managed security for local networks and mission critical assets.

Receive expert management, monitoring and correlation of all deployed security appliances, network devices and applications.

Access 24/7 telephone/email/web access to certified security professionals.

Reduce connectivity expenses by leveraging the firewall platform’s supported VPN capabilities.

Automate the process of log storage and archival to prove regulatory compliance.

Prevent the spread of network viruses through integrated antivirus capabilities on supported firewall platforms.

Go beyond reporting and leverage integrated intrusion prevention capabilities to reduce the ability for attacks to traverse the network.

Ensure endpoint security policy compliance before allowing access to network resources

3.2 Access method #2: IP transit destination QoS (public internet with QoS) - IZO™

As an alternative to private MPLS Access to GMX, Tata Communications will also offer a GMX IP Access Trunk

which can be provided over an IP Transit network. This GMX connection will offer QoS packet transport over

the IP Transit Internet backbone. This capability offers better overall transport quality to the jamvee™ Unified

Communications service than would be possible over a Communications IP Transit network all the way to the

nearest GMX Core Node.

The IP Transit Destination QoS service (aka IZO) provides the following benefits for jamvee™ Unified

Communications Service customers:

Broad Reach – core Internet (IP) transport network with QoS capabilities covering global network PoPs.

Destination QoS – ability to provide a higher quality level of IP packet transport over Tata Communications global IP backbone. This results in better over quality of experience for a unified conference call with real-time media traffic (video and voice) when compared to standard Internet access to the jamvee™ Unified Communications Service.

Standard Internet Addressing – this access method utilizes standard Internet addressing over a private IP Transit access connection.

Lower Cost – the IP Transit connection is a good compromise between full private MPLS connection (lower cost) and best effort Internet connection (higher quality).




This access method is ideal doe enterprises who require a dedicated Internet transport with QoS to access the

jamvee™ Unified Communications service, but don’t need the full capabilities offered by private MPLS access.

This service will also be targeted at customers that have Internet access with other providers, but want a

higher quality access to the jamvee™ Unified Communications service.

3.3 Access method #3: Federated Microsoft Lync connection over the public internet

This jamvee™ Unified Communications Service access method supports a federated connection from an

enterprise or Lync 365 deployment to the jamvee™ Unified Communications Core Lync deployment. This

connection is called a GMX Federated Access Trunk. A Microsoft Lync Federation connection is the standard

interconnect mechanism supported by Microsoft to allow the interconnection of different Lync domains. The

jamvee™ Unified Communications service includes a Lync domain deployment within the GMX network and

this Lync deployment support federation connection to any other customer Lync domain and can be used so the

customers Lync endpoints can directly access the jamvee™ Unified Communications Service.

The GMX Federated Access Trunk provides the following benefits for jamvee™ Unified Communications Service

customers:

Ease of Provisioning – this access method is the easiest way to get Lync EP access into a jamvee™ Unified Communications conference since there are no transport link to provision as would be the case with AM#1 and AM#2, but the quality and performance is limited to “best effort” since this is a direct public Internet connection.

Lowest Cost – this option is the lowest cost option for connecting Microsoft Lyn EPs into the jamvee™ Unified Communications Service.

This transport access method ideal for enterprises who require federated Microsoft Lync access to jamvee™

Unified Communications conferences but do not want to pay for a dedicated transport using either access

method #1 (MPLS GVPN) or access method #2 (IP Transit Destination QoS).




3.4 Access method #4: video conference and unified communications endpoint access over the public internet

This jamvee™ Unified Communications service access method provides traditional “best effort” Internet access

for video conferencing or unified communications endpoints that requires access to a jamvee™ ‘Room’. This

access method normally does not require any specific provisioning or configuration unless the customer’s

network is not properly configured to allow video (SIP/H.323/RTP/SRTP) or UCC (XMPP/RTP/SRTP) traffic to

access the Internet across the enterprise firewall and proxy servers.

The GMX Internet Gateway Access provides the following benefits for jamvee™ Unified Communications

Service customers:

Direct/Easy access – no provisioning or configuration required as along as the endpoint is supported (see Appendix A) and can access the Internet across the customer’s firewall/proxy servers.

Public URI-based dialling – jamvee™ Rooms can be easily access from any point on the Internet using a public service URI (e.g. [email protected]) or a public URI (e.g. [email protected]) for endpoints that dial via a URI.

Public URL-based dialling – jamvee™ Rooms can be access from any point on the Internet using a public service URL (e.g. https://jamvee.com/invited.sf?id=1234567890) for endpoints that dial via a URL (e.g. WebRTC or user clients)

No access costs – Internet access to the jamvee™ Unified Communications Service is provided at no additional costs, except for the end-user’s ISP access charges that they would normally pay to their local Internet Service Provider (ISP).

This access method is ideal for customers or guest participant that do not require dedicated transport.

3.5 Access method #5 and #6: PSTN toll (#5) and toll-free (#6) access for audio-only endpoints

The jamvee™ Unified Communications Service also provides a set of access options for telephone users (audio-

only) that need to connect. A jamvee™ user behind the PSTN from a wired or wireless endpoint can dial a

specific in-country Toll or Toll-Free PSTN access number and be routed to the jamvee™ Unified

Communications Service. The GMX PSTN Gateway Access consists of:

Toll (LNS) access numbers – currently the jamvee™ Unified Communications Service provide support for local access numbers that can be dialled in-country or from nearby country where a toll number is not provided and toll access is required. Toll numbers are currently available in the following countries (for a list of the actual dial-in numbers see Appendix– Audio-only PSTN access numbers):

o India o Japan o Singapore o United Kingdom o United States

mailto:[email protected]


https://jamvee.com/invited.sf?id=1234567890




Toll-Free (ITFS) access numbers – currently the jamvee™ Unified Communications service provide support for in-country Toll-Free access numbers that can be dialled in-country4 to access a jamvee™ conference. Toll-Free access numbers are currently available in the following countries (for a list of the actual dial-in numbers see Appendix– Audio-only PSTN access numbers):

o Australia o Canada o France o Germany o Hong Kong o India o Japan o Mexico o Netherlands o Saudi Arabia o Singapore o South Africa o Spain o United Kingdom (UK) o United States (US)

PSTN routing– all calls destined to a jamvee™ Toll or Toll-Free Access Number are routed via the PSTN into a Global Voice Network via any one of the many interconnect points. These calls eventually terminate on a GMX PoP via a voice SIP Trunk between the GMX ASR SBC and Global Voice Network.

The GMX PSTN Gateway Access provides the following benefits for jamvee™ Unified Communications

Service customers:

Toll and Toll-Free Access – allows the customer to decide whether they want to pay for PSTN access charges for their end-user participants to access a jamvee™ Room.

In-Country Access – customers can offer their end-user participants of a jamvee™ Room with a local access number.

Global Voice Backbone – customers leverage Tata Communications’ extensive global voice footprint which can be an advantage for Wholesale Customers that need global voice access when reselling the jamvee™ Unified Communications service.

This access is ideal for individuals that need to use an audio-only endpoints to access a jamvee™ unified

communications service/

4 Please note that not all toll-free numbers are accessible from all PSTN network providers within a specific country. For example, in some countries (i.e.

Japan) a toll-free number may not be accessible from a specific wireless network provider within that country. In most cases, a toll number can be used

to access the jamvee™ Unified Communications Service from an audio-only device.




3.6 Access method #7: dedicated On-Net SIP trunk for audio-only endpoints

The jamvee™ Unified Communications service also provides a dedicated, on-net audio-only access option using

a private SIP Trunk from the customer’s Call Manager (e.g. Cisco CUCM, Avaya, etc.) to the GMX PoP. This

connection is provided via private transport and supports PSTN-bypass for calls from the enterprise directly into

the jamvee™ Unified Communications service Bridge.

The GMX On-Net SIP Access Trunk provides the following benefits for jamvee™ Unified Communications

Service customers:

Lower Cost Access – low-cost audio access to the jamvee™ Unified Communications Service for customers with large audio conference usage when compared to using the PSTN.

This access method is ideally suited to organizations with large audio-only usage of the jamvee™ Unified

Communications service where fixed cost access is lower than PSTN access.

3.7 Access method #8: On-Net access from other video services

The jamvee™ Unified Communications service also support access from other existing customer Video Services

(dependent on your jamvee™ unified communications partner). Depending on the specific video service, the

access is already provisioned and built-in to the service, i.e. routing to a jamvee™ conference is already

provision such that a video endpoint connected to that service can access a jamvee™ conference as a

Participant (with the appropriate credentials) or a Host (if they subscribe to jamvee™ Unified Communications

services). Endpoints using the following video services will have access to the jamvee™ Unified

Communications service:

VCaaS (a service available to customers of Tata Communications)

Unmanaged Customers (requires customers CUCM/VCS dial-plan routing update to access jamvee™ if not already configured) – Not available for CTS endpoints, supported video conferencing equipment is available – please refer to table in the Appendix.

Managed Intranet customers of Tata Communications with a GMX Access Trunk (requires customers CUCM/VCS dial-plan routing update to access jamvee™ if not already configured) – Not available for CTS endpoints, supported video conferencing equipment is available – please refer to table in the Appendix.




3.8 Conference Dial-Out (Host Initiated)

In addition to the currently offered jamvee™ service on-demand dial-in capability, starting with jamvee™ R4.2,

the service supports the ability to dial-out (on-demand) from the bridge to any addressable video/audio endpoint

device, via the Internet and/or the PSTN. The jamvee™ Desktop/Mobile Apps and the jamvee™ UC WebRTC

App support the ability for the host (i.e. the VMR owner) to dial-out from a VMR using the “Invite People to Join

the Call” button while on an active conference on a VMR as illustrated in the following diagrams:

Dial-Out from an Active VMR Conference to a PSTN Endpoint

In this case a valid PSTN E.164 number (e.g. +1-732-888-6795) is used to add a participant to the conference

with an audio device (i.e. a telephone). The telephone number is entered in the “call someone” field following by

the return key. Once the request is made the jamvee service starts to initiate a PSTN call leg from the bridge to

the endpoint device (called party). Once the user answers they are prompted to see if they want to join the

conference and if they agree they are connected as a participant (guest) to the conference being hosted on the

VMR from which the call was initiated by the Host/VMR Owner.

Dial-Out from an Active VMR Conference to an Internet Endpoint

In this case a valid Internet URI address (e.g. [email protected]) is used to add a participant

to the conference with an audio/video or UCC endpoint device (i.e. any jamvee™ endpoint that is SIP-compatible

like a VC endpoint). The SIP address is entered in the “call someone” field following by the return key. Once the

request is made the jamvee service starts to initiate a SIP URI call leg from the bridge to the endpoint device

(called party). Once the user answers they are connected as a participant (guest) to the conference being hosted

on the VMR from which the call was initiated by the Host/VMR Owner.




NOTE: Conference Dial-Out capabilities are only offered and available from the jamvee UC Desktop/Mobile

Apps or the jamvee UC WebRTC App when registered with the jamvee service as the Host/VMR Owner. The

conference control mechanism required to dial-out is only available in these Apps. This is not available via any

other jamvee™ UC supported endpoints because the conference control capabilities are not available on those

devices.

The following Conference Dial-Out capabilities are currently not supported:

1. Private Dial Plan Endpoints – there is currently no support for host initiated conference dial-out to GMX endpoints that are on a private dial-plan and private network (e.g. unmanaged customers with a GMX Access Trunk and on-boarded endpoints) as these endpoints are typically not addressable via the public Internet. These endpoint must dial-in to a jamvee UC R4 conference.

2. TPaaS/VCaaS Endpoints – because TP/VC endpoints on the TPaaS and VCaaS service have a private dial-plan on private network, these endpoints cannot be dial-out from a jamvee R4 conference hosted on a VMR as these endpoints are not addressable via the public Internet. These endpoint must dial-in to a jamvee UC R4 conference.

3. Public Rooms – because Public Room endpoints have a private dial-plan on private network, these endpoints cannot be dial-out from a jamvee R4 conference hosted on a VMR as these endpoints are not addressable via the public Internet. These endpoint must dial-in to a jamvee UC R4 conference.

4. Any H.323 Endpoints – since the current Conference Dial-Out capability is SIP URI only, dial-out to H.323 VC endpoints is currently not possible. These endpoint must dial-in to a jamvee UC R4 conference.

3.9 Distributed Conferencing

Starting with jamvee™ rel4.4, the deployment of Core Servers have been configured to support distributed

conferencing. This feature allows jamvee conference participants in a single conference call on a VMR to be

distributed across multiple-globally deployed MCU’s in a cascaded fashion while providing the meeting

participants with a consistent meeting experience as if they are on a call on the same bridge/MCU5. The

distributed conferencing feature provides the following benefits:

Scale –the ability to have an increased jamvee™ bridging capacity because a call can span multiple-bridges at the same time so bridging resources are used more efficiently. This covers both the ability to run more concurrent jamvee meetings and the ability to run larger individual meetings. Currently, Total Capacity is up to 1,000 hardware ports capacity of HD video conferencing (up to 720p @ 30 fps) or up to 48,000 hardware ports capacity of audio conferencing (or any combination thereof) deployed across the existing four jamvee PoPs.

5 Please note the exceptions described in the TIP User Guide user guide document.

https://enterprise.jamvee.com/partners/enterprise.jamvee.com/resources/jamveeUC_TIP_user_guide.pdf




Resilience – Is the ability of the jamvee ™bridges to continue running after failure of one component. This is normally at a reduced capacity for a period of time in which the component outage exists. Resiliency includes handling network failures and loss of data centres.

Geographical Distribution – the ability to use the jamvee™ bridge resources closest to the end-user thus avoiding long connections over non-QoS network such as the Public Internet. This includes connecting to a single jamvee bridge instance closest to the participants (e.g. end-users in Europe will connect to the jamvee London PoP and end-users in Asia would connect to the jamvee Singapore or Sydney PoP depending on their location in Asia) and the use of multiple bridge instances with each participant being connected to the jamvee bridge PoP closest to them.

Point of Presence – is a location where one or more jamvee™ bridge instances are located, currently that includes London, New York, Singapore and Sydney. The jamvee™ bridge instances within a jamvee PoP are connected via a LAN and the jamvee PoPs are interconnected via a dedicated Gigabit-Ethernet fibre backbone global network trunk that is solely used and managed to support TC’s unified communications and collaboration services like jamvee™ UC. A PoP may correspond to a single jamvee™ datacentre or a customer site.

The following diagram illustrates a sample distribute conference call on the same VMR across two jamvee

PoPs (NY and London):

Figure #7 – Jamvee Distributed Conference

In this figure we have a single conference call with the following endpoints:




VC Endpoints – in this example we have two VC endpoints (EP2 – a Cisco EX90 and EP3 – a Polycom HDX) both dial-in to the jamvee™ PoP in New York either via the public Internet leveraging the jamvee™ GeoDNS routing capabilities6 by using the standard access URI: [email protected] or 1234567890.vmr@jamvee .com or the URL: https://join.jamvee.com/invited.sf?id=1234567890. The jamvee.com GeoDNS is configured to route endpoints in North America to the New York jamvee™ PoP if dialling over the Internet or they will be provisioned to access the NY PoP via a private access trunks from the enterprise to GMX (Exchange Access Trunk).

Desktop/Mobile Endpoint Apps – this example includes a jamvee™ UC Mobile App running on iOS device in New York and the jamvee™ UC Desktop App running on an Apple Macintosh laptop in Amsterdam, both connected to the Internet. In this case, both endpoints are routed to the appropriate jamvee™ Edge Server via the TURN Server routing capabilities of the Edge Servers. Unlike the GeoDNS approach that is used for VC endpoints or Microsoft Lync, the jamvee™ UC App routing is more sophisticated and takes into account the characteristics of the network (jitter, packet loss, latency) between the endpoint and the closest Edge Server. The system will always try to use the most effective Edge Server from a performance and quality perspective based on the end-user’s location and the quality of their current connection.

Immersive Endpoint – in this example, a Cisco TX 9000 three-screen immersive endpoint is connected to the jamvee conference call from Paris. It is likely that this endpoint is on the scheduled conferencing network (for a managed user) or access is provided via an Exchange Access Trunk (for an un-managed user) or connected to an IXC Partner Exchange (for someone accessing via another supported telco). In this scenario the endpoint routing is provisioned based on the service the customer is using to register their endpoint.

Microsoft Lync Endpoint – Lync endpoints typically connect to jamvee™ using federation from the enterprise Lync Edge Server (closed federation) or just dial using a jamvee™ URI using the jamvee.com domain. In order to do this they must federate with or just dial-out to the jamvee.com domain and the enterprise Lync user is always connected to the in-region jamvee PoP via GeoDNS.

Distributed Conference Link – in between the two bridges shown in the above illustration, a cascade link is establish in order to connect the entire conference for the six endpoints shown above. This cascade link carries the audio, video, content sharing, IM/Chat and Presence information pertaining to the single meeting (VMR) on which this conference is being held. This provides the end-user with the appearance that they are all on a single bridge when in fact their call is actually geographically distributed between Europe and North America in order to achieve a highest-level of quality and performance for the overall meeting.

Note: Please note that there are some limitations on the conference user experience (i.e. endpoint that can be

seen from a specific endpoint) across the distributed conference link.

6 Note that the GeoDNS is a DNS service that is configured for jamvee so that when an end-user enters a URI or URL in an endpoint device that includes

jamvee.com as the domain, the DNS servers will route the request to the appropriate jamvee PoP based on the IP address of the user and which region the

address is located.





3.10 Telepresence Interoperability Protocol (TIP) Support

The jamvee™ service provides support for Cisco-based Telepresence equipment that are compatible with the

Telepresence Interoperability Protocol (TIP) standard for multi-screen immersive room conferencing systems.

The TIP protocol prescribes a method of multiplexing multiple video streams, audio streams and a single

auxiliary-data sharing streams into Real-Time Transport Protocol (RTP) flows - one each for video and audio.

It enables point-to-point and multipoint audio, video, and content sharing sessions across both multi-screen

and single-screen compatible equipment. The TIP protocol also defines how RTP Control Protocol (RTCP) are

used to indicate profile capabilities and media flow options, and how devices can provide feedback and trigger

resiliency mechanisms during a session. The addition of TIP support to the jamvee™ service enables 3-

screen Cisco CTS/TX based equipment to participate in jamvee™ meetings and provide a fully immersive

experience.

This document provides a description of the expected user experience when using a variety of single screen

and/or multi-screen TIP and non-TIP devices on a jamvee™ UC conference. The user experience of a multi-

screen TIP system user will differ depending on the mix of equipment in the meeting and whether the

conference is held on a single jamvee™ bridge, or distributed across multiple bridges.

The specific details of the additional TIP endpoints that are supported on the jamvee service is document in

Appendix A.

3.10.1 Behavior of TIP systems in the jamvee™ service - 3 screen and single screen systems

Transmissions from 3-Screen TIP room-based systems (e.g. CTS 3000 Series, TX-9000 Series, etc.)

o The immersive telepresence system contributes all 3 video segments (one per camera on a three screen system) up to the closest jamvee™ bridge

o Only the active speaker segment (loudest conference participant) of a multi-segment telepresence system is sent to other single-screen systems on the same conference

o Only the active speaker segment (loudest conference participant) of a multi-segment telepresence system is distributed to remote jamvee™ bridges in a distributed conference

Receiving at 3-Screen TIP room-based systems (e.g. CTS 3000 Series, TX-9000 Series, etc.)

o If the active speaker (loudest conference participant) is on a 3-screen endpoint on a local bridge then all 3 streams are shown on the respective large displays of the receiving telepresence unit.

o Otherwise up to 3 separate systems are shown in the large screens, including the active speaker o If there are more attendees than can be displayed on the 3 large screens at the receiving

telepresence system, then these are shown in a filmstrip at the bottom of the screen. o If there aren’t enough attendees on the call to fill all the main display screens (e.g. active

speaker on a one screen system dialing into a 3-screen telepresence room with no other attendees) then the “empty” screens at the receiving telepresence room will be filled with a background image

Transmissions from a Single Screen TIP system (e.g. CTS 500 Series, CTS 1000 Series)

o The single screen is sent to the closest jamvee™ bridge




o The bridge sends the single screen to the other units connected to it o The bridge sends the single screen to the other jamvee™ bridges connected in a distributed

conference

Receiving at Single Screen TIP system (e.g. CTS 500 Series, CTS 1000 Series)

o The active speaker is shown in the main screen (for standard “filmstrip” view) or as a highlighted square in an all-equal (aka Hollywood squares) view

Content Sharing o Any 3-Screen TIP system that have a dedicated screen or screens for content sharing and will

use that screen to display the content o Other systems will see content from a 3-Screen TIP system identically to content from any other

system o Content sharing is handled and displayed consistently irrespective of the number of jamvee™

bridges involved in a conference

For further information and use examples please refer to the TIP User Guide

https://enterprise.jamvee.com/partners/enterprise.jamvee.com/resources/jamveeUC_TIP_user_guide.pdf




3.11 Conference Features/Capabilities

The following list provides a definition of new conference specific feature that are not covered elsewhere in

this document:

1. Clear Chat Feature – the jamvee™ UC Desktop/Mobile Apps and the jamvee™ UC WebRTC App now support the ability to manually clear chat history from a VMR that is used to support different and non-related meetings/conferences. Under normal circumstances, any chat messages posted to a specific VMR is persistent and the chat content can be preserved from meeting-to-meeting in the same VMR. The Clear Chat feature on the jamvee™ UC Apps allows the host/VMR owner to manually clear all historical chat messages from a specific VMR.

2. IVR DTMF Enhancements – software upgrades to the jamvee™ IVR have been deployed to the production jamvee service to provide more reliable DTMF detection when the user is entering their Host or Participant CallID/PIN in specific call flows. With this enhancement the IVR now support both in-band and out-of-band DTMF detection.

3. AC Keypad Controls: Basic Set

Audio Conferencing (AC) Keypad Conference Control allows an jamvee™ Host/Participant user connected

to a VMR on the jamvee™ service via a SIP call flow (e.g. via the PSTN or a VC endpoint connected via

the public Internet) to control certain aspects of the conference (e.g. mute, unmute, mute all, and unmute

all) using the keypad on the endpoint device. The capability is not currently available via the jamvee UC

Desktop/Mobile Apps or the Microsoft Lync call flows, only Host/Participant endpoints that connect to the

jamvee™ service via a standard SIP call flow will have access to this capability.

The supported commands are:

i. *6 – will toggle audio mute/unmute for a specific user (host or participant) on a specific call leg in

the conference ii. *96 – will mute all participants on all call legs on the conference except for the Host (this command

can only be issued by the Host) iii. *97 – this command will unmute all participants on all call legs on the conference (this command

can only be issued by the Host) iv. *93 – this command will terminate/disconnect all participants in the conference (Host only)




4. Dial-Out for H.323 Video Calls (round robin-solution)

This capability allows the conference host/mediator to dial-out from a VMR to a Video Conference endpoint

that support the H.323 protocol (legacy video conferencing endpoints). The call will originate on the call

bridge (jamvee infrastructure) and connect over the public Internet access points at each jamvee PoP. The

jamvee Meeting Hosts and authorized Meeting Room Members using the Jamvee UC Desktop/Mobile Apps

user can now:

Add-in Internet reachable H.323 capable video endpoints (e.g., room systems, desktop video systems, etc.) in to a VMR at any time using IP address dialling. If the user has the IP address, open the “Call Panel”, click “Invite people to join call” button, enter the IP Address dial string (e.g., 123.123.123.11) and click the “Call” button.

Move the jamvee™ UC app audio and video from the user’s computer or iPad to an Internet reachable H.323 compatible video room or desktop system using IP address dialling. If the user has the IP address of the target room or desktop video system “Connect phone or video device” button, click “Add Device”, enter the IP Address dial string (e.g. 123.123.123.11), the desired device name and whether it’s a single or dual screen video system, click “Save”, select the device from the listing and click “Connect”.

Place a call to an Internet reachable H.323 capable video endpoint (e.g., Room systems, desktop video systems, etc.) using IP address dialling. If the user has the IP address of the target video system, click the “+Call” button, enter the IP Address dial string (e.g., 123.123.123.11) and click the “Start Call” button.

Please Note: It is possible that some H.323 video endpoints will not establish audio and/or video, nor provide high

quality video and/or audio, nor support receiving shared content, nor support sending content that could be seen by

other Jamvee meeting attendees. Please check the Jamvee Endpoint Compatibility Matrix listed in the Appendix.




4 Microsoft Lync federation to jamvee.com Microsoft Lync supports “federation” features and provisioning within Lync to allow external users in other public

and/or private Lync SIP domains be able to collaborate with internal users within the enterprise using the Lync

client application. The federation capability supports external communication and collaboration via IM, Presence,

Audio and Video including Content Sharing with user outside their own Lync domain.

In order to support standard Microsoft Lync federation to the jamvee™ Unified Communications service, Lync

Edge Servers must be deployed in the enterprise and across the jamvee™ service PoPs. An enterprise must

deploy a Lync Edge Server outside the enterprise firewall so that signalling (SIP) and media (Audio, Video,

content sharing, IM, and presence) connections can be established from within the internal enterprise Lync

deployment to other external public or private Lync deployments like the jamvee™ Unified Communications

service. As with the enterprise, the Lync Edge Server deployed in the GMX DMZ (i.e. the GMX perimeter

network) controls how users outside the GMX firewall can connect to the jamvee™ internal Lync Core Server

deployment within GMX. The following diagram illustrates the typical Lync federated deployment to the jamvee™

Unified Communications service:

Figure #3: Microsoft Lync Federation with jamvee.com

The GMX Lync Edge Servers are deployed with an Open Lync federation model that can be auto-discovered

by enterprise Lync deployments. In most cases, if open Lync federation is configured on both sides, federated

access to the jamvee™ Unified Communications service Lync Edge Server configuration should be

automatically setup when the users creates their first session to jamvee.com. If that fails, then the following

provide high-level steps as a guideline on how to manually configure federation with the enterprise Lync Edge

Servers on the jamvee.com domain:

1. From a user account that is a member of the RTCUniversalServerAdmins group (or has equivalent user rights), or is assigned to the CsAdministrator role, log on to any computer in the internal Lync enterprise deployment.

2. Open a browser window, and then enter the Admin URL to open the Lync Server Control Panel. For details about the different methods you can use to start Lync Server Control Panel, see Open Lync Server Administrative Tools.

http://technet.microsoft.com/en-us/library/gg195741.aspx

http://technet.microsoft.com/en-us/library/gg195741.aspx




3. In the left navigation bar, click Federation and External Access, and then click SIP Federated Providers.

4. On the Edit SIP Federated Provider page, you can type or edit the following settings:

a. Enable communications with this provider – selecting this setting enables federated communications with this provider’s users (i.e. other users on the jamvee™ Unified Communications service).

b. Provider name – a required property, type the name of the provider as reflected in the listing of SIP Federated Providers (e.g. jamvee.com).

c. Access Edge service (FQDN) – a required property, type the fully qualified domain name of the Access Edge service of the hosted provider that you are configuring. This information is provided by the hosted provider, and should only be changed if the hosted provider makes a change to the FQDN of the Access Edge service at the hosted provider. For the jamvee™ Unified Communications service the FQDN for the Access Edge service is:

i. Access Edge service (FQDN) = lyncfed.jamvee.com

ii. this FQDN will always connect via GeoDNS to the closest GMX Lync Edge Server to

the enterprise Edge Server to minimize latency between eth end-user and the jamvee™ bridge.

d. Default verification level – the default setting, Allow users to communicate with people on

their Contacts list who use this provider will limit communication to contacts that you have accepted and are in your contact list. Selecting Allow users to communicate with everyone using this provider removes the restriction that you must have received and accepted a contact invite. This setting does not limit who can contact you from the hosted provider’s network. It is up to the customers to decide how they want to configure this parameter for jamvee.com federation.

5. When you are done configuring the settings, click Commit to save, or click Cancel to discard your

changes.

4.1 Lync federation and configuration document

A separate document is available which covers all the steps required to federate your Lync estate with the Jamvee™ Unified Communications service. Please download the document here: jamveeUC_lync_federation

https://enterprise.jamvee.com/partners/enterprise/resources/jamveeUC_lync_federation.pdf




5 VNOC helpdesk support services

The Jamvee™ Unified Communications service includes phone technical support helpdesk to help end-users

who are having problems accessing the jamvee™ service. The technical support processes will include:

VNOC Level 1 Phone support for 24x7x365 coverage for jamvee™ “Triage” troubleshooting including: o Comparing the user provided information against what is available in the service provisioning

for Call-ID/Passcode (verified at the SDP–level) o Confirm customer access and dialling instructions o Test the Room by dialling the platform and entering the user provided Call- Id o Determining whether the endpoint been on-boarded or certified and whether the customer’s

dial-plan supports access to the jamvee™ service via any of the three access methods listed previously.

VNOC Level 1 Technical Support for end-user commonly asked questions o My Call-Id or Passcode is not working o Why am I getting a busy tone? o I am hearing this announcement o Do I need to dial a prefix? o How do I add an audio endpoint to the conference?

VNOC Level 1 Basic Triage for Guest or “Best Effort” Endpoints o Triage troubleshooting procedures for determining basic user Service issues including Call

ID/Passcode verification, access numbers or URI/URL/E.164 verification, basic Internet network troubleshooting, video related issues, audio related issues, etc.

o Confirming that endpoint and its software version is supported by the Service o Making the user aware that there may be Customer configured dial-plan issues (e.g. dialling or

trunk access codes/prefix, if required)

Escalation to VNOC Level 2 support o Identify if troubled endpoint is managed or unmanaged o If managed,

Standard endpoint fault management process is executed for managed endpoints Escalation to Level 3 support (ASD VNOC) to validate GMX platform and network

connection for CTS or VC endpoint o If unmanaged,

Escalation to Level 3 (ASD VNOC) to validate GMX platform and network connection for CTS endpoint

o If a Voice-only PSTN Network Issue Escalate to ASD VNOC for Voice Network Support ASD VNOC escalate to Enterprise Voice team for support & remediation

o Issues identified with GMX infrastructure are escalated to ASD VNOC for remediation




6 Conference access and production The jamvee™ Unified Communications service support a variety of different ad-hoc/on-demand conference

access scenarios depending on the call flow, the type of endpoint used to access the jamvee™ conference, and

whether the user is a host/moderator, a participant (authenticated user) or a guest participant (non-authenticated

user). The entire conference experience is driven by a virtual meeting room conference construct. The jamvee™

Room is the virtual space/room where all jamvee™ conference are hosted and has many attributes and user

access methods. In jamvee™ Unified Communications, a conference may or may not require the use of Call-

IDs to access a conference depending on the call flow, the endpoint type and whether the user is already

registered and authenticated with the jamvee™ service and who owns the jamvee™ Room.

For example, if the user is using the new jamvee™ Unified Communications desktop/mobile apps, they are

already automatically authenticated with the service when they entered their service credentials (service account

login/password) during the app installation process. To access a conference as a host/moderator the user can

simply select a provisioned or accessible virtual meeting rooms from the “Rooms” tab on the jamvee™ app and

push the “Start Call” button to enter the virtual meeting room. The user can also access another user’s Room

by simply entering a Participant Call-ID from the “+Call” button on the app and pushing the “Start Call” button.

The jamvee™ Unified Communications apps provide great flexibility in accessing any Room in many different

ways depending on the user endpoint, their user access methods and their network access methods (call

flows/transport). The following terminology and constructs are used when referring to the jamvee™ Unified

Communications service conference access scenarios and associated virtual meeting rooms:

Owner/Account tier – this is the person’s name to which the jamvee™ Unified Communications service account and Room/s are associated (i.e. the account owner). The Owner is also often referred to as the “Host or Moderator” of the Room/s that are provisioned specifically in his/her jamvee™ account. An Owner can have one or more Rooms provisioned for their account. They can also behave as host/moderators for Rooms owned by other jamvee™ user accounts as long as the owner of the room enables direct access rights to their jamvee™ Room to any user within the same tenant tier within the jamvee™ hierarchy.

Enterprise/Tenant tier – the enterprise or tenant tier is the jamvee™ “hierarchy entity” to which the Owner is provisioned. The enterprise/tenant tier defines certain default and required characteristics and access privileges that are associated with all jamvee™ Rooms that are provisioned for all Owner’s within the enterprise/tenant account.

Wholesale tier – in addition to an enterprise/tenant tier, the jamvee™ service also includes a wholesale partner tier under which specific enterprises/tenants can be defined with individual Owners user accounts within each enterprise/tenant. The wholesale tier ties in the root level of the jamvee™ hierarchy.

User types – there are several different user types that need to be considered when access a conference hosted on a specific jamvee™ Room. These types are as follows:

o Host/Moderator User – a host/moderator is an authenticated jamvee™ user that has host

privileges (e.g. the host is able to start a conference when one or more participants have joined a jamvee™ Room). The Owner of a jamvee™ account is always a host/moderator of all jamvee™ Rooms that are provisioned for a specific user account. In addition, any user within a tenant can be given host/moderator privileges by simply adding the user as a “member” of a specific Room in the user portal (from Sept ’14).




o Participant User – a participant user is an authenticated jamvee™ user that can access a jamvee™ Room assuming they have the Participant Call-ID associated with that virtual meeting room. This allows the participant access to conferences hosted on other jamvee™ Rooms owned by other account users but without host/moderator privileges. For example, a participant cannot start a conference on a jamvee™ Room unless they are a member of that virtual meeting room. A participant user always has a jamvee™ user account and can access a conference using any supported user access method over any supported jamvee™ transport access method.

o Guest User – a guest user is a non-authenticated jamvee™ user that does not have any account

credentials on the jamvee™ service and cannot register and pre-authenticate with the jamvee™ service. A guest user must have a Participant Call-ID in order to access a conference hosted on the jamvee™ service. A guest user can only access a jamvee™ Room via:

WebRTC app (requires Google Chrome or Mozilla Firefox browsers) Auto-download Guest App (requires Microsoft IE or Apple Safari browsers) Any video conferencing endpoint (only with endpoints and transport access methods

supported by the jamvee™ Unified Communications service) Any PSTN endpoint (audio only)

Login ID (XMPP JID) – the Jabber Identifiers (JIDs) uniquely identify individual Owners in a XMPP network7. This ID is simply the login credential used by the Owner of the jamvee™ account to register a jamvee™ Unified Communications desktop/mobile app with the jamvee™ edge servers. The format of this login ID is as follows:

o A ten digit number, usually the Host Call-ID for the jamvee™ Room @ jamvee.com, i.e. “Host

Call-ID”@jamvee.com o Example: [email protected] o This login identifier is assigned to the user when their jamvee™ account is created in the

jamvee™ provisioning system (under an Enterprise tier which is under a Wholesale tier) and is valid for registering the jamvee™ Unified Communications Desktop/Mobile Apps.

o The ten digit number is also the same number used as the Host Call-ID for the primary Room associated with the Owner’s account.

o This Login ID is unique within the jamvee™ Unified Communications service.

Login Password – the login password is the password associated with the Owner’s account credentials and tied to their Login ID (XMPP JID). A default password is assigned to the user when their jamvee™ account is created in the jamvee™ provisioning system (under an Enterprise Tier which is under a Wholesale Tier).

o The Login ID and Passwords are both required to register any authenticated jamvee™ Unified

Communications apps to the service, i.e. the jamvee™ Unified Communications desktop/mobile apps and WebRTC App8.

o Once this information is entered after the installation of the jamvee™ Unified Communications app, the information is saved on the Owner’s device (PC/Mac/iPad/iPhone) and subsequently used every time the App is launched.

o The user can also unregister their app from the jamvee™ service by using the “Sign Out” button on the app and sign-in to a different account with different credentials.

o In the current jamvee™ Unified Communications service, the login password is manually assigned during user on-boarding and cannot be changed by the user.

7 The jamvee™ Unified Communications desktop/mobile apps are XMPP clients and the Edge Server is an XMPP Server. 8 Note that the jamvee™ Unified Communications Guest App cannot be used to register to the service and is only use by guest users to the service.




Dial-In URI – the dial-in URI is the fully-qualified Internet URI address (with a resolvable domain) that can be used on the Internet to access any jamvee™ Room configured within the jamvee™ Service.

o The URI contains the Call-ID (i.e. the ten digit number and “.vmr” before the “@” symbol in the URI address) related to the room and identifies which jamvee™ Room the calling party wants to access within the jamvee™ service and with which access privileges, i.e. host or participant/guest. There are two possible Call-IDs (host and participant) associated with each provisioned Room.

o The domain contains the public Internet resolvable DNS domain name for the jamvee™ service (i.e. jamvee.com)

o URI Format: “Host Call-ID”[email protected] e.g. [email protected]

o URI Format: “Participant Call-ID”[email protected] e.g. [email protected]

Dial-In URL – the dial-in URL is the fully-qualified Internet URL address (with a resolvable domain) that can be used on the Internet to access any jamvee™ Room configured within the service using an industry standard browser. The jamvee™ Unified Communications service supports: a) Google Chrome (WebRTC), b) Mozilla Firefox (WebRTC), c) Microsoft Internet Explorer (Guest App) and Apple Safari (Guest App).

o The URL contains the Call-ID (i.e. the ten digit number in the URL address) related to the jamvee™ Room and identifies which Room the calling party wants to access using HTTPS/XMPP within the jamvee™ service. There are two possible Call-IDs (host and participant) associated with each provisioned jamvee™ Room.

o The domain contains the public Internet resolvable DNS domain name for the jamvee™ service (i.e. jamvee.com)

o Host URL format: https://join.jamvee.com/invited.sf?id=“Host Call-ID” e.g. https://join.jamvee.com/invited.sf?id=89901112230

o Participant URL format: https://join.jamvee.com/invited.sf?id=“Particpant Call-ID” e.g. https://join.jamvee.com/invited.sf?id=89901112231

Call-ID – the Call Identifier is a ten digit number followed by “.vmr” that is associated with specific jamvee™ Room within the Owner’s jamvee™ account. In the jamvee™ Unified Communications service a jamvee™ Room has two Call-ID’s:

o Host Call-ID – this is the Call-ID associated with the host/moderator and should only be known

and used by the owner of the jamvee™ Room for security reasons. This Call-ID identifies the user as a host/moderator and automatically launches a conference once one or more participants/guest have join the call. Without the host/moderator the jamvee™ conference is never launched unless the Room is provisioned for not requiring the host to launch the conference. The default is always that the host/moderator is always required.

o Participant Call-ID – this is the Call-ID associated with the participant or guest in a conference

and is provided in the meeting invite to all meeting participants. This Call-ID identifies the user as a participant or a guest and will require the host/moderator before the conference is launched. Without the host/moderator the jamvee™ conference is never launched unless the Room is provisioned for not requiring the host to launch the conference. The default is always that the host/moderator is always required.

o Note that a Call-ID’s are specific to a jamvee™ Room and are unique for each Room within a

URI/URL/XMPP domain (e.g. jamvee.com)



https://join.jamvee.com/invited.sf?id=89901112230

https://join.jamvee.com/invited.sf?id=89901112231




The following table illustrates a sample user account and configuration referenced throughout this section of the

document:

Account/ Attribute Example Notes

Owner/Account Tier: Bob Baker End user name

Enterprise/Tenant Tier: Hot Cupcakes Ltd. End user company

Wholesale Tier: Tata Communications Ltd. Wholesale Partner SP

Login ID - XMPP JID: [email protected] User login for App registration

Password: Pa33W0r3 User login password

Display Name: Bob Baker’s Room Name displayed for the user jamvee™

Room

Access Method A Access Method for the conference host/moderator

Host URI: [email protected] URI for Host/Moderator dial in

Host Call-ID: 8901112230 Jamvee™ Room

Host/Moderator Call ID

Profile: ClassicModerator Profile type

Access Method B Access Method for all conference participants

URI: [email protected] URI for Participant dial in

Participant Call-ID: 8901112231 Jamvee™ Room

Host/Moderator Call ID

Profile: ClassicGuest Profile type

Note: that for each jamvee™ Room there are two access method profiles, one for the host/moderator and one

for all other participants, including guest users. A specific attendee to the conference must use one or the other

depending on whether they are the host/moderator or a participant/guest to the conference.




The user account configuration information shown in the above table can be used in different combinations

depending on the call flow, the type of endpoint and transport access method used to access a jamvee™

conference.

6.1 Dialling guides

The different ways that a host, participant and guest can access the jamvee™ Unified Communications service

have been collated into a separate document – jamvee™ Unified Communications dialling guide (All Methods).

6.2 Bridge resource allocation

The jamvee™ Unified Communications bridge allocation algorithm is defined by the capabilities supported in

the Core Server. There is no custom bridge allocation logic jamvee™ Unified Communications and all allocation

will utilize the MCU cascading algorithm which provides conference hosting optimization depending on the

endpoints participating in the conference and their location, i.e. closest GMX PoP. This algorithm support the

ability to host a single conference across multiple MCU’s by cascading the two bridges in support of a single

conference.

6.3 API services

The current revision of the jamvee™ Unified Communications service will not support any API’s. The first API

will be available in a later release.

6.4 Bandwidth “lane” management

Bandwidth or “Lane” Management is not supported or required for most jamvee™ Unified Communications direct

call flows. This includes the following calls flows:

1. Federated Lync Call Flow 2. Unified Communications Client XMPP/HTTPS Call Flow 3. PSTN Call Flow

For these call flows, there is no bandwidth management supported. The Transport Access Methods used to

support these call flows must be provisioned with the enough bandwidth to support the peak traffic required

across a specific link. All jamvee™ Unified Communications service Internet access links from the Tata

Communications IP Transit network into a GMX PoP consists of Gigabit Ethernet links. These links are

monitored for capacity management purpose and are upgraded should customer traffic exceed the provisioned

capacity. Any private links, including any local loops and IP Transit customer ports for dedicated QoS access,

will have to be designed and provisioned to support the customers anticipated concurrent traffic peaks.

https://enterprise.jamvee.com/partners/enterprise.jamvee.com/resources/jamveeUC_dialling_guide_ALL.pdf




Bandwidth or Lane Management is supported on the following jamvee™ Unified Communications service call

flow:

1. Video Conferencing Call Flow

The bandwidth management capabilities for this flow are identical to those supported in the previous jamvee™

on-demand video conferencing service.




7 Service security Providing secure (encrypted) conferencing capabilities are inherent in the design of the jamvee™ Unified

Communications service. As with the previous jamvee™ on-demand video conferencing service, the Unified

Communications service will support both “Secure” and “Best Effort” encryption on call legs connecting to a

jamvee™ Room. These two options are supported for any of the following jamvee™ Unified Communications

calls flows:

1. Federated Lync Call Flow 2. Unified Communications Client XMPP/HTTPS Call Flow 3. Video Conferencing Call Flow

As with the jamvee™ on-demand video conferencing service, there is no signalling or media encryption

support for the PSTN Call Flow.

The jamvee™ Unified Communications service incorporates a set of security capabilities that provide

customers with options for conducting more secure conference meeting. These features include:

1. Physical Security –includes physical access security at our GMX Network Nodes and the VNOC Data Centre

a. VNOC POPs – are located within hardened, highly available data centre facilities. Each data centre utilizes an array of security equipment, techniques and procedures to control, monitor and record access to the facility, including customer cage areas.

b. On-site manned security 24x365 c. Visitors are screened upon entry to verify identity, and in shared situations, escorted to

appropriate locations. d. All doors, including cages, secured with 2 factor locks (key card and pin) for entry or biometric

hand geometry readers. e. Kinetic locks on all closed cabinets f. CCTV digital camera coverage of the entire centre, including cages, with detailed surveillance

and audit logs g. Confidentiality agreement – each VNOC team member is contractually obligated to keep

confidential all information he/she may be privy to.

2. Transport Security – access to the GMX Core Network can be secured via Layer 3/2 (transport – VRFs/VLANs) when accessing jamvee™ Unified Communications service via dedicated network (MPLS/DGE)

a. Dedicated connections to GMX are provisioned as separate transport VRFs/VLANs for separation of different customer traffic at Layer 3/2 across a shared core transport network (e.g. MPLS/DGE)

b. For the Video Conferencing Call Flow with MPLS/DGE transport access methods, each

VRF/VLAN is also connected to the GMX Core using a Session Border Controller (SBC) which provided signalling and media adjacencies to isolate session level traffic for different customers

c. The GMX Interworking VCS’s and the jamvee™ on-demand video conferencing app Registration Server (RTP Servers) are located in the GMX DMZ and are connected to the GMX




Core Network using a Session Border Controller (SBC) which provided signalling and media adjacencies to isolate session level traffic from the Internet

d. Although jamvee™ Unified Communications service Internet transport access method does not provide transport access security (because it is the public Internet), all new jamvee™ Unified Communications app support TLS/SSL for signalling encryption and AES encrypted media (via SRTP) when connecting to the jamvee™ Unified Communications service.

3. Endpoint and Infrastructure Security – depending on the endpoint type, there may be additional

authentication and encryption capabilities that can be supported to further secure a conference with media encryption. Currently this is available for endpoints that support and are configured for secure conference access (signalling via SIP over TLS and media over SRTP w/128 bit encryption) and for the jamvee™ Unified Communications desktop/mobile apps with support TLS/SSL for signalling encryption and AES encrypted media (via SRTP).

4. Conference Access Security – the jamvee™ Unified Communications service requires a Host Call-ID or Participant Call-ID for conference access. A jamvee™ Room can be provisioned (default for all jamvee™ Rooms) for requiring the host/moderator to join the conference before participants/guests are allowed to communicate with each other. The jamvee™ Unified Communications conference is not started until the conference moderator joins with their Host Call-ID or directly via authenticated jamvee™ Room access (see the Conference Access and Production section of this document for authenticated jamvee™ Unified Communications app access to a jamvee™ Room).

5. Conference Production Security – jamvee™ conference encryption can be provided on a “Best Effort” basis or as a Secure Conference as follows:

a. In the case of “Best Effort” (the default), the conference is encrypted if all endpoints dialling in are endpoints that support encryption and can negotiate encryption with the jamvee™ Unified Communications Bridge. If an endpoint does not support encryption (or encryption not configured) than that specific call leg of the conference will not be encrypted.

b. In the case of a “Secure Conference”, the jamvee™ Unified Communications service will not allow an endpoint to join the conference that has been provisioned as a “Secure Conference” unless it can negotiate encryption with the Jamvee™ Bridge.

c. In order to support Secure Conference the users jamvee™ Room hosting the call must be provision for “Required” encryption setting in the jamvee™ Room profile. The default for users is always best effort encryption (or the “Allowed” setting on the jamvee™ Room profile).

As mentioned previously, there is no support for encryption from the PSTN Call Flow

The following diagrams illustrate the encrypted flows for the two new calls flows (federated Lync and jamvee™

unified communications apps) in the jamvee™ Unified Communications service:




7.1 Encrypted federated Lync call flow

The jamvee™ Unified Communications Federated Lync Call Flow supports the standard Microsoft Lync client-

to-server and server-to-server encryption security protocols (see [2] for more details). This includes using TLS

and MTLS to encrypt instant messages, for SIP signalling, and for content sharing/web conferencing. Media

encryption uses standard SRTP encryption protocols (AES). All server-to-server traffic requires MTLS,

regardless of whether the traffic is confined to the internal enterprise network or crosses the internal network

perimeter (DMZ).

Microsoft requirements for client-to-client traffic depend on whether that traffic crosses the internal corporate

firewall. Strictly internal traffic can use either TLS, in which case the instant message is encrypted, or TCP, in

which case it is not. In order to support end-to-end encryption when connecting to a jamvee™ Unified

Communications conference, the enterprise should deploy TLS for IM, signalling (SIP), content sharing/web

conferencing and SRTP for Audio/Video media encryption. The end-to-end secure call into a jamvee™ Unified

Communications conference is illustrated in the following figure:

Figure #4: Security for the jamvee™ Unified Communications federated Lync call flow




7.2 Encrypted unified communications client XMPP/HTTPS call flow

The jamvee™ Unified Communications apps support TLS/SSL for signalling and IM encryption and AES

encrypted media (via SRTP) when connecting to the jamvee™ Unified Communications service. The WebRTC

client uses HTTPS/SSL for secure communications between the app and the jamvee™ Edge Server, the

jamvee™ Unified Communications apps use TLS and secure communications between the app and the

jamvee™ Edge Server. The Client XMPP/HTTPS Call Flow end-to-end secure call into a jamvee™ Unified

Communications service conference is illustrated in the following figure:

Figure #5: Security for the jamvee™ Unified Communications client XMPP/HTTPS call flow




8 Support for mobile video endpoints

The jamvee™ Unified Communications service provides support for various mobile endpoints including the

following endpoints9:

Mobile Client for iPad

Mobile Client for iPhone

Jamvee™ Unified Communications Mobile Client for iPad

The Mobile App for the iPad supports:

Video

Audio

Content Sharing (receive only)

IM/Chat

Conference Roster Information

Screen Layout changes

Conference control (e.g. dropping participants from a call)

Mobile Client for iPhone

The Mobile App for the iPhone supports:

Video (new with rel4.5 release)

Audio

IM/Chat

Conference Roster Information

Screen Layout changes (new with rel4.5 release)

Conference control (e.g. dropping participants from a call)

9 For a complete list of supported endpoints see Appendix A.




9 Pricing, billing/reporting, and service schedule

The jamvee™ Unified Communications service will support a variety of different pricing/commercial models in

order to meet different customer needs. This will include metered variable usage based models with little

upfront commitment or unlimited use models with a fixed Monthly Recurring Charge (MRC) and limited

number of participants per conference.

9.1 Commercial models for jamvee™ Unified Communications

The jamvee™ Unified Communications Service commercial models follow these key principles:

1. Conference Usage and Conference Access (transport) are always Charged Separately – the current pricing models for the jamvee™ Unified Communications service separate the charges for conference usage, i.e. charges for actual usage of the jamvee™ bridge, from conference access, i.e. transport charges the user may have to pay to access the jamvee™ bridge (for example: PSTN access charges (toll-free access) for participants dialling into a jamvee™ conference, or MPLS GVPN charges for dedicated, on-net access, or Internet Access fees paid to local Service Providers (Tata Communications or others) to connect to a jamvee™ conference via the Internet). If applicable, these charges will be listed in the Customer Order Form (COF).

2. Metered Conference Rates – there are three (3) different types of metered conference rates/charges

that can be applied to each call leg in a jamvee™ conference:

a. Audio Metered Rate – this is audio-only calls legs (no video, no content sharing). b. Web Metered Rate – this is audio plus content sharing call legs (no video)

c. Video Metered Rate – this is video/audio call legs with or without content sharing (full Unified

Communications capabilities). Video call with endpoints that have multiple will always be charged as a single call leg/participants even though the endpoint uses more resources on the bridge. This is designed to simplify the pricing for jamvee™ conferences so that all rates are per call leg participant.

3. All conference call legs support IM and Presence assuming the users has an endpoint that supports these capabilities on a jamvee™ conference (e.g. jamvee™ Unified Communications apps or Microsoft Lync).

4. Jamvee™ Unified Communications service Pricing Models – the pricing models support up to full Unified Communications with video, audio, content sharing, IM, and Presence or any combination thereof on any call leg on a jamvee™ conference. The following are the supported pricing models:

a. Metered Usage Models – charges based on usage metering of audio-only (no video, no content sharing), audio plus content sharing (no video) or full Unified Communications (UC) (with video, audio and with or without content sharing) at three different rates

i. “Pay-as-you-Go” or PAYG Model – this model has no upfront commitment and

conference usage is metered and charged based on the Audio Metered Rate for an




audio-only or the Web Metered Rate for audio + content call legs of the jamvee™ conference or the Video Metered Rate for a video (or full UC) legs of the jamvee™ conference.

ii. Minimum Commitment Bundles (MRCs) with Overages Model – this model is metered

in the same way as the PAYG model but offers much deeper discounts on the metered usage rates based on the customers up front, minimum MRC commitment. The larger the minimum monthly commitment, the lower the Audio Metered Rate (AC), Web Metered Rate (WC) and Video Metered Rates (UC) that will be applied to the total monthly usage. If the customers exceeds their monthly minimum commitment, then any overages are charges at the same discounted metered rates. If the customer falls below the minimum commitment they will always be charged at least the minimum commitment.

b. “Per Seat/Named User” with Unlimited Usage Models – charges for this model are based on a fixed MRC for unlimited monthly conference usage up to the maximum number of simultaneous participants (call legs) per jamvee™ conference.

i. In this model a specific named user (an individual within an enterprise/legal entity) is provided with one jamvee™ Room that can be used to host a single jamvee™ conference at any one time (no simultaneous conferences). Note: currently a jamvee™ user account that has Per Seat/Named User model can only have a single jamvee™ Room configured for each user. It is expected that this limitation will be removed in a future release.

ii. Jamvee™ Rooms cannot be shared with multiple host users in anything that results in simultaneous conferences. The MRC covers only a single conference at any one time.

iii. The jamvee™ Rooms created under this model will be limited in the number of participants that can join a jamvee™ conference hosted on the jamvee™ Room. There will be different MRCs based on the specific maximum number of allowed participants.

iv. This model include the following Service Offers or SO (i.e. maximum participant options):

1. Bronze Service Offer: Up to maximum of 6 simultaneous participants 2. Silver Service Offer: Up to maximum of 12 simultaneous participants 3. Gold Service Offer: Up to maximum of 48 simultaneous participants 4. Premium Service Offer: Up to maximum of 100 simultaneous participants

v. A participant can be an audio-only call leg, or an audio plus content call leg or a video call leg. A jamvee™ conference can have any combination thereof.

5. Jamvee™ Unified Communications Audio/Web Conferencing (AC/WC) Pricing Models – this pricing

model includes audio-only or audio plus content sharing, IM, and Presence or any combination thereof on any jamvee™ conference call leg

a. There is no video allowed with this pricing model and all video capability will be disabled on all jamvee™ Rooms that are provisioned with this pricing model.




b. This model supports both metered usage and per seat/named user models.

c. Metered Usage Models – charges based on usage metering of audio-only at the Audio Metered Rate or audio plus content sharing (no video) at the Web Metered Rate.

i. “Pay-as-you-Go” PAYG Model – no upfront commitment and metered rate based on Audio Metered Rate or Web Metered Rate for each call leg (participant) in the jamvee™ conference.

ii. Minimum Commitment Bundles (MRCs) with Overages – minimum up front MRC commitment with metered usage discount levels based on up-front, monthly commitments. Overages beyond minimum commitment is charges at the discounted Audio Metered Rate or Web Metered Rate for the commitment bundle.

d. “Per Seat/Named User” with Unlimited Usage Models – charges are based on a fixed MRC for unlimited conference usage up to the maximum number of simultaneous participants per conference.

i. In this model a specific named user (an individual within an enterprise/legal entity) is provided with one jamvee™ Room that can be used to host a single jamvee™ conference at any one time (no simultaneous conferences) using audio plus content sharing. Note: currently a jamvee™ user account that has Per Seat/Named User model can only have a single jamvee™ Rooms configured for each user. It is expected that this limitation will be removed in a future release.

ii. Jamvee™ Rooms cannot be shared with multiple host users in anything the results simultaneous conferences. The MRC covers only a single conference at any one time.

iii. The jamvee™ Rooms created under this model will be limited in the number of

participants that can join a jamvee™ conference hosted on the jamvee™ Room as well as video being disabled on these Rooms. There will be different MRCs based on the specific maximum number of allowed participants.

iv. This model include the following Service Offers or SO (i.e. maximum participant

options):

1. WC Silver Service Offer: Up to maximum of 25 simultaneous participants 2. WC Premium Service Offer: Up to maximum of 300 simultaneous participants

v. A participant can be an audio-only call leg or an audio + content call leg.




9.2 Commercial Offer Summary

Transport/access to the jamvee™ service is charged at different rates and Terms and Conditions, based on

the type of transport access being purchased/used. These charges are independent of the conference

charges outlined above.

The following table provides a summary of the supported jamvee™ access that apply:

Access Type Suitable for: NRC MRC Metered

Usage Note

Local Loop Dedicated access to the jamvee™ UC Service

Yes

Yes (depend on

required bandwidth)

Not Applicable Comes with SLA, as per normal TC local loop access service pricing

Dedicated Transport

Dedicated access to the jamvee™ UC Service (GMX) over MPLS GVPN and DGE

Yes

Yes (depend on

required bandwidth)

May apply in some cases.

Comes with SLA, as per normal TC service pricing for MPLS GVPN and DGE.

PSTN ITFS (Inbound)

Customer Toll-Free in country PSTN access for audio only endpoints

No (for jamvee™ numbers only)


PSTN/ITFS metered access charges @ fixed individual country and access type rate

Rates vary based on Country and Call Type (i.e. fixed wire, wireless, public phone origination)

PSTN LNS/ACS (Inbound)

Customer Toll in country access for audio only endpoints



Depends on country and local provider

End user pays local SP for PSTN toll access to the jamvee™ service + jamvee™ customer pays any additional metered usage for LNS that may apply

Public Internet (Inbound)

Anywhere access from a IP-based endpoints that can dial via a URI/URL

No No No End Customer pays local ISP for standard Internet access

Note: the jamvee™ UC service does not support ISDN access so no ISDN charges apply.




10 Appendix A – jamvee™ Unified Communications services supported endpoints list

This appendix defines the endpoint (EP) compatibility list for jamvee™ Unified Communications Services R410.

The following table of reference is that on the jamvee™ enterprise website – in the documentation section:

https://enterprise.jamvee.com/partners/enterprise.jamvee.com/resources/jamveeUC_Compatibility_List.pdf

10 For other Tata Communications Services eg. Managed Services or jamvee™ on-demand video conferencing services please refer to

the product related service description for the list of supported endpoints

https://enterprise.jamvee.com/partners/enterprise.jamvee.com/resources/jamveeUC_Compatibility_List.pdf




11 Appendix B – audio-only PSTN access numbers

Both jamvee™ Services (both the jamvee™ on-demand video conferencing service and the jamvee™ Unified

Communications service) also supports world-wide access from standard wired/wireless telephones that are

connected to the global PSTN network. In most major countries, toll-free access is provided via in-country ITFS

numbers. For the rest of the world, direct-dial toll numbers are available to access the service (see table below).

This table will be enhanced with additional access numbers over time based on customer demand/needs.

End-Users using the in-country, toll-free numbers will not incur any local telephone usage charges by their local

telecom (other fees may apply, e.g. wireless access charges). Any Toll-Free transport charges will be always

be charged to the customer of the jamvee™ Room which is hosting the leg of the call used by the audio-only

endpoint. Calls to any of the toll-access numbers will be charge directly to the end-user by the local telecom or

wireless provider based on their standards toll rates (toll usage fees can vary depending on region and service

provider). In all cases, jamvee™ Unified Communications service bridging usage charges will apply to all audio-

only endpoints on a call using the Audio-only conference rates. Bridging usage charges will be the responsibility

of the user/enterprise owner of the jamvee™ Unified Communications service account (i.e. jamvee™ Room

owner).

The most current audio access numbers can always be found at:

https://enterprise.jamvee.com/partners/enterprise.jamvee.com/resources/JamveeUC_audio_dialling_guide.pdf

https://enterprise.jamvee.com/partners/enterprise.jamvee.com/resources/JamveeUC_audio_dialling_guide.pdf




12 Appendix C – Enterprise firewall/proxy server guidelines

Please consult the separate document, jamveeUC_Proxy_and_Firewall_Settings, that covers configuring

firewalls and proxy servers to access the jamvee™ Unified Communications service.

https://enterprise.jamvee.com/partners/enterprise.jamvee.com/resources/jamveeUC_proxy_and_firewall_settings.pdf

jamvee unified communications administrator guide...and presence communications capabilities in...

Documents