H.323 considerations when using survivable core server

Last Updated : Nov 13, 2025 |

Because H.323 trunk usage can exhaust memory pool and can prevent H.323 stations from registering, Communication Manager 6.0 and later provides a way to control where H.323 trunks are used. When the Group Type field is h.323 and Near-end Node Name is procr on the Signaling Group screen, an additional page, Limit Signaling Group Usage, is added to allow control of H.323 trunk usage.


change signaling-group 3                                        Page   2 of   6
                        LIMIT SIGNALING GROUP USAGE
                        Enable on the main Processor(s)? y
          Enable on Survivable Processors (ESS and LSP): selected
                            Selected Survivable Processor Node Names
                             1:
                             2:
                             3:
                             4:
                             5:
                             6:
                             7:
                             8:

To allow usage of H.323 trunks only on the main server, set Enable on the main Processor(s) to y.

To specify usage of H.323 trunks on survivable core and remote servers, set Enable on Survivable Processors (ESS and LSP) to all, ess-all, none, or selected as per your network requirements. The Selected Survivable Processor Node Name field appears only if you enter selected in the Enable on Survivable Processors (ESS and LSP) field.

For more information about these fields, refer to Avaya Aura® Communication Manager Screen Reference document.