C20 "IncomingMultisiteCall Mode" Setting

[mayank.sharma]

Hi,

My C20 is running TC5.1.6.298375

I wanted to understand how this "IncomingMultisiteCall Mode" Setting works... It is described as in the manual as...

Conference [1] IncomingMultisiteCall Mode

Set the incoming MultiSite call mode. The MultiSite feature allows participants from more than two

locations to join a meeting — by video and/or telephone.

Requires user role: ADMIN

Value space: <Allow/Deny>

Allow: Accept incoming calls to an already active call/conference. The incoming call will be added

to the MCU conference.

Deny: The system will not accept incoming calls when you are in a call. The calling side will

receive a busy signal.

How is this different to Multipoint Mode?

Basically we did some testing with this "IncomingMultisiteCall Mode". Note: I do not have multiway URI configured on this Endpoint and the Multipoint Mode on the endpoint is set to Auto.

With this setting "IncomingMultisiteCall Mode" set to "Allow", when this C20 is in call (Audio/Video) with another endpoint (Cisco MOVI) and I ring it with another endpoint (Cisco IP Phone 7961)  I get a option to merge the calls and I am able to merge the calls successfully in a 3 party conference (2 Video participants & 1 Audio Participant)

My Question is which device is acting as a bridge for the 3 party conference as I do not have multiway configured? Is it the C20 itself acting as the bridge? using the  "One additional telephone call" which was added in TC4.0.0.

With this setting "IncomingMultisiteCall Mode" set to "Deny", when this C20 is in call (Audio/Video) with another endpoint (Cisco MOVI) and I ring it with another endpoint (Cisco IP Phone 7961) I just get a get silence on the Cisco IP Phone. There is also no indication of a incoming call on the C20 at all.  

Regards,

Mayank      

[Teck Chye Tang]

hi,

You are right.  However, the C20 unit does not actually support a multi party video call.  The system is design to support a point to point video call plus a audio call add on.

If a multiparty video call is required or you need to connect more audio participants, we will need to use an external MCU.

for the incomingmultisite call mode setting, when is it set to deny, no other incoming call can comes in once you are already in a call, this is introduce in TC5.x releasse as some customer wants to have this option to prevent any disturbance when they are already in a call.

Regards,

[mayank.sharma]

Hi Teck,

Thanks for the response.

Please see my questions in regards to your response.

"You are right. However, the C20 unit does not actually support a multi party video call. The system is design to support a point to point video call plus a audio call add on"

When the C20 does a point to point video call with another participant plus a audio call add on, then there total 3 parties in a call. Is this 3 party conference hosted on the C20 itself? or is Multiway (MCU) used for this?

Basically what I want to understand is "Is Multiway required to be configured for all calls with 3 parties or is the C20 able to host the 3 party conference (i.e. a point to point video call plus a audio call add on) on its own without Multiway

Regards,

Mayank

[Teck Chye Tang]

hi,

To answer your specific  question, yes it is hosted on the C20 itself.  No multiway required.

[mayank.sharma]

Hi Teck,

Thanks for your prompt response.

What if Multiway is configured on the endpoint... will the C20 still host the conference or will it send it off to the MCU via the Multiway feature?

Also I guess this "plus a audio call add on" applies to both inbound call to the C20 as well as outbound call from the C20. Am I correct?

Regards,

Mayank

[Teck Chye Tang · Accepted solution]

hi,

If multiway is configure, any multisite conference will be escalated to the external MCU.  The codec will not be able to suppor the add on audio internally anymore.

Yes, both inbond and outbound.

[mayank.sharma]

Thanks Tang.

The issue was that Multiway was not working correctly and hence the codec was not able to hand off the call tot he MCU.

Now its been fixed and is working as expected.

Thanks for your prompt responses.

Regards,

Mayank