Hi. I'm a junior video engineer of South Korea.
I am facing some issue of cascading 2 MCU without Conductor.
I have two models, One is MCU 4510 and other is MCU 5310
I would like to cascade these 2 MCU work as 1, I know it consumes 2 media port. It could be adoptable.
As the guide of cascading which is expired on last year, I configured with 2 MCUs but, there is something wrong about it.
1. On Setting up MCU 1, the conference named 333. and
On Setting up the conference, It is written making the conference named 333 again.
I cannot make the conference name 333 duplicated on same MCU, how to solve this issue?
2. I think that it could be a mistake, so I change the numbers of Setting up the conference named 111.
and then, it shows auto attendant view when the Master MCU calls to Slave MCU.
How can I solve this issue? I need experts mercy and advices.
Thank you.
reference below
originally from : https://supportforums.cisco.com/docs/DOC-25617
Setting up MCU 1
- On your first MCU (called MCU1 in this article), go to Endpoints.
- Click Add H.323.
- Complete the fields as follows:
- For Name, enter MCU2
- For Call-out parameters and Call-in match parameters, enter the IP address of MCU2
- For Default family view, select one participant, full screen
Note: This is the view that participants connecting directly to MCU1 will see. This setting is important because it ensures that MCU2 sends only one participant at a time to MCU1 when the cascade is active.
- For Display name override, enter a single space. This precents the MCU from overwriting the participant names along the cascade link, allowing you to see the name of participants on MCU2
- Click Add endpoint
- Go to Conference > Add new conference.
- For Name, enter a name for your conference.
- For Numeric ID, enter a numerical ID for your conference (in this article, 333).
- Select the Permanent checkbox.
- Click Add conference. You are returned to the Conference list.
- Select the new conference and click the Participants tab.
- Add the participants who will be connected directly to MCU1 (for more information about this, see the online help).
Setting up MCU 2
The steps below set up a gateway so that the MCUs can communicate directly and then bring MCU1 into the conference. (The gateway only needs to be set up once and will be used every time this conference occurs).
- On your second MCU (called MCU2 in this article), go to Gateways.
- Click Add new H.323 gateway.
- Complete the fields as follows:
- For Name, type MCU1
- ForAddress, type the IP address of MCU1
- If required, limit the bandwidth that will be used to call between the two MCUs
- For Display name override, enter a single space. This prevents the MCU from overwriting the participant names along the cascade link allowing you to see the names of participants on MCU1
- Click Add H.323 gateway.
- Go to Endpoints and click Add H.323.
- Complete the fields as follows:
- For Name, enter Cascade to MCU1 conference 333
- For Call-out address, enter 333
- For H.323 gateway, enter MCU1
- For Default family view, select one participant, full screen
- For Automatic disconnection, select Enabled. This means that the cascade is automatically disconnected at the end of the conference
- Click Add endpoint.
Setting up the conference
To set up the conference on MCU1:
- Go to Conferences and click Add new conference.
- For Name, enter a name for your conference.
- For Numeric ID, enter the Numeric ID defined about (in this example this is 333).
- Make sure that the Numeric ID registration checkbox is not selected.
- Select Permanent.
- For Invite pre-configured participants, select When at least one other participant is present.
- Click Pre-configured participants.
- Select H.323: Cascade to MCU1 conference 333.
- Select any other pre-configured participants you want to join the conference.
- Click Return to conference configuration.
- Click Add conference. You are returned to the Conference list.
- Select the new conference and click the Participants tab.
- Add the participants who will be connected directly to this MCU.
