[SR-Users] tls client to udp proxy
hiro
23hiro at gmail.com
Mon Jul 15 13:21:03 CEST 2013
I don't know the RFC well enough, but as every other protocol works I
think it's a kamailio bug.
You should be able to reproduce this, I don't think I've done anything special.
On Mon, Jul 15, 2013 at 10:48 AM, Klaus Darilion
<klaus.mailinglists at pernau.at> wrote:
> Inspect the received ACK (log $mb) and check the RURI, and Route headers.
> Maybe the show some bugs. Also, if you manually apply routing to in-dialog
> requests (e.g. forcing the send socket) make sure to not make mistakes.
>
> regards
> Klaus
>
>
> On 12.07.2013 17:52, hiro wrote:
>>
>> hi
>>
>> I have set up tls on kamailio successfully, but when I relay a TLS
>> client to an other proxy ($ru = "sip:" + $rU + "@" +
>> "127.0.0.1:5070;transport=udp";) via udp I get error messages.
>>
>> From the timing it seems like this warning always appears after I get
>> 200OK from proxy, the Invite gets sent correctly, but kamailio seems
>> to fail while sending back the ACK.
>>
>> 18(11231) WARNING: <core> [forward.c:270]: WARNING: get_send_socket:
>> protocol/port mismatch (forced udp:77.180.86.63:5060, to
>> tls:127.0.0.1:5070)
>>
>> TCP->UDP works.
>> TCP->TCP works.
>> UDP->UDP works.
>> UDP->TCP works.
>> TLS->TCP works.
>> TLS->UDP doesn't work.
>>
>> _______________________________________________
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users at lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>
More information about the sr-users
mailing list