|
0:00:14
|
So taking a look at the integration of Unity Express
|
|
0:00:19
|
We need to configure the service engine interface
|
|
0:00:22
|
in IOS, so Unity Express regardless of whether it is
|
|
0:00:27
|
in our labs, in our racks, we actually have the AIM
|
|
0:00:31
|
-queue module AIM-CUE, that´s actually
|
|
0:00:36
|
directly connected to the motherboard of the ISR router.
|
|
0:00:40
|
In the real lab, they´re going to have the nm
|
|
0:00:42
|
e-CUE, so the enhanced network module for queue
|
|
0:00:48
|
so it´ll actually be a network module or service module.
|
|
0:00:51
|
One of the modules that actually physically plugs in
|
|
0:00:54
|
from the outside of the router, either way
|
|
0:01:00
|
its going to, when the router boots up and sees that
|
|
0:01:03
|
create a service engine interface. Now this is the IP
|
|
0:01:07
|
layer 3 based IP interface from the router site.
|
|
0:01:11
|
We used this one, to populate the router side
|
|
0:01:15
|
of the IP connection, so populate the IP address
|
|
0:01:19
|
as the router sees it, and then this is going to be basically
|
|
0:01:22
|
a point to point network,we also use this interface to tell
|
|
0:01:26
|
the Unity Express module what its IP address
|
|
0:01:31
|
and default gateway is. So here you see
|
|
0:01:35
|
interface service engine 00
|
|
0:01:37
|
and we could give it its own, you know slash
|
|
0:01:42
|
24 or more realistically probably a slash 30
|
|
0:01:46
|
network as point to point for IP addresses
|
|
0:01:49
|
one broadcast, one network and two useable IPs
|
|
0:01:52
|
one for each side, one for the router and one for
|
|
0:01:55
|
the network module side, but we really don´t even have
|
|
0:01:58
|
to do that, we can borrow an IP from another interface.
|
|
0:02:01
|
So here, we see that we´ve borrowed an IP
|
|
0:02:05
|
address from a loop back interface and this loop
|
|
0:02:08
|
back interface which happens to be loop back 1
|
|
0:02:11
|
has an IP address. Now it can´t be a slash 32, that is
|
|
0:02:15
|
it can not have a subnet mask of 255 255 255.255
|
|
0:02:20
|
if it did, there´s only IP on that subnet and it is the IP that is
|
|
0:02:25
|
whatever the actual host IP is used there.
|
|
0:02:32
|
And the problem with that obviously is that if there´s one IP
|
|
0:02:35
|
and I borrow it for the service engine which is the router side
|
|
0:02:39
|
then there´s no second IP to give to the Unity Express module.
|
|
0:02:44
|
So this has to be at least a .252 which is a slash 30
|
|
0:02:49
|
or in this case in what´s easiest because this isn´t
|
|
0:02:53
|
the route switch exam is a slash 24 or a 255
|
|
0:02:56
|
255 255.0 subnet. So here that´s what this is,
|
|
0:03:02
|
we´re borrowing that IP address for the router
|
|
0:03:05
|
interface of service engine 00, now just because
|
|
0:03:08
|
we´re borrowing the IP, does not mean that
|
|
0:03:11
|
the router is going to route traffic for this network
|
|
0:03:15
|
out the service engine interface. In fact, by default
|
|
0:03:19
|
it´s going to route all that traffic out the loop back
|
|
0:03:23
|
interface which of course just loops right back into the router.
|
|
0:03:27
|
That´s because the IP address is assigned to loop back 0
|
|
0:03:31
|
it´s not assigned to interface service engine 00, it´s just borrowed
|
|
0:03:35
|
by service engine 00. So what were going to
|
|
0:03:38
|
do in order to route traffic to the one other IP that actually
|
|
0:03:42
|
belongs on the physical interface or virtual interface of service engine 00
|
|
0:03:47
|
which is the IP of the CUE module, which here we have defined
|
|
0:03:50
|
as service module IP address 177.1.250 so the same subnet
|
|
0:03:57
|
but a different IP .254, same subnet mask
|
|
0:04:00
|
The way we´re going to have to do that, is we´re going to have to
|
|
0:04:04
|
create a static host router globally in IOS.
|
|
0:04:08
|
So here we´re saying IP route, if we´re trying to get to
|
|
0:04:12
|
177.1.250.254/32
|
|
0:04:17
|
So that one host IP address, instead of routing out the default
|
|
0:04:21
|
interface loop back 1 routed out the interface service engine 00.
|
|
0:04:27
|
So again this is in your route siwtch exam, but
|
|
0:04:29
|
with CUE, we do have to take certain measures to attain layer 3
|
|
0:04:35
|
functionality and you will be responsible for this, so you do
|
|
0:04:39
|
have to understand some basic level of routing,
|
|
0:04:41
|
and that makes sense because after all, this is a CCIE
|
|
0:04:46
|
exam a Cisco certified internet working exam. Cisco obviously
|
|
0:04:50
|
made their name and their core competency is routing and switching
|
|
0:04:55
|
ad after all we are dealing with VOIP, Voice Over IP, so you
|
|
0:04:59
|
do have to know some things about routing the internet protocol.
|
|
0:05:05
|
Eventhough that´s not obviously the bulk of the exam
|
|
0:05:07
|
we did as well for networking infrastructure, we have to deal
|
|
0:05:10
|
with VLANs and SVIs and a little bit of multicast
|
|
0:05:16
|
even if it was only PIM dense mode, so there are some things.
|
|
0:05:19
|
OK, and then we also tell the service module so
|
|
0:05:23
|
this is how the service module, the queue module, the CUE
|
|
0:05:26
|
gets its IP address and its difficult gateway, so IV default
|
|
0:05:31
|
and the IP address, is the IP address of this interface
|
|
0:05:35
|
which is unnumbered or borrowed from loop back 1
|
|
0:05:38
|
so these 2 IPs are the same.
|
|
0:05:42
|
Once we have this set up and we´ve issued a no shut
|
|
0:05:45
|
down to the interface service 00, then we have the ability
|
|
0:05:50
|
to service or what´s called session in to that module. So
|
|
0:05:56
|
if you have ever worked on an old 6500 that had CAT OS at a layer 2,
|
|
0:06:02
|
and then you would have to, what was called session
|
|
0:06:05
|
in to the msfc or the layer 3, routing module the
|
|
0:06:09
|
multi switch feature card. If you haven´t, you probably have
|
|
0:06:14
|
interacted with CAT 6500s and native IOS, but
|
|
0:06:17
|
that´s not what I´m talking about. If you ever interact
|
|
0:06:20
|
to the old CAT OS, you had to do the same thing.
|
|
0:06:22
|
So essentially what this is, when we´re saying service module
|
|
0:06:25
|
calling on the service module, service engine 00 and then the wors session
|
|
0:06:29
|
this is a reverse telnet. So what we´re doing is from
|
|
0:06:32
|
the router IOS we´re actually reverse telnetting
|
|
0:06:35
|
in to the consul port, into the consult port of the Unity Express module
|
|
0:06:43
|
it has a layer 3 IP address, but we can´t telnet to it
|
|
0:06:48
|
for SSH or anything yet, we haven´t set that functionality up so
|
|
0:06:51
|
to begin with we have to reverse telnet in to the consul.
|
|
0:06:55
|
And to get out of this, if we need to go back
|
|
0:06:57
|
to branch2, we can obviously always type exit.
|
|
0:07:01
|
But if we don´t want to type exit, we want to stay
|
|
0:07:04
|
in the configuration for CUE, but we want to just
|
|
0:07:06
|
jump back to Branch2. We can do what we would do on a terminal server
|
|
0:07:11
|
or an access whichever we prefer to call it.
|
|
0:07:14
|
Which is Ctrl Shift 6, so all 3 of those keys together
|
|
0:07:18
|
and then let go of them and hit X.
|
|
0:07:21
|
Now one another note real briefly is that if you were already
|
|
0:07:25
|
using a terminal or access server to get in to
|
|
0:07:28
|
the Branch2, so you reverse telnet in to the consul of Branch2
|
|
0:07:32
|
And then you did another reverse telnet, so you
|
|
0:07:36
|
issued the session command to get in to the CUE module.
|
|
0:07:40
|
If you hit Ctrl Shift 6 all together and then release and press X
|
|
0:07:46
|
you´ll jump back not from queue back to Branch2
|
|
0:07:49
|
you´ll actually jump all the way back to the root of the terminal server.
|
|
0:07:53
|
If you want to, if that´s what you wanted to do then that´s great.
|
|
0:07:57
|
If what you wanted to do is only jump back one level.
|
|
0:08:01
|
Then what you do is hit Ctrl Shift 6
|
|
0:08:04
|
release and then again Ctrl Shift 6
|
|
0:08:08
|
all together and then release and then X.
|
|
0:08:12
|
It´s not Ctrl Shift 6 X, Ctrl Shift 6 X,
|
|
0:08:15
|
it´s simply Ctrl Shift 6 release, Ctrl Shift 6 release and then X.
|
|
0:08:22
|
OK, that will jump you back just one level.
|
|
0:08:25
|
OK. So moving beyond that, one other thing here is that
|
|
0:08:29
|
in our particular network, in our particular
|
|
0:08:33
|
racks, we tend to run the ospf protocol to
|
|
0:08:38
|
advertise all the networks and interfaces in that
|
|
0:08:42
|
networks, from each device, each router
|
|
0:08:45
|
to all of the other routers and provide full
|
|
0:08:50
|
NLRI, Network Layer Reachability Information
|
|
0:08:55
|
and
|
|
0:08:57
|
if we were running eigrp, we probably wouldn´t run in to this issue
|
|
0:09:01
|
but by default, the way that the ospf protocol and
|
|
0:09:05
|
and really the RFCs were written is that
|
|
0:09:08
|
if I have a loop back interface
|
|
0:09:12
|
it will natively be advertise into, if I have I should
|
|
0:09:18
|
maybe quantify that a little more. If have a loop
|
|
0:09:21
|
back interface with an IP address and a
|
|
0:09:23
|
something other than a /32. I have like a /24
|
|
0:09:27
|
it will actually be advertise in to the ospf process as
|
|
0:09:32
|
a stub type interface because it´s a loop back and
|
|
0:09:38
|
traditionally a loop back indicates that there is exactly
|
|
0:09:42
|
one interface or one IP address, right? So it´s sort of
|
|
0:09:46
|
the thinking was why would there be more than one
|
|
0:09:49
|
IP address on the loop back, the whole idea
|
|
0:09:52
|
it is a test interface that we can loop traffic back
|
|
0:09:56
|
have it theoretically leave the router and loop
|
|
0:09:59
|
right back and come in to the router.
|
|
0:10:02
|
So anyhow it ospf natively advertises even a /24
|
|
0:10:08
|
if it´s a loop back interface as a /32 network
|
|
0:10:12
|
So this would be that only the 177.1.250.1 IP would be able to be reach
|
|
0:10:18
|
eventhough they´re actually was in this particular
|
|
0:10:20
|
instance a second IP address or maybe even more
|
|
0:10:23
|
than that IP addresses on this router
|
|
0:10:27
|
so all the other routers would only be able to ping .1,
|
|
0:10:29
|
they would not be able to ping .254 and we could not have
|
|
0:10:34
|
let´say a call coming in on a VOIP trunk in to router 3
|
|
0:10:38
|
and go to the queue module because the
|
|
0:10:42
|
rtp stream would not make it there because IP routing doesn´t
|
|
0:10:46
|
from the other routers that we´re trying to get there,
|
|
0:10:48
|
doesn´t know how to get there. So what we need to do is
|
|
0:10:51
|
if we´re using ospf, we could in the ospf
|
|
0:10:55
|
router ospf sub command or sub area we could say redistribute static
|
|
0:11:02
|
and that´s going to redistribute the static route in ospf
|
|
0:11:06
|
another and I think the easier way and certainly works everytime
|
|
0:11:11
|
more predictable in my opinion or experience
|
|
0:11:14
|
is on the interface loop back simply say
|
|
0:11:17
|
basically tell it that it´s a different type of network type then
|
|
0:11:22
|
the routing protocol thinks it is by default
|
|
0:11:24
|
it considers it a stub interface or a stub network
|
|
0:11:28
|
but we´re going to tell it it´s a IP ospf, by the way this isn´t
|
|
0:11:33
|
the same as like a ospf stub network this is a
|
|
0:11:36
|
stub interface type, but anyhow we would simply
|
|
0:11:40
|
say IP ospf network point to point and that would
|
|
0:11:43
|
properly advertise the /24.
|
|
0:11:47
|
So once we reverse telnet or session in to the CUE module
|
|
0:11:52
|
we can either press enable and either the password is Cisco or
|
|
0:11:57
|
might just be blank when you get there to the lab.
|
|
0:12:02
|
So that we don´t have that greater than symbol, we have the hash.
|
|
0:12:06
|
Now we´re used to in IOS, if we have that greather than symbol
|
|
0:12:11
|
at the end of our prompt where it privilege 1
|
|
0:12:14
|
and if we have the hash, we´re used to that being
|
|
0:12:18
|
an elevated privilege most often privilege 15
|
|
0:12:22
|
That is not necessarily the case in CUE, CUE is a
|
|
0:12:26
|
a linux server basically running on either a flash
|
|
0:12:29
|
hard or an actual hard disk depending on whether it´s
|
|
0:12:31
|
AIM queue or network module queue.
|
|
0:12:35
|
Either way, what we see that or what we experience
|
|
0:12:40
|
for a shell is it´s an IOS like shell, but it´s really a sandbox
|
|
0:12:45
|
pseudo shell, it´s not really IOS. So whether we are
|
|
0:12:50
|
here at the greater than or here at the hash
|
|
0:12:53
|
that is whether we enter enable or not, we should still
|
|
0:12:56
|
be able to do all the same things. So that is if you hit enter able
|
|
0:12:59
|
sorry, you enter the command enable and
|
|
0:13:03
|
you can´t figure out the password, it doesn´t work,
|
|
0:13:05
|
they´re not telling you. You should still be able to do
|
|
0:13:07
|
all the functionality right there at the greater than.
|
|
0:13:10
|
So we´ll type offline and once we answer the question
|
|
0:13:14
|
yes, that we are sure we want to go offline.
|
|
0:13:16
|
We´ll do the restore factory default.
|
|
0:13:22
|
OK. Now once the reboot has occured. And actually let me go back and say
|
|
0:13:27
|
before we do the restore factory default, it might
|
|
0:13:30
|
be a good idea and in fact even before we´ve gone offline
|
|
0:13:35
|
to do a show software license from CUE
|
|
0:13:41
|
greater than prompt or hash prompt and the reason for this is
|
|
0:13:44
|
we´ll be able to see from the output of that command
|
|
0:13:47
|
and we´ll take a look at here in a moment.
|
|
0:13:49
|
We´ll be able to see from the output of that command,
|
|
0:13:54
|
in fact, in oder to make sure that we do have a default configuration.
|
|
0:13:59
|
I´m actually going to switch over there real quickly and issue this
|
|
0:14:02
|
that way we can not only see it, but also so that we can
|
|
0:14:06
|
do the restore factory default and make sure that we
|
|
0:14:11
|
that the reboot, that we´re talking about that could take
|
|
0:14:14
|
in unvariable amount of time, typically somewhere between
|
|
0:14:17
|
5 to 15 minutes, that we´re not actually waiting for that
|
|
0:14:20
|
during a demo. So let´s just actually switch over there real briefly
|
|
0:14:24
|
we´re over here at Branch2, let´s do a show run
|
|
0:14:28
|
for interface service engine 00, now I may have already populated this
|
|
0:14:32
|
I have not, good. So we´re going to jump in.
|
|
0:14:36
|
Actually, let´s do show IP interface brief
|
|
0:14:40
|
| to include unassign. So we don´t want to see any
|
|
0:14:43
|
IP address is where the column contents for that
|
|
0:14:47
|
column say unassign. So we´re only looking at interfaces
|
|
0:14:50
|
where there are IP addresses assigned and for this
|
|
0:14:53
|
we only see loop back 0, that was the initial config that I had ran.
|
|
0:14:58
|
Let´s go ahead and add the loop back 1, as we were mentioning
|
|
0:15:03
|
and go ahead and assign IP address 177.1.250.1
|
|
0:15:11
|
with a subnet mask of 255 255 255.0
|
|
0:15:17
|
So let´s issue that command again, now we see loop back 1 as well.
|
|
0:15:24
|
And if we, let´s do show run | to section RO
|
|
0:15:33
|
which is router ospf and it looks like were advertising all the networks.
|
|
0:15:38
|
One other quick thing about ospf and really about all igps
|
|
0:15:43
|
eigrp or ospf when we issue and again this is just because
|
|
0:15:48
|
we could see this in the lab, not because I want to exploit or
|
|
0:15:54
|
go in to how every single thing in the router works
|
|
0:15:59
|
but when we issue a network command in a protocol
|
|
0:16:06
|
routing protocol like ospf eigrp, what we´re not saying is
|
|
0:16:10
|
broadcast this network, whatever we put in here
|
|
0:16:14
|
and whatever subnet mask, inversed mask we put in.
|
|
0:16:19
|
What we are saying is if whatever network
|
|
0:16:25
|
or whether host or whatever it is that we put in here
|
|
0:16:30
|
if that exist on the system, on the router
|
|
0:16:34
|
as an IP address on a given interface then take
|
|
0:16:39
|
whatever interface that represents. So for instance
|
|
0:16:42
|
if I wanted to router ospf 1 and I said network
|
|
0:16:49
|
this IP address 177.3.11.1
|
|
0:16:53
|
Now I happen to know that´s actually the network of 177.3.11.0/24
|
|
0:16:59
|
because if I go and look at that interface, I would see
|
|
0:17:02
|
IP address 177.3.11.1 space 255 255 255.0/24
|
|
0:17:11
|
but if I were to say network 177.3.11.1
|
|
0:17:14
|
with the inversed mask, so ospf wild card bits of 0.0.0.0
|
|
0:17:22
|
OK. It´s inversed, so it´s not 255 255 255 255
|
|
0:17:27
|
that´s explicitly saying that IP address, it´s not listing the network.
|
|
0:17:32
|
If it was the network it would be 0.0.0.255, right? So
|
|
0:17:37
|
if I´m doing that, does that mean I´m only advertising this IP address?
|
|
0:17:41
|
No, it means, if whatever I´m putting here
|
|
0:17:44
|
so explicitly that host. If that matches an IP address on the system
|
|
0:17:50
|
then ospf says, OK I will include that interface.
|
|
0:17:53
|
So it goes out to the interface and grabs whatever
|
|
0:17:56
|
network and subnet mask is configured and it advertises it.
|
|
0:18:01
|
OK, so with that, that´s where the easiest way if you´re in a given
|
|
0:18:09
|
CCIE voice lab and for some reason you don´t have
|
|
0:18:12
|
layer 3 connectivity to 1 or multiple interfaces
|
|
0:18:16
|
and you check your router ospf, even if you don´t
|
|
0:18:20
|
really know what you´re doing, at least in a, again
|
|
0:18:25
|
this is just in a voice lab, OK. And I´m not saying this
|
|
0:18:27
|
for a production network, just like you shouldn´t use PIM dense mode
|
|
0:18:30
|
in a production network, obviously this doesn´t go for
|
|
0:18:33
|
a route switch exam, doesn´t even begin to
|
|
0:18:37
|
touch on a route switch exam, but the safest thing to do
|
|
0:18:40
|
in a voice exam would simply be to go in to the
|
|
0:18:43
|
router ospf protocol or router eigrp and issue the network
|
|
0:18:48
|
0000 255 255 255 255
|
|
0:18:52
|
area 0 command. What you´re saying is all interfaces.
|
|
0:18:57
|
So basically 0000 any IP address with all the wild card bits
|
|
0:19:05
|
OK. This is sort of like a default route. You´re basically advertising
|
|
0:19:08
|
all networks or all interfaces that have IP addresses on the system
|
|
0:19:13
|
in to the routing protocol. So this is the
|
|
0:19:16
|
quickest way to get all interfaces to route.
|
|
0:19:20
|
OK. Let´s just make sure I didn´t actually do
|
|
0:19:23
|
anything to ospf, to change that I didn´t. Let´s take a look at my
|
|
0:19:28
|
interface, I´ve got my loop back 1. So let´s go back to
|
|
0:19:32
|
actually let´s switch over to router 1, first before I do that
|
|
0:19:36
|
I will say show IP ospf interface loop back 1
|
|
0:19:43
|
and I´ll see that loop back 1 is up. ospf has this
|
|
0:19:50
|
in its process ID 1, that´s what this right router ospf process ID 1.
|
|
0:19:55
|
And the loop back interface is treated as a stub host
|
|
0:19:59
|
network type is loopback, so if I go over to router 1
|
|
0:20:03
|
and I do show IP route for ospf routes.
|
|
0:20:08
|
In fact actually let me just clear that off and say show IP route
|
|
0:20:12
|
| to include 177.1.250 I believe is what it was
|
|
0:20:19
|
forgot the i for include. I see it, but it has a /32
|
|
0:20:25
|
So actually, so that we can see this work full circle
|
|
0:20:30
|
Let´s go ahead and before I issue antyhing else, do show run
|
|
0:20:35
|
interface loop back 1 and
|
|
0:20:41
|
also do show run interface service engine 00.
|
|
0:20:45
|
Let´s jump in to interface service engine 00
|
|
0:20:50
|
Let´s do an IP unnumbered, so we´re borrowing
|
|
0:20:54
|
the loop back 1 interface and we´ll say service module.
|
|
0:21:01
|
It says no IP address for service engine 00
|
|
0:21:05
|
no IP address on interface that´s because we didn´t put one.
|
|
0:21:08
|
We just borrowed that network, but we didn´t actually assigned
|
|
0:21:11
|
an IP address. So service module IP and we have
|
|
0:21:15
|
address and default gateway. We´re going to sign the
|
|
0:21:18
|
IP address to the CUE module, it´s going to be the same network
|
|
0:21:26
|
but it´s going to be a different host, we´ll just say 254
|
|
0:21:28
|
because that´s what we use in other examples
|
|
0:21:31
|
since this is a /24 it could be any other IP, it could be a
|
|
0:21:35
|
2.5.103 and we´ll issue the same subnet mask
|
|
0:21:41
|
/24 and then we´ll say service module IP default gateway
|
|
0:21:48
|
is 177.1.250. the IP of our
|
|
0:21:54
|
service engine 00 interface which is borrowed from loop back 1.
|
|
0:21:57
|
So it´s the same IP as loop back 1, we´ll say no shut
|
|
0:22:02
|
we´ll exit out and we´ll say can we ping 177.1.250.254
|
|
0:22:08
|
no, because even as router we´re trying to send
|
|
0:22:12
|
traffic out the loop back 1 interface. So what we have
|
|
0:22:16
|
to do is add the IP route for 177.1.250.254
|
|
0:22:24
|
So this specific IP address that we assigned to the CUE module
|
|
0:22:32
|
and the subnet mask will be a host mask or /32
|
|
0:22:36
|
so 255 255 255 255 and then instead of giving it an IP address
|
|
0:22:43
|
because we don´t have an X hop, we have to tell it what
|
|
0:22:47
|
interface to send out because by default it´s trying to send it out
|
|
0:22:50
|
the wrong interface, the loop back 1. So we have
|
|
0:22:52
|
to say service engine 0/0
|
|
0:22:59
|
Now if we try to ping that from our router
|
|
0:23:03
|
we are able to ping from our Branch2 router,
|
|
0:23:06
|
but if we go over to our Branch1 and we try
|
|
0:23:08
|
to ping 177.1.250.254
|
|
0:23:13
|
it´s unreachable, if we try to ping .1 the loop back
|
|
0:23:17
|
that would work, then the reason is the /32
|
|
0:23:21
|
host advertisement. So again on Branch2 config t
|
|
0:23:26
|
interface loop back 1 and IP ospf
|
|
0:23:31
|
network type of point to point will work
|
|
0:23:36
|
and if we go back over and show IP route
|
|
0:23:41
|
in just a moment, as ospf reconverges, there we go,
|
|
0:23:45
|
we see it change from a /32 to a /24
|
|
0:23:48
|
and we can not only ping .1 but we can also ping .254
|
|
0:23:56
|
OK. So now that we´ve done that, we should be able
|
|
0:23:59
|
to go ahead and service, service module
|
|
0:24:05
|
service engine 00 and then we can do other things
|
|
0:24:09
|
like status statistics, hrad bit reset, passwork reset.
|
|
0:24:16
|
Status, you know will tell us what version it´s running
|
|
0:24:18
|
but we can do session, so now we reverse telnet it
|
|
0:24:23
|
and it´s actually booting up from when we had
|
|
0:24:26
|
just no shut that interface so we´re going to go ahead
|
|
0:24:29
|
and as I mentioned this can take quite a long time.
|
|
0:24:32
|
So we´re just going to sit here and wait, I´m sorry
|
|
0:24:35
|
we´re not going to sit here and wait. We´re going to
|
|
0:24:37
|
go back to our slides, but in the real lab
|
|
0:24:40
|
you would make sure that you don´t sit there
|
|
0:24:42
|
and wait for that reboot, but that you do
|
|
0:24:48
|
that you do go in and check this off for license.
|
|
0:24:51
|
So that´s what I say here once the reboot is occured
|
|
0:24:53
|
by the way don´t watch and wait for the reboot to happen
|
|
0:24:56
|
it´s like a pot of boiling water, watch a pot never boils, right?
|
|
0:25:01
|
So do something else make use of your time
|
|
0:25:05
|
don´t sit there for 5 to 10 minutes doing nothing
|
|
0:25:08
|
once it´s done, check back in about 10 minutes.
|
|
0:25:12
|
Don´t check back in 5 minutes because it might not be
|
|
0:25:14
|
done and you´ll just get side track. Check back in 10 minutes
|
|
0:25:17
|
session back in to it and after we have, not only
|
|
0:25:21
|
factory reset it, but also hopefully check
|
|
0:25:25
|
the license and make sure that it´s the right license.
|
|
0:25:28
|
So we have to change the license and it has to go
|
|
0:25:30
|
through a reboot if it´s not running the proper license
|
|
0:25:34
|
For whatever we were told to integrate with
|
|
0:25:36
|
if we were told to integrate with CME and it´s
|
|
0:25:39
|
running the CUCM license then I have to ftp
|
|
0:25:43
|
and they´ll have to provide you with the credentials and the
|
|
0:25:46
|
path and the file name to pull from the ftp server
|
|
0:25:51
|
for most likely it would be running on your XP utility machine
|
|
0:25:54
|
as it is in our networks and if you´re unfamiliar with our network
|
|
0:25:58
|
or have ran in to this but not seen the answer
|
|
0:26:01
|
it´s actually in our voice rack rental access guide.
|
|
0:26:05
|
and it goes over exactly what commands to use
|
|
0:26:08
|
those commands were of course also in the documentation
|
|
0:26:11
|
which since it´s an open book exam and you have
|
|
0:26:14
|
access to all the documentation, you could simply copy and paste
|
|
0:26:17
|
changing the IP address of the ftp server and the name of
|
|
0:26:20
|
the file potentially, once we´re back and everything´s done
|
|
0:26:24
|
rebooting, we´re going to session in to it and
|
|
0:26:26
|
we´re going to run the CLI or Command Line Wizard
|
|
0:26:29
|
to do the initial set up, ntp, dns, even if we´re skipping dns
|
|
0:26:34
|
we do have to have a reachable ntp server
|
|
0:26:37
|
and set the language locale and the tones and all that.
|
|
0:26:44
|
Then we´ll probably web in to this, so we´ll browse
|
|
0:26:49
|
from our web browser to whatever the IP address of the
|
|
0:26:52
|
CUE module is and then /Web and the w has to be capital
|
|
0:26:58
|
it´s a linux, it´s apache, it is case sensitive
|
|
0:27:01
|
and we´ll most likely run the web wizard.
|
|
0:27:05
|
However, if you really want to maximize your time
|
|
0:27:07
|
I would recommend learning the CUE command line
|
|
0:27:10
|
because just like anything else such as IOS
|
|
0:27:13
|
it´s much faster, if you become proficient with it.
|
|
0:27:16
|
The basic concepts of the CLI configuration
|
|
0:27:20
|
are users mailboxes and groups and one thing that you
|
|
0:27:24
|
could certainly do is run the web user interface wizard.
|
|
0:27:28
|
In fact, I´d probably recommend doing this
|
|
0:27:30
|
run the web user interface wizard, just to set up
|
|
0:27:33
|
basic CCN sub system as they´re called in the CUE command line.
|
|
0:27:40
|
I´ve heard reports of people trying to set
|
|
0:27:43
|
those subsystems up from command line and
|
|
0:27:46
|
then not working, but if they set them up from the
|
|
0:27:49
|
web user interface wizard they work fine.
|
|
0:27:52
|
I personally think that, this was just due to a lack of
|
|
0:27:57
|
saving the configuration from command line and then
|
|
0:28:00
|
performing a reboot again on the Unity Express module
|
|
0:28:04
|
if you do set them up from command line, the CCN subsystem
|
|
0:28:09
|
whether jtapi or SIP or pitentially both for fall back
|
|
0:28:15
|
and then you save, that is you write the router or write the
|
|
0:28:19
|
Linux module configuration, the CUE configuration
|
|
0:28:22
|
and then reboot, they should work just fine.
|
|
0:28:28
|
Also one thing to notw is that while most, if I go back
|
|
0:28:34
|
couple slides and take a look just at the interface
|
|
0:28:36
|
until it comes up, whether I´m in greather than or
|
|
0:28:41
|
so or hash from either place. I can issue the same commands
|
|
0:28:46
|
I mentioned, but many times I need to put in config t
|
|
0:28:50
|
configuration terminal just like I would in a router IOS.
|
|
0:28:53
|
There are some things in Unity Express, however
|
|
0:28:56
|
that are done from what the router would call exec mode.
|
|
0:28:59
|
So it looks just like this, so the enable or offline
|
|
0:29:02
|
command, those are exec mode commands
|
|
0:29:05
|
Other things that are exact mode commands are
|
|
0:29:08
|
passwords and pins, those are configured for the user
|
|
0:29:12
|
it exec mode not under config t, almost everything else
|
|
0:29:16
|
actually, everything else that you see here is
|
|
0:29:19
|
done under config t. So creating a user
|
|
0:29:22
|
assigning that user that you just created a phone number
|
|
0:29:25
|
on extension, going in to the voicemail box
|
|
0:29:29
|
for the user that you just did, doing things like
|
|
0:29:32
|
turning off tutorial, context sensitive help
|
|
0:29:35
|
been command completion are still there. So command completion is
|
|
0:29:38
|
beginning a command and once you have enough characters that
|
|
0:29:42
|
make it non ambiguous with other commands,
|
|
0:29:45
|
you can hit tab for command completion or ?
|
|
0:29:49
|
So a comman space ?, or even just being in a subarea such as
|
|
0:29:53
|
voicemail box owner user and then saying
|
|
0:29:56
|
? gives you context sensitive help, those are there as well
|
|
0:30:01
|
here after I´ve exited it out, I´m not in
|
|
0:30:04
|
config t, I´m issuing the password and pin.
|
|
0:30:08
|
OK, this again is config t. I´m creating a group
|
|
0:30:11
|
and assigning memebers to the gourp and here
|
|
0:30:14
|
group name IP phones actually has a phone number.
|
|
0:30:17
|
3001 and the mailbox, so this is what would be
|
|
0:30:20
|
considered a general delivery mailbox, genereal deliver mailbox
|
|
0:30:25
|
is not done with a username as the owner of a mailbox.
|
|
0:30:32
|
So here I´m saying create a voicemail box and
|
|
0:30:35
|
assign it the owner user 1 that I just created.
|
|
0:30:37
|
Here I´m saying the exact same thing voicemail box
|
|
0:30:41
|
but I´m assigning at the owner of the IP phones
|
|
0:30:43
|
which is a group name not a user, so this
|
|
0:30:45
|
becomes a general delivery mailbox where the extension is 3000.
|
|
0:30:51
|
So if I forwarded calls let´s say possibly from a hunt pilot
|
|
0:30:56
|
and preferrably the hunt pilot would not be 3000 or
|
|
0:31:00
|
at least the voicemail box would not be 3000 if the hunt pilot was
|
|
0:31:06
|
and the reason for that is that I want to have the hunt pilot
|
|
0:31:11
|
and the voicemail box extension different at the end of that
|
|
0:31:16
|
you know ephone hunt or voicemail hunt it
|
|
0:31:20
|
back in IOS, back in CME traditional stand alone or
|
|
0:31:24
|
CME as srsts that at the end of that, I´m going to say final.
|
|
0:31:31
|
So I would say my, let´s say for instance ephone hunt 5
|
|
0:31:36
|
whatever circular peer, whatever that I would list
|
|
0:31:40
|
the members of that so list 3001,3002 assigning
|
|
0:31:45
|
phone dn 3001 and 3002 as hunt group members
|
|
0:31:50
|
and then I would say the command final and that would
|
|
0:31:53
|
basically say if it couldn´t reach one of those 2 members
|
|
0:31:56
|
maybe they were both busy or just didn´t answer
|
|
0:31:59
|
it would go to the final destination of
|
|
0:32:03
|
and let´s say my pilot point was 3000, maybe my
|
|
0:32:07
|
phone number for IP phones hunt group would be 3001
|
|
0:32:11
|
or maybe not 3001, but 3100, something else.
|
|
0:32:15
|
Now here´s the reason for that, the voicemail hunt group
|
|
0:32:19
|
forwards to 3100, here the Unity Express just like
|
|
0:32:26
|
Unity Connection seize the forwarding number and try
|
|
0:32:28
|
to initially send that forwarded call to the forwarding
|
|
0:32:33
|
number mailbox. Imagine this is 3100 and not 3000.
|
|
0:32:39
|
And then after a messages accepted and taken
|
|
0:32:44
|
Unity Express has taken the message from the original calling party
|
|
0:32:48
|
it goes out and tries to light dn 3100 with
|
|
0:32:53
|
the mwi if dn 3100 is actually a voicemail pilot
|
|
0:32:59
|
we can´t assign in to a line, but we can
|
|
0:33:04
|
if the pilot was 3000 and the voicemail box was 3100
|
|
0:33:09
|
although we forwarded to a different number than our pilot point.
|
|
0:33:13
|
We can or we can even route that through an ephone dn
|
|
0:33:17
|
if we needed to have another forwarding point or use a voice
|
|
0:33:21
|
translation role, there´s a number of ways we can get the
|
|
0:33:23
|
forwarding number to be what we want and I aplogize
|
|
0:33:27
|
the final number would actually be the voicemail pilot.
|
|
0:33:30
|
So 3800, but we could say if you´re coming
|
|
0:33:33
|
via voice translation role on the outgoing SIP dial peer
|
|
0:33:38
|
in CME going in to queue, Unity Express
|
|
0:33:42
|
We could say if the forwarding or redirect
|
|
0:33:45
|
calling number is 3000 change it to 3100
|
|
0:33:49
|
that way ti hits the proper mailbox and then when
|
|
0:33:53
|
Unity Express goes to light the mwi for 3100
|
|
0:33:57
|
we simply have a new ephone dn called 3100
|
|
0:34:02
|
and we assign it to the line of all the other phones
|
|
0:34:06
|
there that happened to be a part of that hunt group.
|
|
0:34:14
|
So that way we can provide not only mailboxes
|
|
0:34:18
|
with mwi for each phones primary dn, but also for
|
|
0:34:22
|
a group or general delivery mailbox.
|
|
0:34:26
|
Now some candidates have asked or students have asked
|
|
0:34:32
|
over many years and a few blue print view
|
|
0:34:35
|
versions because CUE´s been there for a few blue print versions.
|
|
0:34:41
|
What if for some reason the web user interface was not available?
|
|
0:34:44
|
maybe that is that they actually arrived at the lab and
|
|
0:34:48
|
they met with a problem of being able to actually
|
|
0:34:52
|
see the web user interface for CUE. Well first of all
|
|
0:34:56
|
you can still use the command line, so remember you can do
|
|
0:34:59
|
everything including, first of all command line
|
|
0:35:02
|
initialization obviously run from the command line
|
|
0:35:05
|
but the second wizard, the web user interface set up wizard
|
|
0:35:09
|
as I mentioned all that can be done from command line
|
|
0:35:12
|
as long as as soon you´re done setting up those CCN subsystems
|
|
0:35:15
|
then I would probably go ahead and set up all my users,
|
|
0:35:17
|
groups and everything else i had to do. I would write
|
|
0:35:20
|
that CUE configuration and issue a restart or reload.
|
|
0:35:25
|
And then let that reload and everything should work, but
|
|
0:35:31
|
let´s say you just really wanted to use the web user interface
|
|
0:35:33
|
you´re not familiar with the command line. It´s most
|
|
0:35:36
|
probable that you´re missing just a few commands
|
|
0:35:39
|
in CME or at least in IOS, the IOSthat houses
|
|
0:35:43
|
the CUE module because most certainly the CUE module
|
|
0:35:47
|
could be on a router that doesn´t even have or
|
|
0:35:50
|
you weren´t even told to run CME on, but in IOS
|
|
0:35:53
|
of the router iphttp server enabling that web server
|
|
0:35:58
|
and iphttp path flash and then wherever we happened to find
|
|
0:36:04
|
the user interface for CME, if it was there. OK, so
|
|
0:36:10
|
if you don´t see anything then just flash colon,
|
|
0:36:12
|
but if you do a show flash | to include .htm
|
|
0:36:21
|
maybe .html but .htm is inclusive of htm and html files
|
|
0:36:27
|
then you´ll find, if those files exist anywhere.
|
|
0:36:30
|
If they happened to exist in a subdirectory like
|
|
0:36:32
|
here, we have them in our routers in the GUE, the GUE subdirectory.
|
|
0:36:41
|
It´s also possible that CME web user interface though
|
|
0:36:44
|
probably shouldn´t prevent you from getting to the CUE.
|
|
0:36:48
|
web user interface. Since that serve from the Linux server itself
|
|
0:36:51
|
it may prevent you from the CUE web user interface, not
|
|
0:36:56
|
being able to connect to CME through web
|
|
0:37:01
|
http protocol and therefore see the configuration
|
|
0:37:06
|
and CUE download or import the users from CME.
|
|
0:37:10
|
So if for any reason thas was the case
|
|
0:37:14
|
that the CME web user interface was present
|
|
0:37:17
|
in flash, but not extracted so for instance
|
|
0:37:21
|
it has CME-GUI-XXX.tar so whatever version
|
|
0:37:27
|
or however they´ve named the file. If it´s a tar file
|
|
0:37:31
|
depending on how the flashes formatted, I should be able
|
|
0:37:33
|
to run the archive tar /extract and say flash
|
|
0:37:37
|
colon the name of the file, so I would do show flash | to include tar.
|
|
0:37:44
|
Find that file name and then extract it to flash colon, the root
|
|
0:37:49
|
and also another possibility that I don´t have on the slide is that
|
|
0:37:53
|
triple A was enabled, but not set up properly or inclusive enough
|
|
0:38:00
|
in the IOS router and it´s blocking even remote
|
|
0:38:05
|
telnet session. This would actually be not the web user interface
|
|
0:38:08
|
but you can´t even telnet or reverse telnet, you can´t even session
|
|
0:38:12
|
in to the router. When you try to issue that service module
|
|
0:38:15
|
space srvice engine 00 space session command
|
|
0:38:20
|
that when you try to do that, it says username and password just to get in.
|
|
0:38:25
|
That´s probably indicative of triple A, so I would
|
|
0:38:28
|
Ctrl Shift 6 X or Ctrl Shift 6 Ctrl Shift 6 X
|
|
0:38:33
|
and the reason I mentioned that that terminal server
|
|
0:38:36
|
is because in the real lab, you can elect to telnet
|
|
0:38:39
|
to each of your routers but by default on your candidate dekstop
|
|
0:38:42
|
you have a shortcut for puddy or for secure crt
|
|
0:38:50
|
to get in to each of your routers, but that is actually
|
|
0:38:52
|
taking you through a reverse telnet to the consul so
|
|
0:38:56
|
again if you did that Ctrl Shift 6 X, you would
|
|
0:39:00
|
be jumped out to the group level, so issue it twice and then the X
|
|
0:39:05
|
and then simply back in router IOS inter config t
|
|
0:39:10
|
and say no triple A, so no AAA, new model.
|
|
0:39:15
|
That will take off all any triple A configuration and allow
|
|
0:39:20
|
default access. Another thing is that the possibly that
|
|
0:39:25
|
the web user interface is there, but CUE username and
|
|
0:39:28
|
password doesn´t work. So you can access it when you go to this
|
|
0:39:32
|
when you browse to this IP address and web forward slash
|
|
0:39:37
|
you can get to the page, but your username and pass don´t work.
|
|
0:39:42
|
It´s easy enough, you basically need password recovery for CUE
|
|
0:39:47
|
and it´s terribly simple, you session in to the command line and
|
|
0:39:52
|
guess what you can do without even being able to get in to the
|
|
0:39:54
|
web user interface, you can do pretty much anything in the command line.
|
|
0:39:58
|
If you have consul access to it so we simply create a new user
|
|
0:40:05
|
and so we´ll say username you know our admin or
|
|
0:40:11
|
my admin or whatever you want to call it and there´s already a group
|
|
0:40:15
|
name called administrators. You simply add that new user that you created
|
|
0:40:20
|
and after that you obviously set the password for that user as well.
|
|
0:40:24
|
But you add to the administartors group and then
|
|
0:40:27
|
you try that and you will be able to get in to
|
|
0:40:29
|
the Web User Interface for CUE from there.
|
|
0:40:34
|
So looking at CUE and DTMF relay, so with
|
|
0:40:38
|
Unity Express just like with contact center express.
|
|
0:40:43
|
There is most certainly going to be the need for dtmf.
|
|
0:40:47
|
Let´s say I´m checking my messages, I need to be able to enter my pin
|
|
0:40:51
|
or I need to be able to press 1 to listen to nre messages or 3 to delete
|
|
0:40:57
|
etcetera. Likewise calling parties in possibly want to
|
|
0:41:03
|
issue dtmf whether they´re traversing Auto-attendants.
|
|
0:41:08
|
So menu trees or whether they´re pressing hash
|
|
0:41:12
|
and then 1 after they´re done leaving a message to market
|
|
0:41:17
|
with urgent priority, whatever it is dtmf is neccessary or dtmf relay.
|
|
0:41:23
|
So on an outbound dial peer to CUE, the best dtmf
|
|
0:41:28
|
to enter is dtmf relay SIP notify, by the way and I think we´ve
|
|
0:41:32
|
mention this before, in the media section. I can put multiple
|
|
0:41:37
|
dtmf relay types on the same line. What this means
|
|
0:41:42
|
is that they are in the order of priority that we want
|
|
0:41:45
|
to try them. So if I said dtmf relay SIP notify
|
|
0:41:48
|
space rtp nte because I just in the lab couldn´t recall, wait a minute
|
|
0:41:53
|
for CUE should it be SIP notify or should it be
|
|
0:41:57
|
rtp nte which is Real Time Protocol pockets using name telefany events
|
|
0:42:03
|
also known as rfc 2833, which one is it?
|
|
0:42:08
|
It´s very simple, I could say SIP notify space rtp nte
|
|
0:42:13
|
and then if SIP notify is supported, it will be used
|
|
0:42:17
|
and if it´s not then the next will be used provided than one of the two
|
|
0:42:22
|
is supported, but the label they will be able to be negotiated
|
|
0:42:26
|
and a debug CC SIP messages, specifically in the
|
|
0:42:30
|
sdl, the session description language will tell me
|
|
0:42:33
|
what is being offered and then ultimately negotiated.
|
|
0:42:39
|
All other dial peers, for example a trunk
|
|
0:42:42
|
to and from CUCM should use rtp nte and
|
|
0:42:46
|
if we have rtp nte that is any sort of dtmf relay
|
|
0:42:52
|
that either samples the actual tones, the actual dual tone multi frequency
|
|
0:42:58
|
frequency which would only be Cisco in band proprietory.
|
|
0:43:02
|
or simply uses rtp pockets doesn´t sample the audio takes them as
|
|
0:43:09
|
you know digital zeros and ones binary, but
|
|
0:43:14
|
so it´s sort of an outband in the sense that it´s reliable
|
|
0:43:18
|
but uses utp rtp pockets and the payload to handle that
|
|
0:43:23
|
so rtp nte, then we need to make sure that we
|
|
0:43:27
|
have some sort of mtp or in
|
|
0:43:34
|
Unity Express really in IOS what we would do is just have
|
|
0:43:37
|
a transcoder which is also an mtp. So what handles this CUBE
|
|
0:43:42
|
unified border limit, so we need to make sure that
|
|
0:43:45
|
we have allow connection in bound protocol to
|
|
0:43:48
|
outbound protocol would be SIP, probably a good idea
|
|
0:43:52
|
to have the other way as well, just in case
|
|
0:43:54
|
CUE is playing any tones on an outbound call.
|
|
0:43:59
|
So make sure that you have that and then also you should
|
|
0:44:02
|
make sure that you have as we mentioned earlier, a transcoder.
|
|
0:44:06
|
for a dsp farm under a sccp ccm group
|
|
0:44:12
|
and dsp profile registered to a local CME router
|
|
0:44:17
|
or local CME process, so telefany service
|
|
0:44:19
|
even if you weren´t told to run CME, why?
|
|
0:44:23
|
because that´s the way that unified border element,
|
|
0:44:25
|
as we mentioned back in both the gateways and trunks
|
|
0:44:30
|
module as well as the h323 gate keeper with CUBE module.
|
|
0:44:34
|
That´s the way the CUBE accesses and invokes
|
|
0:44:39
|
a transcoder is the local router must be running
|
|
0:44:44
|
some sort of Skinny server process.
|
|
0:44:50
|
Finally, actually not quite finally to ensure that
|
|
0:44:54
|
CUE works for voicemail and mwi since there´s
|
|
0:44:59
|
going to be SIP signaling from the router to the CUE module
|
|
0:45:02
|
under voice service VOIP and then under the subsection for SIP.
|
|
0:45:08
|
Make sure that you have all SIP traffic
|
|
0:45:13
|
so signaling and media bound to a source
|
|
0:45:17
|
address, the single IP address, most preferrably a loop back
|
|
0:45:21
|
and the same IP address as our source address
|
|
0:45:24
|
under telefany service for CME. And then when we´re defining that IP
|
|
0:45:28
|
and either Unity Express web user interface wizard
|
|
0:45:32
|
for CME or if we´re integrating with CUCM.
|
|
0:45:37
|
For our tertiary fall backs so if we´re integrating
|
|
0:45:40
|
the CUCM is will see in a moment. We´ll have our primary
|
|
0:45:43
|
IP will be our subscriber CUCM server, secondary will be our
|
|
0:45:47
|
publisher server and our tertiary will be our CME fall back
|
|
0:45:53
|
srst, make sure those are all the same loop back IP address
|
|
0:46:00
|
and then looking at mwi
|
|
0:46:04
|
the most efficient and easiest to configure method
|
|
0:46:07
|
for Unity Express to light mwis, whether it´s integrated with
|
|
0:46:15
|
CUCM and Skinny phones, CUCM and SIP phones,
|
|
0:46:20
|
whether it´s integrated with CME and Skinny phones or CME and SIP phones.
|
|
0:46:24
|
And or all of the above possible permutations
|
|
0:46:28
|
is to use SIP unsolicited notify, actually I take that back.
|
|
0:46:31
|
If CUE is integrated with CUCM, I mispoke it´s not using
|
|
0:46:37
|
SIP unsolicited notify, it´s actually signaling mwi via JTAPI.
|
|
0:46:42
|
So if CUE is integrated with CUCM, it´s using JTAPI to light
|
|
0:46:48
|
mwis and because JTAPI or CTI applications
|
|
0:46:52
|
have no need of, well they have the abillity to
|
|
0:46:57
|
control the phones directly or indirectly through the CTI manager
|
|
0:47:01
|
running on the publisher subscriber server.
|
|
0:47:03
|
There´s no need for mwi on and off dns in CUCM
|
|
0:47:08
|
at least not for the Unity Express, we might need those
|
|
0:47:12
|
in the same CUCM cluster 4 Unity Connection
|
|
0:47:15
|
because it uses something called out dialing or actually dials a dn
|
|
0:47:20
|
but Unity Express integrated with CUCM does not need any mwi
|
|
0:47:25
|
dns, it´s using JTAPI. When it integrates with CUE
|
|
0:47:30
|
I´m sorry, with CME, Communication Manager Express
|
|
0:47:35
|
it can use out dialing, but preferrably it will just use SIP
|
|
0:47:39
|
unsolicited notify. So it´s using SIP notify, but it´s unsolicited
|
|
0:47:43
|
that is the phones had not requested the
|
|
0:47:48
|
the paricular SIP notify message so it wasn´t solicited,
|
|
0:47:53
|
it´s necessary that they support unsolicited notify
|
|
0:47:58
|
the way to do this is to set up a mwi server
|
|
0:48:01
|
on the IOS router. It´s simple enough under SIP UA
|
|
0:48:05
|
global configs, SIP UA, subsection we say mwi server
|
|
0:48:09
|
the IP address of the CUE module and then under
|
|
0:48:12
|
telefany service for our Skinny phones, we say mwi relay
|
|
0:48:17
|
and then under the actual ephone dn we say mwi method is.
|
|
0:48:23
|
OK. We don´t put mwi in a number, that´s if we were doing
|
|
0:48:26
|
turning that ephone dn in to an actual mwi on or off dn.
|
|
0:48:33
|
In this case ephone dn 1, although I don´t have the rest
|
|
0:48:36
|
of the configuration here is essentially saying that
|
|
0:48:39
|
this particulay dn, whatever a number it is, probably 3001 for instance.
|
|
0:48:44
|
That dn has a mailbox and that mailbox for mwi
|
|
0:48:48
|
is going to use the SIP method of signaling.
|
|
0:48:54
|
Ephone, notice I have mwi-line 6, what this is saying is
|
|
0:49:01
|
I can tell by default the mwi line will be line 1.
|
|
0:49:07
|
What that means is that I could receive an mwi
|
|
0:49:10
|
lamp light or unlight message for any of my lines.
|
|
0:49:15
|
but what is going to happen is that if it´s
|
|
0:49:19
|
the default of line 1, I will not only show a little
|
|
0:49:22
|
envelope right next to my button on my display, but the
|
|
0:49:26
|
also my actual lamp on my handset will light up.
|
|
0:49:32
|
However, if I received a message on any other line
|
|
0:49:36
|
let´s say line 2, 3, 4, 5 or 6
|
|
0:49:39
|
or more if I have more line buttons on my particular phone.
|
|
0:49:43
|
I will only see the little message, little enveloper icon
|
|
0:49:46
|
next to the line button, I will not see the lamp light.
|
|
0:49:51
|
However, with this command, I can change that default
|
|
0:49:54
|
functionality, so here I´m changing the defualt light lamp line.
|
|
0:49:58
|
to 6, so if I received an mwi on line 1, it will not light the lamp.
|
|
0:50:03
|
but mwi on line 6 will.
|
|
0:50:05
|
|
