<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial, helvetica, sans-serif;font-size:10pt"><DIV>Hi Bogdan,</DIV>
<DIV> </DIV>
<DIV>Thanks for the answer. I now realize I have not provided all relevant information and I have not been fully correct with my first message.</DIV>
<DIV> </DIV>
<DIV>I have to mention that I have a custom module on the server, which takes care of subscriptions for one custom event. This module is workign fine and it is responsible for sending NOTIFYs when needed.</DIV>
<DIV> </DIV>
<DIV>I am pasting three packets of the communication between the client and the server below. The client sends SUBSCRBE through the TLS connection and the server responds with 202 OK to the client using the same (single at that time) TLS connection which came from the client. But after that, when the server (my custom module) needs to send NOTIFY to the client, for some reason the server establishes a new TLS connection to the client through which it sends the NOTIFY. Here are the packets:</DIV>
<DIV> </DIV>
<DIV>-----------------------------------------------------------------</DIV>
<DIV>SUBSCRIBE sips:ivan@10.0.5.5 SIP/2.0<BR>Via: SIP/2.0/tls 10.0.5.112:2013;rport;branch=z9hG4bKPj6a7bed4a838c416fa70d57c85ef98e21<BR>Max-Forwards: 70<BR>From: "Ivan" <sips:ivan@10.0.5.112>;tag=8e8c2497ec8e4edeb3fc031ad861698d<BR>To: sips:ivan@10.0.5.5<BR>Contact: "Ivan" <sips:ivan@10.0.5.112:5061;transport=TLS><BR>Call-ID: 41d9d9772e89462ca9e71e225d03f596<BR>CSeq: 18467 SUBSCRIBE<BR>Event: custom-event<BR>Expires: 120<BR>Accept: text/plain<BR>Allow-Events: presence, refer, custom-event<BR>Content-Type: text/plain<BR>Content-Length: 6</DIV>
<DIV> </DIV>
<DIV>010203</DIV>
<DIV>-----------------------------------------------------------------</DIV>
<DIV>SIP/2.0 202 OK<BR>Via: SIP/2.0/tls 10.0.5.112:2013;rport=2013;branch=z9hG4bKPj6a7bed4a838c416fa70d57c85ef98e21<BR>From: "Ivan" <sips:ivan@10.0.5.112>;tag=8e8c2497ec8e4edeb3fc031ad861698d<BR>To: sips:ivan@10.0.5.5;tag=10.0.1219249054.4<BR>Call-ID: 41d9d9772e89462ca9e71e225d03f596<BR>CSeq: 18467 SUBSCRIBE<BR>Expires: 120<BR>Server: OpenSER (1.3.0-tls (i386/linux))<BR>Content-Length: 0</DIV>
<DIV>-----------------------------------------------------------------</DIV>
<DIV>NOTIFY sips:ivan@10.0.5.112:5061;transport=TLS SIP/2.0<BR>Via: SIP/2.0/TLS 10.0.5.5:5061;branch=z9hG4bKc2bf.75041b55.0<BR>To: sip:ivan@10.0.5.112;tag=8e8c2497ec8e4edeb3fc031ad861698d<BR>From: sip:ivan@10.0.5.5;tag=10.0.1219249054.4<BR>CSeq: 1 NOTIFY<BR>Call-ID: 41d9d9772e89462ca9e71e225d03f596<BR>Content-Length: 6<BR>User-Agent: OpenSER (1.3.0-tls (i386/linux))<BR>Max-Forwards: 70<BR>Event: custom-event<BR>Subscription-State: active;expires=120<BR>Content-Type: text/plain</DIV>
<DIV> </DIV>
<DIV>010203</DIV>
<DIV>-----------------------------------------------------------------</DIV>
<DIV> </DIV>
<DIV>Can it be told from these packets what makes the server think the connection point is different? I suspect the connection point looks different to the server because "sips:ivan@10.0.5.112:5061;transport=TLS" is different SIP URI than "sips:ivan@10.0.5.5", maybe? 10.0.5.112 is the client's IP and 10.0.5.5 is the server's.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Thanks in advance,</DIV>
<DIV> </DIV>
<DIV>Ivan.</DIV>
<DIV>
<DIV> </DIV></DIV>
<DIV> </DIV>
<DIV style="FONT-SIZE: 10pt; FONT-FAMILY: arial, helvetica, sans-serif">
<DIV style="FONT-SIZE: 10pt; FONT-FAMILY: arial, helvetica, sans-serif">----- Original Message ----<BR>From: Bogdan-Andrei Iancu <bogdan@voice-system.ro><BR>To: Ivan Genov <ivangg_q@yahoo.com><BR>Cc: devel@lists.opensips.org<BR>Sent: Wednesday, August 20, 2008 1:20:20 AM<BR>Subject: Re: [OpenSIPS-Devel] How to make OpenSIPS reuse client's TCP/TLS connection (and not try to connect on its own)?<BR><BR>Hi Ivan,<BR><BR>The OpenSIPS reuses the TCP/TLS connection only if the connection point <BR>(where it tries to connect to) is already involved in a established <BR>connection.<BR><BR>In your case, maybe the connection point looks different than any <BR>existing connections, so a new one is opened.<BR><BR>Regards,<BR>Bogdan<BR><BR>Ivan Genov wrote:<BR>> Hi,<BR>> <BR>> I am noticing that when a client connects to the OpenSIPS server via <BR>> TLS the server is establishing a new TLS connection to the client and <BR>> sends the
respond through it. This works OK for internal LAN, but if <BR>> you are trying to connect with the client from outside Internet (or <BR>> other unreachable for the OpenSIPS place) the OpenSIPS cannot <BR>> establish this connection and it will not work.<BR>> <BR>> My expectation was that the SIP server would reuse the same TCP/TLS <BR>> connection that the client made to it, but obviously it is not so. Do <BR>> you know if there is a way to configure the server (possibly the <BR>> client), so that the server reuses the client's connection and does <BR>> not try to create a new one?<BR>> <BR>> <BR>> Thanks,<BR>> <BR>> Ivan.<BR>><BR>> ------------------------------------------------------------------------<BR>><BR>> _______________________________________________<BR>> Devel mailing list<BR>> <A href="mailto:Devel@lists.opensips.org"
ymailto="mailto:Devel@lists.opensips.org">Devel@lists.opensips.org</A><BR>> <A href="http://lists.opensips.org/cgi-bin/mailman/listinfo/devel" target=_blank>http://lists.opensips.org/cgi-bin/mailman/listinfo/devel</A><BR>> <BR><BR></DIV></DIV></div><br>
</body></html>