Globalization and Localization Inbound Calls

[Music] how's it going everyone Jim back with another cisco voice tutorial today we're gonna be looking at globalization and localization some of you may have heard about this some of you may not have this is this is based on incoming and outgoing numbers with globalization and localization what that means is we stretch out in terms of some of you might know we we do a fully-qualified phone number so we stretched that out to a fully qualified Cisco voice world that's a dot 164 we stretched that out to the full 8.1 64 or we condense it down to a local call manager four-digit five digit seven digit whatever York off loes gonna be and how that works with the PSTN tough-love inbound tuflow outbound so we're gonna take a look at this and this is I have a video already on call flow and a video already on the comm manager configuration basics this is kind of lab relating on all of that okay especially on the cost low part cuz we're gonna look at in this video the inbound call flow and then shortly after you can watch another video for me with the outbound call flow for all of this and this is based on the new cisco s are indeed guides i've been using this for a few new years now and I absolutely love the con flow it's easier to troubleshoot it's easy to find things and it gets your number to one single format when it hits the call manager world right and then you change that according to what you want it to do for your phones what you want it to do going towards your comm manager and all this good stuff so we are gonna take a look at how this all works so let me get my face out of the way and let's dig it alright so I've pulled up my little PowerPoint here and like I said we're talking about the call flow inbound today all right and we're going to take a quick look at what's going on so first of all let's get to the next slide here we're gonna look at the Gateway how the calling search space on that gateway works for the incoming calling and called settings all right and we're going to take a look at the inbound call flow within call manager without those calling spaces and partitions work and we're going to look at the device pull settings and why that matters if you've seen my coffee oh you already kind of know where this is going and then the phone route patterns and DN settings and how this all ties in for inbound call flow all right so let's take a look at our topology we have our internet coming in here this is a sip gateway alright we have a sip trunk from the internet world or our PSTN world hit in this cube and it goes to our call manager which is in a ESXi environment this is our core switch so we have our call manager here oops does it mean go to the next slide yeah so it's coming to our call manager we also have a sec for later videos and in our phone so what happens when an inbound call comes in well let's just take a look at that so for example we have a call coming from 304 555-5555 all right it's caught in to us five five five mm so it comes in hits our gateway our gateway is gonna apply some settings to this call first of all our incoming calling search space is sent to this inbound calling search base all right but just as important this gateway prefixes a plus and a 1/2 the calling and the called number right now we're dealing with tangent digits from our PSTN and we are four digits in this lab in our internal call manager right so we're receiving ten digits from the call manager this is going to be skewed if you're receiving four digits or whatever from from your PRI your SIP trunk from the carrier nowadays it's mostly ten digits but it's not always some people still have four digits coming in from your PSTN medium all right but in this case we're receiving ten digits once it hits the sip cube this thing has some settings which we'll look at later and it changes the calling now at prefixes this plus and one on it and our call number comes in with the plus one all right so that's what we see now so now let's go ahead and move forward here and this inbound calling search plate calling search space includes the inbound partition that's all that's in this calling search space don't worry we'll dig into the call manager let you look at it this is just a I'm trying out some nice new pictures here all right so that's on the Gateway setting so it comes in with that it prefixes the plus one well we have a translation pattern in our call manager that has this number that this called number right but we've done this funky pattern and it's got that looks it's got this plus one in the pattern and it's partition is in the end on partition so the gateway can hit that then the calling search space in the translation has internal alright and there's a the calls gonna flow on in and now our number becomes plus one three or four five five five five five out that's the called but this translation translates this called party to 2000 because that's our internal so now our called number becomes two thousand and that two thousand sits on a phone in the internal calling search space alright so the internal calling search space includes the D in partition which is what's sitting on the actual line of the phone so we'd have some transformations also on a device pool this is and we'll dig into that this is the actual pattern on there and it discards it the pre dot so it takes away that plus and the one that we globalized with and now the becau becomes what's local to the phone so that our eyes looking at incoming phone we don't have to see the plus one but the phone still knows about it that's the important part so we see on our phone displays newer models 79 40s 45 60s will not work this way but for newer phones we will see the three or four or five five 5.5 pop up on our directory number 2000 so our caller ID shows this but in our missed receives calls we see this plus one what does that do for us well later in our outbound call flow will see all about that we can just hit redial no edit dialing we don't have to go backspace backspace backspace hit and nine none of that would hit read out our mist receives calls and it will just go so great so this is just a hot overview alright and what happens in our gateway settings is the gateway is where our globalization process starts so those those calls come in to the gateway it globalizes by prefixing that plus one and as I alluded to a minute ago or that needed prefix to get to a fully dot 164 number right so if your are four digits from the carrier you're gonna have plus one five five five five five five five and then whatever your four digit is from the carrier will already be there okay and we also prefixed the calling number so we get that in our phone Myst received call section right so we prefix the incoming calling number as well and then we're out to mark off flow and phone localizes at the device pool level with the transform so we go through that translation profile to switch from our fully globalized number to our internal or as we'll see in a sample on your D end you could have a fully global globalized number or you can have both there's a lot of ways to do this all right and we'll get to all of that and our gateway calling search space it has the inbound partition in the inbound calling search base this is the actual calling search space that's applied into the gateway and it determines our inbound call flow okay and we keep that flow restricted to just inbound stuff so the inbound partition will belong to things like our translation patterns that's where that's actually assigned okay and this allows for easy troubleshooting and in that coffee because there's only one place where the inbound partition is going to be and we can easily search for that in translation patterns or directory numbers so our gateway is actually signed the inbound calling search space and that's the in Val partition that inbound partition is applied to translation patterns and directory numbers and in a translation pattern specifically it has a calling search space assigned to it because it comes into the translation pattern via this inbound partition but then it goes out of that translation pattern with the internal calling search space and within that is where our directory numbers sit so that's how we get from a fully globalized Etan 164 number to our itsy-bitsy little four digit dial plan alright so that's where we're looking at I hope you're liking the visuals now we're going to dig in the comm manager and we get to see how all the nuts and bolts really work alright so now that we're in the call manager this is just the lab this is a production environment so with globalization we start at the gateway so it's a great thing for us to start by looking at the gateway in this lab we don't have an actual gateway we have a trunk or a SIP trunk going to our cube router and so we're going to take a look at this and we're going to show exactly the settings in here that make this globalization work first of all we have our calling search space for inbound calls and this is going up inbound calling search space the only thing in here is an inbound partition and we assign that to translation profiles or specific extensions d-ends that we want for inbound ringing all right but then down here we have for the incoming calling and incoming call settings we're going to prefix this +1 to get us fully globalized okay that's kind of prefixed because we have 10 digits once again coming in so we're just pre fixing this +1 to get every call on the same fully globalized framework okay now for outbound calls we have these transforms which we will get into when we get into the outbound calling video so we're not going to take a look at that now but just be aware that these transforms are here and it deals with localization back out to the PSTN or to the cube all right so we have our prefix numbers we're pointing to our inbound calling search space so let's take a look at that under our calling search spaces we have our inbound and it just has inbound partition so with our gateway once we prefix this plus one we need to be able to route that to our Dowell plan so let's take a look at a translation pattern so we have some others for outbound this is the one we're looking at right now and this is our one and only D ID for this lab at this point in time and you can see that we have added a plus and a one now we need this character it's an escape character because this is the plus is special so we have to use this backslash in here okay the backslash allows that plus to be in our pattern and then we have our plus one and our ten digit number that we are one to match and of course this can be a mask right if we had a bunch of D IDs whatever the case we would mask it right but in our case we only have the one D ID so I had it laid out specifically and it's in the inbound partition so we know our gateway can hit this partition calling search space what's in it allows the call flow to work in our calling search space of this pattern goes to an internal calling search space that becomes important for our next hop now we do need urgent priority set on this so it matches immediately and we're gonna send the call to 3,000 internally in our system all right so let's look at this internal calling search space the internal calling search space has a bunch of stuff in it but the the in alarm is going up the important one is the DN partition okay now we have some other internal stuff we have things for form a caste CCX unity whatever I have things in here for future growth of the lab but this is the important one that is what we actually set on our extensions so if we go and look at a device which only have one registered soft phone for the lab and we can see that the line level it's in that D in partition so we now know that that translation profile can flow from the Gateway do that in Bound calling search space and then cost can flow out of that translation pattern towards our internal calling space okay so what what does this do what does globalisation do it gets all of our numbers to one place and then we can route it within the system easily from that point okay so this whole number including the plus and the 1 can be on our D ends it doesn't have to be in a translation pattern like this it can be directly on the D ends or we can have a mixture of both a four digit five digit extension and a fully globalized and so we'll take a peek at that as well first I want to show you the transforms to where we go from the fully globalized to localize for our calls inbound so let's take a peek at are transformed patterns and we're going to look at the calling because we're going to localize for what our phone displays see now we have stuff in here for outbound as well but we want to look at these phone localizations we have this plus dot bang now a plus 1 dot 304 bang now what this does this is for in my local area we have a 304 area code so I put in my local ones here and we can transform this to what we see our phone display or our color ID when we receive a call so what this transform does is it gets rid of the pre dot so we strip out all this plus one stuff in front of the dot get rid of all that so all we see is through four in the number now if your local area is used to see in seven digits you could put the dot over here get rid of the area code alright that's what this is for it's stripping off for localization to what we want our phones to see so when a call comes in we're not gonna see the plus one we're gonna see just the three or four and how is this applied it's on the device pool so on our main HQ device pool is where our transforms are set and they are right here on the calling party transformations alright so let's go ahead and set the calling search space for that which is the phone calling calling search space alright and then we'll save and reset this device pool and that popped up on my other screen there we go we're gonna just reset this device pool now that the setting will be in place when we start our test calls also wanted to show you what it's like to have fully globalized within our devices itself okay so within our directory number we could have sent here just full plus-one globalisation here now I'm just saying through a four five five five so that can be right there on our directory number and it will match coming in okay so that's one way to do it you would just have to have this partition in something I would name it differently I wouldn't call my DN all right I would name it differently and have it to where the Gateway calling search space can't reach this partition okay that's one way to do it translation patterns to translate it into your internal call plan is another way or if you're transitioning or don't want to bother with the fully qualified write in the directory number that's fine and you really don't want to do a whole bunch of translation patterns well when you set up and do bulk administration and the phones or whatever the case is you can also have your internal calling plan four digits five digits whatever it is and then down here with your Eden 164 alternate number hey guess what that's for you could go ahead and put a mask in here let's say you have a range of D IDs right so you could just do plus one three or four five five five and then have a mask and you can see that this one already knows about this 3000 that's on our directory number then you add it to the route local route partition by giving it a partition and I have this e dot 164 D in partition already in here and it's four things just for this I have this D in partition it's different from our Lydian so we could just add this a dot one sixty four D in partition to our inbound calling search space and calls can come directly to a number that matches right here so we can mix and match all of these different ways to get inbound calling to work just about matching the fully globalized to your internal call doubt land okay I have used this method a lot especially when you know migrating systems that are already in four digits or five digits or whatever the case is but we want to use leverage this fully-qualified a dot 164 number so I will use this field and put ad ID in here with the plus one and this works great as long as the calling search spaces also has this in it so in this case we would go to our inbound calling search space and we would add this dot 164 D in right down here like this and that's how that would work now in my lab I'm gonna stick with just doing translation patterns okay so that is basically inbound calling we have looked at how our gateway settings first deal with the globalization by prefixing this plus one or if you've had fewer digits coming in by your carrier you would stretch that out to make it full of globalized however you need it like my case my air code through a four if I had four digits coming from the carrier it would look like that that just stretches it out to its normal fully qualified I should say e dot 164 format okay we also want to make sure that our routing is good so are calling search space is there to direct calls specifically where we want it about what is in this calling search space then we route it with the translation patterns by matching that plus one this could be a mask or a specific D ID as long as this partition matches what's in that gateway calling search space then we translate to a calling search space that this can get to to reach our internal call plan and in this case we're just going to three thousand so with all that said let's place a test call you so you can see exactly what does on the caller ID of the phone so let me pull up there we go my soft phone has three thousand on it and I'm gonna call from another lab number and we should see that coming in now and there we go so we can see the calling number and notice there we go notice that there is no plus one on the from number go ahead and hang up that call so our transform work that we applied to our device pool it's not showing the plus one in front of that number even though it's prefixed in the Gateway with a plus one that is the localization part and the globalization is getting everything that comes through that system in that fully qualified a dot one sixty four format so that way we know that it's always in that format when we're doing routing when we're doing like a AR when we're doing calls to anywhere within the system or telling hop off or anything like this it makes everything easier with the routing and the cough low alright so now even though this is kind of a outbound call conversation you just saw that that inbound call worked comes in the gateway with the plus one goes through our system and then is localized with the transform so our display just shows the three or four however if we go to our received calls and look at that it has the plus one so I can just hit redial on this and we'll talk about this in more detail in our outbound call flow but all I have to do is hit Dow and that will call back out all right because of the fully qualified format that you know the newer phones they pull from calm editor to get the call history and so because that +1 was actually on there was just transformed away remember about our device pool setting and the calling party right here we have this transform calling party transform this phone calling partition is in that calling search space that we just applied on the device pool so this matches anything this matches one three or four and it takes off that plus one well this will do the same thing if I didn't have this we'd still see the same display this is just for a local three or fours and what I want to do with that I'm showing this here because we could put the dot over here and only see seven digits for local calls okay and all we're doing in here it's discard from the pre dot that's it so that is our discussion on inbound call flow we've seen the inbound call test we've seen how this transform and why this matters right on the device pool on getting our call in party localized to what we want our users to see and what they're used to saying but then it gets it within our system it gets that call to where we want it we can do it via a translation pattern or we can do it on the device level by adding that one 64 section right here or putting it on the lawn itself so we have a quite a few options for inbound call flow now we're going to get to our next topic in the next video an outbound call flow and how all that routing works and I hope that this has been very informative for everyone I hope you've enjoyed it I hope you've got something out of it please like and subscribe my video so to get more and more out for you after this series we're going to look at unity integration and Gateway integration so that's what's up and coming and until then thanks for watching

Channel: Go CodeGuru

Views: 829

Keywords: CUCM, Cisco, voip, voice, code guru, CCNA, CCNP, CCNP VOICE, cisco voice training

Id: BH8h_84hdY8

Length: 29min 9sec (1749 seconds)

Published: Wed Nov 14 2018