Ring back when Manual Dial

[brainwhistler]

Hi,

There is a problem with my single server setup having

Asterisk 1.2.27
ViciDial 2.0.4RC2

My agent Munually Dials the number using 'Fast Dial'. when he dials the number he does not hear the ring back, therefore, he cannot recognizes if the other party's phone is ringing. He only gets the voice if the other party picks up and says hello.

I have alredy tried the 'r' flag with tTo and without tTo in the extension.conf but none worked.

The ring back works when dialing number on softphone only without ViciDial.

Any idea what's could be the issue.

Thanks

[mflorell]

What kind of trunks are you using?

Who is your carrier?

[brainwhistler]

SIP Trunk and Primus Tel is the carrier.

Ring back works when I dial through the softphone.

[mflorell]

Does the same thing happen if he dials through the Manual Dial link and the campaign MANUAL "Dial next number" method?

[avalanche]

I have the same problem with the thread owner.

Trunks: SIP
Carrier: Accela

It is not stated in this thread that the problem happens on all calls. In our case, it happens on some calls.

Does the same thing happen if he dials through the Manual Dial link and the campaign MANUAL "Dial next number" method?

Yes matt, in our case, it does.

Is this carrier related? If so, how can we resolve the issue. Any suggestions?[/quote]

[mflorell]

For manual calls we have used the ASTloop loopback trunk that we setup in VICIDIAL to Answer the call and pass it through to the real dialout trunk.

[logicalthinker]

Hi Matt,

We're having problem with the thread owner.
How to use ASTloop loopback trunk that you've mentioned? Can you show us how to do it? Thanks.

We already tried simulating using different carriers (Accela,Vitelity,Gafachi, etc), tried the 'r' option in the dial command and any other options mentioned in different forums but no to avail. The agents cannot still hear a ring until someone pick-up the phone and talk. We're very sure that this is not a provider/carrier issue.

By the way, we're using vicidial 2.0.5 and we thought that this might be an issue with the latest vicidial version since we haven't encountered this problem using the vicidial 2.0.4.

Any help or suggestions would be greatly appreciated!

Thanks