Problem in SipConnector handling if reverse DNS lookup is missing

[GoogleCodeExporter]

What steps will reproduce the problem?
1. In standalone-sip.xml, bind a interface (e.g. the public-interface) to an IP 
address which does not exist in /etc/hosts or in any DNS server.
2. Start up mobicents platform in standalone mode.
3. SipConnector initialization is now "delayed" and system and e.g. servlets 
are started before full initialization of the SipConnectors happens.

SipConnector[] sipConnectors = (SipConnector[]) 
getServletContext().getAttribute("org.mobicents.servlet.sip.SIP_CONNECTORS");

will in this case return a incorrect number of SIP connectors. 
The attribute is not updated when the SipConnectors are created later on.

What is the expected output? What do you see instead?
SipConnectors should be properly initialized and available for the system 
regardless if a reverse DNS entry is present or not.

What version of the product are you using? On what operating system?
mss-3.0.0-SNAPSHOT-jboss-as-7.1.3.Final
Linux/Debian/Ubuntu

Please provide any additional information below.

Original issue reported on code.google.com by lars.ols...@gmail.com on 1 Dec 2013 at 12:12

[GoogleCodeExporter]

Original comment by jean.deruelle on 2 May 2014 at 8:22

• Changed state: Started
• Added labels: TelScale-7.0.2.GA

[GoogleCodeExporter]

This issue was closed by revision dad7fb89dfe8.

Original comment by jean.der...@telestax.com on 2 May 2014 at 9:03

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by jean.der...@telestax.com on 25 Aug 2014 at 10:52

• Added labels: MSS-2.1.0.FINAL
• Removed labels: MSS-3.0.0.FINAL