[asterisk-dev] port= or bindport= in .conf files ?

[Luigi Rizzo]

when it comes to specify a TCP or UDP port, asterisk's .conf files
use a variety of names, the most popular being

	port = XXXX
		cdr_pgsql.conf, cdr_tds.conf, dundi.conf,
		festival.conf, h323.conf, iax.conf (outbound),
		iaxprov.conf (inbound), jabber.conf (out?),
		manager.conf (inbound),
		mgcp,conf, sip.conf (outbound)
		
	bindport = XXXX
		http.conf (inbound), iax.conf (inbound), sip.conf (inbound),

	sslbindport = XXX
		http.conf (inbound), manager.conf (inbound)

	serverport = XXX
		iaxprov.conf (outbound)

While the (rarely used) bindport and sslbindport have a clear
name and a coherent usage, "port" is more confusing as it is
used for inbound and outbound connections depending on the
file.

There is a lot more uniformity in the bind address, which
is always specified as "bindaddr" or "sslbindaddr"
(though outbound addresses are still specified in multiple
ways e.g. host/serverhost/...)

Given the above, would people agree to use "bindport" everywhere
to specify a port number for inbound connections, and possibly even
support a port number in bindaddr same as iax.conf does e.g.

	bindaddr = 1.2.3.4	# use default port for the service
	bindaddr = 1.2.3.4:5678	# explicit port number
	bindaddr = :5678	# same as 0.0.0.0:5678
	bindaddr = *:5678	# same as 0.0.0.0:5678

cheers
luigi