|
0:00:14
|
Okay, so let us take a look at our next task.
|
|
0:00:19
|
Task 7: Mobile Voice Access and Direct Inward System Access or DISA,
|
|
0:00:25
|
which is not what CCM calls it.
|
|
0:00:27
|
They just call it Mobile Voice Access.
|
|
0:00:29
|
They also got something what we mentioned earlier called
|
|
0:00:32
|
Enterprise Feature Access which
|
|
0:00:34
|
accomplishes the same thing but without an IVR
|
|
0:00:36
|
but we are not going to configure because it needs the mobility number
|
|
0:00:40
|
really is meant for smart clients rather than humans.
|
|
0:00:43
|
This is the human version where we get prompts
|
|
0:00:47
|
but a lot of former
|
|
0:00:49
|
Chaos Use or legacy PV Access
|
|
0:00:51
|
called this Direct Inward Access or DISA.
|
|
0:00:55
|
So we were told to set up CUCM to allow mobile connect users
|
|
0:00:59
|
to be able to dial into an IVR
|
|
0:01:02
|
and they do have to be mobile connect users or at least they have to have
|
|
0:01:05
|
remote destination, actually, they have really be
|
|
0:01:08
|
fully configured for mobile connect.
|
|
0:01:11
|
Whether they have a ring schedule that ever rings their phone or not,
|
|
0:01:14
|
is further relevant but they have to have mobility enable under user
|
|
0:01:19
|
and they also have to have a remote destination profile
|
|
0:01:23
|
which links their user to the remote destinations
|
|
0:01:26
|
and they have to have a remote destination that
|
|
0:01:28
|
they can authenticate against in order to use this feature.
|
|
0:01:32
|
So we do have to or might as well
|
|
0:01:34
|
provision mobile connect
|
|
0:01:36
|
for actual working in order to have,
|
|
0:01:40
|
you know you could set up mobile connect and just
|
|
0:01:42
|
tell the remote destinations to not be enabled.
|
|
0:01:47
|
but you know, so that it would never extend calls outward
|
|
0:01:51
|
but you would at least to have them set up.
|
|
0:01:53
|
So set up CUCM do allow mobile connect
|
|
0:01:55
|
users to be able to dial into an IVR menu,
|
|
0:01:58
|
Interactive Voice Response
|
|
0:02:00
|
that will give them the ability to
|
|
0:02:01
|
enable or disable mobile connect
|
|
0:02:04
|
for each of the remote phones
|
|
0:02:07
|
activate the Mobile Voice Access IVR menu when
|
|
0:02:10
|
PSTN callers ring the DID of
|
|
0:02:14
|
and they do not have to actually call +1
|
|
0:02:17
|
but it is @ the +1 or the US,
|
|
0:02:21
|
US, Canada, Austin Branch1 site of
|
|
0:02:25
|
5126022500 at the Branch1 site and the reason we chose the Branch1 site
|
|
0:02:31
|
is that it is already configured as an H323 gateway.
|
|
0:02:34
|
I believe that we mentioned earlier in the concepts slide introduction
|
|
0:02:40
|
that this has to be an H323 gateway
|
|
0:02:45
|
in 7.0.1 after 7.1 or 7.2, I cannot remember which
|
|
0:02:52
|
and a later version of IOS. I believe it was IOS12424T.
|
|
0:02:58
|
We are using 12422T as in the lab.
|
|
0:03:01
|
Then it could be a SIP gateway or SIP trunk
|
|
0:03:05
|
as well. So the IOs rather could be SIP but
|
|
0:03:09
|
and I have tested this in 12424T IOS and CUCM701
|
|
0:03:15
|
this does not work with SIP and only works with H323.
|
|
0:03:18
|
So that is the reason we chose this site.
|
|
0:03:20
|
Now, incidentally there is another way to do it so that
|
|
0:03:23
|
all gateways whether they are MGCP
|
|
0:03:27
|
or SIP or whatever, can all call in and
|
|
0:03:33
|
also it should be noted that really every site could have their
|
|
0:03:36
|
own specific DID although we do not have a task for that
|
|
0:03:39
|
in this particular module,
|
|
0:03:43
|
There can only be one enterprise DID of Mobile Voice Access
|
|
0:03:48
|
but you could have a separate DID that brings into a local gateway at each site
|
|
0:03:54
|
so that you have users from you know,
|
|
0:03:57
|
thousand different sites call into their local gateway
|
|
0:04:00
|
wherever they are around the world
|
|
0:04:02
|
and that just essentially does a translation
|
|
0:04:04
|
that you should do actually
|
|
0:04:07
|
the translation and have to do the translation, I should note
|
|
0:04:10
|
on the IOS router, not in CUCM translation pattern.
|
|
0:04:14
|
But you can do a translation on the IOS router
|
|
0:04:17
|
that forwards the call into a specific
|
|
0:04:24
|
DID that you know, forwards it to the single enterprise
|
|
0:04:30
|
Mobile Voice Access DID that you will see us configure in just a little bit.
|
|
0:04:33
|
So you can support this in a global fashion
|
|
0:04:36
|
even though CUCM only supports one DN
|
|
0:04:38
|
for its Mobile Voice Access number.
|
|
0:04:43
|
So we are also told to change Hurley’s normal
|
|
0:04:46
|
Corporate Head Quarter Phone 2 Class of Restriction
|
|
0:04:49
|
and releases the shared line for both
|
|
0:04:52
|
line 2 and the remote destination profiles.
|
|
0:04:55
|
So whenever we change it on 1, it will change on the other.
|
|
0:04:59
|
Change this Class of Restriction to allow him to dial International numbers
|
|
0:05:04
|
then ensure that if either user dials
|
|
0:05:06
|
into a Mobile Voice Access and presses 1
|
|
0:05:10
|
to go to make a call back out of the system,
|
|
0:05:13
|
but they are only allowed to make calls according to their proper
|
|
0:05:17
|
lass of Restrictions so we are changing Hurley’s so he can make
|
|
0:05:20
|
calls back out through International
|
|
0:05:23
|
and we are changing, or actually not changing Sawyer,
|
|
0:05:28
|
his branch to Phone 2 at all
|
|
0:05:30
|
and he currently cannot call
|
|
0:05:32
|
in the previous module, he could not call local long-distance
|
|
0:05:36
|
National or International
|
|
0:05:40
|
before this module began in the start of configs, I actually allowed
|
|
0:05:43
|
him to be able to call local so that he could test that
|
|
0:05:46
|
but he is not allowed to call National numbers or International.
|
|
0:05:50
|
So, we will see if we can make this work properly.
|
|
0:05:55
|
So Hurley should be able to dial internal DN's
|
|
0:05:57
|
as well as while we are explaining everything I just mentioned.
|
|
0:06:01
|
Hurley should basically be able to dial everywhere.
|
|
0:06:03
|
Sawyer, should only be able to dial internal as well as local
|
|
0:06:06
|
but getting an error if he tries to dial National or International
|
|
0:06:11
|
from his remote phone in through Mobile Voice Access
|
|
0:06:15
|
just as he would if he was on his desk phone
|
|
0:06:18
|
and then we're told to test the call to make sure that in fact, he cannot do so.
|
|
0:06:22
|
We were also told to ensure that when either user places
|
|
0:06:25
|
either user places a call back out of the system,
|
|
0:06:29
|
that the called party PSTN phones
|
|
0:06:31
|
still shows their proper calling number display
|
|
0:06:34
|
just as if there were making the call from their desk phone.
|
|
0:06:38
|
So we will see if there is anything additional that we need to do
|
|
0:06:42
|
to get back to work. Ok, so now
|
|
0:06:49
|
Let's start with the first bit
|
|
0:06:51
|
Let us actually start with changing Hurley’s Class of Restriction.
|
|
0:06:54
|
Let us go, take a look on CUCM
|
|
0:07:00
|
by his phone
|
|
0:07:06
|
Corporate Headquarter Phone 2
|
|
0:07:08
|
he device as the Calling Search Space of dialled device US-PSTN which can call
|
|
0:07:13
|
all USTN-PSTN patterns.
|
|
0:07:17
|
The line 1002 has CSS-BLOCK-LINE-US-PSTN Restricted
|
|
0:07:25
|
So, we are going to just change that to Unrestricted.
|
|
0:07:29
|
and take a look at the Calling Search Space, actually, let us just go ahead and save this,
|
|
0:07:40
|
reset, already doing the restart of that phone since we saved it.
|
|
0:07:47
|
So, let us take a look at this unrestricted
|
|
0:07:51
|
Calling Search Space
|
|
0:07:55
|
CSS contains block, limit but we get out, output
|
|
0:08:00
|
So we're blocking US-PSTN Unrestricted
|
|
0:08:04
|
I would assume it contains, only partition Internal DNs
|
|
0:08:09
|
and partition Internal DNs does not have any block patterns.
|
|
0:08:13
|
So, essentially, this is unrestricted access
|
|
0:08:15
|
So, why do we do this? Well, back in module 9, we said that
|
|
0:08:19
|
if we did not configure an actual CSS on a particular line
|
|
0:08:23
|
and another administrator comes and tries to modify
|
|
0:08:29
|
the system name, I take a look and say, “Wait a minute, there is no CSS on the line.
|
|
0:08:33
|
Someone forgot to configure something.”
|
|
0:08:36
|
But ultimately, whether we would have
|
|
0:08:38
|
put that unrestricted on, which basically restricts nothing,
|
|
0:08:42
|
or left it blank,
|
|
0:08:44
|
we would meet with the same result which is that he can now dial anywhere.
|
|
0:08:47
|
So, let us just verify its functionality.
|
|
0:08:56
|
need to do Device Search Control again.
|
|
0:09:07
|
So we'll have him try to dial the Nationally 1,
|
|
0:09:25
|
So we'll dial 91512602
|
|
0:09:39
|
We'll off hook and do this again.
|
|
0:09:52
|
Ok, 91512602,
|
|
0:09:58
|
let's call into
|
|
0:10:01
|
6, I waited too long, inter-digit time out. 915126026222.
|
|
0:10:10
|
he is able to dial long distance or national.
|
|
0:10:14
|
And let us try an international call, 9011312070373#
|
|
0:10:32
|
and he is able to dial the International Amsterdam line as well.
|
|
0:10:39
|
Even if changed to 703, the reason was we have tailed and hopped off
|
|
0:10:44
|
nd that reflects on the called display here.
|
|
0:10:51
|
So, he is allowed to dial International, let us try James Ford phone.
|
|
0:10:55
|
So let's go off hook.
|
|
0:10:58
|
Dial, first let us just make sure he can get out to the PSTN with 112,
|
|
0:11:04
|
he certainly can dial emergency and he dialled local,
|
|
0:11:11
|
07037333. He can dial locally.
|
|
0:11:20
|
dial nationally 001070
|
|
0:11:28
|
that number I believe
|
|
0:11:32
|
mapped anywhere, nope. He just goes immediately to
|
|
0:11:36
|
but don't get an error tone or anything else, it's just the call immediately drops.
|
|
0:11:41
|
Let us try International, 000120 and the call is already dropped.
|
|
0:11:50
|
So, why did the call drop? Well, because this phone, I believe, happens to be
|
|
0:12:11
|
this happens to be a SIP load phone and so enunciator can't play to this phone
|
|
0:12:18
|
because enunciator only plays to skinny devices as we've learned in previous modules.
|
|
0:12:24
|
So, James cannot dial nationally or internationally.
|
|
0:12:29
|
Sawyer cannot, Hugo or Hurley can dial everywhere he wants to.
|
|
0:12:34
|
James should take effect for their remote destination shared line.
|
|
0:12:40
|
So, we are taking care of this.
|
|
0:12:45
|
Now, we need to set up actual mobile connect.
|
|
0:12:49
|
I am sorry not mobile connect but Mobile Voice Access.
|
|
0:12:52
|
So, first of all, back in our CUCM, we need to go back to system’s service parameters.
|
|
0:13:04
|
We are all the way to the bottom.
|
|
0:13:08
|
Since ever so slightly up to the
|
|
0:13:11
|
third section from the bottom, System Mobility
|
|
0:13:14
|
and we need to enable Mobile Voice Access.
|
|
0:13:20
|
Save this. And actually I should have put in the Mobile Voice Access Number
|
|
0:13:24
|
before I press Save. So, we will be coming right back down here.
|
|
0:13:30
|
Actually, let us take a look a few other screens before I
|
|
0:13:37
|
mention specifically which
|
|
0:13:39
|
number we should put in this field for Mobile Voice Access.
|
|
0:13:42
|
So, we've enabled it. Now, let us take a look at call routing,
|
|
0:13:47
|
mobility configuration and then media resources, mobile voice access.
|
|
0:13:52
|
and it might surprised you why is
|
|
0:13:55
|
Mobile Voice Access under media resources and mobility under call routing.
|
|
0:14:00
|
Well, let us take a look at mobility.
|
|
0:14:03
|
Mobility, there is the handoff number and partition.
|
|
0:14:06
|
and enterprise feature access and partition.
|
|
0:14:09
|
Now, we only need to enter something if we're going to press Save and we're not.
|
|
0:14:13
|
We do not care about this because the handoff number
|
|
0:14:17
|
is for dual mode phones, the Nokia, GSMs/WiFi phone,
|
|
0:14:23
|
and the enterprise speech or access we mentioned is the same thing
|
|
0:14:26
|
as Mobile Voice Access but without the IVR prompts
|
|
0:14:30
|
and is really used with the mobility advantage server
|
|
0:14:35
|
takes the place of Mobile Voice Access or
|
|
0:14:38
|
can be used in conjunction with but most of the time it would take the place of
|
|
0:14:45
|
and so we have a mobility advantage server and smart clients when there's no IVR.
|
|
0:14:50
|
We're not going to configure this and it really will not work
|
|
0:14:52
|
without the mobility advantage server.
|
|
0:14:56
|
Then, under media resources,
|
|
0:15:00
|
Mobile Voice Access and the reason it is under media resources
|
|
0:15:03
|
is because it actually plays media resources that plays prompts.
|
|
0:15:08
|
So, it takes media.
|
|
0:15:10
|
so we're gonna give a Mobile Voice Access number. Now, we were told
|
|
0:15:14
|
to use the DID of 512 or +15126022500.
|
|
0:15:23
|
So, the last four digits here being the four-digit DN
|
|
0:15:27
|
Now, depending on how the calls are coming in from the Branch1 gateway,
|
|
0:15:31
|
So let us take a look at that real briefly
|
|
0:15:35
|
calls are coming in and inbound call routing, we have significant digits for
|
|
0:15:41
|
and an inbound CSS
|
|
0:15:43
|
So, whatever DN we put there needs to be four digits
|
|
0:15:46
|
and in a partition able to be seen by this calling search space
|
|
0:15:49
|
just like any internal phone DN.
|
|
0:15:55
|
So, back to media resources, Mobile Voice Access
|
|
0:15:59
|
and we were told 2500 so, we will put in 2500 here
|
|
0:16:04
|
a partition, let's just put it in with all the rest of the phones internal DNs
|
|
0:16:09
|
nd let us assign the selected locale, the only one we have installed.
|
|
0:16:14
|
This will tell us what language of prompt files to play.
|
|
0:16:17
|
We would obviously have to install other locales
|
|
0:16:20
|
or CUCM to be able to play other languages.
|
|
0:16:26
|
We have multiple options there in the order that we wish for them to be used.
|
|
0:16:32
|
and so save, and was successful. If we come back here to mobility,
|
|
0:16:36
|
we have nothing configured just to show
|
|
0:16:38
|
and then come back to media resources Mobile Voice Access
|
|
0:16:42
|
and it is configured. This is the DN that we'll copy
|
|
0:16:45
|
and need to put here in service parameters for the mobile Voice Access Number.
|
|
0:16:56
|
If we were using the enterprise feature access,
|
|
0:16:59
|
we would put the enterprise feature access number here.
|
|
0:17:06
|
Save.
|
|
0:17:08
|
Other than ensuring that the actual service is running
|
|
0:17:13
|
on the publisher, let's just go and take a look at that real briefly,
|
|
0:17:16
|
activated and running
|
|
0:17:19
|
up here to serviceability,
|
|
0:17:28
|
We can do service activation but we have already
|
|
0:17:31
|
activated so let us go to feature services
|
|
0:17:34
|
for the publisher only, you will not see it under the subscriber
|
|
0:17:38
|
Now, we are getting into the place where everything up until now
|
|
0:17:41
|
has and will work with the pub or sub being online.
|
|
0:17:45
|
or any number of subscribers you could be home to for call processing engines.
|
|
0:17:50
|
But this particular IVR will not be played unless the publisher is running
|
|
0:17:56
|
and specifically the unified Mobile Voice Access Service is started on the publisher.
|
|
0:18:04
|
So it looks like it's good.
|
|
0:18:06
|
So, everything that we need on the CUCM server is done.
|
|
0:18:10
|
So, now we need to actually configure the Branch1 router.
|
|
0:18:16
|
In order to do that, we need to know what the URL of the
|
|
0:18:20
|
Voice XML or VXML application is
|
|
0:18:25
|
and this is going to be running on the CUCM publisher but we need to grab that.
|
|
0:18:29
|
Well, where can we grab it? The same place we can grab a lot of URLs
|
|
0:18:33
|
in the actual voice lab exam which is from the Unified CUCM SRND
|
|
0:18:41
|
So let's gover over to our bookmarks and let's go into contents
|
|
0:18:45
|
and down to not Device Mobility but Cisco Mobility Applications.
|
|
0:18:50
|
Let us scroll pass Mobile Connect
|
|
0:18:53
|
and go to Mobil Voice Access and Enterprise Feature Access.
|
|
0:18:59
|
We will collapse this so we can see this a little bit better.
|
|
0:19:02
|
So, here we are, this explains the functionality a little bit.
|
|
0:19:09
|
Let us just go back to our bookmarks
|
|
0:19:13
|
and looks specifically at not just go to configuring it.
|
|
0:19:21
|
Here we go, Mobile Voice Access IVR Voice XML Gateway URL
|
|
0:19:26
|
So, click specifically there and here is the URL we need.
|
|
0:19:30
|
Notice that it is the CUCM publisher IP.
|
|
0:19:33
|
So, we are going to copy this
|
|
0:19:37
|
and let us go over our Branch1 router.
|
|
0:19:41
|
We are going to go back on our Branch1 router and we need to create an application
|
|
0:19:52
|
service and we will call it MVA and the URL
|
|
0:19:58
|
We are going to paste but then we are going to back up.
|
|
0:20:01
|
Careful not to do anything with the port number 8080 here
|
|
0:20:04
|
and we are going to just erase
|
|
0:20:08
|
what is in this greater than/less than alligator symbols
|
|
0:20:11
|
and do 177.1.10.10 to replace it with the IP of our publisher.
|
|
0:20:18
|
And if we have term on which we do, as soon as we click this,
|
|
0:20:23
|
it is going to go out and load this VXML script
|
|
0:20:27
|
which has information on how
|
|
0:20:29
|
the service will interact back and forth over HTTP
|
|
0:20:33
|
via VXML with the publisher.
|
|
0:20:37
|
It is gonna load it in the running memory and we should see the results of this.
|
|
0:20:41
|
The HTTP read was successful
|
|
0:20:45
|
the URL, the file read was successful and we now have it on running memory
|
|
0:20:53
|
So, that was all we needed there.
|
|
0:21:00
|
You shall run Pipe to section application
|
|
0:21:02
|
and we see that application note that known to our router as MVA
|
|
0:21:07
|
or Mobile Voice Access. So, now we needed to configure an inbound dial-peer
|
|
0:21:12
|
that is specifically matching that DID.
|
|
0:21:14
|
Now, let us just see how calls come in to the router just to remind ourselves.
|
|
0:21:20
|
So, let us call in from, let us say, Hurley’s home to
|
|
0:21:25
|
15126022500.
|
|
0:21:35
|
So right now we meet with an error, the call comes in, the called number
|
|
0:21:40
|
as 10 digits. So, that is the DN we want to match.
|
|
0:21:44
|
So, let us do show
|
|
0:21:50
|
dial-peer voice some
|
|
0:21:53
|
and see the dial-peer tags we have so we do not want to overwrite anything.
|
|
0:21:58
|
Let us start with 200, let us create a dial-peer voice 200 pots.
|
|
0:22:07
|
The incoming called number is going to be explicitly
|
|
0:22:14
|
longest match exactly what is going to be caught coming in
|
|
0:22:19
|
and then we simply want to pass this off to service MVA.
|
|
0:22:25
|
So, that is done. Now, if we call back,
|
|
0:22:47
|
So when the call came in, we noted that it said enter our pin number.
|
|
0:22:51
|
It didn't say enter our ID or remote destination number.
|
|
0:22:54
|
That is because we called in from a known number, Hurley’s home.
|
|
0:22:58
|
Let us call in from a non-known number.
|
|
0:23:13
|
There, it said enter our remote destination number.
|
|
0:23:16
|
Now, here is the problem with this,
|
|
0:23:18
|
because + even if you happened to have to have a + on a mobile phone,
|
|
0:23:22
|
not remote destination mobile phone but just any old mobile phone
|
|
0:23:26
|
you have to have a + maybe it is on 0 or *
|
|
0:23:29
|
asterisk maybe, you hold down a key. It is not a DTMF digit.
|
|
0:23:33
|
So, it is not going to be pathed.
|
|
0:23:34
|
So, we will never be able to enter our remote destination number.
|
|
0:23:38
|
You might say, “Wait a minute, what about the partial match?"
|
|
0:23:41
|
"the 10 digits?” Well, let us try that.
|
|
0:23:53
|
Alright, let us enter our remote destination number of 2065015555.
|
|
0:24:10
|
Not a recognized remote destination number, so the partial match
|
|
0:24:14
|
only applies to inbound ringing numbers
|
|
0:24:16
|
not to manually enter remote destinations.
|
|
0:24:20
|
Just to ensure that this would work if we change our remote destination,
|
|
0:24:28
|
let us change our remote destination to not include the +1.
|
|
0:24:32
|
Just temporarily, we are going to change it back
|
|
0:24:38
|
try that same inbound call.
|
|
0:24:51
|
Ok. 2065015555#
|
|
0:25:07
|
So, it did not recognize it, could have been my client, 20650155
|
|
0:25:22
|
and it hanged up the call. So, it still did not work properly.
|
|
0:25:27
|
Maybe I took too long to do it. Let us try it one more time.
|
|
0:25:50
|
So it still says that it is not a recognized remote destination number.
|
|
0:25:55
|
Alright, let us take a look at why that might be.
|
|
0:25:59
|
Here is part of the problem, actually let us do a different debug.
|
|
0:26:06
|
Undebug all.
|
|
0:26:10
|
Do show, actually show run type to begin with
|
|
0:26:13
|
dial-peer so that we can see all of our dial peers.
|
|
0:26:18
|
We've an incoming call number dot for pots but we got a more specific one for that.
|
|
0:26:24
|
Dial-peers that we have that hand calls off to CUCM
|
|
0:26:29
|
are 101 and 102 are 101 and 102 for the sub and pub respectively
|
|
0:26:37
|
but notice their destination patterns –are 10 digits in link.
|
|
0:26:41
|
That is because calls coming in from
|
|
0:26:44
|
the PSTN are coming in with 10-digit call numbers all the time.
|
|
0:26:49
|
so all the rest of these are pots for outbounds
|
|
0:26:54
|
I keep going now, I got my dial-peer 200 pots for
|
|
0:26:57
|
inbound but hands calls off to service MVA.
|
|
0:27:01
|
Well, here is the only problem, the MVA VXML script
|
|
0:27:05
|
is interacting back and forth the HTTP with CUCM.
|
|
0:27:11
|
But CUCM is telling the Voice XML Gateway
|
|
0:27:17
|
that, “Hey, by the way, my DN is 2500."
|
|
0:27:26
|
So, when calls go to get handed off to me,
|
|
0:27:29
|
they need to ring the number of 2500.
|
|
0:27:34
|
we don't have the destination pattern of 2500
|
|
0:27:37
|
or 4 digits at all for that matter that point to session target
|
|
0:27:41
|
IPV4/H323
|
|
0:27:46
|
point to the CUCM pub or sub, we only have 10-digit destination patterns.
|
|
0:27:51
|
So, let us do a debug VOIP, dial-peer.
|
|
0:27:58
|
Just to straighten the point a little bit further to bring up my PSTN phone.
|
|
0:28:07
|
Either which one we choose, let us redial.
|
|
0:28:16
|
so that inbound call came in incoming peer or 200 at 2065015555#
|
|
0:28:36
|
How could be? Let us try it from
|
|
0:28:38
|
from another phone, it could be my client because sometimes I have problems with the
|
|
0:28:41
|
CIPC client running in fusion. Let us try another one.
|
|
0:28:44
|
Same exact phone
|
|
0:28:46
|
you can see it is line 1 going up hook and I am just using the physical phone.
|
|
0:28:50
|
So 512602622
|
|
0:29:10
|
So, if you heard that, I can do it again.
|
|
0:29:11
|
It did say enter your pin. Let us do it again really quick.
|
|
0:29:16
|
On line 1.
|
|
0:29:22
|
2065015555#
|
|
0:29:44
|
Probably better to make sure that my pin is line up.
|
|
0:29:47
|
Let us go to user management and user.
|
|
0:30:03
|
Press, make sure this pin is set to 12345
|
|
0:30:07
|
or whatever I want it to be, 12345 is what I am going to use.
|
|
0:30:15
|
Back and look for Sawyer, James Ford, his pin, done.
|
|
0:30:29
|
Let's try this again.
|
|
0:30:58
|
So, now it was just DTMF that was not working
|
|
0:31:00
|
properly on the CIPC probably because of high CPU utilization.
|
|
0:31:06
|
But anyhow, we are properly matching through remote destination.
|
|
0:31:11
|
So, again, let us put in +1,
|
|
0:31:16
|
take it back to the way we had it.
|
|
0:31:27
|
+1
|
|
0:31:32
|
back to just view it here, good and we will try to key that inmanually again.
|
|
0:31:56
|
Again, even if the DTMF was
|
|
0:31:59
|
not working properly from my soft client,
|
|
0:32:01
|
even on the hard phone, if we have +
|
|
0:32:05
|
as part of our remote destination,
|
|
0:32:07
|
one of the downside is that we will not be able to configure
|
|
0:32:13
|
we won't be able to configure unified
|
|
0:32:17
|
mobile voice access to match hand entered ID.
|
|
0:32:23
|
Now, there are some ways we could get around that with
|
|
0:32:25
|
call routing by application dial rules, we could have it at a +.
|
|
0:32:31
|
But right now, we are just going to keep it as is
|
|
0:32:33
|
and we are basically going to say that for right now, if we want to use +,
|
|
0:32:37
|
maybe we will demo that a little later
|
|
0:32:38
|
we have to call in from one of the actual
|
|
0:32:42
|
mobile or home or one of our remote destination numbers.
|
|
0:32:46
|
So, again, I will try to call in from let us say Sawyer’s mobile.
|
|
0:32:49
|
You can see line 6 go off hook here.
|
|
0:32:58
|
You should be able to.
|
|
0:33:08
|
For whatever reason, Sawyer’s mobile is not showing up
|
|
0:33:12
|
but anyhow I will dial in.
|
|
0:33:32
|
So noticed that when we call in, we only
|
|
0:33:36
|
heard after we entered our pin and authenticate it,
|
|
0:33:38
|
we only heard to turn on or to turn on press 2 or 3.
|
|
0:33:43
|
We did not hear “to make a call, press 1.”
|
|
0:33:47
|
So, why did not we hear that?
|
|
0:33:49
|
Well, first of all, let us just deal with the turning on and off
|
|
0:33:52
|
mobile connects since that was the first bullet
|
|
0:33:54
|
and then we will deal with why did not we hear the ability to call back out
|
|
0:33:57
|
So first of all let us call in from let us say
|
|
0:34:01
|
Hurley because he has two mobile connect
|
|
0:34:05
|
remote destinations and we will just take a look at these really briefly.
|
|
0:34:09
|
Actually let me go out on Hurley’s home and mobile
|
|
0:34:18
|
and we see that Hurley’s home has enabled mobile connect
|
|
0:34:22
|
checked and Hurley’s mobile has enabled mobile connect checked.
|
|
0:34:26
|
So, we are going to dial in from his, let us say his mobile phone.
|
|
0:34:39
|
So we are authenticating now, 12345#
|
|
0:34:49
|
Off by pressing 3
|
|
0:35:01
|
Now, here is the problem, we cannot enter the remote destination that we want to turn off.
|
|
0:35:05
|
We could do this however, let me be back up.
|
|
0:35:12
|
I think I actually have to call back in again so I will try to call back in again
|
|
0:35:39
|
So all I did was
|
|
0:35:41
|
dial in, enter my pin and #, press 3 to turn off
|
|
0:35:45
|
and then press 2 to turn off for all remote destinations
|
|
0:35:48
|
So, let us just do a refresh on this page.
|
|
0:35:52
|
Mobile connect is off for Hurley’s mobile.
|
|
0:35:55
|
Mobile connect if I do a refresh on Hurley’s home,
|
|
0:35:58
|
is off for Hurley's home.
|
|
0:36:01
|
but Sawyer’s mobile is of course still on because it is not tied to that user.
|
|
0:36:07
|
So, I turned it off for all remote destinations, I'm gonna dial back in.
|
|
0:36:16
|
Authenticate.
|
|
0:36:21
|
Press 2 to turn on.
|
|
0:36:25
|
and I press that 2
|
|
0:36:30
|
So, I pressed 2 to turn it on for all remote destinations
|
|
0:36:33
|
and again if I do a refresh, back on
|
|
0:36:38
|
and turned it on, refresh on home, it is back on here as well.
|
|
0:36:42
|
So, that is a nice feature
|
|
0:36:45
|
however, again, with +, we would not be able to turn it on
|
|
0:36:49
|
for an individual or turn it off for individual remote destination.
|
|
0:36:53
|
So, now back to our tasks,
|
|
0:37:01
|
we've activated the mobile voice response
|
|
0:37:04
|
and given each the ability to enable or disable
|
|
0:37:07
|
their Mobile Connect from each of their phones.
|
|
0:37:10
|
We have changed Hurley’s Class of Restriction
|
|
0:37:13
|
Now, we need to ensure that if they will dial in
|
|
0:37:15
|
and they press 1 to go to make a call
|
|
0:37:18
|
that they are only allowed to make a call to their existing core.
|
|
0:37:20
|
Well, maybe we just did not hear the option for 1,
|
|
0:37:23
|
kind of like security. Let us try it.
|
|
0:37:25
|
Let us dial in and press 1
|
|
0:37:28
|
to make another call back out of the system.
|
|
0:37:33
|
We are going to authenticate here.
|
|
0:37:37
|
I am just going to and press 1 to dial.
|
|
0:37:44
|
There, press 1 and it says it is an invalid key, I am not able to
|
|
0:37:49
|
press 1 to make a call. Well, the reason for this
|
|
0:37:54
|
is quite simply under N user.
|
|
0:37:58
|
for each of the users
|
|
0:38:01
|
Remember when he had done enable mobility
|
|
0:38:04
|
and given a primary device,
|
|
0:38:06
|
we did not enable Mobile Voice Access.
|
|
0:38:08
|
So, let's do that.
|
|
0:38:12
|
That does not mean that they cannot call into the IVR and use
|
|
0:38:16
|
Mobile Voice Access IVR
|
|
0:38:18
|
to enable and disable Mobile Connect
|
|
0:38:21
|
It just means that they are not allowed to do the
|
|
0:38:23
|
Mobile Voice Access feature of
|
|
0:38:25
|
pressing 1 to make a call back out.
|
|
0:38:28
|
Let us go back up, look up Hurley.
|
|
0:38:36
|
Activated for him as well.
|
|
0:38:40
|
Now, we call back in, we should hear 1
|
|
0:38:46
|
as an option to make the call.
|
|
0:38:52
|
I'm gonna go ahead and authenticate, don't need to wait.
|
|
0:38:57
|
So, now we here to make a call and we are going to try that.
|
|
0:39:05
|
So, let us call 911.
|
|
0:39:11
|
First of all, the call just hung up.
|
|
0:39:15
|
Let's see what if we try dialling another number.
|
|
0:39:20
|
Actually, before we do this,
|
|
0:39:22
|
et us go back to Branch1 gateway
|
|
0:39:25
|
and let us clear off everything
|
|
0:39:28
|
and let us do the call in again so now
|
|
0:39:30
|
I'm gonna call into Mobile Voice Access from Hurley’s mobile.
|
|
0:39:38
|
And we see the call matching on the screen.
|
|
0:39:49
|
Pressing 12345, authenticating with #.
|
|
0:39:56
|
So now, I pressed 1
|
|
0:39:59
|
I'm gonna dial 911 again.
|
|
0:40:05
|
Now, let us take a look at what happened on screen
|
|
0:40:08
|
All of the sudden, first of all, we had the inbound call
|
|
0:40:12
|
matching incoming peer 200
|
|
0:40:14
|
nd it handed off to the Mobile Voice Access and we saw the connect.
|
|
0:40:19
|
Then, once I pressed 1 to make another call,
|
|
0:40:22
|
Mobile Voice Access actually called the DN of 2500
|
|
0:40:26
|
but there is no match. Ultimately no outgoing dial-peer is matched.
|
|
0:40:33
|
This is where we need to have another dial-peer.
|
|
0:40:36
|
Now, if we have already been doing all of our translations
|
|
0:40:39
|
from 10-digits DNs down to 4-digit DNs or called number
|
|
0:40:43
|
on the H323 gateway, though we would already have the two
|
|
0:40:46
|
dial-peers that matched. But here, we need to have
|
|
0:40:52
|
typically one more so we'll create a dial-peer
|
|
0:40:57
|
voice 201
|
|
0:41:00
|
and this is needs to be VOIP because it needs to send it off to the CUCM.
|
|
0:41:04
|
For destination pattern, it is going to be 2500.
|
|
0:41:09
|
Our session target will be IPV4
|
|
0:41:18
|
but with 177.1.10.10, the publisher.
|
|
0:41:21
|
We could have an alternate pointing to the subscriber
|
|
0:41:23
|
because it can take the call in there but again
|
|
0:41:27
|
it's only going to work if the publisher is up so we really don't
|
|
0:41:30
|
need to have any redundancy on this because
|
|
0:41:32
|
it really only works if the publisher is active.
|
|
0:41:36
|
If the publisher was running the Mobile Voice Access
|
|
0:41:41
|
but maybe in real life did not have any call processing
|
|
0:41:44
|
engine activities active so in another words
|
|
0:41:47
|
the CUCM service was not running on the publisher
|
|
0:41:50
|
but the Mobile Voice Access service was
|
|
0:41:53
|
Well, then our VXML script would have still pointed to the publisher
|
|
0:41:56
|
but these dial-peers would point to our
|
|
0:42:00
|
subscribers that we are registered with.
|
|
0:42:02
|
So we might have two or three, probably three servers
|
|
0:42:07
|
in a large environment here maybe four.
|
|
0:42:11
|
So session target, it needs to be H323 we mentioned.
|
|
0:42:14
|
Now, it could have been the Corporate Head Quarter Gateway we just have to actually have a
|
|
0:42:19
|
H323 dial-peer pointing back over
|
|
0:42:22
|
so that would work but then of course we have to set up an H323
|
|
0:42:25
|
gateway in CUCM as well, we already have one for Branch1
|
|
0:42:29
|
So we need DTMF relay because that is gonna be important
|
|
0:42:34
|
So DTMF relay H245 signal
|
|
0:42:37
|
we mentioned is better than alphanumeric because it carries
|
|
0:42:40
|
tone duration as well as the actual DTMF digit
|
|
0:42:45
|
alphanumeric only carries the digit but not the duration of the key press.
|
|
0:42:49
|
We are going to have
|
|
0:42:52
|
a voice class codec that we
|
|
0:42:55
|
hopefully already have configured. Let us do show run
|
|
0:42:57
|
type 2 section voice class codec.
|
|
0:43:04
|
Yup, we already have one configured
|
|
0:43:05
|
so let us add that, voice class codec1
|
|
0:43:12
|
and let us specifically say,
|
|
0:43:17
|
actually, that should probably be enough, do show run
|
|
0:43:20
|
type 2 begin with voice 200, so we are going to dial-peer
|
|
0:43:29
|
with little separation.
|
|
0:43:31
|
Again, with voice 200, begin with the dial-peer that we created for MVA
|
|
0:43:35
|
so here is going to be the inbound
|
|
0:43:44
|
here is going to be the inbound dial-peer
|
|
0:43:47
|
matching the full DNs and then now we got one that is H323
|
|
0:43:52
|
pointing back to publisher with voice class codec1
|
|
0:43:56
|
and DTMF relay
|
|
0:43:58
|
and that should be enough to carry your call out.
|
|
0:44:01
|
Let's go ahead and write this configuration
|
|
0:44:04
|
and we are going to clear out our buffer
|
|
0:44:06
|
and now we will try to make the call back in
|
|
0:44:08
|
still with our debug VOIP dial-peer
|
|
0:44:11
|
nd see if what we are trying to do works
|
|
0:44:14
|
and by the way, 911, since I didn't have enough
|
|
0:44:18
|
and 112, the emergency services numbers,
|
|
0:44:20
|
since I did not have enough lines on here for this particular
|
|
0:44:23
|
well I do if we were using CIPC
|
|
0:44:25
|
assuming that you might be using the 7960
|
|
0:44:28
|
or 61 for your PSTN phone,
|
|
0:44:31
|
I did not configure anymore DNs. So it is overlaid
|
|
0:44:34
|
on Sawyer’s mobile. So if you see 911 ringing on this line, that's the reason
|
|
0:44:38
|
because it is overlaid here
|
|
0:44:40
|
not because it is actually ringing Sawyer’s
|
|
0:44:42
|
mobile and doing some strange translation.
|
|
0:44:44
|
Alright, so we will call from Hurley’s mobile
|
|
0:44:46
|
into the system and authenticate
|
|
0:44:53
|
We see the call coming in, incoming
|
|
0:44:56
|
dial-peer 200. We are going to authenticate.
|
|
0:45:04
|
We'll press 1
|
|
0:45:09
|
911#
|
|
0:45:22
|
so we heard the call actually
|
|
0:45:24
|
what we see the call
|
|
0:45:26
|
leave for 2500
|
|
0:45:28
|
It matches the outgoing dial-peer of 201.
|
|
0:45:32
|
We send the call out
|
|
0:45:34
|
but for whatever reason, that
|
|
0:45:35
|
user is not allowed to dial 911.
|
|
0:45:39
|
So we need to take a look and see
|
|
0:45:42
|
maybe why that is per se.
|
|
0:45:47
|
One of the things is that we really probably
|
|
0:45:49
|
don't want that user dialling 911 anyhow
|
|
0:45:53
|
so one of the ways that we can prevent that
|
|
0:45:56
|
is if when we click on service parameters
|
|
0:46:02
|
We're all the way to the bottom
|
|
0:46:07
|
and we can actually do remote access blocked numbers
|
|
0:46:11
|
such as 911 and things of that nature to
|
|
0:46:14
|
ensure that users cannot call.
|
|
0:46:16
|
Before we do that, let us try some other,
|
|
0:46:20
|
actually, take a look here.
|
|
0:46:23
|
First to dial our remote destination profile
|
|
0:46:26
|
and let us remember
|
|
0:46:29
|
that we talked about earlier
|
|
0:46:31
|
on either of our RDPs
|
|
0:46:33
|
that are calling search spaces used
|
|
0:46:35
|
when calls are coming in from a particular entity
|
|
0:46:39
|
and Mobile Voice Access, we mentioned earlier
|
|
0:46:42
|
is where calls will be coming into CUCM
|
|
0:46:44
|
from the remote destination profile
|
|
0:46:47
|
when they are rerouting mobile connect
|
|
0:46:50
|
they use the rerouting calling search space.
|
|
0:46:52
|
When they are coming in to make
|
|
0:46:54
|
another call, so use Mobile Voice Access to call into that
|
|
0:46:58
|
IVR and then to make a call back out,
|
|
0:47:00
|
that is where the Calling Search Space comes into play.
|
|
0:47:03
|
So currently, it is set to none
|
|
0:47:05
|
so obviously that it not going to allow much, right?
|
|
0:47:09
|
So let us set it to dial device US for Hurley's phone.
|
|
0:47:14
|
Let us try it now.
|
|
0:47:23
|
Try the call again
|
|
0:47:28
|
Authenticate. Press 1.
|
|
0:47:36
|
911.
|
|
0:47:43
|
Now, the call is going back out
|
|
0:47:45
|
and you can see it ringing on again Sawyer’s mobile because
|
|
0:47:49
|
that is 911 overlaid there.
|
|
0:47:58
|
We see it going out from router 1
|
|
0:48:01
|
and what number did it come from,
|
|
0:48:02
|
the calling party number of 2065011002
|
|
0:48:09
|
which was Bill Hurley’s desk phone.
|
|
0:48:14
|
So it is ringing out as a proper number
|
|
0:48:20
|
proper calling number
|
|
0:48:22
|
It was ringing 911. Why did it go out Corporate Head Quarter Gateway?
|
|
0:48:26
|
I mean I realized that Hurley is a Corporate Head Quarter user phone 2
|
|
0:48:33
|
but remember what we said earlier single number reach was gonna try
|
|
0:48:37
|
the calling party not the rerouting calling party.
|
|
0:48:41
|
Wait a minute, rerouting was for mobile connect.
|
|
0:48:44
|
This is Mobile Voice Access using calling search space
|
|
0:48:49
|
and so this actually is the calling party, this is
|
|
0:48:54
|
the ANI or the calling party so it uses
|
|
0:48:58
|
the calling party, the remote destination profiles device pool
|
|
0:49:03
|
and calling search space. So since it uses its device pool of Corporate Headquarters,
|
|
0:49:08
|
it uses that to go back and look for a local route
|
|
0:49:10
|
group which is Corporate Headquarters
|
|
0:49:12
|
so calls coming from this phone will primarily go out the local gateway
|
|
0:49:19
|
And that also ensures that dialling is kept the same.
|
|
0:49:26
|
Now, that we got the call to go back out, let's block
|
|
0:49:28
|
911. Actually, before we do that, let's try
|
|
0:49:32
|
another call and let us clear out the buffer.
|
|
0:49:36
|
of Corporate Head Quarter and Branch1 gateway
|
|
0:49:41
|
and let us try another call
|
|
0:49:45
|
from Hurley’s mobile to let us say the Amsterdam international number.
|
|
0:49:53
|
Let's try this.
|
|
0:50:02
|
We are authenticating then press to make a call.
|
|
0:50:09
|
We are gonna dial international but we have to dial a 9
|
|
0:50:12
|
first just like we would from our desk phone.
|
|
0:50:14
|
So 90112031,
|
|
0:50:22
|
Sorry I dialled that wrong. Let's start over.
|
|
0:50:27
|
Authenticate, press 1.
|
|
0:50:34
|
That should be 901131207037333#
|
|
0:50:50
|
We see that the call is coming forwarded
|
|
0:50:56
|
and it is going out router 3 from the proper calling number
|
|
0:51:03
|
at a local call because of tail and hop off, so that's great
|
|
0:51:14
|
So the call is ringing properly. Let us block 911 so that that does not work.
|
|
0:51:19
|
Turn this off, let us go ahead and
|
|
0:51:21
|
undebug all and then debug ISTNQ931 on this branch 1
|
|
0:51:30
|
Dial-peers are matching now. Let us go back to system service parameters
|
|
0:51:45
|
and we are now going to block the remote access number of 911 and 112
|
|
0:51:51
|
because we don't want users dialing
|
|
0:51:53
|
those numbers from Mobile Voice Access. That would obviously be bad.
|
|
0:51:58
|
not that they are probably intentionally doit but maybe accidentally.
|
|
0:52:05
|
specially if urgent priority has checked on 911
|
|
0:52:08
|
they press 91 for long distance and then they accidentally put in another one
|
|
0:52:13
|
and then they put in all the rest of their digits and they press #
|
|
0:52:18
|
it is still going to match against the patterns that are in their
|
|
0:52:22
|
calling search space and subsequent partition and
|
|
0:52:28
|
he possibility is there that
|
|
0:52:33
|
not the possibility, it would match 911 if urgent priority was checked.
|
|
0:52:37
|
If it was not checked, then it would not necessarily.
|
|
0:52:44
|
Now let's try this call again.
|
|
0:53:02
|
Let me try this again
|
|
0:53:19
|
Now, the call came in on Branch1
|
|
0:53:24
|
but it could not complete because we have blocked that number.
|
|
0:53:27
|
Let us just make sure the rest of the numbers still work properly.
|
|
0:53:49
|
91512026222#
|
|
0:54:07
|
It is ringing the PSTN and so everything works properly there.
|
|
0:54:14
|
o that works. Let's try calling from Sawyer’s phone.
|
|
0:54:24
|
He's gonna call into the mobile connect.
|
|
0:54:38
|
Let's try 112
|
|
0:54:42
|
So the system blocked that. Let us try another call into MVA
|
|
0:54:49
|
So this is from Sawyer’s
|
|
0:54:53
|
from Sawyer’s mobile, we are going to try a local call
|
|
0:54:57
|
So 0 for second redial tone and then 70373333.
|
|
0:55:09
|
o it is not routing. Why is that? Well, if we remember
|
|
0:55:19
|
on our remote destination profile,
|
|
0:55:23
|
We gave Hurley a CSS but not Sawyer. Actually, let us go back
|
|
0:55:30
|
to our service parameters real briefly because there's something we want to look at here
|
|
0:55:57
|
This should not actually be currently using
|
|
0:55:59
|
their calling search space. One of the other things I wanted to point out was
|
|
0:56:02
|
inbound calling search space for remote destination.
|
|
0:56:06
|
By default, it set to use the trunk or gateways inbound calling search space.
|
|
0:56:11
|
That is what it is currently set to but I think it could be the problem that I was
|
|
0:56:15
|
describing earlier where I save they did not properly update the database
|
|
0:56:19
|
So I am going to change this and then I am going to change it right back
|
|
0:56:26
|
but I think it is showing one thing but what's
|
|
0:56:31
|
actually functioning is quite a different thing, thing that I
|
|
0:56:37
|
explained earlier. Now, I'm gonna change it back to the default
|
|
0:56:40
|
and then I'll explain what this does, if this works,
|
|
0:56:53
|
Go back down once loading is complete.
|
|
0:56:58
|
Your trunk or inbound calling search space, Ok. So now let us try calling
|
|
0:57:03
|
in from Sawyer’s mobile.
|
|
0:57:15
|
We're pressing 1
|
|
0:57:18
|
we'll dial 0 for a second redial tone and then local.
|
|
0:57:28
|
it is still not routing that call so let us go set
|
|
0:57:35
|
Sawyer’s remote destination profile.
|
|
0:57:42
|
Found calling search space to dialled device Netherlands PSTN.
|
|
0:57:50
|
update was successful and now we will try that call again
|
|
0:57:55
|
ooking at the branch gateway for the outbound call. So Sawyer’s mobile again.
|
|
0:58:13
|
Now, the call is ringing out as a local call properly.
|
|
0:58:18
|
Let us try calling international for Sawyer.
|
|
0:58:32
|
So I'm gonna do 000012065015111
|
|
0:58:45
|
"The president’s use is not authorized for your line."
|
|
0:58:52
|
Now, going back to system service parameters,
|
|
0:58:58
|
what I wanted to show
|
|
0:59:00
|
was that and it seems like maybe there was a bug in this version but by default,
|
|
0:59:06
|
the inbound calling search space for remote destination usage
|
|
0:59:11
|
for Mobile Voice Access is trunk or gateway,
|
|
0:59:15
|
which means that if I had opened
|
|
0:59:18
|
other window, the gateway that the call comes in on which is in this case always Branch1,
|
|
0:59:26
|
the inbound calling search space was device US-PSTN.
|
|
0:59:31
|
Maybe since I dialled 0, then it would not have worked properly but
|
|
0:59:38
|
it looks like it did acknowledge 0
|
|
0:59:43
|
and the reason that I'm saying this because I have the US-PSTN
|
|
0:59:45
|
which does not match Netherlands
|
|
0:59:47
|
translation PSTN patterns and partitions
|
|
0:59:52
|
but I was able to dial 112 which is only a match by Netherlands
|
|
0:59:57
|
device CSS in partitions. I was able to dial 070373333, the local number
|
|
1:00:06
|
so it obviously was using the line and device
|
|
1:00:10
|
which is what we can change this to so in the way that this works
|
|
1:00:15
|
so that we actually have the ability to have separate
|
|
1:00:18
|
Class of Restrictions from our desktop.
|
|
1:00:21
|
Our desktop might have let's say,
|
|
1:00:25
|
you know possible separate restrictions
|
|
1:00:28
|
but then also possibly separate gateways that we want to originate calls from
|
|
1:00:34
|
because remember the device points to the “Allow”
|
|
1:00:38
|
which typically indicates the
|
|
1:00:43
|
actual outbound gateway and the line typically deals with the
|
|
1:00:50
|
blockage so what it is the Class of Restrictions, what are we not allow to dial.
|
|
1:00:55
|
Again going back to module 9, if you need a refresher on that, so
|
|
1:01:00
|
here, the device is the remote destination profile
|
|
1:01:04
|
and the line calling search space concatenated
|
|
1:01:07
|
is the shared line. So the line would not change between phone
|
|
1:01:10
|
and desk phone and remote destination
|
|
1:01:14
|
because it is shared but the device,
|
|
1:01:17
|
the remote destination profile would be used rather than the desk phone.
|
|
1:01:20
|
This is what we normally need to change it to
|
|
1:01:23
|
in order to get the results that we are experiencing right now but for whatever reason,
|
|
1:01:27
|
it is working with the default of trunk or gateway
|
|
1:01:32
|
but it is actually using remote destination profile and I am just gonna ahead
|
|
1:01:36
|
and just in case other
|
|
1:01:42
|
tabbed window was causing any problems, you're going to reload this and change it to
|
|
1:01:48
|
remote destination profile plus line calling search space and save it
|
|
1:01:52
|
and it should still continue to work. It looks like it is a bug that it's
|
|
1:01:57
|
still working when trunk or gateway because it really should allow us to dial
|
|
1:02:04
|
Netherlands type patterns and if it was using trunk or gateway,
|
|
1:02:10
|
even if we could not dial Netherlands type patterns,
|
|
1:02:12
|
we would be able to dial internationally using a US dial scheme 9011
|
|
1:02:18
|
but in fact, it looks to be a bug but it's
|
|
1:02:21
|
still using RDP end line calling search space.
|
|
1:02:25
|
Just in case the bug is not present in your real lab
|
|
1:02:29
|
version of CUCM which
|
|
1:02:32
|
probably will be unless it is my browser that is causing the issue
|
|
1:02:36
|
then you would need to change this and that is what we are
|
|
1:02:38
|
ultimately giving to. You would need to change it from the default
|
|
1:02:41
|
to remote destination profile.
|
|
1:02:44
|
So let us try this again
|
|
1:02:49
|
we will make the call in from Sawyer’s mobile.
|
|
1:03:00
|
We are going to dial local first.
|
|
1:03:07
|
to prove that it is still working, you got that.
|
|
1:03:11
|
Now, we will try to make a national
|
|
1:03:14
|
that said user busy here and that reason is because it's
|
|
1:03:21
|
from the same phone.
|
|
1:03:25
|
Now, let us try to call
|
|
1:03:32
|
Now, let us try to call a national number from Sawyer’s mobile dialing in
|
|
1:03:57
|
so, we got the president’s use is not authorized. That is because it is matching
|
|
1:04:00
|
an explicit block pattern that is in a partition
|
|
1:04:04
|
feasible to the CSS
|
|
1:04:06
|
dial device Netherland block restricted
|
|
1:04:10
|
for line, not dial device but dial line
|
|
1:04:14
|
restricted and that matches a partition that has a
|
|
1:04:18
|
translation or PSTN pattern. Let us show it here really briefly.
|
|
1:04:31
|
Those that start with 0
|
|
1:04:33
|
We are dialing 00, so 0 for outside dial tone
|
|
1:04:37
|
and then 0 for national peers restricted coming in here
|
|
1:04:42
|
It sets a block with president’s level exceeded so that is why we're hearing that feedback
|
|
1:04:49
|
ame thing for international
|
|
1:04:52
|
from Sawyer’s line but now let us try to dial
|
|
1:04:55
|
international from Hurley’s mobile or home.
|
|
1:05:19
|
and the call is working properly.
|
|
1:05:22
|
So we now have both of them able to dial in.
|
|
1:05:29
|
Hurley is able to dial internal,
|
|
1:05:32
|
local, we have not really tried internal but we could try that real quick
|
|
1:05:35
|
Why not let's that real quick.
|
|
1:05:38
|
Let's actually bring up other phones on the screen so we can see them as well.
|
|
1:05:43
|
Now, let us dial from Hurley’s home this time. Actually, let us dial from Sawyer’s mobile to
|
|
1:05:47
|
prove that he still can dial internal as well.
|
|
1:05:55
|
authenticate and press 1 to dial
|
|
1:06:01
|
And let's dial Hugo Reyes Hurley from Sawyer’s mobile.
|
|
1:06:07
|
So just dialled 1002#
|
|
1:06:16
|
and we see it coming from 3002.
|
|
1:06:20
|
The only thing is we do not see calling name display.
|
|
1:06:26
|
Go check out our remote destinations
|
|
1:06:31
|
pool or really our remote destination profile,
|
|
1:06:42
|
our line, the color ID number,
|
|
1:06:58
|
and probably do not want to show the dialled number on forwarded.
|
|
1:07:52
|
Registered, tell you to search again and control.
|
|
1:08:08
|
Dialing off the PSTN again first.
|
|
1:08:28
|
We're still not seeing the name. I have to check in to that but we are seeing the number.
|
|
1:08:34
|
and we are seeing it coming from
|
|
1:08:37
|
3002 and we were dialling an internal DN
|
|
1:08:40
|
So Hurley can dial internal DN
|
|
1:08:52
|
We'll try dialing
|
|
1:08:54
|
Eloise at 2001, so we will just do 2001#
|
|
1:09:04
|
again it does show 1002
|
|
1:09:08
|
for whatever reason it is not showing the name
|
|
1:09:10
|
and it is not showing it to the PSTN either, I'm gonna search for the bugs
|
|
1:09:13
|
but everything is configured correctly and it should be showing the names
|
|
1:09:18
|
bug just like the system service parameter by default
|
|
1:09:25
|
So we have met all the requirements.
|
|
1:09:30
|
They can dial in, Class of Restriction works.
|
