"...It is also RECOMMENDED that a server listen for requests on the default SIP ports (5060 for TCP and UPD, 5061 for TLS over TCP) on all public interfaces...For any port and interface that a server listens on for UDP, it MUST listen on that same port and interface for TCP"

Note the term "recommended". Yes, standard practice is to use 5060 but if one wants to debate compliancy...

In your case, you are using the recommended server listening port. So, no need to debate the finer points. The next question is the client source port. Again, from RFC 3261, section 18.

Paragraph 2: "...When the connection is

accepted by the transport layer, this index is set to the source IP

address, port number, and transport. Note that, because the source

port is often ephemeral, but it cannot be known whether it is

ephemeral or selected through procedures in [4],..."

This specifically states that the client source ports may be ephemeral (>1024 to ). To me, this means that using src port 50000 is compliant with RFC3261.

They spell out the port range that CUPC will use for source ports. Note that it is a range of ports that the CUPC client will use. So, if you can convince the security folks to work with you, provide the appropriate range of ports.

Hi All,
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
view more

The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.
...
view more