<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
On 12/2/11 12:48 PM, Bruno Bresciani wrote:
<blockquote
cite="mid:CAKv6MrYkMahaBguMP+gTLXbTEOf1mMUrQ-nck=Jn=h2UA5hbuA@mail.gmail.com"
type="cite">Hello <br>
<br>
Is attached the diagram showing the call flow... I have a cell
phone with Android and Bria softphone registered on kamailio via
TLS protocol. When I make a call by Bria, this INVITE is routed of
the kamailio to gateway SIP via UDP protocolo because Bria
specified transport=TLS only contact header and nothing in R-URI.<br>
I want all way the call is forwarded with TLS protocol.<br>
</blockquote>
<br>
do you want to force TLS between Kamailio and gateway only if calls
comes via TLS? Or always (e.g., call comes over UDP to Kamailio and
has to go via TLS to gateway)?<br>
<br>
If you want to enforce always tls, then just set $du before relaying
to gateway:<br>
<br>
$du = <a class="moz-txt-link-rfc2396E" href="sip:gatewayip;transport=tls">"sip:gatewayip;transport=tls"</a>;<br>
<br>
There are also functions from tm where you can force tls transport
(see the readme of tm module).<br>
<br>
If you want to send over tls only when it comes via TLS, then do the
checking<br>
<br>
if(proto==TLS) {<br>
# came over tls, enforce tls for outgoing to gateway<br>
$du = <a class="moz-txt-link-rfc2396E" href="sip:gatewayip;transport=tls">"sip:gatewayip;transport=tls"</a>;<br>
}<br>
<br>
Cheers,<br>
Daniel<br>
<blockquote
cite="mid:CAKv6MrYkMahaBguMP+gTLXbTEOf1mMUrQ-nck=Jn=h2UA5hbuA@mail.gmail.com"
type="cite"><br>
Cheers<br>
<br>
<br>
<br>
<div class="gmail_quote">2011/12/1 Daniel-Constantin Mierla <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div bgcolor="#FFFFFF" text="#000000"> Hello,
<div><br>
<br>
On 11/30/11 11:59 AM, Bruno Bresciani wrote:
<blockquote type="cite">Now I understood why the messagem
is forward with UDP protocol... This problem occurs with
bria on android plataform, this softphone send the
INVITE request with tls protocol specified only on the
contact header.<br>
<br>
Contact: "XXX" <a moz-do-not-send="true"><sip:XXX@YYY.YYY.YYY.YYY:YYY;transport=TLS></a>.<br>
<br>
as Daniel pointed out, "The contact header address is
not used for routing SIP requests, only Route headers
and R-URI addresses"<br>
<br>
In this case, I should add the transport protocol TLS on
R-URI before to forward message with t_relay function...
Correct?<br>
</blockquote>
</div>
it is not clear for me why you need to forward on TLS if the
destination address is not requiring that. Maybe you can
draw a diagram showing the call flow, who is on TLS and how
is happening at this moment and what you would like to
happen.<br>
<br>
Cheers,<br>
<font color="#888888"> Daniel</font>
<div>
<div><br>
<br>
<blockquote type="cite"> <br>
Cheers<br>
<br>
<br>
<div class="gmail_quote">2011/11/29 Daniel-Constantin
Mierla <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin: 0pt
0pt 0pt 0.8ex; border-left: 1px solid rgb(204,
204, 204); padding-left: 1ex;">
<div bgcolor="#FFFFFF" text="#000000">
<div> <br>
<br>
On 11/29/11 6:24 PM, Bruno Bresciani wrote:
<blockquote type="cite">Thank's for attention
Andrew<br>
<br>
I'm reading the source code of tm module to
try understand better this behavior... <br>
I can't understand what meaning that "the
outbound proxy address is set"... where I
define this address? <br>
</blockquote>
<br>
</div>
Outbound proxy address is stored in an internal
structure, it is not part of a SIP request. It
represents the address where to send the
request, regardless of request URI (r-uri)
address. One common use case is when dealing
with NAT routers, the r-uri is set to the
contact address of the destination phone and the
outbound proxy address is set to the NAT router.<br>
<br>
From configuration file, you can access it via
$du (read and write via assignment operation).
There are couple of modules that may set the
outbound proxy address, like registrar/usrloc,
rr, lcr...<br>
<br>
Maybe the best is to post here an ngrep with the
SIP trace of such case, that we can see if
something is wrong.<br>
<br>
Cheers,<br>
<font color="#888888"> Daniel</font>
<div><br>
<blockquote type="cite"> <br>
<br>
<div class="gmail_quote">2011/11/29 Andrew
Pogrebennyk <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:apogrebennyk@sipwise.com"
target="_blank">apogrebennyk@sipwise.com</a>></span><br>
<blockquote class="gmail_quote"
style="margin: 0pt 0pt 0pt 0.8ex;
border-left: 1px solid rgb(204, 204,
204); padding-left: 1ex;"> Bruno,<br>
the address from contact header is put
into R-URI on outgoing request to<br>
that user. This is where I catch that
parameter. I think we should debug<br>
why kamailio sends the request using
UDP, it is not clear, as Daniel<br>
pointed out it should work
automatically. I think I had to do these<br>
manipulations because in my case the
outbound proxy address is set<br>
<div><br>
On 11/29/2011 05:38 PM, Bruno
Bresciani wrote:<br>
> In my case the transport=TLS is
present in contact header, has the
same<br>
> treatment of R-URI?<br>
><br>
> Cheers<br>
<br>
<br>
</div>
<div>
<div>_______________________________________________<br>
SIP Express Router (SER) and
Kamailio (OpenSER) - sr-users
mailing list<br>
<a moz-do-not-send="true"
href="mailto:sr-users@lists.sip-router.org"
target="_blank">sr-users@lists.sip-router.org</a><br>
<a moz-do-not-send="true"
href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users"
target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a moz-do-not-send="true" href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>
<a moz-do-not-send="true" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<br>
</div>
<div>
<pre cols="72">--
Daniel-Constantin Mierla -- <a moz-do-not-send="true" href="http://www.asipto.com" target="_blank">http://www.asipto.com</a>
Kamailio Advanced Training, Dec 5-8, Berlin: <a moz-do-not-send="true" href="http://asipto.com/u/kat" target="_blank">http://asipto.com/u/kat</a>
<a moz-do-not-send="true" href="http://linkedin.com/in/miconda" target="_blank">http://linkedin.com/in/miconda</a> -- <a moz-do-not-send="true" href="http://twitter.com/miconda" target="_blank">http://twitter.com/miconda</a></pre>
</div>
</div>
</blockquote>
</div>
<br>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a moz-do-not-send="true" href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>
<a moz-do-not-send="true" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<br>
<pre cols="72">--
Daniel-Constantin Mierla -- <a moz-do-not-send="true" href="http://www.asipto.com" target="_blank">http://www.asipto.com</a>
Kamailio Advanced Training, Dec 5-8, Berlin: <a moz-do-not-send="true" href="http://asipto.com/u/kat" target="_blank">http://asipto.com/u/kat</a>
<a moz-do-not-send="true" href="http://linkedin.com/in/miconda" target="_blank">http://linkedin.com/in/miconda</a> -- <a moz-do-not-send="true" href="http://twitter.com/miconda" target="_blank">http://twitter.com/miconda</a></pre>
</div>
</div>
</div>
</blockquote>
</div>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla -- <a class="moz-txt-link-freetext" href="http://www.asipto.com">http://www.asipto.com</a>
Kamailio Advanced Training, Dec 5-8, Berlin: <a class="moz-txt-link-freetext" href="http://asipto.com/u/kat">http://asipto.com/u/kat</a>
<a class="moz-txt-link-freetext" href="http://linkedin.com/in/miconda">http://linkedin.com/in/miconda</a> -- <a class="moz-txt-link-freetext" href="http://twitter.com/miconda">http://twitter.com/miconda</a></pre>
</body>
</html>