|
0:00:15
|
We really don´t have that many slides today
|
|
0:00:18
|
we´re just going to look at some basic comparisons for features
|
|
0:00:22
|
and we will take a look a little bit more in depth
|
|
0:00:26
|
at some of the administration guide
|
|
0:00:29
|
and possibly the SRND for CME.
|
|
0:00:33
|
One of the things we want to look at is a comparison
|
|
0:00:36
|
of possible feature support and this is for skinny phones only
|
|
0:00:42
|
because SIP phones don´t support the dual line or octoline.
|
|
0:00:46
|
Well, it´s not that they don´t support them, it´s that
|
|
0:00:49
|
they don´t have the idea of them and we talked about why
|
|
0:00:53
|
last couple modules actually when we
|
|
0:00:58
|
showed how SIP phones, just as a brief refresher.
|
|
0:01:02
|
How SIP phones create VOIP dial peers
|
|
0:01:07
|
The voice register dn and the voice register pool combination
|
|
0:01:12
|
create VOIP dial peers
|
|
0:01:16
|
with skinny phones we showed how the voice.
|
|
0:01:20
|
Sorry not voice, but the ephone dn
|
|
0:01:23
|
creates a pots style peer and the ephone
|
|
0:01:27
|
creates a port, it´s actually reverse ephone creates the dial peer
|
|
0:01:32
|
and the ephone dn creates the port,
|
|
0:01:36
|
it´s kind of a little bit in reverse, but anyway
|
|
0:01:39
|
It´s sort of really doesn´t matter, but essentially that the
|
|
0:01:42
|
ephone dn, for every ephone dn and ephone combo
|
|
0:01:47
|
there is a pots port and dial peers, subsequent dial peer created.
|
|
0:01:53
|
And we talked a little about the fact that these were
|
|
0:01:56
|
pots dial peers or e, FXS ports
|
|
0:02:00
|
electronic or virtual FXS ports and look at
|
|
0:02:04
|
maybe some of the reasons why that was
|
|
0:02:08
|
There really are many many reasons and as we
|
|
0:02:11
|
begin looking at some of the features that the
|
|
0:02:14
|
skinny phones support today. I think it will become
|
|
0:02:17
|
even more clear why Cisco chose to go with
|
|
0:02:21
|
virtual FXS ports and virtual
|
|
0:02:27
|
or not virtual but pots dial peers as suppose
|
|
0:02:30
|
to the way that they pretty much were force to implement
|
|
0:02:34
|
the SIP phones which is through VOIP dial peers.
|
|
0:02:38
|
You´re going to see a lot of feature support
|
|
0:02:41
|
that really wouldn´t be possible if the skinny
|
|
0:02:44
|
phones had been implemented as VOIP dial peers.
|
|
0:02:49
|
And the reason that Cisco had to implement the
|
|
0:02:53
|
SIP phones as VOIP dial peers and are having
|
|
0:02:57
|
to you know really go back and scratch their heads
|
|
0:03:00
|
and figure out how they´re going to support all of these
|
|
0:03:03
|
Wide array of features that the skinny phones already support.
|
|
0:03:08
|
The reason they had to implement MS VOIP dial peers was
|
|
0:03:12
|
if they wanted to truly implement SIP as a
|
|
0:03:16
|
industry standard according to the RFCs,
|
|
0:03:19
|
then they really couldn´t deviate from those RFCs
|
|
0:03:24
|
Those ITF request ro comments that outline
|
|
0:03:29
|
how SIP end point and SIP signaling in general should be
|
|
0:03:35
|
should be implemented.
|
|
0:03:38
|
And so because of that they to fall, they had to work within
|
|
0:03:41
|
that existing construct and they really had to use VOIP
|
|
0:03:45
|
dial peers that we´ll going to see as we move on expecially today
|
|
0:03:50
|
that a lot of the features that skinny phones support
|
|
0:03:53
|
SIP phones do not support, they do support some.
|
|
0:03:56
|
OK, so first of all if we´re using this single line
|
|
0:04:01
|
or another words single media channel with the skinny phone
|
|
0:04:05
|
and this is actually what the ephone dn registered to a skinny phone
|
|
0:04:09
|
of course. Then the barge is not supported
|
|
0:04:13
|
it´s not supported on dual line or 2 media channels either.
|
|
0:04:16
|
It is supported on octoline or 8 media channels
|
|
0:04:21
|
and one of the reasons we mentioned that this was, was because
|
|
0:04:26
|
with a dual line we have something called
|
|
0:04:30
|
exclusive use, that is if we have a shared line
|
|
0:04:36
|
a shared dn between 2 skinny phones and that dn
|
|
0:04:41
|
is also a dual line ephone dn, there are 2 media channels.
|
|
0:04:47
|
The moment that one ephone or skinny phone seizes
|
|
0:04:52
|
whether to answer a call or to make an outgoing call
|
|
0:04:55
|
whenever it seizes that dual line dn both
|
|
0:04:59
|
media channels are reserved for the phone that did the seizing.
|
|
0:05:04
|
And the reason for this is probably failry clear
|
|
0:05:08
|
what if that phone needed to either a.receive
|
|
0:05:12
|
call waiting, incoming or b. do a consultative
|
|
0:05:17
|
transfer or forward that existing call back out to someone else.
|
|
0:05:21
|
If there´s not another media channel available
|
|
0:05:24
|
then we you know, really can´t do that consultative
|
|
0:05:29
|
transfer or have the possibility of call waiting.
|
|
0:05:32
|
So with only 2 media channels, the first phone to seize it
|
|
0:05:35
|
gets both media channels. Now as soon as we go beyond
|
|
0:05:39
|
2 media channels, you know if we had a triple line or a
|
|
0:05:43
|
quad line or a quin line or anything else.
|
|
0:05:47
|
Then all the sudden opportunities open up especially
|
|
0:05:49
|
if you have a quad line, but there´s no such thing as a quad line.
|
|
0:05:53
|
We do have an octo line, that´s just the next place they went
|
|
0:05:56
|
instead of creating 4 media channels they said
|
|
0:05:59
|
let´s just quadruple the dual line, let´s make it an octo line.
|
|
0:06:05
|
So there´s 8 media channels and there is the opportunity
|
|
0:06:08
|
for non exclusive use. OK? So
|
|
0:06:13
|
one phone can seize one media channel and another
|
|
0:06:17
|
phone can seize another media channel and
|
|
0:06:21
|
really it doesn´t need to reserve 2 media channels whenever
|
|
0:06:24
|
you seize one. It´s just basically each one reseizes
|
|
0:06:27
|
and reserves one channel, the one´s in use
|
|
0:06:31
|
and then we basically know that there are more
|
|
0:06:35
|
media channels available if need be for
|
|
0:06:38
|
consultative transfer and call waiting and so forth.
|
|
0:06:42
|
So we also open up the possibility with an octo line
|
|
0:06:46
|
or Barge feature on a shared line.Looking at busy trigger.
|
|
0:06:55
|
Busy trigger, we are going to look at today gives us
|
|
0:06:58
|
actually we looked at that back in module 1
|
|
0:07:01
|
We look at that, sorry, Module 1 for CME, but
|
|
0:07:05
|
module 15, the first CME module, I should say.
|
|
0:07:09
|
Let me created that on an ephone template and
|
|
0:07:12
|
we look at an octo line, so busy trigger gives us
|
|
0:07:15
|
the ability to say, hey we´ve got 8 media channels
|
|
0:07:18
|
maybe it´s not a shared line, maybe it´s all reserved on one phone
|
|
0:07:22
|
but I only want 3 or 2 channels to have to be use
|
|
0:07:29
|
before the next call that comes in should automatically
|
|
0:07:33
|
trigger the call forward busy. OK?
|
|
0:07:39
|
And also we have something to go along with that
|
|
0:07:44
|
called maximum calls where we can say, hey there´s
|
|
0:07:48
|
8 media channels, but if only you know
|
|
0:07:53
|
4 are used maybe 2 is the busy trigger.
|
|
0:07:56
|
2 none idle channels should send the next call to busy
|
|
0:07:59
|
but there are 2 more available channels for media use for
|
|
0:08:02
|
outgoing reasons. 4 is the maximum we want to use
|
|
0:08:06
|
per phone or per button per phone. OK,
|
|
0:08:10
|
so those are only available with octo line, with dual line and
|
|
0:08:13
|
obviously the single line, they´re already limited.
|
|
0:08:17
|
Conferencing, we looked at this in the last deep dive.
|
|
0:08:21
|
Module 16, if we want an 8 party conference
|
|
0:08:26
|
we would actually have to have 4 ephone dns
|
|
0:08:29
|
that are dual lines, in order to create 8 meida channels.
|
|
0:08:33
|
or times 2 or we can do this with 1 octo line.
|
|
0:08:39
|
So it´s a lot more efficient and recommended.
|
|
0:08:42
|
FXO trunk optimization, we can do that in single and dual line.
|
|
0:08:46
|
That is basically a one for one mapping of
|
|
0:08:50
|
an FXO trunk to a ephone dn for use in really making
|
|
0:08:57
|
CME look a lot more like a small key system for maybe
|
|
0:09:02
|
serving. Not that it´s price, not that it´s a cost effective at this
|
|
0:09:07
|
model but you know for serving 20 or 30 phones
|
|
0:09:11
|
are something very small, we´re not looking at that
|
|
0:09:15
|
mainly because FXO ports and FXS aren´t on this
|
|
0:09:17
|
CCIE voice lab any longer. We don´t have any installed
|
|
0:09:21
|
but that´s the general theory behind that, hunt stop channel.
|
|
0:09:26
|
So if we´ve got a single channel then there´s nno reason to
|
|
0:09:29
|
hunt between channels, but the minute we have more than one channel.
|
|
0:09:33
|
We do have the ability to stop hunting between channels
|
|
0:09:38
|
or no hunt stop channel or don´t stop hunting between channels
|
|
0:09:43
|
another words allow the second call and third call and fourth call
|
|
0:09:47
|
to roll over to the next few media channels.
|
|
0:09:52
|
Intercom we´re going to look at today, only available
|
|
0:09:55
|
single line, there are a lot of features that are only available
|
|
0:09:57
|
in a single line. Key system such as FXO trunk optimization
|
|
0:10:01
|
only available with the single line.
|
|
0:10:05
|
We´re to look at maximum calls NWI we´ll look at that in messaging
|
|
0:10:09
|
overlays if we wish to have multiple dns
|
|
0:10:13
|
over top of one button, we can do this with
|
|
0:10:16
|
C which, O which is just overlay, C which is
|
|
0:10:20
|
call waiting enabled overlay for dual line purpose
|
|
0:10:24
|
or single line and X which is extension.
|
|
0:10:29
|
So we can actually have extended overlays
|
|
0:10:32
|
this is a concept that is not present in CUCM.
|
|
0:10:36
|
In the big CUCM, we only have the ability to have
|
|
0:10:40
|
one dn per line button, in fact we can even have a secondary number.
|
|
0:10:45
|
In CME, we can have a single ephone dn which is either
|
|
0:10:49
|
a single line or a dual line or an octo line
|
|
0:10:51
|
that has a primary and secondary number.
|
|
0:10:54
|
So 2 different numbers and then as long as it´s a single or
|
|
0:10:57
|
dual line, not an octo line, then we can actually
|
|
0:11:01
|
overlay those directory numbers on top of
|
|
0:11:06
|
a single button, so we can have up to ten
|
|
0:11:08
|
actually may have extended it up to 20, I haven´t tested that, but
|
|
0:11:11
|
it used to be tp to ten separate ephone dns.
|
|
0:11:15
|
Each with possibly a primary and secondary
|
|
0:11:19
|
number overlayed on a single button. Now
|
|
0:11:22
|
that´s not available with octo line and the reason overlay
|
|
0:11:28
|
along with hunt stop channel and no hunt stop
|
|
0:11:32
|
channel were 2 things that we used to use
|
|
0:11:37
|
when we had and also shared lines all 3 of those combined together
|
|
0:11:42
|
to create a little bit of a confusing probably don´t need to go over it
|
|
0:11:45
|
because it´s a little confusing now and because we have an alternative
|
|
0:11:49
|
but a little bit of a confusing and work around
|
|
0:11:55
|
way to allow multiple calls in to a single
|
|
0:11:59
|
phone line or at least a single phone line button
|
|
0:12:01
|
on multiple shared phones for use in things like receptionist.
|
|
0:12:07
|
You know reception type situations.
|
|
0:12:12
|
And today we have octo line which really eliminate
|
|
0:12:16
|
the need for all that because multiple phones can
|
|
0:12:19
|
call waiting and share the media channels and they´re not reserved.
|
|
0:12:23
|
So we don´t need overlay there, paging we look at
|
|
0:12:26
|
last module, single line only, park. We´ll look at today
|
|
0:12:30
|
single line only and privacy deals with shared line
|
|
0:12:33
|
and privacy and barge go together, and those again are only available
|
|
0:12:37
|
for the reason I mentioned earlier with shared lines on an octo line.
|
|
0:12:45
|
Looking at the difference between barge and Cbarge
|
|
0:12:49
|
for built in and shared conference bridging.
|
|
0:12:52
|
Now we look a little bit at this, pretty much this exact
|
|
0:12:57
|
and I realized the print here maybe a little small.
|
|
0:13:00
|
It´s in the admin guide under barge
|
|
0:13:03
|
so you can certainly look at it there, you can pull it up, but
|
|
0:13:06
|
we look at this a little bit in the CME, I´m sorry in the
|
|
0:13:10
|
call manager module for call features.
|
|
0:13:15
|
When we look at shared lines between skinny and SIP phones there
|
|
0:13:19
|
with CME version 7.0.1
|
|
0:13:26
|
which is the version that´s in the lab. We really don´t have
|
|
0:13:30
|
the concept too much, we´ll look at it a little bit today
|
|
0:13:34
|
of shared lines with SIP phones. In fact
|
|
0:13:37
|
there really is no technical support for shared line with SIP
|
|
0:13:41
|
phones in 7.0.1. Now as soon as CME 7.1 came out
|
|
0:13:48
|
a lot of new features became available and
|
|
0:13:52
|
shared line is supported there and that would be under
|
|
0:13:57
|
12.4.24t is when CME 7.1 emerged.
|
|
0:14:04
|
But again that´s not the version in the lab
|
|
0:14:06
|
so we´re not going to look in to those features today.
|
|
0:14:09
|
We will look at a kind of a version of a shared line with SIP phones
|
|
0:14:14
|
and when we get in to 7.1 and shared lines.
|
|
0:14:20
|
That´s when built in conference bridging
|
|
0:14:25
|
for barge becomes available for SIP phones, but
|
|
0:14:30
|
when we´re just looking at skinny phones which is the only
|
|
0:14:32
|
technical support for shared lines with 7.0.1 CME,
|
|
0:14:37
|
then the only thing we have available for skinny phone
|
|
0:14:40
|
first of all is for skinny phones and second is the use of Cbarge.
|
|
0:14:45
|
So some of the differences when we barge with a built in
|
|
0:14:49
|
conference, there´s no media break.
|
|
0:14:52
|
The user does receive a barge tone if it´s configured.
|
|
0:14:57
|
We display the name to barge at the initiator´s phone
|
|
0:15:03
|
but the target phone, the person that was barge in to
|
|
0:15:07
|
just shows standard to from, so they kind of
|
|
0:15:11
|
unless there´s a barge tone configured because there´s
|
|
0:15:15
|
no media break and because they still show their standard
|
|
0:15:18
|
to and from, you know whomever they´re talking to.
|
|
0:15:22
|
Both the target phone and the other phones
|
|
0:15:25
|
really don´t necessarily know that
|
|
0:15:29
|
they´ve been barge in to and if the initiator of the barge
|
|
0:15:34
|
in to the bargee releases that call, there´s no media interruption.
|
|
0:15:43
|
So really a barge with a built in conference bridge can be
|
|
0:15:50
|
very non discreet or sorry very discreet,
|
|
0:15:55
|
very silence, you wouldn´t necessarily know that you´ve been
|
|
0:15:59
|
barge in to unless there´s barge tone configured.
|
|
0:16:02
|
With conference barge, we are allowing obviously a lot more
|
|
0:16:06
|
participants because we have a hardware conference bridge that we´re
|
|
0:16:10
|
taking hold of and there is a media break because everyone has
|
|
0:16:15
|
to stop their RTP stream, now it´s almost seamless
|
|
0:16:18
|
but there is a media break, it does pull in the hardware conference bridge
|
|
0:16:22
|
and if the hardware conference bridge, like we had configured.
|
|
0:16:26
|
In the last deep dive module has conference leave and join tone.
|
|
0:16:31
|
Then they´re certainly going to hear those
|
|
0:16:33
|
as well as any barge tone has configured.
|
|
0:16:36
|
The display on all 3 phones, at least the target phone
|
|
0:16:42
|
if being another skinny phone, the other phone
|
|
0:16:45
|
the third party phone would show it if it was a skinny phone
|
|
0:16:48
|
or even if it was an IP phone, I should say.
|
|
0:16:52
|
But if it´s an off system PSTN phone obviously they´re not
|
|
0:16:56
|
going to see any display but they would still hear the tone.
|
|
0:17:01
|
It allows other people to barge in and already barge call.
|
|
0:17:06
|
Of course that´s also available with a built in conference bridge
|
|
0:17:09
|
provided there´s enough resources on the built in conference bridge.
|
|
0:17:16
|
The maximum number of parties is determined by the
|
|
0:17:20
|
conference resource or the built in can only have a maxmum of 3.
|
|
0:17:26
|
And of course there´s a media break when you hang up
|
|
0:17:28
|
as well, so it´s very noticeable when you barge in to a
|
|
0:17:33
|
shared conference bridge or a Cbarge, the hardware conference bridge.
|
|
0:17:40
|
OK, looking at some of the useful show command we look at some
|
|
0:17:43
|
of these yesterday or the last deep dive, few days ago actually.
|
|
0:17:52
|
We look at show voice call, show call active voice compact
|
|
0:17:55
|
Show call active voice type 2 include peer or peer ID
|
|
0:18:00
|
Debug CC SIP, we didn´t really pull up the debug.
|
|
0:18:06
|
In fact we we´re going to do that first thing today, the debug for
|
|
0:18:09
|
transcoding, troubleshooting, X code, MSP or media stream provider
|
|
0:18:14
|
and another one we didn´t look at, we´ll look at today
|
|
0:18:17
|
is debug VOIP conference MSP or conference media stream provider
|
|
0:18:23
|
And also did´t look at, we talked about, but didn´t look at
|
|
0:18:25
|
the output of, we will that today. Debug VOIP
|
|
0:18:29
|
dspapi inout, so debug for voice over IP.
|
|
0:18:34
|
The dsp, the digital signal processor
|
|
0:18:37
|
api, the application programming interface
|
|
0:18:40
|
and both inbound and outbound messages, this can be useful
|
|
0:18:43
|
for a lot of things including codec mismatch or
|
|
0:18:47
|
RTPNTE, pay low type mismatch, all sorts of things.
|
|
0:18:53
|
We look a lot at the show dsp farm units and session summary
|
|
0:18:59
|
and another thing we´ll look at is show ephone dn
|
|
0:19:01
|
conference, show ephone dn park, show ephone dn
|
|
0:19:05
|
call back, there´s a lot of show ephone and show ephone dn
|
|
0:19:08
|
specifics that we can look at.
|
|
0:19:11
|
|
