Versions Compared

Old Version 7

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 8

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH2sbsarkar
AUTH1bgoswami
JIRAIDAUTHSBX-60957
REV5bscoggins
REV6bscoggins
JIRAIDAPPR2SBX-60959
REV3avalente
JIRAIDAPPRSBX-60958
REV1sgardell

Panel

In this section:

Table of Contents
maxLevel4

The

Spacevars
0series4
  platforms (SBC 5000 series, SBC 7000, SBC SWe) listen to the TCP/IP network ports listed in the following tables. Some of these ports will not be open if the corresponding product features are not configured.

Info
titleNote

The actual ports that the

Spacevars
0product
listens to depends on the actual system configuration.

Warning
titleWarning

Due to an IPMI vulnerability, Sonus recommends not connecting the BMC Ethernet port to an external network unless the network is deemed well-protected.

[Reference: NIST National Vulnerability Database website]

Multiexcerpt
MultiExcerptNameME1

SBC 5000/7000 Series BMC Ports

Caption
0Table
1SBC 5000/7000 Series BMC Ports
Protocol

Network Port

Application Level ProtocolProcess Using the Ports

Usage

Notes
TCP22SSHSSHDBMC CLI via SSHBMC CLI over SSHv2.
TCP80TLS 1.2lighttpdBMC GUI redirection to port 443

HTTP server redirects browser to port 443 for HTTPS. No actual BMC access on port 80.

TCP443TLS 1.2lighttpdBMC GUI via HTTPS 
TCP

5120

TCPcdserver opp

BMC Remote Console: CD

 
TCP

5121

 not used

not used

BMC Remote Console: Keyboard and Mouse

 
TCP

5123

not usednot used

BMC Remote Console: Diskette

 
TCP

5555

not usednot used

BMC Remote Console: Encryption

 
TCP

5556

not usednot used

BMC Remote Console: Authentication

 
TCP

6481

not usednot used

BMC Remote Console: Servicetag Daemon

 
TCP

7578

TCP 

BMC Remote Console: Video

 
TCP7579   BMC Remote Console: Serial 
TCPRandom portTCPIPMI  
Multiexcerpt
MultiExcerptNameME2

SBC Core Management Ports

Caption
0Table
1SBC Core Management Ports
Protocol

Network Port

Application Level ProtocolProcess Using the Ports

Usage

Notes

TCP

 

 

 

 

 

 

 

 

 

 

 

22

SSHSSHD

SBC application CLI via SSH 

Application CLI over SSHv2.

80

TLS 1.2lighttpd

Embedded Management Application (EMA) GUI redirection to port 443

HTTP server redirects browser to port 443 for HTTPS. No actual EMA access on port 80. 

443

 TLS 1.2lighttpd

EMA GUI via https

 

444

connexip manager 

EMA GUI, Platform Mode via https

 

2022

confd 

Netconf OAM interface 

Netconf over SSHv2. Used by Sonus EMS to manage the SBC.

2024

sftp 

Linux SFTP access via SSH 

 
3091ssreq-tcpSSREQSSReq troubleshooting toolDefault TCP port

4680

  

SecureLink client GUI via http 

The SecureLink client is a RASO feature that creates and maintains an SSH connection to the SecureLink server at SonusHQ, to support remote troubleshooting. This port presents a GUI interface to manage the SL client.

NOTE: SecureLink runs on a separate VM instance for SBC SWe; hence this port is not applicable for SBC SWe.

Port 4680 is restricted to "localhost." This ensures that Gatekeeper (the SecureLink GUI) cannot be accessed remotely using the management port of the SBC. 

UDP

 

 

123NTPNTPDNetwork Timing Protocol Daemon (NTPD) 

161   

SNMPSNMP daemon

SNMP agent 

Statistics and status retrieval. Read only.

3054DIAMETER+DSPSX call processing requestsThis port is used for call processing requests coming from the PSX to the SBC over Diameter+. This can also be configured through PKT ports.
3055DIAMETER+DSKeep alive messages and registration (Diameter).This can also be configured through PKT ports.

3069  

DMARSHSCPA

ERE   

ERE SIP SCPA process.

3090ssreq-udpSSREQSSReq troubleshooting toolDefault UDP port

65xxx  

  

PSX    

Dynamically allocated server port number. Part of SBC communication with external PSX.

 

SBC Core Media Physical Ports at Interface IP Addresses

Caption
0Table
1SBC Core Media Physical Ports at Interface IP Addresses
Protocol

Network Port

Application Level ProtocolProcess Using the Ports

Usage

Notes

UDP

500

IKEIKE

IKE

IKEv1 or IKEv2 Internet Key Exchange for IPSec

1024-65534

RTP, RTCP,SRTP,SRTCP 

RTP, RTCP, SRTP, SRTCP

Real time media

ESP

N/A

  

IPSec ESP

Encapsulating Security Payload

 

SBC Core Media Physical Ports at Signaling Port IP Addresses

Caption
0Table
1SBC Core Media Physical Ports at Signaling Port IP Addresses
Protocol

Network Port

Application Level ProtocolProcess Using the Ports

Usage

Notes

TCP

2569

MSCSAM

GW – GW signaling

Sonus proprietary gateway-to-gateway signaling. Listen port is configurable; 2569 is the default.

NOTE: This port is not applicable for SBC SWe as GW-GW signaling is not supported for SWe.

5060

SIPSIPE

SIP signaling over TCP

Listen port is configurable; 5060 is the default.

5061

SIPSIPE

SIP signaling over TLS over TCP

Listen port is configurable; 5061 is the default.

UDP

5060

SIPSIPE

SIP signaling over UDP

Listen port is configurable; 5060 is the default.

SCTP

5060

SIPSIPE

SIP signaling over SCTP

Listen port is configurable; 5060 is the default.

ESP

N/A

  

IPsec ESP

Encapsulating Security Payload. Terminates on signaling address when IPSec is used in IMS access and peering modes (in peering mode, the protected address may be different).

Info
titleNote

If a zone's sipSigPort is configured for transportProtocolsAllowed =   sip-tls-tcp, and either Egress IPSP Transport Type is TLS Over TCP and/or the Egress TG’s transportPreference is tls-tcp, the SBC increments the configured portNumber by 1 and uses it as the new port number for SIP over TLS signaling. The SBC then opens a TCP socket for SIP over TLS for the new TCP port number.

Example: When sipSigPort is configured with a portNumber of 5060 and transportProtocolsAllowed = sip-tls-tcp, the SBC listens on TCP port 5061 for SIP over TLS.

 

Pagebreak