Posts Tagged ‘trivia’
UPDATE: We Have a Winner!
Congratulations to Fredy and Antonis for both answering the question correctly.
Because we only had 2 answers to this contest (and it’s the second time we’ve run it), and they were both correct, as well as both having gone above and beyond the requirements to answer the basic question/problem, but adding additional correct and excellent configurations and annotations — we are awarding each of them the same prize!
At a most basic level, the problem with my configuration was that you cannot used an AS Numbered Instance of EIGRP at the top level to configure SAF (Service Advertisement Framework). Yes, EIGRP does have to have an AS#, but that must come within an EIGRP Virtual Instance Named (VIN)!
They both went above and beyond by pointing out many other great points that are well worth reading.
Congratulations to both of you, and look for my email in relation to your prizes!
By the way, since this is such a cool new technology that holds so much potential for real world production environments, I will do a follow-up blog post outlining the basics and some advanced topics surrounding CCD and SAF. Look for that here, soon.
Time for another INE CCNP Voice Trivia Contest. This week we will start early and give you until Monday 28 November to choose a winner, giving you a bit over four days to come up with the correct responses.
This is actually a re-post of an earlier contest –one containing knowledge that every CCNP Voice engineer must know to pass the CIPT2 (642-457) exam– that never met with a correct answer in the previous run. I have recorded around 4.5 hours of material on just this topic beginning here in this video, so take a look at these videos over the next few days, and see if you can sort out the answer.
Time for another INE Voice Trivia Contest. This week we will wait until Friday morning to choose a winner, giving you all a few days to come up with correct responses.
Here is the problem that needs solving for this week’s Voice Trivia Contest:
Integration with an corporate LDAP has been properly setup and many users have been imported into the CUCM server, but now it has been requested that an LDAP Custom Filter be built in order to limit the imported users down to only a few.
The base LDAP schema is that there is an OU called “island natural exports” in the domain of “ine.com”.
The only desired users to remain imported are:
- A user with the last name of “Linus”
- All users who are in the department of “executives” that also have a manager whose canonical name is “Hugo Reyes”
I am running this week’s Voice Trivia Contest a bit early (launching it on Thursday instead of Friday) to try to give more people a chance to win that might not otherwise see this over the weekend, however we will still end the contest on Monday morning, as usual.
Here are the facts for this week’s Voice Trivia Contest:
- Tobias has a phone on which he needs to be able to have two BLF SD buttons that accurately show the presence status of Gob, Buster and Lindsay’s primary DNs. This needs to include status updates for when either Gob or Lindsay’s primary DN is ringing, but not when Buster’s primary DN rings.
- Gob, Buster and Lindsay’s primary DNs are all in the same Partition.
- Tobias has a SUBSCRIBE Calling Search Space that contains that Partition all three phones’ primary DNs are in.
- Tobias also needs to be able to view Call Lists (Missed Calls, Corporate Directory, etc.), but when he views them, he should only see the BLF status change for Lindsay’s DN, and not for Gob or Buster’s DNs.
- To aid in that, two Presence Groups have been setup. One for Tobias and Lindsay which have been assigned to both their Phone devices and their Lines. One for Gob and Buster, which have been assigned to both their Phone devices and their Lines. The Presence Groups both explicitly have Disallow Subscription to each other’s group reciprocally.
- All is good with Tobias’s BLF SDs on his phone display, and he can see all of their status changes appropriately – including seeing when Gob or Lindsay’s DNs ring, but not Buster’s.
- However, there is an issue. When he pulls up the Corporate Directory and searches for everyone, he sees BLF status updates for both Lindsay and Gob, but not for Buster. Remember that he should not see Gob’s BLF status updates either.
Austin has devised a dial plan that meets the needs of his company (Backyard Adventures, Inc), and one of the core components of it meets a requirement set forth by his company’s executive branch – namely, that although people in U.S. offices of his company dial a ’9′ as a PSTN access code prior to dialing any additional digits for outside public calls, the executive branch dictates that they do not want the IP phones that dialed such a number to see that preliminary ’9′ on the phone’s display, once the call has been placed.
(e.g. If Pablo dialed 9-206-501-5111 for a local call in Seattle, then his display should only show 2065015111 once the call has been placed)