×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

move participant from an MCU 5320 to another MCU 5320

Unanswered Question
Oct 16th, 2013
User Badges:

Does anyone know if it is possible at the API interface on an MCU 5320 to move the video participant from an MCU 5320 to another MCU 5320


We experience sometimes that there is no free ports on an MCU to expand an ongoing video conferencing and would therefore like to move the entire video conference over to another 5320 MCU that has free ports


Sincerely,


Jesper

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Martin Koch Wed, 10/16/2013 - 16:22
User Badges:
  • Red, 2250 points or more

I think I have not seen any "transfer" option in the Codian API, but check out the documentation section for

your MCU, the API calls are described.


Besides that, sure, you can identify a conference, disconnect all on the old, generate a new conference,

dial out to the known participants and there you go.


Inbound calls can become an issue depnding how you have configured dial ins and it definitly does not mix

with TMS or conductor as they need to have full control.


Some endpoint versions also have the capability of a unattended call transfer, but this would require API access to

all the endpoints.


Also cascading the conference to an other one can be a possibility.



Besides that you might want to look into the usage of the conductor, clustering your MCUs, use the TPS,

use TMS, ... to improve your resource allocation.



Please remember to rate helpful responses and identify helpful or correct answers.

Gaurav Pathak Fri, 10/18/2013 - 00:44
User Badges:

Hi Jesper,


Cascading of conference is not supported in 5300 series MCUs. You would require Cisco Conductor to achieve this functionality. To increase ports availibility in case of all ports utilized and no room left for new conference, you can go for stacking of both MCUs or


Create same service prefix for both MCUs for eg: 30 and put both MCUs in different subzones (lets says subzone 1 and subzone 2) in VCS. Create search rule with higher priority (eg: 40)  to route calls first to Subzone 1 (i.e to your first MCU) and second search rule with lower priority (eg: 45) to route calls to Subzone 2 when someone dials 30XXXX. By this call will be automatically will land to second MCU in case all ports of first MCU are utilized. Hope this info helps.


Regards,

Gaurav

Actions

This Discussion