CCIE Collaboration Lab Training :: URI Dialing Between Clusters

everybody thanks for joining us today for IP experts V lecture on URI dialing between clusters if you tuned in last week you saw that we talked about URI dialing between phones on the same cluster and how to actually make that configuration happen but today we're going to talk about how to get that working between clusters using ILS or inter cluster lookup service so but first I want to just acknowledge that it's another great turnout today I really appreciate everybody attending you know once again please feel free to ask questions at any time it's not going to bother me at all it's not going to interrupt the lecture it's it's going to help everybody if you ask a question because some people might have that same question so let's start talking about what we actually need to configure for you right darling between clusters first of all we already have accessibility from HQ to site B with a sip trunk in between for the directory numbers so HQ is the range 1000 or 1 xxx site B is the - xxx range so now between those two phones we're just going to need to dial you know the four-digit number that's how we have it configured right now so there is the directory number base dialing between these clusters already configured so we don't have to do any of that but I do want to show you the phones that we have through phone view configured so to show you kind of what we're working with today and how we've configured things so let me pull that up real quick so if you see here we have on the top we have HQ phone 1 and HQ phone 2 on the bottom we have site B phone 1 and site B phone - so like I mentioned before we have already got URI dialling working between phones on the same cluster but how do we get it to start working with phones that are on different clusters well as you can see I've been nice enough to configure speed dials for us already I know that was pretty nice thing for me to do so you don't have to hear me explain how to configure speed dial again but as you can see you know we want to speed down on the phone because we can't normally dial a URI with keypad so it's important that we configure the speed dials so let's just take HQ phone one for example we have a speed dial to HQ phone - and it speed down the site B phone 1 and side B phone 2 and as you can see they're at the same domain we're at the same domain IP expert comm this is pretty typical of any corporation that you're going to see I mean you might have different DNS names throughout corporations to say you know sales or marketing or technical support or whatever you might have different domain names for that but largely speaking or have the same top-level domain the top-level domain being IP expert for us like IP expert comm for us so why did I bring that up because it is very important to differentiate somehow between these domain names I mean if you have a domain name on HQ and a domain name on site B they're the exact same how do you know what cluster to route those to that's going to be something we talk about a little bit later today but just think about that as we go through the lecture so like I mentioned here we got both phones set up already with the speed dials even though they may not work let's go ahead and try though a call from HQ to HQ phone one to HQ phone to you just make sure everything's working that's button three here okay so it sounds like that's working it's going to answer that call and one thing I want to point out just like I pointed out last week we have the call that's active but you don't see a URI anywhere in that call because these are just directory numbers the UI's alias - directory number so you're only going to see the directory number when that call is connected so let's go ahead and end that call switch back to my old keypad there all right now this will refresh the screen of course in a few seconds with the updated phone view which is a great piece of software by the way which is the also the software slight side note that we have on our racks that you can when you do rent racks from us this is a software that you can use to access our phones remotely or you can bring your own phones but that's a another topic of conversation all right so we have our phones configured to dial within the same cluster now let's see if we can dial phones between clusters so that's just speed dial button for on this HQ phone one here and that will dial site B phone one so we hit that you may be able to hear that but it's a fast busy possibly the worst sound in all of voice or collaboration you don't to hear that sound anyway all right so that that all that did was demonstrate that we don't have anything configured between clusters to dial your eyes her to pass your eyes all right so let's start the configuration then let's started on the HQ cluster as you can see right now I've already got the the site B SIP trunk up which is going to be pointing towards site B of course for the directory numbers where to discuss so it covers this to xxx range and likewise the site B cluster has got a route pattern pointing towards the HQ cluster in the same fashion so but that's going to be pointing towards one xxx and I did something that's technically not a best practice to do I assign that route pattern directly to the SIP trunk but once again see a collaboration lab exam or any CCI exam is not a test of best practices it's a test of everything they can possibly throw at you so you want to make sure you can deal with different situations and this is one of the reasons why I added this this way so we don't want to or what what what this is going to present here for us is is if we try to configure a way to route a URI across this trunk we can't do it because we already have a route pattern assigned to it and so no other route patterns can be assigned to that Citro because it's already used if we had put it in a route group and a route list then we can use that SIP trunk over and over and over again but this was by design I wanted to show exactly how we're going to create this SIP trunk between clusters so first thing we need to do then we're going to create a SIP trunk there's actually a lot of configuration things we need to do before we actually do the step trunk now first thing you got you got to think about here is you have a SIP trunk that needs a device pool needs maybe a location CSS possibly maybe a security profile maybe a standard profile there are a lot of different things that you can configure before you even touch the actual SIP trunk configuration so why would you need any of those things first of all so let's go to right down the list you have a SIP trunk let's say where the subtract configuration page we see the device pool the vise pool is going to control a couple different things for us but the main thing would be you know media resources and codec codec is very important of course because it's going to determine which codec is used between devices on the system so if I'm dialing from an HQ phone to a phone that's on the other end of the SIP trunk we want to be able to regulate that by using a region or a device pool in this case because you can't sign a region specifically to the SIP trunk so we're going to need to create a device well we know that right off the bat and if we want to have flexibility in our codec we need to create a region as well and now going down the line we want to be able to take calls from that trunk so we want to if you have CSS and partitions configured in your design like we had talked about before you need to those configured it's a really good idea you need to have a CSS assigned to your trunk as well in order to access those directory numbers or anything else that's on the system that you you want another system to access also you're going to need a non-secure sip trump pro 4 or a sip drug security profile a lot of times you use the non secure sip front profile but let's let's go ahead and create a separate one for this trunk and I'll show you why in a minute and also the standard sip profile for the SIP trunk there's a lot of different options you can set in these parameters so it's a good idea to create one per trunk a lot of times you're just going to use the standard and non-secure but you never know there's a lot of options that are kind of hidden in there that you might want to change at some point so first things first though let's create a device pool that's going to be assigned to this this SIP trunk so if I go to system and device pool let me get all the way and click the find button we have 3 device pulls already in the system but we're going to take this SB sip device pool which is assigned to the current SIP trunk that's on the system and we're going to copy it and assign it to our new SIP trunk we're creating so let's take this guy as you can see it's only one member signed to the SIP trunk copy it and let's make the name they now something I want to discuss here quickly to is the name that I use and this is just something that that I do but it might be useful for you as well is I use the name that's going to connect to the end system so let's say that I have a sip trunk to site B which is exactly what we're configuring right now I want to say site B sip device Bowl like DP or region R eg or location LLC or or trunk just spell out trunk you know it's going to have different suffix but it's going to have the same you know knit like meat-and-potatoes name that you're going to put in there so if you I mean if you keep those straight then it's going to save you a lot of time later because you're going to know exactly what goes where so in this case we're going to say site B because it's pointing towards site B I'm going to be using your eyes so this is URI and it's going to be pointing to our SIP trunk so it's a sip and then underscore DP for device pool that's just the way I do it it kind of makes sense to me you can do it whatever way makes sense to you but I do recommend that you remain consistent if possible I've got our call manage your grip assign there the date/time group that we are all also have here and then region we forgot to create a region so we it's okay we can save the device pool configuration page create a region and come back and change it nothing else is really important here for right now so let's go ahead and click Save and as you can see it has zero members which of course is you know accurate because we've just created it so let's go to the system region information and region menu click find you can see that we only have a couple regions configured here let's add a new one and let's call it site B underscore URI and you can see this device pool one comes up that we just created it's probably not going to do that in the CCI live exam and make your life easy but like I said we want to use the same name but just change the suffix that way it's a lot easier to remember so I have site B URI sip underscore region save that guy let's go back to device pool alright now we've gone ahead and changed the region let's save it now all is right with the world we have the device pool configured everything is saved we're good to go now we can configure our SIP trunk right no we can we've got a couple other things to configure here so let's let's think about what we talked about we have device pool we're also going to have what can anybody tell me right well right partitions and CSS as we talked about that for sure somebody just said CSS good you're paying attention here you know that the CSS and partitions are crazy important for this exam so we've got that configured already actually I pre configured that for us anything else that we want to discuss there okay security profile we can take a look at that so we need a SIP trunk security profile so we can go to system security and SIP trunk security profile so you can see we have the default profiles in here we got a non secure sip conference bridge and a non secure trunk profile let's click on the non secure SIP trunk profile and let's take a look in here now this is something I excuse me I wanted to touch on a little bit is we already have a sip trunk configured to site B now are we going to be able to create another SIP trunk to the same cluster well no responses to that one so I'm just going to tell you the answer the answer is no you can't create another SIP trunk to the same cluster on the same port so the reason the reason that we're in this page right now the SIP trunk security profile is because first of all John suggested that but second of all we're here to configure the port number that is going to be able to accept on the SIP trunk so the incoming port we've already got a connection on port 5060 to site B and there's already an incoming incoming connection on port 5060 from site B so we need to configure a different port so let's take a look and see what we need to do here is it's 50 60 we can just choose a random port let's say 50 88 so we've changed our incoming port and actually what we need what we should probably do because this is going to screw up a lot of things is copy this configuration first we need to make a copy so we're not saving on the original non secure profile because that'll change the profile for every sip trunk you have configure the system and one of my former instructors back in the day called that a resume generating event because you would definitely be fired for that one so let's copy that one just to make sure we don't have to generate a resume and let's name it with the port number at the end so that way we kind of know which port we're talking about and change the income report to fifty eighty eight and we'll save that all right now we can go to our SIP trunk one before one more thing we have to configure one more thing before we actually get there the SIP profile is also important we can oftentimes use the standard sip profile but in this case we're going to be using a different sip profile so if we go to device device settings in sip profile let's click find and see what we got all right we have the standard sip profile here we have one for VCS and one for telepresence we're going to use the standard sip profile for this trunk and I'm not going to go through all the settings here but I will go through the one that's going to be important for us first of all to avoid that resume generating event let's copy it and the important thing that we're going to need to put on this page or the setting that we're going to need to select here has to do with your eyes and that is going to be use fully qualified domain name in sip requests think about what we're doing we're actually you know we have a domain at the end of our URI so if we don't put that fully qualified domain name we may miss something so if we don't have that selected the call may not work correctly so let's click the box here use fully qualified domain name and sip requests we have the standard sip profile let's actually name that something that's recognizable like fqdn fully qualified domain name and click Save and now we are finally ready to configure a sip trunk we've waited long time for this so let's go to device and trunk add our new trunk select sip and it's going to default the profile of the sip of course and the trunk service type to none now we can name our device and like we showed in the device pool in the region we want to name that something that's consistent so SB URI and you can see our device pool and region come up here to validate that we're right and we selected region so let's go ahead and change that - trunk now we can select the device pool that we've already configured in the system which is going to be SB URI SIP device pool now scroll down and let's set our calling search space - gateway trunk CSS which is going to like I mentioned before contain internal directory numbers and other things like that so we're going to set our significant digits - all now in the outbound call section there is a step a very important parameter that we need to set as well can anybody tell me what that is just by looking at it here okay a couple good guesses there but we're going to be changing the calling and connected party info format parameter and the reason why because right now it says delivered en only in the connected party so we want to be able to deliver URI and Deanna in the connected party if available that's going to be important for the display if you're using the URI as the primary source of communication let's go ahead and select that deliver URI and Deanna connected party if available and we're going to go ahead now and set our destination address which is going to be the site B publisher cluster and like I mentioned before the important part of the configuration here is since we already have a SIP trunking figure we need to forward it to a different port and we've chosen port 5088 for that so let's make that destination port 5088 also the last two things here going to configure our SIP trunk security profile select the one we've already configured which is 5088 that's that's to accept incoming calls on that port and lastly we're going to configure our SIP profile to use the fully qualified domain name and that should be it right there so let's click the Save button click OK there and of course since the ad was successful let's go ahead and reset the trunk first thing you should do after you create a sub trunk you'd be surprised how many things you forget when you're when you're under pressure one I think it was in one of my CCI voice attempts I had not reset the h.323 trunk that I was configuring to a gatekeeper and I was pulling my hair out but something as simple as a reset going to save me about 20 minutes so always reset your trunk is the moral the story there all right now we have our URI SIP trunk configured and I've gone ahead and configure that on the site B cluster as well just to save us a little bit of time so I have the HQ URI SIP trunk configured as well so we have side B and HQ alright so what's the next thing we have to do we have to somehow get ILS to replicate these directory numbers between clusters and share these directory numbers if we're going to use ILS so like I mentioned we're going to need to try to differentiate between the domains somehow because you saw in the phones we actually have let me let me pull this up real quick we have IP expert comm as the domain for each of these phones so we need to somehow differentiate between those two in order to route it to the correct cluster if I just use the domain name it won't know what cluster to go to so let's pull that up there we go here there it is but okay so you do this by creating a route string to a cluster and you're also going to be using you know your your directory your eyes here in order to configure the inter cluster services so inter cluster director URI configurations where you want to go which was under call routing sorry inter cluster directory or I and inter cluster director your on configuration in order to successfully exchange these catalogs with another cluster you need to check this box that's configured here so if we check the box and we have loop down here check the box and we have the ability to add a route string now many of you have never configured a route string before this doesn't make any sense why do we need a route string let's let's try to differentiate ourselves here we're on the HQ cluster and if another cluster sees our directory or I how do they know where it's from how do they know we're you know where it goes to when they actually get that synced on their end so may be a good idea to do was is make it location-based make it physical location based so we have this cluster that's the HQ cluster that's located in in our topology is in San Jose and we have the site B cluster in our topologies in Chicago so we can say the route string is HQ for the HQ cluster we'll say San Jose dot San Jose dot see a dot us that's pretty descriptive of the location so when another cluster gets that directory synchronization from HQ it's going to say oh okay this is from San Jose you know this is the director numbers from or the URI is from San Jose so now we've set HQ to exchange directory right catalogs with any other remote cluster that is connected to using this route string HQ San Jose CA us so hit save here that's a quick little update successful let's do the same thing on site B so we go to call routing inter-cluster directory or I inter cluster directory or I configuration let's click the exchange directory or catalogs again and this time we're going to be using a route string that represents the site B cluster so it's going to be site B or s be Chicago IL dot us so now when HQ gets those directory numbers or you rise synchronized on their end it's going to use this this route string here so click Save and we see the update successful so great so now we have the ability to exchange these catalogs but how do we actually do it it's not going to go over that SIP trunk that's only going to be used for actually routing the call so we need to have some way of synchronizing these your eyes so we're going to go on the HQ cluster to advanced features and ILS configuration right now you can see here it's set for standalone cluster mode a standalone cluster it's basically it's not going to synchronize with anything I mean that's kind of what a standalone cluster does you also have the option here of hub cluster and spoke cluster a hub cluster is technically supposed to be used for some type of aggregating device like like session manager Edition session management Edition cluster SME or you can designate it with a as another cluster your system somewhere but it's supposed to be some type of hub cluster that's why it's called hub cluster here you can also create a spoke cluster which logically speaking would be just another site off of that hub so if you had eight clusters in your eight different clusters in North America and you want to aggregate a diol plan using SME you might do that by putting SME to the hub cluster setting and then synchronizing all the directory your eyes that way so let's go ahead and actually create this as a hub cluster so if we change the role there to hub cluster and since this is a lab let's change this synchronization time from 10 minutes to 1 minute and speed things up a little bit and you have the option here of using TLS certificates which is which is great a great security feature but in the interest of time here let's just go ahead and make this make this password based so if we select a radio button here to use password we'll just make that IP expert that's a pretty tough one to guess I know alright that's it so we hit save and when we do it's going to pop up with this window here for us to register to another ILS cluster if we leave this blank then we don't have to register anywhere and this checkbox here is pretty important activate the inter cluster and lookup service on all nodes in the cluster so we want to do that actually let's go ahead and leave that off let's just run this on the publishers for now so if we click ok that means we're not connecting to any other cluster in the system for right now and we're going to click OK to change the authentication method here and Firefox asked me over password we're going to ignore that and basically what this is doing now it's activating the service it's restarting the ILS service and certain unified service ability and it's it's starting this configuration of the hub cluster and it will pop up here in a second and it will say you know this is now ready to be connected or whatever let's look here we started inter cluster lookup service on 10 893 11 which is our publisher server at HQ it's ready and it's found one hub cluster so if we scroll down you can see here just get out of the way a little bit you can see you have the HQ cluster it's the local cluster and you see that it's a hub and you see the route string that we configured HQ San Jose CA us and the URI data synchronization status up-to-date and of course it's up-to-date because it's local it doesn't have to synchronize anyway so let's go ahead now and since this is configured as a hub cluster let's configure site B as a spoke cluster let's go over to site B and go to LS configuration there and this is also set to standalone cluster like the like the hub cluster was set or like the HQ cluster was set to let's change that to spoke change the synchronisation time here to 1-minute again and I'll use the ultra secure password of IP expert alright now this is going to pop up that window that's going to connect it's going to ask you to connect to a different cluster this time we're actually going to put something in the window we're going to connect to this publisher server that's running the HQ cluster so let's put that address in there 10.8 dot ninety 3.11 we'll click OK and it's going to need to restart the ILS service to make that happen which is fine all right so that's going to take just a second to register there once it comes up with the configuration page that's saved it's going to it's going to take just a second and then it's going to try and synchronize those directory of your eyes so what we can do in the meantime while this is while we're waiting for this page to save and everything to load and all that we can configure the SIP route pattern and this is this is going to be necessary for us to get those your eyes from cluster to cluster so like I mentioned we can't use a domain name to differentiate between between clusters because they have the same domain name so that's why we created these route strings so if we go into SIP route pattern and create a route route string type pattern pointing to the other cluster then we're able to dial so let's go ahead and do that move back in the right hand corner here and okay so it looks like the service was restarted it's ready and I did not find that a hub clusters yet by the way so it's just going to take actually should take only about a minute that's what we set here but in the meantime let's go to HQ cluster and go to call routing and sip route pattern click find here we don't have any route patterns in the system let's add new we're going to use domain routing and this is a little bit confusing here you see you have ipv4 pattern under this domain routing drop-down it doesn't really make any sense because yeah it could be an ipv4 pattern that you're putting in there but it's it it's in this case it's going to be a domain base pattern or a route string base pattern so it's not very descriptive field so don't let that throw you off so from the HQ cluster we're going to connect to this IB cluster of course so we need to put that site B route string in there so this was site B or SB Chicago dot il for Illinois dot us all right so I've got that rust stirring in there now what the route partition my favorite subject so you can change this of course which I recommend doing let's just go ahead and put this in the internal partition for now that way everybody's got access to it that needs it and we can either do a SIP trunk or a route list I'm going to go against best practices yet again here and just assign the SIP trunk directly to the SIP route pattern just for illustrative purposes and so we have a lot of trunks to select from here so we're going to have the site be URI SIP trunk which is the one we created for you ride island purposes and then nothing else that we need to configure here so let's click the Save button now we see that that actually all changed this to lower the lower case here for the pattern and we've got our domain routing pattern configured in the system now so anything else we need to do here I don't think so let's go ahead and go to site B and go to call routing sip route pattern split fine and obviously we don't have anything here either all right so we have domain routing again and we're going to create our pattern which is going to be our sip route string to the HQ cluster here so HQ San Jose that CA dot u s alright now we're going to also put this one in the internal partition and we're going to select our HQ URI SIP trunk sign it directly to the truck again nothing else we need there so those are the two things that we actually need to do we have those route patterns can figure out both clusters so now let's go ahead and check on our ILS status let's go to the hub cluster which is HQ and go to advanced features ILS configuration and now you see that it's found one hub cluster and one spoke cluster spoke cluster obviously being the site B cluster in this case since we can figure that so if you scroll down here I'm going to get out of the way again scroll down here you can see the HQ cluster of course because that's the hub cluster that we have configured if you expand that down here the little arrow down there you can see under that hub cluster is now going to be this site B cluster the the SP cluster that we've configured to be a spoke and you can see that has a last contact time it has a role in the network which shows up as spoke and it also has the cluster URI route string which is SP - Chicago IL dot us it shows a last URI data received and also the fact that it's up to date which is probably the most important part of this I mean you have as you can see right here just sneak in there it's up to date so that's a great thing because now we can actually try to make a call between clusters so let's pull up our phones and where should we go here let's go from HQ phone one to site B phone two which is going to be one two three four five v button so we find we select that phone and we let's make sure we have automatic screen shots enabled on all these guys we do all right so one two three four five fifth button we have the HQ phone one selected let's go and make that call and you can hear that that's ringing over here and let's go ahead and pick it up and the call is now active between these two phones we've successfully made a user ID call between clusters once again that's going to show up as you know just the director numbers here because yeah you are is just going to be an alias to these directory numbers so we've made that call between systems let's go ahead and test another call let's go from the 99 and 71 phone to the the 1971 phone is HQ phone too and we'll go to side B phone one so I'm going to change the keypad for that that's going to be 1 2 3 4 5 should be v 1 and it is I was looking physically at the phone there alright so I do 1 2 3 4 5 I click that it is now dialing to site B phone - let's change the keypad and this click answer and now when the phone is refresh you'll see that they're connected here great so obviously that phone is connected with 1000 or I'm sorry yeah with 1000 - we had a call from HQ phone - to site B phone - all right so with that said that is the entirety of the you write dialing configuration and section and so I guess I'll go ahead and turn over and ask if you guys have any questions I see actually there's one there's a couple queued up already sorry I missed those but we have the first question here from Scott Scott asks do I have to configure the route string to dial between clusters well in this case you don't ever have to do anything really look at it that way you don't have to configure a route string to dial between clusters you can actually use a wildcard pattern if you want and what let me show you what I mean by that let's go back to HQ and look at the cipa route pattern that we created and if we want to use I mean we have SP dot Chicago to aisle at us we have that exact route string here we don't have to configure that technically we can configure a wildcard pattern so if I just said asterisk that means everything so we're going to send everything every sip route pattern out this SB URI SIP trunk if you really wanted to do that you could set that so now this up says update successful here so let's go ahead and try a test call there from this is from HQ to site B so an HQ phone should technically be able to still call using this wildcard pattern let's go with HQ what may in this caller so if I want HQ phone one this IP phone one so that's one two three four and you can hear that that calls are ringing there and like I said let me go let me go back and show you this is really all you need technically but that doesn't allow you to get granular with it I mean if you want to point different route strings to different clusters which is probably what you're going to want to do then you're going to have to to configure it with the specific route string that you're using good question though I appreciate that next question that have built up here Mike asks do I need to have inter cluster routing using directory numbers in order to support URI dialing between clusters do I need to have inter cluster routing using directory numbers in order to support you all right okay I see what you're asking here so you are dialing between clusters you don't have to have I mean you don't have to have director number dialing right let's let's go I'll show you here if if we go to our SIP trunks I mean they're two separate SIP trunks you can see you know ones ones for D ends ones for your eyes but we could even go as far as to you know let's just let's not though I was going to delete it but let's just point it to it nonexistent IP all right so now that normal SIP trunk that used that's used to dial to the other cluster is down so let's let's go ahead and show that slide that call up there and we ended the call there so if i dial to 2001 it shouldn't work because we've we've pointed that SIP trunk to another location so if i go to 0 0 1 and hit the dial soft key took a little about a little while but I got a fast busy which has every already mentioned is the worst sound you can hear alright so that that is is not working anymore but if I were to use it you right ooh dial to site B phone one one two three four fourth button I can hit that and now that call is successful because it's using a different set trunk to get there so just because you've you've got you know you write or because you've got a directory number dialing configured doesn't mean that you are dying will worker won't work they're completely independent of each other or they can be sometimes you might even use the same SIP trunk to support URI dialing and directory number dialing a lot of cases you probably will do that so it looks like that's all the questions I had today so I really I want to thank you again for coming out I really appreciate the support and the questions and I feel like we had a pretty great discussion here today so once again any questions let me know I'll be available and thanks for joining and we'll talk to you next week

Channel: IPexpertInc

Views: 9,264

Keywords: CCIE Collaboration, CCIE Collaboration Lab, CCIE Training, URI Dialing Between Clusters

Id: llo_czH5C-k

Length: 42min 1sec (2521 seconds)

Published: Tue Jun 17 2014