Virtual SNR in Cisco Unified Communications Manager Express - Exam 400-051: CCIE Collaboration | Provider: Cisco

Virtual SNR in Cisco Unified Communications Manager Express

Prev Question Next Question

Question

Which two statements about virtual SNR in Cisco Unified Communications Manager Express are true? (Choose two.)

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E.

AB.

To configure a virtual SNR DN on Cisco Unified SCCP IP phones, perform the following steps: Prerequisites - Cisco Unified CME 9.0 or a later version.

Restrictions - -> Virtual SNR DN only supports Cisco Unified SCCP IP phone DNs.

-> Virtual SNR DN provides no mid-call support.

Mid-calls are either of the following: Calls that arrive before the DN is associated with a registered phone and is still present after the DN is associated with the phone.

Calls that arrive for a registered DN that changes state from registered to virtual and back to registered.

-> Mid-calls cannot be pulled back, answered, or terminated from the phone associated with the DN.

-> State of the virtual DN transitions from ringing to hold or remains on hold as a registered DN.

References: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucme/admin/configuration/guide/cmeadm/cmesnr.html#pgfId-1012065

Virtual Single Number Reach (SNR) is a feature in Cisco Unified Communications Manager Express (CUCME) that allows calls to a single phone number to be routed to multiple devices. The devices can include IP phones, mobile phones, and other devices that can receive calls.

The two statements that are true about virtual SNR in CUCME are:

A. The SNR DN must be configured as SCCP. This statement is true because virtual SNR in CUCME requires the SNR DN to be configured as a Skinny Client Control Protocol (SCCP) endpoint. SCCP is a proprietary signaling protocol used by Cisco Unified Communications devices. By configuring the SNR DN as SCCP, CUCME can communicate with the device to control call forwarding and other features.

D. The virtual SNR DN must be assigned to an ephone. This statement is true because the virtual SNR DN must be assigned to an ephone in CUCME. An ephone is a virtual representation of a physical phone device in CUCME. By assigning the virtual SNR DN to an ephone, CUCME can control call routing and other features associated with the DN.

B, C, and E are not true statements about virtual SNR in CUCME:

B. Calls cannot be pulled back from the phone associated with the DN. This statement is not true because calls can be pulled back from the phone associated with the DN in virtual SNR. If a call is answered on a mobile phone, for example, it can be transferred back to the IP phone associated with the DN by pressing a transfer button on the mobile phone.

C. Ephone hunt groups are supported. This statement is not true because ephone hunt groups are not supported in virtual SNR. Ephone hunt groups are used to distribute calls to a group of phones based on a pre-defined hunt order. Virtual SNR, on the other hand, is used to route calls to multiple devices associated with a single phone number.

E. Music on hold is supported for trunk and line side calls. This statement is not true because virtual SNR does not support music on hold for trunk and line side calls. Music on hold is used to provide background music or messages to callers who are on hold. In virtual SNR, calls are routed to multiple devices, so music on hold cannot be used to provide a consistent experience for callers who are placed on hold.