vicidial.org

We're having a problem with call monitoring using vicibox? "failed to established call, anyone can help,,thanks...

CLI Output:

[Mar 2 17:58:45] -- Executing [08600051@default:1] Dial("SIP/102-0000002b", "IAX2/ASTblind:Jz+Odx+3/DCZ@127.0.0.1:41569/68600051|55|To") in new stack
[Mar 2 17:58:45] -- Called ASTblind:Jz+Odx+3/DCZ@127.0.0.1:41569/68600051
[Mar 2 17:58:49] NOTICE[5783]: chan_iax2.c:4050 __auto_congest: Auto-congesting call due to slow response
[Mar 2 17:58:49] -- IAX2/ASTblind-11311 is circuit-busy
[Mar 2 17:58:49] -- Hungup 'IAX2/ASTblind-11311'
[Mar 2 17:58:49] == Everyone is busy/congested at this time (1:0/1/0)
[Mar 2 17:58:49] == Auto fallthrough, channel 'SIP/102-0000002b' status is 'CONGESTION'
[Mar 2 17:58:49] -- Executing [h@default:1] DeadAGI("SIP/102-0000002b", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----CONGESTION----------") in new stack
[Mar 2 17:58:49] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0


ViciBox Redux 3.1.9
ViciDial v.2.2.1
ViciDial SVN Trunk v.2.4-295 Build 110103-1135
Asterisk v.1.4.39.1-vici
no other hardware connected

describe exactly what you did to cause this?

I'm trying to monitor using 0+sessionID.

most likely ip_relay is not running. I believe we ran into this issue a few times, not sure what we did to fix it though.

ok, so to extrapolate from your description, you are using a phone registered to the system and dial 0+sessionID and this is the CLI and the call fails (you're not using any gui features for this except to acquire said sessionID)?

Can you dial the regular sessionID without the 0?

have you turned off the firewall? (is that where the ip_relay is running? inside iptables?)

a firewall can prevent ip_relay from running, but ip_relay really has nothing to do with iptables, it is a separate application that we include with ViciDial and it is installed when you run the install.pl script. Sometimes it's as simple as having the keepalive not there in the /etc/astguiclient.conf, and sometimes you have to recompile ip_relay to work on your system, although that is very rare.

experienced the same problem, cannot monitor when dialing 0 + session id. that is why i used 6 + session but what i don't like using 6 was disconnected monitoring after each call.

solved using this configurations
admin > server > Conf File Secret and change it to "test"

I do not know the logic of these but it's simply works..

I would like to bump up this post.
I've installed VERSION: 2.2.1-237 BUILD: 100510-2015 on ubuntu 10.03.2.

I can't monitor with 0 prefix or when on real time reports screen. Barge seems to work fine, also when dialing with 6 prefix it seems to work ok. But when clicking listen i get this cli output:


-- Executing [XXX*XXX*XXX*XXX*08600052@default:1] Goto("Local/XXX*XXX*XXX*XXX*08600052@default-ccba,2", "default|08600052|1") in new stack
-- Goto (default,08600052,1)
-- Executing [08600052@default:1] Dial("Local/XXX*XXX*XXX*XXX*08600052@default-ccba,2", "IAX2/ASTblind:test@127.0.0.1:41569/68600052|55|To") in new stack
-- Called ASTblind:test@127.0.0.1:41569/68600052
-- IAX2/127.0.0.1:41569-7886 is circuit-busy
[Apr 18 18:36:30] NOTICE[11469]: chan_iax2.c:4050 __auto_congest: Auto-congesting call due to slow response
-- Hungup 'IAX2/127.0.0.1:41569-7886'
== Everyone is busy/congested at this time (1:0/1/0)
== Auto fallthrough, channel 'Local/XXX*XXX*XXX*XXX*08600052@default-ccba,2' status is 'CONGESTION'
> Channel Local/XXX*XXX*XXX*XXX*08600052@default-ccba,1 was never answered.
-- Executing [h@default:1] DeadAGI("Local/XXX*XXX*XXX*XXX*08600052@default-ccba,2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----CONGESTION----------") in new stack


There is albo another problem that can be related. I can't register any IAX2 client. I get this error:
[Apr 18 18:36:29] ERROR[11473]: chan_iax2.c:4322 handle_call_token: Call rejected, CallToken Support required. If unexpected, resolve by placing address 89.xx.xx.xx.xx in the calltokenignore list or setting user user1 requirecalltoken=no

I've added requirecalltoken=no at iax-vicidial.conf but it doesn't help.

I would appreciate your support.

I've checked /etc/astguiclient.conf and ip_relay is there as keepalive

is ip_relay also RUNNING?

Dear Williamconley,
Than you for the reply. The ip_relay is not running on the system. When executing it manually by relay_control start i get an error:
./relay_control start
starting up ip_relay services
done

./relay_control: 57: ip_relay: not found
./relay_control: 57: ip_relay: not found

Following this (http://www.wlug.org.nz/CommonErrors) howto I got this output after "strings /usr/share/astguiclient/ip_relay/ip_relay |grep \.so":
/lib/ld-linux.so.2
libc.so.6
setsockopt
could not create listen sockets!
could not create bind tcp listen socket!
could not create bind udp listen socket!
could not create listen on tcp socket!
could not create tcp target socket!
could not connect tcp target socket to %d.%d.%d.%d:%d!
could not create target udp socket!
could not connect udp target socket to %d.%d.%d.%d:%d!

you may want to look at the stock vicibox method of installaing ip_relay.

i note that you said you get an error, but in some linux packages the method of starting the software can make a difference. try to find it in the install script and in the startup routine and duplicate them (but manually so YOU can see the output). you could also look at your logs after a reboot (and perhaps your mail) to see if ip_relay is tossing an error.

i've never had any problem with ip_relay so i've never had to "fix" it. try (just taking a pot shot):

Code: Select all

cd /var/log
grep ip_relay * -R -n

also of note is that your grep command for .so resulted in matching the "so" in "socket" and it was searching the ip_relay script itself, not output from an attempted start of the software ... so the result is not apparently related to an error (just a list of strings containing "so" in the original script file).

keep Tryin'

I had similar issue on goautodial

Try this, worked for me

yum install glibc-devel

great post jkidd. Helping out with only 60 posts. Excellent