Configure Polycom MGC Video Conferencing Bridge Platforms with Avaya S8500 and S87xx Server

Example 3: S87xx with 2 CLANs/MGC-50 with 3 boards, board redundancy, and CLAN redundancy

In this example, CLAN1 is chosen as the primary CLAN for the Polycom MGC system to use, and CLAN2 is a backup. CLAN2 provides backup to CLAN1 for Polycom MGC registration and incoming and outgoing calls. If Polycom MGC board IP1 fails, IP2 and IP3 will continue to be able to make incoming and outgoing calls.

Note that the incoming signaling groups for CLAN2 will be out-of-service unless the Polycom MGC boards are forced to register with CLAN2 in the event that CLAN1 is unavailable.

Trunk 1: MGC-A Incoming:

SigGroup 1: CLAN1, IP1; 31 trunk members

SigGroup 2: CLAN1, IP2; 31 trunk members

SigGroup 3: CLAN1, IP3; 31 trunk members

SigGroup 4: CLAN2, IP1; 31 trunk members

SigGroup 5: CLAN2, IP2; 31 trunk members

SigGroup 6: CLAN2, IP3; 31 trunk members

Trunk 2: MGC-A Outgoing Primary:

SigGroup 7: CLAN1, IP1; 31 trunk members

SigGroup 8: CLAN2, IP1; 31 trunk members

Trunk 3: MGC-A Outgoing Secondary:

SigGroup 9: CLAN1, IP2; 31 trunk members

SigGroup 10: CLAN2, IP2; 31 trunk members

SigGroup 11: CLAN1, IP3; 31 trunk members

SigGroup 12: CLAN2, IP3; 31 trunk members

Issue 3 January 2008 87

Page 87
Image 87
Avaya 16-601423 manual Trunk 1 MGC-A Incoming