6. Anywhere, Any Device, Any Time
Cisco Webex
Cisco Webex
Room DeviceCisco Webex
Desk Phone
Cisco Video
Endpoints
3rd
Party endpoints
& service
integrations
Webex Teams
Mobile App
Webex Teams
Desktop App
WebEx
App
Cisco Webex – Meetings
BRKCOL-2607 6
7. NEW
Spark Board 70
Room 70D G2Room 70S G2Room 55DRoom 55
NEW NEW NEW
Room Kit PlusRoom KitRoom Kit Mini
NEW NEW
Room Kit Pro
NEW NEW NEW
NEW
Soon
Board 55 Board 70 Board 85
2019
DX80
Share
Soon
9. Creating unique value by
connecting on-premises and
cloud services
Hybrid Calendar Service
Cisco Webex platform
Messaging | Meetings | Calling
Existing Services
Hybrid Call Service
• Call Service Aware
• Call Service Connect
Hybrid Directory Service
Hybrid Media Service
Hybrid Data Security
Cisco Webex Hybrid Services: AND, not OR
9BRKCOL-2607
Hybrid Message Service
10. Expressway
Windows
*Includes Business Edition or HCS
Webex
Messenger
Integrating On-Premises and Cloud
10
Directory Calendar Media KMS
Microsoft AD Exchange Media Node
Data
Security
Call Message
IM&PCisco UCM*
?
Platform
BRKCOL-2607
16. Provisioning via Directory Connector
• Infrastructure for premises directory synchronization to the Identity cloud services
• Directory connector integrates with AD to retrieve user information to sync with the
identity service, and specifies the Active Directory synchronization agreement and
attribute mappings
• Customer installs Directory Connector in its network on a Windows Domain server
(Windows Server 2003, 2008 R2, 2012, 2012 R2, 2016) with administrative user privilege
• Directory Connector supports Single Forest, Multi-Domain and Multi-Forest, Multi-Domain
Directory
Connector
Active
Directory
Cisco Webex Cloud
Identity/SSO
HTTPS
BRKCOL-2607 16
19. Calendaring Scheduling Integration with @webex or @meet
@webex will backfill the users personal room
information into the calendar invite (seen here)
@meet will utilize the Cisco Webex Teams
space information when populating a calendar
invite, or create a new space (next page).
BRKCOL-2607 19
27. Edge
Calendar
WebEx
Messenger
27
Calendar Service Hybrid Exchange Calendaring
BRKCOL-2607
Cloud Calendar Connector uses the same
system architecture; however, the connector
resides in the Cisco Collaboration Cloud (i.e.
requires no premises infrastructure)
29. Webex Hybrid Call Service at a Glance
Call Service Aware
Provides the Webex Teams application an awareness of calls placed between the on
premise devices of two Aware enabled users. This means a one-to-one space will be
created for the users and they will be offered the ability to share their screen with one click.
Call Service Connect
Provides Webex Teams users the ability to make and receive calls on their Webex Room
Devices or Webex Teams application by leveraging the on premise infrastructure’s dialing
capabilities
29
30. Call Connect for Webex Teams
30Presentation ID
Calling my mobile from Teams
Calling my Cisco phone number
from my mobile
36. SIPTrunk
XMPP
Expressway
C
DMZ
Collaboration Cloud Infrastructure
Collaboration Cloud Services
Media/TranscodingNotification/Alerts
Content Sharing
Call Control RoomsIdentity/SSO
File
Storage
Metadata
Storage
Metrics &
Reporting
Billing &
Provisioning
Management Calendar Future
Messaging Interop
Serviceability
Connector
FutureService
Connector
Management
Connector
Common Connector Framework
Message
Connector
Calendar
Connector
Message Service
Directory
Connector
DC
Call
Connector
RESTful https
BRKCOL-2607 36
AXL / XMPP
37. Cisco Webex Teams / Jabber Interoperability - Presence
37
• When user is running Jabber, the user’s Presence on
Jabber shall be based on existing Jabber logic
• Available / Busy / Presenting / In meeting, etc.
• When user is not running Jabber, the user’s Presence
on Jabber shall be based on WebEx Teams activity
• “Available On WebEx Teams” when the user has
been active on WebEx Teams within the last 24
hours
• “Offline” when the user has not been active on
WebEx Teams for over 24 hours
Note: Webex Teams Presence is not impacted due to user’s Jabber activity
BRKCOL-2607
38. Cisco Webex Teams / Jabber Interoperability - Message
38
• Cisco Webex Teams Interop will allow 1:1 message only between
Jabber and Webex Teams users.
• Users must be configured and enabled on both IM&P and Webex
Teams
• Message Connector will map Jabber and the Webex Teams ID using
a common email address
• Notifications include is Typing, Message Read, Deletes, or Missed
• File transfer is not supported.
o When a Webex Teams user posts a file, Cisco Jabber will receive a notification to
get access to the file in the Webex Teams web client
BRKCOL-2607
45. Unified CM support only
• 10.5 or later
Cisco UCM registered IP phones
• Supporting G.711 or G.722
Expressway support only
• X8.10 or later
• Can use existing Expressway C/E deployment
• Audio scale dependent on Expressway deployment
and services enabled.
Webex site
• WBS 33.x or higher
• Included in Flex, A-WBX and A-SPK SKU need the
Webex Edge Audio package
• Not available on CCA-SP, CCA-ENT or TSP sites.
• Requires migration to Webex Audio Site
Requires a signed certification from a Cisco trusted
Certificate Authority (CA)
Cisco Webex Edge Audio
Architecture requirements
IP
Phone
Cisco
Unified
CM
Customer
Premises
Media Path
Z
Expressway C/E
Webex Edge
Audio
Signaling
Meetin
g
Version 1.1
46. Webex Edge Audio Configuration Steps:
1. Obtain dial-in numbers and Lua script
from Site Administration
2. Configure DNS SRV records (5062)
3. Configure Unified CM
4. Set Up Expressway-C
5. Set Up Expressway-E
5. Open Firewall ports
6. Apply Signed Certificate From Trusted
Certificate Authority
7. Apply Edge Audio Callback Settings
Cisco Webex Edge Audio
Architecture configuration
IP
Phone
Cisco
Unified
CM
Customer
Premises
Media Path
Z
Expressway C/E
Webex Edge
Audio
Signaling
Meetin
g
Version 1.1
47. 1. Endpoint dials Webex Audio access number.
2. Cisco UCM matches the number and routes
as +E.164 through SIP trunk to Expressway-
C.
3. LUA script on SIP trunk to Expressway-C
applies transformations required for correct
routing to Webex
4. Expressway-C sends request to
Expressway-E.
5. Expressway-E routes call to the Webex
cloud.
6. Meeting resources are setup.
Cisco Webex Edge Audio
Dial in Signaling Call Flow
IP
Phone
Cisco
Unified
CM
Customer
Premises
Media Path
Z
Expressway C/E
Webex Edge
Audio
Signaling
Meetin
g
Dials Webex Access Number
SIP Trunk
1
2 3 4
5
Version 1.1
48. 1. The IP phone sends media to Expressway-C
2. The Expressway-C sends media to
Expressway-E via the traversal zone
3. The Expressway-E sends media to the
Webex cloud.
4. IP phone’s audio is mixed into the meeting
and it hears the other participants.
Cisco Webex Edge Audio
Dial in Media Call Flow
IP
Phone
Cisco
Unified
CM
Customer
Premises
Media Path
Z
Expressway C/E
Webex Edge
Audio
Signaling
1
2 3
4
Meetin
g
Version 1.1
49. Webex Edge Audio Callback Set Up Steps:
1. Apply Webex Edge Audio Callback Settings
• Define country callback parameters in Site Admin
• Ensure proper SRV record configuration for
Expressway
• Ensure connectivity checks are successful.
• Cisco UCM routes the +E.164 audio call to the IP
phones or local PSTN
Cisco Webex Edge Audio
Architecture configuration
IP
Phone
Cisco
Unified
CM
Customer
Premises
Media Path
Z
Expressway C/E
Webex Edge
Audio
Signaling
Meetin
g
PSTN
Version 1.1
52. • CCA- SP, CCA-ENT, TSP customers can not use their present
configuration with Edge Audio.
• If a call fails, user needs to dial into the call or callback.
• Dial-in through customer owned E.164 or VOIP numbers is not
supported.
• Reroute call back to Webex PSTN resources if rejected by UCM is
not available
• Unable to define Class of Service for call back
• OPUS codec not supported
Webex Audio Caveats
Initial release
Version 1.1
57. • A customer sets up dual connections to
Equinix for redundancy
• Cisco Webex has redundant connection to
Equinix at all colocations across the globe
• BGP routing is used to route traffic across
the peering connection.
• Customers that have a global presence
can choose which regions to peer.
• Customer’s Internet connection is used as
fallback
Architecture
Equinix
PRI SEC
Customer Premises
PRI SEC
ORD10-WXBB-CRT01
Cisco Webex
ORD10-WXBB-CRT02
ORD10-WXBB-PE02ORD10-WXBB-PE01
Intern
et
Version 1.1
58. Z
• Media flows via Equinix peering
connection.
• Webex Meetings app signaling
and media use the peering
connection
• Signaling for cloud registered
devices and Webex Teams uses
the public Internet
• Third party services accessed via
the Internet
Signaling and Media Flow
Customer
Signaling only
Internet
Media Path
Signaling
Webex AS13445
Webex IP blocks:
https://collaborationhel
p.cisco.com/article/en-
us/WBX000028782
Version 1.1
63. Uses the Node
1. Any Webex registered device
Ø SX, MX, RK series, Webex Board
2. Webex Teams app
3. CUCM registered devices
Ø Calling a Webex scheduled, Webex
PMR, or space meeting including the IX.
4. VCS/Exp registered devices
Ø Calling a Webex scheduled Webex
PMR, or space meeting
Ø SIP or H.323 (requires Interworking)
5. Webex dial back to Webex
registered endpoints
Can NOT Use the Node
1. Webex Teams browser client
Ø web.ciscospark.com
2. Webex Call registered phones
Ø 88xx and 78xx (Spark Call) IP
Phones
3. Webex dialing back to SIP registered
endpoints
4. Webex Meetings app
What devices and scenario can the media node
be used?
67. • Video Mesh and Edge Audio work
independently but are part of an overall
solution when connecting to a Webex meeting.
• IP phones dialing in or call back to the Webex
meeting use +E.164 numbers and utilize the
Expressway to connect to the Webex meeting.
(Webex Edge Audio)
• Cisco UCM registered SIP video endpoints,
Webex registered devices and Webex Teams
app dial SIP URIs to the Webex meeting and
use Video Mesh for local media processing.
• Webex Meeting app goes directly to the
Webex Cloud.
Cisco Webex Edge Audio + Video Mesh
Signaling and Media
Version 1.1
SIP
Video
Endpoint
Cisco
Unified
CM
Customer
Premises
Media Path
ZExpressway C/E
Webex Edge
Audio
Signaling
Video
Mesh
Cloud
Registered
Video
Endpoint
IP
Phone
SIP Trunk
Meetin
g
SIP
Trunk
68. • Webex Connect is a peering connection
to Cisco Webex.
• Both Video Mesh and Webex Edge Audio
can use the Webex Edge Connect peering
service to connect media to the Webex
Meeting, but it is not a requirement.
• Webex Teams signaling goes via the
Internet link and all media goes via Webex
Connect.
• Webex Meetings app sends signaling and
media via Webex Connect.
• If the peering connection is not available
all signaling and media traffic will flow via
the Internet.
Cisco Webex Edge Audio + Video Mesh +
Connect
Architecture
SIP Video
Endpoint
IP
Phone
Laptop
Client
Cisco
Unified
CM
Customer
Premises Media Path
ZExpresswa
y
Webex Edge
Video Mesh
Signaling
Connect
InternetLaptop
Client
Meeting
Version 1.1
75. • Hybrid services connect premises resources to cloud
• Each hybrid service can be deployed independently
• Benefits
• Leverage premises investments
• Enhance user experience
• Increase security
• Ease management
• Transition to cloud at desired pace
Key Points