|
0:00:15
|
OK guys we're back and just about to move on to the next task,
|
|
0:00:19
|
but before we do, did find the issue
|
|
0:00:23
|
it was a problem with my start-up config as a modified version of the
|
|
0:00:26
|
final config from deep dive module 15.
|
|
0:00:29
|
And specifically the problem with the SIP phones was that
|
|
0:00:33
|
let me just do a show run | 2 section voice service.
|
|
0:00:40
|
Under voice service VOIP and the sub section of SIP,
|
|
0:00:45
|
when you're just copying and pasting and of course I'll correct this
|
|
0:00:49
|
or when you load them to INE router or even if you just load them into
|
|
0:00:51
|
your own rack, the order that which the configuration comes up,
|
|
0:00:57
|
but the order that the configuration comes up is voice service VOIP,
|
|
0:01:01
|
whole section including the SIP subsection is
|
|
0:01:06
|
in the router earlier, in fact let me just, for the sake of demonstration,
|
|
0:01:11
|
show the whole, so here's the voice service VOIP.
|
|
0:01:17
|
And this SIP and specifically the bind control and bind media
|
|
0:01:20
|
or bind all which adds both of those, that comes before
|
|
0:01:27
|
the voice register global and more specifically voice register dn and pools
|
|
0:01:33
|
which create any dial peers and it also comes before all of the rest of
|
|
0:01:38
|
any of your dial peers, well here's the thing.
|
|
0:01:42
|
If you do not have a VOIP dial peer then the router's logic
|
|
0:01:46
|
is how can we bind the control of signaling if we don't have any
|
|
0:01:51
|
VOIP dial peers? You might think well just take it as a configuration.
|
|
0:01:56
|
You take other things related to the signaling protocol.
|
|
0:02:00
|
But don't have any VOIP dial peers and then just you know
|
|
0:02:03
|
apply it later whenever we do, well for some reason the router
|
|
0:02:06
|
doesn't like that no matter how many times you put the
|
|
0:02:09
|
commands in and we saw this in the last deep dive module.
|
|
0:02:13
|
It will not take those commands until you have a VOIP dial peer.
|
|
0:02:17
|
So I had already put those in, so it's copying and pasting
|
|
0:02:20
|
the start up config, then VOIP dial peers were
|
|
0:02:24
|
created with the voice register pools and dns.
|
|
0:02:26
|
And I had to go back and put this in, so essentially
|
|
0:02:31
|
the phones were being told by this command in their configuration files
|
|
0:02:36
|
that all of the signaling for SIP should be coming
|
|
0:02:41
|
from 1771 254.3 but everytime they try to contact
|
|
0:02:46
|
that they didn't get a response from that IP address.
|
|
0:02:49
|
They probably did get a response from the closest interface,
|
|
0:02:53
|
which is the fas00.11 voice VLAN sub interface.
|
|
0:03:01
|
OK? So that was the problem, we can clear this back off.
|
|
0:03:08
|
And get going with our next task 16.2 IOS voice translation rules and
|
|
0:03:14
|
a form of globalization, we're actually gonna do a lot more of that
|
|
0:03:17
|
in the Module 20 expert internet working with CUCM
|
|
0:03:21
|
in CME, so we're told to ensure that all inbound calls
|
|
0:03:28
|
from the PSTN reach their appropriate four digit extension.
|
|
0:03:33
|
Provision a method for this that takes into account that not all
|
|
0:03:36
|
extensions are registered yet and that they're maybe more dial
|
|
0:03:39
|
peers created later. Essentially what this is saying,
|
|
0:03:44
|
in a cryptic sort of way, that could be the way that your
|
|
0:03:47
|
lab is worded, so that's the reason I did it
|
|
0:03:51
|
is that we can't use, we cannot a voice translation
|
|
0:03:57
|
rule on an inbound dial peer because there could be more dial peers
|
|
0:04:04
|
created later, so instead we have to do it on an inbound voice port
|
|
0:04:11
|
from the PSTN also ensure that for all outbound calls to the PSTN,
|
|
0:04:15
|
the calling party number display reflects the following
|
|
0:04:18
|
for the respective phone dialing.
|
|
0:04:20
|
Calls to emergency local or national should display the Branch2
|
|
0:04:26
|
calling phone's DID number with the beginning geographic
|
|
0:04:30
|
code so for example 020 703 3001 or 2 or 3003 or 4
|
|
0:04:39
|
calls to international number should display the Branch2 calling phone's
|
|
0:04:42
|
E164 number beginning with country so 31
|
|
0:04:46
|
the 0 is not there, if you want a little bit more explanation on that,
|
|
0:04:50
|
probably go back and watch Modules 10 and 11
|
|
0:04:54
|
talking more about dial plans and then 2070333 and then
|
|
0:05:00
|
the XXX DID 1000 series numbers that Branch2 site phones. OK.
|
|
0:05:09
|
So let's switch over to our router,
|
|
0:05:12
|
and we're gonna drop in to config T mode and we're gonna begin
|
|
0:05:18
|
we're gonna start and create voice translation rule 1,
|
|
0:05:26
|
and we're going to say rule 1, we know from past that
|
|
0:05:32
|
this right here or maybe not, if you haven't watched some of the others,
|
|
0:05:36
|
voice translation rule 1, this is actually rule set 1.
|
|
0:05:39
|
It's a set of rules and I didn't just x it out here,
|
|
0:05:46
|
it doesn't actually call it rule set, it just calls it rule 1.
|
|
0:05:51
|
But if you do a debug voice translation,
|
|
0:05:54
|
you will see that it actually refers to this as rule set 1.
|
|
0:06:00
|
So as not to confuse you with rule 1, rule 2, and rule 3 that
|
|
0:06:03
|
follow below translation rule 1 or actually translation rule set 1.
|
|
0:06:09
|
OK. And some rules or I should say some laws
|
|
0:06:16
|
with voice translation rules, we have to have a matching number,
|
|
0:06:20
|
and a translated number and this
|
|
0:06:26
|
by the way some people have talked about or mentioned over the break
|
|
0:06:30
|
actually one person did that there was some voice clipping, is there,
|
|
0:06:35
|
Is everyone hearing me OK? Or is there any voice clipping?
|
|
0:06:38
|
Or breaks in the audio right now?
|
|
0:06:45
|
Give me a comment or a checkbox if there is no breaks
|
|
0:06:52
|
and a, I don't know what else is there, an x
|
|
0:06:58
|
or disagree if there's a problem with the voice at this point.
|
|
0:07:04
|
Can everyone either give me a checkbox or an x?
|
|
0:07:09
|
OK, great sounds like at least a couple people
|
|
0:07:11
|
are reporting back that the voice is fine right now.
|
|
0:07:14
|
Occasionally I will mute it to cough so please disregard that.
|
|
0:07:21
|
OK. Adjust now. Alright so voice translation rule 1,
|
|
0:07:26
|
we have to have a match number and then we have to have a
|
|
0:07:30
|
a replacement pattern or translated number, these have to be
|
|
0:07:34
|
delineated by a set of forward slashes.
|
|
0:07:37
|
So a forward slash then your matched number then a forward slash
|
|
0:07:42
|
right now I have no match number, it's null, then a space,
|
|
0:07:49
|
and then a forward slash and then your translated number,
|
|
0:07:51
|
then a forward slash, so if I did this right here,
|
|
0:07:56
|
two forward slashes, space two forward slashes, it would translate
|
|
0:08:00
|
nothing to nothing, or really anything to anything.
|
|
0:08:03
|
It wouldn't match anything explicitly and anything that is not
|
|
0:08:07
|
explicitly matched is forwarded uninhibited to the replacement pattern.
|
|
0:08:14
|
OK? If I did something like match so forward slash
|
|
0:08:21
|
forward slash so nothing in there for the match pattern space
|
|
0:08:25
|
forward slash 213 forward slash then
|
|
0:08:30
|
any amount of digits that came in as part of the match pattern,
|
|
0:08:35
|
and whether it was calling or called inbound or outbound,
|
|
0:08:39
|
that would all depend on future things where I apply this rule set.
|
|
0:08:44
|
So for right now, whatever type number, whatever direct
|
|
0:08:46
|
it is we're going to apply it to, anything that's matched will be
|
|
0:08:51
|
auomatically attended to the end of 213 uninhibited
|
|
0:08:57
|
because all we're doing here is essentially saying add 213
|
|
0:09:00
|
because again anything not explicitly matched will be
|
|
0:09:05
|
forwarded in the position that it is currently in
|
|
0:09:08
|
to the translated or replacement number.
|
|
0:09:13
|
Now if I did something different like a regular expression
|
|
0:09:16
|
like dot which indicates any one character or digit,
|
|
0:09:21
|
and then plus which is a regular expression that says
|
|
0:09:25
|
any one or more of the previous character,
|
|
0:09:31
|
which was a wild card of anything,
|
|
0:09:35
|
so this essentially means any amount of digits,
|
|
0:09:39
|
any random format of the digits and we're matching
|
|
0:09:43
|
all of them explicitly. Another way to write this would be with an asterisk.
|
|
0:09:47
|
That might be a little more intuitive to people's wild card matching.
|
|
0:09:53
|
OK? So I could do forward slash dot anything
|
|
0:09:58
|
space forward slash 213 forward slash, now that would actually take
|
|
0:10:05
|
any number and turn it into 213, it wouldn't be
|
|
0:10:10
|
automatically uninhibited forward to the dn because we did match it.
|
|
0:10:14
|
And this is not like a pots dial peer where you have to explicitly match
|
|
0:10:17
|
the number, all you have to do is match it and
|
|
0:10:19
|
if you match it, then you are changing it.
|
|
0:10:22
|
OK, so that's a rule, also we can do tests back out it
|
|
0:10:28
|
executive mode, it's not on a config T, so we'll do test voice translation.
|
|
0:10:35
|
And we have to say the rule set so translation rule set 1,
|
|
0:10:39
|
and then the number, so let's say 555 212 6789.
|
|
0:10:46
|
We translate any number that we match,
|
|
0:10:50
|
into because we did match the number into 213.
|
|
0:10:56
|
Now if I said the previous forward slash forward slash space
|
|
0:11:02
|
translated or replaced number as forward slash 213,
|
|
0:11:05
|
forward slash to end it.
|
|
0:11:08
|
Then I did my test, now we see that
|
|
0:11:12
|
555 212 6789 is translated to prefix 213,
|
|
0:11:20
|
to the existing 555 212 6789.
|
|
0:11:26
|
OK?
|
|
0:11:28
|
I can also do things like regular expressions, so I can say
|
|
0:11:33
|
well actually before I do this, let's match 555
|
|
0:11:38
|
and change it to
|
|
0:11:42
|
888, now if I don't put that ending
|
|
0:11:47
|
forward slash then it doesn't know that the command is
|
|
0:11:51
|
terminated or delineated properly so I do have to have those.
|
|
0:11:56
|
Now if I do my test on, let's say, let's leave it as it was 555 212 6789
|
|
0:12:06
|
I note that it matches 555 212 6789,
|
|
0:12:10
|
and it translates it into 888 212 6789.
|
|
0:12:15
|
So it matched the 555 of the 10 digit 555 212 6789.
|
|
0:12:21
|
And translated just that part, the rest of it was not matched.
|
|
0:12:25
|
And you say that this matches 555 only, no.
|
|
0:12:28
|
This doesn't say only match 555, if we wanted to say only match 555,
|
|
0:12:35
|
we would have to have a dollar sign which is a regular expression
|
|
0:12:38
|
indicating the end of the string.
|
|
0:12:41
|
Now when I test this, this won't match, didn't match with any of the rules.
|
|
0:12:49
|
So if I change it to just 5552, it still doesn't match with any of the rules.
|
|
0:12:55
|
If I change it to just 555, now it matches and it's replaced with 888.
|
|
0:13:01
|
Because I put the dollar sign saying the end of the string.
|
|
0:13:05
|
What if I tested 323 555?
|
|
0:13:10
|
That matches 323 555 changes it to 323 888.
|
|
0:13:17
|
Again I only indicated the end of the string.
|
|
0:13:20
|
So if I would have done that same test again,
|
|
0:13:23
|
with a 9 at the end, it would match, but as long as the
|
|
0:13:27
|
because that the string matches 555 which could be anything,
|
|
0:13:32
|
555 and those three fives have to be the end of the string.
|
|
0:13:39
|
I could have 323 555 212 555
|
|
0:13:44
|
it still ends with a triple five and only that will be changed.
|
|
0:13:48
|
So now I have 323 555 which was left uninhibited,
|
|
0:13:53
|
212 888 because remember up here I was just saying the last
|
|
0:13:58
|
three fives in the string then my terminator,
|
|
0:14:03
|
those are the ones that are gonna be replaced with 888.
|
|
0:14:06
|
So if I only wanted to match 555 explicitly and only,
|
|
0:14:12
|
I would need to change my rule from match 555$ to match
|
|
0:14:19
|
carrot 555$.
|
|
0:14:22
|
Now that won't match.
|
|
0:14:27
|
S let's ust go back to 323 555 that won't match,
|
|
0:14:32
|
555 212 that won't match,
|
|
0:14:37
|
but 555 explicitly will match and be translated.
|
|
0:14:42
|
So regular expression such as carrot and dollar sign also such as
|
|
0:14:48
|
dot which actually is an irregular expression.
|
|
0:14:50
|
Actually that might be the asterisk. Some of them are
|
|
0:14:54
|
Cisco specific, by the way this is a implementation
|
|
0:14:57
|
but it's a Cisco tweaked implementation and I take liberties.
|
|
0:15:02
|
It's an implementation of the unix new sed,
|
|
0:15:06
|
SED or Serial Editor but it is a tweaked version.
|
|
0:15:12
|
So do show run | to section voice translation,
|
|
0:15:17
|
so here's what we have so far
|
|
0:15:21
|
OK.
|
|
0:15:23
|
So that was just kind of a beginning actually
|
|
0:15:26
|
let's do one other thing in terms of rules.
|
|
0:15:30
|
Let's change this to show sets.
|
|
0:15:33
|
So if I say match with carrot, let's do without a carrot to begin with.
|
|
0:15:39
|
Let's say 555 3,
|
|
0:15:45
|
let's actually be specific to what we're using in voice today.
|
|
0:15:48
|
703 3...
|
|
0:15:54
|
OK that's the number I want to match, but when I translate it,
|
|
0:15:57
|
I just want to translate it down to four digits.
|
|
0:16:01
|
So four digits, I'll put it in as,
|
|
0:16:06
|
what will I do? Can I do 3...? No it doesn't like the dots at the end.
|
|
0:16:12
|
Some things will take those like a number expansion.
|
|
0:16:16
|
But and even translation rules, but not voice translation rules.
|
|
0:16:21
|
So what I have to do is kind of say, hey I just want to match
|
|
0:16:25
|
this information or maybe even just this information
|
|
0:16:28
|
these wild cards and forward that on to the end.
|
|
0:16:32
|
Alright. Well here's how we have to do it.
|
|
0:16:37
|
We have those three dots, we need to set up, we have that closing
|
|
0:16:42
|
forward slash, we need to set up parenthesis
|
|
0:16:45
|
opening and closing parenthesis around them
|
|
0:16:47
|
to say that's a set of numbers that we want to call
|
|
0:16:51
|
to our translated number.
|
|
0:16:55
|
So I could say call set number 1 which is done with the operator
|
|
0:17:01
|
called backslash and then the numeral of the number of the set
|
|
0:17:05
|
none canonically speaking so we don't start counting by zero.
|
|
0:17:08
|
we start counting by 1, so backslash 1 will call that set of digit.
|
|
0:17:15
|
Wait a minute, I needed that three, I can do one of two things,
|
|
0:17:18
|
I can either move my parenthesis to the outside of the three.
|
|
0:17:21
|
Or I can just specifically put that three in there as a digit,
|
|
0:17:27
|
and then say backslash 1 which the backslash 1 calls the first set.
|
|
0:17:33
|
And then end it with a forward slash, now the problem is,
|
|
0:17:37
|
let's do our test.
|
|
0:17:42
|
If I match 703 3001, it didn't match with any of the rules.
|
|
0:17:50
|
And the reason is, these parenthesis are special character
|
|
0:17:54
|
that have to be escaped. So IOS doesn't bark at you, it didn't
|
|
0:17:58
|
say invalid input, it said that before, but not with the parenthesis.
|
|
0:18:03
|
I have to go back in and add backslashes to escape them.
|
|
0:18:08
|
Backslashed in the matched number are escaping special characters.
|
|
0:18:17
|
Backslashes in the translated number indicate sets
|
|
0:18:21
|
from the matched number that we want to append.
|
|
0:18:24
|
Now if I do my match, now it will match 7033
|
|
0:18:31
|
anything, anything, anything, so 7033 001
|
|
0:18:36
|
and change it to 3 backslash 1 so 3
|
|
0:18:43
|
and then the first set. Another way to do this is do debug voice translation.
|
|
0:18:52
|
And now let's do this test,
|
|
0:18:56
|
and we'll see that we have a successful substitution
|
|
0:19:00
|
here was the pattern that was actually sent to the translation engine.
|
|
0:19:04
|
Here was the matched pattern as it was configured.
|
|
0:19:09
|
Notice they don't have the backslashes or the forward slashes but
|
|
0:19:13
|
they are necessary to work. The replacement pattern as it was
|
|
0:19:17
|
configured was 3 and then backslash 1.
|
|
0:19:20
|
And then the actual replace pattern and watch the word wrap,
|
|
0:19:24
|
replace pattern was 3001.
|
|
0:19:27
|
So this debug voice translation can really be useful to you.
|
|
0:19:33
|
OK. So do show run | 2 section voice translation, let's see what we have
|
|
0:19:40
|
This works just fine, however it's pretty complex and the only reason I
|
|
0:19:44
|
did it was simply to show you of the power and complexity
|
|
0:19:48
|
that voice translation rules can yield and we did this
|
|
0:19:51
|
along with a number of other things in, I believe it was Module 10.
|
|
0:19:56
|
Yes, Module 10 and some others as well when we were talking about SIP.
|
|
0:20:02
|
Trunk to a SIP gateway, to the PSTN, and doing globalization
|
|
0:20:08
|
the plus sign adding so there is another module,
|
|
0:20:12
|
that goes into a number of other voice translation examples,
|
|
0:20:16
|
but if you missed any of what we just went over in terms of rules,
|
|
0:20:20
|
and you're watching the recording, then you know stop and
|
|
0:20:23
|
move the playhead back a little bit and rewatch that.
|
|
0:20:28
|
But let's go on to actually our configutation for today.
|
|
0:20:31
|
So rather than a little bit more complex rule like we have here,
|
|
0:20:35
|
let's just scrap this and try to create a simple rule, rule 1
|
|
0:20:42
|
forward slash 703 and by the way we don't, I guess know
|
|
0:20:46
|
what's coming in from the PSTN, so probably it might be good to
|
|
0:20:50
|
do debug ISTN Q931 and just place a call in from the PSTN.
|
|
0:20:58
|
Let's place a call in from a local number
|
|
0:21:05
|
OK we get busy tone because it's unallocated.
|
|
0:21:08
|
Because 703, the called party number 703 3001
|
|
0:21:12
|
isn't configured, that's we're about to do our voice translation for.
|
|
0:21:16
|
But it comes in with seven digits and I already knew that
|
|
0:21:20
|
that's what I was starting to configure but
|
|
0:21:22
|
just wanted to make sure you knew why I was doing it,
|
|
0:21:25
|
so rule 1 703 now what did we want to have left 3001.
|
|
0:21:32
|
Remember we said anything that we don't explicitly match
|
|
0:21:37
|
will be appended to the end as it was unharmed.
|
|
0:21:41
|
And anything that we explicitly match will be translated to whatever we
|
|
0:21:45
|
explicitly translated to. What if we just match 703
|
|
0:21:50
|
and translate it to nothing? Let's test that rule.
|
|
0:21:58
|
Do test voice translation rules 703 3001,
|
|
0:22:02
|
that does the same thing it matches 703
|
|
0:22:06
|
and it translates it to nothing, gets rid of it
|
|
0:22:10
|
leaving just the 3001, so that should work just fine.
|
|
0:22:15
|
So let's try our call in again.
|
|
0:22:20
|
The only problem is we haven't applied it yet, of course. OK.
|
|
0:22:25
|
So now let's move on and jump back out and say voice
|
|
0:22:29
|
translation profile, so we've got our translation rule
|
|
0:22:33
|
and our translation profile and we'll call this one,
|
|
0:22:37
|
we will call it seven digit
|
|
0:22:42
|
DNIS called number 24.
|
|
0:22:47
|
So we're translating seven digits down to four and we're gonna translate
|
|
0:22:52
|
ans here's where we can do called, calling, redirect called,
|
|
0:22:55
|
or redirect traget that I explained earlier in the slide in intersection.
|
|
0:22:59
|
We're gonna do translate called and rule set number 1.
|
|
0:23:04
|
Then we're gonna jump into our voice port,
|
|
0:23:09
|
:15 because we were told there could be more dial peers
|
|
0:23:12
|
in the future so we don't want to do it in our generic inbound dial peer.
|
|
0:23:16
|
And we're going to say translation profile
|
|
0:23:21
|
and it's going to be in the incoming direction and it's gonna be the name
|
|
0:23:25
|
seven digit DNIS to four, now if we hit redial,
|
|
0:23:33
|
the call should ring. Why? Well I don't know.
|
|
0:23:37
|
Let's check, let's get rid all of our screen and scroll back,
|
|
0:23:43
|
and do debug voice translation
|
|
0:23:48
|
and do a dial from the PSTN in.
|
|
0:23:53
|
And we could answer the call, but we'll go ahead and hang it up.
|
|
0:23:56
|
And so we've got our ISTN debug in here and here we see
|
|
0:24:02
|
matched with rule 1 with rule set 1,
|
|
0:24:05
|
successful substitution the actual pattern, the configured matched pattern,
|
|
0:24:10
|
the replaced pattern for the match pattern which was nothing.
|
|
0:24:14
|
And then the result, the effective replaced pattern.
|
|
0:24:20
|
OK. So it goes, actual pattern
|
|
0:24:24
|
configured matched pattern, configured replace pattern
|
|
0:24:29
|
result of the actual replaced pattern.
|
|
0:24:33
|
OK. And that's what allowed it, plus the direct and redial
|
|
0:24:36
|
to go ahead and ring extension 3001.
|
|
0:24:39
|
OK.
|
|
0:24:41
|
So we'll go ahead and do undebug all and go ahead and do debug
|
|
0:24:45
|
ISTN Q931, we stil want to see that but
|
|
0:24:49
|
we don't want to see our voice translation debug all the time.
|
|
0:24:55
|
OK.
|
|
0:24:57
|
I supposes it probably wouldn't be bad, let's go ahead and leave it on.
|
|
0:25:00
|
Do debug voice translation.
|
|
0:25:04
|
OK. Let's clear our screen and we're gonna jump in to
|
|
0:25:07
|
voice translation, don't make the mistake of just saying
|
|
0:25:10
|
translation rule because as I mentioned there is a
|
|
0:25:12
|
translation that's not as powerful.
|
|
0:25:15
|
Voice translation rule set to rule 1 of rule set 2
|
|
0:25:21
|
is going to be that we want to
|
|
0:25:25
|
we took inbound from 7 down to 4,
|
|
0:25:29
|
but now we want to make sure that outbound calls
|
|
0:25:32
|
have their appropriate calling number appended, so right now,
|
|
0:25:37
|
if we just do call out to 112
|
|
0:25:45
|
we see that
|
|
0:25:48
|
our calling party number is 3001.
|
|
0:25:52
|
And we were told local numbers, emergency numbers, so 0703 7333
|
|
0:26:00
|
that still shows four digits, if we do national 0010 704 74444
|
|
0:26:11
|
that still shows four digits and 000 which by the way I looked up
|
|
0:26:17
|
and there is secondary dial tone for SIP so I thought I remember there was
|
|
0:26:20
|
but there isn't at this point,
|
|
0:26:22
|
0001 20, I waited too long talking for interdigit timeout.
|
|
0:26:29
|
000 1206 501 51111#
|
|
0:26:36
|
We see that we are also still sending out calling display of 3001.
|
|
0:26:42
|
So for everything except for international, we want to send out
|
|
0:26:46
|
020 703 3001
|
|
0:26:49
|
and for international we want to send out 3120 703 3001.
|
|
0:26:54
|
OK. So we're in voice translation rule 2,
|
|
0:27:00
|
we're gonna create rule 1 and rule set 2 and this is going to match,
|
|
0:27:06
|
only 3...$ so any 3000 series number,
|
|
0:27:15
|
and it's gonna translate it to 020 703
|
|
0:27:21
|
and we want to call everything that we matched up here,
|
|
0:27:24
|
now we could put this in parenthesis however that's just a little bit
|
|
0:27:28
|
more work and aesthetically it's a little
|
|
0:27:33
|
a little more to think about suppose you could say a little more confusing
|
|
0:27:37
|
but just a little more to mentally process every time you look
|
|
0:27:39
|
configuration especially if you're troubleshooting something that
|
|
0:27:41
|
doesn't seem to be working. So there is two ways that we can actually call
|
|
0:27:46
|
everything that was in the matched number regardless of whether it's
|
|
0:27:50
|
inside of a set or not, the two ways are the special operator
|
|
0:27:55
|
backslash zero which calls everything. We can do a test here.
|
|
0:28:02
|
By the way when I'm adding those rules, you can see that the
|
|
0:28:06
|
debug engine is being triggered as well.
|
|
0:28:13
|
I'm just looking back for my test command, there we go do test
|
|
0:28:17
|
voice translation to 3001, we see that it
|
|
0:28:23
|
it is 020 703 3001. OK, so backslash 0 is one way.
|
|
0:28:30
|
Another way is with, I'm still with rule 1, I'm just overwriting it,
|
|
0:28:34
|
is with the ampersand command.
|
|
0:28:40
|
Wait for this to process and now do our test again,
|
|
0:28:45
|
And it also appends everything to the end.
|
|
0:28:48
|
OK? I like ampersand, it's a little cleaner. Sometimes it's actually hard
|
|
0:28:52
|
to distinguish it from another when you're looking quickly at do
|
|
0:28:56
|
show run | 2 begin let's say voice translation,
|
|
0:29:03
|
Sometimes it's a little hard to distinguish that ampersand.
|
|
0:29:05
|
Some people might like backslash 0, I prefer the ampersand.
|
|
0:29:09
|
But two different ways to accomplish the same thing.
|
|
0:29:12
|
OK? So now we're going to put that into a voice translation
|
|
0:29:16
|
profile and we'll call this one four digit
|
|
0:29:22
|
ANI or calling to 10, translate calling
|
|
0:29:30
|
rule set 2 and then we need another one so
|
|
0:29:38
|
vice translation rule set number 3 rule 1 and rule set 3
|
|
0:29:44
|
will be forward slash, pretty much the same thing, forward slash carrot 3...$
|
|
0:29:55
|
forward slash and we'll translate this one to 3120703
|
|
0:30:03
|
ampersand all of the rest.
|
|
0:30:08
|
And to keep in good form, we'll test it.
|
|
0:30:16
|
Do test rule number 3 for 3001 and we see that the
|
|
0:30:23
|
successful substitution is there, the replace pattern is
|
|
0:30:26
|
well we can see it up here 3120703 3001.
|
|
0:30:31
|
So we will put this into a voice translation profile called four digit
|
|
0:30:41
|
ANI to 12 digis.
|
|
0:30:46
|
We could call it whatever we want, translate, calling or rule set 3.
|
|
0:30:54
|
Alright, so let's erase this screen show run | 2 begin with voice translation.
|
|
0:31:03
|
Here's our rule 1 that's being translated call DNIS
|
|
0:31:08
|
7 dial down to 4 rule set 2
|
|
0:31:12
|
which is translating calling four digit up to 10 ANI
|
|
0:31:16
|
rule set 3 which is translating the same match number
|
|
0:31:20
|
four digit up to 12 for rule set 3, and so we'll go down to our dial peers.
|
|
0:31:28
|
And we'll jump in back into config T and say for dial peer 1,
|
|
0:31:36
|
we're gonna do a translation
|
|
0:31:40
|
profile in the outgoing direction for
|
|
0:31:47
|
tha was gonna be four digit ANI to 10.
|
|
0:31:54
|
Same thing for POTS dial peer 2, pots dial peer 3,
|
|
0:32:01
|
pots dial peer 4, and pots dial peer 5, we're gonna change that to
|
|
0:32:06
|
the 12, the four digit ANI to 12, so notice the difference in the naming,
|
|
0:32:11
|
of our voice translation profiles.
|
|
0:32:16
|
So we'll do a show run again, this time pull up our dial peers.
|
|
0:32:23
|
Write our router config, we can see the difference in our dial peers from
|
|
0:32:28
|
before, let's go ahead and test everything.
|
|
0:32:34
|
So emergency services should show from 020,
|
|
0:32:42
|
0 and then 112 emergency services should still show that.
|
|
0:32:46
|
Good, 0703 7333
|
|
0:32:53
|
to a local number,
|
|
0:32:56
|
should show the proper same number, same calling display.
|
|
0:33:01
|
00 10704 7444
|
|
0:33:05
|
national or long distance, again we were told to show the same thing.
|
|
0:33:09
|
And then for international will be the difference here so
|
|
0:33:14
|
000 1206 501 5111#
|
|
0:33:21
|
and here we're showing country code 3120703
|
|
0:33:28
|
3001 just like we were instructed to do.
|
|
0:33:32
|
So we'd use voice translation rules to show different outbound calling
|
|
0:33:36
|
depending on where the called number was, so different calling
|
|
0:33:43
|
number displayed based on the dialed digits.
|
|
0:33:50
|
OK. And that was the subform of globalization that we had here
|
|
0:33:53
|
was the international, we'll use the same thing,
|
|
0:33:57
|
when we're on Module 20 doing internetworking between the two
|
|
0:34:00
|
if we want to deal with globalization to and from
|
|
0:34:05
|
globalization forward to globalization through 164 with plus dialing
|
|
0:34:09
|
that we went over in Module 10 and 11 extensively for CUCM.
|
|
0:34:14
|
If we want to do that when we're networking with CUCM.
|
|
0:34:16
|
|
