|
0:00:14
|
Okay, so now let’s take a look at Call Detail Records
|
|
0:00:16
|
and Call Management Records, CDRs and CMRs.
|
|
0:00:21
|
And to begin with on the CUMA or Cisco Unified Communication Manager Administration Interface.
|
|
0:00:27
|
Let’s go ahead and log in first to just see the standard admin interface.
|
|
0:00:34
|
We need to look at a few things that we need to set.
|
|
0:00:37
|
Call Detail Records were not enabled by default.
|
|
0:00:40
|
We first must come to the System Column and go to Service Parameters.
|
|
0:00:46
|
Now this is actually one of the
|
|
0:00:49
|
specific parameters that we’re going to have to enable per server
|
|
0:00:53
|
and we would enable them per CPE or Call Processing Engine.
|
|
0:00:59
|
So whichever subscriber servers, in this case, in my lab I have a publisher
|
|
0:01:04
|
that is acting as a CPE but whichever in production network, whichever CPE, whichever subscribers are
|
|
0:01:09
|
enabled to have the Call Manager, specifically the Call Manager Service Active.
|
|
0:01:20
|
And the parameters that are server specific are always the first ones that we see.
|
|
0:01:26
|
So until we get to anything that says cluster-wide.
|
|
0:01:30
|
So here we see Cisco Call Managers, parameters on this particular server, the pub.
|
|
0:01:36
|
we’ve got call travelling for dealing with
|
|
0:01:43
|
various codes that we could run into Code Yellow,
|
|
0:01:47
|
to many calls, types of situations, what we can do to throttle that.
|
|
0:01:52
|
Here we’ve got the System Column and CDR-enabled.
|
|
0:01:56
|
Now, the default, as we can see as False, I’m going ahead and change this to True.
|
|
0:02:01
|
I’ve also done something that you would typically not do in a production environment.
|
|
0:02:06
|
But in a lab environment, it’s most advisable to do
|
|
0:02:11
|
and that’s to enable to CDR, tell it to log calls with zero duration
|
|
0:02:17
|
because if we want to take a look at our CDR records, but we’re in a lab environment,
|
|
0:02:22
|
a lot of times, just depends on who you are
|
|
0:02:25
|
but a lot of times, I, for instance, who makes a call
|
|
0:02:28
|
and I will either not actually answer the call
|
|
0:02:33
|
or I’ll answer it once or twice and make sure that media works properly,
|
|
0:02:39
|
make sure that in the call that I can hear both sides at that two-way audio
|
|
0:02:44
|
nd that everything goes properly and then all the subsequent calls
|
|
0:02:49
|
I will simply make that quick call and
|
|
0:02:53
|
probably quickly hang up or not even answer it.
|
|
0:02:56
|
And so if you want to look at the CDR records, you need to enable zero duration.
|
|
0:03:01
|
In a production environment, this is not advisable in fact, I think on changing it, no doesn’t.
|
|
0:03:06
|
I thought I told you that it’s not advisable in here
|
|
0:03:16
|
It doesn’t give you the warning. But basically this can result in a high number of CDR records
|
|
0:03:26
|
particularly in environments where there’s going to be a lot of calls that are
|
|
0:03:32
|
initially generated but not completed.
|
|
0:03:35
|
The next thing that’s really good idea to change,
|
|
0:03:39
|
both in lab and production environment, is Digit Analysis Complexity.
|
|
0:03:45
|
Now this is not so much for CDR, but something else that we’ll take a look at, the Dialled Number Analyzer.
|
|
0:03:51
|
The Dialled Number Analyzer, is something that we can use to
|
|
0:03:57
|
diagnose and troubleshoot our calls and see where they’re going out to the PSTN and what not.
|
|
0:04:03
|
And the default is standard analysis for the complexity that it is going to use to analyze.
|
|
0:04:11
|
But especially if you’re ever using and we haven’t got too much into it yet,
|
|
0:04:16
|
but especially if you're ever using Plus Styling or Globalized Styling,
|
|
0:04:22
|
something that’s CCNP voice topic.
|
|
0:04:25
|
Then, you will most certainly want to take
|
|
0:04:29
|
and change that to translation and alternate pattern analysis versus just the standard route pattern analysis.
|
|
0:04:37
|
This will help us see a lot more information.
|
|
0:04:41
|
We also have some various things
|
|
0:04:43
|
related to our STL traces
|
|
0:04:48
|
and then we get in to the cluster-wide parameters.
|
|
0:04:52
|
So, I'm going to go ahead and change, I've changed this to True, I don’t need to save it.
|
|
0:04:55
|
I'm gonna go ahead and look at the subscriber
|
|
0:05:04
|
And again I've said CDR,
|
|
0:05:06
|
log calls and digit analysis complexity to True, True
|
|
0:05:11
|
and translation and alternate from their defaults of False, False and standard analysis.
|
|
0:05:20
|
It’s also important to note
|
|
0:05:23
|
that in order to have proper CDR records, it’s important to have end users
|
|
0:05:29
|
to have those end users,
|
|
0:05:34
|
linked or device-associated.
|
|
0:05:38
|
n this case don’t actually have B-Line, which was a bad example,
|
|
0:05:41
|
that’s a phone that’s currently not on this cluster but I think H. Reyes has a phone assigned
|
|
0:05:47
|
as well as CPC device, it’s important to have them selected for their device control,
|
|
0:05:55
|
their primary extension which can only be done after the device association or device control
|
|
0:06:01
|
And then as well as on the individual devices on the individual phones,
|
|
0:06:10
|
it’s important to have the owner-user ID set
|
|
0:06:16
|
and remember or recall or actually we haven’t talked about it yet, but we will later
|
|
0:06:22
|
If for some reason extension mobility has been enabled on a phone, watch when I do this
|
|
0:06:32
|
Once extension mobility has been enabled on a phone,
|
|
0:06:36
|
you can no longer set the owner ID,notice that it’s grade out.
|
|
0:06:41
|
So if you noticed that the owner user ID
|
|
0:06:46
|
dropped down selectable parameters is grade out, if the name is proper
|
|
0:06:51
|
and has already been set, J Shepherd has already been set
|
|
0:06:59
|
then that takes, just because it’s greyed out, it does not mean that J Shepherd is not the owner, he is
|
|
0:07:04
|
everything is fine there, call detail records as well as
|
|
0:07:08
|
device mobility, other things that need this
|
|
0:07:12
|
will work properly, but it’s juts important that if it’s not set properly or not set at all,
|
|
0:07:19
|
that you first disable extension mobility
|
|
0:07:28
|
and then set your owner-user ID
|
|
0:07:33
|
And then if you need to go back and re-enable extension mobility
|
|
0:07:37
|
But those owner-user IDs are important. So once we've done that,
|
|
0:07:43
|
we are going to go ahead and come up here to navigation and go to
|
|
0:07:49
|
Cisco Unified Serviceability
|
|
0:07:58
|
And from Cisco Unified Serviceability,
|
|
0:08:01
|
assuming that we've gone ahead and activated our services and made sure everything works,
|
|
0:08:05
|
we can see that we have, once we activated our services we have CDR analysis and reporting
|
|
0:08:11
|
So this is known as CDRs, the Call Detail Records
|
|
0:08:15
|
So this is the Call Detail Records Analysis and Reporting
|
|
0:08:18
|
or CDR Analysis and Reporting which is CAR.
|
|
0:08:23
|
Cisco loves their acronyms, of course.
|
|
0:08:26
|
We also have the Dialled Number Analyzer that we spoke of and CDR Management
|
|
0:08:32
|
or CMR, Call Management Records. So let's take a look
|
|
0:08:37
|
So let’s take a look at our CAR tool and this is
|
|
0:08:41
|
obtained by just going to “forward/CAR” as well
|
|
0:08:45
|
just if we wanted to go to dialled number analyzer, this will open up
|
|
0:08:49
|
“/DNA” and you could just go to the IP address with the
|
|
0:08:55
|
443 reroutes to 8443 which is the Tom Cada SSL port
|
|
0:09:02
|
and “/DNA” for dialled number analyzer, we’ll get to that
|
|
0:09:07
|
and a note popped up or a window popped up saying, when I went to CDR analysis and reporting telling me
|
|
0:09:14
|
that the following notes, CDR log calls with zero duration is activated
|
|
0:09:20
|
Hence, CDRs will be generated even the phone is made off hook.
|
|
0:09:25
|
I think they meant the phone call is made off hook.
|
|
0:09:30
|
And it tells us that this competitively generates large number of CDR files
|
|
0:09:33
|
for which the duration is zero and will populate billing tables very fast.
|
|
0:09:38
|
So, hence, the 2-minute high watermark
|
|
0:09:43
|
limit can be bridged in a very short time, this is a no production environment.
|
|
0:09:46
|
Again, for a lab environment this is just fine.
|
|
0:09:55
|
It also tell us that
|
|
0:09:57
|
we’re continuously loading 24/7 configurations activated so we’re logging all the time
|
|
0:10:03
|
not just part of the days if we want to enable CMRs, call management record loading
|
|
0:10:08
|
please uncheck load CDR only option from CAR system scheduler CDR load.
|
|
0:10:16
|
So let’s take a look at that, let’s hear from RNCAR,
|
|
0:10:21
|
from system scheduler CDR load, it tells us to untick load CDR only.
|
|
0:10:33
|
So now, CMRs will also be loaded and we have to wait a moment while that reloads.
|
|
0:10:53
|
And it also told us in the pop-up window which has gone ahead and closed,
|
|
0:11:01
|
the oldest and latest call records that were in there
|
|
0:11:07
|
And I haven’t made any calls too recently on my system so I have to look back a little ways.
|
|
0:11:15
|
So let’s take a look at few other things on the system column
|
|
0:11:19
|
look at the system parameters so male parameters,
|
|
0:11:24
|
dialled plan, gateway, trunk, and system preferences
|
|
0:11:29
|
We’ll take a look at the male. This is going be a male ID and password so username and password
|
|
0:11:37
|
of a male account probably set-up specifically for
|
|
0:11:42
|
unified communications CDR, the domain name and the server name, IP
|
|
0:11:48
|
or host name if you set-up for DNS, so that
|
|
0:11:52
|
reports can be automatically scheduled in male then I should start by saying,
|
|
0:11:57
|
this provides the CAR tool,
|
|
0:11:59
|
CDR analysis and reporting tool, provides a very preliminary and it was only ever intended as a preliminary
|
|
0:12:07
|
call management record system. All of the CDR,
|
|
0:12:12
|
all of the call detail records that are generated and call management records that are generated
|
|
0:12:17
|
are extremely robust in the database but in terms of a reporting interface,
|
|
0:12:22
|
this only provides a rudimentary reporting and scheduling interface.
|
|
0:12:26
|
If you really want detailed billing records, all the information is there
|
|
0:12:31
|
but it is advisiable to have a 3rd party billing server.
|
|
0:12:36
|
Of course, that’s not what is covered in your exams.
|
|
0:12:40
|
However it is good note for production environment that this is probably not going to meet
|
|
0:12:47
|
many costumer requirements. Youll see that it’s decent but it’s
|
|
0:12:51
|
fairly especially if you look at some of the professional enterprise once out there.
|
|
0:12:56
|
This one is fairly limited.
|
|
0:12:59
|
So anyhow, our male, we also have a Dialled Plan Configuration
|
|
0:13:05
|
So here’s with the Dialled Plan Configuration.
|
|
0:13:09
|
Let’s take a look, we notice some very interesting patterns.
|
|
0:13:12
|
We’re going to talk about in CUCM, when we get to Dialled Plan,
|
|
0:13:17
|
the way that patterns are set up in traditional route patterns or translation patterns or DNs.
|
|
0:13:24
|
We are also going to take a look at SIP dial rules
|
|
0:13:28
|
and they have a little bit of a different pattern structure because they have to follow the SIP or FC
|
|
0:13:33
|
and here we see even a little bit different structure in terms of some
|
|
0:13:39
|
differences in what we see for instance, capital T,
|
|
0:13:44
|
capital G, these things are not allowed
|
|
0:13:49
|
per se in the traditional patterns.
|
|
0:13:52
|
This is just for the CDR conditions we’re identifying.
|
|
0:13:58
|
So let’s just take a look
|
|
0:14:00
|
almost all ways in CUCM, you'll hear me say it a lot and we’ll go and look at it a lot.
|
|
0:14:05
|
We’ll do help for this page
|
|
0:14:07
|
and the reason is, if there’s something specific like what this capital T means, or what is this
|
|
0:14:12
|
exclamation, which I’ll probably refer to often as a “bang.”
|
|
0:14:16
|
What does this mean, what does “XG bang” mean?
|
|
0:14:19
|
Help for this page will almost always tell us.
|
|
0:14:23
|
First of all it’s telling us that
|
|
0:14:27
|
what we’re looking at, so Boolean, =, > or
|
|
0:14:31
|
So =5 digits, =7 digits, =10, =10, =10, =11, 11, 11 and then >3.
|
|
0:14:41
|
What is the pattern?
|
|
0:14:43
|
So, equal to5 digits with this particular pattern.
|
|
0:14:46
|
and then the reason for this is we want to identify these types of calls
|
|
0:14:51
|
as what they are, what we want them be
|
|
0:14:55
|
classified as for our Call Detail Records. So are they an on-net call,
|
|
0:14:59
|
or is this a local, long distance or international,
|
|
0:15:04
|
also referred to as local, national or subscriber and national
|
|
0:15:09
|
and then international. On-net, obviously being on net.
|
|
0:15:15
|
I can’t remember if we have already or we’ll talk about that.
|
|
0:15:19
|
Oh yeah we've already talked about that, on-net versus off-net versus PSTN.
|
|
0:15:24
|
So, on-net, off-net,
|
|
0:15:26
|
as two of the types and then the 3rd type being PSTN
|
|
0:15:30
|
which is a form of off-net
|
|
0:15:33
|
and then we also have just we could call something others.
|
|
0:15:36
|
So we've, or actually this is the default,
|
|
0:15:41
|
I haven’t changed anything of these yet,
|
|
0:15:44
|
but these are the, let's see 1 2 3 4 5 6 7 8, 9 default
|
|
0:15:50
|
patterns and identifying types based on
|
|
0:15:53
|
the condition and number of digits.
|
|
0:15:55
|
All equal to a certain number of digits except for the last
|
|
0:15:58
|
is international in Math, must be greater than three digits.
|
|
0:16:01
|
is obviously set up for the North American numbering plan
|
|
0:16:04
|
and it might not even be set up for what you want it to be set up for.
|
|
0:16:08
|
This doesn’t include plus styling.
|
|
0:16:11
|
So if you were using plus styling, we would want to change this.
|
|
0:16:14
|
we would want to change this.
|
|
0:16:16
|
We would want to add pluses to most everything where it pertained properly.
|
|
0:16:22
|
You can see that theyre using five digits on on-net.
|
|
0:16:26
|
Most everything will do is four.
|
|
0:16:29
|
So, that is something I just now changed.
|
|
0:16:32
|
But again, taking a look, we see that the pattern G
|
|
0:16:36
|
signifies that this has been classified
|
|
0:16:41
|
as a specified rule Gate G
|
|
0:16:44
|
is equals the wild card for the gateway area code
|
|
0:16:47
|
that is specified in the configuring gateway topic.
|
|
0:16:50
|
This is something we’ll take a look at when we got system
|
|
0:16:52
|
system parameters, gateway configuration
|
|
0:16:56
|
gateway configuration next, we're currently at dialled plan
|
|
0:16:59
|
Maybe we want to go ahead and take a look at gateway to identify
|
|
0:17:03
|
local area codes or local city codes, local geographic codes
|
|
0:17:07
|
for our particular gateways.
|
|
0:17:12
|
We see that T retrieves toll-free numbers that are configured in CAR
|
|
0:17:17
|
Where?
|
|
0:17:18
|
They're configured, we're gonna get rid of that
|
|
0:17:24
|
Those are configured right here, so 1800
|
|
0:17:28
|
1855, 1866, so, this is a kind of separated
|
|
0:17:33
|
value set of toll-free numbers.
|
|
0:17:37
|
You know, 5 is in the UK. I might do something like 800.
|
|
0:17:40
|
This is set up for the US currently. So those who are my 800 numbers.
|
|
0:17:44
|
So T is going to specify any of these
|
|
0:17:49
|
currently for digit prefixes.
|
|
0:17:51
|
They don’t have to be four digits, whatever I put up there separated by commas.
|
|
0:17:55
|
So, T and then “bang”, wee see “bang,”
|
|
0:17:59
|
it signifies multiple digits,
|
|
0:18:01
|
anything more than one digit so that is the same as the CUCM
|
|
0:18:04
|
translation or route pattern field.
|
|
0:18:07
|
And this is also the same, X signifies a single digit.
|
|
0:18:11
|
when we say T “bang,” we’re saying 1800.
|
|
0:18:15
|
Any additional digits, but it has to have additional digits, at least one
|
|
0:18:19
|
or 1855 additional, 1866 additional, 1877 additional or 1888 additional.
|
|
0:18:25
|
Those, as long as they have a total of 10 digits
|
|
0:18:29
|
and begin with 1800 or 855, 866, 877 and 888.
|
|
0:18:35
|
And then additional digits equal to 10, we will classify that as Others.
|
|
0:18:40
|
Also, if it’s equal to 11 digits and begins with T.
|
|
0:18:47
|
Maybe the reason we would do this is maybe we also want to have, 800, 855, 866, 877.
|
|
0:19:00
|
I noticed that these don’t begin with 9
|
|
0:19:05
|
This just depends on how you have your dialled plan set up.
|
|
0:19:09
|
If your dialled plan has 9 as its secondary dial tone or trunk,
|
|
0:19:16
|
PSTN trunk access code or possibly a lot in the rest of the world uses 0
|
|
0:19:21
|
for that secondary trunk access code.
|
|
0:19:23
|
Whatever you have that set up as,
|
|
0:19:25
|
that may be something that you want to specify
|
|
0:19:28
|
before your patter and identify the number of digits,
|
|
0:19:31
|
or you might want to specify it as a secondary trunk code.
|
|
0:19:34
|
A lot of software, third party billing software
|
|
0:19:38
|
where you don’t really need to come in to CAR and set anything up.
|
|
0:19:41
|
The CDR records are going to be generated as long as in CUCM,
|
|
0:19:46
|
in the CUCMA under the system service parameters
|
|
0:19:51
|
as long as we enable the CDR records for our
|
|
0:19:55
|
processing engine subscriber servers, the CDR records will be generated
|
|
0:20:00
|
and then we will off-load them to a third party billing server.
|
|
0:20:04
|
Then those third party billing servers can look those up and a lot of those servers.
|
|
0:20:10
|
In fact, every third party enterprise billing software that I’ve ever seen
|
|
0:20:16
|
always has a field that we can fill in specifically to input our secondary
|
|
0:20:26
|
secondary dial tone or PSTN trunk access code.
|
|
0:20:30
|
And typically some have multiple in case or cluster span multiple countries.
|
|
0:20:35
|
So that would take care of that. If you're using that third party software,
|
|
0:20:40
|
you don't really need to set any of these up.
|
|
0:20:43
|
But it is good to know this obviously for a lab environment.
|
|
0:20:48
|
So, we got 7-digit local calls that have more than one digit,
|
|
0:20:52
|
call them local if they are 10-digit local calls
|
|
0:20:56
|
I'm sorry if they are 10-digits
|
|
0:20:59
|
we consider them long distance or 11-digits we consider them long distance or nationals.
|
|
0:21:05
|
Now, wait a minute, what about our local calls that are 10 digits?
|
|
0:21:07
|
Well, those are specified by our gateway.
|
|
0:21:10
|
If they begin with the toll-free, they are Others.
|
|
0:21:13
|
If they begin with our gateway code which we are about set up here on
|
|
0:21:16
|
the system parameters gateway configuration.
|
|
0:21:20
|
Then we’ll consider them local
|
|
0:21:23
|
if they X and then G so one digit and then G.
|
|
0:21:27
|
Probably it would be safe to put in one here but we
|
|
0:21:32
|
could just as well say a single digit or 1.
|
|
0:21:36
|
And then the gateway code or the area code, we’ll consider the local.
|
|
0:21:41
|
. If they have more than 3 digits and they begin with 011 which is the international
|
|
0:21:45
|
prefix for the US we consider them international
|
|
0:21:49
|
if they were in another country, maybe 00
|
|
0:21:52
|
If we’re including the secondary PSTN code, maybe 0.
|
|
0:21:56
|
Maybe if it was Australia, 00 or 11.
|
|
0:22:00
|
Anyhow, this is the idea
|
|
0:22:06
|
So hopefully it makes sense.
|
|
0:22:08
|
So I'm gonna go ahead and update with number of digits 4 for our on-net.
|
|
0:22:15
|
So let’s take a look at our Gateway Configuration.
|
|
0:22:21
|
And we see that we have three gateways and they are currently specified with no area codes.
|
|
0:22:28
|
So, let’s say 206, if we do set, we set them on 03.
|
|
0:22:33
|
So, let’s say 206, for branch, looks like I have
|
|
0:22:40
|
My Corporate Headquarter Gateway is actually a SIP trunk
|
|
0:22:45
|
So iIt doesn’t show up as a gateway because it is not in call manager or
|
|
0:22:50
|
Unified Communications Manager terms.
|
|
0:22:52
|
It’s not a gateway per se, it is a trunk.
|
|
0:22:55
|
So, I don't see that here, but I do have
|
|
0:22:59
|
dot3 which is my H323 version of my branch 2
|
|
0:23:04
|
Here’s my MGCP version, I've just had them in there twice
|
|
0:23:07
|
because once I was using it as MGCP and once as H323
|
|
0:23:12
|
And the problem I'm my area code for there is 20, that’s in Amsterdam.
|
|
0:23:17
|
So it’s in another country
|
|
0:23:18
|
This CDR or CAR
|
|
0:23:22
|
I shoudn't say CDR, the CDR is just the records but CAR
|
|
0:23:26
|
Cisco’s internal implementation of the analysis and reporting tool
|
|
0:23:30
|
is only meant for single country or cluster.
|
|
0:23:34
|
Of course, we can do more, we would want to use enterprise billing software for that
|
|
0:23:40
|
and maximum number of ports because new one 30
|
|
0:23:44
|
So branch 1 router 2 is actually at the 512 area code
|
|
0:23:49
|
and I can’t set the corporate headquarter from here.
|
|
0:24:00
|
And it said that it didn’t like 0 as the maximum number of ports
|
|
0:24:04
|
So, we could put how many calls we thought we might have a the same time, so 512
|
|
0:24:20
|
So we also have trunk
|
|
0:24:23
|
trunk configuration, here is where I can do my area codes for my trunks
|
|
0:24:29
|
So,here I've got my corporate headquarter PSTS gateway
|
|
0:24:31
|
this is going to be my 206 area code.
|
|
0:24:34
|
And I've got call control discovery
|
|
0:24:36
|
something we’ll look at much much later and a cups trunk.
|
|
0:24:40
|
Neither of those I want to set.
|
|
0:24:42
|
I might want to set more than one port, again, it’s a trunk
|
|
0:24:46
|
It’s really a single connection like I can have more than one call up to me.
|
|
0:24:56
|
I can also set a company name under system references.
|
|
0:25:03
|
Continuing under the system column,
|
|
0:25:08
|
Under scheduler, we are ready to look at CDR load
|
|
0:25:11
|
where we unticked load CDR only and enable to CMRs or call management records.
|
|
0:25:17
|
We can look at daily, weekly and monthly jobs.
|
|
0:25:21
|
let us just look at weekly.
|
|
0:25:23
|
so we can see when the weekly report generation is set to run
|
|
0:25:27
|
and we can change this, we can change when the daily
|
|
0:25:30
|
and when the monthly report is set to run.
|
|
0:25:34
|
Taking a look at the database,
|
|
0:25:36
|
we can configure automatic purge or also manually purge
|
|
0:25:41
|
the CAR database. So this is the billing data, billing air or purge history
|
|
0:25:46
|
table within the database and should we manually or set up automatic purge
|
|
0:25:52
|
to do between a certain date or older than a certain date
|
|
0:25:57
|
so that it doesn’t become to overwhelmed.
|
|
0:26:00
|
Good idea to make sure you have an automatic purge
|
|
0:26:04
|
so we’ve got a low watermark of 80%,
|
|
0:26:08
|
80% of our maximum database space allocated
|
|
0:26:12
|
and our maximum looks like it’s about 6GB
|
|
0:26:15
|
So once we get above 80%,
|
|
0:26:19
|
we’re going to generate warnings.
|
|
0:26:20
|
Once we get above 90%, we are going to begin purging records.
|
|
0:26:24
|
And we’re saying the maximum age of call detail records is 60 days.
|
|
0:26:28
|
If you have an abnormally high call volume,
|
|
0:26:32
|
you might want to have 30 days.
|
|
0:26:33
|
Again, if you're offloading all this CDR record
|
|
0:26:36
|
onto a third party dedicated billing server with
|
|
0:26:40
|
you know, it's gonna offload into its database,
|
|
0:26:44
|
store it in there. It’s going to have probably a lot bigger hard drives.
|
|
0:26:50
|
In fact, you can’t run, you used to be able to but you cannot run
|
|
0:26:54
|
CDR reports against the CDR database on the CUCM cluster.
|
|
0:26:59
|
It has to be offloaded first and then you run the reports
|
|
0:27:02
|
off of your own third party billing server.
|
|
0:27:05
|
Unless, you’re using the CAR tool,
|
|
0:27:06
|
that will run directly against the CDR database on the cluster.
|
|
0:27:11
|
But it’s recommended to
|
|
0:27:14
|
offload everything and run that third party server
|
|
0:27:18
|
so that you can have a lot more than 30 or 60 days of billing history.
|
|
0:27:24
|
Next, let’s come up here to log screens and look at our event log
|
|
0:27:40
|
The following errors occured
|
|
0:27:43
|
Error code: system error
|
|
0:27:51
|
Well anyway, if it would let us go to log screen event log,
|
|
0:27:56
|
What this is just looking at, we have a number of different reports,
|
|
0:28:01
|
daily, weekly and monthly that can run
|
|
0:28:05
|
and we can take those available reports, put them
|
|
0:28:08
|
in the right hand window pane for selecting
|
|
0:28:12
|
those reports and then hit “Ok” between the certain date range
|
|
0:28:17
|
and we can take a look at the event log for when those
|
|
0:28:20
|
reports basically to see when those reports ran if they ran successfully
|
|
0:28:25
|
if they had an errors, things of that nature.
|
|
0:28:28
|
Let's just make sure any of these are going to work good
|
|
0:28:32
|
So that's the system column.
|
|
0:28:35
|
Looking at the report configuration column, and we’ll get over with the ones on the left in a bit.
|
|
0:28:40
|
Rating engine, so this deals more with Call Management.
|
|
0:28:45
|
Look at the duration, the time of day and the voice quality.
|
|
0:28:50
|
So how long, first of all, let’s look at Voice Quality.
|
|
0:28:56
|
So this deals with mean opinion scores
|
|
0:28:59
|
So we've got the Good, Acceptable, Fair, and Poor. Good is the best.
|
|
0:29:04
|
And we want to possibly assign those multiplication factors.
|
|
0:29:08
|
They are all currently set to the same weight.
|
|
0:29:11
|
And what we can do is use these weights to really affect.
|
|
0:29:17
|
If we use and get to soft keys a little bit but back in
|
|
0:29:23
|
Unified Communication Manager Administration, we can assign soft keys
|
|
0:29:30
|
fact, let’s just go ahead and look at that real briefly.
|
|
0:29:35
|
Not soft keys in general but just the particular soft key.
|
|
0:29:41
|
I'm going too fast, don't worry, we will certainly take a look
|
|
0:29:45
|
at how to assign soft keys and everything.
|
|
0:29:49
|
But for let’s say we’re in a connected call state,
|
|
0:29:54
|
users have the ability, we can take the unselected soft keys
|
|
0:29:58
|
and grab this quality report tool
|
|
0:30:01
|
and bring it over to the selected soft keys that actually show up
|
|
0:30:05
|
up in the order by position in the phone
|
|
0:30:09
|
So, they would have, 1, 2, 3, depending how many soft key buttons and probably hit more
|
|
0:30:13
|
than 1, 2, 3, hit more second time, 1, 2, 3, hit more third time, 1, 2, 3,
|
|
0:30:19
|
hit more the fourth time or we could move this up anywhere we wanted.
|
|
0:30:24
|
And if they hit the more soft keys four times,
|
|
0:30:28
|
they would come to the fifth screen which would have
|
|
0:30:31
|
quality report tool.
|
|
0:30:33
|
As a soft key they could select that and
|
|
0:30:37
|
by doing so, they can log that particular call
|
|
0:30:42
|
that they’re on especially if the user has been reporting
|
|
0:30:45
|
issues with the quality of their voice.
|
|
0:30:49
|
So you can instruct the users
|
|
0:30:52
|
that are experiencing this kind of issues.
|
|
0:30:56
|
Probably, I don't want to tell anyone to do this,
|
|
0:30:59
|
to go ahead and use this soft key, sign it to their phone
|
|
0:31:03
|
and use this whenever you are on a call and you experience
|
|
0:31:08
|
a problem with that call with the audio or else, either you
|
|
0:31:13
|
or the other side of your party
|
|
0:31:18
|
and this will log statistics about the call.
|
|
0:31:23
|
Jitter, packet loss, everything else that we’ll take a look at
|
|
0:31:28
|
that we can see from the web interface of the phones.
|
|
0:31:33
|
So this rating engine
|
|
0:31:38
|
the time of day that this is running from and the duration
|
|
0:31:45
|
we’re going to log information about this particular call.
|
|
0:31:50
|
also let’s say 6 seconds,
|
|
0:31:52
|
or maybe we want to up that to 10 seconds
|
|
0:31:55
|
We only want to gather information for a short period of time.
|
|
0:31:58
|
We don't want to gather information for the entire call,
|
|
0:32:01
|
maybe they’re experiencing some static on the call.
|
|
0:32:04
|
It’s not so bad they hang up, but they are certainly complaining about the call.
|
|
0:32:11
|
We don't want to, maybe they're on at those, however it's not so bad
|
|
0:32:14
|
But they hang up so they're on for 30 minutes, we don't want to log 30 minutes of data
|
|
0:32:19
|
And probably the default of 6 seconds is fine
|
|
0:32:21
|
You might want to a little bit more
|
|
0:32:23
|
just keep in mind there’s a lot of information generated in that time.
|
|
0:32:28
|
In terms of the matrix that we use to distinguish or
|
|
0:32:33
|
delineate, differentiate between Good, Acceptable, Poor
|
|
0:32:39
|
what was the other one?
|
|
0:32:41
|
We can come up to report configuration and do define CUOS
|
|
0:32:45
|
and Good, Acceptable, Fair and Poor, that was the four
|
|
0:32:49
|
And we can say, first of all, we’ve got the lost packet percentage
|
|
0:32:53
|
from and to so from 0 to 15 percent
|
|
0:32:58
|
lost packet is considered as Good.
|
|
0:33:01
|
I personally wouldn’t consider 15 percent packet loss as good
|
|
0:33:05
|
I would consider that
|
|
0:33:07
|
as really bad, this is the default, though so I might want to take that to
|
|
0:33:11
|
I don't know, 1% for Good?
|
|
0:33:17
|
1.01% to 30% packet loss, they’re considering it Acceptable.
|
|
0:33:25
|
If you have 45% packet loss, you don't have a call.
|
|
0:33:29
|
I mean, you don't have even hardly have IP routing at that point but anyhow
|
|
0:33:35
|
adjust this as you see fit.
|
|
0:33:38
|
So, we’ve got lost packets, we’ve got jitter and we’ve got latency.
|
|
0:33:43
|
Notice that for lost packets, we’re saying from 0 to 1%
|
|
0:33:48
|
but this is not applicable. The idea is that
|
|
0:33:52
|
we have our lost packets in our top,
|
|
0:33:55
|
we are doing not applicable
|
|
0:33:57
|
in the top here for jitter and latency so it only has to equal
|
|
0:34:01
|
0 to 1% packet loss in order to trigger good.
|
|
0:34:06
|
And we have a second row for jitter.
|
|
0:34:10
|
We don't have anything for latency.
|
|
0:34:12
|
So, if we wanted to have latency, we would add a row.
|
|
0:34:19
|
So, I tick that box and it added a row above there so I have my
|
|
0:34:24
|
NA, NA, NA, NA and then for latency, I would have from
|
|
0:34:30
|
this is just latency, this isn’t the difference in latency which is jitter but let’s say,
|
|
0:34:36
|
, I hardly consider 20 as a Good jitter, maybe 10 or 15
|
|
0:34:41
|
but regardless we can set these
|
|
0:34:45
|
let's say latency, we see good as
|
|
0:34:48
|
this is gonna be round trip, actually no I think this is one way, let's say
|
|
0:34:57
|
1-130, something like that
|
|
0:35:05
|
So we can specify these lost percentages as acceptable as fair.
|
|
0:35:11
|
These jitter variations from and to
|
|
0:35:15
|
as Acceptable, Fair, Poor and Good, etc and we can update.
|
|
0:35:19
|
However, we want our quality service matrix to be defined.
|
|
0:35:24
|
Back to our actual CDR automatic records,
|
|
0:35:28
|
we can do report configuration, automatic generation and alert.
|
|
0:35:34
|
So, we can say which of these reports
|
|
0:35:37
|
either monthly reports, daily reports,
|
|
0:35:40
|
, somebody’s actually going to take look at that those reports,
|
|
0:35:43
|
, like top-end charge or top-end duration, or top number of calls
|
|
0:35:47
|
or traffic summary but which daily, weekly
|
|
0:35:49
|
reports do we want to be enabled and then deal with any custom parameters for those.
|
|
0:35:59
|
If we click Custom Parameters, this opens up a new window
|
|
0:36:03
|
and we can choose whether we want this particular reports to be generated automatically,
|
|
0:36:08
|
whatever it is set to in CSV or PDF format
|
|
0:36:12
|
If we want to email this option, this report out
|
|
0:36:18
|
this particular reports that I selected was traffic summary by hour of the day and it’s a daily report,
|
|
0:36:23
|
though I want to mail it or do I just want to
|
|
0:36:27
|
actually run the report but not mail it which means I have to log in to the CAR
|
|
0:36:32
|
interface to retrieve it and which call types do I want to log on.
|
|
0:36:36
|
Do I only want to log on maybe on-net calls or here I have all of them selected,
|
|
0:36:42
|
on-net, international, I also have internal
|
|
0:36:45
|
which is a slight differentiation from on-net
|
|
0:36:49
|
so on-net might be in between clusters which might be why we have five
|
|
0:36:54
|
characters for instance and may be back on that
|
|
0:36:59
|
on that particular system dialled plan configuration maybe I would have put
|
|
0:37:04
|
something like five digits beginning with an 8
|
|
0:37:08
|
or whatever it was that used to go in between clusters
|
|
0:37:12
|
or internal calls, DNs that it knows about
|
|
0:37:16
|
incoming, international outgoing,
|
|
0:37:20
|
local outgoing, national or long distance outgoing, others and also something called tandem.
|
|
0:37:25
|
We're basically we are looping or coming in and going back out
|
|
0:37:31
|
which quality of service do I wanna report on
|
|
0:37:33
|
All of these I can change for other reports
|
|
0:37:36
|
as well as particular alerts that I might have set up, I can enable those.
|
|
0:37:44
|
And finally notification limits,
|
|
0:37:48
|
when I should set flags that show up on the RTMT.
|
|
0:37:57
|
So alerts when good calls are less than 20% of the calls are good.
|
|
0:38:03
|
When poor calls are greater than 30% of the overall calls,
|
|
0:38:06
|
or if a daily charge limit has gone for user beyond 200 units
|
|
0:38:11
|
things that we can take a look at. But we can generate these limits
|
|
0:38:15
|
and generate notifications to the alerting center, RTMT, to people
|
|
0:38:20
|
that might be watching our cluster with various management tools.
|
|
0:38:31
|
So, moving on, we kind of going
|
|
0:38:34
|
a little bit, not necessarily left to right here. We need to start out with system
|
|
0:38:39
|
and look the reports. Now, let’s take a look at CDR.
|
|
0:38:44
|
First of all, note that we can export CDR and CMR records,
|
|
0:38:50
|
so we can choose our date range, let’s say we choose June 1st to July 1st
|
|
0:38:54
|
and export both CDR and CMR, click export to file.
|
|
0:39:00
|
We can right click and save this As
|
|
0:39:07
|
and once we do, delete the file
|
|
0:39:12
|
And they actually export as .txt, you can rename them as CSV
|
|
0:39:19
|
and then open them up and so here are our CMR records.
|
|
0:39:24
|
Notice the last three before the CSV that I changed it to CMR.
|
|
0:39:28
|
So we've got an issue about that
|
|
0:39:32
|
call identifier for originating call, destination call identifier
|
|
0:39:37
|
and you can see that I already haven’t taken any quality reports.
|
|
0:39:43
|
We don't see any jitter, latency or things of that nature.
|
|
0:39:47
|
We do see the calling party number, the called party number,
|
|
0:39:52
|
the calling number partition and the called number partition
|
|
0:39:58
|
the global cluster ID, so this global call ID, by the way
|
|
0:40:03
|
we didn’t actually go over this, let me just go this real quick
|
|
0:40:06
|
So back in the admin interface, under system
|
|
0:40:10
|
enterprise parameters, we’ll take a look at this later
|
|
0:40:12
|
but we’ve got a cluster ID. So for each individual cluster,
|
|
0:40:16
|
it’s a good idea to rename it from the default which is standalone cluster
|
|
0:40:21
|
to something unique and intuitively named for your organization.
|
|
0:40:26
|
I've got C01 because later we’re going to look at a second cluster and I have C02 over there.
|
|
0:40:33
|
But that’s where this global call ID is saying that these all came from cluster 1
|
|
0:40:38
|
They all went through a particular device name which was a phone or a call control discovery trunk
|
|
0:40:45
|
or my SIP trunk out to the PSTN from my corporate headquarters
|
|
0:40:50
|
where the call originally came from so maybe it came from the
|
|
0:40:54
|
corporate headquarter PSTN gateway and went out of CCD trunk,
|
|
0:40:58
|
came from a phone and went out the gateway, so we've got all these information.
|
|
0:41:05
|
And I also have my CDR records. I've got all my date times.
|
|
0:41:12
|
These are in Unix time formats, so I have to change that with
|
|
0:41:16
|
Again, good reason to use their party billing software, but regardless
|
|
0:41:20
|
I’ve got some of these it’s actually just because it’s opened in
|
|
0:41:25
|
in Excel and I did not specify the column formats
|
|
0:41:30
|
but calling party number,
|
|
0:41:35
|
IP address for immediate transport, all sorts of information
|
|
0:41:39
|
really a lot of information we can see in here, you can see we've got
|
|
0:41:45
|
how many columns that is, but it’s a lot of columns.
|
|
0:41:58
|
We’re almost to DAs so that’s four times through the alphabet so
|
|
0:42:03
|
over a hundred tables, about 104, 103
|
|
0:42:07
|
columns, sorry not tables. Anyhow, a lot of good information
|
|
0:42:14
|
Back to CDR, we have the ability to search
|
|
0:42:18
|
by user, by phone number so let’s do a search by user
|
|
0:42:24
|
and let’s research by phone number, let’s say 1001
|
|
0:42:34
|
or now let’s rather search by internal-based users.
|
|
0:42:42
|
Let’s say Jack, “Search”. Here we've got Jack Shepherd.
|
|
0:42:50
|
We'll “Select”, “Close”, there’s 1001.
|
|
0:42:54
|
We’ll say from June to July and “Ok”
|
|
0:43:03
|
and report’s truncated because there’s so much information, we did search a very large range
|
|
0:43:08
|
and we've got all sorts of information about the calls that this particular phone has made.
|
|
0:43:17
|
Calling number 1001 probably will almost always be that.
|
|
0:43:22
|
unless maybe it has a shared line or came from a redirect or something
|
|
0:43:25
|
25001 in the partition with direct external phone number mass or
|
|
0:43:31
|
or alternate Ids. So, a lot of information here.
|
|
0:43:36
|
We can search by gateway, by cause for call termination.
|
|
0:43:40
|
So why the call was turned down, was it normal or was there a problem
|
|
0:43:45
|
by call precedence level mostly military use, malicious calls.
|
|
0:43:50
|
So another thing that soft keys can offer,
|
|
0:44:02
|
is let’s say I'm in a connected state,
|
|
0:44:05
|
I have the ability to, in fact it's there by default, toggle malicious call trace.
|
|
0:44:11
|
So, MC ID, Malicious Call ID, industry standard, so that
|
|
0:44:16
|
and this actually can be passed even out to the PSTN if you’re over ISTN PRI,
|
|
0:44:21
|
if the carrier supports it so that if there is you're receiving
|
|
0:44:25
|
legally or illegal harassing phone calls,
|
|
0:44:30
|
you can go to your soft key and hit that soft key and we can
|
|
0:44:34
|
search internally to see when those malicious calls
|
|
0:44:38
|
were generated as reports by the user
|
|
0:44:42
|
or by call types
|
|
0:44:47
|
and actually all of these call types, this particular bit is
|
|
0:44:54
|
these are all successful, I'm sorry, successful failed
|
|
0:44:58
|
These are all IME or Intercompany Media Engine so we really don't
|
|
0:45:03
|
care too much about that in this particular or in any of our studies at this point.
|
|
0:45:09
|
It’s not in any of the bits, but it’s basically routing between clusters, between companies
|
|
0:45:16
|
by use of the Intercompany Media Engine and SIP trunks and the Internet.
|
|
0:45:22
|
So looking at device reports
|
|
0:45:24
|
we have gateway detail, summary or utilization,
|
|
0:45:27
|
route pattern, and hunt pilot usage.
|
|
0:45:31
|
So, utilization of route patterns or route pilots,
|
|
0:45:34
|
route list or hunt list and even route groups and LAN groups
|
|
0:45:39
|
and even hunt pilot summary in detail.
|
|
0:45:42
|
We can look at conference bridge utilization.
|
|
0:45:44
|
I mean all these pretty much have a similar interface and we generate the report
|
|
0:45:48
|
but it’s important to know what we can generate reports on
|
|
0:45:52
|
So trunk utilization, voice mail utilization, gateway utilization,
|
|
0:45:56
|
CUOS detail or summary reports.
|
|
0:46:00
|
So earlier we were looking at running these automatically but here’s actually where we set up
|
|
0:46:04
|
the individual rapports to run or
|
|
0:46:07
|
create or modify our daily, weekly or monthly reports to run.
|
|
0:46:13
|
Forced authorization code and client matter code
|
|
0:46:16
|
reports malicious call detail,
|
|
0:46:20
|
errors for CDR as well as individual user reports.
|
|
0:46:25
|
So maybe bills based on department, if we have those department set up
|
|
0:46:29
|
Departments, again, based on the end user
|
|
0:46:36
|
and whatever department they happen to be in.
|
|
0:46:39
|
In this case, it’s not modifiable because I am synced to LDAP
|
|
0:46:43
|
If I wasn’t, I could modify it here.
|
|
0:46:45
|
Since I am, this has to be modified on the Microsoft Active Directory LDAP.
|
|
0:46:50
|
So bills by departments, top number of calls by
|
|
0:46:56
|
charge, by duration or by number of calls
|
|
0:47:00
|
has what IP phones service
|
|
0:47:03
|
as well as IPMA or Manager Assistant Call
|
|
0:47:07
|
Manager and Assistant Call Usage
|
|
0:47:10
|
So let’s say top number of calls by number of calls
|
|
0:47:14
|
it kind and seems a little bit repetitive
|
|
0:47:16
|
Let’s say top number of calls by duration, let's change it there.
|
|
0:47:22
|
So, rather than top number of calls by who made the most calls.
|
|
0:47:25
|
Let’s see the top number of calls based on the longest calls.
|
|
0:47:29
|
So individual users, let's generate the report
|
|
0:47:33
|
between June and July in PDF
|
|
0:47:38
|
which CSV would probably be better because I can download it.
|
|
0:47:44
|
Date is only available from June 14 to June 29th.
|
|
0:47:47
|
It tells me no problem, ain't June 14th it was when I enabled CDR
|
|
0:47:54
|
and it also gives me some nice warnings. Currently 3 out of 7
|
|
0:47:57
|
phones have owner-user IDs configured.
|
|
0:48:00
|
If any user ID is not associated,
|
|
0:48:03
|
or if the device only uses extension mobility but has not yet been logged in to essentially
|
|
0:48:09
|
the reports will display records under CAR’s default
|
|
0:48:13
|
user which is called “_Unspecified User.”
|
|
0:48:17
|
So use the CCM Admin, back here Device,
|
|
0:48:22
|
and go to the phone page to configure the owner-user ID
|
|
0:48:26
|
ID and changes will only take effect for newly generated CDRs not retroactively.
|
|
0:48:32
|
And actually in my Firefox window, Internet explorer
|
|
0:48:39
|
works better for this but I'll only be able to see if it's even gonna show me
|
|
0:48:46
|
It’s actually giving me an error, it’s telling me I needed QuickTime
|
|
0:48:50
|
I don't know why that might be.
|
|
0:48:53
|
let’s do that faster this time and say Ok quicker
|
|
0:49:02
|
A lot of times it will only show me the first page
|
|
0:49:06
|
even if there are multiple pages, but again you can send the report
|
|
0:49:10
|
or if you have a proper browser, you can see everything, so it's look like Jack Shepherd
|
|
0:49:15
|
1001 has made the most calls, 33
|
|
0:49:19
|
and then 28 by unspecified and then Hugo has made 7 calls.
|
|
0:49:24
|
And the total duration of those seconds again from
|
|
0:49:27
|
June 1st or really June 14 to June 29th
|
|
0:49:31
|
has been 866 seconds and 75 seconds respectively for the two identified users.
|
|
0:49:40
|
So that really is CAR
|
|
0:49:43
|
in a nut shell, CDR analysis and reporting tool
|
|
0:49:48
|
Let’s just go back to our Unified Serviceability
|
|
0:49:57
|
and take a look at CDR management
|
|
0:50:03
|
before we end this particular video and we can take a look
|
|
0:50:08
|
at the overall disc allocation that we have for call management records.
|
|
0:50:12
|
Our 80% high watermark, 40% low water mark.
|
|
0:50:17
|
And if we click on any one of these, it will take us
|
|
0:50:22
|
to the page where we can modify this information
|
|
0:50:27
|
Before these flips, we have our CDR/CMR
|
|
0:50:30
|
file preservations so keep these records for 30 days.
|
|
0:50:34
|
We can change that to a lower date. We can’t go beyond 30 days.
|
|
0:50:39
|
o our high watermark is when we begin after 3GB to scale back.
|
|
0:50:46
|
We can go a little bit higher up to 90.
|
|
0:50:49
|
Low watermark is when we've passed back under the low water threshold so
|
|
0:50:54
|
CDRs have basically throttled back down.
|
|
0:50:58
|
Once we go above 80%, we’re going to be unthrottling them.
|
|
0:51:01
|
Once they fall back below 40% to 39%
|
|
0:51:05
|
then all the sudden we’ll start allowing them to build up again at a regular rate.
|
|
0:51:09
|
Our total usage if we’ve got big disk, we can go up to
|
|
0:51:14
|
looks like a maximum here of 33 or 3.3GB.
|
|
0:51:19
|
And we can even disable them altogether based on high watermark
|
|
0:51:22
|
rather than just throttling them.
|
|
0:51:23
|
But of course the best idea as I've mentioned all along is to have a third party billing server
|
|
0:51:29
|
and so this is where we would add that particular
|
|
0:51:33
|
new server and we can export records based on FTP or secure.
|
|
0:51:40
|
And in case you didn’t know SFTP or Secure FTP as some people call it,
|
|
0:51:45
|
is really FTP over SSH.
|
|
0:51:48
|
Sometimes called SSH FTP,
|
|
0:51:50
|
it is not FTP over SSL, that is the FTP S protocol
|
|
0:51:56
|
So this is FTP over SSH, most servers support it.
|
|
0:52:00
|
Most clients support it.
|
|
0:52:03
|
Anyhow, the IP address or host name, the username, password and the path
|
|
0:52:09
|
with which we want to send those records out to.
|
|
0:52:12
|
. And then we don't have to worry about keeping them beyond 30 days or beyond the certain
|
|
0:52:17
|
level of disk space.
|
|
0:52:21
|
So that’s pretty much it for our
|
|
0:52:23
|
reporting and analysis in CDR and CMR records.
|
