|
0:00:14
|
So let´s go ahead and log in to CUCM
|
|
0:00:16
|
and take a look at some of the
|
|
0:00:17
|
examples of some of these
|
|
0:00:21
|
so first of all, let´s look at
|
|
0:00:24
|
time of day
|
|
0:00:26
|
partitions
|
|
0:00:30
|
and we´ll just create a partition here
|
|
0:00:32
|
we´ll call a partition
|
|
0:00:34
|
let´s call it
|
|
0:00:37
|
PST
|
|
0:00:39
|
haven´t really thought of a good name
|
|
0:00:41
|
let´s say PST
|
|
0:00:44
|
Monday thru Friday
|
|
0:00:47
|
8 to 5
|
|
0:00:51
|
and then we´ll also create
|
|
0:00:52
|
or let´s you know just let´s just use
|
|
0:00:53
|
the example that we had
|
|
0:00:56
|
8 to 12
|
|
0:00:58
|
Eastern
|
|
0:01:00
|
and then partition for
|
|
0:01:03
|
PST
|
|
0:01:04
|
or GMT -8
|
|
0:01:06
|
or Monday thru Friday 9
|
|
0:01:09
|
to 17 so that´s
|
|
0:01:13
|
according to Eastern time that´s
|
|
0:01:15
|
12 to really 20
|
|
0:01:20
|
OK? or
|
|
0:01:21
|
8 PM
|
|
0:01:24
|
so we´ll create those two
|
|
0:01:27
|
we´ll create the partitions
|
|
0:01:28
|
not that we really have to do those first
|
|
0:01:31
|
and now we´ll come back to
|
|
0:01:32
|
class of control and we´ll create time periods
|
|
0:01:38
|
and we´ll give this a time
|
|
0:01:39
|
period called
|
|
0:01:41
|
let´s just say Monday thru Friday
|
|
0:01:46
|
and we´ll say
|
|
0:01:51
|
8 to 12
|
|
0:01:54
|
so the time of day start
|
|
0:01:56
|
is going to be 0800
|
|
0:01:58
|
time of day end
|
|
0:02:01
|
is going to be 1200
|
|
0:02:05
|
and we either want it
|
|
0:02:06
|
to repeat every week
|
|
0:02:08
|
from Monday thru Friday
|
|
0:02:11
|
or else we coud have it
|
|
0:02:12
|
repeat every year on very
|
|
0:02:14
|
particular dates
|
|
0:02:15
|
from those dates until another date
|
|
0:02:17
|
of from the date to the same date
|
|
0:02:19
|
if we just want it for one date
|
|
0:02:21
|
we could even say things like
|
|
0:02:22
|
like Monday thru Monday if we
|
|
0:02:23
|
only wanted this to be a Monday rule
|
|
0:02:26
|
but we are saying Monday thru Friday
|
|
0:02:31
|
OK, so we have a
|
|
0:02:33
|
time period there
|
|
0:02:35
|
notice there is no time zone
|
|
0:02:38
|
we haven´t added that yet
|
|
0:02:40
|
it´s not done on the time period
|
|
0:02:41
|
so I´m just going to copy that time period
|
|
0:02:44
|
and say Monday thru Friday, 9 to 17
|
|
0:02:48
|
and we´ll modify this
|
|
0:02:50
|
to say 9
|
|
0:02:52
|
to, I passed it
|
|
0:02:55
|
1700 again Monday thru Friday
|
|
0:03:00
|
so now we have these two
|
|
0:03:03
|
time periods and there´s also one
|
|
0:03:05
|
that is preconfigured and
|
|
0:03:06
|
non-configurable call all the time
|
|
0:03:10
|
so now we´re going to create
|
|
0:03:12
|
and actually let´s just go ahead and create
|
|
0:03:14
|
a few more like what we saw
|
|
0:03:15
|
in that particular
|
|
0:03:17
|
let´s to Saturday
|
|
0:03:19
|
I think it was
|
|
0:03:21
|
9
|
|
0:03:23
|
9 to let´s just say 17
|
|
0:03:29
|
so we´ll do
|
|
0:03:30
|
9 AM to
|
|
0:03:35
|
to 1700
|
|
0:03:37
|
repeat every week on Saturday
|
|
0:03:40
|
thru Saturday
|
|
0:03:43
|
and then we´ll copy this
|
|
0:03:45
|
change the name to Sunday
|
|
0:03:48
|
and change the
|
|
0:03:50
|
day from Sunday
|
|
0:03:53
|
to Sunday
|
|
0:03:55
|
so now we´ve got 4
|
|
0:03:58
|
and
|
|
0:03:59
|
what we´re going to do
|
|
0:04:01
|
is then come up and create
|
|
0:04:03
|
our time schedule
|
|
0:04:07
|
and we see that
|
|
0:04:09
|
we have a default of all the time
|
|
0:04:12
|
we´re going to create one called
|
|
0:04:17
|
Monday thru Friday
|
|
0:04:21
|
8 to 12
|
|
0:04:25
|
Saturday
|
|
0:04:28
|
9 to17
|
|
0:04:33
|
and we can give it a description
|
|
0:04:36
|
and so we´re going to add our 8 to 12
|
|
0:04:39
|
and our Saturday
|
|
0:04:41
|
to the selected time periods
|
|
0:04:43
|
and we´ll press save again
|
|
0:04:46
|
notice that we´re not
|
|
0:04:48
|
specifying any time zone yet
|
|
0:04:51
|
we´ll go ahead and press Sunday
|
|
0:04:52
|
change the name
|
|
0:05:01
|
and we will
|
|
0:05:03
|
get rid of these and are other two
|
|
0:05:09
|
OK, so now we´ve got this
|
|
0:05:10
|
two time schedules
|
|
0:05:12
|
now, we´re going to go back to the
|
|
0:05:15
|
there we go
|
|
0:05:16
|
back to the partitions that we just created
|
|
0:05:31
|
and what we´re going to do is assign
|
|
0:05:33
|
the time schedule for
|
|
0:05:36
|
Monday thru Friday
|
|
0:05:38
|
9 to 17 and a Sunday
|
|
0:05:40
|
9 to 17
|
|
0:05:42
|
and here´s where we going to
|
|
0:05:43
|
specify the time zone
|
|
0:05:45
|
so the reason we do this
|
|
0:05:47
|
on the time zone on the partition
|
|
0:05:49
|
is so that we can be more granular
|
|
0:05:51
|
or modular really
|
|
0:05:53
|
and create time patterns
|
|
0:05:55
|
or time periods and schedules
|
|
0:05:56
|
that actually
|
|
0:05:58
|
can be use for more than
|
|
0:06:00
|
one time zone
|
|
0:06:02
|
because we´re only specifying the time zone
|
|
0:06:03
|
once we actually get to the part
|
|
0:06:05
|
partition where we assign the time schedule
|
|
0:06:08
|
so GMT -8
|
|
0:06:12
|
for let´s say
|
|
0:06:16
|
where is it?
|
|
0:06:17
|
Pacific standard time
|
|
0:06:19
|
8 for GMT -8 and then
|
|
0:06:21
|
Pacific daylight time
|
|
0:06:23
|
for instance
|
|
0:06:25
|
and then we can go back
|
|
0:06:28
|
and say
|
|
0:06:30
|
Eastern for our Eastern
|
|
0:06:34
|
partition and we´ll use the
|
|
0:06:37
|
I think, yes, 8 to 12
|
|
0:06:39
|
specified time zone
|
|
0:06:41
|
is GMT -5
|
|
0:06:46
|
or
|
|
0:06:49
|
I can find it here, here we go
|
|
0:06:52
|
we can either find the particular city if we want
|
|
0:06:55
|
or something generic like Eastern
|
|
0:06:57
|
standard time and Eastern daylight time
|
|
0:06:59
|
GMT 5
|
|
0:07:01
|
and now we´ve set those partitions
|
|
0:07:03
|
so again
|
|
0:07:05
|
as soon as I place
|
|
0:07:07
|
you know go to a phone and use it
|
|
0:07:09
|
to directory number or
|
|
0:07:10
|
even just create a
|
|
0:07:11
|
stand alone unassigned directory number
|
|
0:07:15
|
whether it´s a meet me pattern
|
|
0:07:17
|
whether it´s a
|
|
0:07:19
|
route pattern
|
|
0:07:20
|
whether it´s a translation pattern
|
|
0:07:22
|
all of those are patterns or dn´s
|
|
0:07:24
|
and they have a partition
|
|
0:07:25
|
anything that has a partition
|
|
0:07:28
|
if I have
|
|
0:07:30
|
given it that this partition
|
|
0:07:32
|
then it has to be currently
|
|
0:07:35
|
and it doesn´t matter whether it´s
|
|
0:07:36
|
you know whether we´re looking at it
|
|
0:07:38
|
from the perspective of Eastern time zone
|
|
0:07:39
|
but if I look at it from the perspective
|
|
0:07:41
|
of Eastern time zone
|
|
0:07:42
|
it has to be Monday thru Friday
|
|
0:07:44
|
8AM until
|
|
0:07:45
|
1200 hours or 12 PM noon
|
|
0:07:48
|
or Saturday from 9 AM to
|
|
0:07:51
|
1700 hours GMT
|
|
0:07:54
|
minus 5
|
|
0:07:55
|
if it´s in the other partition, it had to be
|
|
0:07:57
|
from the perspective of GMT -8
|
|
0:08:00
|
had to be Monday thru Friday
|
|
0:08:01
|
9 AM which is of course
|
|
0:08:04
|
12 PM Eastern
|
|
0:08:06
|
until 1700 PST
|
|
0:08:08
|
or PDT and
|
|
0:08:10
|
all day Sunday
|
|
0:08:12
|
from 9 until 1700 PST
|
|
0:08:15
|
as long as it´s storing those times
|
|
0:08:17
|
then the partition is visible
|
|
0:08:19
|
and the dn will be able to be dialed
|
|
0:08:21
|
if it´s not during those times
|
|
0:08:23
|
then the partition will not be able to be dialed
|
|
0:08:26
|
now if we had, let´s say
|
|
0:08:27
|
the example that we had earlier
|
|
0:08:30
|
in the slides of 2
|
|
0:08:32
|
hunt pilots for 8000
|
|
0:08:34
|
what would happen to the calls everytime
|
|
0:08:37
|
that a call came in and it wasn´t
|
|
0:08:39
|
let´s say it was Monday
|
|
0:08:41
|
at
|
|
0:08:42
|
2300 hours Eastern
|
|
0:08:45
|
which is
|
|
0:08:46
|
you know 2000 hours or 8 PM Pacific
|
|
0:08:49
|
so it doesn´t fall within either of the
|
|
0:08:52
|
time periods
|
|
0:08:54
|
time schedules or time periods
|
|
0:08:56
|
for either of the partition
|
|
0:08:58
|
well in that case
|
|
0:08:59
|
as we saw it
|
|
0:09:01
|
the user will get reorder tone
|
|
0:09:03
|
we might want to configure
|
|
0:09:04
|
a third partition
|
|
0:09:06
|
that´s active all the time
|
|
0:09:08
|
and place it lowest in the
|
|
0:09:10
|
Calling Search Space
|
|
0:09:11
|
and have it be a catch all
|
|
0:09:13
|
sort of a catch all net
|
|
0:09:14
|
you know maybe that would route calls to
|
|
0:09:17
|
voice mail
|
|
0:09:18
|
maybe it would route them somewhere else
|
|
0:09:19
|
regardless
|
|
0:09:20
|
it would be a dn that caught all
|
|
0:09:22
|
the calls when they didn´t match
|
|
0:09:25
|
the equal
|
|
0:09:27
|
dn match of 8,000
|
|
0:09:28
|
during the higher ordered
|
|
0:09:31
|
visible or active paritition times
|
|
0:09:34
|
based on the time period or time schedule
|
|
0:09:38
|
OK? Taking a look at the
|
|
0:09:42
|
example that we talked about for
|
|
0:09:44
|
the hunt group call coverage
|
|
0:09:48
|
if I create a directory number
|
|
0:09:50
|
and I simply say
|
|
0:09:52
|
call forward all to
|
|
0:09:54
|
let´s say a pilot point
|
|
0:09:56
|
for instance 8,000
|
|
0:09:58
|
and I send it to you know whatever
|
|
0:10:00
|
Calling Search Space I know
|
|
0:10:02
|
can get to that hunt pilot
|
|
0:10:05
|
OK, so I call forward all
|
|
0:10:08
|
and then
|
|
0:10:10
|
we go over to the hunt pilot
|
|
0:10:13
|
OK? So we create a line group
|
|
0:10:15
|
lets just actually go through
|
|
0:10:16
|
and look at a line group
|
|
0:10:18
|
In fact i actually already have one
|
|
0:10:20
|
configured so I´m just going to
|
|
0:10:21
|
use that for voice mail
|
|
0:10:25
|
so first of all
|
|
0:10:27
|
I have my line group named
|
|
0:10:29
|
my ring no answer
|
|
0:10:31
|
that´s what RNA
|
|
0:10:31
|
Ring No Answer reversion time out so
|
|
0:10:34
|
What Ring No answer time out
|
|
0:10:36
|
should be used
|
|
0:10:38
|
before the line group
|
|
0:10:40
|
considers
|
|
0:10:41
|
the call not to be answered
|
|
0:10:43
|
and this needs to be a shorter time
|
|
0:10:46
|
then your selected dn´s
|
|
0:10:50
|
have for their Ring No Answer, otherwise
|
|
0:10:53
|
you have the possibility
|
|
0:10:54
|
depending on service parameters
|
|
0:10:56
|
of the call actually
|
|
0:10:57
|
forwarding in to that user´s voicemail box
|
|
0:11:00
|
OK?
|
|
0:11:00
|
So typically you want to have this as
|
|
0:11:02
|
shorter than your shortest
|
|
0:11:07
|
line group number
|
|
0:11:09
|
has for their Ring No Answer
|
|
0:11:11
|
then we have the distribution Algorithm
|
|
0:11:13
|
how should
|
|
0:11:14
|
here´s our find directory numbers
|
|
0:11:16
|
to add to a line group
|
|
0:11:17
|
so what partition are they in
|
|
0:11:19
|
what does a directory number contain
|
|
0:11:20
|
or do we just want to scroll through them
|
|
0:11:21
|
if there´s not that many
|
|
0:11:23
|
and we can select them
|
|
0:11:24
|
by holding command
|
|
0:11:26
|
or control if you´re on a Mac
|
|
0:11:28
|
or I can select them using the shift
|
|
0:11:31
|
key to select a range
|
|
0:11:32
|
and add to line group
|
|
0:11:34
|
but once we have the selected dn´s
|
|
0:11:37
|
of course I can higlight those and
|
|
0:11:38
|
bring them down to the remove
|
|
0:11:40
|
dn press save and then they want up here, but
|
|
0:11:43
|
of the selected dn´s, how do I want
|
|
0:11:45
|
calls to be extended to them?
|
|
0:11:47
|
Do I simply want to tap down again?
|
|
0:11:49
|
we will always try 1851
|
|
0:11:51
|
unless it´s not available
|
|
0:11:52
|
then it will try 1852
|
|
0:11:55
|
or do I want it to be circular?
|
|
0:11:56
|
which mean always try 1851
|
|
0:11:58
|
then 1852, then 1851
|
|
0:12:01
|
then 1852 and continue
|
|
0:12:03
|
Do I want it to be longest idle?
|
|
0:12:06
|
you know which call, or which dn
|
|
0:12:08
|
or which number has not
|
|
0:12:10
|
had a call the most recent
|
|
0:12:12
|
which one´s been the idle the longest
|
|
0:12:14
|
or broadcast?
|
|
0:12:15
|
send them to both at the same time
|
|
0:12:18
|
OK, send all calls to both
|
|
0:12:20
|
ring all calls or all dn´s simultaneously
|
|
0:12:25
|
then I have hunt options
|
|
0:12:27
|
if there was no answer
|
|
0:12:28
|
or if there was busy
|
|
0:12:29
|
or if the phone was basically
|
|
0:12:31
|
not registered, not available
|
|
0:12:33
|
three different options
|
|
0:12:35
|
if the phone
|
|
0:12:37
|
first member, so let´s say we´re doing
|
|
0:12:39
|
a tap down which mean we will always
|
|
0:12:41
|
extend the call to 1851 first
|
|
0:12:44
|
if it´s not
|
|
0:12:45
|
if there is no answer
|
|
0:12:47
|
then we can try the next member
|
|
0:12:50
|
and then go to the next group
|
|
0:12:53
|
in the hunt list, so remember
|
|
0:12:56
|
we´re at the line group level
|
|
0:12:58
|
we build line group
|
|
0:13:00
|
then we build hunt list
|
|
0:13:01
|
then we build hunt pilot
|
|
0:13:02
|
a hunt list can contain
|
|
0:13:03
|
multiple line groups
|
|
0:13:06
|
hunt pilot only points to one list
|
|
0:13:08
|
so here we´re saying should we
|
|
0:13:10
|
go to the next member in this group
|
|
0:13:13
|
then should we try the next
|
|
0:13:15
|
group in the hunt list
|
|
0:13:17
|
or
|
|
0:13:18
|
should we try the next member
|
|
0:13:21
|
but if that member is in available
|
|
0:13:23
|
do not go to the next group
|
|
0:13:25
|
in which case it goes back up
|
|
0:13:27
|
to the hunt pilot
|
|
0:13:28
|
and to it´s call forward no answer
|
|
0:13:32
|
or should we not even try
|
|
0:13:33
|
any of the remaining members in this group
|
|
0:13:36
|
we just go directly to the next group
|
|
0:13:39
|
or should we stop hunting all
|
|
0:13:41
|
together and simply go back
|
|
0:13:42
|
to the hunt pilot
|
|
0:13:43
|
and report a call
|
|
0:13:45
|
forward no answer in which case the
|
|
0:13:47
|
hunt pilot will take its
|
|
0:13:48
|
call forward no answer setting
|
|
0:13:51
|
we have these options
|
|
0:13:52
|
all four of these options
|
|
0:13:53
|
for these 3 situations
|
|
0:13:56
|
that the
|
|
0:13:57
|
and it doesn´t necessarily
|
|
0:13:58
|
have to be tap down it could be
|
|
0:14:00
|
circular and whichever particular
|
|
0:14:03
|
phone happened to be
|
|
0:14:05
|
you know, during the instance
|
|
0:14:06
|
that the call has made, maybe we had 10
|
|
0:14:09
|
here and where at
|
|
0:14:10
|
call 7
|
|
0:14:11
|
and it turns up not available
|
|
0:14:14
|
At that instant, what do we want to do?
|
|
0:14:16
|
Do we want to try the next member
|
|
0:14:17
|
then go to the next
|
|
0:14:19
|
line group in the hunt list
|
|
0:14:21
|
or try the next member but then don´t
|
|
0:14:23
|
go to the next group, go back up to the hunt
|
|
0:14:25
|
pilot and do a
|
|
0:14:26
|
essentially that would be a
|
|
0:14:27
|
call forward busy, I believe
|
|
0:14:30
|
and then
|
|
0:14:32
|
I should say or do you want to skip
|
|
0:14:34
|
the remaining members in this group and go
|
|
0:14:35
|
directly to the next group
|
|
0:14:37
|
in the hunt list
|
|
0:14:38
|
or do we just want to stop hunting
|
|
0:14:39
|
all together
|
|
0:14:40
|
and again go back up
|
|
0:14:42
|
to the hunt pilot
|
|
0:14:43
|
so let´s go to
|
|
0:14:46
|
our hunt list
|
|
0:14:48
|
and take a look
|
|
0:14:51
|
so here we have
|
|
0:14:52
|
1 line group
|
|
0:14:55
|
and we could again have multiple
|
|
0:14:59
|
we have to specify what CUCM group
|
|
0:15:01
|
is going to be
|
|
0:15:03
|
utilize in terms of which subscribers
|
|
0:15:06
|
typically subscribers only but
|
|
0:15:08
|
subscriber publisher here in our small lab
|
|
0:15:10
|
we´ll take and process the calls
|
|
0:15:13
|
should this hunt list be enabled?
|
|
0:15:15
|
and is this
|
|
0:15:16
|
particular hunt list which in this case it is
|
|
0:15:18
|
is it use for voicemail?
|
|
0:15:20
|
and we always want to remember to reset
|
|
0:15:22
|
anything with the word list
|
|
0:15:24
|
in it´s title should always be reset before useit
|
|
0:15:29
|
and finally we go up to the hunt pilot
|
|
0:15:33
|
and so this is where
|
|
0:15:36
|
just like every other
|
|
0:15:38
|
route pattern or anything else
|
|
0:15:40
|
we have the ability to
|
|
0:15:42
|
deal with calling party transformation
|
|
0:15:44
|
connected party, called party
|
|
0:15:47
|
OK?
|
|
0:15:49
|
we have AAR group settings
|
|
0:15:52
|
that need to be filled out
|
|
0:15:54
|
and we also have the
|
|
0:15:57
|
so here´s where we configure our hunt list
|
|
0:16:01
|
we´re in a partition whether it´s a time of day
|
|
0:16:04
|
partition or not
|
|
0:16:05
|
and
|
|
0:16:07
|
here´s where we have our ability
|
|
0:16:09
|
to forward hunt no answer
|
|
0:16:11
|
or forward hunt busy
|
|
0:16:14
|
OK? So if we wanted to forward hunt no answer
|
|
0:16:16
|
or busy to a specific destination we would
|
|
0:16:19
|
put in that destination dn
|
|
0:16:20
|
and fill in the Calling Seach Space
|
|
0:16:23
|
if we wanted to use
|
|
0:16:25
|
personal preference
|
|
0:16:27
|
we would tick these boxes
|
|
0:16:29
|
or we could tick one box just for busy and forward
|
|
0:16:32
|
you know to a specific destination
|
|
0:16:34
|
for no answer if that´s what we desired
|
|
0:16:36
|
and again that would go back
|
|
0:16:38
|
to let´s just say
|
|
0:16:41
|
a generic directory number
|
|
0:16:43
|
and that directory number
|
|
0:16:45
|
that had originally done the forward all
|
|
0:16:47
|
to the hunt pilot
|
|
0:16:50
|
the used personal preference
|
|
0:16:53
|
would then come back to these original
|
|
0:16:55
|
directory number that had done the forward all
|
|
0:16:57
|
and say, what is the forward no coverage
|
|
0:16:59
|
for internal or external set to
|
|
0:17:02
|
and of course internal
|
|
0:17:04
|
specifies
|
|
0:17:05
|
is the calling number
|
|
0:17:07
|
something that we see as a pattern
|
|
0:17:09
|
or dn that´s registered to CUCM
|
|
0:17:13
|
if it´s not something that we see then we
|
|
0:17:16
|
can use something alternate in terms of
|
|
0:17:18
|
where we want to route it
|
|
0:17:19
|
typically these are the same thing
|
|
0:17:20
|
so maybe we wanted to route
|
|
0:17:22
|
this call out to, I don´t know 911
|
|
0:17:25
|
bad idea in real life, but just as an example
|
|
0:17:28
|
OK?
|
|
0:17:28
|
And so we have specify a Calling Search Space
|
|
0:17:31
|
that contains the partition
|
|
0:17:32
|
that can match that pattern
|
|
0:17:34
|
whether it´s a translation or route pattern
|
|
0:17:36
|
doesn´t matter
|
|
0:17:38
|
OK? And notice it automatically
|
|
0:17:39
|
configrues my external coverage
|
|
0:17:41
|
for me as soon as I do internal
|
|
0:17:43
|
that´s just out of, you know
|
|
0:17:46
|
It´s just kind of a nice thing
|
|
0:17:48
|
we can obviously change this to
|
|
0:17:51
|
91
|
|
0:17:53
|
206501
|
|
0:17:56
|
you know 5555 or 5111
|
|
0:18:02
|
as long as the Calling Search Space can get there
|
|
0:18:06
|
OK? So that´s
|
|
0:18:07
|
hunt group call coverage
|
|
0:18:10
|
as it pertains to use personal preference
|
|
0:18:12
|
and even just the specifics of
|
|
0:18:14
|
the hunt and line group
|
|
0:18:18
|
taking a look at the
|
|
0:18:20
|
client matter codes
|
|
0:18:21
|
first of all we have client matter codes and
|
|
0:18:23
|
and force authorization codes
|
|
0:18:24
|
here, so let´s go explore those
|
|
0:18:28
|
fine, we see that we don´t have
|
|
0:18:29
|
any currently
|
|
0:18:30
|
so we´ll create a simple client matter code
|
|
0:18:32
|
and we had some examples earlier
|
|
0:18:34
|
of something like a
|
|
0:18:36
|
I had 555
|
|
0:18:39
|
and the description is personal calls
|
|
0:18:44
|
and I´ll add a new one
|
|
0:18:46
|
which was let´s say
|
|
0:18:51
|
347 was client1
|
|
0:18:57
|
add another one, 643 was client2
|
|
0:19:01
|
and so on and so forth, you would add
|
|
0:19:03
|
as many clients as you needed
|
|
0:19:05
|
they´re client matter code
|
|
0:19:07
|
probably the name of them is a description
|
|
0:19:11
|
then we would go up to
|
|
0:19:14
|
our route patterns
|
|
0:19:19
|
and we would create a new route pattern
|
|
0:19:22
|
let´s say
|
|
0:19:23
|
9.@ now we don´t have any
|
|
0:19:25
|
route filters yet
|
|
0:19:27
|
So we´ll have to go specifysome of those
|
|
0:19:30
|
we´ll just keep this so that we can look at that
|
|
0:19:32
|
but we put it in a partition
|
|
0:19:34
|
whatever we wanted to put it in
|
|
0:19:38
|
So let´s say
|
|
0:19:41
|
I don´t know let´s say dial, US dial local
|
|
0:19:44
|
and the numbering plan we would select
|
|
0:19:46
|
North American numbering plan if that´s
|
|
0:19:48
|
what we´re using
|
|
0:19:50
|
that´s the one that´s installed in CUCM by default
|
|
0:19:52
|
but of course you can add
|
|
0:19:53
|
the other numbering plans
|
|
0:19:55
|
It specify the route filter eventhough
|
|
0:19:56
|
I don´t have one yet
|
|
0:19:57
|
but we will go ahead and create one
|
|
0:19:59
|
and come back here
|
|
0:20:02
|
I would then specifies the call classification
|
|
0:20:04
|
which by default
|
|
0:20:06
|
is off net
|
|
0:20:10
|
first of all, we mentioned about
|
|
0:20:11
|
overlap sending
|
|
0:20:13
|
OK? If I need to send digit at a time
|
|
0:20:15
|
from the phone
|
|
0:20:17
|
through the route pattern out to
|
|
0:20:19
|
the PSTN PRI
|
|
0:20:21
|
I would tick this on the route pattern
|
|
0:20:24
|
another place that we can allow
|
|
0:20:27
|
and notice that this grays out
|
|
0:20:30
|
plan matter code and
|
|
0:20:31
|
force authorization code, why?
|
|
0:20:33
|
because if I´m sending the digits live
|
|
0:20:35
|
real time to the PSTN
|
|
0:20:38
|
then I obviously can´t
|
|
0:20:39
|
intervene a CUCMand put in
|
|
0:20:42
|
the requirement for, you know another
|
|
0:20:46
|
tone back to the phone to
|
|
0:20:48
|
require a client matter code because
|
|
0:20:49
|
those client matter codes or
|
|
0:20:50
|
force authorization codes if I
|
|
0:20:51
|
did gather them
|
|
0:20:53
|
they would be send out to the PSTN as well
|
|
0:20:55
|
so overlap sending out of necessity
|
|
0:20:58
|
of just the
|
|
0:21:01
|
you know
|
|
0:21:02
|
way in which we describe it
|
|
0:21:04
|
out of just the functionality
|
|
0:21:06
|
disables
|
|
0:21:08
|
FAC´s and CMC´s
|
|
0:21:11
|
OK?
|
|
0:21:12
|
and if we wanted to do overlap receiving from the ISTN
|
|
0:21:15
|
we would come here to systems service parameters
|
|
0:21:18
|
and we´ll take a look at that in a minute
|
|
0:21:21
|
we would of course choose our
|
|
0:21:22
|
gateway or route list, we´ll take a look at
|
|
0:21:25
|
or probably already have actually
|
|
0:21:28
|
our route option we
|
|
0:21:30
|
can always route the pattern that´s the default
|
|
0:21:32
|
we can always block the pattern and choose
|
|
0:21:34
|
what kind of enunciator message is
|
|
0:21:35
|
played or whether no air
|
|
0:21:37
|
this played it all, it just simply
|
|
0:21:39
|
hangs up on the calling party
|
|
0:21:41
|
but anyway here we going to route the pattern
|
|
0:21:42
|
adn we´re going to choose simply
|
|
0:21:44
|
require client matter code
|
|
0:21:46
|
and that´s simply it
|
|
0:21:49
|
this is the authorization code
|
|
0:21:50
|
will not be activated
|
|
0:21:52
|
press OK because we didn´t do
|
|
0:21:54
|
force authorization code, we did client matter code
|
|
0:21:58
|
OK, please cancel and check
|
|
0:21:59
|
this is one of the default messages that comes up
|
|
0:22:01
|
by default everytime
|
|
0:22:04
|
please cancel and check FAC
|
|
0:22:05
|
if that´s what you want to activate
|
|
0:22:07
|
any updates to this route pattern
|
|
0:22:08
|
also automatically update the associated
|
|
0:22:11
|
route list
|
|
0:22:13
|
or gateway if it´s pointing directly
|
|
0:22:15
|
to a gateway, OK?
|
|
0:22:17
|
obviously I think we´ve mentioned before
|
|
0:22:19
|
we can only point directly to a gateway
|
|
0:22:22
|
if that gateway is not in a route
|
|
0:22:24
|
group and therefore used by a route list
|
|
0:22:27
|
and if we are pointing directly
|
|
0:22:29
|
to any given gateway
|
|
0:22:30
|
that gateway can not be used
|
|
0:22:32
|
by a route group or oute list so
|
|
0:22:34
|
those are
|
|
0:22:37
|
conversely, respectively
|
|
0:22:41
|
synonymous there
|
|
0:22:43
|
OK? We can always do Urgent Priority if
|
|
0:22:45
|
maybe typically for emergency services
|
|
0:22:49
|
so here we required a client matter code
|
|
0:22:53
|
in the same way, we could
|
|
0:22:56
|
we could require an
|
|
0:22:58
|
Force Authorization Code and notice
|
|
0:23:00
|
we actually can do both
|
|
0:23:03
|
again
|
|
0:23:04
|
there are going to be even rarer situations
|
|
0:23:06
|
where you would want to do both but
|
|
0:23:08
|
in the case where you did
|
|
0:23:09
|
you could have both
|
|
0:23:11
|
and they have a little bit of a different tone
|
|
0:23:14
|
as to you know, what is the actual
|
|
0:23:18
|
tones sent back to the calling phone
|
|
0:23:20
|
to indicate which type of code needs to be
|
|
0:23:23
|
dial and of course you would train your
|
|
0:23:25
|
users, you´re always going to
|
|
0:23:26
|
dial this code first and then you´ll dial this
|
|
0:23:29
|
code if you were using both but
|
|
0:23:30
|
have never seen anyone used both
|
|
0:23:32
|
OK, so let´s untick client matter
|
|
0:23:34
|
code and let´s say require
|
|
0:23:36
|
Force Authorization Code rather
|
|
0:23:40
|
so, if we want to do Force Authorization code
|
|
0:23:42
|
but we also have to provide is what is the
|
|
0:23:45
|
Authorization level for this particular pattern
|
|
0:23:47
|
if it´s a local pattern
|
|
0:23:51
|
maybe US local dialing
|
|
0:23:53
|
maybe my Authorization level is 10
|
|
0:23:56
|
I can have my Authorization level be
|
|
0:23:58
|
101 if I want
|
|
0:23:59
|
you know I can get very granular
|
|
0:24:01
|
102, 103
|
|
0:24:03
|
I can do whatever I want but
|
|
0:24:04
|
Authorization level 10
|
|
0:24:08
|
So
|
|
0:24:09
|
here I´m requiring an FAC off level 10
|
|
0:24:13
|
so I need to come create some
|
|
0:24:14
|
Force Authorization Code
|
|
0:24:16
|
of which I currently don´t have any
|
|
0:24:18
|
so if I add new
|
|
0:24:21
|
Authorization Code name let´s say US local dialing
|
|
0:24:27
|
that Authorization code
|
|
0:24:29
|
Let´s see what did we used earlier, we said
|
|
0:24:32
|
I think 55
|
|
0:24:34
|
is the code
|
|
0:24:35
|
and the Authorization level is 10
|
|
0:24:39
|
and maybe I would also add
|
|
0:24:42
|
US
|
|
0:24:45
|
national dialing
|
|
0:24:48
|
or you know long distance dialing
|
|
0:24:50
|
I want to call it that
|
|
0:24:51
|
and the code was 2179
|
|
0:24:55
|
with the level 20
|
|
0:24:58
|
OK?
|
|
0:25:00
|
so if the user
|
|
0:25:03
|
back at this route pattern
|
|
0:25:09
|
if they dialed
|
|
0:25:12
|
9
|
|
0:25:13
|
something
|
|
0:25:14
|
and the route filter which we´re going to define
|
|
0:25:16
|
match it as local
|
|
0:25:18
|
and they know that they´re dialing their code
|
|
0:25:21
|
or all of their usage
|
|
0:25:23
|
is long distance and they know that
|
|
0:25:25
|
that they always dial 2179
|
|
0:25:27
|
and we can even give
|
|
0:25:28
|
very specific codes to very specific people
|
|
0:25:31
|
OK?
|
|
0:25:32
|
So I can not just have a single code
|
|
0:25:35
|
For all users that are dialing long distance
|
|
0:25:37
|
but I could have, you know
|
|
0:25:39
|
code 1 for Tom
|
|
0:25:41
|
and he´s allowed to dial long distance
|
|
0:25:43
|
and as long as
|
|
0:25:44
|
you know it can be a unique code
|
|
0:25:46
|
but as long as it is
|
|
0:25:48
|
at the level
|
|
0:25:49
|
of 20 or higher
|
|
0:25:52
|
but not quite international high
|
|
0:25:54
|
then he will be able to dial
|
|
0:25:56
|
this because it´s a
|
|
0:25:57
|
10 level and he has 20
|
|
0:26:00
|
or you´d be able to dial
|
|
0:26:03
|
national numbers which we would obviously
|
|
0:26:05
|
create a duplicate pattern, heavy route
|
|
0:26:08
|
filter that specify national or long distance
|
|
0:26:10
|
whatever you want to call it
|
|
0:26:11
|
and had the level of 20
|
|
0:26:14
|
OK?
|
|
0:26:15
|
So let´s go take a look at the route filters
|
|
0:26:18
|
So as we go up to a route filter
|
|
0:26:24
|
we see that we don´t have any by default
|
|
0:26:27
|
so we´re going to create one based on the
|
|
0:26:28
|
North America numbering plan
|
|
0:26:30
|
OK? we can add other
|
|
0:26:33
|
numbering plans
|
|
0:26:35
|
OK, we have dial plan installer
|
|
0:26:37
|
and we do have the ability to
|
|
0:26:39
|
add additional dialing plans or numbering plans
|
|
0:26:42
|
we´re not going to do that now, we´re just going to use
|
|
0:26:44
|
the North America numbering plan
|
|
0:26:46
|
so we´ll add a new one based on
|
|
0:26:47
|
this numbering plan
|
|
0:26:49
|
and we´ll call it
|
|
0:26:51
|
US local dialing
|
|
0:26:55
|
So
|
|
0:26:57
|
here
|
|
0:26:59
|
we might say
|
|
0:27:01
|
area code exists
|
|
0:27:05
|
and
|
|
0:27:06
|
Boolean and
|
|
0:27:09
|
subscriber exists
|
|
0:27:15
|
OK, that would be enough
|
|
0:27:16
|
to specify
|
|
0:27:18
|
that this is a, I shouldn´t have say area code
|
|
0:27:22
|
let me actually edit it
|
|
0:27:24
|
and let me say
|
|
0:27:27
|
let me say area code
|
|
0:27:30
|
does not exist
|
|
0:27:34
|
rather
|
|
0:27:35
|
so area code does not exists but subscriber
|
|
0:27:37
|
exist, so this would be an example of 7 digit
|
|
0:27:40
|
dialing, I might say US
|
|
0:27:42
|
loca
|
|
0:27:44
|
7 or 10 digit dialing
|
|
0:27:50
|
now obviously if you have 7 and 10 digit
|
|
0:27:52
|
dialing or whatever country you happen
|
|
0:27:55
|
to be creating
|
|
0:27:56
|
or thinking about a dial plan in relation to
|
|
0:28:01
|
if it has multiple different
|
|
0:28:05
|
variable link number plans
|
|
0:28:08
|
or variable link dial plans
|
|
0:28:10
|
you very well may get in to
|
|
0:28:13
|
and probably will get in to over lap
|
|
0:28:14
|
dialing where you
|
|
0:28:16
|
need to have interdigit time out
|
|
0:28:18
|
but I can also
|
|
0:28:20
|
add a clause
|
|
0:28:23
|
where I maybe say
|
|
0:28:25
|
local area code exists
|
|
0:28:28
|
and I might specify what that
|
|
0:28:29
|
local area code is
|
|
0:28:31
|
or I might even say something like
|
|
0:28:34
|
area code equals
|
|
0:28:36
|
and maybe 206 for Seattle
|
|
0:28:40
|
and subscriber exists
|
|
0:28:46
|
OK?
|
|
0:28:47
|
So within this clause, this right here
|
|
0:28:56
|
this right here is a single clause
|
|
0:29:00
|
there we go
|
|
0:29:03
|
go back to my hand drawing
|
|
0:29:06
|
OK, so that´s within a single clause
|
|
0:29:09
|
and within the single clause
|
|
0:29:11
|
is the Boolean AND
|
|
0:29:13
|
both of these must be true
|
|
0:29:17
|
and here is clause number 2
|
|
0:29:20
|
but between the clauses
|
|
0:29:25
|
there is a Boolean OR
|
|
0:29:27
|
so clause 1 must be true
|
|
0:29:30
|
area code does not exist
|
|
0:29:32
|
and subscriber does exits
|
|
0:29:37
|
or
|
|
0:29:39
|
area code does exists but
|
|
0:29:40
|
equals what I happened to know
|
|
0:29:42
|
as my local area code
|
|
0:29:45
|
and subscriber exist
|
|
0:29:47
|
so I might want to change this to
|
|
0:29:49
|
something like actual not US local but
|
|
0:29:51
|
Seattle
|
|
0:29:53
|
local
|
|
0:29:54
|
7 or 10 digit dialing
|
|
0:29:58
|
and Seattle is a bad example because
|
|
0:30:00
|
it´s a big enough city that you
|
|
0:30:01
|
have to dial 10 digits
|
|
0:30:02
|
but if this were s mall enough city
|
|
0:30:04
|
and again
|
|
0:30:05
|
we really don´t want to match
|
|
0:30:06
|
7 and 10 digit dialing but
|
|
0:30:08
|
you never know though I´ve certainly had
|
|
0:30:11
|
client requirements where you do
|
|
0:30:13
|
so
|
|
0:30:14
|
you can use route filters
|
|
0:30:16
|
to break this kind of information out
|
|
0:30:18
|
we can also just do
|
|
0:30:20
|
the other way which is
|
|
0:30:21
|
obviously what will spend most of our
|
|
0:30:24
|
discussion talking about which is
|
|
0:30:28
|
throughout all the videos of learning
|
|
0:30:30
|
for unified communications which is just
|
|
0:30:32
|
specifying the entire
|
|
0:30:36
|
the entire actual pattern in the pattern field
|
|
0:30:40
|
you´ll find that route filters can
|
|
0:30:43
|
seemed to be really nice and they are
|
|
0:30:45
|
they certainly have the ability
|
|
0:30:48
|
I close the wrong
|
|
0:30:50
|
piece
|
|
0:30:51
|
route filters have the ability to
|
|
0:30:54
|
be very nice
|
|
0:30:56
|
in some cases but they also can
|
|
0:30:59
|
after you´ve actually done
|
|
0:31:00
|
a (31:03) deployment with them
|
|
0:31:01
|
you can see that they can sometimes be
|
|
0:31:04
|
a bit of a pain
|
|
0:31:05
|
it just depends on
|
|
0:31:07
|
you know what you would like to
|
|
0:31:09
|
really do more
|
|
0:31:10
|
and it doesn´t look like I change this
|
|
0:31:12
|
there we go
|
|
0:31:14
|
Seattle
|
|
0:31:21
|
OK
|
|
0:31:22
|
one of the things is that all of
|
|
0:31:24
|
this information for the clause
|
|
0:31:26
|
is stored within a single sequel
|
|
0:31:29
|
cell
|
|
0:31:32
|
inside of a table and so
|
|
0:31:34
|
there´s a limit to the number of
|
|
0:31:36
|
characters that can actually be used
|
|
0:31:38
|
so sometimes
|
|
0:31:39
|
if you´re trying to break out
|
|
0:31:40
|
let´s say in the US we have
|
|
0:31:42
|
what are called NPA NXX
|
|
0:31:45
|
and so
|
|
0:31:46
|
an NPA would be
|
|
0:31:48
|
you´re basically your area or city code
|
|
0:31:51
|
and that´s going to be XXX
|
|
0:31:53
|
dash
|
|
0:31:54
|
and then XXX
|
|
0:31:56
|
it´s going to be called
|
|
0:31:57
|
so this is what´s referred to as your NPA
|
|
0:32:02
|
and this is what´s referred to as your NXX
|
|
0:32:07
|
or your prefixed
|
|
0:32:08
|
and then come the actual subscriber
|
|
0:32:11
|
or also actually referred to
|
|
0:32:13
|
in the
|
|
0:32:16
|
in the
|
|
0:32:17
|
clause domain here
|
|
0:32:20
|
of route filters
|
|
0:32:21
|
as your office code
|
|
0:32:24
|
the office code
|
|
0:32:26
|
would actually be
|
|
0:32:28
|
your NXX and then the subscriber
|
|
0:32:31
|
would really be the last four digit
|
|
0:32:33
|
but
|
|
0:32:34
|
so we probably should say area code
|
|
0:32:36
|
and office code and subscriber exist but
|
|
0:32:39
|
you know
|
|
0:32:41
|
so
|
|
0:32:44
|
your subscriber digits
|
|
0:32:47
|
OK, so
|
|
0:32:49
|
in the US a lot of times, we have
|
|
0:32:51
|
as I have I will mention
|
|
0:32:53
|
which is not necessarily
|
|
0:32:55
|
in fact very rarely the case in
|
|
0:32:57
|
many the other countries that I´ve worked with
|
|
0:32:59
|
we have over laying
|
|
0:33:01
|
city codes or over the effect we don´t
|
|
0:33:02
|
call them city codes, at all
|
|
0:33:04
|
we call them area codes because they can
|
|
0:33:06
|
define an area within a city
|
|
0:33:08
|
so for instance 206 only defines
|
|
0:33:10
|
the portion of Seattle
|
|
0:33:11
|
and there are other
|
|
0:33:13
|
area codes that are use as well
|
|
0:33:16
|
and when we have to break this out
|
|
0:33:18
|
but we call them breaking out NPA NXX´s
|
|
0:33:21
|
and so
|
|
0:33:22
|
if you´ve ever been task with breaking out
|
|
0:33:24
|
NPA NXX´s
|
|
0:33:27
|
by usage of route filters
|
|
0:33:30
|
you can quickly find
|
|
0:33:33
|
that you will quickly run out of
|
|
0:33:36
|
actual character space
|
|
0:33:38
|
becasue you´ll have so many
|
|
0:33:40
|
clauses
|
|
0:33:41
|
you know area code equals
|
|
0:33:43
|
or area code equals
|
|
0:33:45
|
or area code equals
|
|
0:33:48
|
but within the clauses area code equals this
|
|
0:33:50
|
and office code equals this
|
|
0:33:53
|
or area code equals this and
|
|
0:33:55
|
office code equals this or area equals this
|
|
0:33:58
|
office code equals this
|
|
0:33:59
|
and sometimes you can actually quickly
|
|
0:34:00
|
run out depending on how many
|
|
0:34:02
|
NXX´s that second set of three X´s
|
|
0:34:05
|
or second set of 3 digits
|
|
0:34:07
|
that you have that you need to break out
|
|
0:34:09
|
to deal with if you have to
|
|
0:34:11
|
dial 7 or 10 digits
|
|
0:34:13
|
and this is actually more so in the cities that are
|
|
0:34:15
|
small that are becoming bigger
|
|
0:34:17
|
that you run into this problem
|
|
0:34:18
|
but
|
|
0:34:19
|
you can find that you will actually run out
|
|
0:34:21
|
of the amount of characters allowed
|
|
0:34:23
|
in a single database
|
|
0:34:25
|
cell
|
|
0:34:26
|
and so thefore you have to create
|
|
0:34:27
|
multiple route filters
|
|
0:34:29
|
to deal with that NPA NXX over lay
|
|
0:34:32
|
and you assign those multiple route filters to
|
|
0:34:34
|
multiple 9.@ route patterns
|
|
0:34:37
|
like we´re going to go back and assign this
|
|
0:34:40
|
route filter
|
|
0:34:44
|
to our 9.@ route pattern
|
|
0:34:47
|
and the way you deal with that is
|
|
0:34:49
|
you simply create copy of your 9.@
|
|
0:34:53
|
and you put it in a different partition
|
|
0:34:55
|
can´t put it the same that
|
|
0:34:56
|
would be shared line and you can´t
|
|
0:34:57
|
have that for route pattern
|
|
0:34:59
|
so you put it in a different partition
|
|
0:35:01
|
and you give both of those
|
|
0:35:03
|
route patterns in the two different partitions
|
|
0:35:05
|
the two different
|
|
0:35:07
|
route filters that you´ve created
|
|
0:35:08
|
that really create the aggregate overall
|
|
0:35:10
|
picture that you want
|
|
0:35:11
|
and then you just be sure that you put
|
|
0:35:12
|
both partitions
|
|
0:35:14
|
in the Calling Search Space
|
|
0:35:16
|
doesn´t really matter which one is higher because
|
|
0:35:18
|
the route filter will differentiate between them
|
|
0:35:22
|
OK? So the 9.@ or @ symbol
|
|
0:35:24
|
@ symbol specifies a numbering plan
|
|
0:35:26
|
of some sort
|
|
0:35:27
|
in North America by default
|
|
0:35:30
|
installed but you can install others
|
|
0:35:33
|
and
|
|
0:35:34
|
presents the necessity
|
|
0:35:35
|
of having a route filter in order to
|
|
0:35:39
|
enumerate what that
|
|
0:35:40
|
@ symbol actually stands for
|
|
0:35:47
|
so we did mention about the
|
|
0:35:49
|
moving on, we mentioned about
|
|
0:35:51
|
the overlap sending, notice
|
|
0:35:52
|
it´s grayed out because I have require
|
|
0:35:54
|
Force Authorization code
|
|
0:35:55
|
soon as I unticked that it
|
|
0:35:56
|
becomes available
|
|
0:35:58
|
we talked about the call classification
|
|
0:36:01
|
on or off net which can be specify
|
|
0:36:03
|
by at the pattern level
|
|
0:36:04
|
also if I have a gateway
|
|
0:36:07
|
or trunk
|
|
0:36:08
|
let´s say I have a gateway
|
|
0:36:10
|
and
|
|
0:36:11
|
I actually have one already with
|
|
0:36:18
|
lwt´s just use
|
|
0:36:19
|
I have a few gateways here
|
|
0:36:20
|
let´s just use a
|
|
0:36:22
|
PRI that I already have
|
|
0:36:26
|
on a gateway
|
|
0:36:27
|
I also have the ability to specify
|
|
0:36:30
|
whether the
|
|
0:36:32
|
information
|
|
0:36:33
|
the call should be
|
|
0:36:35
|
classified as off net or on net
|
|
0:36:37
|
if I used system default
|
|
0:36:39
|
what that means is
|
|
0:36:40
|
go back to where
|
|
0:36:42
|
the classification will set earlier
|
|
0:36:44
|
so in another words
|
|
0:36:45
|
everything has to go through a route pattern
|
|
0:36:46
|
in order to get to a gateway
|
|
0:36:48
|
or trunk
|
|
0:36:50
|
whether it goes directly or
|
|
0:36:51
|
whether it goes to a route list route group
|
|
0:36:54
|
it has to go
|
|
0:36:56
|
initially through a route pattern to get
|
|
0:36:57
|
to a gateway or trunk
|
|
0:36:59
|
so, if I set
|
|
0:37:01
|
the call classification of the route pattern
|
|
0:37:04
|
then it´s already been set
|
|
0:37:05
|
so use the system default that is
|
|
0:37:07
|
used whatever it was already set as
|
|
0:37:10
|
However, I also have the ability to
|
|
0:37:14
|
and that can be very useful because
|
|
0:37:16
|
there might be times when I want to have certain patterns
|
|
0:37:19
|
make it look like as if
|
|
0:37:21
|
you know this is an on net call
|
|
0:37:23
|
or keeping it on net
|
|
0:37:24
|
eventhough it actually is going off
|
|
0:37:26
|
net to the PSTN, that´s not normal
|
|
0:37:28
|
but there are certain
|
|
0:37:29
|
search situations where you might want to do that
|
|
0:37:33
|
call classification on net or off net is
|
|
0:37:35
|
recorded in the call detail records
|
|
0:37:39
|
and the call management records it´s also
|
|
0:37:41
|
useful for things like
|
|
0:37:43
|
preventing toll fraud
|
|
0:37:45
|
there are service
|
|
0:37:47
|
parameters that deal with
|
|
0:37:48
|
off net to off net transfer blocking
|
|
0:37:52
|
so another words if a call comes from
|
|
0:37:54
|
or in through a gateway
|
|
0:37:56
|
and then
|
|
0:37:58
|
based on the DNIS digits
|
|
0:38:00
|
ultimately routes back out through a
|
|
0:38:03
|
gateway to the PSTN
|
|
0:38:06
|
if those are classified
|
|
0:38:08
|
as off net and off net
|
|
0:38:09
|
that would be an off net to off net
|
|
0:38:12
|
reroute or forward
|
|
0:38:14
|
or a if a user did it, a transfer
|
|
0:38:17
|
and we have the abillity in systems service
|
|
0:38:19
|
parameters to block off net to off net transfers
|
|
0:38:22
|
we also have the ability to block
|
|
0:38:24
|
conference calls
|
|
0:38:26
|
when the
|
|
0:38:29
|
when there are no more
|
|
0:38:31
|
on net parties
|
|
0:38:33
|
connected so for instance
|
|
0:38:35
|
maybe I´m trying to be devious and
|
|
0:38:38
|
I want my wife
|
|
0:38:41
|
I wouldn´t do this, but maybe I want my wife
|
|
0:38:43
|
to be able to call her friends
|
|
0:38:45
|
in UK because she lived
|
|
0:38:47
|
there for a couple of years
|
|
0:38:50
|
and so I want to bill it to my company´s dime
|
|
0:38:54
|
because I´m malicious or you know
|
|
0:38:56
|
just not pay for it
|
|
0:38:58
|
and so that´s
|
|
0:39:00
|
equivalent of toll fraud
|
|
0:39:01
|
so I call up my wife on her mobile
|
|
0:39:04
|
and then I also call up
|
|
0:39:06
|
her friend from the UK
|
|
0:39:09
|
and they´re talking
|
|
0:39:11
|
and I
|
|
0:39:12
|
because I conference the three in
|
|
0:39:14
|
I do an add hawk conference
|
|
0:39:16
|
and I call her you know
|
|
0:39:17
|
call her friend up from the UK and
|
|
0:39:19
|
hit conference, so they´re all conference together
|
|
0:39:20
|
and then I leave the conference
|
|
0:39:23
|
OK? So I can go to systems service
|
|
0:39:24
|
parameters and we´ll just look
|
|
0:39:25
|
here real quick
|
|
0:39:27
|
either pub or sub
|
|
0:39:29
|
under the call manager service
|
|
0:39:33
|
and we´ll take a look
|
|
0:39:35
|
there´s always contact sensitive
|
|
0:39:37
|
help based on the field name if you
|
|
0:39:39
|
click on anyone of these field names
|
|
0:39:42
|
they bring up contact sensitive help
|
|
0:39:43
|
You can always do a Ctrl F
|
|
0:39:45
|
to find information within the page
|
|
0:39:48
|
but you´re only searching for
|
|
0:39:49
|
the words that appear on this page
|
|
0:39:51
|
nothing in the html textbox
|
|
0:39:54
|
or drop downs
|
|
0:39:55
|
OK?
|
|
0:39:57
|
unless it happens to be the default
|
|
0:39:59
|
But if I click on one of these contacts sensitive help
|
|
0:40:04
|
names, if I do Ctrl F find here,
|
|
0:40:09
|
I'm actually able to find not only the default,
|
|
0:40:13
|
but minimum maximum, what units
|
|
0:40:16
|
and also not just the name of the field, but also the definition of
|
|
0:40:20
|
it so I can typically find a lot faster,
|
|
0:40:24
|
or more effectively what it is I'm looking for. So if I do Offnet
|
|
0:40:30
|
maybe it's Offnet. Alright, let's do Block
|
|
0:40:36
|
There we go, so I had to hit enter three times, block,
|
|
0:40:40
|
OK it was Offnet without any dash or space
|
|
0:40:44
|
so block Offnet to Offnet Transfer, the default is false
|
|
0:40:47
|
so it doesn't block it, but I can turn that to true.
|
|
0:40:52
|
Ok, so let's search for Offnet.
|
|
0:40:57
|
And
|
|
0:40:58
|
here we go, use Original Call Classification for transferred calls
|
|
0:41:02
|
here we go drop Adhoc conference, so I can either drop at never
|
|
0:41:07
|
when the conference controller, the person that set up the conference leaves
|
|
0:41:11
|
or when no Onnet parties remain in the conference to block
|
|
0:41:16
|
the default is, don't ever drop it, but this is a very
|
|
0:41:20
|
this is a very normal thing that I change this to for most of my consulting
|
|
0:41:26
|
clients because they don't want
|
|
0:41:30
|
this kind of toll fraud to occur
|
|
0:41:33
|
so there are good reasons for that or having the OffNet Call Classification
|
|
0:41:38
|
besides the call detail records which are certainly very useful themselves.
|
|
0:41:44
|
Another thing we dealth with was the overlap sending,
|
|
0:41:48
|
so there's three main places we find it, first of all
|
|
0:41:50
|
always look under the main section that you're under
|
|
0:41:53
|
here we're under a cluster wide parameter, so if I change it one server,
|
|
0:41:56
|
it changes it on all.
|
|
0:41:58
|
And it's for devices specifically PRI and MGCP gateway devices.
|
|
0:42:04
|
So first of all I can discard non-inband
|
|
0:42:08
|
progress in overlap sending,
|
|
0:42:13
|
so it determines whether the progress message received
|
|
0:42:17
|
in an overlap sending state the PRI is sending me one digit at a time
|
|
0:42:22
|
without inband information, is discarded or reported by the call control
|
|
0:42:27
|
via PRI or Q.SIG, Q.SIG is a form
|
|
0:42:32
|
of a tunneling over top of PRI, a lot more enhancement to
|
|
0:42:38
|
PRI but it's typically used, in fact almost exclusively used through
|
|
0:42:43
|
integrations with other PBXs, not out to the PSTN.
|
|
0:42:48
|
OK? So overlap there
|
|
0:42:53
|
there's also the T304 timer
|
|
0:42:56
|
OK, for ISTN layer 3 for the user overlap sending
|
|
0:43:00
|
this is basically the T302 timer
|
|
0:43:04
|
of course is the interdigit timeout
|
|
0:43:07
|
between phone keypad key presses
|
|
0:43:12
|
the default is 15,000 milliseconds or 15 seconds
|
|
0:43:16
|
the minimum I can have for interdigit timeout is three seconds
|
|
0:43:20
|
and the maximum is 75 seconds.
|
|
0:43:23
|
T304 is almost like an interdigit timeout but specifically for overlap sending
|
|
0:43:34
|
OK? We already looked at this one,
|
|
0:43:39
|
and then there's also the overlap receiving flag for PRIs.
|
|
0:43:43
|
So is overlap receiving from a PSTN PRI supported? The default is true.
|
|
0:43:50
|
It is supported.
|
|
0:43:53
|
OK, and then there's also the H225 T302
|
|
0:43:58
|
timer.
|
|
0:44:00
|
And H225T304, so these are specific
|
|
0:44:04
|
if we scroll up to the section this was under
|
|
0:44:08
|
these are specific not just to device which is what is the T302
|
|
0:44:12
|
and T304 timers were set at.
|
|
0:44:15
|
but to device H323, so device deals with Skinny and SIP phones
|
|
0:44:21
|
and device H323 deals with H323
|
|
0:44:25
|
gateways or trunks.
|
|
0:44:30
|
OK, so we have the ability to do that there and also,
|
|
0:44:34
|
If we're actually out at a IOS gateway,
|
|
0:44:38
|
if I jump in into global config mode,
|
|
0:44:40
|
and go to interface, let's say serial 00023 which is my D channel
|
|
0:44:48
|
I can specify things like ISTN, specify a lot of information obviously
|
|
0:44:54
|
but ISTN let's say overlap receiving
|
|
0:44:58
|
so simply specify whether it supports it or not, enter,
|
|
0:45:03
|
what the terminating character is and what the T302 timer is,
|
|
0:45:08
|
and currently I'm using a
|
|
0:45:11
|
PRINI or national switch and it tells me that
|
|
0:45:14
|
overlap receiving is, I'm using a PRI IDSS
|
|
0:45:19
|
and it's not supported on this switch type, so I would have to,
|
|
0:45:22
|
switch over to a switch type or convert my ISDN switch type
|
|
0:45:27
|
to one that is supported.
|
|
0:45:31
|
OK, I could also deal with things such as ISDN sending complete
|
|
0:45:37
|
And this is something common in other countries where the
|
|
0:45:41
|
there's actually a sending complete indicator
|
|
0:45:45
|
sent in the outgoing setu-up message,
|
|
0:45:47
|
to let them know if we've sent all the digits to the PSTN.
|
|
0:45:51
|
and typically deals with overlap sending and receiving.
|
|
0:45:56
|
OK? And one other thing I wanted to look back in CUCM,
|
|
0:46:00
|
really two other things, one was a SIP route pattern,
|
|
0:46:04
|
something that we really didn't talk about too much.
|
|
0:46:06
|
And one was the SIP dial rule, so we talked about the SIP dial rules.
|
|
0:46:11
|
Let's go ahead and take a look at
|
|
0:46:13
|
these and we probably don't have any created yet,
|
|
0:46:16
|
so if again these are for the SIP phones,
|
|
0:46:20
|
if we wanted to basically create a dial plan that
|
|
0:46:23
|
could be sent down to a phone, let's say in the case of a 7960 or 40
|
|
0:46:30
|
so that they, since they don't support KPML,
|
|
0:46:34
|
so that we don't have to wait for interdigit timeout
|
|
0:46:37
|
or even just for newer phones that
|
|
0:46:41
|
maybe we want to assume the need for
|
|
0:46:45
|
interdigit time out with missed or received calls
|
|
0:46:48
|
really with returning a call through call history so missed receive calls
|
|
0:46:54
|
especially when they begin with a plus
|
|
0:46:57
|
and we'll talk about those actual types of patterns later but
|
|
0:47:01
|
you know we're returning a call to a plus and so therefore the
|
|
0:47:04
|
translation or route pattern that has that matcheable plus character,
|
|
0:47:09
|
has urgent priority ticked and we
|
|
0:47:14
|
are sending from a SIP KPML phone, so because of that
|
|
0:47:20
|
we want to issue that need so
|
|
0:47:22
|
first of all there's two different types of dial patterns and they affect
|
|
0:47:26
|
how we input the actual values or pattern matching
|
|
0:47:33
|
in the dial rules that we're gonna create
|
|
0:47:36
|
so unless you have a 7905 or 7912
|
|
0:47:40
|
then all of the others are gonna be used here, 7940 or 7960
|
|
0:47:44
|
or other which is really everything else
|
|
0:47:47
|
OK? So almost always you'll be wanting
|
|
0:47:49
|
these unless you happen to have these two phones.
|
|
0:47:52
|
So we'll choose next,
|
|
0:47:54
|
We'll get a name, maybe call it something like avoid
|
|
0:47:58
|
call history return timeout for instance.
|
|
0:48:08
|
And we can have multiple patterns within this rule set
|
|
0:48:15
|
so let's say first all we want to avoid,
|
|
0:48:19
|
call history return
|
|
0:48:24
|
and so we want to add pattern
|
|
0:48:27
|
you can add private line automatic private ring down,
|
|
0:48:29
|
but here we'r ejust gonna do add pattern
|
|
0:48:34
|
and this would be PLAR for a SIP phone, we
|
|
0:48:39
|
know how to do PLAR for a Skinny phone
|
|
0:48:42
|
I believe we've talked about that, if not it's as simple as
|
|
0:48:44
|
creating a translation pattern with no pattern.
|
|
0:48:49
|
OK, if i create, just on a quick side, if I create a translation pattern,
|
|
0:48:52
|
that has no pattern here, but it has a pattern that actually matches
|
|
0:48:56
|
whatever calling search space, and hopefully I have limited this
|
|
0:48:59
|
calling search space to only a couple phones, maybe
|
|
0:49:03
|
shipping dock, you know loading phone or a
|
|
0:49:07
|
elevator type phone, a lift phone.
|
|
0:49:10
|
so that whenever they go off hook, their calling search space matches
|
|
0:49:14
|
this partition so you don't want every phone matching it.
|
|
0:49:16
|
And they don't enter any digits, so it immediately matches everything
|
|
0:49:20
|
which is nothing and immediately routes the call
|
|
0:49:24
|
to whatever called party mask you say, 2001.
|
|
0:49:28
|
OK, that's your private line automatic ring down for Skinny phones.
|
|
0:49:34
|
But back to SIP dial rules,
|
|
0:49:38
|
I knew this was gonna happen
|
|
0:49:41
|
as soon as I open another tab, there we go,
|
|
0:49:44
|
OK, so now I've got my individual pattern
|
|
0:49:49
|
or button or timeout or user but
|
|
0:49:51
|
we'll probably use pattern and timeout the most, so maybe my pattern
|
|
0:49:56
|
I want it to match, and actually before we do any values here
|
|
0:49:59
|
let's go up to help for this page,
|
|
0:50:02
|
to see specfically what pattern type matching I can use
|
|
0:50:09
|
so this will open up to help which really is
|
|
0:50:14
|
the administration guide and we see that these phones all use
|
|
0:50:20
|
KPML 49617071 use the 794060 other dial rules.
|
|
0:50:27
|
OK, the same apply for the newer phones as well
|
|
0:50:33
|
and here if we come down to the
|
|
0:50:37
|
values, let's see where is the, there's a specific table
|
|
0:50:44
|
there we go, pattern formats, so see the pattern formats topic
|
|
0:50:48
|
so we'll click there.
|
|
0:50:49
|
A period, remember this is going to be different than a translation
|
|
0:50:53
|
pattern or route pattern or a DN pattern
|
|
0:50:55
|
how you would enter these normally in CUCM, it's going to be different.
|
|
0:50:59
|
Why, because it's following the RFC
|
|
0:51:02
|
or these type of downloadable
|
|
0:51:05
|
configurations or dial plans into the phone.
|
|
0:51:09
|
Remember that SIP is an intelligent end point protocol whereas Skinny
|
|
0:51:13
|
client server protocol. Skinny relies on having the server present.
|
|
0:51:19
|
SIP doesn't rely on that. KPML sort of makes it
|
|
0:51:22
|
almost like a Skinny phone in that regard digit by digit.
|
|
0:51:26
|
But otherwise it has the ability to have a completely independent or
|
|
0:51:30
|
self aware dial plan and that's what we're doing, so period
|
|
0:51:35
|
or dot matches any single digit, just like in IOS.
|
|
0:51:39
|
Hyphen means more digits can be entered.
|
|
0:51:43
|
OK, so if this character is needed, it must apply at the
|
|
0:51:46
|
end of a rule, this is basically specifying interdigit timeout
|
|
0:51:50
|
or in IOS this would be a T
|
|
0:51:53
|
or timeout so wait for additional digits so 1408T5.
|
|
0:52:00
|
OK, we'll get to T in a moment, by the way this says T,
|
|
0:52:03
|
set the T to second so it's saying 1408
|
|
0:52:09
|
wait for five seconds for interdigit time out and
|
|
0:52:13
|
dash says more characters can be entered.
|
|
0:52:16
|
But it's showing you this is illegal because
|
|
0:52:18
|
the dash has to appear at the end.
|
|
0:52:20
|
So this would be a interdigit timeout,
|
|
0:52:24
|
dash allowing more characters for the time out value of five seconds
|
|
0:52:30
|
OK? The pound or hash key,
|
|
0:52:34
|
really the octothrop to be technical, acts as a terminating key
|
|
0:52:40
|
but this termination can be applied only after matching
|
|
0:52:44
|
this hit, so for instance if we want to use
|
|
0:52:49
|
# as an actual dialable character, then we simply use #,
|
|
0:52:53
|
if we want to use asterisk as a DTMF dialable character
|
|
0:52:56
|
because they're obviously on our keypad # and *,
|
|
0:52:59
|
we can use both just by specifying # or *.
|
|
0:53:08
|
Actually * is one or more characters, so you can't use that.
|
|
0:53:12
|
I apologize and by the way I think I was looking at 7905 or 7912 so
|
|
0:53:18
|
that is not what we would do, I think that is
|
|
0:53:23
|
actually you don't have to do anything, I think that's the one difference.
|
|
0:53:28
|
between the 7905/12 and the other phones.
|
|
0:53:34
|
So my apologies, let's a look more at this, but the # acts
|
|
0:53:39
|
as a terminating key, so another if I do want to terminate interdigit timeout
|
|
0:53:42
|
which I don't have to specify, like I just said you did.
|
|
0:53:45
|
On the newer phones at least that is, in the older phones you do.
|
|
0:53:51
|
Then I have to do the character, >#.
|
|
0:53:56
|
If I wanted * to be the terminating, the interdigit
|
|
0:54:00
|
timeout terminating character, I would do greater >*.
|
|
0:54:05
|
OK.
|
|
0:54:06
|
If I just do an *, that matches one or more characters, it's a wild card.
|
|
0:54:11
|
If I want to actually dial the *, then I escape it with a \.
|
|
0:54:17
|
OK, just like you would do in normal programming languages,
|
|
0:54:20
|
comma can generate secondary dial tone.
|
|
0:54:24
|
So you know, if you're configuring this, just take a look.
|
|
0:54:28
|
So I want to specify a plus,
|
|
0:54:32
|
which is actually not specified over here
|
|
0:54:36
|
normally it would be part of a regular expression
|
|
0:54:39
|
and we would have to escape it.
|
|
0:54:41
|
But in this particular case, SIP dial rules, I don't have to.
|
|
0:54:44
|
And I want any other character.
|
|
0:54:47
|
So if it matches the string beginning with a plus in any other characters,
|
|
0:54:51
|
then I want to immediately go ahead and forward that
|
|
0:54:55
|
so I've matched a pattern, once I match a pattern,
|
|
0:54:58
|
it will forward it to CUCM, so there we go.
|
|
0:55:02
|
Now I'm going to say all other calls,
|
|
0:55:06
|
so I'm specifying my second rule,
|
|
0:55:09
|
within my overall rule set, this is my rule set.
|
|
0:55:14
|
So notice what happens here.
|
|
0:55:16
|
Here is my first pattern which is a void call history return time out
|
|
0:55:21
|
or maybe a timeout.
|
|
0:55:29
|
And it shows the pattern, it always adds another pattern field
|
|
0:55:36
|
or another field that you can choose what to be,
|
|
0:55:39
|
maybe I would say timeout 0.
|
|
0:55:42
|
So send it immediately,
|
|
0:55:46
|
maybe I wouldn't, I think actually for this one I won't do anything
|
|
0:55:49
|
save or actually
|
|
0:55:52
|
net update failed because I did it wrong, let me go back to it.
|
|
0:55:55
|
What I should rather do is delete this particular parameter,
|
|
0:55:58
|
if I say delete the pattern, that's deleting, let me just show you here.
|
|
0:56:04
|
That was deleting this entire pattern,
|
|
0:56:10
|
within the rule set.
|
|
0:56:13
|
OK, so that's deleting all that, it's always gonna give you
|
|
0:56:16
|
extra new blank space partly as a
|
|
0:56:19
|
visual separator and partly just in case you want to put any
|
|
0:56:22
|
additional parameters in, which you don't fill it in, obviously if you
|
|
0:56:26
|
if you do fill it in, it creates another one.
|
|
0:56:28
|
OK, but if I just wanted to create one of the individual parametersm,
|
|
0:56:33
|
within that rule, within the overall rule set,
|
|
0:56:38
|
then I will not click delete pattern, I will click delete parameter, say save,
|
|
0:56:43
|
and I still have this empty pattern but
|
|
0:56:47
|
I just have my primary pattern plus
|
|
0:56:50
|
and then any additional characters, go ahead and route that
|
|
0:56:53
|
for all other calls, I want
|
|
0:56:57
|
*, in fact I would not want timeout on that last one, OK?
|
|
0:57:03
|
Trust me, when returning plus missed calls, you do not want that.
|
|
0:57:08
|
Here
|
|
0:57:09
|
what I do want is to say save, I can actaully just click
|
|
0:57:12
|
add new parameter or save,
|
|
0:57:14
|
and I do want timeout 0.
|
|
0:57:18
|
OK, so look what it did here, at this point,
|
|
0:57:22
|
avoid call history return was on the top,
|
|
0:57:25
|
and it brought it down to the bottom,
|
|
0:57:27
|
and now all other calls is on the top
|
|
0:57:32
|
for whatever reason, so all other calls, timeout 0.
|
|
0:57:36
|
This is what I actually want, I press save.
|
|
0:57:40
|
OK so all other calls,
|
|
0:57:43
|
the pattern is just anything,
|
|
0:57:46
|
the timeout I want to be 0,
|
|
0:57:49
|
so in other words, any other calls,
|
|
0:57:51
|
I want to begin sending them immediately to CUCM,
|
|
0:57:55
|
and it will basically use KPML for all regular calls.
|
|
0:58:00
|
and KPML is a very nice thing,
|
|
0:58:01
|
so I want to use KPML for all calls except
|
|
0:58:04
|
for call history, you know returned calls
|
|
0:58:10
|
that begin with a plus.
|
|
0:58:12
|
So once I've created this rule, save everything
|
|
0:58:16
|
then I would come over to my devices
|
|
0:58:20
|
that we're using the SIP protocol
|
|
0:58:23
|
such as, let's see this 9971 that I have here,
|
|
0:58:28
|
and I would scroll down
|
|
0:58:32
|
to the protocol specific information section
|
|
0:58:35
|
and the SIP dial rules and I would apply those SIP dial rules.
|
|
0:58:40
|
I would hit the apply config button and that would apply the SIP dial rule.
|
|
0:58:49
|
So one other thing deals with SIP route patterns
|
|
0:58:52
|
these are very simple
|
|
0:58:54
|
you've probably seen or heard, talked about the ability to dial
|
|
0:58:59
|
and very common from applications, obviously not so
|
|
0:59:04
|
easy currently from dial pads, although this will actually become
|
|
0:59:08
|
more and more possible but
|
|
0:59:11
|
from third party applications or even Cisco applications,
|
|
0:59:14
|
that I should say software web-based apllications.
|
|
0:59:19
|
You have the ability to route to a domain, so let's say
|
|
0:59:25
|
I can either use domain or IP address routing,
|
|
0:59:27
|
but let's say if it's a domain, I say
|
|
0:59:31
|
maybe ine.com
|
|
0:59:34
|
maybe it's Branch2
|
|
0:59:38
|
.ine.com, so essentially anything the domain name
|
|
0:59:41
|
that comes after the @
|
|
0:59:43
|
So I would route to
|
|
0:59:45
|
msnow@branch2.ine.com
|
|
0:59:49
|
or maybe even just msnow@ine.com
|
|
0:59:52
|
and I'm going to, I need to have a partition of course,
|
|
0:59:55
|
I'm going to send that off to a particular trunk.
|
|
1:00:00
|
OK, maybe it's a trunk
|
|
1:00:03
|
connected to my Branch2 site or something like that
|
|
1:00:06
|
but whatever SIP trunk that I have set up,
|
|
1:00:09
|
and on the other end of that SIP trunk is something
|
|
1:00:11
|
that knows how to route at ine.com
|
|
1:00:16
|
whether I'm sending to msnow@ine.com and there's a resolver
|
|
1:00:20
|
that can say, msnow is
|
|
1:00:22
|
DN4327
|
|
1:00:25
|
or even if I just send it to 4327@ine.com
|
|
1:00:29
|
as long as 4372 can be
|
|
1:00:31
|
either resolved or routed at the other end of that SIP trunk
|
|
1:00:35
|
then I can go ahead and have that as a routable trunk.
|
|
1:00:39
|
or routable pattern so that I can do
|
|
1:00:42
|
domain type dialing. OK? This is only for the SIP protocol.
|
|
1:00:52
|
So let's just go ahead and test these, Forced Authorization Code and
|
|
1:00:56
|
Client Matter Codes briefly, I have gone ahead and brought up
|
|
1:00:59
|
Corporate Headquarter Phone1 and I've actually gone ahead
|
|
1:01:03
|
and created a calling search space,
|
|
1:01:07
|
called test that I have applied,
|
|
1:01:10
|
to this phone and there's no calling search space on the line,
|
|
1:01:14
|
and the calling search space test only contains the partition
|
|
1:01:20
|
partition PSTN, Monday through Friday, 9:00 to 17:00
|
|
1:01:26
|
and actually this is now Seattle.
|
|
1:01:30
|
Local dialing only,
|
|
1:01:33
|
because the route filter that we applied,
|
|
1:01:39
|
canotains only Seattle dialing, so I changed the
|
|
1:01:42
|
partition to something that is currently active,
|
|
1:01:46
|
actually let's change it to partition
|
|
1:01:49
|
EST so
|
|
1:01:51
|
Eastern Standard Time which is not during those hours,
|
|
1:01:55
|
even though it is Monday through Friday.
|
|
1:01:57
|
And I brought up this phone, let's just go ahead and dial,
|
|
1:02:00
|
first of all 911.
|
|
1:02:02
|
Actually let me back up even a little bit more,
|
|
1:02:04
|
there is nothing else in this partition.
|
|
1:02:06
|
OK, this is the pattern that exists in the
|
|
1:02:09
|
CUCM configuration in this partition.
|
|
1:02:12
|
And
|
|
1:02:16
|
Let's to the calling search space,
|
|
1:02:21
|
for test and let's actually add both of those partitions that
|
|
1:02:25
|
that we created, those time of day partitions.
|
|
1:02:29
|
So it doesn't really matter which one we put on top,
|
|
1:02:31
|
because remember they don't have any overlaps in time period.
|
|
1:02:36
|
Ok, so back at the route pattern the
|
|
1:02:42
|
There's nothing else in this partition,
|
|
1:02:45
|
EST and there's nothing else in the partition for PST,
|
|
1:02:49
|
Monday through Friday 9:00 to 17:00 or this one 8:00 to 12:00.
|
|
1:02:52
|
OK, this one is not active right now because this one is currently
|
|
1:02:56
|
let's say eastern time it is 15:21.
|
|
1:03:00
|
Fifteen hundred hours, twenty one minutes.
|
|
1:03:03
|
So first off, even if this partition was
|
|
1:03:08
|
active or visible,
|
|
1:03:11
|
this 9.@ specifies 9
|
|
1:03:16
|
which provides outside dial tone and then @
|
|
1:03:20
|
specifies the numbering plan and route filter
|
|
1:03:23
|
and this only as we looked at specifies Seatte 7 or 10 digit dialing.
|
|
1:03:28
|
So what we're gonna find is that we would not
|
|
1:03:31
|
be able to dial something like 911,
|
|
1:03:34
|
even if this partition we're active, but currently
|
|
1:03:37
|
the partition being active,
|
|
1:03:39
|
not active, we can't even dial Seattle 7 or 10 digit dialing
|
|
1:03:46
|
OK and actually my PSTN is not set-up for 7 digit dialing,
|
|
1:03:48
|
but we can test 10 digit.
|
|
1:03:50
|
So we'll go ahead test 911
|
|
1:03:55
|
and we should get pretty much
|
|
1:03:59
|
make sure the volume is up, we should get
|
|
1:04:03
|
reorder tone right now.
|
|
1:04:07
|
Or the enunciator telling us that your call cannot be completed as dialed.
|
|
1:04:13
|
And eventually reorder tone, OK so we can't do that.
|
|
1:04:18
|
So now let's try dialing
|
|
1:04:22
|
92065015111
|
|
1:04:31
|
And again, the call cannot be completed right now because
|
|
1:04:35
|
the route partition is not active.
|
|
1:04:37
|
So let's change it to an active route partition
|
|
1:04:43
|
and I have to save twice,
|
|
1:04:46
|
because I opened another tab.
|
|
1:04:50
|
OK, and I've actually gone ahead and added
|
|
1:04:53
|
Forced Authorization Code and Client Matter Code.
|
|
1:04:57
|
So first off, let's make sure that we can't dial 911 still,
|
|
1:05:02
|
we should only be able to dial
|
|
1:05:06
|
we should only be able dial the @ where the @ matches the
|
|
1:05:10
|
7 or in this case the only thing we have
|
|
1:05:12
|
available on our PSTN 10 digit
|
|
1:05:14
|
area code beginning with 206, so local or Seattle area code
|
|
1:05:19
|
OK? So let's change this back to 92065015111
|
|
1:05:26
|
which is a valid PSTN number
|
|
1:05:29
|
and we'll press dial.
|
|
1:05:31
|
And we hear the beep beep and as soon as
|
|
1:05:35
|
the screen refreshes, we'll see Enter Authorization Code
|
|
1:05:39
|
So we need to enter,
|
|
1:05:41
|
and I didn't enter it in time, I was talking, so I'll the number again.
|
|
1:05:47
|
OK, after we enter the authorization code,
|
|
1:05:51
|
which is going to be 2179, which is actually our national
|
|
1:05:55
|
code, we could do the
|
|
1:05:58
|
we certainly could the local code as well, if I can remember what that was
|
|
1:06:02
|
055, that's right, but after I enter my
|
|
1:06:06
|
forced authorization code, I need to press the # key to let it
|
|
1:06:10
|
know that I'm done entering digits, because I can have variable link
|
|
1:06:13
|
FAC codes as we do, 554
|
|
1:06:17
|
local and 2179 for national.
|
|
1:06:20
|
So I'm gonna dial the number, we hear the beep beep,
|
|
1:06:24
|
you see the Enter Authorization Code,
|
|
1:06:28
|
I'm entering 2179#
|
|
1:06:31
|
and you heard the same beep beep, but now the screen shows
|
|
1:06:35
|
enter CMC code or Client Matter Code,
|
|
1:06:38
|
so I'm entering 555 for personal, and then #
|
|
1:06:44
|
and
|
|
1:06:46
|
the display updates and the PSTN phone is ringing.
|
|
1:06:51
|
So I can combine the two together,
|
|
1:06:56
|
but the nice thing is that, although the tone is the same,
|
|
1:07:00
|
it's been so long honestly since I've
|
|
1:07:02
|
done this in practice and I thought the tone was different but
|
|
1:07:05
|
the tone is the same, but there is a display at the bottom,
|
|
1:07:08
|
that says whether it's a Forced Authorization or a Client Matter Code,
|
|
1:07:12
|
and the FAC does come first, just as it's ordered on this page.
|
|
1:07:16
|
OK? So our route filter works, our @ symbol,
|
|
1:07:20
|
indicating the route filter and numbering plan works, our FACs work,
|
|
1:07:24
|
our CMC works, and our time of day partition works.
|
