Configuring FMS on IIS, separate IP addresses

 Specifies what IP address and port(s) to bind to. This is specified 

 as a string in the form "<ip>:<port>,<port>,...,<port>".            

 For example, "127.0.0.1:1935,80,443". This says to bind to the IP   

 address of 127.0.0.1 on ports 1935, 80, and 443. You can bind to    

 any IP by not specifying anything in front of the colon.            

 For example, ":1935,80,443". This says to bind to any IP on ports   

 1935, 80, and 443. If no colon is found, the data is assumed to be  

 an IP address, and will bind to port 1935 as the default.           

 For example, "127.0.0.1". This says to bind to IP 127.0.0.1 on port 

 1935. If a colon is found but no ports are specified after it, port 

 1935 is used as the default port in which to bind.                  

 For example, "127.0.0.1:". This says to bind to IP 127.0.0.1 on     

 port 1935.  If you wish to bind to multiple IP addresses on this    

 adaptor, specify additional <HostPort> tags; 1 for each additional  

 IP that you wish to bind to. NOTE: Another adaptor may also try to  

 bind to the same IP-port combination resulting in a conflict. This  

 is considered a conflict since it is undesirable to have more than  

 one adaptor listening on the same IP-port pair. To resolve this     

 conflict, the first adaptor to do the bind - wins. A warning will   

 be logged indicating that the specified IP-port combo is in-use.    

 The ctl_channel tag attribute controls the internal port that an    

 fmsedge process listens on. When an fmscore process is started, it  

 establishes a control channel with the fmsedge process by conneting 

 to it on this internal port. Each <HostPort> tag corresponds to an  

 fmsedge process. If multiple <HostPort> tags exist, then each needs 

 to have a different ctl_channel configured.