two entries pointing to the same host, causing conflicts

[hboetes]

If you'd examine the templates generated by sccp_manager: They create two entries for my hosts, one for the external and one for the external IP. This is causing delays. Where can I configure it only using the internal IP?

    <callManagerGroup>                                                                                                                                                        
      <members>                                                                                                                                                               
        <member priority="0">                                                                                                                                                 
          <callManager>                                                                                                                                                       
            <ports>                                                                                                                                                           
              <ethernetPhonePort>2000</ethernetPhonePort>                                                                                                                     
            </ports>                                                                                                                                                          
            <processNodeName>10.10.10.10</processNodeName>                                                                                                                     
          <name>Asterix</name></callManager>                                                                                                                                  
        </member>                                                                                                                                                             
      <member priority="1">                                                                                                                                                   
          <callManager>                                                                                                                                                       
            <ports>                                                                                                                                                           
              <ethernetPhonePort>2000</ethernetPhonePort>                                                                                                                     
            </ports>                                                                                                                                                          
            <processNodeName>123.45.67.8</processNodeName>                                                                                                                    
          <name>Asterix</name></callManager>                                                                                                                                  
        </member></members>                                                                                                                                                   
    </callManagerGroup>                                                                                                                                                       

[dkgroot]

@PhantomVl
Both members should never point at the same server (causes looping) and srst should be disabled...
The problem with current config is "crossover connections and looping". Secondary members are normally only used for cluster connections to a secondary server.

[PhantomVl]

The configuration includes all interfaces on which the server listens . You can also specify an external address in the settings . The network configuration must ensure that only one connection address is available.

[hboetes]

• This is far from obvious while reading the configuration page.
• After committing it restarts the module and kicks everyone. A warning would be in place. A separate restart button would also be an idea.

[hboetes]

On the positive side, registering of phones was a lot faster this time.

[hboetes]

Text description next to the bind:address setting:

 Bind Address: The address to bind to for SCCP. In general, it should be set to '0.0.0.0'. If you find problems with one-way audio, you can set this to a specific address in the server. Note that '127.0.0.1' is always wrong here. Also note that placing in your external IP address will cause the chan_sccp module to not load. A manual edit of the /etc/asterisk/sccp.conf file will be needed to fix and reload the module. 

Doesn't that sound oddly familiar?

[dkgroot]

It sounds like that help text could use a little cleanup :-)