Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Cisco Exam 350-801 Topic 6 Question 79 Discussion

Actual exam question for Cisco's 350-801 exam
Question #: 79
Topic #: 6
[All 350-801 Questions]

Which behavior occurs when Cisco UCM has a Call Manager group that consists of two subscribers?

Show Suggested Answer Hide Answer
Suggested Answer: D

When building a variable-length route pattern, you need to create a second route pattern followed by the # wildcard. This will allow the user to indicate the end of the number by dialing #. For example, if you want to create a route pattern for international calls, you would create a route pattern like this:

9.011!#

This route pattern will match any number that starts with 9.011, followed by any number of digits, and then ends with #.

The other options are incorrect because:

Configuring a single route pattern for international calls will not allow the user to indicate the end of the number.

Setting up all international route patterns to 0.! will not allow the user to indicate the end of the number.

Reducing the T302 timer to less than 4 seconds will not allow the user to indicate the end of the number.


Contribute your Thoughts:

Wai
1 months ago
If the endpoints had to deregister every time a subscriber was rebooted, the users would probably start launching the phones at the network admins. C is definitely the way to go.
upvoted 0 times
...
Caren
1 months ago
I was totally going to pick B, but now that I think about it, why would the endpoints register with the bottom subscriber? C is clearly the right answer here.
upvoted 0 times
...
Evangelina
2 months ago
D seems plausible, but it would be really inconvenient for the endpoints to have to deregister and re-register every time a subscriber is rebooted. C is the way to go.
upvoted 0 times
Benton
6 days ago
C) Endpoints attempt to register with both subscribers in a load-balanced method.
upvoted 0 times
...
Gearldine
11 days ago
Agreed, it's definitely a more efficient way to handle registration with multiple subscribers.
upvoted 0 times
...
Ahmad
15 days ago
D) If a subscriber is rebooted, endpoints deregister until the rebooted system is back in service.
upvoted 0 times
...
Kenneth
20 days ago
Yeah, that makes sense. It would ensure better redundancy and load balancing.
upvoted 0 times
...
Alyce
26 days ago
A) Endpoints attempt to register with the top subscriber in the list.
upvoted 0 times
...
Lindsey
26 days ago
I think C is the correct answer, endpoints register with both subscribers in a load-balanced method.
upvoted 0 times
...
...
Jess
2 months ago
I thought the endpoints would just register with the top subscriber, but C makes sense. Load balancing is a common strategy for high-availability systems.
upvoted 0 times
...
Rebecka
2 months ago
The correct answer is C. Endpoints attempt to register with both subscribers in a load-balanced method. This ensures redundancy and high availability for the Cisco UCM system.
upvoted 0 times
Dong
2 days ago
Exactly, it helps ensure that the Cisco UCM system stays up and running smoothly.
upvoted 0 times
...
Kimbery
11 days ago
So if one subscriber goes down, the endpoints can still register with the other one.
upvoted 0 times
...
Shelba
17 days ago
That makes sense, it's important to have redundancy and high availability.
upvoted 0 times
...
Bettyann
21 days ago
I think the correct answer is C. Endpoints attempt to register with both subscribers in a load-balanced method.
upvoted 0 times
...
...
Linwood
2 months ago
But what if one subscriber is rebooted? Wouldn't endpoints deregister until it's back?
upvoted 0 times
...
Jimmie
3 months ago
I agree with Paola, endpoints should register with both subscribers for load balancing.
upvoted 0 times
...
Paola
3 months ago
I think the answer is C.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77