29 Nov
2011
29 Nov
'11
2:50 p.m.
Hi All,
kamailio 3.1.2 recognize value "transport=TLS" on contact header or only
"transport=tls"?
kamailio forwards (t_relay function) the message with UDP protocol when
value "transport=TLS" is on contact header.
Cheers
29 Nov
29 Nov
3:08 p.m.
Hi Bruno,
What I have done is an explicit check
if (uri_param("transport","tls") ||
uri_param("transport","TLS"))
to call force_send_socket with either udp or tls port.
It would be cool for kamailio to select the proper socket automatically,
I think there was a discussion on that previously but I can't find it
right now. Hopefully someone else has a hint :)
On 11/29/2011 02:50 PM, Bruno Bresciani wrote:
Hi All,
kamailio 3.1.2 recognize value "transport=TLS" on contact header or only
"transport=tls"?
kamailio forwards (t_relay function) the message with UDP protocol when
value "transport=TLS" is on contact header.
Cheers
4:31 p.m.
On 11/29/11 3:08 PM, Andrew Pogrebennyk wrote:
Hi Bruno,
What I have done is an explicit check
if (uri_param("transport","tls") ||
uri_param("transport","TLS"))
to call force_send_socket with either udp or tls port.
It would be cool for kamailio to select the proper socket automatically,
I think there was a discussion on that previously but I can't find it
right now. Hopefully someone else has a hint :)
On 11/29/2011 02:50 PM, Bruno Bresciani wrote:
> Hi All,
>
> kamailio 3.1.2 recognize value "transport=TLS" on contact header or only
> "transport=tls"?
>
> kamailio forwards (t_relay function) the message with UDP protocol when
> value "transport=TLS" is on contact header.
Kamailio is selecting the
proper outbound socket when switching
transport layers -- if the call comes via UDP and R-URI is over TLS,
then it will send over TLS. Parsing of R-URI does case insensitive
matching for transport parameter, so TLS is the same as tls. I have many
configs doing transport gatewaying, where I don't use anything but
simply t_relay()
Can you check to see if there is no outbound proxy address set ($du)?
Ultimately, maybe you can run with debug=3 and look at log messages.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Dec 5-8, Berlin: http://asipto.com/u/kat
http://linkedin.com/in/miconda -- http://twitter.com/miconda
5:38 p.m.
In my case the transport=TLS is present in contact header, has the same
treatment of R-URI?
Cheers
2011/11/29 Daniel-Constantin Mierla <miconda(a)gmail.com>
On 11/29/11 3:08 PM, Andrew Pogrebennyk wrote:
Hi Bruno,
What I have done is an explicit check
if (uri_param("transport","tls") ||
uri_param("transport","TLS"))
to call force_send_socket with either udp or tls port.
It would be cool for kamailio to select the proper socket automatically,
I think there was a discussion on that previously but I can't find it
right now. Hopefully someone else has a hint :)
On 11/29/2011 02:50 PM, Bruno Bresciani wrote:
layers -- if the call comes via UDP and R-URI is over TLS, then it will
send over TLS. Parsing of R-URI does case insensitive matching for
transport parameter, so TLS is the same as tls. I have many configs doing
transport gatewaying, where I don't use anything but simply t_relay()
Can you check to see if there is no outbound proxy address set ($du)?
Ultimately, maybe you can run with debug=3 and look at log messages.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Dec 5-8, Berlin: http://asipto.com/u/kat
http://linkedin.com/in/miconda -- http://twitter.com/miconda
Hi All,
kamailio 3.1.2 recognize value "transport=TLS" on contact header or only
"transport=tls"?
kamailio forwards (t_relay function) the message with UDP protocol when
value "transport=TLS" is on contact header.
Kamailio is selecting the proper outbound socket when switching transport
6:07 p.m.
Bruno,
the address from contact header is put into R-URI on outgoing request to
that user. This is where I catch that parameter. I think we should debug
why kamailio sends the request using UDP, it is not clear, as Daniel
pointed out it should work automatically. I think I had to do these
manipulations because in my case the outbound proxy address is set
On 11/29/2011 05:38 PM, Bruno Bresciani wrote:
In my case the transport=TLS is present in contact
header, has the same
treatment of R-URI?
Cheers
6:24 p.m.
Thank's for attention Andrew
I'm reading the source code of tm module to try understand better this
behavior...
I can't understand what meaning that "the outbound proxy address is set"...
where I define this address?
2011/11/29 Andrew Pogrebennyk <apogrebennyk(a)sipwise.com>
Bruno,
the address from contact header is put into R-URI on outgoing request to
that user. This is where I catch that parameter. I think we should debug
why kamailio sends the request using UDP, it is not clear, as Daniel
pointed out it should work automatically. I think I had to do these
manipulations because in my case the outbound proxy address is set
On 11/29/2011 05:38 PM, Bruno Bresciani wrote:
In my case the transport=TLS is present in
contact header, has the same
treatment of R-URI?
Cheers
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
8:22 p.m.
On 11/29/11 5:38 PM, Bruno Bresciani wrote:
In my case the transport=TLS is present in contact
header, has the
same treatment of R-URI?
If it is the contact header in a request has the SIP
address with
transport TLS, then that is not used for routing. The only header than
can enforce a destination is Route. Otherwise, the request URI (the
address in first line of SIP request) is used for routing.
The contact header address is to inform the other party where to send
back requests within same dialog.
Cheers,
Daniel
Cheers
2011/11/29 Daniel-Constantin Mierla <miconda(a)gmail.com
<mailto:miconda@gmail.com>>
On 11/29/11 3:08 PM, Andrew Pogrebennyk wrote:
Hi Bruno,
What I have done is an explicit check
if (uri_param("transport","tls") ||
uri_param("transport","TLS"))
to call force_send_socket with either udp or tls port.
It would be cool for kamailio to select the proper socket
automatically,
I think there was a discussion on that previously but I can't
find it
right now. Hopefully someone else has a hint :)
On 11/29/2011 02:50 PM, Bruno Bresciani wrote:
Hi All,
kamailio 3.1.2 recognize value "transport=TLS" on contact
header or only
"transport=tls"?
kamailio forwards (t_relay function) the message with UDP
protocol when
value "transport=TLS" is on contact header.
Kamailio is selecting the proper outbound socket when switching
transport layers -- if the call comes via UDP and R-URI is over
TLS, then it will send over TLS. Parsing of R-URI does case
insensitive matching for transport parameter, so TLS is the same
as tls. I have many configs doing transport gatewaying, where I
don't use anything but simply t_relay()
Can you check to see if there is no outbound proxy address set ($du)?
Ultimately, maybe you can run with debug=3 and look at log messages.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Dec 5-8, Berlin: http://asipto.com/u/kat
http://linkedin.com/in/miconda -- http://twitter.com/miconda
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Dec 5-8, Berlin: http://asipto.com/u/kat
http://linkedin.com/in/miconda -- http://twitter.com/miconda
8:28 p.m.
On 11/29/11 6:07 PM, Andrew Pogrebennyk wrote:
Bruno,
the address from contact header is put into R-URI on outgoing request to
that user.
The contact header address is not used for routing SIP requests, only
Route headers and R-URI addresses -- all SIP requests may have a contact
header, for INVITEs is mandatory, but again, it has no relevance in
routing the respective request.
Maybe you refer to the contact header that is in the REGISTER sent by a
phone, which is saved in location table. When someone is calling that
phone, the address from location table is taken and replaces the R-URI.
Cheers,
Daniel
This is where I catch that parameter. I think we
should debug
why kamailio sends the request using UDP, it is not clear, as Daniel
pointed out it should work automatically. I think I had to do these
manipulations because in my case the outbound proxy address is set
On 11/29/2011 05:38 PM, Bruno Bresciani wrote:
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Dec 5-8, Berlin: http://asipto.com/u/kat
http://linkedin.com/in/miconda -- http://twitter.com/miconda
In my case the transport=TLS is present in
contact header, has the same
treatment of R-URI?
Cheers
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
8:32 p.m.
On 11/29/11 6:24 PM, Bruno Bresciani wrote:
Thank's for attention Andrew
I'm reading the source code of tm module to try understand better this
behavior...
I can't understand what meaning that "the outbound proxy address is
set"... where I define this address?
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.
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...
Maybe the best is to post here an ngrep with the SIP trace of such case,
that we can see if something is wrong.
Cheers,
Daniel
2011/11/29 Andrew Pogrebennyk <apogrebennyk(a)sipwise.com
<mailto:apogrebennyk@sipwise.com>>
Bruno,
the address from contact header is put into R-URI on outgoing
request to
that user. This is where I catch that parameter. I think we should
debug
why kamailio sends the request using UDP, it is not clear, as Daniel
pointed out it should work automatically. I think I had to do these
manipulations because in my case the outbound proxy address is set
On 11/29/2011 05:38 PM, Bruno Bresciani wrote:
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Dec 5-8, Berlin: http://asipto.com/u/kat
http://linkedin.com/in/miconda -- http://twitter.com/miconda
In my case the transport=TLS is present in
contact header, has
the same
treatment of R-URI?
Cheers
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list
sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
30 Nov
30 Nov
11:59 a.m.
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.
Contact: "XXX" <sip:XXX@YYY.YYY.YYY.YYY:YYY;transport=TLS>.
as Daniel pointed out, "The contact header address is not used for routing
SIP requests, only Route headers and R-URI addresses"
In this case, I should add the transport protocol TLS on R-URI before to
forward message with t_relay function... Correct?
Cheers
2011/11/29 Daniel-Constantin Mierla <miconda(a)gmail.com>
On 11/29/11 6:24 PM, Bruno Bresciani wrote:
Thank's for attention Andrew
I'm reading the source code of tm module to try understand better this
behavior...
I can't understand what meaning that "the outbound proxy address is
set"... where I define this address?
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.
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...
Maybe the best is to post here an ngrep with the SIP trace of such case,
that we can see if something is wrong.
Cheers,
Daniel
2011/11/29 Andrew Pogrebennyk <apogrebennyk(a)sipwise.com>
Bruno,
the address from contact header is put into R-URI on outgoing request to
that user. This is where I catch that parameter. I think we should debug
why kamailio sends the request using UDP, it is not clear, as Daniel
pointed out it should work automatically. I think I had to do these
manipulations because in my case the outbound proxy address is set
On 11/29/2011 05:38 PM, Bruno Bresciani wrote:
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
listsr-users@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Dec 5-8, Berlin:
http://asipto.com/u/kathttp://linkedin.com/in/miconda -- http://twitter.com/miconda
In my case the transport=TLS is present in
contact header, has the same
treatment of R-URI?
Cheers
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
1 Dec
1 Dec
1:14 p.m.
Hello,
On 11/30/11 11:59 AM, Bruno Bresciani wrote:
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.
Contact: "XXX" <sip:XXX@YYY.YYY.YYY.YYY:YYY;transport=TLS>.
as Daniel pointed out, "The contact header address is not used for
routing SIP requests, only Route headers and R-URI addresses"
In this case, I should add the transport protocol TLS on R-URI before
to forward message with t_relay function... Correct?
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.
Cheers,
Daniel
Cheers
2011/11/29 Daniel-Constantin Mierla <miconda(a)gmail.com
<mailto:miconda@gmail.com>>
On 11/29/11 6:24 PM, Bruno Bresciani wrote:
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Dec 5-8, Berlin: http://asipto.com/u/kat
http://linkedin.com/in/miconda -- http://twitter.com/miconda
Thank's for attention Andrew
I'm reading the source code of tm module to try understand better
this behavior...
I can't understand what meaning that "the outbound proxy address
is set"... where I define this address?
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.
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...
Maybe the best is to post here an ngrep with the SIP trace of such
case, that we can see if something is wrong.
Cheers,
Daniel
2011/11/29 Andrew Pogrebennyk <apogrebennyk(a)sipwise.com
<mailto:apogrebennyk@sipwise.com>>
Bruno,
the address from contact header is put into R-URI on outgoing
request to
that user. This is where I catch that parameter. I think we
should debug
why kamailio sends the request using UDP, it is not clear, as
Daniel
pointed out it should work automatically. I think I had to do
these
manipulations because in my case the outbound proxy address
is set
On 11/29/2011 05:38 PM, Bruno Bresciani wrote:
--
Daniel-Constantin Mierla --http://www.asipto.com
Kamailio Advanced Training, Dec 5-8, Berlin:http://asipto.com/u/kat
http://linkedin.com/in/miconda -- http://twitter.com/miconda
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users In my case the transport=TLS is present in
contact header,
has the same
treatment of R-URI?
Cheers
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
mailing list
sr-users(a)lists.sip-router.org
<mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
2 Dec
2 Dec
12:48 p.m.
Hello
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.
I want all way the call is forwarded with TLS protocol.
Cheers
2011/12/1 Daniel-Constantin Mierla <miconda(a)gmail.com>
Hello,
On 11/30/11 11:59 AM, Bruno Bresciani wrote:
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.
Contact: "XXX" <sip:XXX@YYY.YYY.YYY.YYY:YYY;transport=TLS>.
as Daniel pointed out, "The contact header address is not used for routing
SIP requests, only Route headers and R-URI addresses"
In this case, I should add the transport protocol TLS on R-URI before to
forward message with t_relay function... Correct?
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.
Cheers,
Daniel
Cheers
2011/11/29 Daniel-Constantin Mierla <miconda(a)gmail.com>
On 11/29/11 6:24 PM, Bruno Bresciani wrote:
Thank's for attention Andrew
I'm reading the source code of tm module to try understand better this
behavior...
I can't understand what meaning that "the outbound proxy address is
set"... where I define this address?
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.
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...
Maybe the best is to post here an ngrep with the SIP trace of such case,
that we can see if something is wrong.
Cheers,
Daniel
2011/11/29 Andrew Pogrebennyk <apogrebennyk(a)sipwise.com>
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
listsr-users@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Dec 5-8, Berlin:
http://asipto.com/u/kathttp://linkedin.com/in/miconda -- http://twitter.com/miconda
Bruno,
the address from contact header is put into R-URI on outgoing request to
that user. This is where I catch that parameter. I think we should debug
why kamailio sends the request using UDP, it is not clear, as Daniel
pointed out it should work automatically. I think I had to do these
manipulations because in my case the outbound proxy address is set
On 11/29/2011 05:38 PM, Bruno Bresciani wrote:
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
listsr-users@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Dec 5-8, Berlin:
http://asipto.com/u/kathttp://linkedin.com/in/miconda -- http://twitter.com/miconda
In my case the transport=TLS is present in
contact header, has the same
treatment of R-URI?
Cheers
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
1:24 p.m.
Hello,
On 12/2/11 12:48 PM, Bruno Bresciani wrote:
Hello
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.
I want all way the call is forwarded with TLS protocol.
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)?
If you want to enforce always tls, then just set $du before relaying to
gateway:
$du = "sip:gatewayip;transport=tls";
There are also functions from tm where you can force tls transport (see
the readme of tm module).
If you want to send over tls only when it comes via TLS, then do the
checking
if(proto==TLS) {
# came over tls, enforce tls for outgoing to gateway
$du = "sip:gatewayip;transport=tls";
}
Cheers,
Daniel
Cheers
2011/12/1 Daniel-Constantin Mierla <miconda(a)gmail.com
<mailto:miconda@gmail.com>>
Hello,
On 11/30/11 11:59 AM, Bruno Bresciani wrote:
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Dec 5-8, Berlin: http://asipto.com/u/kat
http://linkedin.com/in/miconda -- http://twitter.com/miconda
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.
Contact: "XXX" <sip:XXX@YYY.YYY.YYY.YYY:YYY;transport=TLS>.
as Daniel pointed out, "The contact header address is not used
for routing SIP requests, only Route headers and R-URI addresses"
In this case, I should add the transport protocol TLS on R-URI
before to forward message with t_relay function... Correct?
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.
Cheers,
Daniel
Cheers
2011/11/29 Daniel-Constantin Mierla <miconda(a)gmail.com
<mailto:miconda@gmail.com>>
On 11/29/11 6:24 PM, Bruno Bresciani wrote:
--
Daniel-Constantin Mierla --http://www.asipto.com
Kamailio Advanced Training, Dec 5-8, Berlin:http://asipto.com/u/kat
http://linkedin.com/in/miconda -- http://twitter.com/miconda
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users Thank's for attention Andrew
I'm reading the source code of tm module to try understand
better this behavior...
I can't understand what meaning that "the outbound proxy
address is set"... where I define this address?
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.
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...
Maybe the best is to post here an ngrep with the SIP trace of
such case, that we can see if something is wrong.
Cheers,
Daniel
2011/11/29 Andrew Pogrebennyk <apogrebennyk(a)sipwise.com
<mailto:apogrebennyk@sipwise.com>>
Bruno,
the address from contact header is put into R-URI on
outgoing request to
that user. This is where I catch that parameter. I think
we should debug
why kamailio sends the request using UDP, it is not
clear, as Daniel
pointed out it should work automatically. I think I had
to do these
manipulations because in my case the outbound proxy
address is set
On 11/29/2011 05:38 PM, Bruno Bresciani wrote:
--
Daniel-Constantin Mierla --http://www.asipto.com
Kamailio Advanced Training, Dec 5-8, Berlin:http://asipto.com/u/kat
http://linkedin.com/in/miconda -- http://twitter.com/miconda
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users In my case the transport=TLS is present in
contact
header, has the same
treatment of R-URI?
Cheers
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) -
sr-users mailing list
sr-users(a)lists.sip-router.org
<mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
1:45 p.m.
Hello
I want to send over tls only when it comes via TLS, when some device
doesn't specify the TLS protocol on R-URI ... Thank's for your reply!!! I
wrote a other form to insert transport=tls at the kamailio.cfg, but you
wrote an easier way to update R-URI
Cheers
2011/12/2 Daniel-Constantin Mierla <miconda(a)gmail.com>
Hello,
On 12/2/11 12:48 PM, Bruno Bresciani wrote:
Hello
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.
I want all way the call is forwarded with TLS protocol.
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)?
If you want to enforce always tls, then just set $du before relaying to
gateway:
$du = "sip:gatewayip;transport=tls";
There are also functions from tm where you can force tls transport (see
the readme of tm module).
If you want to send over tls only when it comes via TLS, then do the
checking
if(proto==TLS) {
# came over tls, enforce tls for outgoing to gateway
$du = "sip:gatewayip;transport=tls";
}
Cheers,
Daniel
Cheers
2011/12/1 Daniel-Constantin Mierla <miconda(a)gmail.com>
Hello,
On 11/30/11 11:59 AM, Bruno Bresciani wrote:
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.
Contact: "XXX" <sip:XXX@YYY.YYY.YYY.YYY:YYY;transport=TLS>.
as Daniel pointed out, "The contact header address is not used for
routing SIP requests, only Route headers and R-URI addresses"
In this case, I should add the transport protocol TLS on R-URI before to
forward message with t_relay function... Correct?
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.
Cheers,
Daniel
Cheers
2011/11/29 Daniel-Constantin Mierla <miconda(a)gmail.com>
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
listsr-users@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Dec 5-8, Berlin:
http://asipto.com/u/kathttp://linkedin.com/in/miconda -- http://twitter.com/miconda
On 11/29/11 6:24 PM, Bruno Bresciani wrote:
Thank's for attention Andrew
I'm reading the source code of tm module to try understand better this
behavior...
I can't understand what meaning that "the outbound proxy address is
set"... where I define this address?
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.
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...
Maybe the best is to post here an ngrep with the SIP trace of such case,
that we can see if something is wrong.
Cheers,
Daniel
2011/11/29 Andrew Pogrebennyk <apogrebennyk(a)sipwise.com>
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
listsr-users@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Dec 5-8, Berlin:
http://asipto.com/u/kathttp://linkedin.com/in/miconda -- http://twitter.com/miconda
Bruno,
the address from contact header is put into R-URI on outgoing request to
that user. This is where I catch that parameter. I think we should debug
why kamailio sends the request using UDP, it is not clear, as Daniel
pointed out it should work automatically. I think I had to do these
manipulations because in my case the outbound proxy address is set
On 11/29/2011 05:38 PM, Bruno Bresciani wrote:
> In my case the transport=TLS is present in contact header, has the
same
> treatment of R-URI?
>
> Cheers
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
listsr-users@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Dec 5-8, Berlin:
http://asipto.com/u/kathttp://linkedin.com/in/miconda -- http://twitter.com/miconda
4553
days inactive
4556
days old
13 comments
3 participants
participants (3)
-
Andrew Pogrebennyk -
Bruno Bresciani -
Daniel-Constantin Mierla