For SIP deployments, you must create the Internal (toward Call Server) and External (toward Trunk Server) signaling interfaces and media interfaces. You must create and define the signaling interfaces and media interfaces by navigating to Network & Flows > Signaling Interface and Network & Flows > Media Interface.
Note:
The fixed ports for TCP, UDP, or TLS defined under Network & Flows > Signaling Interface must not be assigned a port number that falls within a Signaling Port range. A fixed port for TCP, UDP, or TLS is a shared Listen Port for multiple calls incoming to Avaya SBC from a Trunk Server or Call Server.
Name
Description
Signaling Port Range
(Direction = Away from Avaya SBC) This port range is used by Avaya SBC to start connections for outgoing SIP requests from Avaya SBC towards a SIP Server (Call Server or Trunk Server).
Config Proxy Internal Signaling Port Range
(Direction = Away from Avaya SBC) This port range is used by Avaya SBC to start connections from Avaya SBC toward Configuration Servers. For example, configuration servers of the following types: HTTP, HTTP Proxy, HTTPS, LDAP, TFTP, and SCEP.
Listen Port Range
(Direction = Toward Avaya SBC) This port range is used in PORTID Mode, see Managing SIP Server Configurations. Avaya SBC listens on these ports for requests from a SIP Server (usually a Call Server) during nonpersistent, phone-related communications, for example, calls and signaling, where a link does not stay up indefinitely.
HTTP Port Range
(Direction = Away from Avaya SBC) This port range is used by Tinyproxy to start connections for Avaya SBC towards the upstream server or any other http server based on the routing for nonpersistent, nonphone-related communications (e.g., web services, media) where a link does not stay up indefinitely.
