Busy Tone Detection

[mauricio]

I make a announced call transfer but VoiceGuide dont detect when the called line is busy and wait upon the timeout occurs (in vg.ini) to take the "fail" path.

I check the modem and he says "BUSY" when i dial, but VG don't.

Im using USRobotics modems (model 2976).

Is there any parameter i must revise?

Thanks in advance

[SupportTeam]

Modems do not let you set any parameters... if the modem does not detect busy tone form the transfer destination correctly then the only option is to try another modem…

 

Waiting for a time-out when transfer destination is busy is pretty standard when using modems for announced call transfers (you're lucky to have the hookflash working for you...)

 

If you are doing call transfers it's highly recommended to get a Dialogic card.

[Guest Guest_mauricio]

The modem detects the busy tone, but IVG dont take the fail path inmediatly.

Where can i see the modem answer in the IVG?

The big problem with the Dialogic card is the cost... The USR modem cost $100 and the Dialogic board $1600!

[SupportTeam]

Could you please post a copy of VoiceGuide's Debug Printout which captures the problem, this will allow us to see what is going wrong.

(When running the script click on VoiceGuide's View menu and select 'Event Trace Log' option - any log information will then appear in this window. You must open the trace window before making the call.)

 

Dialogic cards do not cost that much. Which country are you in?

[mauricio]

I'm in Argentina!

I know DL cards cost about $495 in USA but here in Argentina, Intel sold the D4PCI from $1450 to $ 1.611!!!!

 

IVG make a call transfer to extension 16 (that extension is busy, i leave the handset pickup)

 

Here is the trace log:

 

120338,89 1 generate LINEGENERATETERM_DONE

120339,42 0 LsAwaitingCalls EV_TIMEOUT_TIMETOREINITLINE

120339,42 0 ReinitTelephony due to IDLE start

120339,42 0 tapic lineDeallocateCall(MainCall:66125) 0

120339,56 0 lineOpen(0) => 0

120339,56 0 Waiting for a call...

120339,56 0 lineOpen(0)LineHandle=65595

120340,11 1 LsXferStart EV_TAPI_GENERATE

120341,20 1 LsXferPlayVts EV_HOOKFLASHFINISHED

120341,20 1 tapic lineGenerateDigits(65903,16,0) => 0

120341,58 1 generate LINEGENERATETERM_DONE

120342,92 1 LsXferPlayVts EV_TAPI_GENERATE

120342,92 1 [Transfer Ope16] Playing (Operador.wav)

120342,98 1 PlaySoundStart ok [Operador.wav]

120347,92 1 Play End line[1] (id=852593)

120347,92 1 LsXferPlayAnn EV_PLAY_FINISHED

120347,92 1 LsXferPlayAnn EV_TIMEOUT_REPLAYMSG

120347,92 1 [Transfer Ope16] Playing (Operador.wav)

120348,00 1 PlaySoundStart ok [Operador.wav]

120352,92 1 Play End line[1] (id=857593)

120352,92 1 LsXferPlayAnn EV_PLAY_FINISHED

120352,92 1 LsXferPlayAnn EV_TIMEOUT_REPLAYMSG

120352,92 1 [Transfer Ope16] Playing (Operador.wav)

120353,00 1 PlaySoundStart ok [Operador.wav]

120357,92 1 Play End line[1] (id=862593)

120357,94 1 LsXferPlayAnn EV_PLAY_FINISHED

120357,94 1 LsXferPlayAnn EV_PLAY_FINISHED

120357,94 1 tapic lineGenerateDigits(65903,!,0) => 0

120358,41 1 generate LINEGENERATETERM_DONE

120359,47 1 LsXferPlayAnn EV_TAPI_GENERATE

120359,47 1 PlayFinishCause=CallRejected

120359,47 1 Going down Fail path (iXferType=1)

120359,91 1 LsXferStart EV_TIMEOUT_READYTOBEGINTRANSFER

 

Here, IVG takes the "FAIL" path (extension 16 was busy), and dial next number

 

120359,91 1 [Transfer Ope17] Announced Transfer to 17 (Generate)

120359,91 1 tapic lineGenerateDigits(65903,!,0) => 0

120400,38 1 generate LINEGENERATETERM_DONE

120401,44 1 LsXferStart EV_TAPI_GENERATE

120402,59 1 LsXferPlayVts EV_HOOKFLASHFINISHED

120402,66 1 tapic lineGenerateDigits(65903,17,0) => 0

120403,09 1 generate LINEGENERATETERM_DONE

120404,14 1 LsXferPlayVts EV_TAPI_GENERATE

120404,20 1 [Transfer Ope17] Playing (Operador.wav)

120404,33 1 PlaySoundStart ok [Operador.wav]

120408,25 1 dtmf 1 (65903,49,2)

120408,25 1 LsXferPlayAnn 1

120408,52 1 PlaySoundStop ok

120409,50 1 LsXferPlayAnn EV_PLAY_FINISHED

120409,53 1 LsXferPlayAnn EV_TAPI_GENERATE

120409,56 1 PlayFinishCause=CallAccepted

120409,58 1 Going down Success path (iXferType=1)

120409,66 1 Hanging up call... [Hangup Module]

120409,66 1 RecSoundStop ok

120409,67 1 PlaySoundStop ok

120409,69 1 fnHangupCall end

120409,81 1 callstate DISCONNECTED 65903,1,0

120409,83 1 LsAwaitingCalls EV_REMOTEPARTY_DISCONNECT

120409,84 1 Hanging up call...

120409,86 1 RecSoundStop ok

120409,88 1 PlaySoundStop ok

120409,92 1 fnHangupCall end

120409,92 1 callstate IDLE 65903 0 0

120409,94 1 WorkingMode@Idle=

120409,95 1 tapi Reply (LineEvReply) ok 65784 0

120410,00 1 tapi Reply (LineEvReply) ok 66365 0

120410,09 0 sys cleanup Start

120410,11 0 sys cleanup End

120410,97 1 LsAwaitingCalls EV_TIMEOUT_TIMETOREINITLINE

120410,98 1 ReinitTelephony due to IDLE start

120411,05 1 tapic lineDeallocateCall(MainCall:65903) 0

120411,20 1 lineOpen(1) => 0

120411,22 1 Waiting for a call...

120411,23 1 lineOpen(1)LineHandle=66468

 

If i make the call with "hiperterminal" the modem says "BUSY" when calling the busy extension, so, i know both modem and pbx are ok.

 

I'm a registered user of IVG and using the lastest IVG (5.1.7), in a Windows 2000 Pro PC.

Again, thanks in advance!

[SupportTeam]

If i make the call with "hiperterminal" the modem says "BUSY" when calling the busy extension, so, i know both modem and pbx are ok.

As you can see in the trace the modoem does not report busy (probably not even programmed to listen for it) when transfering a call in Voice mode:

120341,20 1 tapic lineGenerateDigits(65903,16,0) => 0

120341,58 1 generate LINEGENERATETERM_DONE

120342,92 1 LsXferPlayVts EV_TAPI_GENERATE

120342,92 1 [Transfer Ope16] Playing (Operador.wav)

120342,98 1 PlaySoundStart ok [Operador.wav]

120347,92 1 Play End line[1] (id=852593)

120347,92 1 LsXferPlayAnn EV_PLAY_FINISHED

120347,92 1 LsXferPlayAnn EV_TIMEOUT_REPLAYMSG

120347,92 1 [Transfer Ope16] Playing (Operador.wav)

120348,00 1 PlaySoundStart ok [Operador.wav]

120352,92 1 Play End line[1] (id=857593)

120352,92 1 LsXferPlayAnn EV_PLAY_FINISHED

120352,92 1 LsXferPlayAnn EV_TIMEOUT_REPLAYMSG

120352,92 1 [Transfer Ope16] Playing (Operador.wav)

120353,00 1 PlaySoundStart ok [Operador.wav]

120357,92 1 Play End line[1] (id=862593)

120357,94 1 LsXferPlayAnn EV_PLAY_FINISHED

120357,94 1 LsXferPlayAnn EV_PLAY_FINISHED

120357,94 1 tapic lineGenerateDigits(65903,!,0) => 0

120358,41 1 generate LINEGENERATETERM_DONE

120359,47 1 LsXferPlayAnn EV_TAPI_GENERATE

120359,47 1 PlayFinishCause=CallRejected

as I mentioned before:

Waiting for a time-out when transfer destination is busy is pretty standard when using modems for announced call transfers (you're lucky to have the hookflash working for you...)

[mauricio]

some is wrong... the modem answer "BUSY" but IVG dont use the modem answer.

Can IVG read the modem answer to the call? (BUSY is answered 6 seconds by modem later you make the call, at least with a communication program using AT commands.)

What parameter can i modify in VG.INI to test?

Some suggest? (please, dont tell me about buy a Dialogic Card!, really is behind our limits)

againg, a lot of thanks.

[mauricio]

Have any other timeout to set?

"Waiting for a time-out when transfer destination is busy is pretty standard when using modems for announced call transfers (you're lucky to have the hookflash working for you...)"

I modify the "AnnouncedTransfersMaxWaitTime" in "VG.INI", but it also cut the call if is not busy and the operator cant answer too fast (our PBX: 16 seconds = 4 rings).

[SupportTeam]

I modify the "AnnouncedTransfersMaxWaitTime" in "VG.INI", but it also cut the call if is not busy and the operator cant answer too fast (our PBX: 16 seconds = 4 rings).

You will need to experiment to see what setting of AnnouncedTransfersMaxWaitTime will be the best compromise for your system...