here's an old list of all ports, it's not exactly what you're asking...
but this is what you'd get from devs.
I had to build my documentation and figure the rest out for myself (our
commercial product comes with documentation). The wiki is public
documentation maintained by the community.
All ports are assumed to be both UDP and TCP (even where the component only
uses one of them).
*Port Component
Use *
3478 sipXopenfire Stun server port.
3479 sipXrelay Local discovery port for STUN.
3480 sipXbridge Local discovery port for STUN.
5060 sipXproxy SIP
5061 sipXproxy SIP/TLS
5064 sipXopenfire SIP Dialog watcher plugin SIP signaling port.
5070 sipXregistrar SIP
5071 sipXregistrar SIP/TLS
5075 sipXregistrar SIP registration event subscriptions
5077 sipXregistrar SIP registration replication
5080 sipXbridge SIP WAN-Facing port
5081 sipXbridge SIP/TLS WAN-Facing port
5090 sipXbridge SIP LAN-Facing port
5091 sipXbridge SIP/TLS LAN-Facing port
5110 sipXpublisher SIP
5111 sipXpublisher SIP/TLS
5120 sipXpark SIP
5121 sipXpark SIP/TLS
5130 sipXpresence SIP
5140 sipXrls SIP
5141 sipXrls SIP/TLS
5150 sipXacd SIP
5151 sipXacd SIP/TLS
5152 sipXacd Presence Monitor XML-RPC(?)
5160 sipXpage SIP
5161 sipXpage SIP/TLS
5170 sipXsaa Shared Appearance Agent
5222 sipXopenfire The standard port for clients to connect to the
server. Connections may or may not be encrypted.
5223 sipXopenfire The port used for clients to connect to the
server using the old SSL method.
5229 sipXopenfire Flash Cross Domain.
5656 *reserved for test user agents on developer systems*
6050 sipXcallController SIP TCP/UDP port for SIP Signaling.
6051 sipXcallController SIP TLS port for SIP Signaling (reserved).
6565 *reserved for test user agents on developer systems*
6666 sipXcallController HTTPS port for REST API (local domain)
6661 sipXcallController HTTPS port for REST API (foreign domain)
7070 sipXopenfire HTTP Binding (unsecured).
7443 sipXopenfire HTTPS Binding.
7777 sipXopenfire File Transfer Proxy.
8021 FreeSWITCH event_socket inteface
8080 FreeSWITCH FreeSWITCH XML-RPC
8084 sipXivr event_socket interface
8085 sipXivr Jetty interface
8088 sipXbridge HTTP sipXbridge XML RPC port
8089 sipXrelay HTTP sipXrelay XML RPC port
8090 sipXconfig HTTP
8091 sipXconfig HTTPS
8100 sipXpublisher HTTP (voicemail store interface)
8101 sipXpublisher HTTPS (voicemail store interface)
8110 sipXacd XML-RPC/HTTPS provisioning
8111 sipXpresence HTTP
8130 sipXconfig call resolver remote data
8184 sipXacccode Access Code - event_socket interface
8185 sipXprovision HTTP Auto-Provisioning Servlet
8443 sipXconfig SSL web UI
8500... sipXpage RTP/RTCP ports
8999 openUC Only Reverse Proxy for openUC REST services
9000... sipXvxml RTP/RTCP ports
9094 sipXopenfire Admin Console
9095 sipXopenfire Admin Console
10000...sipXacd RTP/RTCP ports
11000:12999 FreeeSWITCH RTP/RTCP ports
15060 FreeSWITCH SIP
30000:31000 sipXRelay RTCP ports for sipx relay (no ports in this range
should be used).
Mike
On Fri, Mar 2, 2012 at 4:59 AM, Borginger Rikard <
[email protected]> wrote:
> Would it be better to ask this question to the developer-list instead?
>
>
> ------------------------------
> *Från:* [email protected] [
> [email protected]] för Michael Picher [
> [email protected]]
> *Skickat:* den 2 mars 2012 10:36
> *Till:* Discussion list for users of sipXecs software
> *Ämne:* Re: [sipx-users] Ports used in an HA-system..
>
> Many...
>
> don't forget dns, stunnel, etc...
>
> Plus it's all changing with 4.6. I'm not sure that there's a wiki page
> with this info, but it might be good for you to create one.
>
> Mike
>
> On Fri, Mar 2, 2012 at 4:28 AM, Borginger Rikard <
> [email protected]> wrote:
>
>> Hi guys.
>>
>> I'm still very interested in which ports and protocols the HA-servers
>> are talking over.
>>
>> I seen some SNMP, NTP and some SSL-traffic over tcp/8092 and 5077
>>
>> Anyone with details in this?
>>
>> / Rikard, Sweden
>>
>> _______________________________________________
>> sipx-users mailing list
>> [email protected]
>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>
>
>
>
> --
> Michael Picher, Director of Technical Services
> eZuce, Inc.
>
> 300 Brickstone Square****
>
> Suite 201****
>
> Andover, MA. 01810
> O.978-296-1005 X2015
> M.207-956-0262
> @mpicher <http://twitter.com/mpicher>
> www.ezuce.com
>
>
> ------------------------------------------------------------------------------------------------------------
> Hope to see you at the sipX CoLab! http://www.sipfoundry.org/sipx-colab
> A gathering for - open source users, eZuce customers & eZuce partners
> Get the inside track on 4.6 and a glimpse at the future of sipXecs!
>
>
> _______________________________________________
> sipx-users mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>
--
Michael Picher, Director of Technical Services
eZuce, Inc.
300 Brickstone Square****
Suite 201****
Andover, MA. 01810
O.978-296-1005 X2015
M.207-956-0262
@mpicher <http://twitter.com/mpicher>
www.ezuce.com
------------------------------------------------------------------------------------------------------------
Hope to see you at the sipX CoLab! http://www.sipfoundry.org/sipx-colab
A gathering for - open source users, eZuce customers & eZuce partners
Get the inside track on 4.6 and a glimpse at the future of sipXecs!
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
