on
02-23-2021
07:09 PM
- edited on
03-25-2021
09:36 PM
by
Hilda Arteaga
This event had place on Tuesday 16th, February at 9:30am PST
The need for virtual collaboration across individuals, teams, organizations, and industries has been significantly changed with the global challenges presented in 2020. The industry now demands rapid adoption of cloud services and more flexible integrations across disparate services and geographies.
In this session, Cisco Press authors and collaboration experts address how border controllers play a key role in enabling the on-premise to cloud migration and consumption of collaboration technologies. They provide a review of new Cisco Unified Border Element (CUBE) features, and some insight into how Session Border Controllers (SBCs) are enabling cloud integrations and improving collaboration security.
Join the solution experts, who have a combined total of over 70 years of experience designing or supporting complex enterprise collaboration deployments. In addition, the authors will revisit a selection of topics that were covered in the book Understanding Session Border Controllers, and review how the concepts remain important and relevant in a changing world.
You can download the slides of the presentation in PDF format here. And the recording of the session here.
A: [Kyzer] Very much so. The topics selected for the book are ones that will keep the book relevant for a long time. Specifically the Security chapter goes over TLS 1.3 for this very reason which was a draft when the book was being written.
A: [Steve] For me, it was 2 years in my job role to learn the core of the technology and pass the written exam, and then a 6 months pursuit of the lab.
[Kyzer] For me, 4 years of core collaboration job experience. 6 months of study for the written exam and a year or more of study for the lab.
A: CUBE Trunk licenses (STD or RED) are included in Webex Calling Flex License at 2:1 ratio (users:trunk) for Webex Calling calls only (1 leg to Webex Calling and the other to either the ITSP or CUCM). Note: CSR 1000v licenses are not included in Webex Calling Flex and need to be purchased separately. Take a look at https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/mcp/DEPLOYMENT_CALLING_Unified_CM_to_Webex_Calling.pdf and https://www.cisco.com/c/en/us/products/collateral/unified-communications/unified-border-element/guide-c07-742037.html (available for partners).
A: SIP and HTTP are two very different protocols that serve different purposes. However, HTTP and HTTPS are used with UC API feature set to integrate CUBE with CUCM and 3rd party applications: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucme/CUCIS_API/CUCIS_API_Guide.html
A: CUBE media proxy platforms can be found in this link however it cannot be collocated with a normal CUBE handling SBC features. https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/configuration/cube-book/voi-cube-media-proxy.html
A: Have you tried implementing via this guide? It should be available on IOS-XE 17.3.2 via this guide: https://www.cisco.com/c/dam/en/us/solutions/collateral/enterprise/interoperability-portal/direct-routing-with-cube.pdf
A: Take a look at the resources here: https://www.cisco.com/c/en/us/solutions/collaboration/unified-communications-manager-cloud/index.html
A: Capacity testing is still ongoing at the moment.
A: SIP doesn't supported e2e encryption. It is on a per hop basis Media, however can be e2e encrypted.
A: Yes, please review: https://cway.cisco.com/csa/
A: That is only supported on Digital/Analog Voice Gateways (FXS/FXO/ISDN etc). Otherwise you can do pass through as per this guide: ml/ios/voice/cube_sip/configuration/15-mt/cube-sip-15-mt-book/voi-cube-v150-mer-sdp-passthru.pdf
A: Please have a look to https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube_sip/configuration/15-mt/cube-sip-15-mt-book/voi-cube-v150-mer-sdp-passthru.pdf That is the only current implementation in CUBE. I know Sectéra VIPer phones are moving towards a new Soft Modem feature to eliminate the reliance on analog v.150 gateways for pure IP networks.
A: CSR1000v is the current vCUBE virtualized software.
A: There are a number of filter options available for "debug ccsip". If there are specific filters you would like to see, please let us know.
A: Cisco IOS XE Bengaluru 17.4.1a, Cisco IOS XE Amsterdam 17.3.2. See https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/configuration/cube-book/voip-trace-for-cube.html
A: Cisco CUBE can leverage installed PVDM4 Digital Signal Processors (DSPs) / Packetized and the existing dspfarm configuration set to register a dspfarm to CUBE (associate application cube). This is known as Local Transcoding Interface (LTI based Transcoding) and allows CUBE to perform codec interworking such as g729 on one call-leg and g711ulaw on another along with some raw in-band to OOB DTMF interworking where required. See: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/configuration/cube-book/cube-book_chapter_0111111.html
A: It captures VoIP Trace captures SIP messages, SIP errors and debugs related to SIP finite state machine (FSM), events and API calls. And it will not capture CCAPI input but will have similar dial-peer matching information.
A: [Kyzer]The passport itself is Jason Web Token (JWT) data encoded as base64 for the SIP Identity header. Work into other data types carried in Passport is currently underway via https://tools.ietf.org/html/draft-ietf-stir-passport-rcd-09
[Kaustubh]Base64 encoding is used regardless of whether or not a Photo/Logo is part of the PASSporT claim set. The data that can be carried in PASSporT is not restricted to image data. There are a whole host of additional claims that may be embedded within PASSporT. For example, the nickname of the caller, the organizational affiliation of the caller, the title of the caller, among many others. The following IETF draft provides the set of claims that may be used in PASSporT as part of Rich Call Data: (https://tools.ietf.org/html/draft-ietf-sipcore-callinfo-rcd-01) Once the complete set of claims corresponding to Rich Call Data is added to the PASSporT (this is largely driven by organizational policy or by caller preference), a serialized string containing JSON name-value pairs is constructed, following which the serialized string is BASE64 coded. As a final step a signature is calculated over the BASE64 encoded string to cryptographically assert the set of claims.
A: Nothing at the moment. Please take a look at UCM Cloud https://www.cisco.com/c/en/us/solutions/collaboration/unified-communications-manager-cloud/index.html
A: It can be done in different ways, nevertheless, in this book Kaustubh Inamdar was placed on the top since he is the one who started this idea and provided more content for this publication. Another interesting thing to mention, is that Arun Arunachalam requested to place his name at the need of the list since he considered his name to be longer than the other ones.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: