I found the reason of the problem. When sipXecs is searching existing clients, because of a missing local IP information in the client socket object it discards the existing client. As a result it tries to open a new connection.
On Thu, Oct 7, 2010 at 8:10 PM, Arman Güngör <[email protected]> wrote: > Hi, > > When a phone sends a REGISTER request to sipXecs using TLS, sipXecs does > not use the existing connection for response. It tries to open a new TCP > connection to the same port of client. Which part of sipXecs is responsible > from this decision? Where it checks the existing connections and creates a > new one ? > > Regards, > > Arman >
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
