|
0:00:14
|
So now, let's take a look at CUCM and
|
|
0:00:20
|
So, first of all, CUCM supports the following gateway protocols:
|
|
0:00:25
|
Skinny or SCCP, MGCP or the Media Gateway Control Protocol,
|
|
0:00:32
|
and this is only supported in CUCM at version 0.1
|
|
0:00:36
|
which is a very important distinction because IOS gateways also support 1.0.
|
|
0:00:42
|
And don't worry, it's not that 0.1, it's such a low release as it, you know,
|
|
0:00:48
|
obviously a very low release in terms of release numbers
|
|
0:00:51
|
but this has been the way that it has been for years and it works just fine.
|
|
0:00:56
|
So it's not really too big of a concern in terms of functionality.
|
|
0:01:01
|
Not to say that MGCP hasn't ever had bugs, but anyhow,
|
|
0:01:07
|
and we also have the ability to integrate H.323 version 2 IOS gateways.
|
|
0:01:17
|
So CUCM-supported TDM types, by gateway protocol.
|
|
0:01:22
|
And I actually shouldn't even necessarily say TDM
|
|
0:01:24
|
because some are simply analog altogether
|
|
0:01:26
|
but carrier, CO or PSTN circuit types by gateway protocol.
|
|
0:01:35
|
The Skinny protocol can support ISDN BRI
|
|
0:01:38
|
and FXS only as a gateway.
|
|
0:01:42
|
MGCP has the ability to support ISDN PRI for both T1 and E1
|
|
0:01:48
|
but only after doing a full T1 and E1.
|
|
0:01:51
|
There's no partial support.
|
|
0:01:53
|
There is a work around with something called Beach Handle Maintenance and Services Parameters
|
|
0:01:58
|
but this is not supported by tack as a full-time running production environment solution
|
|
0:02:04
|
and there's also only five fields there so we can only have five partial T1s or E1s.
|
|
0:02:10
|
If you want tohave partial T1s or E1s,
|
|
0:02:13
|
with CUCM, do not use MGCP, use either H.323 or a SIP trunk.
|
|
0:02:21
|
But we are talking about gateways right now.
|
|
0:02:23
|
So MGCP supports T1 and E1 fall for PRI. It will also support BRI.
|
|
0:02:28
|
It will also support T1 channel-assoicated signaling,
|
|
0:02:32
|
but not E1 channel-associated signaling.
|
|
0:02:34
|
So E1 R2 cast is not supported through MGCP.
|
|
0:02:39
|
It would have course be supported through H.323 or SIP.
|
|
0:02:42
|
Also MGCP can support FXO and FXS.
|
|
0:02:46
|
Foreign exchange office out to the PSTN,
|
|
0:02:48
|
Foreign exchange station to an analog phone.
|
|
0:02:52
|
Also, the protocol H.323, any and all of the TDM circuit types.
|
|
0:02:59
|
Looking at what CUCM considers as trunk types,
|
|
0:03:03
|
So Port H.323 and SIP,
|
|
0:03:06
|
And for H.323 we have three sub-categorizations,
|
|
0:03:14
|
H.225 trunks, so basically an Industry Standard 221 H.323 trunk but it is gatekeeper controlled.
|
|
0:03:25
|
We also have an Inter-Cluster trunk which is also an H.323 type of a trunk.
|
|
0:03:31
|
But it has Cisco proprietary extensions essentially.
|
|
0:03:35
|
we know that what's on the other side is a Cisco device
|
|
0:03:37
|
either CUCM cluster or CME
|
|
0:03:41
|
and we have the ability to do that
|
|
0:03:43
|
ICT (Intercluster Trunk) with either Gatekeeper
|
|
0:03:46
|
or non-Gatekeeper control.
|
|
0:03:47
|
Notice that we don't have H.225
|
|
0:03:49
|
non-Gatekeeper controlled trunk.
|
|
0:03:51
|
This would be, if you wanna do and set that up
|
|
0:03:53
|
that would be a H.323 Gateway that you would configure.
|
|
0:03:59
|
For SIP, we're gonna look at them by
|
|
0:04:02
|
Trunk Service Type. Now thisn't 8.0 that there is
|
|
0:04:04
|
Trunk Service Type.
|
|
0:04:06
|
And most of the configuration that we're gonna look at
|
|
0:04:08
|
again we've stated, is
|
|
0:04:10
|
is based on the 7.0 platform and
|
|
0:04:12
|
not very much has changed, anything that has, we
|
|
0:04:15
|
certainly update you on and we will take a look at
|
|
0:04:18
|
one additional things specifically
|
|
0:04:21
|
for 8.0 which is Call Control Discovery
|
|
0:04:23
|
but that really doesn't come
|
|
0:04:24
|
until we're dealing with these gateways
|
|
0:04:28
|
in terms of CCNP Voice, so if you're
|
|
0:04:30
|
watching this for the first time for CCNA Voice,
|
|
0:04:32
|
we don't deal with Call Control Discovery because it's not part of the blueprint
|
|
0:04:36
|
For CCNP Voice, that certainly would
|
|
0:04:40
|
be part of the blueprint and we have
|
|
0:04:43
|
about 4 hours of configuration for that
|
|
0:04:47
|
Ok so SIP by Trunk Service Type, we have
|
|
0:04:50
|
the non-Trunk Service Type which is also
|
|
0:04:53
|
labelled and is the default.
|
|
0:04:55
|
This can be used for Gateway to the PSTN
|
|
0:04:57
|
to any or all of the
|
|
0:04:59
|
TDM circuite types or really the analog or digital PSTN circuits.
|
|
0:05:04
|
It also could be used for generic SIP ISTP
|
|
0:05:07
|
either out through CUBE, the Unified Border Element
|
|
0:05:10
|
or else just directly to an ISTP.
|
|
0:05:13
|
Or even any normal Voice
|
|
0:05:15
|
Call Over SIP, just a trunk to
|
|
0:05:17
|
another cluster, CUCM, CME,
|
|
0:05:21
|
IOS Gateway, Toll By-pass, whatever.
|
|
0:05:24
|
It also can be used in the non-default type for Presence.
|
|
0:05:28
|
We also have the Trunk Service Type of SAF CCD or
|
|
0:05:32
|
Service Advertisement Framework Call Control Discovery.
|
|
0:05:36
|
We have another SIP trunk for Extension Mobility Cross Cluster
|
|
0:05:40
|
and another one for Intercompany Media Engine.
|
|
0:05:43
|
The last two of which are not covered on the
|
|
0:05:46
|
on any of the exams yet, so you don't need to know about them
|
|
0:05:50
|
or if they have and we've updated this, you know
|
|
0:05:52
|
many years on the future then, we obviously have videos on it.
|
|
0:06:00
|
And then MTP involvement for trunks.
|
|
0:06:04
|
So, Media Termination Points
|
|
0:06:08
|
if we're dealing with H.323,
|
|
0:06:11
|
this required the usage of an MTP
|
|
0:06:14
|
if we want to enable Outbound Fast Start.
|
|
0:06:17
|
So slow start is the default
|
|
0:06:20
|
which of course means that we are
|
|
0:06:25
|
sending our H.225 call setup first
|
|
0:06:29
|
and then after the call setup has been accepted
|
|
0:06:33
|
we're doing our H.245 media negotiation.
|
|
0:06:37
|
That's slow start, with fast start,
|
|
0:06:39
|
we send our desired DTMF relay and codec
|
|
0:06:43
|
in our H.225 setup message so
|
|
0:06:47
|
we're trying to start the communication a lot
|
|
0:06:49
|
faster basically trying to cut through the audio
|
|
0:06:51
|
and get the RTP stream up
|
|
0:06:55
|
faster than having to go through all the
|
|
0:06:57
|
H.245 negotiations.
|
|
0:07:01
|
It doesn't mean that there won't be H.245 traffic
|
|
0:07:04
|
but we've already set a number of parameters
|
|
0:07:06
|
so we don't have to go back and forth as much.
|
|
0:07:08
|
So if I'd want to do Outbound Fast Start
|
|
0:07:11
|
whether I'm using the older 7.0 or
|
|
0:07:14
|
newer 8.0 or even beyond 9.0 or whatever.
|
|
0:07:19
|
Guess I shouldn't say for 9.0 because I don't know that yet, it's not out yet.
|
|
0:07:22
|
Require the usage of an MTP to enable it, yes.
|
|
0:07:26
|
You have to have an MTP to enable it.
|
|
0:07:28
|
And in fact it won't even let you
|
|
0:07:30
|
choose an outbound codec for fast start or
|
|
0:07:33
|
tick the tick box for enable Outbound Fast Start
|
|
0:07:35
|
unless you have MTP required ticked
|
|
0:07:39
|
on that H.323 entity
|
|
0:07:43
|
or if you have, I'm sorry
|
|
0:07:46
|
and you have to provide a Media Resource Group list
|
|
0:07:48
|
even if one was available to you in a Device Pool.
|
|
0:07:51
|
You still have provide it explicitly on the page.
|
|
0:07:54
|
However it's not required
|
|
0:07:56
|
and MTP is not required for Inbound Fast Start.
|
|
0:08:00
|
Now for SIP,
|
|
0:08:02
|
the requirement for the usage of a Media
|
|
0:08:05
|
termination point to enable Outbound Early Offer
|
|
0:08:12
|
is not there after version 8.
|
|
0:08:15
|
But before version 8, so most of the videos that you'll
|
|
0:08:17
|
take a look at before somebody updated one
|
|
0:08:19
|
we do require it for Outbound Fast Start
|
|
0:08:23
|
I'm sorry not fast start but the analogous
|
|
0:08:27
|
to it which is the early offer
|
|
0:08:30
|
for SIP, we require it in version 7.0
|
|
0:08:33
|
and 7172 etc.
|
|
0:08:36
|
but it's not required beginning in version 8.0 and beyond.
|
|
0:08:44
|
Now the funny thing about that is, it actually still
|
|
0:08:47
|
requires you check the tick box for MTP required so
|
|
0:08:51
|
the originating codec
|
|
0:08:54
|
is the name of the drop down on a SIP trunk
|
|
0:08:56
|
that you'll see. That doesn't actually even
|
|
0:08:59
|
it's grade out, it doesn't become
|
|
0:09:02
|
lit up and able to populated or changed
|
|
0:09:04
|
until you tick the tick box for
|
|
0:09:06
|
MTP required on a SIP trunk.
|
|
0:09:09
|
But you can check it via RTMT or
|
|
0:09:12
|
performance modern statistics
|
|
0:09:14
|
or IOS command line
|
|
0:09:16
|
and MTP is not invoked after 8.
|
|
0:09:19
|
It's also not invoked for inbound early offer.
|
|
0:09:24
|
Again, 7.0 and before
|
|
0:09:27
|
or 7.x and before inbound, MTP was not required for
|
|
0:09:32
|
early for and it was required for outbound.
|
|
0:09:37
|
So keep note of those.
|
