Sorry, here it is:
root@kamailio:/etc/kamailio# kamctl dispatcher dump
SET_NO:: 1
SET:: 1
URI:: sip:192.168.1.102:5060;transport=tcp flags=AP priority=0
attrs=weight=100
On Sun, Jul 24, 2016 at 7:40 PM, SamyGo wrote:
> I asked for "kamctl dispatcher dump". 'show' only
I asked for "kamctl dispatcher dump". 'show' only prints the table.
On Jul 24, 2016 18:38, "Tickling Contest"
wrote:
> Thanks, Sammy. I fixed the error re: transport on Kamailio, but now
> nothing is sent as the dispatcher doesn't seem to work as expected by me.
>
Thanks, Sammy. I fixed the error re: transport on Kamailio, but now nothing
is sent as the dispatcher doesn't seem to work as expected by me. Here's
the output you requested, any help is appreciated:
root@kamailio:/etc/kamailio# kamctl dispatcher show
dispatcher gateways
Hey,
Can you show whats the output of the following commands on Kamailio server:
"kamctl dispatcher dump"
"netstat -pln | grep kamailio"
Send the output of the second command from asterisk server as well i.e
"netstat -pln | grep asterisk"
Looking at the error it seems like you are trying to
Hey guys,
I dug a little deeper and I found these logs in /var/log/kamailio where
192.168.1.102 is my asterisk server:
ul 24 14:25:32 kamailio /usr/sbin/kamailio[3726]: ERROR: tm [ut.h:343]:
uri2dst2(): no corresponding socket for af 2
Jul 24 14:25:32 kamailio /usr/sbin/kamailio[3726]: ERROR: tm
I corrected an error with my dispatcher configuration and now, I do hit the
code where
ds_select_dst ("1", "4")
is no longer null.
However, while the xlog I added says uac_req_send () is called, nothing is
sent. The xlog prints out the value of $uac_req(hdrs) as
Contact:
Thanks, guys!
Sammy, I tried your code in REGFWD, but unfortunately, it does not forward
anything to Asterisk. I can confirm this because it keeps going into the
else clause in the REGFWD (which I added to confirm). My current REGFWD
looks like this:
route[REGFWD] {
If you're using Kamailio as a registrar, then it would make the most sense
to also use it as your outbound proxy for Asterisk.
This would mean whenever Asterisk needs to dial an extension, it would
instead make a SIP call to your Kamailio instance which would then perform
the lookup, forking, and
Hi Tickles,
a) Have you tried doing this on Asterisk realtime ? for any regular direct
registering extension w/o kamailio(even before kamailio) ? If an extension
registers to one asterisk the rest of the boxes would know where to contact
this extension via realtime-db ? I'd say give that a try
Hello,
When using Kamailio with the dispatcher module for Asterisk load balancing,
I am offloading REGISTERs to Kamailio (works fine), but would like to
forward the REGISTERs to Asterisk so that outgoing calls from Asterisk will
be possible. I know this is not strictly necessary (e.g., just use
10 matches
Mail list logo