> OpenSIPS do reuses the TCP connections, but there are some conditions > for this to happen - when something needs to be sent out via TCP, first > i s checked if there is an already existing connection to the source > IP and port. If so, it will be reused. > > So, you say that the the clients do register via TCP (and the > connections are up) via C1 and C2. Now one of the clients tries to call > the other one, so the call is sent out (let;s say) via C1 to opensips > and opensips is failing to deliver the call via C2 to the second client, > right?
Yes. That's the case. And I already found the cause of the troubles: The eyebeam-client does not use the port where the TLS connection has been setup in the Contact header field. It uses at totally different port as Contact: Examples: Alice registers via TLS at 10.0.0.1:2852 and uses as contact sip:al...@10.0.0.1:18855. Bob registers via TLS at 10.0.0.2:2692 and uses as contact sip:b...@10.0.0.2:36251. I verified the Contact addresses in the location database and thanks to siptrace() I captured also easily the REGISTER request. So it is clear that OpenSIPS forwards the request to a port where eyebeam is not listening. Did anyone see such a strange behaviour? I will post the issue at the eyebeam support forum. Regards Franz _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users