|
0:00:12
|
Ok guys let's get started again.
|
|
0:00:14
|
And let's take a look at our demo.
|
|
0:00:17
|
Ok, so to begin with,
|
|
0:00:19
|
let's go to our CUCM administration web page
|
|
0:00:24
|
and create a gateway.
|
|
0:00:28
|
And shouldn't have any here.
|
|
0:00:33
|
So let's just create -- let's start with an H.323 gateway.
|
|
0:00:43
|
And we will make this H.323 gateway a corporate headquarter gateway to
|
|
0:00:48
|
the PSTN via an ISDN PRI.
|
|
0:00:52
|
So the device name will be the IP address that we'll be contacting.
|
|
0:00:57
|
It's the one place in CUCM where we have to put the IP address
|
|
0:01:02
|
as the device name.
|
|
0:01:06
|
So 177.1.254.1, we'll use the loopback 0
|
|
0:01:13
|
as always unless instructed to do otherwise.
|
|
0:01:16
|
And we'll call it corporate headquarter... Let's call it
|
|
0:01:21
|
corporate headquarter PRI gateway.
|
|
0:01:25
|
Device pool will be corporate headquarter of course.
|
|
0:01:28
|
MRGL can be obtained from the device pool.
|
|
0:01:31
|
Location can be obtained from the device pool.
|
|
0:01:34
|
AAR group, a lot of things we haven't looked at yet.
|
|
0:01:38
|
We'll look at those in a little bit.
|
|
0:01:44
|
MTP required. We don't want to do that unless
|
|
0:01:47
|
we absolutely know that we need to.
|
|
0:01:48
|
By default CUCM does have the ability to dynamically allocate
|
|
0:01:52
|
an MTP if needed.
|
|
0:01:54
|
There are very few times when you must check that.
|
|
0:01:57
|
But when those occasions arise
|
|
0:02:00
|
or if for some reason a call fails, you can always go back and
|
|
0:02:03
|
attempt to tick that box and see if that will
|
|
0:02:07
|
solve the problem.
|
|
0:02:09
|
But for most things that we'll do, if almost everything in the lab
|
|
0:02:12
|
we shouldn't need it because it can be dynamically added.
|
|
0:02:17
|
Retry video as audio. We're not too concerned about that.
|
|
0:02:20
|
We don't have actual video end points to test with in the lab.
|
|
0:02:23
|
Wait for far end H.245 TCS or Terminal Capability Set.
|
|
0:02:29
|
This is going to be important to -- it's obviously on by default
|
|
0:02:33
|
It's going to be important to consider if we're working with a CUBE.
|
|
0:02:38
|
Sometimes when we're working with CUBE, we don't have the
|
|
0:02:41
|
ability to really use terminal capabilities set because
|
|
0:02:48
|
we're not going H.245 end-to-end or H.225
|
|
0:02:52
|
H.323 end-to-end
|
|
0:02:54
|
And so H.245 won't be negotiated with the far end,
|
|
0:02:57
|
so it depends on what we're doing
|
|
0:03:00
|
in the situation where we're going between protocol,
|
|
0:03:05
|
signaling protocols from H.323 to SIP
|
|
0:03:07
|
in a CUBE element.
|
|
0:03:10
|
Or CUBE router.
|
|
0:03:11
|
We would uncheck this
|
|
0:03:13
|
because we're not really going to wait for the far end
|
|
0:03:15
|
to negotiate with us.
|
|
0:03:17
|
The actual CUBE might do negotiation with us.
|
|
0:03:22
|
Depends, we might want to use Fast- Start, it all depends on what we're doing
|
|
0:03:26
|
and it all depends on what's supported. So you can always try it with it on.
|
|
0:03:31
|
And the easy way to look at it is if something fails,
|
|
0:03:34
|
this would probably be one of the first things that I would uncheck.
|
|
0:03:38
|
I would not run and check media termination point required right away.
|
|
0:03:42
|
Ok, so I would first uncheck, wait for far end TCS
|
|
0:03:46
|
and see if that solves your problem.
|
|
0:03:49
|
This will probably more be related to if the call can be nailed up
|
|
0:03:56
|
or if the call actually sets up, but then doesn't negotiate
|
|
0:04:00
|
codecs or DTMF relay properly.
|
|
0:04:05
|
You could come back a second time and optionally look at this,
|
|
0:04:07
|
but for the most part we should be fine and right now
|
|
0:04:10
|
we're not going to introduce CUBE right away.
|
|
0:04:12
|
We will be introducing CUBE and in fact on the
|
|
0:04:16
|
corporate headquarter router, so this H.323 link may be
|
|
0:04:20
|
what we'll use to -- in fact it probably will be
|
|
0:04:24
|
what we'll use for our demonstration purposes
|
|
0:04:27
|
to go out to CUBE out to an ITSP, but for right now
|
|
0:04:32
|
it's going to be out to a PRI.
|
|
0:04:35
|
Ok, so we'll take a look at specifically we'll go through
|
|
0:04:41
|
and see how it affects us to leave it on or take it off.
|
|
0:04:44
|
So significant digits, this is going to be
|
|
0:04:46
|
under the subsection of call routing for inbound calls.
|
|
0:04:49
|
So we are going to want any calls that come in probably
|
|
0:04:53
|
to be reduced down to the four most significant digits which
|
|
0:04:56
|
are from the right.
|
|
0:04:59
|
If we have a situation where we're instructed
|
|
0:05:02
|
to route tail and hop off through our H.323 gateway
|
|
0:05:07
|
or trunk or any SIP or H.323 gateway or trunk
|
|
0:05:11
|
from another site, that would be a time when we'll probably
|
|
0:05:15
|
need all significant digits or basically say that all digits
|
|
0:05:19
|
are significant.
|
|
0:05:20
|
And use a calling search space to route the call over to a
|
|
0:05:26
|
translation pattern where we can then allow
|
|
0:05:30
|
calls that are destined for internal four-digit extensions
|
|
0:05:33
|
to be pruned down to four digits
|
|
0:05:35
|
or calls that are destined for actual other outbound trunks
|
|
0:05:41
|
other PSTN access or tail and hop off as I mentioned
|
|
0:05:47
|
we can route those to the appropriate route patterns or
|
|
0:05:50
|
translation patterns. Most likely translation patterns
|
|
0:05:57
|
as we need to, but for right now we're going to go ahead and put
|
|
0:06:01
|
this down to four significant digits for the inbound
|
|
0:06:03
|
so that we don't have to have a translation pattern yet.
|
|
0:06:07
|
And for calling search space we'll simply give it access to phones.
|
|
0:06:10
|
We wouldn't want to give it access to manager access
|
|
0:06:12
|
because then calls from the PSTN can go
|
|
0:06:15
|
directly to managers whereas if they go through CSS phones
|
|
0:06:18
|
remember that even with IPMA we have the IPMA route point
|
|
0:06:25
|
partition in this CSS for phones
|
|
0:06:29
|
and so calls in from the PSTN destined for a manager will
|
|
0:06:33
|
still have to go through that manager's assistant which is what we desire.
|
|
0:06:39
|
AAR calling search space, we'll look at that when we look at
|
|
0:06:41
|
high availability.
|
|
0:06:44
|
We can enable inbound Fast-Start and this does not hurt us in any way to do so.
|
|
0:06:48
|
It just says, 'We support it.'
|
|
0:06:50
|
We're obviously not forcing it
|
|
0:06:52
|
because Fast-Start is something that's
|
|
0:06:55
|
sent, not really -- well it's initiated, I should say, from the sender
|
|
0:07:02
|
not the receiver.
|
|
0:07:04
|
So the sender in the call setup
|
|
0:07:06
|
goes ahead and sends a Fast-Start message.
|
|
0:07:10
|
So if we enable this, we're simply saying we support it
|
|
0:07:12
|
which is a good idea.
|
|
0:07:14
|
Redirecting number for information element.
|
|
0:07:19
|
This is going to be good if we need to support the RDNs.
|
|
0:07:23
|
So the redirecting number for maybe a Voice Mail call or something like that.
|
|
0:07:29
|
We'll certainly take more look at that when we get to the messaging section.
|
|
0:07:35
|
For the most part we can leave the called party, calling party
|
|
0:07:41
|
information element, numbering plan
|
|
0:07:43
|
set to call manager
|
|
0:07:46
|
which means you need to go back to the previous entity
|
|
0:07:50
|
that handed the call to me, the gateway,
|
|
0:07:52
|
so this is for outbound calls.
|
|
0:07:53
|
I should clarify.
|
|
0:07:56
|
So go back to the previous entity inside of CUCM
|
|
0:08:00
|
that handed the call to you
|
|
0:08:02
|
which is probably a route list or actually route group
|
|
0:08:05
|
within a route list, so route list details
|
|
0:08:08
|
see if that information for called or calling type or plan
|
|
0:08:12
|
was changed there. If not there, then go back to the route pattern,
|
|
0:08:16
|
see if it was changed there, if not, go back to the translation
|
|
0:08:20
|
pattern and actually whatever was changed to the translation
|
|
0:08:24
|
pattern takes effect immediately.
|
|
0:08:26
|
But just leaving it at call manager means essentially
|
|
0:08:31
|
accept whatever we've already been told for this field.
|
|
0:08:35
|
Obviously if we configure something here, this will override.
|
|
0:08:39
|
Now there is one thing that can override the gateway
|
|
0:08:42
|
and that is the called party transformation pattern or CSS.
|
|
0:08:55
|
Ok, so we have this idea of a called and calling party.
|
|
0:08:58
|
Actually we're not going to get into the idea, the concept of this yet.
|
|
0:09:01
|
So I really don't want to even maybe begin talking about this.
|
|
0:09:05
|
This we will get into in great detail in dial plan.
|
|
0:09:09
|
So display IE delivery if we want to have
|
|
0:09:13
|
any sort of calling name display, we need display IE.
|
|
0:09:18
|
So the information element and calling name will be stuffed
|
|
0:09:22
|
inside display IE.
|
|
0:09:25
|
Now if this were an MGCP gateway
|
|
0:09:28
|
we would have to choose between display IE
|
|
0:09:31
|
and facility IE
|
|
0:09:34
|
in terms of where we want to stuff the calling name.
|
|
0:09:38
|
And really that would be determined based on the
|
|
0:09:40
|
type of ISDN switch that we're using.
|
|
0:09:44
|
This being an H.323 gateway,
|
|
0:09:46
|
we don't care about ISDN. We are abstracted from ISDN
|
|
0:09:51
|
If you remember back to the slide
|
|
0:09:53
|
the TDM signaling protocol only goes between the PSTN
|
|
0:09:59
|
and the voice gateway.
|
|
0:10:00
|
And that's where ISDN determines
|
|
0:10:02
|
should the calling name be stuffed into display
|
|
0:10:06
|
information element or into the facility information element
|
|
0:10:10
|
or IE
|
|
0:10:12
|
For H.323, they're all going to be in the display IE.
|
|
0:10:15
|
And the gateway is dynamically mapped display to display.
|
|
0:10:20
|
Display to facility can also be mapped dynamically
|
|
0:10:24
|
and the current IOS gateways are intelligent enough to do that.
|
|
0:10:28
|
There are also additional commands that we can use
|
|
0:10:31
|
to dive down and do all sorts of extra things.
|
|
0:10:38
|
Ok, but we definitely need to have this checked if we want
|
|
0:10:42
|
to have calling name display.
|
|
0:10:44
|
Again, redirecting number. We just saw this, but
|
|
0:10:46
|
that was under inbound subsection and here we're
|
|
0:10:49
|
under the outbound. Probably a good thing to have.
|
|
0:10:52
|
Enable outbound Fast-Start, so this is not just saying
|
|
0:10:55
|
support it, this is saying use it. And choose the codec that will
|
|
0:10:59
|
be used to state what codec it is that we wish to negotiate
|
|
0:11:06
|
in the H.225 setup.
|
|
0:11:08
|
Remember that doing this
|
|
0:11:11
|
forces us to have an MTP.
|
|
0:11:12
|
This is one of the situations where we have to utilize an MTP,
|
|
0:11:16
|
so we would go up and say
|
|
0:11:19
|
media termination point required.
|
|
0:11:21
|
And you'll actually see that when we get to the SIP gateway
|
|
0:11:23
|
if we enable SIP Early-Offer it will really actually will be grayed
|
|
0:11:28
|
out and not allow us to do that until we choose media termination point required.
|
|
0:11:33
|
So we probably don't want to have this checked.
|
|
0:11:38
|
And then we have incoming calling party settings.
|
|
0:11:40
|
Again, things we'll get to in the dial plan section.
|
|
0:11:44
|
Ok, so let's go ahead and say save.
|
|
0:11:47
|
Reset the gateway
|
|
0:11:51
|
within CUCM to have it take effect.
|
|
0:11:58
|
And again remember that we will not see it registered.
|
|
0:12:00
|
It will always say unknown. The IP address should show up,
|
|
0:12:04
|
but the status will always say unknown.
|
|
0:12:09
|
And there's really nothing that we have to do over
|
|
0:12:12
|
on the actual gateway side except to configure some
|
|
0:12:16
|
form of an inbound dial peer.
|
|
0:12:19
|
Ok, so if we were to send a call out through this gateway,
|
|
0:12:24
|
for instance if I go and just create a, let's say, a route pattern.
|
|
0:12:31
|
And let's make sure we don't have any.
|
|
0:12:33
|
Nope, so let's create one.
|
|
0:12:34
|
And just say let's say 911
|
|
0:12:39
|
It's in the internal DNs. Actually let's just
|
|
0:12:41
|
leave it in the non partition for right now.
|
|
0:12:44
|
The gateway will point to directly will be the H.323
|
|
0:12:48
|
gateway we just set up. We'll say route this pattern.
|
|
0:12:52
|
That looks all fine.
|
|
0:12:54
|
We'll say save.
|
|
0:13:01
|
If we now bring up our Variphy control
|
|
0:13:12
|
and let's bring up just corporate headquarter phone here.
|
|
0:13:23
|
And we go to dial
|
|
0:13:25
|
actually let's go to our gateway and say
|
|
0:13:27
|
debug ccapi
|
|
0:13:34
|
in out
|
|
0:13:39
|
whoops
|
|
0:13:41
|
Ok.
|
|
0:13:43
|
debug voice ccapi and out
|
|
0:13:50
|
And let's just dial 911
|
|
0:13:57
|
It's not going to route anywhere, but we do see information come to us.
|
|
0:14:03
|
So we see that information came from Jack Shepherd.
|
|
0:14:06
|
Whoops scrolled up a little too far.
|
|
0:14:09
|
Or down.
|
|
0:14:10
|
From the ANI or calling number of 1001
|
|
0:14:13
|
to the destination of 911
|
|
0:14:20
|
And we see other -- whoops
|
|
0:14:22
|
See other information about type
|
|
0:14:25
|
and -- I keep hitting the scroll button on accident
|
|
0:14:29
|
sorry
|
|
0:14:31
|
about calling type, about called information
|
|
0:14:34
|
type of number unknown.
|
|
0:14:37
|
NPI is unknown.
|
|
0:14:39
|
Or the plan, numbering plan indicator.
|
|
0:14:44
|
I could also undebug all and say debug voip
|
|
0:14:50
|
dial peer
|
|
0:14:56
|
and let's just clear off the screen.
|
|
0:14:58
|
And try that call again. I'm just going to hit redial over here.
|
|
0:15:04
|
And of course there was no match, but if we scroll up
|
|
0:15:07
|
we'll see that
|
|
0:15:12
|
our associate incoming peer core resulted in no match.
|
|
0:15:17
|
So after all rules, we couldn't match any inbound dial peer.
|
|
0:15:23
|
If we configured an outbound dial peer, we could possibly match with zero,
|
|
0:15:28
|
but
|
|
0:15:35
|
outgoing dial peer would certainly not match unless
|
|
0:15:36
|
we had actually configured one, so we didn't have an outbound
|
|
0:15:39
|
dial peer match either, so
|
|
0:15:42
|
it wouldn't be difficult to -- let's go ahead and set up
|
|
0:15:45
|
our gateway side of this, our ISDN.
|
|
0:15:47
|
So let's go to our controller and if we do sh run | s controllers
|
|
0:15:56
|
Let's just to | s control
|
|
0:15:58
|
and we've got a T1 0/0/0 that we can see is shut down
|
|
0:16:03
|
even if we didn't see the description
|
|
0:16:05
|
we do see another controller, but it's setup as a channel group.
|
|
0:16:09
|
This is a data circuit.
|
|
0:16:11
|
So this is the only other one we have available.
|
|
0:16:14
|
We're going to go ahead and say pri-group timeslots
|
|
0:16:21
|
1 through 3 is what we actually available to us based on our DSPs.
|
|
0:16:29
|
We could add a few more channels, but we can't have
|
|
0:16:31
|
a full T1 in this particular case. In the real lab you should have
|
|
0:16:35
|
a full T1, at least you have enough DSPs to create one
|
|
0:16:39
|
just depending on what the lab requirements state.
|
|
0:16:43
|
And we'll say -- that's all we're going to say actually.
|
|
0:16:47
|
We're not using NFAS
|
|
0:16:49
|
or Network Facilities Application Specific D-Channel.
|
|
0:16:55
|
What we can do with this is if we actually had multiple
|
|
0:16:59
|
T1s or -- I think it works with T1s as well.
|
|
0:17:03
|
Multiple T1s, let's say we had five
|
|
0:17:06
|
and the carrier supports this, then we can bond all of those
|
|
0:17:10
|
together and use all of those B-Channels, essentially
|
|
0:17:13
|
instead of having five D-Channels one for each T1
|
|
0:17:18
|
PRI, we could have one D-Channel and we would gain an additional four
|
|
0:17:24
|
B-Channels instead of having to use that extra channel as
|
|
0:17:28
|
a D-Channel, a Data channel
|
|
0:17:30
|
So we can bond them together with NFAS
|
|
0:17:32
|
and again the carrier has to support it because they
|
|
0:17:36
|
have to be doing the exact same thing on their side.
|
|
0:17:37
|
So you'd probably pay a little additional for that.
|
|
0:17:40
|
It makes more sense when you have a lot of PRIs
|
|
0:17:44
|
maybe 20 or something instead of having -- you're essentially
|
|
0:17:47
|
getting a whole new T1 for almost the price of
|
|
0:17:51
|
just the 20
|
|
0:17:54
|
Ok, service would be if we're going to add service MGCP
|
|
0:17:58
|
that's not what this gateway is
|
|
0:17:59
|
we'll probably make our Branch 1 our MGCP gateway.
|
|
0:18:02
|
So as soon as I hit this and then no shut
|
|
0:18:05
|
assuming that I had the proper framing and line coding which
|
|
0:18:10
|
we haven't gone back and used the old framing of
|
|
0:18:14
|
super frame and line coding of AMI in quite some time so
|
|
0:18:18
|
we're using extended super frame
|
|
0:18:20
|
and bipolarite zero substitution or B8ZS of course.
|
|
0:18:24
|
So we see that not only did the controller change state to up,
|
|
0:18:28
|
but an interface popped up
|
|
0:18:30
|
which is just like our controller
|
|
0:18:32
|
but on a serial, so 0/0/0:23 counting canonically this is the
|
|
0:18:38
|
24th channel, this is the D-Channel.
|
|
0:18:40
|
So this is where we would configure anything pertaining to the D-Channel.
|
|
0:18:43
|
And we also actually had a voice interface change state to up.
|
|
0:18:49
|
So our voice interface is 0/0/0
|
|
0:18:52
|
and we also see :23(1), (2) and (3)
|
|
0:18:55
|
these are our B-Channels, so if we do sh ip int br now
|
|
0:19:00
|
we're going to see not only serial 0/0/0:23,
|
|
0:19:05
|
but :0, 1 and 2 and this is the first, second and third B-Channel
|
|
0:19:10
|
because we said timeslots 1 through 3
|
|
0:19:14
|
So
|
|
0:19:21
|
Here we've got our controller.
|
|
0:19:23
|
We're going to take a look at
|
|
0:19:27
|
0/0/0 which this will actually show us all of our voice stuff
|
|
0:19:34
|
our controller, our D-Channel interface and our voice port.
|
|
0:19:40
|
Voice port is where we can configure specific things to Layer 3
|
|
0:19:44
|
such as our digit manipulation or a companding type
|
|
0:19:50
|
things of that nature.
|
|
0:19:56
|
D-Channel we can specify switch type and things of that nature.
|
|
0:19:59
|
We did actually -- I should have noted we did have to have a switch
|
|
0:20:03
|
type defined globally before we brought up the controller.
|
|
0:20:07
|
And one other thing I'd like to mention, in lab you'll be
|
|
0:20:10
|
using -- in fact let me just do sh run, sorry, do sh inventory
|
|
0:20:18
|
Here in our racks just because we had them around and there's
|
|
0:20:22
|
really no point in replacing them simply for the one additional
|
|
0:20:27
|
command that you get in the lab.
|
|
0:20:28
|
We had Vwick-2 port multiflex trunk T1s and in the Branch 2
|
|
0:20:36
|
router we have an E1 or a 2-port E1.
|
|
0:20:38
|
In the real lab they use Vwick 2-2 MFT
|
|
0:20:43
|
or Vwick 2-1 MFT depending on whether they have one or two ports per card.
|
|
0:20:49
|
But the point is, is that they are Vwick 2 or the second generation.
|
|
0:20:54
|
At the end of the 1 MFT or 2 MFT
|
|
0:20:56
|
it will say -T1/E1
|
|
0:21:00
|
And then typically it'll say T1/E1-T1 or E1
|
|
0:21:07
|
and what that is, is the Vwick 2s have the ability to be either
|
|
0:21:13
|
T1s or E1s software configurable.
|
|
0:21:18
|
And that will go and configure the actual Layer 1 characteristics
|
|
0:21:24
|
of the card that's inserted in the router.
|
|
0:21:28
|
So before you'll even see a controller,
|
|
0:21:32
|
you may not -- in fact you'll probably have one MFTs
|
|
0:21:35
|
because your data channel will certainly be up, but before you'll see anything
|
|
0:21:39
|
you will -- or you might even have a serial, and old serial for
|
|
0:21:44
|
your actual data link, but you will have to configure
|
|
0:21:48
|
the word or the command 'card-type'
|
|
0:21:52
|
Now I don't actually have it even as a command in here
|
|
0:21:54
|
because I don't have Vwick 2s.
|
|
0:21:57
|
And IOS is smart enough in many circumstances or
|
|
0:22:00
|
many situations not to include commands even in question mark
|
|
0:22:05
|
context sensitive help
|
|
0:22:09
|
unless it sees certain types of hardware present.
|
|
0:22:14
|
So I don't even show the command 'card-type' but in the real lab
|
|
0:22:17
|
you will need to because you are guaranteed to have Vwick 2s
|
|
0:22:21
|
you'll need to issue the card-type command in order to choose
|
|
0:22:26
|
what card 0/0/0 or 0/0/1 or
|
|
0:22:30
|
wherever it happens to be placed, what card you want and how you
|
|
0:22:34
|
want it configured. Whether you want it as T1 or as an E1
|
|
0:22:39
|
Ok, so you'll have to do that and after you do that, then
|
|
0:22:42
|
the controller will show up.
|
|
0:22:44
|
So in other words, if I did
|
|
0:22:48
|
this command
|
|
0:22:49
|
or even do sh run | controller,
|
|
0:22:53
|
I wouldn't even see controller T1 or controller E1 pop up until
|
|
0:22:57
|
I issue that card-type command.
|
|
0:22:59
|
Ok, so that is one difference from our racks that you'll have to consider.
|
|
0:23:07
|
Ok, and then you would also have to have the global ISDN switch type
|
|
0:23:12
|
which we obviously already had and I believe is standard default
|
|
0:23:17
|
in the config, so pretty sure. You may want to change it before
|
|
0:23:21
|
you bring up your PRI; however, even if you don't change it before
|
|
0:23:28
|
you bring up the PRI, you can certainly go back into the actual
|
|
0:23:31
|
controller and switch it. In fact, you don't have access to the PSTN
|
|
0:23:36
|
in the real world or in the lab.
|
|
0:23:41
|
So they will have to tell you what ISDN type they're using
|
|
0:23:45
|
and I'm just going to look here real quick to see what this particular
|
|
0:23:48
|
load is set to. For my corporate headquarter site I believe it's
|
|
0:23:54
|
5 ESS, but let's see, sh run... Let's do sh ip int br
|
|
0:24:05
|
and I believe it's 0/0:23, so
|
|
0:24:08
|
sh run
|
|
0:24:11
|
oops
|
|
0:24:17
|
Ah! It's set to NI, ok
|
|
0:24:20
|
what about 0/4
|
|
0:24:25
|
23 which is my Branch 1 also set to NI and what about
|
|
0:24:30
|
what is it, 0/2:15?
|
|
0:24:37
|
is primary net 5, ok
|
|
0:24:40
|
So in the real lab they would tell you that, so we are going to use
|
|
0:24:42
|
NI for this particular example.
|
|
0:24:48
|
We can also set things here such as ISDN
|
|
0:24:56
|
there's a lot of ISDN commands obviously,
|
|
0:24:59
|
but we can do things such as ISDN information
|
|
0:25:03
|
sorry ISDN outgoing
|
|
0:25:08
|
information element
|
|
0:25:10
|
and after we do information element we can do a lot of things
|
|
0:25:13
|
like redirecting number, so in other words, are we
|
|
0:25:17
|
going to support RDNs or redirecting number as part of the outgoing
|
|
0:25:23
|
information elements?
|
|
0:25:26
|
We can also do ISDN outgoing. We could say display.
|
|
0:25:33
|
There's really no difference between doing this command, outgoing IE display
|
|
0:25:37
|
and outgoing the one that they make right here at this level
|
|
0:25:42
|
display IE. It's the same thing. They just figured that since most
|
|
0:25:46
|
people want to support calling name, they're going to have
|
|
0:25:49
|
that -- they're going to be using that, so they saved you
|
|
0:25:51
|
having to type IE space display or question mark
|
|
0:25:55
|
and sifting through all the rest.
|
|
0:25:57
|
Ok, it's quite a common one to be used.
|
|
0:26:04
|
So we've added a couple ISDN specific information bits
|
|
0:26:07
|
and this will as we mentioned map dynamically between ISDN
|
|
0:26:10
|
display information element and H.323
|
|
0:26:14
|
Remember that H.323 is built by the same group of people,
|
|
0:26:18
|
the ITUT, and it was built and based on ISDN Q.931
|
|
0:26:32
|
Ok, so we're not going to do anything more with the voice port just yet.
|
|
0:26:37
|
We'll go ahead and create a... Yep let's go ahead and create
|
|
0:26:39
|
a dial peer for voice, we'll call it 100 and it's going to be of the type voip
|
|
0:26:50
|
and we'll say incoming called number .
|
|
0:26:52
|
so any inbound numbers
|
|
0:26:55
|
that are coming from any type that is VoIP and the session
|
|
0:27:01
|
protocol that is -- well we have Cisco, multicast and SIPV2
|
|
0:27:07
|
We don't want multicast for voice conferencing.
|
|
0:27:10
|
We don't want the Cisco session protocol and we don't want SIP.
|
|
0:27:12
|
We want H.323, that's because that's the default of this dial peer
|
|
0:27:16
|
and there's actually no configurable command for it.
|
|
0:27:19
|
So if you configured one of these others like SIP
|
|
0:27:22
|
all you would do is the no version of that
|
|
0:27:24
|
in order to take this back to an H.323 dial peer.
|
|
0:27:28
|
So we don't need any session protocol
|
|
0:27:32
|
Incoming called number is good enough to...
|
|
0:27:35
|
do sh run | s voice 100
|
|
0:27:43
|
I did that because of this portion.
|
|
0:27:46
|
So we've got a dial peer that can at the default codec
|
|
0:27:50
|
so do sh dial-peer 100
|
|
0:27:55
|
oops
|
|
0:27:56
|
Let's end out. sh dial-peer
|
|
0:28:02
|
voice 100
|
|
0:28:04
|
We can see there's a lot of information in here.
|
|
0:28:09
|
5, 6, 7 pages worth,
|
|
0:28:11
|
but I can always pipe that to an output modifier
|
|
0:28:16
|
And I'll pipe it to include, let's say, g729
|
|
0:28:23
|
And I can see the codec is G.729
|
|
0:28:26
|
I could have just done codec.
|
|
0:28:37
|
Actually I would need to do h\. if I wanted to just find that.
|
|
0:28:41
|
Alright, so it's...
|
|
0:28:44
|
Is it H.225?
|
|
0:28:46
|
There we go.
|
|
0:28:49
|
No, that's not actually what I want.
|
|
0:28:58
|
So session protocol is Cisco which is the H.323
|
|
0:29:02
|
that's the default protocol there.
|
|
0:29:07
|
Ok, so there's a lot of information in the show dial-peer
|
|
0:29:10
|
a lot of it can be useful. Output modifiers can really
|
|
0:29:13
|
be your friend in terms of seeing what the current codec is
|
|
0:29:21
|
all sorts of stuff, I mean there's just tons of information in here
|
|
0:29:24
|
incoming, outgoing, COR list, translation profiles
|
|
0:29:28
|
all things that we'll get to
|
|
0:29:31
|
QoS settings, EF if we're looking at signaling.
|
|
0:29:36
|
Remember I said the default signaling was AF 31
|
|
0:29:40
|
for all VoIP dial peers and even MGCP, so that might
|
|
0:29:44
|
be one of the things we wanted to do was jump into dial peer
|
|
0:29:48
|
and say voice 100 and say IP QoS
|
|
0:29:53
|
dsp for... let's say cs3
|
|
0:29:59
|
for signaling
|
|
0:30:02
|
and media's already set to EF
|
|
0:30:19
|
Oh! DSCP was in caps, that's why it didn't show up when I did dscp
|
|
0:30:24
|
There we go.
|
|
0:30:25
|
And now we've changed the signaling to CS3
|
|
0:30:29
|
We're not going to do any destination patterns or
|
|
0:30:31
|
anything like that because we haven't really...
|
|
0:30:33
|
Well actually you know what, we can go ahead and do destination
|
|
0:30:35
|
pattern. We know what's going to be coming in from the PSTN.
|
|
0:30:39
|
And I haven't really laid out any particular task topics, but if you were
|
|
0:30:45
|
looking at a lab scenario or whatever, they of course would tell you what the
|
|
0:30:50
|
carrier is going to be routing in in terms of digits.
|
|
0:30:52
|
What DID digits you're going to "own" at that site.
|
|
0:30:59
|
So I'll just be the voice of that rather than laying them out on paper.
|
|
0:31:03
|
And by the way, if you prefer that type of a -- or even want to
|
|
0:31:07
|
see something similar to that our volume 1 goes into all of that
|
|
0:31:11
|
it's based on the CCIE Voice deep dive, so we lay out
|
|
0:31:16
|
full tasks. I think there's -- I'm trying to think how many tasks there are.
|
|
0:31:21
|
I think there's over 300 some tasks, maybe more
|
|
0:31:26
|
for the volume 1 and we go into about a 115 hours of video demo
|
|
0:31:32
|
for all that a really detailed level. Lay out exactly the specifics, so
|
|
0:31:37
|
for this corporate headquarter site according to the dial plan
|
|
0:31:40
|
that we have loaded on our PSTN, the inbound number from
|
|
0:31:44
|
the PSTN will be 2065011XXX or 1000 series numbers.
|
|
0:31:57
|
So depending on how we want it to route that to the
|
|
0:32:02
|
to the CUCM. If we wanted to route it as the full ten digits
|
|
0:32:06
|
we could certainly do so.
|
|
0:32:08
|
If we wanted to modify it before it gets to the CUCM,
|
|
0:32:13
|
we could do that as well.
|
|
0:32:15
|
So assuming that we didn't want to modify it, we could
|
|
0:32:18
|
jump back into our dial peer
|
|
0:32:23
|
and say that the destination pattern would be
|
|
0:32:27
|
206 -- actually let's do ^ which is a regex or regular expression
|
|
0:32:32
|
indicating the beginning of a line.
|
|
0:32:35
|
So 2065011...$
|
|
0:32:41
|
Dollar sign being regular expression indicating the end of a line.
|
|
0:32:45
|
You could say end of a string. It's actually the end of a line. It's fine.
|
|
0:32:49
|
So we've got anything beginning with 206501 and specifically
|
|
0:32:54
|
1 series numbers
|
|
0:32:57
|
because there are additional numbers that are
|
|
0:33:00
|
2065012 or 3 that don't belong to us.
|
|
0:33:05
|
These are really the only three variable
|
|
0:33:07
|
most significant digits that we have to work with.
|
|
0:33:10
|
This is a static or something that cannot change.
|
|
0:33:12
|
So these are what will be pointed to or toward the CUCM.
|
|
0:33:19
|
And in that case if we're talking about pointing toward the CUCM
|
|
0:33:22
|
earlier we had an incoming call number coming from CUCM
|
|
0:33:26
|
on this dial peer, but if we're going toward the CUCM
|
|
0:33:29
|
we should have a session target of IPv4
|
|
0:33:35
|
and if I can type here again looking to my right, but typing straight down
|
|
0:33:39
|
IPv4 and we'll do 177.1.10.10
|
|
0:33:48
|
so pointing to that IP address.
|
|
0:33:52
|
And we can choose to use the preference command if we're going
|
|
0:33:56
|
to have multiple dial peers and of course it would be a good idea.
|
|
0:33:59
|
let's do sh run | s voice 100
|
|
0:34:04
|
It would be a good idea to have multiple dial peers.
|
|
0:34:09
|
101
|
|
0:34:11
|
with the same destination pattern and with the
|
|
0:34:14
|
session target of .20
|
|
0:34:18
|
We don't need incoming called number.
|
|
0:34:21
|
because we don't need redundant dial peers for inbound calls from
|
|
0:34:26
|
CUCM to the H.323 gateway.
|
|
0:34:29
|
There's no benefit in that.
|
|
0:34:31
|
The redundancy of a dial peer is well -- the dial peer
|
|
0:34:36
|
is dependent on the router being up, the loopback being up
|
|
0:34:40
|
which really means any of the routable interfaces are up.
|
|
0:34:42
|
At least routable to CUCM.
|
|
0:34:45
|
So in our case one Fast Ethernet 0/0
|
|
0:34:51
|
The call control sub system being up.
|
|
0:34:56
|
And that's it, I mean it's not like an extra dial peer is going to help
|
|
0:35:02
|
us in any way, so you could put this again on the next dial peer
|
|
0:35:05
|
it's probably not going to hurt, it just might add to the
|
|
0:35:10
|
troubleshooting a little bit if you put an inbound voice translation rule
|
|
0:35:13
|
so inbound incoming into the dial peer which means it's coming in
|
|
0:35:17
|
from CUCM.
|
|
0:35:20
|
But you forgot to put it on the other one.
|
|
0:35:22
|
That could be a problem. If it's outbound voice
|
|
0:35:25
|
translation rule or anything outbound, you will have to apply
|
|
0:35:27
|
it to both because they both go to separate places.
|
|
0:35:31
|
But coming in, it doesn't matter where it's coming from
|
|
0:35:33
|
it will at least meet this one dial peer if the router is available to take calls.
|
|
0:35:39
|
So we won't copy and paste that, but we will copy and paste
|
|
0:35:43
|
the QoS for DSCP and this is things that the router is
|
|
0:35:47
|
obviously originating, so this is traffic coming from the router
|
|
0:35:51
|
going out to CUCM.
|
|
0:35:52
|
We could even have a whole third VoIP dial peer
|
|
0:35:55
|
just for calls from CUCM
|
|
0:35:58
|
and then just make these two outbound to CUCM
|
|
0:36:01
|
if we wanted to just to keep things maybe a little bit more
|
|
0:36:05
|
separated and maybe a little more clear.
|
|
0:36:10
|
Hopefully it's fine to just have this, hopefully everyone understands.
|
|
0:36:14
|
If anyone has any questions, please at any point go ahead and ask.
|
|
0:36:21
|
Ok.
|
|
0:36:25
|
So, since we have the same destination pattern
|
|
0:36:31
|
we could certainly use a preference command for calls
|
|
0:36:36
|
again this is for outbound
|
|
0:36:38
|
so for calls from the IOS router to CUCM
|
|
0:36:43
|
we could say -- by default the default preference is zero
|
|
0:36:50
|
and it climbs up to ten.
|
|
0:36:54
|
Lower numbers being more preferable.
|
|
0:36:56
|
So zero would be the first picked and we could change
|
|
0:37:00
|
this to maybe say preference 1
|
|
0:37:10
|
So here I've got my two dial peers 100
|
|
0:37:13
|
and 101
|
|
0:37:14
|
And 101 has the same destination pattern, different target, but
|
|
0:37:18
|
it's got preference 1
|
|
0:37:21
|
That's certainly one way to do it.
|
|
0:37:22
|
Or maybe I wanted all calls to go to the Sub
|
|
0:37:24
|
first and then to the Pub.
|
|
0:37:26
|
Well, I could jump this up to preference 2
|
|
0:37:28
|
or I could just drop this to preference 0 and make
|
|
0:37:30
|
dial peer 100 preference 1
|
|
0:37:33
|
either way
|
|
0:37:34
|
I'm actually just going to go ahead and take preference back to zero.
|
|
0:37:38
|
So when I do sh run again they don't show up.
|
|
0:37:42
|
And what I'm going to do instead is go to dial-peer
|
|
0:37:47
|
hunt, so space hunt question
|
|
0:37:50
|
and I see that I've got different hunting choices.
|
|
0:37:53
|
So by default zero is -- I should say zero is the default, so If I do
|
|
0:37:58
|
do sh run | to include, if I can remember to hit include
|
|
0:38:07
|
dial-peer hunt, I see it doesn't show up.
|
|
0:38:10
|
If I change dial-peer hunt to option 4
|
|
0:38:14
|
and I do sh run
|
|
0:38:16
|
it shows up in the running config.
|
|
0:38:18
|
If I change it back to zero, and do sh run
|
|
0:38:24
|
it doesn't show up because it's the default.
|
|
0:38:26
|
So looking back here zero says here is what we should
|
|
0:38:29
|
use to choose which dial peer to route to.
|
|
0:38:31
|
First look for the longest match in the phone number.
|
|
0:38:34
|
Then if you've got two that have the same longest -- same exact match
|
|
0:38:39
|
whatever, however long that match is
|
|
0:38:41
|
if they evaluate to the same, then choose explicit preference.
|
|
0:38:46
|
So that's where if I had preference 0 here and
|
|
0:38:49
|
preference 1, that would be the tie breaker.
|
|
0:38:52
|
But if you don't have or if all things are equal
|
|
0:38:55
|
the preferences are equal, as they are,
|
|
0:38:57
|
then choose a random selection.
|
|
0:38:59
|
Just randomly we'll go back and forth.
|
|
0:39:02
|
And you might think this would load balance, but
|
|
0:39:04
|
random is truly random, so it could choose 100, 101
|
|
0:39:08
|
100, 101, 101, 101,100, 100, 100, 100, 100, 100, 100, 101, 100, 100, 101
|
|
0:39:15
|
it could go back and forth at any random intervals. There's nothing
|
|
0:39:19
|
to say it will load balance back and forth.
|
|
0:39:21
|
If we wanted it to load balance,
|
|
0:39:24
|
if we note, option 1 is just the same for the first two tie breaker criteria,
|
|
0:39:30
|
but the last is least recent use.
|
|
0:39:32
|
So that actually will load balance.
|
|
0:39:34
|
And then there's all sorts of other things including
|
|
0:39:36
|
just random selection. Now even if we chose
|
|
0:39:38
|
something such as random selection and we add a 100 dial peers
|
|
0:39:42
|
it would still have to match in some way.
|
|
0:39:45
|
It won't just choose any dial peer
|
|
0:39:48
|
it would have to match, so if did 911
|
|
0:39:52
|
it would at least -- if I had a dial peer that had destination pattern
|
|
0:39:56
|
.T and destination pattern 9..
|
|
0:40:01
|
and destination pattern 911
|
|
0:40:03
|
all three of those match, but if I had also a fourth destination pattern
|
|
0:40:07
|
a fourth dial peer with a destination pattern 234
|
|
0:40:09
|
that in no way matches 911, so that couldn't be chosen.
|
|
0:40:12
|
But any of the other three would be chosen
|
|
0:40:15
|
at any random selection.
|
|
0:40:17
|
I don't know why you would use that, but it's there.
|
|
0:40:19
|
So I'm going to actually choose dial peer hunt 1
|
|
0:40:22
|
and this will load balance.
|
|
0:40:28
|
voice 10
|
|
0:40:30
|
Ok, so whoops
|
|
0:40:31
|
I meant to do section
|
|
0:40:34
|
rather than include
|
|
0:40:37
|
Ok, so this dial peer hunt algorithm combined with
|
|
0:40:40
|
two equal longest matches and equal preferences
|
|
0:40:43
|
will load balance back and forth between them.
|
|
0:40:46
|
And in large designs where you'd have three or four or five maybe
|
|
0:40:51
|
six subscribers and those would be the only ones that you would
|
|
0:40:54
|
have call processing engines send calls to, you would
|
|
0:40:57
|
probably want to round robin load balance across them.
|
|
0:41:02
|
Ok,
|
|
0:41:04
|
so if we wanted, we could just go ahead and set up
|
|
0:41:07
|
dial-peer voice 1 pots
|
|
0:41:12
|
and say destination pattern 911
|
|
0:41:17
|
and port 0/0/0: I'm sorry -- yeah 0/0/0
|
|
0:41:27
|
no :23
|
|
0:41:29
|
and
|
|
0:41:33
|
let's just do sh run
|
|
0:41:36
|
so we've got our inbound dial peers and our outbound dial peer.
|
|
0:41:40
|
And we're not going to get into dial plan yet, but I just created one
|
|
0:41:44
|
so that we can test it.
|
|
0:41:45
|
We wrote the router config and let's sh deb
|
|
0:41:49
|
we've got debug VoIP dial peer on
|
|
0:41:51
|
so let's just go ahead and hit redial
|
|
0:41:54
|
on that... whoops
|
|
0:41:56
|
call again
|
|
0:42:02
|
And just see
|
|
0:42:04
|
that
|
|
0:42:06
|
call came in.
|
|
0:42:09
|
Incoming dial peer was 100
|
|
0:42:11
|
the called number was 911
|
|
0:42:17
|
If we scroll down
|
|
0:42:18
|
enough, we've got a list of matched outgoing dial peers
|
|
0:42:22
|
dial peer 1
|
|
0:42:25
|
and the result was a success.
|
|
0:42:29
|
Ok, so the call did go out the dial peer.
|
|
0:42:33
|
We just hung up.
|
|
0:42:36
|
Alright, so we've already wrote that router config.
|
|
0:42:39
|
Let's undebug all.
|
|
0:42:42
|
And let's
|
|
0:42:47
|
move over to our Router 2
|
|
0:42:51
|
let's do sh run so our Branch 1 router
|
|
0:42:55
|
do sh | in isdn
|
|
0:43:01
|
and we do have a global ISDN primary NI
|
|
0:43:05
|
Let's go ahead and config t
|
|
0:43:07
|
controller T1 0/0/0
|
|
0:43:12
|
and we'll do
|
|
0:43:15
|
PRI group timeslots
|
|
0:43:17
|
You know what, one other thing I forgot to do over on corporate headquarter
|
|
0:43:20
|
that I don't want to move beyond before we do it
|
|
0:43:25
|
is the time.
|
|
0:43:27
|
So if we do sh run | s controller
|
|
0:43:33
|
we don't see anything related to time. We could do
|
|
0:43:37
|
clock source internal.
|
|
0:43:39
|
I'm sorry we could do clock source internal, but we also
|
|
0:43:42
|
could do clock source line which is what we would typically do.
|
|
0:43:47
|
But network clock participate and select are two commands
|
|
0:43:53
|
that we generally want to use for the newer Vwick cards
|
|
0:43:57
|
to select our time source
|
|
0:44:02
|
where we want to participate with or who we want to use as
|
|
0:44:06
|
a default selection, so let's say priority 1 is going to be
|
|
0:44:11
|
controller T1 0/0/0
|
|
0:44:15
|
And we also want to do a network clock participate
|
|
0:44:19
|
for the wick zero.
|
|
0:44:22
|
How do we know it's wick zero, well first of all it's not
|
|
0:44:25
|
a name card, it's not a network module slot.
|
|
0:44:30
|
How do we know that? Well do sh inventory
|
|
0:44:34
|
we can tell that our two-port T1
|
|
0:44:37
|
voice interface daughter card is on slot 0
|
|
0:44:42
|
Subslot 0
|
|
0:44:45
|
So, we could say slot 0, we could try to I should say.
|
|
0:44:54
|
But we see that we only have the ability to configure slot 1 and 2
|
|
0:44:57
|
This is because slot 0 is the motherboard and it's already participating per se.
|
|
0:45:02
|
Actually what it's doing is it's giving you the option for wick
|
|
0:45:07
|
and those wick cards are 0 through 3 or the 4
|
|
0:45:12
|
slots, the four Hwick or wick, so WAN interface card
|
|
0:45:17
|
Hwick high speed WAN interface card
|
|
0:45:19
|
or Vwick voice WAN interface card
|
|
0:45:21
|
that are available on the backboard
|
|
0:45:23
|
on the motherboard.
|
|
0:45:25
|
So if it's slot 0 which is the motherboard subslot 0
|
|
0:45:28
|
then it's actually going to be wick 0
|
|
0:45:30
|
So we could do wick 3, it'll tell us it's empty
|
|
0:45:33
|
wick 1, it'll tell us it's empty,
|
|
0:45:35
|
but wick 0, it will take.
|
|
0:45:39
|
And timing is very important when you're dealing with
|
|
0:45:43
|
a TDM or Time Division Multiplexing network.
|
|
0:45:46
|
If you don't have time synced up, then how can you mux on time?
|
|
0:45:51
|
Or demux?
|
|
0:45:53
|
Ok, so PRI group time slots
|
|
0:45:56
|
and we might as -- we'll add those network clock commands as well.
|
|
0:46:00
|
1 through 3
|
|
0:46:02
|
and no shut
|
|
0:46:06
|
we'll jump out and say
|
|
0:46:08
|
or I guess we could
|
|
0:46:10
|
jump back in and say clock source line
|
|
0:46:13
|
exit network clock select
|
|
0:46:18
|
1 priority 1 T1 0/0/0
|
|
0:46:24
|
network clock participate
|
|
0:46:27
|
wick 0, it's in the same slot.
|
|
0:46:33
|
And we could save ourselves some time by coming over here
|
|
0:46:42
|
and copying and pasting.
|
|
0:46:58
|
And in fact we could save ourselves some time even with the
|
|
0:47:14
|
oops let me go back even one more
|
|
0:47:16
|
and just save ourselves some time even just with this
|
|
0:47:20
|
of course we would probably want to put this into Notepad.
|
|
0:47:31
|
And edit it so that it's proper for our environment.
|
|
0:47:34
|
So this is...
|
|
0:47:43
|
5126022
|
|
0:47:53
|
and this is fine.
|
|
0:47:58
|
All this should be fine.
|
|
0:48:02
|
And in fact let's just do... No that's fine.
|
|
0:48:05
|
So we'll just go ahead and copy this
|
|
0:48:08
|
and paste that in
|
|
0:48:12
|
and the only thing I want to go back and change is
|
|
0:48:15
|
session protocol.
|
|
0:48:18
|
We're going to have this one
|
|
0:48:20
|
well you know what I said we'd make Branch 1 our MGCP.
|
|
0:48:26
|
That's no problem we'll make Branch 2.
|
|
0:48:31
|
Nah you know what, I do actually want to make
|
|
0:48:33
|
Branch 1 our MGCP
|
|
0:48:35
|
to vary it from other demos.
|
|
0:48:37
|
So let's just -- let's go back and say
|
|
0:48:41
|
no dial peer voice 100
|
|
0:48:46
|
no 101
|
|
0:48:47
|
and no dial peer 1
|
|
0:48:49
|
so we just got rid of those dial peers and actually what we're going to have to do
|
|
0:48:52
|
so this is a good example if you misconfigure something like...
|
|
0:48:55
|
do sh | s 0/0/0
|
|
0:49:00
|
If you misconfigure something such as PRI group time slots
|
|
0:49:04
|
1 through 3 and you forget to hit service
|
|
0:49:08
|
MGCP
|
|
0:49:09
|
here's the step that you have to take to reverse that.
|
|
0:49:12
|
You first have to jump into the voice port and shut it down.
|
|
0:49:16
|
You next have to jump into the interface serial 0/0/0:23
|
|
0:49:21
|
and shut that down.
|
|
0:49:24
|
Then you have to jump into the controller
|
|
0:49:30
|
and shut that down.
|
|
0:49:31
|
And then you can say no PRI group timeslots
|
|
0:49:34
|
1 through 3
|
|
0:49:37
|
If you don't do that, it will -- IOS will bark at you and tell you
|
|
0:49:41
|
that you had to go back and do a few additional things.
|
|
0:49:44
|
So PRI group timeslots 1-3
|
|
0:49:48
|
It'll say voice port not shut down or ISDN D-Channel
|
|
0:49:52
|
not in shut down state.
|
|
0:49:55
|
And we're going to say service MGCP.
|
|
0:50:00
|
By the way, if you forget to add the service MGCP
|
|
0:50:03
|
there will be another nice notifier which is when it creates the D-Channel.
|
|
0:50:07
|
Ok, so this D-Channel right here
|
|
0:50:11
|
and you go to put the command ISDN bind l3 or bind Layer 3
|
|
0:50:16
|
bind q931 to CCM manager.
|
|
0:50:23
|
The option, so we'll just jump into it now.
|
|
0:50:25
|
Interface serial 0/0/0:23
|
|
0:50:29
|
and say isdn bind-l3
|
|
0:50:33
|
to CCM
|
|
0:50:34
|
This option won't be there.
|
|
0:50:36
|
This option will not be there if you forgot to put in service MGCP.
|
|
0:50:40
|
You'll only see backhaul or IUA backhaul
|
|
0:50:43
|
Ok, so we want to send it to CCM manager.
|
|
0:50:52
|
Ok, so
|
|
0:51:01
|
let me just do a show here real quick.
|
|
0:51:03
|
Question: if I'm using the MGCP
|
|
0:51:07
|
do I need any of those other ISDN commands that I had?
|
|
0:51:11
|
So for instance...
|
|
0:51:18
|
they might be back too far here.
|
|
0:51:21
|
Do I need commands like ISDN
|
|
0:51:26
|
outgoing display IE?
|
|
0:51:32
|
Well, while it's being controlled by MGCP
|
|
0:51:34
|
the answer is no. You do not need them.
|
|
0:51:37
|
However if the gateway is going to fall back to local router control
|
|
0:51:42
|
of that PRI for SRST situations
|
|
0:51:47
|
and it's going to need to support calling name
|
|
0:51:49
|
then yes you do need it. Go ahead and put it in now
|
|
0:51:53
|
so that you don't have to jump into the router
|
|
0:51:56
|
interface and do that when you're in SRST mode.
|
|
0:51:59
|
Most likely you won't be out at that remote site anyway
|
|
0:52:01
|
and the WAN will be down,
|
|
0:52:03
|
but yes you would need that when in fallback.
|
|
0:52:06
|
Before fallback you wouldn't need it.
|
|
0:52:16
|
Ok,
|
|
0:52:19
|
so we could also put in the isdn outgoing ie redirecting if we wanted
|
|
0:52:28
|
which is actually supported by default.
|
|
0:52:31
|
Ok, so
|
|
0:52:39
|
at this point let's jump back and go to our MGCP commands.
|
|
0:52:45
|
So mgcp call-agent
|
|
0:52:48
|
and we're going to put in 177.1. we want this to be
|
|
0:52:52
|
the primary call agent, so let's do .10.20 which is the Subscriber.
|
|
0:52:58
|
And this is where I said don't put in anything else.
|
|
0:53:03
|
The UDP port or service type or anything. Just hit enter.
|
|
0:53:09
|
It'll fill in the rest for you.
|
|
0:53:14
|
Mainly it will fill in the service type MGCP version 0.1
|
|
0:53:22
|
We need mgcp dtmf relay
|
|
0:53:26
|
and we're going to use for VoIP
|
|
0:53:29
|
we're going to use codec all
|
|
0:53:33
|
mode out of band
|
|
0:53:41
|
We are going to
|
|
0:53:44
|
say mgcp -- there's an mgcp bind command.
|
|
0:53:47
|
We didn't look at the H.323 bind.
|
|
0:53:51
|
We can go back and do that at the corporate headquarter Router 1
|
|
0:53:56
|
But for MGCP we can certainly bind control and media.
|
|
0:53:59
|
So signaling and our RTP
|
|
0:54:02
|
to a source interface such as let's say loopback 0
|
|
0:54:06
|
This is typically a good idea.
|
|
0:54:10
|
So control and we'll do media as well.
|
|
0:54:13
|
However, there's something to be aware of and that is
|
|
0:54:17
|
when you enter these two commands and then
|
|
0:54:20
|
you say mgcp enter to turn this on
|
|
0:54:23
|
assuming you've already provisioned everything in your CUCM which
|
|
0:54:25
|
we haven't done quite yet and we will go do
|
|
0:54:30
|
It will actually register with the closest interface which
|
|
0:54:33
|
in this case would be a Fast Ether -- I'm sorry in this case we're over at Branch 1
|
|
0:54:37
|
it would be a serial interface.
|
|
0:54:38
|
The closest interface over to CUCM.
|
|
0:54:42
|
Just based on the routing table, so if I do sh ip route 177.1.10.10
|
|
0:54:50
|
or .20 it doesn't matter.
|
|
0:54:52
|
It's going to show me that it's going to route this traffic
|
|
0:54:54
|
via serial interface.
|
|
0:54:57
|
So the IP address of it serial 0/0/1:0.1 sub interface
|
|
0:55:05
|
that will be the IP address that it will register with.
|
|
0:55:08
|
Why? It's just an old bug.
|
|
0:55:10
|
So it's easy enough to fix do sh run | s mgcp
|
|
0:55:17
|
and the fix is very simple.
|
|
0:55:18
|
You simply say no mgcp
|
|
0:55:20
|
and you copy and paste these... whoops
|
|
0:55:24
|
copy and paste these commands right over top of themselves
|
|
0:55:27
|
it's almost like you have to kick it to get it to take it.
|
|
0:55:29
|
And then you can say mgcp
|
|
0:55:32
|
and now it will register with the proper loopback interface.
|
|
0:55:35
|
Ok, but be aware that, that is a bug that persists even
|
|
0:55:38
|
into the versions of IOS in the lab.
|
|
0:55:43
|
Ok, so we've got our mgcp dtmf relay and bind command.
|
|
0:55:51
|
We can configure our CCM manager commands.
|
|
0:55:54
|
So ccm manager mgcp
|
|
0:55:57
|
so tell the CCM manager application process to use MGCP mode.
|
|
0:56:05
|
Certainly ccm manager music on hold
|
|
0:56:08
|
since we had -- in fact I think we already did that
|
|
0:56:11
|
since we had multicast music on hold.
|
|
0:56:15
|
CCM manager fallback-mgcp
|
|
0:56:18
|
if we want to have an SRST mode where the router takes over.
|
|
0:56:23
|
So ccm manager fallback mgcp
|
|
0:56:27
|
In fact, before I hit enter on this let me do sh ccm or
|
|
0:56:34
|
do sh ccm manager
|
|
0:56:36
|
and notice -- first of all it's trying to registering
|
|
0:56:39
|
it's trying to register right now because it doesn't have
|
|
0:56:41
|
a configuration in CUCM to register with.
|
|
0:56:44
|
But notice that mgcp fallback mode is currently not selected.
|
|
0:56:53
|
There's a big difference between mgcp fallback
|
|
0:56:56
|
not selected and if I
|
|
0:56:58
|
put here ccm manager fallback mgcp
|
|
0:57:01
|
and then do this show command again
|
|
0:57:03
|
I now see that mgcp fallback mode is enabled,
|
|
0:57:07
|
but off currently.
|
|
0:57:09
|
When it's on it will show Enabled/ON
|
|
0:57:16
|
I can also do ccm manager redundant host
|
|
0:57:18
|
so this is where I'm going to add 177.1.10.10
|
|
0:57:23
|
for the Publisher as a fallback
|
|
0:57:25
|
now when I do sh ccm
|
|
0:57:27
|
previously I just saw registering with .20
|
|
0:57:30
|
because of the MGCP.
|
|
0:57:33
|
Now I see the primary is .20 and the backup
|
|
0:57:36
|
it says backup ready, but it's not really ready.
|
|
0:57:40
|
By the way this show ccm command
|
|
0:57:42
|
or show ccm manager
|
|
0:57:44
|
is -- let me scroll up just a little bit
|
|
0:57:45
|
is very useful because one of the first thing that comes up is
|
|
0:57:49
|
MGCP domain name
|
|
0:57:52
|
and it tells you Branch 1
|
|
0:57:53
|
Now the domain name is important because
|
|
0:57:56
|
you need to know how to register it to the call manager
|
|
0:58:00
|
when you actually create the MGCP gateway page
|
|
0:58:05
|
in the web page.
|
|
0:58:06
|
And it's going to ask you -- in fact let's just go over there real quick.
|
|
0:58:11
|
Won't do the whole thing. I'm not going to skip around too much
|
|
0:58:14
|
although it is a little bit of back and forth
|
|
0:58:19
|
inevitably.
|
|
0:58:20
|
For MGCP we choose the type of gateway.
|
|
0:58:23
|
So a show inventory would tell us that
|
|
0:58:25
|
that it's a 2811
|
|
0:58:29
|
Protocol is going to be MGCP. We're not using skinny.
|
|
0:58:32
|
That would only be for FXO or FXS.
|
|
0:58:33
|
And here it says domain name.
|
|
0:58:35
|
What do we enter here? Whatever show ccm tells us.
|
|
0:58:41
|
Branch 1
|
|
0:58:41
|
This is important because if there is a domain name
|
|
0:58:44
|
configured or in other words, IP domain name
|
|
0:58:50
|
like ine.com or something like that.
|
|
0:58:52
|
If I had that, then I'd do a show ccm
|
|
0:58:55
|
this changes this to Branch1.ine.com
|
|
0:59:00
|
I'm going to go ahead and take that out and say no
|
|
0:59:04
|
and then do the show again
|
|
0:59:06
|
but it's very important that those match.
|
|
0:59:07
|
MGCP commands are sent... whoops
|
|
0:59:13
|
MGCP instructions in communication are sent back and forth
|
|
0:59:20
|
with the fully qualified domain name of the router or at least
|
|
0:59:23
|
as far as it know its own FQ DN
|
|
0:59:27
|
and then -- well actually it's the port numbers @
|
|
0:59:32
|
the at symbol, the domain name.
|
|
0:59:36
|
Or fully qualified domain name.
|
|
0:59:38
|
So whatever the router thinks it is, CUCM needs to think the same
|
|
0:59:42
|
and vice versa.
|
|
0:59:45
|
And while we're talking about that let's just choose a Pub Sub.
|
|
0:59:48
|
We've got Sub.
|
|
0:59:49
|
It's important because of the way the messages are sent back and forth.
|
|
0:59:55
|
And debug mgcp messages or packets actually
|
|
0:59:58
|
to see that information and how they're sent back and forth.
|
|
1:00:02
|
But if I do sh inventory
|
|
1:00:08
|
it's also very important that I know
|
|
1:00:10
|
where my voice cards that I want to control are.
|
|
1:00:14
|
So two port voice interface daughtercard on slot 0
|
|
1:00:18
|
Ok, so here we have module and slot 0 and module and slot 1
|
|
1:00:23
|
I'm going to choose the module, the only one for the four
|
|
1:00:27
|
Vwick or Voice wick motherboard.
|
|
1:00:32
|
And I'm going to press ISDN switch type
|
|
1:00:35
|
this would only be important if I was doing a full configuration
|
|
1:00:38
|
which is the CCM manager config server command
|
|
1:00:43
|
which we're not going to do because it configures
|
|
1:00:47
|
essentially too much for us.
|
|
1:00:50
|
Stuff that we'll have to go rip out later.
|
|
1:00:51
|
And then after slot 0 what's the subslot?
|
|
1:00:55
|
It's also 0
|
|
1:00:57
|
So it's important because it's going to name the messages
|
|
1:01:00
|
0/ -- it's a little more naming than that, it's actually DS1-0
|
|
1:01:10
|
with the slot 0 the sub unit or subslot
|
|
1:01:12
|
and we need to put in what it is,
|
|
1:01:14
|
so it was a Vwick-2MFT-T1
|
|
1:01:19
|
The actual naming of this card isn't actually so important
|
|
1:01:23
|
as the sub components that it will produce
|
|
1:01:26
|
and the naming of those.
|
|
1:01:28
|
But we'll just do what it says.
|
|
1:01:30
|
So Vwick-2
|
|
1:01:33
|
MFT-T1 versus what you'll see in the lab, will be these Vwick
|
|
1:01:38
|
Vwick-2 so the gen 2s of either 1 MFT or 2 MFT
|
|
1:01:42
|
and here's where you have the T1 or E1- and this is
|
|
1:01:47
|
is it configured as a T1 or is it configured as an E1
|
|
1:01:50
|
or is the two port configured as a T1 or an E1
|
|
1:01:55
|
Ok, so we'll just choose what this is.
|
|
1:01:56
|
And say save.
|
|
1:01:59
|
And now we have the proper 0/0/0 naming.
|
|
1:02:05
|
Ok, but that's the show inventory that's going to get us there.
|
|
1:02:10
|
Ok, we've pretty much actually configured most of what we need to do here.
|
|
1:02:13
|
Let's do sh run | s mgcp|ccm manager
|
|
1:02:21
|
and here we've got on our controller
|
|
1:02:25
|
our PRI time group so it turned up with the service MGCP.
|
|
1:02:29
|
We've got ccm manager fallback mgcp
|
|
1:02:32
|
redundant host, ccm manager mgcp
|
|
1:02:36
|
we've got mgcp enter
|
|
1:02:38
|
the call agent pointing to the primary
|
|
1:02:40
|
the proper version
|
|
1:02:42
|
we've got out of band dtmf relay
|
|
1:02:45
|
and the bind for loopback 0
|
|
1:02:49
|
So let's go ahead and at this point jump into our configuration on CUCM.
|
|
1:02:55
|
Protocol is going to be a PRI.
|
|
1:02:57
|
This T1 would be for a CAS circuit or channel associated signaling.
|
|
1:03:02
|
So this is the actual naming of the device name.
|
|
1:03:08
|
s 0 for slot 0, su 0 for sub unit
|
|
1:03:12
|
and then DS1-0 or the first DS1 or first T1
|
|
1:03:18
|
counting canonically at Branch 1
|
|
1:03:21
|
Device pool, we're at Branch 1
|
|
1:03:27
|
I can leave location to hub none because remember it will choose none
|
|
1:03:30
|
go back to the device pool and find its proper location.
|
|
1:03:37
|
PRI NI 2 for national.
|
|
1:03:40
|
Or primary NI 2
|
|
1:03:41
|
We're the user side.
|
|
1:03:43
|
We can choose how to do the channel selection
|
|
1:03:46
|
bottom-up or top-down.
|
|
1:03:48
|
Top-down begins with one and goes down to either
|
|
1:03:55
|
23 or 30 depending on how many B-Channels you have.
|
|
1:04:00
|
Bottom-up comes the other way.
|
|
1:04:03
|
By the way, ascending begins with one
|
|
1:04:05
|
and goes to 23, descending
|
|
1:04:07
|
goes from 23 up, so bottom-up equals descending
|
|
1:04:11
|
and top-down equals ascending.
|
|
1:04:17
|
Ok, I like to uncheck inhibit restarts at PRI initialization.
|
|
1:04:23
|
The reason I like to do this is that if I leave this checked
|
|
1:04:28
|
I could actually hit once this is saved and I'll have a reset button
|
|
1:04:32
|
I could make a change on CUCM's side
|
|
1:04:34
|
hit reset and think that the change has taken effect,
|
|
1:04:37
|
but I don't really know yet if it's fully taken effect
|
|
1:04:42
|
if it's actually finished resetting that sub section of the CCM process.
|
|
1:04:50
|
The gateway within the CCM process.
|
|
1:04:52
|
If I uncheck this inhibit restarts at PRI initialization
|
|
1:04:59
|
the router it will actually send a Q.931 message
|
|
1:05:04
|
especially if I have over here do debug isdn q931 turned on
|
|
1:05:13
|
I will see it send a Q.39 restart for each B-Channel and
|
|
1:05:18
|
I'll see the PSTN respond with an ack, and acknowledgement for each B-Channel.
|
|
1:05:23
|
Now this can be really useful because from the router side
|
|
1:05:28
|
in a easy to read a debug that I'm always going to have running
|
|
1:05:35
|
I'll quickly see when that reset has actually taken effect
|
|
1:05:38
|
and when I know that I can go ahead and test my call again.
|
|
1:05:41
|
Now I wouldn't do this in real life.
|
|
1:05:43
|
In real life I would leave this checked, inhibit the restarts.
|
|
1:05:49
|
But in a test environment I would uncheck this.
|
|
1:05:52
|
Enable status poll is only needed if you're using a fairly antiquated
|
|
1:05:57
|
service parameter called B-Channel maintenance
|
|
1:05:59
|
that we don't need to use.
|
|
1:06:01
|
Significant digits again the same four unless we're told otherwise.
|
|
1:06:05
|
Calling search space that can get to the phones for now.
|
|
1:06:09
|
We'll leave the rest of this. Here's where we have Display IE.
|
|
1:06:14
|
Now PRI NI 2 actually uses facility IE for calling name.
|
|
1:06:21
|
Whether the carrier is going to support that, in other words
|
|
1:06:24
|
whether in the real lab your carrier is going to be a Cisco IOS router.
|
|
1:06:31
|
Just depends on how they have it setup.
|
|
1:06:33
|
Cisco IOS routers are terribly forgiving when it comes to a lot of things
|
|
1:06:37
|
including ISDN specifications and switch types.
|
|
1:06:41
|
So they may have it setup where...
|
|
1:06:45
|
If you just do display IE, it most likely will work.
|
|
1:06:48
|
They could have it setup if they're telling you to use primary NI
|
|
1:06:51
|
which is the most common switch type in North America at least.
|
|
1:06:56
|
Net 5 being the most common in most of Europe.
|
|
1:07:00
|
By the way, that's also the same as the PRI Euro.
|
|
1:07:09
|
They could have it setup to just not care and so display IE could work just fine.
|
|
1:07:14
|
They could have it setup to only accept
|
|
1:07:17
|
the proper type of information element for calling name
|
|
1:07:22
|
based on the switch type that you have
|
|
1:07:24
|
which like I said PRI NI 2
|
|
1:07:27
|
is going to be -- also called PRI National is going to be
|
|
1:07:31
|
facility IE.
|
|
1:07:32
|
So here's the simple thing.
|
|
1:07:35
|
Just check Display IE.
|
|
1:07:37
|
And see if it works.
|
|
1:07:39
|
And if it's an H.323 gateway something like that,
|
|
1:07:42
|
then obviously make sure you have it enabled on your
|
|
1:07:44
|
ISDN interface.
|
|
1:07:47
|
But if it doesn't work, then you may have to say
|
|
1:07:51
|
send calling name and facility IE.
|
|
1:07:53
|
Now if you were to say send calling name and facility IE,
|
|
1:07:56
|
remember we are controlling the PRI protocol
|
|
1:07:59
|
we're controlling Q.931
|
|
1:08:01
|
whoops sorry
|
|
1:08:02
|
all this is Q.931 specific control
|
|
1:08:06
|
because it's backhauled to us.
|
|
1:08:08
|
Sorry about that constant scroll.
|
|
1:08:12
|
My mouse is a little too sensitive. I have to change the settings on it.
|
|
1:08:19
|
So if we were in fallback mode and you said well wait a minute...
|
|
1:08:22
|
Well first of all, should we ever choose both?
|
|
1:08:24
|
You typically will never choose both.
|
|
1:08:27
|
But let's say we're in fallback mode
|
|
1:08:30
|
and we had done do sh run... let's see
|
|
1:08:35
|
do sh run int ser0/0/0:23
|
|
1:08:41
|
We had done isdn outgoing display IE
|
|
1:08:44
|
but if we were in fallback mode and this was truly NI 2
|
|
1:08:48
|
we would have the proper type which would be ISDN outgoing
|
|
1:08:58
|
information element.
|
|
1:09:03
|
Facility there it is.
|
|
1:09:06
|
Ok, and we're going to support the facility IE, we're not going to do
|
|
1:09:08
|
any code set shifts.
|
|
1:09:13
|
But we would also have ISDN
|
|
1:09:17
|
supplementary service name calling.
|
|
1:09:22
|
Not main calling
|
|
1:09:23
|
name calling.
|
|
1:09:27
|
And we would do the same thing over on the corporate headquarter
|
|
1:09:29
|
side because that's an H.323 gateway with PRI NI 2
|
|
1:09:42
|
So redirecting number yes. IE facility and name calling
|
|
1:09:46
|
we would not have display IE,
|
|
1:09:49
|
so it just depends on what the carrier is supporting.
|
|
1:09:54
|
And again in this case, this is for MGCP fallback
|
|
1:09:59
|
in the H.323 corporate headquarter Router 1
|
|
1:10:03
|
that would be for normal operations that we would switch it to that.
|
|
1:10:07
|
So you can always try one and switch it to the other.
|
|
1:10:09
|
Right now our PSTN is not setup for the name calling
|
|
1:10:12
|
I don't believe. I can actually go back and take a look real quick.
|
|
1:10:21
|
No it is.
|
|
1:10:22
|
It is actually setup for the name calling.
|
|
1:10:24
|
Ok.
|
|
1:10:25
|
So we will do this.
|
|
1:10:26
|
We will choose...
|
|
1:10:29
|
We'll choose facility IE.
|
|
1:10:31
|
In real life if you were working on a PRI NI2
|
|
1:10:34
|
or National and you chose display IE
|
|
1:10:38
|
you would see in the Q.931 message depending on how the carrier had the
|
|
1:10:42
|
switch type setup
|
|
1:10:45
|
or the specifics of the switch setup
|
|
1:10:47
|
you would definitely see bad information element
|
|
1:10:50
|
as part of your receive Q.931 messages
|
|
1:10:54
|
from the PSTN. You might even not get the call to nail up.
|
|
1:10:58
|
It might refuse the call based on a bad information element.
|
|
1:11:02
|
But that's in real life.
|
|
1:11:04
|
We'll support RDNs or Redirecting Number
|
|
1:11:07
|
outbound and inbound.
|
|
1:11:10
|
And we don't need this.
|
|
1:11:12
|
We would need that maybe if we're going to a PBX.
|
|
1:11:17
|
And so that should be it.
|
|
1:11:18
|
The product specific. This is going to be essentially Layer 1 information
|
|
1:11:23
|
line coding, framing, clock
|
|
1:11:25
|
first of all it's already set right, but...
|
|
1:11:27
|
Echo cancellation
|
|
1:11:29
|
But all this would really only take effect again if
|
|
1:11:31
|
we were using the ccm manger config server command.
|
|
1:11:35
|
So I'm going to say save.
|
|
1:11:37
|
Reset the gateway to take effect.
|
|
1:11:39
|
We'll definitely do that.
|
|
1:11:44
|
Reset, reset
|
|
1:11:51
|
And we can go back and jump in just to see if it's registered.
|
|
1:11:54
|
It's not registered yet.
|
|
1:11:56
|
A simple no mgcp
|
|
1:12:00
|
wait until it's torn down
|
|
1:12:02
|
mgcp
|
|
1:12:03
|
should take care of it.
|
|
1:12:09
|
Let's go back to find list and show end points.
|
|
1:12:15
|
Ok, it still says unregistered.
|
|
1:12:16
|
Shows the IP address as the loopback.
|
|
1:12:22
|
That's good.
|
|
1:12:27
|
Let's just take a look at our whole configuration here.
|
|
1:12:29
|
Let's do sh run | s 0/0/0|mgcp|ccm-manager
|
|
1:12:45
|
Ok, we've got -- oh our controller is shut down.
|
|
1:12:49
|
That would definitely do it.
|
|
1:12:51
|
no shut
|
|
1:12:52
|
no mgcp
|
|
1:12:54
|
mgcp
|
|
1:12:58
|
write our router config
|
|
1:13:02
|
and do a find
|
|
1:13:05
|
and there we see the loopback 0 for Branch 1 Router 2 is registered
|
|
1:13:10
|
with the Subscriber.
|
|
1:13:13
|
Ok, so all should be good there and we should be able to make
|
|
1:13:15
|
calls out of there once we get our dial plan up.
|
|
1:13:19
|
And here's what we saw: our restarts.
|
|
1:13:22
|
So for each channel we saw a restart and we transmitted
|
|
1:13:27
|
a restart and we received a restart acknowledgement.
|
|
1:13:31
|
And I like seeing those. I think they're quite useful.
|
|
1:13:36
|
Ok let's change our corporate headquarters very quickly
|
|
1:13:41
|
to interface serial 0/0/0:23
|
|
1:13:47
|
no isdn outgoing display-ie
|
|
1:13:53
|
instead we're going to do isdn outgoing ie facility
|
|
1:14:00
|
and isdn supplementary service name calling
|
|
1:14:05
|
I know your mother told you not to call names
|
|
1:14:07
|
it's not nice to do name calling, but
|
|
1:14:10
|
in this case it's Ok.
|
|
1:14:13
|
Little humor to see if anyone's still awake.
|
|
1:14:16
|
Ok, so let's switch over to Branch 2
|
|
1:14:18
|
We've got our MGCP gateway up.
|
|
1:14:20
|
We don't need any dial peers there. Let's switch over to Branch 2
|
|
1:14:24
|
And we'll bring up our E1 over here,
|
|
1:14:28
|
so card type except that we're not using Vwick-2s.
|
|
1:14:31
|
We will use network clock
|
|
1:14:35
|
select
|
|
1:14:36
|
and this is priority 1, but an E1
|
|
1:14:40
|
0/0/0
|
|
1:14:42
|
network clock participate
|
|
1:14:46
|
wic 0 again
|
|
1:14:50
|
controller e1 0/0/0
|
|
1:14:56
|
Let's do no shut
|
|
1:14:57
|
pri group time slots
|
|
1:14:59
|
1 through 3
|
|
1:15:05
|
clock source line
|
|
1:15:09
|
interface serial0/0/0:15
|
|
1:15:17
|
15 being our D-Channel
|
|
1:15:21
|
and
|
|
1:15:23
|
let's take a look at
|
|
1:15:25
|
ISDN, here we are going to do isdn outgoing display-ie
|
|
1:15:31
|
and isdn outgoing information element redirecting number
|
|
1:15:39
|
We don't need any bind there.
|
|
1:15:42
|
And let's grab our dial peers
|
|
1:15:45
|
and let's change the number that we were going to use for Branch 1
|
|
1:15:49
|
Here depending on how much we're going to send over to CUCM
|
|
1:15:54
|
Let's say...
|
|
1:15:56
|
Well the carrier is going to be sending in
|
|
1:16:02
|
well the carrier actually sends in a couple things
|
|
1:16:03
|
and this is going to be our SIP trunk, so we're going to wait and see
|
|
1:16:07
|
what the carrier sends in because the carrier actually sends in a
|
|
1:16:10
|
couple things depending on how we're dialing into this site.
|
|
1:16:14
|
So we're going to wait until dial plan to add the destination patterns.
|
|
1:16:18
|
Ok, we will go ahead and have the incoming called number
|
|
1:16:21
|
so this will be our inbound dial peer from CUCM.
|
|
1:16:27
|
I'm actually going to add session protocol
|
|
1:16:31
|
and I wouldn't recommend typing it out like this in
|
|
1:16:34
|
Notepad necessarily.
|
|
1:16:36
|
But SIP V2
|
|
1:16:39
|
I like to use the router for the first one to make sure
|
|
1:16:41
|
I get all the syntax right, then copy and paste it in Notepad.
|
|
1:16:46
|
So I'm going to get rid of the destination pattern.
|
|
1:16:48
|
I'll still use the session target because these will be
|
|
1:16:51
|
outbound dial peers eventually.
|
|
1:16:53
|
In fact that's all this one will do.
|
|
1:16:55
|
And I'm not going to add -- you know what I'll just add
|
|
1:17:01
|
destination pattern 112
|
|
1:17:04
|
is going to be my emergency services
|
|
1:17:06
|
for that site.
|
|
1:17:08
|
And 0/0/0:15, so let's go ahead and add these dial peers.
|
|
1:17:17
|
Ok.
|
|
1:17:20
|
One of the things that I haven't added yet we can add is a
|
|
1:17:22
|
voice class codec.
|
|
1:17:26
|
We'll just give it the tag of 1
|
|
1:17:28
|
And for the voice class codec let's say that the codec
|
|
1:17:32
|
preference is always going to be the higher codec
|
|
1:17:37
|
of g711ulaw
|
|
1:17:44
|
and codec preference 2
|
|
1:17:47
|
could be alaw if we were going to use it.
|
|
1:17:55
|
And codec preference 3
|
|
1:17:58
|
could be g729 r8
|
|
1:18:04
|
and so do sh run | s voice class
|
|
1:18:11
|
so I've got my voice class codec.
|
|
1:18:13
|
And if I jump into my dial peer
|
|
1:18:16
|
voice 100
|
|
1:18:19
|
and say voice class codec 1
|
|
1:18:23
|
and then do the same for dial peer 101
|
|
1:18:28
|
and I'm going to add these to
|
|
1:18:32
|
what I'm going to do over at Router 1 for H.323 as well
|
|
1:18:37
|
I don't need them for my MGCP one: because I don't have dial peers.
|
|
1:18:40
|
But two: even when I have dial peers for fallback
|
|
1:18:42
|
to SRST, those are going to be TDM or POTS style peers, not VoIP.
|
|
1:18:47
|
If they were VoIP pointing to call manager
|
|
1:18:49
|
I would have MGCP communications, but I don't have communications.
|
|
1:18:54
|
So I don't need VoIP dial peers to call manager.
|
|
1:18:58
|
And I haven't actually created voice class codec, that's a good point,
|
|
1:19:01
|
over on Router 1, so let's copy and paste that.
|
|
1:19:10
|
And then put that in and also put it in 101 as well.
|
|
1:19:15
|
And the reason I want to do that, if I don't put any
|
|
1:19:18
|
voice class codec in there, I'm going to be at g729 r8 always.
|
|
1:19:22
|
That might be fine for over the WAN, but for on LAN
|
|
1:19:29
|
corporate headquarter, gateway to corporate headquarter phones
|
|
1:19:32
|
my region 8 a maximum of 711
|
|
1:19:35
|
so I can negotiate that. Maybe my test requirements
|
|
1:19:38
|
stated that you should use 711 for local LAN
|
|
1:19:42
|
and 729 between sites.
|
|
1:19:44
|
But G.729 would have been forced without the usage
|
|
1:19:49
|
of a voice class codec to allow negotiation for a dial peer.
|
|
1:19:52
|
So it's very important that you don't forget to put those
|
|
1:19:55
|
on your VoIP dial peers pointing to
|
|
1:19:58
|
CUCM from either H.323 or SIP gateways.
|
|
1:20:04
|
Alright, so let's clear off this router.
|
|
1:20:07
|
Clear off the screen and do sh run | s 0/0/0
|
|
1:20:16
|
or...
|
|
1:20:20
|
voice
|
|
1:20:24
|
sorry that's a colon. OR voice
|
|
1:20:29
|
so I've got my select
|
|
1:20:31
|
my voice class codec
|
|
1:20:35
|
I've got my voice-card. We don't need to do dsp farm
|
|
1:20:39
|
or dsp tdm pooling because we only have our DSPs on the
|
|
1:20:44
|
same motherboard as our Vwics.
|
|
1:20:47
|
If they were on a different network module, that's when
|
|
1:20:49
|
we need the dspn farm or dspn tdm pooling, same thing
|
|
1:20:54
|
command
|
|
1:20:56
|
for our serial D-Channel interface
|
|
1:21:00
|
we've got our primary net 5
|
|
1:21:02
|
we've got our isdn incoming-voice voice
|
|
1:21:05
|
display-ie
|
|
1:21:07
|
outgoing ie redirecting number
|
|
1:21:12
|
We've got our actual voice port where we call that from our
|
|
1:21:19
|
POTS dial peer.
|
|
1:21:20
|
The only one we've created so far.
|
|
1:21:23
|
And we've got our dial peer voice 100 and 101 pointing
|
|
1:21:26
|
back to Pub and Sub.
|
|
1:21:27
|
Ah! One of the other things I didn't add was the
|
|
1:21:30
|
config t dial-peer 1 to load balance between them.
|
|
1:21:37
|
Ok, so we should be pretty good.
|
|
1:21:39
|
We can debug isdn q931
|
|
1:21:43
|
from all routers at this point.
|
|
1:21:48
|
I think we're already doing it from over here.
|
|
1:21:53
|
In fact let's just clean off the screen and tell it do it,
|
|
1:21:56
|
so it's obvious. Oops.
|
|
1:22:01
|
So it's obviously on.
|
|
1:22:03
|
And we should be able to go -- let's go ahead and
|
|
1:22:07
|
clear this off and let's go back to CUCM
|
|
1:22:11
|
and add a gateway.
|
|
1:22:13
|
We can't add a gateway for SIP, but we can add a trunk.
|
|
1:22:18
|
So add new.
|
|
1:22:20
|
SIP trunk
|
|
1:22:22
|
device protocol's obviously SIP.
|
|
1:22:25
|
The device name we can call it whatever we want.
|
|
1:22:27
|
Branch 2 gateway.
|
|
1:22:31
|
Or even gateway_branch2
|
|
1:22:34
|
MRGL location, those will get it from the device pool.
|
|
1:22:37
|
MTP not required.
|
|
1:22:41
|
Incoming calling party settings we'll talk about on dial plan.
|
|
1:22:45
|
Call routing information, remote party ID and asserted identity.
|
|
1:22:50
|
this gets into essentially remote party ID is dealing with
|
|
1:22:56
|
the calling number, connected number,
|
|
1:23:01
|
display, privacy if privacy is on or not.
|
|
1:23:07
|
If essentially -- one of the good things to use here is help for this page.
|
|
1:23:12
|
And it'll tell you.
|
|
1:23:16
|
Essentially if we turn SIP privacy to none,
|
|
1:23:19
|
then no matter whether we had a translation pattern that said
|
|
1:23:22
|
the caller ID or connected name was restricted
|
|
1:23:27
|
if we say none it's going to ignore that.
|
|
1:23:30
|
If we say ID, then the trunk on the other side
|
|
1:23:34
|
we're asking it to support the SIP privacy ID because
|
|
1:23:37
|
of course the information elements are still there
|
|
1:23:39
|
with the connected name and calling name.
|
|
1:23:42
|
We're just flagging them as restricted.
|
|
1:23:44
|
The progress indicator is saying restricted
|
|
1:23:49
|
for that information element essentially.
|
|
1:23:51
|
It's not really an information element, it's not H.323 but
|
|
1:23:53
|
for that type of information I should say it's flagged as restricted.
|
|
1:23:57
|
And we're telling the carrier to honor it.
|
|
1:24:01
|
to... Let me just bring this up here.
|
|
1:24:14
|
Here we go. I just did a search for privacy.
|
|
1:24:16
|
So here we go.
|
|
1:24:25
|
So none. The SIP trunk includes the privacy none header.
|
|
1:24:28
|
And implies that this overrides anything that comes from CUCM.
|
|
1:24:32
|
So from route pattern or translation patterns.
|
|
1:24:37
|
ID. It includes the privacy header ID and implies that
|
|
1:24:39
|
presentation is restricted for both name, calling name
|
|
1:24:43
|
and number, a caller ID.
|
|
1:24:45
|
This overrides whatever happens previously in CUCM.
|
|
1:24:49
|
And ID-Critical not only turns on the header for privacy ID, critical
|
|
1:24:55
|
but it implies presentation's restricted for both name and number and
|
|
1:24:58
|
the label critical basically means that services requested for this
|
|
1:25:03
|
message are critical and if the network cannot provide these,
|
|
1:25:06
|
then the request should be rejected, so the carrier
|
|
1:25:09
|
or whoever's on the other side should reject the message
|
|
1:25:11
|
if they can't honor restricting what we told them to restrict.
|
|
1:25:16
|
But of course if we just leave it to default, then whatever we set previously
|
|
1:25:20
|
in CUCM at a translation pattern where we might say restrict the name,
|
|
1:25:25
|
but don't restrict the number, something like that
|
|
1:25:27
|
that honored because it's set at the default.
|
|
1:25:31
|
Asserted identity means we're asserting that we
|
|
1:25:32
|
are who we say we are -- whoops
|
|
1:25:34
|
and there's two different types PAI and PPI and you can read
|
|
1:25:38
|
about those here as well.
|
|
1:25:40
|
They just have to do with the type of header that gets sent.
|
|
1:25:46
|
So whether it's privacy asserted identity or privacy preferred identity.
|
|
1:25:52
|
Significant digits inbound is four.
|
|
1:25:55
|
This is one of the fields whenever you do CUCM
|
|
1:25:57
|
BAT inserts, it almost always goofs up this significant digits on
|
|
1:26:02
|
at least SIP trunks and most gateways as well.
|
|
1:26:04
|
Calling search space. We'll leave it for phones for now.
|
|
1:26:10
|
Redirecting number diversion header inbound.
|
|
1:26:12
|
There are some issues, some bugs related to diversion header
|
|
1:26:17
|
inbound or outbound. We'll take a look at those when we
|
|
1:26:19
|
get to messaging if they become relevant.
|
|
1:26:22
|
In this case, I don't think with this being at Branch 2 they'll be relevant
|
|
1:26:27
|
actually it might be, it might come into play.
|
|
1:26:29
|
So we'll take a look at these as we come to messaging and
|
|
1:26:32
|
deal more with redirected numbers.
|
|
1:26:35
|
We'll turn them on for right now though.
|
|
1:26:39
|
And then SIP information. If this is an SRV or a Service Record in DNS
|
|
1:26:44
|
this destination pattern can be IP or DNS
|
|
1:26:47
|
provided that the server is DNS enabled and if it's not
|
|
1:26:50
|
you can go to command line, so SSH into the Pub and Sub
|
|
1:26:54
|
you would need to do it on both.
|
|
1:26:56
|
And turn on DNS support, so point it to an IP
|
|
1:27:01
|
sorry point it to a DNS server
|
|
1:27:03
|
and probably turn on a domain name for each server as well.
|
|
1:27:07
|
But once you've enabled that, this can be a host name
|
|
1:27:13
|
fully qualified domain name or it can be an IP address.
|
|
1:27:17
|
We're going to go ahead and put in just an IP address right now.
|
|
1:27:22
|
In my deep dives I go into not only fully qualified domain name,
|
|
1:27:26
|
but a service record where the service record being
|
|
1:27:30
|
different from DNS. Notice that port will disappear if I hit SRV
|
|
1:27:34
|
it changes to zero and I could change it back to 5060, but it's
|
|
1:27:37
|
just going to go back to zero.
|
|
1:27:39
|
Basically saying, all the information in terms of
|
|
1:27:43
|
which server I should route it to in which priority
|
|
1:27:46
|
because I might have multiple different preferences for
|
|
1:27:50
|
priority or weights for them so that I can have redundancy
|
|
1:27:54
|
or load balancing or anything like that
|
|
1:27:59
|
as well as the actual port and protocol, so TCP or UDP in
|
|
1:28:03
|
what port number you should connect to.
|
|
1:28:04
|
All of that will be obtained from the DNS service record.
|
|
1:28:10
|
But right now we're just going to use this.
|
|
1:28:12
|
Notice that the MTP preferred originating codec is grayed out.
|
|
1:28:16
|
This is SIP Early-Offer outbound.
|
|
1:28:21
|
So there is no Early-Offer inbound that we have to enable.
|
|
1:28:23
|
It is supported or it's enabled.
|
|
1:28:27
|
If I check MTP required,
|
|
1:28:29
|
then this becomes ungrayed out and I can choose my Early-Offer codec.
|
|
1:28:35
|
But we're not going to do that as I mentioned in 8
|
|
1:28:39
|
you do not need an MTP to do an originating codec
|
|
1:28:44
|
or an Early-Offer anymore.
|
|
1:28:47
|
Ok, I have to choose a security profile.
|
|
1:28:53
|
Keep in mind there's all sorts of places that the proctors
|
|
1:28:56
|
or labs can introduce inherent troubleshooting for you,
|
|
1:28:59
|
so for instance one of my labs SIP security trunk profile
|
|
1:29:02
|
you have to choose one. There is one by default called non-secure
|
|
1:29:05
|
and you have to choose a SIP profile as well.
|
|
1:29:08
|
Well, these look like the standard default ones right?
|
|
1:29:12
|
So no problem.
|
|
1:29:14
|
By the way, DTMF signaling preference should be left
|
|
1:29:16
|
to no preference which will negotiate for you the best codec.
|
|
1:29:22
|
And RFC 2833 is of course the best because -- and skinny phones
|
|
1:29:27
|
also speak that, so there's no need for an MTP
|
|
1:29:30
|
or any sort of transcoder or anything else in the path.
|
|
1:29:33
|
But I'll go ahead and press save.
|
|
1:29:36
|
And note on the security trunk profile on this particular --
|
|
1:29:40
|
this is just a demo, we're not -- this isn't a full blown lab.
|
|
1:29:43
|
But on one of my labs, one of the inherent troubleshooting
|
|
1:29:48
|
niceties that I added for whoever was taking the lab
|
|
1:29:51
|
was that if I went to SIP trunk security profile
|
|
1:29:54
|
I'll open it in a new tab.
|
|
1:29:57
|
Find. There's only the standard.
|
|
1:30:00
|
Just because it says it's the standard one doesn't necessarily mean it is.
|
|
1:30:05
|
I had changed it to encrypted and so the incoming outgoing was TLS
|
|
1:30:09
|
the port number was wrong. It was expecting encrypted and
|
|
1:30:14
|
the naming was mischievous.
|
|
1:30:18
|
Well, it was just the default naming. I didn't touch it,
|
|
1:30:21
|
but where I put the error was the problem.
|
|
1:30:23
|
So check when it comes to troubleshooting.
|
|
1:30:28
|
These would be very similar to -- you might say,
|
|
1:30:30
|
"Well isn't that kind of wrong or mischievous or
|
|
1:30:35
|
isn't that kind of unfair for the proctors to do?"
|
|
1:30:38
|
Well if you think about it from the perspective of you walking into
|
|
1:30:42
|
a preconfigured CUCM cluster or preconfigured deployment
|
|
1:30:48
|
and you're called in not to deploy or design or upgrade,
|
|
1:30:52
|
but to troubleshoot something that's not working,
|
|
1:30:55
|
someone else that did something to the network, it's really
|
|
1:30:57
|
no different than that.
|
|
1:30:59
|
So that's what they're trying to perfect is not only engineers
|
|
1:31:02
|
that know how to design and deploy, but also really
|
|
1:31:05
|
know the protocols through and through and know the servers
|
|
1:31:08
|
and platforms and can troubleshoot really well.
|
|
1:31:11
|
Ok, so let's reset.
|
|
1:31:14
|
And I'll click reset.
|
|
1:31:16
|
And again, there's not going to be any registration.
|
|
1:31:22
|
In fact for SIP, it doesn't even registration.
|
|
1:31:27
|
Gateways it does just because the type gateways in general
|
|
1:31:31
|
well MGCP and H.323 happen to fall within the same sub section
|
|
1:31:36
|
of gateways.
|
|
1:31:37
|
If this SIP happened to fall within gateways, you would see
|
|
1:31:40
|
registered or a column for registered and it would basically say unregistered.
|
|
1:31:49
|
Ok,
|
|
1:31:50
|
so at this point we should be able to -- well actually let's
|
|
1:31:56
|
create a route pattern.
|
|
1:31:58
|
Or grab our existing route pattern.
|
|
1:32:00
|
No, let's just create a new one.
|
|
1:32:01
|
Say route pattern is 112
|
|
1:32:05
|
Leave it in the null partition.
|
|
1:32:07
|
Send it to the -- sorry not Branch 1,
|
|
1:32:11
|
but Branch 2 gateway
|
|
1:32:19
|
and we should be able to test going out to 112
|
|
1:32:22
|
we don't have any CSS going out.
|
|
1:32:24
|
So we can dial.
|
|
1:32:27
|
And we saw the call go out.
|
|
1:32:33
|
Ok, went out of Branch 2 router as Jack Shepherd
|
|
1:32:38
|
calling party 1001
|
|
1:32:42
|
called party type unknown
|
|
1:32:47
|
and normal call clearing.
|
|
1:32:59
|
Ok, so any questions so far on gateways?
|
|
1:33:07
|
We're going to take a look more at CUBE as we get into
|
|
1:33:10
|
the next section for gatekeeper.
|
|
1:33:14
|
One of the things that we're going to do is do a
|
|
1:33:19
|
gatekeeper link to a -- we'll probably do a little bit between
|
|
1:33:23
|
two sites, but we'll do a gatekeeper link between
|
|
1:33:27
|
the corporate headquarter site and a backbone enabled --
|
|
1:33:34
|
gatekeeper enabled ITSP or Internet Telephony Service Provider
|
|
1:33:39
|
and we'll take a look at CUBE in conjunction with that.
|
|
1:33:43
|
So we'll cover that during the next demo after we discuss gatekeepers.
|
