 Welcome to the Network Engineering video blog. I am your host, Michael Crane. So in today's video, we are going to move our SIP test bed. Well, actually, we're going to move it to the Los Angeles test bed. Our test bed. So we're basically just testing SIP phone to SIP phone, right? And so we need to connect these guys to a real router. And it doesn't necessarily have to be a router, but for us it's going to be a router because we're going to be using Cisco Call Manager Express, right? Cisco has a couple of products. One is the Call Manager Express, which runs on these 3845 routers. And they also have the CUCM, which is a Cisco Unified Call Manager, which runs on virtual machines and an appliance like a Linux box. They both have the same name, but they're not the same product. They kind of do the same thing. They're both PBX type applications. But I believe the CUCM product that runs on Linux was purchased by Cisco. And I believe this one right here, they developed themselves. Anyway, so we're going to be using the Call Manager Express. And we're going to put it on our Los Angeles test bed. All right. And so I'm basically just going to put all this that we're using in our SIP test bed that's going to go right here. And this will, and we'll use, and then we'll set up the Cisco Call Manager Express, or the CME. I'm just going to call it the CME from now on, the BRPBX. It'll run in this Los Angeles gateway. And if you remember from a long time ago, when I purchased these routers, the Los Angeles gateway and the Chicago gateway both have CME installed on them. So we're good to go. And the reason why I'm having to do this is, you probably already know, but I'll just state it anyway, is you can only do so much testing, SIP testing, phone to phone. For what we're doing, we've exhausted everything we need. Now we need a back-to-back user agent or a proxy. And the CME will be a back-to-back user agent for us. So I went ahead and copied that config over from our SIP test bed. Didn't bother changing the IP address, the station IDs from 44, 45, and 46. I did have to change the net mass, though, to .13. But for now, we'll just keep it VLAN1 default. I'm going to try to use this configuration document. I can only find two that were actually any good. And this one looked pretty good. I like the layout of it. This is very familiar to me. If you've been watching my videos for a while, you know that this is very familiar. You see all the analog stuff's plugged into the router. That's very common. And then all the IP stuff is going through this catalyst. We're going to be using an SMC switch because it's a power over ethernet switch. I thought about plugging it into our catalyst switch here or 3750, but there's really no need, right? There's actually a little ethernet switch built into this router. If you've been watching, you know that the fast ethernet card says, like, gosh, I forget 16 ports on it or something like that. So it's like a little mini switch in there. So you'll see some switch commands that will do this little document right here. I'm just going to go through it. And we're going to just go step by step setting up our call manager express. At some point, we'll have to veer away from it because it's using the skinny call control protocol, which is SCCP. And we're going to be using Grandstream SIP phones. We're not going to be using skinny phones. That's proprietary to Cisco. Oh, by the way, another document I found is this Bohemath. Look at this thing. Cisco Unified Communications Manager Express Systems Administrator Guide. At least it's been updated this year. Look at it. 1600 pages long. Yeah. I think we'll just use this as a reference. This document here, it's pretty long. But like I said, at some point, we're going to veer away from it. And plus, it goes into setting up this Unity Express, which is like voicemail, right? But I'm pretty sure we can use the CME to do some voicemail. Well, we'll have to check. I know on some of the routers, they support it. But if we don't have enough flash memory, then we're not going to get very much voicemail. Well, by the way, if you're wondering what this is here, even the experienced network engineers can lay an egg every once while, right? This is version 11 document. So when I was first looking at this, here's a version 10. I noticed this subnet mask right here. I'm like 16. That's not right. And it's actually dotted all over. It's 16 again. 16 again. 16 here. Of course, I copied and pasted it earlier and propagated that same error. And now it's six times throughout this document. This is version 10. I've already fixed it, but I wanted to show you this right here. So I know what I did, right? And I already fixed it. It's slash 25 is what it's supposed to be. But what I did is I said, okay, I want 128 IP addresses, right? Let's look at... Okay, here we go. So I wanted 128 IP addresses, right? So instead of taking 256 and dividing by two, which gives you 128. So the subnet mask would have been 255, 255, 255, 128. I took 32 and divided it by two, which gave me 16. And that's not right. Because subnet, a bit mask of 16, about 65,000 station IDs, right? It's 255 times 255. And so I drew this out just to just kind of show you, wrote this example out. So if you want 16 IP addresses, you do 256 minus 16, which gives you a subnet mask of 240. Or to use a bit mask. So you do 124816. So you'd want a bit mask of 28, right? And if you want a bit mask of 128 IP addresses, it's 1248163264128. So it'd be slash 25, which is what I put right here, all right? And then everything in between. You just count up. So this is 1248163264128. And of course, if you want 255, then all these are zero, right? Which gives you 255, 255, 255.0. And that's your whole 255 IP addresses. And if you only want one IP address, it's 255, 255, 255.255, or it's slash 32, right? Okay, so I was kind of thumbing through this document a little bit. And it looks like they want to use DHCP for the phones, which is fine. I usually for testing, I usually give them static IPs. But I kind of wanted to stick to this document, just so you had something to reference. As you're watching this video kind of going through this stuff, I've got this link plugged in right here, but it hasn't been provisioned yet. So we need to provision this. And we need to change the IP address and this SMC switch, which is actually still on dot one, like that. So what I'm going to do, I'm going to go ahead and swing this this link right here back to my management network, which is the dot one network. That way we can, we'll just log in to each one of the phones. We'll set it for DHCP. And then we'll give this ethernet switch. We'll change it to 13.41 instead of 1.41, right? And its default gateway would be 13.1. So I'll be right back. All right, so I'm logged into all three devices. We're going to, let's see, I think it's under basic. Yep. I'm going to just do the phones first and then I'll do the switch last. And hopefully when we get the dot 13 network set up, we'll be able to log back into these guys. So I'm just going to add, oh, that's all right. We're going to do DHCP. Okay, so just enable DHCP and click update and reboot. It's probably going to get an address from my network, my management network, but that's okay. All right, DHCP, scroll down, update, reboot. Okay, basic. Oh, DHCP, update and reboot. Okay. And this guy right here, we're going to set them to dot 13.41. So let's see, land settings. I'll just add a three to this guy. And as default gateway will be three, 13. VLAN one, that is correct. Management VLAN is one. Okay, so apply. Yep. Okay. All right, there we go. So now we just got to get the router set up. Okay, so I'm logged into the Cisco Los Angeles router, gateway one. And let's see here. Show config. Let me copy all this out. All right. There's not much in this router, is there? And we don't really care. We're going to do this in little chunks, because I don't want these videos to be real long. I want people to be able to find them, you know, find what they're looking for and without having to weed through an hour long video, right? So I plugged it into this guy right here. And here's where I plugged it in. Here's that, the 16 ports I was telling you, it's like a little ethernet switch, right? There's the one right there. So one port, port zero. Okay, that makes sense. So config T. Let's see if we want this guy right here. Copy, paste description is So what is its name? So we call it the LA e-switch one for that one. So we'll call this one LA e-switch two. And I'll say, so link for SMC LA e-switch, oops, two. All right. Okay, so we don't want an IP address. We're going to do, that's a, I don't think we need this command. Let's see, switch, switch, port, access, VLAN one. And then load, interval 30. That's just so it updates the count, the stats faster. And I'll do a control C and a right. I'll just do a show config. Yeah. Yeah, see it didn't, that command, the switch port mode, the switch port access command was, is defaulted. So that's why I didn't add it in there, right? Now, if we would have changed this to a different VLAN, it would have added it in there. But speaking of VLANs, let's go down here and check. So we're going to give our VLAN one an IP address. So config T, interface VLAN, oops, VLAN one, oops. And IP address, 192.168.13.1, 255.255.255.0. All right, oops, I forgot to turn on the term, oops, one. And I missed all the console messages, but okay. Gosh, I can't think. There's not a lot to this, right? So let's just try it. So ping 192.168.1.41, nope. And I figured out what we forgot. It's a layer one problem. Those things will get you every time. I still have the ethernet switch cable plugged into the management LAN. Let me move it real quick. Much better. Let's try that ping command again. Oh, still no, darn. Oh, yeah, what's that command for VLANs? Config T, man, this will get you every single time. Uh-oh, line protocol on every VLAN changed state to up. Oh, maybe. Actually, I think the router beat me to it. But let's just do it anyway. VLAN one. Now, you notice I didn't put interface VLAN one. I just put VLAN one. And then it's that shutdown state. So I'm just going to do a no shut on it. Oh, that's right. VLAN one is default, right? So it should always be up. So never mind. So, oh, look what I'm trying to ping. 1.41, yep. Now you see how I got that slash 16 in there, right? Yeah, that's what happens when you're trying to engage your mouth and your brain at the same time. It just doesn't work. Hey, very good. Okay, so take a quick look at this document real quick. Yeah, so the next step is defining the DHCP server for the phones. And now we can ping from the router to our SMC switch. And so these phones are my grand stream phones are just sitting there waiting for a DHCP server. So to keep this video short, I want to keep everything in little segments because this is going to be a kind of a complicated configuration. So I'm just going to go ahead and stop here. And then in the next video, we'll start with configuring the DHCP server. Okay, so don't forget you can support the network engineering video blog by donation using a credit card and PayPal or by purchasing products at the MUXALL store. Details and links are in the description under this video. Well, that's about it for this video. If you liked the video, give it a big thumbs up. That helps and hit the subscribe button. That really helps. If you have any questions or comments, post them in the comments under this video. Thanks for watching and I'll see you next time.