Between the last two Nuggets, which have explained to what
partitions and calling search spaces are and given a flurry
of examples on how to implement them, you should
have a good foundation on which we can start building.
So now get ready Neo, for the world of the real.
Let's talk about central dial plans and emergency call
routing, using partitions and calling search spaces.
This is where it gets--
I'll say-- pretty scary and pretty cool
all at the same time.
Now here's the scenario.
You have a centralized call manager cluster
sitting over here.
All of your servers exist at one location.
We'll just say it is Arizona.
And you have maybe 500 IP phones sitting there in
Arizona at this big corporate office.
Now you support a remote location.
Let's just say it's Minnesota.
And Minnesota is small enough-- they
only have 20 IP phones--
that you decided not to put in a call
manager cluster solution.
There you just want to run it in a centralized dial plan
scenario to where these phones go across the WAN to get their
call manager connection.
But at that location, you've installed
and their own gateway.
Let's just draw it right here.
It'll be a logical one, which supports both the PSTN
connections as well as the WAN connections.
Maybe in Minnesota you decided to get four analogue FXO ports
coming into that router so that you don't have to, you
know, route them across the WAN and then across the PSTN
for them to call locally in Minnesota.
Because you're going to pay a needless long distance because
you're going to originate a call from Arizona to reach
phones that are local here in Minnesota.
Likewise, you want to have those analog trunks.
Because if one of these phones decides to dial an emergency
number like 911, you want it going out that local gateway
so that all the fire trucks show up at the right location,
rather than showing up in Arizona at their PSTN.
That's a fire truck.
So this is where we have to have some trickery, if you
will, with our dial plan.
What we'll need to do is create two PSTN dialing plans,
one for each location.
Watch this.
This is actually pretty neat.
When I saw this the first time, I was like, ah, that's
pretty slick.
So I'm going to create a nine.
Let's just do two through nine.
Let's create a 10-digit dialing, a local dialing for
Minnesota--
XX-XXX-XXXX.
So that's 10-digit dialing.
And then we'll do nine.
And let's just make it easy on us.
Whoa, not too easy.
One, and so that will be our long distance.
So you'll get the idea with this.
So this is our Minnesota dial plan.
And we're going to point that to the Minnesota gateway.
I'm getting confused with all my drawing tools here.
So I'm going to point that to the Minnesota gateway.
I'm going to say, OK, if these guys dial these numbers, then
I'm going to point them there.
Now here's the catch.
I'm going to create a second dial plan.
Let me see if I can do this here-- copy and paste--
that does this exact same dial plan, but
this time for Arizona.
And I'm going to point that one to the Arizona gateway.
Maybe they have a T1 line to the PSTN and whatever WAN
connection.
But I'm going to point these same exact patterns to the
Arizona gateway.
Now the question that's brewing in everybody's mind--
so these phones over here are managed by the same call
manager cluster as here.
They're all just phones.
So somebody in Minnesota picks up and dials nine and whatever
number they're dialing.
How does this call manager cluster know?
Because the Minnesota phone dialed it to send it out that
way, and somebody in Arizona dialing the same exact number,
the call manager cluster would know somehow to
send it out that way.
Well, are we or are we not in a section on partitions and
calling search spaces?
So what we're going to do is we're going to actually create
these same patterns, and we're going to put them into
different partitions.
We might say this is the Minnesota PSTN partition that
those guys are in.
And then this one is the Arizona PSTN partition that
those guys are in.
Then we're going to create two different
calling search spaces.
We'll CSS_AZ and--
I get so excited I can't even write anymore--
CSS_MN.
And we will put these guys, these guys, like that and
assign this calling search space to
the phones in Arizona.
Are you getting it?
Come on, somebody stand up and say, amen brother!
And that's what we're going to do to put this
restriction in there.
So it's not that the call manager magically knows that
this phone is in Minnesota so I'm going to use this.
The phone itself is logically restricted from even using
these patterns, because they are in a different partition
that its calling search space does not have access to.
So what would that configuration look like?
How does the call manager let you create duplicate patterns?
Let me show you.
I'm going to go into the Call Manager Administration.
Well, let's do this.
I'm going to go to Route/Hunt.
I've got the patterns right here.
Now I've got these created from the previous Nugget that
we created.
Let me do this.
No, I'm not going to do that.
I'm going to go to this one.
I'm actually going to remove it from this little local
partition that's in.
I'm going to remove all of them from their partition.
And I actually delete the international one, just
because it wasn't part of our example for now.
So these guys have been removed from the partition.
I did that because I want to show you something.
Watch what happens.
I'm going to go to Add New.
Actually, there it is, nice and easy in my list, two
through nine, dah, dah, dah.
Hit the Tab key and say, well, I'm going to send it out.
Maybe this represents the Arizona gateway.
So I'm going to put that in there and hit Save.
Watch what happens.
Yeah yeah, yeah yeah.
I was like, it took it.
No it doesn't.
No, it says, Add Failed.
I'm sorry, I can't.
Because why?
Why, call manager, did you not take this?
A route pattern exists with the same pattern and what--
partition.
You cannot have a duplicate
patterns in the same partition.
So here's how we would have to do this.
We would go into the class of control.
Now I've got my little dummy partitions from before.
But I'm going to create some new ones.
I'll do just like we had on there--
Minnesota PSTN and Arizona PSTN.
Save those guys, so those partitions are now created.
Come over here to the route patterns.
And by the way, you can do everything with the Bulk
Administration Tool.
If you've got a bunch of patterns, go
BAT and assign that.
We'll just say these are, for grins, part of
the Minnesota PSTN.
We've now assign that guy.
He's in Minnesota.
Minnesota, that's how they say it there in my horrible
attempt to do that--
Minnesota.
We've now got those assigned.
Now I can click on Add New.
Let's add that nine, two through nine.
I've got it typed in.
That's our 10-digit.
So I'll put description, 10-digit.
But this is for Arizona.
And what I'm going to do-- put that in the
Arizona PSTN partition.
Appoint it to the Arizona gateway, which we are
envisioning as 1051254.
OK, OK, back to Find List--
now, look at that, duplicate route patterns.
But because they're in different
partitions, we're all good.
I'm going to add the one more for grins--
9.1 two through nine.
So we'll do Arizona long distance.
But we'll put that into the Arizona PSTN partition, add
that to the Arizona gateway.
Good, good, go.
Look at that-- we've got now duplicate route patterns.
But they are kept separate because they're in different
partitions.
Remember I was saying in the last Nugget, when I was going
through the examples, you could create a calling search.
Let's say we did.
We create a calling search space, Minnesota-- actually
I'll just write it under here-- that has the in
Minnesota PSTN, followed by the Arizona PSTN partition.
You could do that and then assign this to the actual
phones in Minnesota.
But what would happen?
Well, when they dial nine to do an outside line, it's going
to first try the route patterns associated with this
partition, which are pointing to this gateway.
And it's going to try and go out there.
But by listing both of them, what does that mean?
Would it ever come down here?
Yes, it might.
Maybe this gateway is down.
Well, since it runs the WAN link, that
wouldn't do us much good.
But maybe all of these are disconnected, or all of these
are used up.
You've used all four of those trunks.
At that point, this is going to report full.
It's essentially an invalid destination.
Call manager is going to say, OK, well let's try coming down
here and now sending it across the WAN.
So now by doing it that way, you give the people in
Minnesota their four analog trunks that are going out to
their PSTN locally.
But if those are all four used up, we can route them out the
Arizona PSTN that's the T1 line, a little larger pipe.
Yes, you're going to pay long distance likely if they're
calling the local Minnesota number.
But at least they get service.
Tell me that's not awesome.
Like once you get that, you're like, oh.
It starts becoming real.
And you go, OK, I get these partitions and it's starting
to make sense.
I don't know if you've ever played with it, but there is a
free Linux-based IPBX--
is what you would call it--
called Asterisks.
It's free if you want to start hacking your way through it.
There's actually a lot of people, even corporations,
universities, that have decided to use Asterisks,
because obviously it's free.
But you get no support.
It's just one that you kind of piece your way together.
They have this same style of configuration.
I like the name that Asterisks uses for it.
Their partition concept works similar to this.
They call it a context.
As in a phone has permission to access this context or this
grouping of phone numbers that you've
placed inside the context.
So sometimes words play games.
And I can start saying, OK, maybe
partition didn't make sense.
But I see that the phone is able to access their context,
which says that you can dial these phone numbers, so that
similar style of thing.
OK, let me clear all that off.
And now do you see how emergency call
routing would work?
It's exactly the same concept.
I put it as two different ones, but work hand in hand.
In the United States, we use 911 and 9.911 as our patterns
for emergency call routing.
We would again create duplicate patterns.
Here I'll just give you an example of it.
We come in here to the route patterns, and I would say, OK,
911 will now be associated.
This will be the Minnesota 911.
I'll be put in that PSTN partition.
And that will go out the Minnesota router, which we'll
just is that guy.
So that 911 would now be separated, and we would create
one for 9.911 as well so, people are in their right mind
when they call, they can.
But 911 for Arizona would be associated there.
And that one would go to the Arizona PSTN router.
So this allows you to truly kind of-- and I like the
name-- partition your dial plan into separate groups so
that whoever has access to those partitions
allow you to do that.
Now last thing I'll mention here is you might have the
question, well, if you create 911 for Minnesota and appoint
it that way, and then you have a 911 emergency call for
Arizona and point it that way, should you put both of those
into the calling search space for Minnesota?
So you'll have 911 in Minnesota first and then 911
in Arizona second.
So if this is down for whatever reason, they'll come
out here and get 911 or emergency service.
I would leave that one to you and a whole big
ole group of lawyers.
I'm not going to answer that question.
Because here's what happens--
someone severs a leg.
I don't know why I always think of severed limbs when I
think of 911.
But someone severs a leg in Minnesota, dials 911.
It just so happens that all the lines are full.
So call manager routes them out to Arizona.
The person is in a delirious state, and the 911 operator is
saying, OK, we see your location as 5935 South 54th
Street, Phoenix, Arizona.
The person's like, yes, emergency bleeding.
And they're like, OK.
All the emergency trucks show up here, and person with
severed leg perishes.
Jeremy's ethical humanity is like, good grief.
Get them out there, and at least give them the chance to
tell them no, I'm not in Arizona.
I'm in Minnesota.
Please route my call to the right 911 provider.
Give them the chance.
But good grief, our system is messed up to where if somebody
did that and they're like, oh, I lost a limb because you
routed me out Arizona, I don't know.
This is a Cisco course.
This is not standing up in court and saying, look.
I don't know how all that would work.
You see where I'm going with this, right?
OK.
So you have the possibility of routing them
over there as a failover.
I don't know if you should or not.
But what I will say is make sure that if they call 911 you
don't accidentally route them out the wrong location because
of a configuration mistake.
I mean it's one thing to have people say, the network's down
because you made a mistake.
But the whole severed limb thing takes it
to a whole new level.
I hope this has been informative for
you in so many ways.
And I'd like to thank you for viewing.