you should do that from the first place, so we do not lose time for
nothing, checking source code which is not even used. For this
combination you are on your own, it is supposed you know what you do
and have the knowledge to troubleshoot -- the relaying itself is in
the tm module, uac module just fills some structure and calls tm
function.
Cheers,
Daniel
I'm actually using kamailio's 1.5 UAC module on an
Opensips 1.6.2 :$ so I don't know if the problem could be
related to that. Anyway, here is the bad register message when
using only $uac_req(ruri)="sip:8.14.80.37:5061". Note that
the SIP part itself its correct, but the UDP destination port is
wrong:
Thanks for pointing out to the SIP traces. I found out
that it if the request is to be sent to a destination
using a port other than 5060, it is required to add the
$uac_req(ouri) parameter too:
Interesting, it should work when changing the 'ruri'
attribute as well. Can you send a sip trace with changed
r-uri for the two requests that go to wrong destination?
Thanks,
Daniel
Thanks!
Alejandro Rios Peña
DISCLAIMER: The opinions expressed are my own, and
not necessarily those of my employer.
It works great with one instance of
Asterisk, but now that I'm testing with two
Asterisk instances to load balance, and I
see a problem regarding the registration
forwarding to the second Asterisk.
I tried adding a second "uac_req_send()"
bellow the first one, but Kamailio only
sends the first request and the REGISTER
never gets to the second Asterisk: