Hello,
On 4/11/11 5:49 PM, Alejandro Rios P. wrote:
Hi Daniel
You may want to kill me but I'll be honest,
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
Hi Daniel
You may want to kill me but I'll be honest, 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 SI
Hello,
On 4/8/11 6:14 PM, Alejandro Rios P. wrote:
Hello Daniel
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:
$uac_req(ouri)="sip:" + $var(ast
Hello Daniel
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:
$uac_req(ouri)="sip:" + $var(asterisk_ip) + ":" + $var(asterisk_port);
$uac_req(our
Hello,
On 4/8/11 12:28 AM, Alejandro Rios P. wrote:
Hi all,
I am testing the scenario described here:
http://kb.asipto.com/asterisk:realtime:kamailio-3.1.x-asterisk-1.6.2-astdb
It works great with one instance of Asterisk, but now that I'm testing
with two Asterisk instances to load balanc
Hi all,
I am testing the scenario described here:
http://kb.asipto.com/asterisk:realtime:kamailio-3.1.x-asterisk-1.6.2-astdb
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 forwardin
