Pass the Cisco Field Engineer 500-710 Questions and answers with CertsForce

= When adding a Cisco Meeting Server to TMS, you need to configure the following items before the server can be used in scheduled conferences12:

domain: This is the domain name of the Cisco Meeting Server, which is used to generate the conference aliases and URIs. For example, if the domain is cisco.com, the conference alias will be something like 123456@cisco.com. The domain name must match the domain name configured on the Cisco Meeting Server and the certificates used for secure communication.

numeric ID base: This is the starting number for the numeric conference IDs that TMS assigns to the conferences scheduled on the Cisco Meeting Server. For example, if the numeric ID base is 1000, the first conference will have the numeric ID 1000, the second conference will have the numeric ID 1001, and so on. The numeric ID base must be unique for each Cisco Meeting Server in TMS and must not overlap with any existing conference IDs in TMS.

numeric ID quantity: This is the number of numeric conference IDs that TMS can assign to the conferences scheduled on the Cisco Meeting Server. For example, if the numeric ID quantity is 100, TMS can assign numeric IDs from 1000 to 1099 to the conferences on the Cisco Meeting Server. The numeric ID quantity must be sufficient to accommodate the expected number of conferences on the Cisco Meeting Server.

The other options are not required or relevant for adding a Cisco Meeting Server to TMS. The DNS address and MAC address are not used by TMS to identify or communicate with the Cisco Meeting Server. The conference ID range is not a valid parameter for TMS.

References := Connect to TMS, Cisco Meeting Server - Configuration Guides

 A SIP alias is an alternative address for a SIP URI, which is the standard format for identifying a user or a service in a SIP network. A SIP URI consists of a user part, an at sign (@), and a host part, such as user@host. The user part can be a username, a phone number, or any other identifier. The host part can be a domain name, an IP address, or any other network address. For example, alice@example.com, +1234567890@voip.com, and bob@192.168.1.1 are valid SIP URIs1.

A SIP alias is a way of creating multiple SIP URIs for the same user or service, using different user parts or host parts. For example, if a user has a SIP URI of john.doe@cisco.com, he can also have a SIP alias of jdoe@cisco.com, or john.doe@voip.cisco.com, or any other combination of user and host parts. A SIP alias can be useful for providing different contact options, simplifying dialing, or hiding the real SIP URI for privacy or security reasons2.

To configure a SIP alias, you need to have a SIP account with a SIP service provider that supports SIP alias, such as iptel.org. You also need to have a SIP device or application that can register and use the SIP alias, such as a VoIP phone, a softphone, or a router. You can create and manage your SIP alias using the web interface of your SIP service provider, or using the configuration settings of your SIP device or application2.

The correct format for a SIP alias is the same as the format for a SIP URI, which is user@host. Therefore, the option C. John.doe@cisco.com is the correct format for a SIPalias, as it has a user part (John.doe) and a host part (cisco.com) separated by an at sign (@). The other options are not correct formats for a SIP alias, because:

A. 212-555-1212 : This is a phone number, not a SIP URI. It does not have a user part or a host part, and it does not have an at sign (@).

B. +12125551212 : This is also a phone number, not a SIP URI. It does not have a user part or a host part, and it does not have an at sign (@).

D. John.doe : This is only a user part, not a SIP URI. It does not have a host part, and it does not have an at sign (@).

References := Session Initiation Protocol (SIP) Parameters, How to configure SIP Alias | DrayTek

= OAuth is an open standard for authorization that allows applications and services to access resources on behalf of a user, without sharing the user’s credentials. OAuth uses access tokens to grant permissions to applications and services to access the user’s resources1. Cisco Spark supports OAuth 2.0, which is the latest version of OAuth2.

To use OAuth access tokens with Cisco Spark, you need to follow these steps2:

Register your application or service to Cisco Spark as an integration. You will receive a client ID and a client secret, which are used to identify your application or service to Cisco Spark.

Redirect the user to the Cisco Spark authorization URL, where the user can login with their Cisco Spark credentials and grant permissions to your application or service. The permissions are defined by the scopes that you specify in the authorization URL. For example, if you want to access the user’s messages and rooms, you need to request the spark:messages_read and spark:rooms_read scopes.

Receive an authorization code from Cisco Spark, which is sent to the redirect URI that you specify in the authorization URL. The redirect URI must match the one that you registered with Cisco Spark.

