[Users]Can OpenSER uses same TCP session from the registration in some TLS case?

[Pat wang]

Hi Klaus,

I forgot to say that the R-URI is the same as the one as in the Contact URI. 
The Eyebeam is registered with a contact URI as: 
user1 at 192.168.100.1:port1;rinstance=xxx;transport=tls
and the Request-URI received on OpenSER matches exactly as the Contact URI.

What I am trying to do is to have OpenSER as TLS to UDP protocol converter 
to a 3rd party proxy without TLS feature.  I need the 3rd party proxy keeps 
record of the TLS clients by configuring OpenSER forward the REGISTER from 
the TLS client through UDP. If a call is from UDP client to TLS client the 
3rd party proxy does the replacement of RURI and proxy it to OpenSER through 
UDP. What I expect is OpenSER uses the existing TCP session to proxy the 
INVITE to the TLS client. Any new suggestiongs?

Thanks,

Patrick

>From: Klaus Darilion <klaus.mailinglists at pernau.at>
>To: Pat wang <wangyu39 at hotmail.com>
>CC: users at openser.org
>Subject: Re: [Users]Can OpenSER uses same TCP session from the registration 
>in	some TLS case?
>Date: Fri, 20 Oct 2006 08:43:54 +0200
>
>Pat wang wrote:
>>Hi,
>>
>>I am working on the TLS with OpenSER and I found an something interesting. 
>>If an INVITE received by OpenSER with a Request-URI of the client AOR then 
>>OpenSER proxy the request via the same TCP session established during 
>>registration. If the INVITE has a Request-URI of the client's contact URI 
>>then OpenSER start a new TCP session.
>>
>>For example:
>>One Eyebeam registers with AOR as: user1 at tlstest.com and has a contact URI 
>>of user1 at 192.168.100.1. When an INVITE contains a RURI as
>
>the contact must be at least user1 at 192.168.100.1;transport=TLS, and usually 
>also a port is specified.
>
>Thus I guess it happens as you directly dial the contact without transport 
>parameter and port.
>
>regards
>klaus
>
>PS: Of course a dump would help:
>
>"ngrep -W byline -t port 5060"
>
>if you use TLS use port 5061 and use the NULL encryption schema in TLS 
>settings.
>
>
>
>>user1 at tlstest.com then OpenSER look up the location table and replace it 
>>with the user1 at 192.168.100.1 then proxy it via the same TCP session as the 
>>one during the registration. If an INVITE already has RURI as 
>>user1 at 192.168.100.1 then OpenSER proxy this INVITE by starting a new TCP 
>>session and Eyebeam does not accept the new session. The call will be 
>>failed in this case. I can't find any solution to fix this issue. Could 
>>someone know this issue please give some advice?
>>
>>Thanks,
>>
>>Patrick
>>
>>_________________________________________________________________
>>All-in-one security and maintenance for your PC.  Get a free 90-day trial! 
>>http://clk.atdmt.com/MSN/go/msnnkwlo0050000002msn/direct/01/?href=http://www.windowsonecare.com/?sc_cid=msn_hotmail
>>
>>
>>
>>_______________________________________________
>>Users mailing list
>>Users at openser.org
>>http://openser.org/cgi-bin/mailman/listinfo/users
>

_________________________________________________________________
All-in-one security and maintenance for your PC.  Get a free 90-day trial! 
http://clk.atdmt.com/MSN/go/msnnkwlo0050000002msn/direct/01/?href=http://www.windowsonecare.com/?sc_cid=msn_hotmail