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.
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.
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