SOLVED Manage to break XiVO - No incoming Calls Now

[Bart]

Not sure what happened. XiVO was working fine last night. Now today I have a problem with all incoming calls started failing... Not sure what happened or why.

VERBOSE[20781][C-00000000] pbx.c: Executing [2019177778@from-extern:1] Set("SIP/VITEL-IN-00000000", "XIVO_BASE_CONTEXT=from-extern") in new stack
VERBOSE[20781][C-00000000] pbx.c: Executing [2019177778@from-extern:2] Set("SIP/VITEL-IN-00000000", "XIVO_BASE_EXTEN=2019177778") in new stack
VERBOSE[20781][C-00000000] pbx.c: Executing [2019177778@from-extern:3] GotoIf("SIP/VITEL-IN-00000000", "?:action") in new stack
VERBOSE[20781][C-00000000] pbx_builtins.c: Goto (from-extern,2019177778,5)
VERBOSE[20781][C-00000000] pbx.c: Executing [2019177778@from-extern:5] Gosub("SIP/VITEL-IN-00000000", "did,s,1(1,)") in new stack
VERBOSE[20781][C-00000000] pbx.c: Executing [s@did:1] Set("SIP/VITEL-IN-00000000", "XIVO_DSTNUM=2019177778") in new stack
VERBOSE[20781][C-00000000] pbx.c: Executing [s@did:2] Set("SIP/VITEL-IN-00000000", "XIVO_CONTEXT=from-extern") in new stack
VERBOSE[20781][C-00000000] pbx.c: Executing [s@did:3] Set("SIP/VITEL-IN-00000000", "XIVO_PRESUBR_GLOBAL_NAME=DID") in new stack
VERBOSE[20781][C-00000000] pbx.c: Executing [s@did:4] Set("SIP/VITEL-IN-00000000", "XIVO_INCALL_ID=1") in new stack
VERBOSE[20781][C-00000000] pbx.c: Executing [s@did:5] Set("SIP/VITEL-IN-00000000", "__XIVO_CALLORIGIN=extern") in new stack
VERBOSE[20781][C-00000000] pbx.c: Executing [s@did:6] AGI("SIP/VITEL-IN-00000000", "agi://127.0.0.1/callerid_extend") in new stack
WARNING[20781][C-00000000] res_agi.c: Connecting to '127.0.0.1:4573' failed for url 'agi://127.0.0.1/callerid_extend': Connection refused
WARNING[20781][C-00000000] res_agi.c: Couldn't connect to any host. FastAGI failed.

More AGI failures after the above - so some how AGI got corrupted?

Any ideas?

Bart

 

[ou812]

I too am having intermittent issues with my voip.ms account failing over on some calls then fine a few seconds later. I tried switching to 5080 and peer instead of friend but no change.

Gary

 

[billsimon]

Not sure what happened. XiVO was working fine last night. Now today I have a problem with all incoming calls started failing... Not sure what happened or why.

...
VERBOSE[20781][C-00000000] pbx.c: Executing [s@did:6] AGI("SIP/VITEL-IN-00000000", "agi://127.0.0.1/callerid_extend") in new stack
WARNING[20781][C-00000000] res_agi.c: Connecting to '127.0.0.1:4573' failed for url 'agi://127.0.0.1/callerid_extend': Connection refused
WARNING[20781][C-00000000] res_agi.c: Couldn't connect to any host. FastAGI failed.

More AGI failures after the above - so some how AGI got corrupted?

The error says the connection was refused. So is the AGI server listening on 4573 (use "netstat -pan | grep 4573" to find out) and are there any iptables rules in place that would prevent the connection on localhost? (Usually not)

 

[Bart]

Did some more testing and I believe the problem (at least for me) is xivo-agid (shown in monitor tab) won't start properly (show 'un-monitored').
# telnet localhost 4573 => unable to connect

# ps -ax | grep java
11346 pts/0 S+ 0:00 grep java

# netstat -pan | grep 4573 => returns nothing

# service xivo-agid status
● xivo-agid.service - xivo-agid server
Loaded: loaded (/lib/systemd/system/xivo-agid.service; enabled)
Active: failed (Result: exit-code) since Mon 2016-08-08 10:38:28 PDT; 8s ago
Process: 12206 ExecStart=/usr/sbin/xivo-agid (code=exited, status=0/SUCCESS)
Process: 12205 ExecStartPre=/usr/bin/install -d -o xivo-agid -g xivo-agid /var/run/xivo-agid (code=exited, status=0/SUCCESS)
Main PID: 12213 (code=exited, status=1/FAILURE)

Aug 08 10:38:28 answerdb.com systemd[1]: xivo-agid.service: main process exited, code=exited, status=1/FAILURE
Aug 08 10:38:28 answerdb.com systemd[1]: Unit xivo-agid.service entered failed state.

Added TCP 4573 to firewall = no joy

 

[wardmundy]

Paging @Sylvain Boily. You might also want to post this on the XiVO Forum. Lots of good help on XiVO internals there. If it is a bug, that will also get the developers attention.

 

[Bart]

Yep - Posting there... One user ask me to try a few things, but no luck yet

@Sylvain Boily

 

[Sylvain Boily]

Looks like you have your answer on xivo forum ;-)

http://projects.wazo.community/boards/1/topics/7181?r=7198#message-7198

 

[Bart]

Yes, thanks Guys,
The problem was self inflicted when I adding logging for faxing. Don't do that. I also realize xivo is not as forgiving as PIAF version. Make a mistake with PIAF it seems to ignore it and moves on and not make it stop working. However the xivo forum was able to zero in to the problem. I just wish I understood xivo as well

Bart

 

[fizadmin]

Why are all the xivo related links broken?

 

[Sylvain Boily]

Hello, change xivo.io to wazo.community.

 

[fizadmin]

Ok, thanks - why did this change happen?

Also, maybe the admin of this forum should try to make a comprehensive edit to all references of divorce and change them to Waco (a quick find/replace in the database can take care of that)

 

[Sylvain Boily]

Hello, please check here. http://blog.wazo.community/introducing-wazo.html#introducing-wazo