Page tree

Versions Compared

Key

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

...

PORTTCP/UDPPURPOSECHANGING PORTSECURITYNOTES

see PBX SIP section above

TCPSangoma Connect Signaling
Sangoma Connect uses chan_PJSIP TCP signaling by default
Change this port in the PBX Admin GUI→ Settings Asterisk SIP Settings → PJSIP TCP Bind PortOpening this port to untrusted source IPs is necessary for mobile clients, but it's important that it be protected with PBX Responsive Firewall and/or Intrustion Detection (fail2ban)Used for signaling
See PBX SIP section aboveUDPMedia
Sangoma Connect media uses the default Asterisk SIP RTP range
The port can be changed by going to Settings → Asterisk SIP Settings → General SIP Settings Tab. Note: same RTP port configuration as SIP.Safe to open this up to untrusted networks

Used for media


8443TCPNode Server. The SangomaConnect node servers binds on this port only on localhost interface (127.0.0.1). If ConnectMobile SSL certificates are being used, the binding to this port will be secured (https).The port can be changed by going to Settings → Advanced Settings → SangomaConnect section → .This port is ONLY opened and used on localhost (127.0.0.1). No need to enable/expose it on the firewall.Used for internal Sangoma Connect API


Zulu 3

 

PORTTCP/UDPPURPOSECHANGING PORTSECURITYNOTES

8002

TCPZulu 3 Client Communication with PBXCan change this port inside the PBX Admin GUI > Advanced Settings > Zulu Section > Zulu Bind AddressSafe to open this up to untrusted networks as the traffic is encrypted with SSL and requires username and password authentication.Used for signalling
10000-20000UDPMedia - RTPThe port can be changed by going to Settings → Asterisk SIP Settings → General SIP Settings Tab. Note: Zulu uses the same rtp port configuration as SIP.Safe to open this up to untrusted networks, as your RTP traffic can come from anywhere your Zulu users are connecting from.Used for handling media during a call

...