Application relay configuration for RTCP monitoring

Last Updated : Apr 25, 2023 |

You must configure two relay services to send the RTCP MON traffic to the prognosis server.

  • Relay 1: For RTCP MON traffic coming from DMZ Avaya SBC and Core Phones. RTCP MON traffic is received on Core SBC-1 public IP-A and is sent out to the prognosis server using Core SBC-1 private IP-A.

  • Relay 2: For traffic coming from Media Gateway. RTCP MON traffic is received on core SBC-1 private IP-A and is sent out to the prognosis server using Core SBC-1 private IP-B.

46xx settings file configuration for RTCP monitoring

You must add the following parameters in the 46XX settings file for Remote SBC and Core SBC phone groups:

  • SET RTCPCONT 1

  • SET RTCPMON 192.168.11.105 {SBC Relay IP towards Phone}

  • SET RTCPMONPORT “5005"

  • SET RTCPMONPERIOD 5

Communication Manager/Media Gateway configuration for RTCP monitoring

You must provision the RTCP Monitor IP address with the Core Avaya SBC internal signaling IP address on the System Parameter ip-options page.

  • RTCP Monitor Server IP: Core Avaya SBC Internal Signaling IP

  • Server Port: 5005

In back-to-back Avaya SBC deployment, calls go through the remote Avaya SBC, DMZ Avaya SBC, and Core Avaya SBC.

Therefore, you must configure application relay RTCP monitoring in:

  • Core Avaya SBC

  • Remote Avaya SBC

  • Remote user deployment

    A regular remote user deployment can have one Avaya SBC with or without high availability. The steps for configuring application relay for RTCP monitoring in remote Avaya SBC deployment are the same as the configuration steps for Core Avaya SBC.