|
0:00:11
|
So, first of all, some of the features for calling features are things like Call Park, Call Pick Up, Barge, and Whispering Intercom.
|
|
0:00:26
|
So for Call Park, a few things to keep in mind, is that you cannot park the same DN or range of DNs on two separate CUCM Call Processing Engines.
|
|
0:00:40
|
Well, let's revise that you should not park the same DN or range DN's on two separate CPEs.
|
|
0:00:47
|
You actually can do it by creating the same pattern but on different RegEx formats or Regular Expression formats.
|
|
0:00:56
|
And then we should distinguish that Call Park is not the same as Directed Call Park.
|
|
0:01:01
|
With Directed Call Park, it doesn't matter how you format them.
|
|
0:01:06
|
They automatically are available on both servers or all the subscriber servers in your production cluster.
|
|
0:01:16
|
Directed Call Park does not decipher between CUCM or CPEs.
|
|
0:01:23
|
So we'll take a look at that. Looking at Call Pickup,
|
|
0:01:28
|
With Call Pickup, obviously the idea is that the phone is ringing and we want the ability to pick a ringing call on another phone.
|
|
0:01:37
|
So with Group Pickup, we have th ability to pick up a ringing call in another group.
|
|
0:01:43
|
It still picks up the first ringing phone in another specifically dialled group number, but we have to dial the group number.
|
|
0:01:52
|
And whichever phone was ringing first if multiple phones are ringing in that other group that we dial, the first phone will be picked up.
|
|
0:02:00
|
Other Call Pickups allow us to pick up a ringing call in the same or another group.
|
|
0:02:08
|
It happens by association and preference. So we set up groups.
|
|
0:02:19
|
Basically, we'll go and pickup the first ringing phone in our group
|
|
0:02:25
|
or it will pickup the first ringing phone in any other group whichever phone has been ringing first.
|
|
0:02:36
|
So if there's a phone ringing in our group, and we will pick that one up.
|
|
0:02:39
|
If there's a phone ringing in group 2 and 3, and we have group 2 and 3 associated with our group 1,
|
|
0:02:47
|
but group 2 is a little bit higher, then we will pick up the phone in group 2 first.
|
|
0:02:52
|
And the there is Directed Call Pickup where the user is able to dial a specific DN that thay know or wish to pickup.
|
|
0:03:01
|
This typically works best with BLF Speed Dials where we've also indicated the call pickup checkbox
|
|
0:03:10
|
which shows us on the BLF a rapid flash when that phone is ringing.
|
|
0:03:16
|
and then we press Directed Call Pickup and press the BLF Speed Dial of the rapidly flashing DN.
|
|
0:03:24
|
And that directs us to be able to pickup that DN.
|
|
0:03:27
|
Now, in order to be able to do that we still have to either be in the same group or associated to that group
|
|
0:03:35
|
where that DN lives, however, it doesn't have to be the first ringing call.
|
|
0:03:42
|
or there could be other phones or DNs ringing in any of our associated groups in any order
|
|
0:03:51
|
and it doesn't matter about the preference or about the first ringing call.
|
|
0:03:57
|
So, with Barge and cBarge, we're really dealing with shared lines here.
|
|
0:04:02
|
And anytime we have two DNs in the same partition, and applied to different devices.
|
|
0:04:11
|
So we have the same DN, the same line essentially.
|
|
0:04:15
|
Actually it's two separate lines, the Line 1, Line 2 or whatever but it happens to appear on.
|
|
0:04:22
|
Let's say Line 2 on device Bravo-Echo-Echo-Alpha or Bravo-Alpha-Alpha-Echo.
|
|
0:04:29
|
We'll take this one of our Mac addresses. And then we've got Line 3 on device 5673, whatever are the Mac addresses.
|
|
0:04:39
|
And it doesn't matter that there are different line numbers.
|
|
0:04:41
|
It matters that there are the same DN and the same partition on two separate devices
|
|
0:04:47
|
or appearing as a line on two separate devices and that's what defines a shared line.
|
|
0:04:51
|
When that happens, we have the ability to Barge or conference Barge, cBarge in to a shared line.
|
|
0:05:01
|
If we're set up with the proper permissions.
|
|
0:05:05
|
So, Barge to differentiate it from cBarge, Barge relies on a built in bridge on the target phone.
|
|
0:05:13
|
So, if I'm on phone Headquarter Phone 1, and I'm trying to Barge into a call on Branch 1 Phone 1,
|
|
0:05:25
|
Branch 1 Phone 1 is the target phone. So If I want to Barge versus cBarge,
|
|
0:05:32
|
if I want to Barge, then Branch 1 Phone 1 being the target phone
|
|
0:05:36
|
has to have the value of built in bridge configured and enabled on that phone device page.
|
|
0:05:46
|
And phone has to have the configuraiton so it had to be reset or restarted.
|
|
0:05:51
|
And what this does is that it effectively enables the built-in DSP on the target phone
|
|
0:05:58
|
to act as a mixing channel for the RTP streams.
|
|
0:06:07
|
It does have some limitations, but it also some benefits.
|
|
0:06:14
|
One of the benefits is, there is no cut in the RTP stream.
|
|
0:06:18
|
When I mix it in, I just automatically add in the DSP that is already being used.
|
|
0:06:23
|
So I just add in another channel.
|
|
0:06:25
|
Whereas with cBarge, conference Barge, I'm actually calling in to play and actual hardware conference bridge.
|
|
0:06:33
|
And if I'm calling in to play a hardware conference bridge,
|
|
0:06:37
|
then what I need to do is cut the RTP stream for the original conversation.
|
|
0:06:43
|
So I'm the Barger, I'm the third party, the one that really wasn't welcomed in to the conversation necessarily.
|
|
0:06:50
|
But I'm Barging in.
|
|
0:06:52
|
And so the original conversation, let's say on Branch 1 Phone 1 talking to the PSTN.
|
|
0:07:01
|
That RTP string is going to be cut and those two streams
|
|
0:07:07
|
from the PSTN and from Branch 1 Phone 1 are going to be mixed in to a hardware conference bridge.
|
|
0:07:13
|
As will my Headquarter Phone 1 RTP stream also be mixed in through that, whatever chosen conference bridge
|
|
0:07:22
|
So that's one of the downsides to it.
|
|
0:07:34
|
cBarge can use a software conference bridge on the CUCM servers
|
|
0:07:39
|
but just keep in mind that those conference bridges,
|
|
0:07:42
|
out on the fact that we disabled their runflags in the IP voice media streaming service parameters.
|
|
0:07:48
|
Keep in mind that they can only speak and mix the G711 Codex.
|
|
0:07:58
|
And if we want to get the Join button to work,
|
|
0:08:01
|
that is maybe I have already got a conference going up
|
|
0:08:07
|
and I now want to Join in another party, a fourth person,
|
|
0:08:12
|
then I need to use certain service parameters to get that Join to work.
|
|
0:08:20
|
Also, one thing to keep in mind when we deal with Barge or cBarge,
|
|
0:08:26
|
is that I have the ability to do something called Single-button Barge.
|
|
0:08:31
|
And I can enable this on the phone or on the device pool.
|
|
0:08:35
|
If I enable on a given phone, single-button Barge or single-button cBarge,
|
|
0:08:44
|
I actually choose from the drop-down which of the two I want to be utilized for the single button feature.
|
|
0:08:53
|
One of the things is, is that when the phone if the phone ever falls back in to SRST mode,
|
|
0:09:00
|
either traditional SRST or CME SRST,
|
|
0:09:04
|
the Single-button Barge functionality or Single-button cBarge, either one,
|
|
0:09:10
|
will prevent Barge or cBarge from ever working.
|
|
0:09:14
|
There's further limitations, neither Barge nor cBarge works in traditional SRST.
|
|
0:09:24
|
And only cBarge works for anything and it's in CME as SRST.
|
|
0:09:32
|
So in standard CUCM, registered, everything's fine, configuration and registration, no problem.
|
|
0:09:41
|
I can use Barge. I can use cBarge. I can use Single-button Barge or Single-button cBarge.
|
|
0:09:48
|
Fallback to tradional SRST, that's the Call-Dash-Manager-Fallback command in IOS.
|
|
0:09:56
|
Actually none of the four: Barge, cBarge, Single-button Barge or single-button cBarge.
|
|
0:10:02
|
None of those will work. If I fall back to CME as SRST,
|
|
0:10:08
|
So that's the Telephony Services Configuration.
|
|
0:10:11
|
that we'll talk about later. We talk about Unified CM Express.
|
|
0:10:15
|
If I'm in telephony service but in SRST mode,
|
|
0:10:23
|
then Barge will not work, Single-button Barge will not work,
|
|
0:10:30
|
Single-button cBarge will not work.
|
|
0:10:33
|
The only thing thta will work is traditional cBarge.
|
|
0:10:37
|
So traditional hardware-based conference bridge
|
|
0:10:39
|
and of course if I had a hardware conference bridge on the same IOS router,
|
|
0:10:45
|
As my telephony service is CME,
|
|
0:10:50
|
and I had that hardware conference bridge originally registered to CUCM.
|
|
0:10:57
|
I would need to also have it set to fallback to CME
|
|
0:11:02
|
and have it configured under telephony services as well.
|
|
0:11:05
|
And as long as it did, and as long as under telephoy services,
|
|
0:11:08
|
I had configured a conference for hardware.
|
|
0:11:13
|
And I had my hardware conference ePhone DN set up.
|
|
0:11:16
|
Then I would be able to use four shared skinny lines.
|
|
0:11:21
|
To phones that will fallback to the same CME as SRST, I would be able to use cBarge
|
|
0:11:29
|
But only traditional, not Single-button.
|
|
0:11:31
|
And we'll actually look at that demonstration when we come to our Unified CMExpress module.
|
|
0:11:46
|
And the last thing, very easy, is Whisper Intercom.
|
|
0:11:51
|
This is an auto-answer via speakerphone functionality.
|
|
0:11:56
|
If there are no calls present on the phone,
|
|
0:11:59
|
the target phone gets a receive-only streaming moxing,
|
|
0:12:03
|
if there is a live call present at Intercom times.
|
|
0:12:06
|
So in other words, If I am trying to do Whisper Intercom over the Branch 1 Phone 1,
|
|
0:12:12
|
but they are talking to PSTN phone or even talking to another IP phone.
|
|
0:12:16
|
If I do a Whisper Intercom over them, they'll hear my voice in their ear
|
|
0:12:21
|
in the receive stream but they will not cross over into the transmit stream.
|
|
0:12:25
|
So the person, the third party, the Branch 1 Phone 1 was talking to, they will not hear anything.
|
|
0:12:31
|
That's just the function of how it works.
|
|
0:12:34
|
There's nothing you need to do to get that to work.
|
|
0:12:37
|
Also, if they were idle, then it would auto-interview a speaker phone but with mute pressed.
|
|
0:12:45
|
And pressing mute doesn't actually undo it. I have actually have to press the line button
|
|
0:12:51
|
that is used for my Intercom to be able to speak back
|
|
0:12:54
|
if I want a two-way communcation. Otherwise, it's a one-way communication.
|
|
0:13:00
|
And I can't have any Intercom speed dial associated with the Intercom line, however I don't have to.
|
|
0:13:05
|
The other phone, the phone that I'm trying to Intercom over to,
|
|
0:13:09
|
but they must have an Intercom line in order to be able to call them.
|
|
0:13:12
|
So, both phones have to have an Intercom line.
|
|
0:13:16
|
You cannot place a call from a traditional DN over to an Intercom DN. They are separate.
|
|
0:13:24
|
Looking at just a few calling features with phone and line settings,
|
|
0:13:30
|
We already mentioned this about the line and phone.
|
|
0:13:33
|
Line always takes highest precedence, first priority.
|
|
0:13:36
|
The device takes the next highest second priority.
|
|
0:13:39
|
Device pool takes the third.
|
|
0:13:41
|
And service parameter takes the lowest or fourth priority.
|
|
0:13:45
|
Also dealing with Call Forward Settings,
|
|
0:13:48
|
If I have Do Not Disturb turned on on my device,
|
|
0:13:53
|
either administratively from the admin phone page or if I have a DND Line button keyor soft key, sorry.
|
|
0:14:03
|
Either one, I can enable it and DND always triggers call forward busy
|
|
0:14:13
|
whenever the voice mail or a specific DN whichever is configured.
|
|
0:14:18
|
So, DND, Do Not Disturb, triggers a call for a busy if I've got DND set to call reject.
|
|
0:14:28
|
Now, the DND from the Phone Admin page can be set to either disable ringer or reject the call.
|
|
0:14:38
|
If it's just set to disable ringer, which is the default, then pressing DND just basically silences the ringer
|
|
0:14:45
|
and then it will set there and ring but you won't hear it.
|
|
0:14:49
|
And it will finally go to your call forward no setting timeout and it will go to that setting.
|
|
0:14:55
|
But if I have it set it to call reject,
|
|
0:14:58
|
then as soon as I press the DND rejecting the call, and then it will go to my call forward busy settings.
|
|
0:15:06
|
Now, if a call's coming in as I press DND, then I'm rejecting it live
|
|
0:15:13
|
and it won't follow the call for busy settings because I'm rejecting kind of live.
|
|
0:15:19
|
If I already had the call for DND set, before the next call came in,
|
|
0:15:26
|
and I already had the behavior set to call reject before the next call came in.
|
|
0:15:33
|
Then it would fall in my call for basic setting.
|
|
0:15:36
|
iDivert will always send the call to my Pilot Point of the Line, my voice mail pilot
|
|
0:15:47
|
of the line based on my assigned voice mail of the profile.
|
|
0:15:51
|
So, no matter what I do, I can always hit iDivert and send them to voice mail
|
|
0:15:58
|
as the calls ringing in live but DND will forward to call busy.
|
