Cisco® 400-051 Exam Practice Questions (P. 5)
- Full Access (939 questions)
- Six months of Premium Access
- Access to one million comments
- Seamless ChatGPT Integration
- Ability to download PDF files
- Anki Flashcard files for revision
- No Captcha & No AdSense
- Advanced Exam Configuration
Question #41
Refer to the exhibit.

How many SIP signaling dialog(s) took place in this SIP message exchange between two SIP user agents?

How many SIP signaling dialog(s) took place in this SIP message exchange between two SIP user agents?
- A1
- B2
- C3
- D4
- E5
- F6
Correct Answer:
A
During the establishment, maintenance and termination of a SIP session, signaling messages are exchanged between the two SIP endpoints. There are two different kinds of signaling "conversations" that those messages take part in: transactions and dialogs.
A transaction is a SIP message exchange between two user-agents that starts with a request and ends with its final response (it can also contain zero or more provisional responses in between). For example, during the termination of a SIP session, one user releases the call by sending a BYE request and the other party replies back with a 200 OK response. This message exchange is called a transaction.
But what happens in the case of the INVITE request? The establishment of a SIP session starts basically with an INVITE request and is considered as completed upon the receipt of the ACK. In this case, the transaction starts with the INVITE request and ends with the 200 OK, so the ACK is not part of the transaction. The
ACK can be considered as a transaction on its own. However, when the final response to an INVITE is not a 2xx response, then the ACK is considered as part of the transaction. A dialog is a complete exchange of SIP messages between two user-agents. That means that transactions are actually parts of a dialog. For example, in the case of a SIP session establishment, a dialog starts with the INVITE-200 OK transaction, continues with the ACK and ends with the BYE-200 OK transaction.
The picture below depicts the dialog and transactions that take place during the establishment of a SIP session:

Note: There can also be subsequent requests that belong to the same dialog, such as a BYE or a re-INVITE message. As out-of-dialog requests are considered messages such as an initial INVITE request for a new session or an OPTIONS message for checking capabilities.
There are different SIP headers/parameters that identify the dialogs and transactions, and they will be analyzed in later posts.
References: https://telconotes.wordpress.com/2013/03/13/sip-transactions-vs-dialogs/
A
During the establishment, maintenance and termination of a SIP session, signaling messages are exchanged between the two SIP endpoints. There are two different kinds of signaling "conversations" that those messages take part in: transactions and dialogs.
A transaction is a SIP message exchange between two user-agents that starts with a request and ends with its final response (it can also contain zero or more provisional responses in between). For example, during the termination of a SIP session, one user releases the call by sending a BYE request and the other party replies back with a 200 OK response. This message exchange is called a transaction.
But what happens in the case of the INVITE request? The establishment of a SIP session starts basically with an INVITE request and is considered as completed upon the receipt of the ACK. In this case, the transaction starts with the INVITE request and ends with the 200 OK, so the ACK is not part of the transaction. The
ACK can be considered as a transaction on its own. However, when the final response to an INVITE is not a 2xx response, then the ACK is considered as part of the transaction. A dialog is a complete exchange of SIP messages between two user-agents. That means that transactions are actually parts of a dialog. For example, in the case of a SIP session establishment, a dialog starts with the INVITE-200 OK transaction, continues with the ACK and ends with the BYE-200 OK transaction.
The picture below depicts the dialog and transactions that take place during the establishment of a SIP session:

