MT#55283 warn about mismatched port ranges

Change-Id: I229056084844702e88867f4c9a17fe3b311d1036

daemon/media_socket.c

@@ -834,6 +834,17 @@ static void __interface_append(struct intf_config *ifa, sockfamily_t *fam, bool
 
 		g_hash_table_insert(__intf_spec_addr_type_hash, &spec->local_address, spec);
 	}
+	else {
+		if (spec->port_pool.min != ifa->port_min
+				|| spec->port_pool.max != ifa->port_max)
+		{
+			ilog(LOG_ERR, "Ignoring mismatched port range (%d > %d) on new "
+					"interface '" STR_FORMAT "', keeping existing "
+					"port range %d > %d", ifa->port_min, ifa->port_max,
+					STR_FMT(&ifa->name), spec->port_pool.min,
+					spec->port_pool.max);
+		}
+	}
 
 	ifc = uid_slice_alloc0(ifc, &lif->list);
 	ice_foundation(&ifc->ice_foundation);

docs/rtpengine.md

@@ -1695,7 +1695,8 @@ default name extracted from the name of the config section.
 
 Non-alias interfaces support the additional option __advertised__ to set the
 advertised address, as well as __port-min__ and __port-max__ to set a port
-range different from the global setting. Round-robin interface usage is
+range different from the global setting. Note that all interfaces sharing a
+single IP address must use the same port range. Round-robin interface usage is
 supported in the same way as described above, i.e. by using a colon and a
 suffix as part of the interface name.