|
0:00:14
|
OK, so let´s move on to task 1.5 and after this task which has
|
|
0:00:20
|
little bit of involvement to it, we´ll take a quick break. So basic call forwarding,
|
|
0:00:26
|
so we´re instructed to provision James Ford´s phone which is extension 3002,
|
|
0:00:31
|
so that the calls ringing in to him that he sees the calling party name
|
|
0:00:36
|
and number as well as the original party that forwarded a call to him and
|
|
0:00:42
|
the last party to forward the call. So we´re dealing with call forwarding,
|
|
0:00:45
|
we´re basically saying if there was a call that was forwarded to James Ford´s phone,
|
|
0:00:50
|
he would not only be able to see the calling party name and number,
|
|
0:00:55
|
so those two pieces of information, so what was that referred to as earlier,
|
|
0:00:59
|
CLIP but actually CLIN Calling Line Identification Name and CLIP, Calling Line
|
|
0:01:10
|
Identifications Presentation, the presentation number and then as well as the
|
|
0:01:23
|
original party that forwarded the call and the last party to forward the call
|
|
0:01:27
|
so either understand this before we go a little bit further into the next
|
|
0:01:32
|
few bullets. Let´s take a look at understanding a little bit about call-forwards.
|
|
0:01:44
|
Alright, let´s change our color. So if I have a phone and let´s call this 1001
|
|
0:01:52
|
then another phone 1002. Now 1001 goes to call 1002, let´s just take a look
|
|
0:02:04
|
some terms. What is 1001 known as? Calling party, what's something,
|
|
0:02:11
|
what´s another term that can be used to exchange with a calling party?
|
|
0:02:21
|
Caller ID. Caller ID, what´s another term? Alerting number.
|
|
0:02:26
|
I´m actually looking for one other term that may not be as proper as
|
|
0:02:36
|
it could be in some settings but generally helpful to refer to them
|
|
0:02:42
|
as easy, you know three or four digit, three or four character numbers.
|
|
0:02:48
|
What I´m looking for is actually ANI. OK? 1001 is the ANI and actually
|
|
0:02:58
|
I´ll just go ahead and turn on everyone´s mics for these discussions,
|
|
0:03:01
|
so that anyone that wants to go ahead and speak up can go ahead do so
|
|
0:03:04
|
just like, mic was and I’ll turn down my speaker. OK, so ANI
|
|
0:03:10
|
are Automatic Number Identification. What is 1002 going to be referred to as?
|
|
0:03:17
|
Anyone else? I'm assuming DNIS. DNIS. That´s correct DNIS.
|
|
0:03:38
|
OK, Dialed Number Identification Service, so the called number. Now, if 1002
|
|
0:03:46
|
forwards a call, whether by you know manual forward or call-forward busy,
|
|
0:03:52
|
call-forward no answer really doesn´t matter. So 1003, then who is the DNIS now?
|
|
0:04:07
|
DNIS was 1002 and David puts in through Q and A, that 1003 is now the DNIS,
|
|
0:04:15
|
that´s correct. OK? Well, you can only have a calling, you can only have
|
|
0:04:22
|
one ANI and you can only have one DNIS, so what does that make
|
|
0:04:27
|
1002 at this point? Redirecting number? That´s right, the redirecting number.
|
|
0:04:38
|
So the RDNIS, the redirecting DNIS or redirecting dialed number.
|
|
0:04:51
|
OK, so that´s good, we´ve got that handled. Now, let´s say that
|
|
0:04:56
|
1003 forwards to 2001, this makes 2001 the DNIS, this is the called number.
|
|
0:05:16
|
So what does 1003 become? Anyone speak right up, no problem.
|
|
0:05:32
|
What´s 1003 going to become? 1003 is going to be the RDNIS, the redirected DNIS,
|
|
0:05:43
|
so wait a minute back to 1002, what does that make 1002?
|
|
0:05:48
|
Doesn´t that depend on what checkboxes we have in the DN as far as
|
|
0:05:52
|
original called party flags? Well, that´s actually ultimately where we´re getting to
|
|
0:05:57
|
but it doesn´t have anything to do with what 1002 is, in terms of the life
|
|
0:06:03
|
of the call just what somebody sees and that is ultimately, you´re correct Michael,
|
|
0:06:09
|
that is ultimately what we´re getting to but in terms of what 1002 is,
|
|
0:06:16
|
that doesn´t have to do anything with it. So 1002 doesn´t change,
|
|
0:06:24
|
1002 is still a redirected DNIS. It just happens to be the original directing number.
|
|
0:06:35
|
OK? So now 2001 forwards to let´s say DN 3001. Actually, let´s take a look
|
|
0:06:47
|
at our task because I believe we´re instructed to create something very similar to this.
|
|
0:06:54
|
Let´s see, OK. Set DND on Hugo Reyes´ phone 1002 to Enabled
|
|
0:07:03
|
and set Eloise Hawking´s phone to call forward all to 3002,
|
|
0:07:07
|
so if we remember we just did in basic ring settings and call forwarding,
|
|
0:07:13
|
we set Hugo Reyes´ phone to call forward busy to 2001. So we´re turning
|
|
0:07:18
|
DND on on his phone, so that when his phone is called, it will forward
|
|
0:07:23
|
to Eloise Hawking at 2001 and we´re going to forward her to 3002.
|
|
0:07:29
|
OK? So, we´re going from 1001 to 1002, Hugo with 1002 forward to 2001
|
|
0:07:37
|
and then that will call forward all the 3002, so let´s go ahead
|
|
0:07:40
|
and bring up that scenario. So that was 1001 to 1002.
|
|
0:08:03
|
OK? So, 2001 is where this is going and then 2001 was going to
|
|
0:08:15
|
forward to 3002, now that´s where we´re going to end our task but
|
|
0:08:33
|
we´ll just look one more at an example here. So what if 3002 forwarded to 3001?
|
|
0:08:40
|
3001 becomes the new DNIS, 3002 becomes a RDNIS or redirecting DNIS.
|
|
0:08:48
|
So the reason I added one more here is to display the idea that,
|
|
0:08:53
|
first of all the ANI never changes. The DNIS changes as we go from forward
|
|
0:09:02
|
forward to forward, but there´s still always only one DNIS or one dialed number.
|
|
0:09:08
|
I shouldn´t say one dialed number, one called number. As we go along,
|
|
0:09:14
|
each DNIS, if it forwards, becomes an RDNIS or Redirecting number or
|
|
0:09:20
|
forwarding number but there´s still all of these information is kept through
|
|
0:09:26
|
the entire life of the call so the fact that the call originally went to 1002
|
|
0:09:34
|
that is kept and actually when we get in to other modules that deal with
|
|
0:09:39
|
other servers in the Unified Communication Suite, one being the unified
|
|
0:09:45
|
contacts center or CUCCX especially contact center express but also enterprises
|
|
0:09:53
|
as well but we won´t be dealing with that one for now,
|
|
0:09:55
|
we see that they have the ability to reference dialed number.
|
|
0:10:01
|
Now dialed number will always be 1002, why? Because that is the number
|
|
0:10:07
|
that 1001 actually put in the keypad, now they´re a little, they press the digits
|
|
0:10:16
|
on their keypad, that´s my bad attempt at keypad there. They dialed 1002,
|
|
0:10:21
|
so 1002 is actually still the dialed number, but it´s no longer the DNIS,
|
|
0:10:27
|
it´s now a redirected number, but it´s also still known as the
|
|
0:10:32
|
original redirected number. 3002 down here, OK? If 3001 is the new
|
|
0:10:41
|
final DNIS, 3002 is the last redirecting. Now, 2001 doesn´t really have
|
|
0:10:54
|
any special you know known feature about it, it´s just a redirecting number,
|
|
0:11:00
|
we typically don´t care about anyone that was a forwarding station except
|
|
0:11:07
|
for the original forwarding station and many times the final or last
|
|
0:11:14
|
redirecting or last forwarding station. Typically don´t care about any of the other
|
|
0:11:20
|
people in between. What we tend to want to know is who was the
|
|
0:11:25
|
original person to forward, also what is the dialed number whether the user
|
|
0:11:31
|
actually intend to get no matter what they ultimately did get or not whether it´s
|
|
0:11:36
|
voicemail or 15 phones on down the line or 911, if someone had
|
|
0:11:41
|
you know set up something not so great as a forward. Whatever they ultimately
|
|
0:11:46
|
got we do tend to want to know what did they dial, so what was
|
|
0:11:49
|
the dialed number. So this original forwarded number would still be
|
|
0:11:53
|
the dialed number as well. OK? So, in terms of what do we want displayed on
|
|
0:12:05
|
this phone and actually let´s just go ahead and back up one level
|
|
0:12:10
|
because we need to take a look as it pertains to our task here
|
|
0:12:16
|
and I wanted to add that extra layer of obstruction to talk about the fact
|
|
0:12:23
|
that the middle redirecting number is typically inconsequential, so we will
|
|
0:12:30
|
remove, I´m not sure if it was going to be faster to do this and
|
|
0:12:35
|
erase manually or just to redraw the whole thing but I think it will be faster.
|
|
0:12:40
|
OK? So it´s no longer going to be RDNIS, it´s just going to be the DNIS,
|
|
0:12:44
|
so 2001 will be. OK? So, now what we´re concerned with, if we look back
|
|
0:13:12
|
at the task real quickly, is that in the above test, where the call has already
|
|
0:13:20
|
been forwarded twice, if that James´ phone, if a call is ringing in to him
|
|
0:13:30
|
so he is 3002, this is James´ phone. Call is ringing in to him,
|
|
0:13:44
|
if he sees the calling party, so the ANI and number, as well as the
|
|
0:13:48
|
original party that forwarded the call and the last party to forward the call,
|
|
0:13:52
|
so what we´re saying is that we want this phone to see,
|
|
0:14:00
|
we wanted to see ANI, we wanted to see original redirecting and
|
|
0:14:09
|
we wanted to see last redirecting. Now, this is going to be a lot of information
|
|
0:14:12
|
on the screen and I´m not necessarily advocating or suggesting that you would
|
|
0:14:16
|
want to do this too often in real life. We´re just looking at the over all,
|
|
0:14:21
|
the functionality and capability. That´s really what we want to see on the screen.
|
|
0:14:31
|
OK? We´re also told to, well let´s go ahead and do that first.
|
|
0:14:36
|
Go ahead and initiate that configuration before we move on,
|
|
0:14:46
|
so 3002 Branch 2 Phone 2 should be James Ford phone,
|
|
0:14:53
|
but what we´re seeing is and actually all these are already checked by default.
|
|
0:15:03
|
These are the two that are checked. Forwarded call information
|
|
0:15:07
|
display on this device. Now, why are we going to this device which is 3002
|
|
0:15:16
|
versus anyone of the other phones here, there DNs here, DN here, DN here.
|
|
0:15:29
|
We´re only issuing the configuration on this DN, because either this is information
|
|
0:15:38
|
on this display, on James Ford´s 3002 display about forwarded calls.
|
|
0:15:45
|
So it´s forwarded calls to him, so we want to know caller name
|
|
0:15:52
|
and number and redirected number and the dialed number. OK?
|
|
0:15:57
|
So remember the redirected number, so first of all caller name and number,
|
|
0:16:02
|
this is the calling party name and number. OK? So that´s the person
|
|
0:16:07
|
that was originally calling, this is the ANI, these are the ANI.
|
|
0:16:15
|
Then we had redirected number, we bring up this overlay, the redirected number
|
|
0:16:20
|
was in terms of CUCM, at least on this page it doesn´t make the differentiation.
|
|
0:16:27
|
I´m not saying all of the CUCM, but on this page CUCM doesn´t make differentiation
|
|
0:16:32
|
between original forwarded number and last redirecting. It essentially says the
|
|
0:16:37
|
last redirecting is the redirected number. OK? So this is specifically what
|
|
0:16:46
|
we want for the ability to see the RDNIS, the last person to redirect
|
|
0:16:53
|
then remember we mentioned a dialed number is the original dialed number
|
|
0:16:59
|
as the user is 1001, taking the original call dials it on their keypad,
|
|
0:17:06
|
this is the dialed number 1002. Here when we select dialed number,
|
|
0:17:13
|
we are saying we also want to see the original forwarding number,
|
|
0:17:20
|
that´s another way to look at that. Otherwise, if that wasn´t the case,
|
|
0:17:25
|
redirected number and dialed number would be repetitive, wouldn´t it?
|
|
0:17:29
|
It would be the same thing, in this case, it´s not. We´re going to
|
|
0:17:34
|
all of them, then click Save and if we look back at our task,
|
|
0:17:46
|
now we´re going to add this on, but we we´re told to set the DND
|
|
0:17:54
|
on Hugo Reyes´ phone. So, let´s go ahead and turn his DND on.
|
|
0:18:05
|
OK. DND should show up here as active, so we´ll forward to 2001.
|
|
0:18:10
|
We´re actually going to and I can just click this little guy right here to open.
|
|
0:18:32
|
There, back to find phones and back to Eloise was Branch 1 Phone 1, 2001.
|
|
0:18:44
|
And we´ll tell this to call forward all, not the voicemail but to, what was it?
|
|
0:18:53
|
3001, I believe. Yup, sorry to 3002. Ford's phone, save there,
|
|
0:19:17
|
we'll go ahead ans restart that phone. I have that restart over here
|
|
0:19:20
|
in another window. We will, we don´t need restart anything on
|
|
0:19:24
|
Hugo Reyes´ phone because DND obviously doesn´t need a restart.
|
|
0:19:29
|
Maybe not obvious but it does not need a restart. But now we can go
|
|
0:19:33
|
and test the functionality and then we´ll add this second bullet point on.
|
|
0:19:38
|
OK. Let´s tell this to search for phone again, make sure the phone
|
|
0:19:42
|
is registered, it is. Up and we need to add on one more phone, 2002.
|
|
0:20:14
|
OK. So, now we´ve got the loop, so Jack is going to call over to Hugo,
|
|
0:20:19
|
DND is going to forward to Eloise and Eloise is going to forward to
|
|
0:20:24
|
James Ford at 3002. Alright? So we will go ahead and place the call from
|
|
0:20:30
|
1001 to 1002 and we see that James Ford´s phone is ringing as these two
|
|
0:20:44
|
forwarded them. Forwarded for the calling party name of Jack Shepherd,
|
|
0:20:50
|
the calling party number of 1001 for Hugo Reyes, that was the dialed number
|
|
0:20:56
|
by Eloise Hawking and we can´t quite see 2001 here, but you can´t see it
|
|
0:21:01
|
on the real display either. OK? So it´s a lot of information, maybe
|
|
0:21:05
|
and very likely in most cases too much information but the important
|
|
0:21:09
|
thing is we know what each of those checkboxes do, case of the Jack Shepherd
|
|
0:21:14
|
that was over here. OK, so on the line caller name that´s the Jack Shepherd bit,
|
|
0:21:37
|
caller number that´s the 1001, redirected number that is Eloise Hawking.
|
|
0:21:46
|
OK? Eloise Hawking is the redirecting is by is being forwarded by Eloise Hawking
|
|
0:21:54
|
and the dialed number was for Hugo Reyes, he was the dialed,
|
|
0:22:00
|
he was the intended party. If there are any questions regarding any four of those
|
|
0:22:06
|
checkboxes here or this information or even our overlay, we can put back
|
|
0:22:11
|
on our white background in just a moment before we move on and add more information.
|
|
0:22:25
|
Anyone is welcome to go ahead and speak up or key in any questions
|
|
0:22:29
|
if you have any, so far. OK, with no questions then what I´ll do,
|
|
0:22:40
|
is I´ll go ahead and answer this call, actually I´m going to put mute on here.
|
|
0:22:46
|
So I can also mute on here, feedback and the spring goes well, awesome.
|
|
0:22:54
|
There you go. Alright, now I see from Jack Shepherd. What I don´t see,
|
|
0:22:59
|
I go back to my task is the next bit, Bullet 2. Ensure that there are
|
|
0:23:06
|
some sort of information that displays on James Ford´s phone indicating that
|
|
0:23:11
|
this was a call, a forwarded call even after the call has been picked
|
|
0:23:14
|
up by him, but we picked the phone on James´ phone and we don´t see
|
|
0:23:19
|
any indication of a forward call we see from Jack Shepherd,
|
|
0:23:23
|
we don´t see anything forward for Jack Shepherd. OK? So let´s go ahead
|
|
0:23:28
|
and tear that call down, to bring up some form of additional information
|
|
0:23:42
|
or additional configuration to accomplish that. Now, we don´t really see anything
|
|
0:23:46
|
here on this line indicating that, but does anyone have any idea where we might
|
|
0:23:53
|
go to look for it? That´s actually going to be under system and service parameters,
|
|
0:24:04
|
typically we´ll put up either server as long as the heading says clusterwide parameter
|
|
0:24:10
|
and it will and we´ll pull up the Cisco call manager service. Once this loads,
|
|
0:24:21
|
it´s a good idea and I think I´ve mentioned this before, really very highly
|
|
0:24:28
|
recommended good idea to go through and after you click actually advanced,
|
|
0:24:33
|
look through every single section and understand what everything does. OK?
|
|
0:24:38
|
Again if it says clusterwide parameter and then in parenthesis, what that
|
|
0:24:42
|
parameter is, so devices in general versus like devices for PRI or devices
|
|
0:24:49
|
for SIP, this is devices in general. In clusterwide parameter, we only need
|
|
0:24:55
|
to make the change on one or the other or however many subscribers
|
|
0:25:00
|
we might have on our cluster. If it doesn´t say clusterwide parameter
|
|
0:25:05
|
like this first three, CUCM call throttling, system and SDL trace and
|
|
0:25:11
|
there´s few others. Then we actually have to go do it on each individual
|
|
0:25:15
|
publisher and subscriber in the cluster. OK? So we´re going to scroll down.
|
|
0:25:20
|
Now, we could take a look at each one of these and we´re actually
|
|
0:25:23
|
going to probably through the course of all the deep dives,
|
|
0:25:26
|
look at almost every single field. We´re not going to sit here and if looking
|
|
0:25:31
|
at every feature on a phone is going to bore you, this would take
|
|
0:25:34
|
an enormous amount of time but we will be looking at some very specific ones.
|
|
0:25:40
|
How would you find them in the lab? Who would want to do this?
|
|
0:25:44
|
Well, maybe search for something like forward, so this is what we find,
|
|
0:25:49
|
clusterwide parameters for the feature, call feature of forward and we´ve got,
|
|
0:25:56
|
looks like about 12 or 13 there, we counted them. Now, what you´ll want
|
|
0:26:03
|
to do is again click on the field name which brings up contact sensitive help
|
|
0:26:08
|
for that field and actually there´s going to be a scroll bar, so I´m going to
|
|
0:26:12
|
bring it over, but that will mess up where I´m at, I´ll leave this open
|
|
0:26:16
|
and then click any one of these, to bring it right back to where I want it,
|
|
0:26:20
|
extend it over. OK. So, what I actually want and I would mention when you´re
|
|
0:26:28
|
reading through this and trying to understand, if the field name isn´t
|
|
0:26:31
|
definitive enough or maybe it seems like it is, there might be more information
|
|
0:26:38
|
under the hood very well just may want to even, instead of just looking at
|
|
0:26:43
|
these values or field names and values, look through the contact sensitive help
|
|
0:26:50
|
and read through this. And also when you do your finds, open us this window
|
|
0:26:55
|
and look Control F for find and then search for you know maybe forwarded
|
|
0:26:59
|
or something like that. You´ll tend to find a lot more information including
|
|
0:27:04
|
the values that in html textboxes and dropdowns cannot be searched for with a find.
|
|
0:27:11
|
It doesn´t look for information there, but in this contact sensitive help field
|
|
0:27:17
|
or webpage it will actually show you, not only the default but also the
|
|
0:27:22
|
minimum maximum values and any other specific buzz words or keywords.
|
|
0:27:27
|
so what we´re actually looking for is a field called retained forwarded information,
|
|
0:27:34
|
and this parameter determines whether forwarding information displays to the called
|
|
0:27:39
|
party after the party goes off hook, the default is false. We´re going to change
|
|
0:27:44
|
it to true, press save. Now, some of these features require restarting
|
|
0:27:54
|
either phones or gateways or sometimes even the CUCM service on any active CPEs
|
|
0:28:01
|
or call processing engines of which we have two, a pub and a sub
|
|
0:28:06
|
because we have subscribers doesn´t necessarily mean that they´re taking calls
|
|
0:28:11
|
and acting as call processing engines. OK? So now we´ve gone ahead
|
|
0:28:16
|
and change this retained forwarded information, true. Typically when they
|
|
0:28:24
|
require you to restart a phone or a service they´ll tell you, not.
|
|
0:28:29
|
I think they´re actually pretty good about I can off to tap my head,
|
|
0:28:32
|
I can´t think of one that does require a restart of any devices that they
|
|
0:28:36
|
don´t tell you about. There was times in the past where sometimes
|
|
0:28:40
|
you have to restart something. Thing for right now everything is fairly well
|
|
0:28:43
|
documented. But now we´ll do the exact same call again, we´re going to call
|
|
0:28:51
|
from Jack Shepherd´s phone to Hugo Reyes and it´s going to be forwarded
|
|
0:28:57
|
by Eloise Hawking and I´ll go ahead and hit mute here,
|
|
0:29:01
|
and then after I answer this call. Now, this one displays, it´s actually
|
|
0:29:09
|
not showing right now because of the, nope I thought it was because
|
|
0:29:15
|
of the bottom microphone mute. So this actually maybe one of those,
|
|
0:29:19
|
that´s not documented well, but now we have to restart the phones for.
|
|
0:29:23
|
I do not believe that we have to restart the, we're gonna make sure that,
|
|
0:29:27
|
yeah, it does say update successfully. OK. Button restart these two phones,
|
|
0:29:33
|
so that was 1001 and 3002. Correc those two phones.
|
|
0:30:13
|
Really, always you have to restart is, was James´ phone, 3002.
|
|
0:30:26
|
OK, make sure refresh is turned at a rate decent, OK. So make sure
|
|
0:30:33
|
you´re going to go ahead and turn off auto refresh on these just so it
|
|
0:30:36
|
doesn´t go off. Alright, we´ll go ahead and dial 1002 again.
|
|
0:30:49
|
Now, we see that it´s a forward Jack Shepherd, so we see after
|
|
0:30:56
|
the fact that James goes off hook, we retain information about it being
|
|
0:31:01
|
a forwarded call, now why do we want it? Well, in this example
|
|
0:31:05
|
we didn´t really illustrate a reason why we would want it and whether you can
|
|
0:31:11
|
come up with a you know example right at the top of your head or not,
|
|
0:31:14
|
sometimes they can from you know past customer history, I actually can
|
|
0:31:19
|
certainly come up with a reason why I might want original dialed number
|
|
0:31:24
|
to display or redirected number and why sometimes I might want even
|
|
0:31:29
|
to show that it´s a continued to be display as a forwarded call. For instance
|
|
0:31:37
|
I actually have a shared office space here in Columbus where I´m doing
|
|
0:31:40
|
the recording and so there´s a lot of other people in this overall general office
|
|
0:31:45
|
and whenever the receptionist answers a call, she answers the call on behalf
|
|
0:31:51
|
of anyone of the various companies that are represented here.
|
|
0:31:56
|
OK, so she answered the call for me, although I don´t really have
|
|
0:31:59
|
her answer any of my calls. She would answer it you know,
|
|
0:32:03
|
internet work expert Mark Snow, Marks Snows is, I'm not exactly sure
|
|
0:32:07
|
what exactly she says, but she needs to know who the call was originally for
|
|
0:32:12
|
but then somehow that you know it was for me but it´s ringing in to her,
|
|
0:32:18
|
so essentially we could set up a specific DID for me and have that ring
|
|
0:32:26
|
it to maybe some form of a dummy DN, that is a DN, it's not
|
|
0:32:30
|
associated line. Some people call them dummy DN, and that phantom DN
|
|
0:32:37
|
could have my name as alerting information and then her phone
|
|
0:32:44
|
could be set to display original dialed number and retain information
|
|
0:32:50
|
about it being forwarded. And maybe my number could have that or
|
|
0:32:55
|
my phone could have that set up as well, my line that I´m answering
|
|
0:32:58
|
the call on. In that way she can see that the call rang in for
|
|
0:33:02
|
a specific DID which was destined for a phantom DN for me,
|
|
0:33:06
|
so she knows how to answer the call and it displays right in front of her,
|
|
0:33:11
|
so that´s just one example. There might be many reasons why
|
|
0:33:14
|
you might want to do that, you may very well not want to do that,
|
|
0:33:17
|
but it´s certainly good to know for your real world implementations,
|
|
0:33:22
|
be they in house or consulting clients or maybe even more importantly,
|
|
0:33:28
|
if you´re here possibly Cisco certifications like the CCIE voice exam.
|
|
0:33:33
|
OK, we´ve got one more thing to add to this, so let´s go ahead
|
|
0:33:36
|
and look at our last bit. In the above test, where the call is already
|
|
0:33:43
|
been forwarded twice, if James should attempt to forward the call again,
|
|
0:33:48
|
it should fail whenever Jack initiates the above call, forwarding James phone
|
|
0:33:54
|
or go ahead and forward James phone to 3001 and then place the call
|
|
0:33:59
|
from Jack at 1001, to James well actually to 1002 to Hugo forwarding
|
|
0:34:05
|
to Eloise forwarding to James and then James forwarding to 3001 to test.
|
|
0:34:11
|
You should hear re order tone. You can unforward when you´re done testing.
|
|
0:34:14
|
So what are we essentially saying? We´re saying now that if James at 3002
|
|
0:34:27
|
forward the call one more time to another DN of 3001 then essentially
|
|
0:34:43
|
this call forward here failed and if Jack whose making the call here over to Hugo,
|
|
0:34:55
|
he makes that same call and it forwards, forwards, forwards or it tends to forward
|
|
0:35:01
|
it should fail and Jack should hear reorder tone. So what is this doing?
|
|
0:35:06
|
How many times are we forwarding it here? So let´s see, it´s forwarded once,
|
|
0:35:11
|
twice, three times. OK? So we´re essentially saying that there should be well,
|
|
0:35:23
|
this could I shouldn´t say essentially, it could be interpreted a couple different ways
|
|
0:35:28
|
again part of our task here is to begin to prepare you for how the
|
|
0:35:33
|
wording of the CCIE voice exam will be, read another certifications that may
|
|
0:35:39
|
not give you exactly what they want you to do in terms of what they
|
|
0:35:44
|
want you to configure, what fields what values, but they will tell you
|
|
0:35:49
|
the functionality that they want to occur and so we very clearly did specify
|
|
0:35:55
|
the functionality, if the call had already been forwarded twice and James attempts
|
|
0:36:00
|
to forward the call again, it should fail whenever Jack initiates the above call.
|
|
0:36:05
|
OK? SO here we´re saying or one way to interpret this is that the third
|
|
0:36:12
|
forward will be the maximum amount that it can be forwarded.
|
|
0:36:22
|
OK? Actually, let me ask you, so how do you view this? What we are
|
|
0:36:27
|
getting at here is the ability, specifically we´re looking for maximum number
|
|
0:36:35
|
of forwards, maximum number of hops and a forward and as you can see
|
|
0:36:40
|
the service parameters in just a moment, as I go ahead and press mute
|
|
0:36:44
|
to let everyone give me their feedback and ideas, I navigate over there.
|
|
0:36:49
|
What I want to know is what value am I looking for, for this field?
|
|
0:36:54
|
For maximum number of forwarded calls or hops.
|
|
0:37:09
|
Thus we don´t want the third forward to be completed,
|
|
0:37:13
|
we want to set the max hops to two.
|
|
0:37:33
|
OK? So we are looking for forward maximum hop count, this parameter
|
|
0:37:39
|
specifies the maximum number of times that a single call can be forwarded
|
|
0:37:42
|
or diverted, as special considerations for QSIG, which we won´t
|
|
0:37:46
|
take a look at today, so we really don´t care about any of the rest
|
|
0:37:50
|
of this because it´s dealing with QSIG, special considerations for QSIG.
|
|
0:37:55
|
So Michael saying that we should change this value to two, so the maximum
|
|
0:38:02
|
hop count for forwarded calls to be two, well we´ll just test it.
|
|
0:38:18
|
Alright, so let´s place the call, first of all, let´s just make sure that
|
|
0:38:25
|
it rings normally to James, okay, it rings normally to James.
|
|
0:38:27
|
OK, it rings normally to James, so it was forwarded once
|
|
0:38:33
|
and then twice to James, but now when we set James to call forward all,
|
|
0:38:41
|
actually we have to probably take a look at his and I'll open this
|
|
0:38:45
|
in a new window, so Branch 2 Phone 2 and take a look at the call
|
|
0:38:51
|
and search base on his call forward all line, which isn´t set in to anything,
|
|
0:38:58
|
probably doesn´t matter because they all contain internal DNs. We´re going to
|
|
0:39:03
|
forward all to 3001 to actually see about call forward all should
|
|
0:39:15
|
probably be set here. Well, it is call forward all, so now let´s go ahead
|
|
0:39:24
|
and try this call, there we go, there shows forwarded to 3001,
|
|
0:39:29
|
let´s go ahead and try the call now. Now, we´re calling Hugo whose forwarding
|
|
0:39:36
|
to Eloise whose forwarding to James and we´re getting reorder tone
|
|
0:39:40
|
because the maximum amount of forwards has now been violated.
|
|
0:39:44
|
So Michael is correct, we wanted the maximum amount of forward hops to be two,
|
|
0:39:50
|
that´s what we´re looking for here. OK? See if there´s anything else to that task,
|
|
0:40:02
|
I believe that was it. At the risk of being technically we have to unforward it
|
|
0:40:09
|
and make sure it rings on his phone before we could say that´s accurate.
|
|
0:40:11
|
Well, it´s true we did actually after I changed this maximum forward,
|
|
0:40:18
|
after I changed this value we did try the call but it does also say
|
|
0:40:23
|
to uforward it again, so let´s go ahead and unforward it, ring it and
|
|
0:40:30
|
the call does ring through two hops on to James phone and we can answer it.
|
|
0:40:38
|
It´ll show that it was a forwarded call. OK? David had another suggestion.
|
|
0:40:53
|
And he asked what if we wanted to or maybe what if we interpreted this task
|
|
0:41:00
|
as in the above test where the call is already been forwarded if James
|
|
0:41:05
|
should attempt to forward the call again, it should fail whenever Jack initiates
|
|
0:41:09
|
the above call, so maybe just for James. So David's suggestion for that,
|
|
0:41:14
|
if we wanted to limit it to just to James forwarding it, that would fail
|
|
0:41:18
|
would be to configure a call forward all calling search base but essentially
|
|
0:41:23
|
cannot get to the DN of 3001 and that´s a very valid solution as well.
|
|
0:41:31
|
It´s not where we´re looking for but It would work and in the lab,
|
|
0:41:34
|
let me say this two ways, in the lab functionality is what is rewarded
|
|
0:41:41
|
or given points for not stylistic way of implementing or configuration
|
|
0:41:47
|
or meeting the tasks requirements, that being said there is one thing to consider
|
|
0:41:53
|
which is that in the lab another task maybe not even geographically contiguous
|
|
0:42:00
|
so another task that might not even be right next to it or
|
|
0:42:02
|
at the same page or maybe four pages up, feeling of something completely different
|
|
0:42:08
|
might have somewhere and I´m not highlighting it because it does,
|
|
0:42:11
|
this one doesn´t, but might have some form of a restriction that, this gets
|
|
0:42:18
|
into the I of CCIE, that internet works in some fashion with this task
|
|
0:42:24
|
and causes you to only be able to accomplish it in some in one particular way
|
|
0:42:31
|
or with one particular type of configuration. We don´t have anything like that
|
|
0:42:34
|
on this technology focused sub module. OK? We have nothing like that,
|
|
0:42:42
|
however just keep in mind that that is possible and something to watch out for,
|
|
0:42:47
|
but in as far as this module and as far as this task is concerned,
|
|
0:42:53
|
David´s solution would be completely a valid one, we could simply block
|
|
0:42:58
|
the ability to reach this DN or whatever DN he actually happens to press,
|
|
0:43:08
|
you have to call forward all with some other calling search base.
|
|
0:43:15
|
But the only problem is, if we did that, we would actually have to
|
|
0:43:19
|
be the administrator that would configure the DN to forward there
|
|
0:43:23
|
and configure the CSS that would not match, why is that? If we configure a,
|
|
0:43:29
|
let´s say we left this blank as an administrator, the value for the destination
|
|
0:43:33
|
and we changed the calling search base to something that would not allow
|
|
0:43:38
|
him to get there, a transformed calling search base, that does not have
|
|
0:43:41
|
any internal DNs. You can save this and illustrate this, but do a restart
|
|
0:43:50
|
and yes we´ll have to reconnect with this phone. Still trying to restart,
|
|
0:44:07
|
you can see in front of me. OK, it should be done, it looks like it,
|
|
0:44:18
|
maybe kept the display. OK, let´s just test just to make sure if the call works,
|
|
0:44:23
|
call forwards no problem, end the call. Now if I´m over here and I´m James,
|
|
0:44:34
|
you´re one missed call and I tried to do a call forward, and I dial 3001,
|
|
0:44:40
|
turn this up a little bit. OK, if I try to dial 3001. OK?
|
|
0:45:00
|
So, I couldn't even initiate the call forward, so when Jack goes to call me
|
|
0:45:06
|
it will still ring because I wasn´t able to initiate the call forward
|
|
0:45:11
|
so I didn´t get reorder tone however, an administrator could have done this
|
|
0:45:19
|
call forward all, even though the DN could not be reached, erase that
|
|
0:45:25
|
and restart over here. Wait for this phone to restart.
|
|
0:45:48
|
Yeah, it comes back up properly, good. But now if I redial,
|
|
0:45:54
|
actually let´s go off hook and just clear this and we can see that
|
|
0:45:59
|
we´re forwarded to 3001 even though the CSS shouldn’t allow us
|
|
0:46:02
|
to get there, so now we get the reorder tone calling from Jack.
|
|
0:46:08
|
So David´s idea was a good one in that it could be accomplished
|
|
0:46:12
|
by the administrator, it wouldn´t allow future functionality from the end user
|
|
0:46:18
|
to accomplish it because of the CSS that wouldn't even allow us to begin
|
|
0:46:23
|
to send our call forward anywhere that we weren´t allowed to, however
|
|
0:46:28
|
ultimately it would meet the requirements. If you´re ever in doubt of something
|
|
0:46:33
|
like this in terms of wording or you have multiple ways that you could
|
|
0:46:37
|
accomplish something or maybe you can´t think of multiple ways,
|
|
0:46:41
|
you can only think of one way you can certainly go up
|
|
0:46:45
|
and talk to the proctor and say, listen I´m not exactly sure if this is
|
|
0:46:51
|
the way that you want me to implement this portion and show
|
|
0:46:56
|
them your lab book, show them say, listen I understand everything
|
|
0:46:58
|
you´re asking for these three bullets. Got it no problem, but I´m not
|
|
0:47:03
|
exactly sure what to do here, I know what you´re wanting to accomplish and I
|
|
0:47:10
|
could do it in this manner or in this fashion, but not sure if it will
|
|
0:47:14
|
meet your requirements. Is this what you´re looking for or are you
|
|
0:47:18
|
looking for something a little bit different or maybe even go ahead
|
|
0:47:23
|
and mention, I know that this would not allow future functionality to work,
|
|
0:47:27
|
only the administrator configured it but these are valid things to bring up
|
|
0:47:32
|
to a proctor and ask them, are you looking for something more?
|
|
0:47:36
|
Should I go back and keep reading? They´re not going to tell you exactly
|
|
0:47:39
|
what to do but they will, especially if you demonstrate and understand,
|
|
0:47:44
|
demonstrate your understanding and say, hey I understand what everything
|
|
0:47:47
|
you´re asking me to do here and I´ve already got that working,
|
|
0:47:49
|
it´s just this one part that the wordings are a little unclear to me and
|
|
0:47:53
|
so can you help me out with it? What are you looking for or
|
|
0:47:56
|
if you can´t tell me exactly what you´re looking for here is what I´m interpreting
|
|
0:48:00
|
that as and how to implement that, would that, do you think that
|
|
0:48:08
|
would meet your requirements or should I keep looking, other way to do it,
|
|
0:48:12
|
is there a better way? Those are questions that they can ask or answer you know,
|
|
0:48:17
|
they could say well yeah, I actually, the way that you´re mentioning, you´re right
|
|
0:48:24
|
it wouldn´t allow future functionality. It wouldn´t allow the user to implement
|
|
0:48:28
|
that call forward all so it doesn´t, might meet the requirements of the herding
|
|
0:48:34
|
but I can tell you that there is something else we´re looking for,
|
|
0:48:38
|
so keep looking. They can help you out if you give them enough
|
|
0:48:41
|
good information, but they´re not going to give you the answer.
|
|
0:48:45
|
But certainly ask any questions regarding anything that you don´t have,
|
|
0:48:49
|
full understanding or clarification of the wording. OK? Great suggestion David.
|