Note: There can also be subsequent requests that belong to the same dialog, such as a BYE or a re-INVITE message. As out-of-dialog requests are considered messages such as an initial INVITE request for a new session or an OPTIONS message for checking capabilities.
There are different SIP headers/parameters that identify the dialogs and transactions, and they will be analyzed in later posts.
References: https://telconotes.wordpress.com/2013/03/13/sip-transactions-vs-dialogs/
send
light_mode
delete
Question #42
Which two statements describe characteristics of Binary Floor Control Protocol? (Choose two.)
- AIts binary encoding is designed to work in high-bandwidth environments.
- BIt is designed for audio or video conference sessions of three or more participants.
- CIt enables management of shared content resources independent of video streams.
- DIt supports TLS-based authentication.
- EIt supports SIP as well as H.323.
Correct Answer:
CD
BFCP is a deliverable developed as part of the Internet Engineering Task Force (IETF) XCON Centralized Conferencing working group. The IETF XCON working group was formed to focus on delivering a standards-based approach to managing IP conferencing while promoting broad interoperability between software and equipment vendors.
CD
BFCP is a deliverable developed as part of the Internet Engineering Task Force (IETF) XCON Centralized Conferencing working group. The IETF XCON working group was formed to focus on delivering a standards-based approach to managing IP conferencing while promoting broad interoperability between software and equipment vendors.
send
light_mode
delete
Question #43
What is the minimum number of TCP sessions needed to complete a H.323 call between two H.323 gateways using slow start?
- A0
- B1
- C2
- D3
- E4
Correct Answer:
C
H.323 has two modes of operation: slow start and fast start. The initiation of a call may proceed in a slow start or fast start in H.323. In a slow start, H.323 signaling consists of Setup, Call Proceeding, Alerting, and Connect steps. After these steps, the H.245 media negotiation is performed. When a call is initiated in H.323 fast start, the H.245 media negotiation is performed within the initial Setup message. With slow start, multiple TCP connections are needed for an H.323 call, such as one H.225 signaling channel and one H.245 signaling channel if required (minimum of these two).
C
H.323 has two modes of operation: slow start and fast start. The initiation of a call may proceed in a slow start or fast start in H.323. In a slow start, H.323 signaling consists of Setup, Call Proceeding, Alerting, and Connect steps. After these steps, the H.245 media negotiation is performed. When a call is initiated in H.323 fast start, the H.245 media negotiation is performed within the initial Setup message. With slow start, multiple TCP connections are needed for an H.323 call, such as one H.225 signaling channel and one H.245 signaling channel if required (minimum of these two).
send
light_mode
delete
Question #44
Which element was added to H.225 messages to enable Fast Connect in H.323 version 2?
- AfastStart
- BfastConnect
- CH.245 PDU
- DUser-User Information
- EConnection Information
Correct Answer:
A
Fast start allows for H323 media connections to be started at the beginning of a call. This is helpful for ringback scenarios, and also reduces the amount of time calls take to establish media. H245 is still negotiated later, but the actual media can be done earlier through H225 messages.
A
Fast start allows for H323 media connections to be started at the beginning of a call. This is helpful for ringback scenarios, and also reduces the amount of time calls take to establish media. H245 is still negotiated later, but the actual media can be done earlier through H225 messages.
send
light_mode
delete
Question #45
What is the name of the logical channel proposal that is transmitted from the called entity to the calling entity in H.323 Fast Connect?
- AForward Logical Channel
- BBackward Logical Channel
- CReverse Logical Channel
- DOriginator Logical Channel
- EDestination Logical Channel
Correct Answer:
C
Unlike the OpenLogicalChannel request used by H.323 for video uni-directional logical channels, the request used by H.324 for opening video bi-directional logical channels specifies the temporalSpatialTradeOff Capability in both the forward and reverse directions--in the forwardLogicalChannelParameters.dataTypeandreverseLogicalChannelParameters.dataType components, respectively. The semantics of temporalSpatialTradeOffCapability used in forward LogicalChannelParameters.dataType is described in the previous section. The semantics for its presence in the reverse direction is described in this section.
C
Unlike the OpenLogicalChannel request used by H.323 for video uni-directional logical channels, the request used by H.324 for opening video bi-directional logical channels specifies the temporalSpatialTradeOff Capability in both the forward and reverse directions--in the forwardLogicalChannelParameters.dataTypeandreverseLogicalChannelParameters.dataType components, respectively. The semantics of temporalSpatialTradeOffCapability used in forward LogicalChannelParameters.dataType is described in the previous section. The semantics for its presence in the reverse direction is described in this section.
send
light_mode
delete
Question #46
Which procedure uses H.225 messages to exchange H.245 Master-Salve Determination information?
- AH.323 Fast Connect
- BH.245 tunneling
- CH.225 tunneling
- DH.323 early media
- EH.245 terminal capability set
Correct Answer:
B
The H.245 protocol is a media control protocol that is a part of H.323 protocol suite. The H.245 protocol is used primarily to negotiate master-slave relationship between communicating endpoints. These endpoints exchange terminal capabilities and logical channel manipulations (open, close, modify).The H.245 messages can be encapsulated and carried between H.225 controlled endpoints within H.225 messages. This way of "piggy-backing" an H.245 message to H.225 message is referred to as H245 Tunneling. The H.245 Tunneling method is optional and negotiable between communicating H.323 endpoints. If both endpoints support this option, usually the H.245 Media Controlled messages are exchanged via the Tunneling method.
B
The H.245 protocol is a media control protocol that is a part of H.323 protocol suite. The H.245 protocol is used primarily to negotiate master-slave relationship between communicating endpoints. These endpoints exchange terminal capabilities and logical channel manipulations (open, close, modify).The H.245 messages can be encapsulated and carried between H.225 controlled endpoints within H.225 messages. This way of "piggy-backing" an H.245 message to H.225 message is referred to as H245 Tunneling. The H.245 Tunneling method is optional and negotiable between communicating H.323 endpoints. If both endpoints support this option, usually the H.245 Media Controlled messages are exchanged via the Tunneling method.
send
light_mode
delete
Question #47
Which two VoIP protocols use SDP to describe streaming media sessions? (Choose two.)
- ASCCP
- BH.323
- CSIP
- DMGCP
- ERAS
- FcRTP
Correct Answer:
CD
The Session Description Protocol (SDP), defined in RFC 2327, describes the content of sessions, including telephony, Internet radio, and multimedia applications.
SDP includes information about [8]:
Media streams: A session can include multiple streams of differing content. SDP currently defines audio, video, data, control, and application as stream types, similar to the MIME types used for Internet mail.
Addresses: SDP indicates the destination addresses, which may be a multicast address, for a media stream.
Ports: For each stream, the UDP port numbers for sending and receiving are specified.
Payload types: For each media stream type in use (for example, telephony), the payload type indicates the media formats that can be used during the session.
Start and stop times: These apply to broadcast sessions, for example, a television or radio program. The start, stop, and repeat times of the session are indicated.
Originator: For broadcast sessions, the originator is specified, with contact information. This may be useful if a receiver encounters technical difficulties.
CD
The Session Description Protocol (SDP), defined in RFC 2327, describes the content of sessions, including telephony, Internet radio, and multimedia applications.
SDP includes information about [8]:
Media streams: A session can include multiple streams of differing content. SDP currently defines audio, video, data, control, and application as stream types, similar to the MIME types used for Internet mail.
Addresses: SDP indicates the destination addresses, which may be a multicast address, for a media stream.
Ports: For each stream, the UDP port numbers for sending and receiving are specified.
Payload types: For each media stream type in use (for example, telephony), the payload type indicates the media formats that can be used during the session.
Start and stop times: These apply to broadcast sessions, for example, a television or radio program. The start, stop, and repeat times of the session are indicated.
Originator: For broadcast sessions, the originator is specified, with contact information. This may be useful if a receiver encounters technical difficulties.
send
light_mode
delete
Question #48
Which RAS message is used between two gatekeepers to resolve an alias address?
- AGRQ
- BARQ
- CIRQ
- DLRQ
- ERRQ
Correct Answer:
D
LRQ These messages are exchanged between gatekeepers and are used for inter-zone (remote zone) calls. For example, gatekeeper A receives an ARQ from a local zone gateway requesting call admission for a remote zone device. Gatekeeper A then sends an LRQ message to gatekeeper B. Gatekeeper B replies to the LRQ message with either a Location Confirm (LCF) or Location Reject (LRJ) message, which depends on whether it is configured to admit or reject the inter- zone call request and whether the requested resource is registered.
D
LRQ These messages are exchanged between gatekeepers and are used for inter-zone (remote zone) calls. For example, gatekeeper A receives an ARQ from a local zone gateway requesting call admission for a remote zone device. Gatekeeper A then sends an LRQ message to gatekeeper B. Gatekeeper B replies to the LRQ message with either a Location Confirm (LCF) or Location Reject (LRJ) message, which depends on whether it is configured to admit or reject the inter- zone call request and whether the requested resource is registered.
send
light_mode
delete
Question #49
When a Cisco IOS gatekeeper receives an ARQ from a registered endpoint, what is the first step it will take in an attempt to resolve the destination address?
- ACheck to see if the destination address is locally registered.
- BCheck to see if the destination address matches the technology prefix.
- CCheck to see if the destination address matches the local zone prefix.
- DCheck to see if the destination address matches the remote zone prefix.
- ECheck to see if the destination address matches the default technology prefix.
Correct Answer:
B
Admission Request (ARQ) and Location Request (LRQ) are the two H.225 Registration, Admission, Status (RAS) messages that trigger a gatekeeper to initiate the call routing decision process.
✑ ARQLocal zone messages that are sent by H.323 endpoints (usually gateways) to the Cisco gatekeeper. Gatekeepers receive ARQs from an endpoint if.
- A local zone endpoint initiates a call. OR
- A local zone endpoint request permission to admit an incoming call.
B
Admission Request (ARQ) and Location Request (LRQ) are the two H.225 Registration, Admission, Status (RAS) messages that trigger a gatekeeper to initiate the call routing decision process.
✑ ARQLocal zone messages that are sent by H.323 endpoints (usually gateways) to the Cisco gatekeeper. Gatekeepers receive ARQs from an endpoint if.
- A local zone endpoint initiates a call. OR
- A local zone endpoint request permission to admit an incoming call.
send
light_mode
delete
Question #50
When a Cisco IOS gatekeeper receives an LRQ, what is the first step it will take in an attempt to resolve the destination address?
- ACheck to see if the LRQ reject-unknown-prefix flag is set.
- BCheck to see if the destination address matches the technology prefix.
- CCheck to see if the destination address matches the hop-off technology prefix.
- DCheck to see if the destination address matches the remote zone prefix.
- ECheck to see if the LRQ forward-queries flag is set.
Correct Answer:
B
LRQ These messages are exchanged between gatekeepers and are used for inter-zone (remote zone) calls. For example, gatekeeper A receives an ARQ from a local zone gateway requesting call admission for a remote zone device. Gatekeeper A then sends an LRQ message to gatekeeper B. Gatekeeper B replies to the LRQ message with either a Location Confirm (LCF) or Location Reject (LRJ) message, which depends on whether it is configured to admit or reject the inter- zone call request and whether the requested resource is registered.
B
LRQ These messages are exchanged between gatekeepers and are used for inter-zone (remote zone) calls. For example, gatekeeper A receives an ARQ from a local zone gateway requesting call admission for a remote zone device. Gatekeeper A then sends an LRQ message to gatekeeper B. Gatekeeper B replies to the LRQ message with either a Location Confirm (LCF) or Location Reject (LRJ) message, which depends on whether it is configured to admit or reject the inter- zone call request and whether the requested resource is registered.
send
light_mode
delete
All Pages