MGCP gateway configuration

- [Instructor] In our last video, we created an H.323 gateway. Specifically, I added on a Cisco 2911 router to our HQ typology. We connected it into HQ switch 2 and we connected it out to another router acting as our PSTN. And we set things up such that our HQ IP phones could use that router as a gateway to get out to the PSTN. In other words, the rest of the world. And I had a phone that's pretending to be on the PSTN with a number of +1 408-333-3001. And we made sure we could call back and forth between an HQ phone and that PSTN phone. What we're going to do in this video is take a look at an alternate approach to using an H.323 gateway. The CO core exam blueprint says we should also know how to configure an MGCP gateway. So I have removed the H.323 configuration we did in the previous video, I deleted the gateway from communications manager, I removed the H.323 config from the router. So we're starting from scratch, configuring an MGCP gateway. To configure this MGCP gateway we've got work to do both on our communications manager server as well as the gateway itself. And MGP, it's a client server protocol. That means that our communications manager server, it's going to be responsible for route plan information instead of creating all of those doll piers like we did with the H.323 gateway. Now let's begin our work here on our communications manager server. Let's go under Device and Gateway. Let's just confirm that we do not have a gateway. We do not, so let's add one. You might remember when we added the H.323 gateway under the Gateway Type menu, we just scroll down and we said H.323 gateway. However, MGCP requires us to be much more specific because an MGCP end point, our T1 port in this example, it's going to register with communications manager. So we have to educate communications manager about the architecture of our router and how it's populated. And I'm using a Cisco 2911 router. By the way, if you don't know what router model you're using, we could go over to the router and say show inventory. And this tells us that I'm using a 2911. Oh and while we're here, also notice that the T1 module that I'm using, it's a VWIC version two, one multiflex trunk. It's got one port, not two ports, and it could be either a T1 or an E1 but we want it to act as a T1. That's going to be important to know when just a moment. But for now, we're confirming that we have a 2911 and I'll say next. For the protocol, I'm setting this up as an MGCP gateway. And we'll say next. For the domain name, you might think, well, I don't have my router configured for domain services, so I could just put anything here. Actually, this is critical and it's often configured incorrectly. This domain name, it is case sensitive and it needs to match your router's domain name. And if your router is not assigned to a domain, it's going to be the host name of your router. So what I would do is I would go out to my router and I would say, show me my running configuration pop the output to include any instance of the word domain. Because if I had configured a domain, it would show up there. If I go on global configuration mode I could say IP domain-name, and I could give a name. I could say something like cisco.local. I'm not going to do that though, I'm just going to leave the domain name empty but I needed to confirm that I do not have a domain name assigned. Since I don't, I'm just going to use the host name of the router as the domain name. And I'll say, this is going to be using the HQ communications manager group. So this is giving us some redundancy. This registration of the end point is going to act much like the registration of a Cisco IP phone. It's going to know about our subscriber and our publisher, it's going to download its configuration via TFTP. So that communications manager group is telling it to register with the subscriber and if that's not available register with the publisher. Now, we start to educate communications manager about the architecture of the router. What modules do we have? And module and slot zero. Slot zero represents the motherboard as we discussed in our last video. So I'm going to select NM-4VWIC-MBRD. That means network module. We have four empty bays into which we can insert these VWICs and it's controlled by the motherboard. I'm going to save that and say, okay. And since I have those four different bays, those subunits, we see those here. And if we go back to our router, we'll notice that we're in slot zero, that's the motherboard, we're in sub slot zero. So for the sub slot, I'm going to say that we have a VWIC version two, 1MFT T1 or U1 but we want it to act as a T1. So I'll select that and we'll say save. And now it knows that we have a digital voice port with an address of 0/0/0 but this port is not configured. We see that evidenced by this question mark. So let's click on that port and it's going to ask us, how do we want this set up? Do I want it to act as a digital access T1? In other words, using something like channel associated signaling, as we discussed earlier in this lesson, or do I want it to be a PRI, an ISDN primary rate interface. That's what I want. I'll say digital access PRI, next. And I'll set the device just like I would for a phone to HQ. We'll scroll down a bit. And because I'm using a fractional T1, I'm only using the first three channels. We talked about that in our last video, I need to change the channel selection order. So it's going to start with channel one. I need to change it from bottom up to top down. If you were using all 23 bear channels, that would not be an issue. And because I am doing a fractional T1, I also want to check enable status poll that gives communications manager the ability to take B channels out of service. And when we get a call coming in from the PSTN, we don't know what that's going to look like. Maybe that PST caller dialed just our office code because they were local. Maybe they dialed our area code and our office code because they were long distance, but I only want to pay attention to the last four digits. I'll say significant digits, four. And when we're extending the call from the MGCP gateway out to a Cisco IP phone, the gateway has to have permission to do that. So I'll give it a calling search space of HQ. For calling party presentation, I'd like to set that to allowed so we can display our caller id. And speaking of caller id information carried on that PRI circuit, we saw how to configure this on a router in our last video, I want to say display IE for information element delivery, redirecting that number IE delivery, outbound and inbound. I think we're done. So I'll say save And okay. And right now it says we're unregistered because we've got some work to do over on our router. So let's go to the router. And the first thing we want to do is to tell the router that that VWIC that we have installed, we want it to act as a T1 port instead of an E1 port. This is a command we gave in our last video. In global configuration mode, I'm going to say card type T1. It's in slot zero, it's controlled by the motherboard and in sub slot zero. That's where this VWIC is installed. So this is going to be a T1 port, not an E1 port. And once I do that, I can tell my router to point to my publisher as my MGCP configuration server. I'll say CCM-manager config server and I'll give the publishers address of 10.3.3.1. And now I'm going to say CCM-manager config. The first command said, here's the server containing your configuration file. And the second command that says, okay, go get that configuration file. And it's an XML configuration file, much like a Cisco IP phone would download its configuration file. That's going to take several seconds to go through this registration process. So we'll give it just a bit of time to complete the registration. And it is taking control of our T1 port. It's enabling MGCP. All right, I think it's done. We can do a confirmation by saying show CCM-manager. And we see that we are registered with our subscriber and our backup is standing by and ready. That's our publisher. The reason we're pointing to our subscriber is because of the communications manager group we used. So we see we are registered. Let's go back to our communications manager and I'll do a reload. And we'll confirm that we are indeed registered and it says we are now registered, awesome. Well, let's place a call. Now at this point, I've not yet gone in and created a route group and a route list and a route pattern like we did with the H.323 gateway. We could do that. I don't want to spend time in this video doing that because it's exactly what we did in the previous video. But I want to confirm that this gateway is working by placing a call from my PSTN phone coming in to HQ phone 1. So what I'm going to do is that debug command that we gave in the last video, I'll say, debug ISDN q931. And I'm going to go to my PSTN phone and I'm going to dial 2222001. You might've heard that phone ringing in the background. You can see that the calling party shows up as it's fully globalized E.164 number. And the number that was dialed was 2222001. But because we said significant digits were four, it only paid attention to the four right most digits, 2001. And that's the directory number of HQ phone 1. So now in this lesson we have seen how to create an H.323 gateway and now an MGCP gateway.