Free Practice Questions for Cisco 500-710 Exam

 In an H.323 call that is not interworked, meaning that both the caller and the callee are using the H.323 protocol, the Expressway acts as an H.323 gatekeeper and routes the following signaling protocols through itself:

Q.931: This is the call signaling protocol that is used to establish, maintain, and terminate calls between any two H.323 entities. Q.931 messages are exchanged over a TCP connection between the endpoints and the Expressway. The Expressway can perform address translation, admission control, and call routing based on the Q.931 messages.

RAS: This is the registration, admission, and status protocol that is used between an H.323 endpoint and the Expressway to provide services such as endpoint registration, address resolution, bandwidth management, and zone management. RAS messages are exchanged over a UDP connection between the endpoints and the Expressway. The Expressway can accept or reject registration requests, allocate bandwidth, and monitor the status of the endpoints based on the RAS messages.

H.245: This is the control protocol for multimedia communication that is used to negotiate the capabilities, open and close logical channels, and exchange control and indication signals for audio, video, and data streams. H.245 messages are exchanged over a TCP connection between the endpoints and the Expressway. The Expressway can modify or enforce the capabilities, allocate ports, and relay the media control signals based on the H.245 messages.

The other protocols, such as RTP, RTCP, and H.254, are not routed through the Expressway in an H.323 call that is not interworked. RTP and RTCP are the protocols for sending or receiving multimedia information (voice, video, or text) between the endpoints. H.254 is not a valid protocol name, but it might be a typo for H.264, which is a video coding standard that defines how video streams are compressed and decompressed. These protocols are exchanged directly between the endpoints over UDP connections, without involving the Expressway. References := Cisco Expressway Administrator Guide (X14.0) - About H.323Cisco Expressway Basic Configuration Deployment Guide (X14.0) - H.323 Call Flow [Cisco Expressway Administrator Guide (X14.0) - Configuring H.323]

 TURN servers must be configured in a resilient and scalable Cisco Meeting Servers solution on the CMS edge only. The CMS edge is the component that provides firewall traversal and NAT traversal for external participants using WebRTC or SIP. The CMS edge acts as a TURN server that relays the media traffic between the external participants and the CMS core, which hosts the conferences. The CMS edge also performs media demultiplexing and encryption/decryption for the media streams. The CMS core does not need to have TURN servers configured, as it communicates directly with the internal endpoints and the CMS edge. The Cisco Unified Communications Manager does not need to have TURN servers configured either, as it is not involved in the media path for the CMS conferences123 References := 1Cisco Meeting Server - Configuration Guides 2Cisco Meeting Server 3.8, Scaled and Resilient Server Deployment Guide 3TURN Server and WebRTC

= To match any incoming call to the Expressway that is searching for an E.164 address of only 6 digits and append the domain cisco.com to the end, you need to use a pattern match and a replace string using regular expressions. Regular expressions are a way of describing patterns of text using special characters and symbols1. The Expressway supports the use of regular expressions in several features, such as search rules, transforms, and dial plan2.

A pattern match is a regular expression that defines the criteria for matching the incoming call. A replace string is a regular expression that defines how to modify the matched call and add the desired domain. The Expressway uses the following syntax for pattern match and replace string2:

The pattern match is enclosed in parentheses, such as (pattern).

The replace string is preceded by a colon, such as :replace.

The replace string can use backreferences to refer to the matched groups in the pattern match, such as \1, \2, etc.

For example, the pattern match and replace string (pattern):replace means that the Expressway will match the incoming call with the pattern and replace it with the replace string.

In this question, the pattern match should match an E.164 address of only 6 digits. An E.164 address is a global phone number that can have up to 15 digits, starting with a plus sign (+)3. To match only 6 digits, we can use the following regular expression:

({6}\d) : This means that the Expressway will match any 6 consecutive digits (\d) and capture them as a group ({6}). The curly braces indicate the number of repetitions of the preceding character. The parentheses indicate the grouping of the characters.

The replace string should append the domain cisco.com to the end of the matched E.164 address. To do this, we can use the following regular expression:

:\1@cisco.com : This means that the Expressway will replace the matched E.164 address with the first captured group (\1) followed by an at sign (@) and the domain cisco.com.

Therefore, the correct pattern match and replace string using regular expressions are:

pattern match: ({6}\d)

replace string: \1@cisco.com

The other options are incorrect because:

A. pattern match: ({6}) : This means that the Expressway will match any 6 consecutive characters () and capture them as a group. The asterisk means that the preceding character can be repeated zero or more times. This is too broad and can match non-digit characters as well.

C. pattern match: ({5}\d) : This means that the Expressway will match any 5 consecutive digits (\d) and capture them as a group. This is too short and will not match an E.164 address of 6 digits.

D. replace string: \6@cisco.com : This means that the Expressway will replace the matched E.164 address with the sixth captured group (\6) followed by an at sign (@) and the domain cisco.com. This is incorrect because there is only one captured group in the pattern match, so \6 will not refer to anything.

F. replace string: $@cisco.com : This means that the Expressway will replace the matched E.164 address with a dollar sign ($) followed by an at sign (@) and the domain cisco.com. This is incorrect because the dollar sign is a special character in regular expressions that means the end of the string. To use it literally, it needs to be escaped with a backslash ().

References := Regular Expressions, Cisco Expressway Basic Configuration Deployment Guide, E.164 : The international public telecommunication numbering plan

