No sound on busy / wrong number

[raasdnil]

OK... I have a weird problem.

Firstly, if I manually dial using Asterisk, everything works fine. I can make calls, I get busy signals and incorrect number notifications.

When I call with our own in house custom auto dialer, I can make calls, get busy signals and incorrect number notifications.

But when I call (manually or on autodial) with Vicidial, I can make a call and talk. All no problems. But if the number I am calling is busy, or it is a wrong number, I only get silence.

We have a few of these vicidial setups in different locations, comparing the Asterisk CLI output of a call from another one of our vicidial servers (that is working correctly) and this one, match each other line for line. The hangup event is received etc. An output of this is at the bottom of the email.

I am using astguiclient 2.0.4-142 on top of Asterisk 1.4.22 on Centos 5 with the 2.6.18 Linux kernel.

I installed using the scratch install. The only changes I did were:

1) using Asterisk 1.4 instead of 1.2 (needed for our custom app), but we use this elsewhere with vicidial with no problem

2) Didn't apply the patches listed to asterisk as it was stated only for versions 1.2.x.

Anyone got any hints or ideas on this?

The call log from the CLI follows (note, vicidial calls an external server which is our phone gateway running asterisk with a ulaw iax2 trunk, this is how we have it successfully working elsewhere).

> Channel Local/8600051@default-2482,1 was answered.
-- Executing [09898999999@default:1] AGI("Local/8600051@default-2482,1", "agi://127.0.0.1:4577/call_log") in new stack
== Manager 'sendcron' logged off from 127.0.0.1
-- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
-- Executing [09898999999@default:2] Dial("Local/8600051@default-2482,1", "IAX2/twnext/09898999999||tTo") in new stack
-- Called twnext/09898999999
-- Call accepted by 192.168.11.250 (format ulaw)
-- Format for call is ulaw
== Manager 'sendcron' logged off from 127.0.0.1
== Manager 'sendcron' logged off from 127.0.0.1
-- Hungup 'IAX2/twnext-16384'
== Everyone is busy/congested at this time (1:0/0/1)
-- Executing [09898999999@default:3] Hangup("Local/8600051@default-2482,1", "") in new stack
== Spawn extension (default, 09898999999, 3) exited non-zero on 'Local/8600051@default-2482,1'
-- Executing [h@default:1] MeetMeCount("Local/8600051@default-2482,1", "0000000000|COUNT") in new stack
== Parsing '/etc/asterisk/meetme.conf': Found
-- Executing [h@default:2] GotoIf("Local/8600051@default-2482,1", "0?kick:hang") in new stack
-- Goto (default,h,5)
-- Executing [h@default:5] Hangup("Local/8600051@default-2482,1", "") in new stack
== Spawn extension (default, h, 5) exited non-zero on 'Local/8600051@default-2482,1'
== Spawn extension (default, 8600051, 1) exited non-zero on 'Local/8600051@default-2482,2'
-- Executing [h@default:1] MeetMeCount("Local/8600051@default-2482,2", "0000000000|COUNT") in new stack
== Parsing '/etc/asterisk/meetme.conf': Found
-- Executing [h@default:2] GotoIf("Local/8600051@default-2482,2", "0?kick:hang") in new stack
-- Goto (default,h,5)
-- Executing [h@default:5] Hangup("Local/8600051@default-2482,2", "") in new stack
== Spawn extension (default, h, 5) exited non-zero on 'Local/8600051@default-2482,2'

[mflorell]

I have seen mention of issues with 1.4.22 and IAX on the mailing lists, not sure if this is your issue, but downgrading to 1.4.21.2 might be worth a try.

Have you tried putting an Answer on your gateway machine when the call comes from the VICIDIAL machine to be dialed out?