|
0:00:14
|
Let's take a look at our phones. They have registered.
|
|
0:00:20
|
And I should still have control
|
|
0:00:24
|
over Branch 2 Phone 1
|
|
0:00:29
|
and Branch 2 Phone 2
|
|
0:00:31
|
Excellent.
|
|
0:00:32
|
And I also realized that -- let's do sh run | b ephone-dn
|
|
0:00:41
|
I also realized that I accidentally put the core list incoming key ring
|
|
0:00:46
|
international on ephone DN 1 that was proper.
|
|
0:00:48
|
But I put core list incoming key ring internal on ephone DN 2
|
|
0:00:53
|
and that's actually the shared line
|
|
0:00:56
|
so I'm actually going to jump into this ephone DN 2
|
|
0:01:04
|
and remove that core list incoming and put it where it should be
|
|
0:01:11
|
which is on ephone DN 3
|
|
0:01:23
|
So here we've got incoming core list international on 1
|
|
0:01:26
|
nothing on 2 and internal on 3
|
|
0:01:33
|
So now let's go ahead and try to make a call.
|
|
0:01:37
|
We've already tried to call out with 3001 and it's been
|
|
0:01:40
|
successful. With 3002 let's go ahead and make a call
|
|
0:01:45
|
to 112, an emergency services number
|
|
0:01:50
|
and it looks like that call goes out properly
|
|
0:01:52
|
with no issues.
|
|
0:01:56
|
Although we may not want our calling party number to
|
|
0:02:00
|
be four digits.
|
|
0:02:02
|
We may want it to be four digits if it's going to a corporate
|
|
0:02:06
|
headquarter or Branch 1 site, but we may not want it to be four digits if it's
|
|
0:02:09
|
going out to anywhere else on the PSTN.
|
|
0:02:12
|
So let's go ahead and jump back and create a voice
|
|
0:02:16
|
actually let's do sh run | b voice translation rule first
|
|
0:02:21
|
so we don't overwrite anything we already have created.
|
|
0:02:23
|
We rule set 1 and 9, so let's go ahead and create
|
|
0:02:28
|
rule set let's just say 2
|
|
0:02:33
|
and we will say for rule 1 if we match the DN beginning
|
|
0:02:41
|
with 3...$/ we will translate it to
|
|
0:02:50
|
020703& so call everything from the matched number.
|
|
0:02:57
|
And we could be more specific with calling type
|
|
0:03:00
|
if that was needed or required by a lab.
|
|
0:03:04
|
And maybe that's good enough. Maybe some numbers we want
|
|
0:03:07
|
to appear as seven digits, others ten, we could certainly do that
|
|
0:03:10
|
with two rules or actually we would do it with two
|
|
0:03:13
|
rule sets and apply them to different voice translation profiles
|
|
0:03:18
|
apply those to different outbound dial peers depending on
|
|
0:03:23
|
the dialed digits, but for now that'll be good.
|
|
0:03:28
|
Let's actually -- you know what, we are going to
|
|
0:03:33
|
have...
|
|
0:03:40
|
yeah that's fine, so I was trying to think where we should
|
|
0:03:44
|
apply these, so we could
|
|
0:03:50
|
we could apply these to the voice port like we applied the incoming
|
|
0:03:53
|
ten digit to four digit, we could apply -- create another translation profile
|
|
0:03:58
|
four digit up to ten digit, in fact let's just go ahead and do that.
|
|
0:04:02
|
voice translation profile
|
|
0:04:07
|
and we'll call it 4 digit to 10 digit
|
|
0:04:12
|
and we will translate calling rule set 2 and we could apply
|
|
0:04:19
|
that to the voice port in translation profile outgoing.
|
|
0:04:23
|
The only problem is it would translate for all calls including
|
|
0:04:27
|
those in SRST mode up to the four-digit dial over to
|
|
0:04:35
|
corporate headquarter 1000 series numbers and Branch 1
|
|
0:04:38
|
2000 series numbers, so instead do sh dial peer voice sum
|
|
0:04:44
|
we're going to apply them to the individual ports
|
|
0:04:48
|
or sorry, to the individual outbound dial peers.
|
|
0:04:53
|
So 10, we'll do translation profile outgoing and we
|
|
0:05:00
|
called 4 digit to 10 digit
|
|
0:05:06
|
same thing to 11
|
|
0:05:09
|
same thing to 12
|
|
0:05:11
|
and 13 and 14
|
|
0:05:16
|
actually 14 is our international peer.
|
|
0:05:22
|
So truth be told, we may want to create another
|
|
0:05:25
|
voice translation rule
|
|
0:05:38
|
3 and create rule 1
|
|
0:05:42
|
begins with 3...$
|
|
0:05:46
|
and translates to 3120703&
|
|
0:05:56
|
and put that in voice translation profile
|
|
0:06:03
|
4 digit to full E164
|
|
0:06:11
|
translate calling -- what was that? Rule set 3
|
|
0:06:19
|
And then we were on dial peer 14
|
|
0:06:25
|
and we'll do translation profile 4 digit to -- let's just do the whole thing there.
|
|
0:06:31
|
So I make sure I don't mistype it -- to full E164
|
|
0:06:35
|
What we won't do is we won't apply it to our dial peers that go
|
|
0:06:41
|
out for our 4-digit dial.
|
|
0:06:46
|
Ok, so let's try that call again.
|
|
0:06:55
|
So 112
|
|
0:06:57
|
so it not only has class of restriction it can dial out
|
|
0:06:59
|
but it now has the proper calling party.
|
|
0:07:04
|
But let's test to call over to 2001, we tested 1001 with
|
|
0:07:10
|
phone 1, let's test 2001 with phone 2
|
|
0:07:15
|
It dials out, it's only used calling party of four digits
|
|
0:07:19
|
because we didn't apply a voice translation rule
|
|
0:07:21
|
and it is ringing properly, you actually hear a mad
|
|
0:07:26
|
cacophony of ringing because it's also ringing the single number reach
|
|
0:07:30
|
or mobile connect for Branch 1 that's registered to CUCM.
|
|
0:07:33
|
Both of those are internal numbers. I'm sorry the first one was EMS,
|
|
0:07:38
|
the second one was an internal labeled by class of restriction.
|
|
0:07:43
|
The next one we'll dial is let's say an international number.
|
|
0:07:48
|
So we'll dial 00012065011001
|
|
0:07:57
|
Now remember, this is essentially what the router translated or
|
|
0:08:02
|
digit manipulated the number when we just dialed 1001 to.
|
|
0:08:08
|
However, when we dial it specifically, we match a different
|
|
0:08:10
|
dial peer and therefore a different class of restriction.
|
|
0:08:15
|
So if we try to dial this, we are blocked.
|
|
0:08:23
|
And the reason has to do with the class of restriction.
|
|
0:08:26
|
If I took this same number and plugged it in over here,
|
|
0:08:36
|
it's actually going to wait for the interdigit timeout.
|
|
0:08:39
|
I could have put in a hash.
|
|
0:08:43
|
And we can change that interdigit timeout under the
|
|
0:08:47
|
telephony service and timeouts command
|
|
0:08:51
|
but it rings out just fine, so the number I copied
|
|
0:08:56
|
and pasted that from one box to another, the number wasn't the problem
|
|
0:08:59
|
the class of restriction is what prevented the Branch 2 phone 2
|
|
0:09:03
|
from dialing and essentially preserved in SRST fallback
|
|
0:09:11
|
our proper class of restrictions.
|
|
0:09:18
|
Ok, so any questions with anything we've done to this point?
|
|
0:09:31
|
It looks like someone's typing in a question. I'll just go ahead
|
|
0:09:33
|
and give you a moment to do that.
|
|
0:09:38
|
So the question was, "With auto provisioning, if we change
|
|
0:09:42
|
the Mac address of an IP phone while it's registered in CUCM
|
|
0:09:50
|
will the change affect the CME the next time we have a WAN outage?
|
|
0:09:56
|
So what you're asking is
|
|
0:10:03
|
if I understand this correctly, we have auto registration
|
|
0:10:07
|
auto provision all, so it provisioned the -- as we see
|
|
0:10:11
|
the ephone DNs, it also provisioned the ephones and you're saying if
|
|
0:10:19
|
now the WAN has come back up.
|
|
0:10:21
|
Everything is fine, so the first time the WAN had to
|
|
0:10:24
|
go down the first time in order to create these,
|
|
0:10:27
|
otherwise, the only way we could manipulate anything would be
|
|
0:10:29
|
if we did SRST auto provision none.
|
|
0:10:32
|
Ok, if you actually do auto provision all and you go ahead
|
|
0:10:36
|
and create everything manually which is essentially like what you
|
|
0:10:43
|
would do if you told it auto provision none
|
|
0:10:45
|
but if you say auto provision all and it -- and then you go ahead and create
|
|
0:10:48
|
everything manually, you will have some issues.
|
|
0:10:50
|
But we said auto provision all, you're saying we allowed the
|
|
0:10:53
|
phones to fallback maybe the very first time on purpose
|
|
0:10:57
|
we wrote an ACL or took down the serial link just to
|
|
0:11:01
|
get everything to auto provision
|
|
0:11:03
|
then the WAN comes back up or we take the ACL off and
|
|
0:11:10
|
all the phones are registered back to CUCM and now if we
|
|
0:11:14
|
change a Mac address, well then that Mac address wouldn't
|
|
0:11:20
|
match that particular ephone again.
|
|
0:11:24
|
Will the change affect the CME the next time we have WAN outage?
|
|
0:11:28
|
Absolutely it would. Basically, the phone would not see it --
|
|
0:11:33
|
or the -- when the phone contacted CME as SRST
|
|
0:11:38
|
and said, 'Hey I am this Mac address, I am this DN etc.'
|
|
0:11:43
|
CME would look and see it already has an ephone
|
|
0:11:47
|
well actually I should say it doesn't have an ephone with the
|
|
0:11:50
|
proper Mac address because you're stating that we changed
|
|
0:11:53
|
it and so it would then create a new ephone assuming that
|
|
0:12:00
|
we had enough ephones available, so if max ephones equals 10
|
|
0:12:05
|
and currently we're at 2, then there's going to be
|
|
0:12:09
|
plenty more. If we had already registered ten phones and max
|
|
0:12:13
|
ephones was ten, well then that phone won't get registered.
|
|
0:12:17
|
But yes, the simple answer to your question is if I change a
|
|
0:12:20
|
Mac address while the phones are not in fallback, the next
|
|
0:12:24
|
time they try to go to fallback it will definitely affect the
|
|
0:12:28
|
configuration in some way, either create a new ephone or possibly not allow it to be
|
|
0:12:32
|
registered.
|
|
0:12:37
|
No problem.
|
|
0:12:40
|
So one more thing I do want to point out
|
|
0:12:46
|
as I bring it up here
|
|
0:12:50
|
in another window that I'm bringing over
|
|
0:12:52
|
this is of course the link the shortcut that you have
|
|
0:12:56
|
on your CCIE candidate desktop in the lab exam
|
|
0:12:59
|
to all the product documentation.
|
|
0:13:03
|
So from here we can go to products
|
|
0:13:06
|
voice and unified communications
|
|
0:13:09
|
IP telephony
|
|
0:13:11
|
call control and this is the place where we find
|
|
0:13:14
|
communication manager or call manager, but in this case
|
|
0:13:19
|
we want to go down to UCM express or communication
|
|
0:13:23
|
manager express.
|
|
0:13:27
|
And we're going to want to look at the configuration guide.
|
|
0:13:32
|
And specifically the administrator guide.
|
|
0:13:37
|
And this where we would typically download the PDF
|
|
0:13:41
|
if we hadn't already
|
|
0:13:44
|
we can just look through this while it's downloading.
|
|
0:13:48
|
There it is and I'll actually...
|
|
0:13:52
|
I would probably have told it to save this link
|
|
0:13:59
|
so let's tell it to save it over here, that's fine
|
|
0:14:04
|
to my downloads folder is fine. It's coming down rather quickly.
|
|
0:14:10
|
And in the lab we would then pull it up as a PDF
|
|
0:14:14
|
of course we would be using Acrobat Reader.
|
|
0:14:16
|
This just happened to pull up in my Apple preview
|
|
0:14:21
|
and so your table of contents would be over on the left.
|
|
0:14:24
|
So it would look a little different certainly, but
|
|
0:14:26
|
I could look in my table of contents and see all
|
|
0:14:31
|
sorts of things relating to whether I wanted information
|
|
0:14:34
|
on configuring dial plans, hopefully you don't need information about
|
|
0:14:37
|
that, but hopefully if you needed things like configuring call park
|
|
0:14:43
|
or configuring call coverage features such as hunt groups
|
|
0:14:48
|
or pickup, call pickup.
|
|
0:14:52
|
Ok, if you needed information on paging, let's say I don't see
|
|
0:14:56
|
paging quickly and I want to do a control F and search for
|
|
0:15:00
|
paging and I see verify paging
|
|
0:15:06
|
so this happens to be under the section of configuring paging
|
|
0:15:09
|
if I just scroll up a little bit I see...
|
|
0:15:15
|
keep going because that's -- there we go. How to configure paging
|
|
0:15:18
|
for skinny phones, it's not supported for SIP phones.
|
|
0:15:22
|
And configuring a simply paging group, tells me what to do.
|
|
0:15:25
|
I need to create an ephone DN, I need to create a number,
|
|
0:15:29
|
a name and then the paging multicast address.
|
|
0:15:35
|
And then it shows that I can actually combine paging groups.
|
|
0:15:42
|
And then I verify it by placing -- so I've created my
|
|
0:15:48
|
actual paging DN and then I place a paging DN
|
|
0:15:52
|
on an ephone.
|
|
0:15:54
|
So things such as this -- this is where we're saying
|
|
0:15:57
|
I actually went back and looked, I don't have three deep dive modules
|
|
0:16:01
|
I have four deep dive modules on CME.
|
|
0:16:05
|
So there's a ton of information out there and there's a lot of
|
|
0:16:10
|
different features that could be asked of you
|
|
0:16:13
|
but the good news is with CME, it's not going to be a large
|
|
0:16:17
|
point section of your exam. It could comprise a decent
|
|
0:16:20
|
amount, I mean five to ten points certainly, maybe even
|
|
0:16:23
|
a little bit more, maybe 12 or 13, but it's not
|
|
0:16:25
|
going to be a huge section and they're going to ask you for
|
|
0:16:28
|
one or two specific things on it other than something
|
|
0:16:31
|
like basic like get SRST like functionality.
|
|
0:16:35
|
So if you need something specific -- BLF monitoring
|
|
0:16:41
|
of ephone DNs, call park paging, whatever it happens to
|
|
0:16:45
|
be, you can look at the PDF. Of course you have to know
|
|
0:16:49
|
how to get to the PDF, so that's why we were showing that...
|
|
0:16:52
|
that route and then download the PDF to your desktop.
|
|
0:16:58
|
And then you can certainly either use the table of contents
|
|
0:17:02
|
which if you wanted to do that you could just look through
|
|
0:17:04
|
the web based interface or you can -- and the reason
|
|
0:17:11
|
to have the PDF is so that you can search the entire
|
|
0:17:13
|
document for whatever feature it is versus clicking on
|
|
0:17:16
|
each one of these individual pages, html pages, and then
|
|
0:17:22
|
doing a control F and searching within that page.
|