Exchange the authorization code for an access token and a refresh token from Cisco Spark, using your client ID and client secret. The access token is used to access the user’s resources on Cisco Spark, such as messages, rooms, people, etc. The refresh token is used to obtain a new access token when the current one expires.

Use the access token to make API requests to Cisco Spark on behalf of the user. You need to include the access token in the Authorization header of your HTTP requests, such as Authorization: Bearer <access_token>.

Therefore, the two options that are requirements to use OAuth access tokens with Cisco Spark are:

C. Applications can only request the access token when the authenticated user grants permissions to this service. This is true because the user needs to authorize the application or service to access their resources on Cisco Spark, by logging in and consenting to the scopes that the application or service requests.

E. Services can request the access token only when the authenticated user grants permissions to this service. This is also true because the service needs to obtain the user’s consent to access their resources on Cisco Spark, by redirecting the user to the Cisco Spark authorization URL and receiving an authorization code.

The other options are not requirements to use OAuth access tokens with Cisco Spark, because:

A. Tokens must request access to servers before applications register to Cisco Spark. This is false because tokens are not entities that can request access to servers. Tokens are strings that represent the permissions that the user grants to the applications or services. Applications or services need to register to Cisco Spark before they can request tokens, not the other way around.

B. Servers must register to Cisco Spark as an application to request access tokens. This is false because servers are not the same as applications. Servers are physical or virtual machines that host applications or services. Applications or services are software programs that interact with Cisco Spark. Servers do not need to register to Cisco Spark, but applications or services do.

D. Applications must register to Cisco Spark as a server to request access tokens. This is also false because applications are not the same as servers. Applications are software programs that interact with Cisco Spark. Servers are physical or virtual machines that host applications or services. Applications do not need to register to Cisco Spark as servers, but as integrations.

References := OAuth 2.0, Cisco Spark for Developers - Authentication

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

Cisco Meeting Server allows you to customize the appearance and behavior of the spaces that host the meetings. You can add a logo to the standard layout, change the background color, adjust the video quality and bandwidth, enable or disable file sharing, and more. You can also create customized layouts for specific spaces or participants, using the API or the ActiveControl app. These customization options can enhance the user experience and the branding of your organization. References: Cisco Meeting Server 3.8 Customization Guidelines, Cisco Meeting Server 3.7 and later, Administrator Guide to Screen Layouts and Pane Placement, and Customized Layouts, Cisco Meeting Server 3.6 Demo v1

= The Calendar Connector for Cisco Spark Hybrid is a feature that allows users to schedule and join Webex meetings from their Microsoft Exchange calendars. To integrate the Calendar Connector with Microsoft Exchange, an impersonation account is needed on the Exchange server. An impersonation account is a service account that has the permission to access other users’ calendars and send meeting invitations on their behalf. The Calendar Connector uses the impersonation account to monitor and update the users’ calendars, and to add Webex meeting details to the invitations. To create and configure an impersonation account on Microsoft Exchange, follow the steps in the deployment guide1. References := Deployment guide for Hybrid Calendar - Deploy Expressway-based Hybrid Calendar for Microsoft Exchange

To schedule endpoints that are registered to the Cisco UCM to conferences using TMS, the Cisco UCM must first be added to a folder in TMS Systems > Navigator12.

This is because TMS needs to discover the endpoints that are registered to the Cisco UCM and import them into its database12.

To add the Cisco UCM to a folder in TMS Systems > Navigator, the following steps are required12:

Navigate to Systems > Navigator in TMS and select a folder where you want to add the Cisco UCM.

Click Add Systems and select Unified CM from the drop-down menu.

Enter the IP address or hostname of the Cisco UCM publisher server, the username and password of the application user, and the SIP domain of the Cisco UCM.

Click Save.

TMS will then connect to the Cisco UCM and discover the endpoints that are registered to it. The endpoints will appear under the Unified CM node in the folder.

The endpoints can then be scheduled to conferences using TMS.

References := 1: Cisco TelePresence Management Suite Provisioning Extension Deployment Guide (14.6) - Adding Unified CM to Cisco TMSPE 2: Cisco TelePresence Management Suite Administrator Guide (15.13) - Adding Unified CM to Cisco TMS

 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]