The Expressway supports two protocols for traversing media across a firewall: H.460.18/19 and Assent. Both protocols use a TCP/TLS connection established from the client to the server for signaling, and UDP ports for media. The difference is that H.460.18/19 is a standard protocol for H.323 firewall traversal, while Assent is a Cisco proprietary protocol for SIP firewall traversal123

H.460.18/19 is an extension of the H.323 protocol that allows endpoints to communicate with each other through a firewall or a NAT device. H.460.18 defines the signaling procedures for establishing a TCP/TLS connection between the endpoint and the Expressway-E, which acts as the traversal server. H.460.19 defines the media procedures for sending and receiving RTP/RTCP packets through the same TCP/TLS connection orthrough UDP ports. The Expressway-E uses media demultiplexing to route the media packets to the correct destination124

Assent is a protocol that is similar to H.460.18/19, but it is used for SIP firewall traversal of media. The signaling is traversed through a TCP/TLS connection established from the client to the server. The media is traversed through UDP ports that are negotiated using the SDP offer/answer exchange. The Expressway-E uses media demultiplexing to route the media packets to the correct destination123

References := 1Cisco Expressway Administrator Guide (X14.0) - Firewall Traversal 2Cisco Expressway IP Port Usage for Firewall Traversal 3Firewall Traversal and NAT Traversal On Cisco Expressway Explained With Wireshark 4Firewall Traversal Mechanisms > CCIE Collaboration Quick Reference

= Call Service Connect is a hybrid service that allows integration between Cisco Spark and Cisco Unified Communications Manager (CUCM). Call Service Connect enables the Cisco Spark app to be used as a softphone for voice and video calling, and to share an extension with the CUCM desk phone. Call Service Connect also provides a unified call history and caller ID across Cisco Spark and CUCM devices123

Call Service Connect requires media traversal capabilities and licenses to be installed on the Expressway-C and Expressway-E pair that connects the CUCM and the Cisco Collaboration Cloud. Call Service Connect also requires mutual TLS (mTLS) authentication between the Expressway-E and the cloud, and between the Expressway-C and the CUCM. Call Service Connect depends on Call Service Aware, which is another hybrid service that synchronizes the user and device information from the CUCM to the cloud. Call Service Aware must be deployed before Call Service Connect124

References := 1Cisco Spark Hybrid Services Data Sheet 2Cisco Spark Hybrid Services Deployment Guide 3Cisco Spark Hybrid Services At-a-Glance 4Deployment guide for Hybrid Calling for Webex Devices (Device Connector)

 Microsoft Skype for Business (S4B) interoperability with Cisco Meeting Server (CMS) allows S4B users to join CMS meetings and vice versa. Chat can be used between S4B and Cisco Meeting App (CMA) users, as both support the SIP SIMPLE protocol for instant messaging. However, chat cannot be used between S4B and Cisco Meeting Server Spaces, as Spaces do not support chat functionality. Calls can be placed between S4B and CMA users, as both support the H.264 video codec and the Opus audio codec. Local directories can be used between S4B users and CMA, but only if the CMA is configured to use the same domain as the S4B server. References: Configure Cisco Meeting Server and Skype for Business, Plan for Video Interop Server in Skype for Business Server, Deploy Video Interop Server in Skype for Business Server

Cisco Spark hybrid call service integrates Cisco Spark with an existing Cisco call-control platform, such as Cisco Unified Communications Manager, Cisco Business Edition 6000/7000, or Cisco Hosted Collaboration Solution. This integration enables users to make and receive calls on their Cisco device or Spark application using the same dialing procedure as with on-premises registered endpoints. For example, users can dial extension numbers, PSTN numbers, or URIs from their Cisco device or Spark application and reach any destination that is reachable from their on-premises call-control platform.

Cisco Spark hybrid call service has two service components, called Call Service Aware and Call Service Connect1. Call Service Aware makes Cisco Spark aware of calls within your existing Cisco call control. It enables features such as call history, missed call notifications, and one-button-to-push join for meetings on Cisco Spark. Call Service Connect enables calls between Cisco Spark and your existing call control so that, to users they appear as one system. It allows users to make and receive calls on their Cisco device or Spark application using their enterprise directory number, regardless of their location or network. It also enables features such as single number reach, shared line appearance, and call transfer and forwarding.

Therefore, the correct answer is Call Service Connect, as it is the Cisco Spark hybrid call service component that integrates Cisco Spark with an existing Cisco call-control platform and makes it possible for users to make and receive calls on their Cisco device or Spark application using the same dialing procedure as with on-premises registered endpoints.

References := Cisco Spark Hybrid Services Data Sheet, The best of both worlds – Cisco Spark Hybrid Services

The Expressway uses subzones and pipes to control the bandwidth used by endpoints on the network. Subzones are logical groups of endpoints that share the same bandwidth policies and settings. Pipes are logical connections between subzones or zones that limit the total or per-call bandwidth available for calls. The Expressway allows the administrator to configure the bandwidth limits for each subzone and pipe, as well as the behavior when the bandwidth is insufficient or not specified. The other options are not valid methods for bandwidth control on the Expressway. References: Cisco Expressway Administrator Guide (X14.0) - Bandwidth Control, Cisco Expressway Basic Configuration Deployment Guide (X14.0) - Configuring Bandwidth Management