Transfers on D/4PCI

[bailsson]

I have a Dialogic D/4PCI-EURO (purchased from you) and together with VG 5.1.5 originally installed on a Win XP machine which worked off and on for a few weeks (totally unreliable!).

 

Having taken the advice given in other posts it has now been installed on installed on a clean freshly formatted PC running a new installation of Win 2000 SP2, VG 5.1.7, Dialogic SR 5.1.1 and nothing else. (& a Panasonic TD-816AL PBX)

 

The problem is that I get a disconnect tone/reorder tone whenever the card attempts to transfer a call - I guess the hookflash used by the card is too long.

 

A caller being transferred (announced) to say extension 202 by the dialogic card (at 305) the reorder tone/disconnect tone

 

Meanwhile extension 202 will ring and the call recipient will hear the message generated by the dialogic card, then of course there will be no caller at the other end.

 

Without the '!' in the dial string the initial caller hears the numbers being dialed to the extension without any further progress with the actual transfer of the call.

 

Changing the Flash length setting on the Dialogic card doesn't make any difference (it shows on config settings - but doesnt seem to alter the output)

 

Call log follows

 

012920.74 5 linedevstate 2048 0 0

012920.74 5 callstate OFFERING 66288 0 4

012920.75 5 Could not obtain handle to kill process. (new call) 972, 0

012920.75 5 Answer the call at 8/01/2004 1:29:20 AM

012920.76 5 lineAnswer(66288) => 66253

012920.77 5 callinfo CALLEDID

012920.77 5 callinfo ORIGIN

012920.77 5 ring 0

012921.30 5 callstate CONNECTED 66288,1,0

012921.30 5 WorkingModeTAPI@Connected=

012921.30 5 WorkingModeScript@Connected=

012921.34 5 Inband detection not enabled

012921.34 5 StartLoadedVgs at 8/01/2004 1:29:21 AM

012921.35 5 tapi Reply (LineEvReply) ok 66253 0

012921.35 5 [Play 1] Playing

012921.35 5 [Play 1] Playing (C:\Program Files\VoiceGuide\system\voice\10.wav)

012921.38 5 PlaySoundStart ok [C:\Program Files\VoiceGuide\system\voice\10.wav]

012921.38 5 RunModule PLAY end

012922.12 5 wb(57110100)

012922.18 5 Play End line[5] (id=571101)

012922.19 5 LsPlayMsg EV_PLAY_FINISHED

012922.24 5 dtmf 2 (66288,50,2)

012922.25 5 LsPlayMsgFinished 2

012922.59 5 LsXferStart EV_TIMEOUT_READYTOBEGINTRANSFER

012922.59 5 [ANNOUNCE 201] Announced Transfer to 201 (Generate)

012922.61 5 tapic lineGenerateDigits(66288,!,50) => 0

012923.45 5 generate LINEGENERATETERM_DONE

012924.42 5 LsXferStart EV_TAPI_GENERATE

012924.53 5 LsXferPlayVts EV_HOOKFLASHFINISHED

012924.55 5 tapic lineGenerateDigits(66288,201,50) => 0

012924.84 5 generate LINEGENERATETERM_DONE

012925.75 5 LsXferPlayVts EV_TAPI_GENERATE

012925.75 5 fn PlaySoundStartNumbers TsfrCallFrom.wav, TsfrAskAccept.wav, , Digits

012925.77 5 sVbsFunctionToUse=Digits

012925.84 5 Started SayNumber VBScript OK. (C:\Program Files\VoiceGuide\data\vbs_5_SayNumber.vbs)

012925.96 5 cl Play_Start C:\Program Files\VoiceGuide\system\voice\TsfrCallFrom.wav,,C:\Program Files\VoiceGuide\system\voice\TsfrAskAccept.wav

012925.99 5 PlaySoundStart ok [C:\Program Files\VoiceGuide\system\voice\TsfrCallFrom.wav,C:\Program Files\VoiceGuide\system\voice\TsfrAskAccept.wav]

012931.92 5 dtmf 1 (66288,49,2)

012931.92 5 LsXferPlayAnn 1

012931.98 5 PlaySoundStop ok

012932.89 5 LsXferPlayAnn EV_PLAY_FINISHED

012932.90 5 LsXferPlayAnn EV_TAPI_GENERATE

012932.90 5 PlayFinishCause=CallAccepted

012932.91 5 Success path not defined - hanging up (iXferType=1)

012933.91 5 LsXferPlayAnn EV_TIMEOUT_HANGUP

012933.91 5 Hanging up call...

012933.92 5 RecSoundStop ok

012933.93 5 PlaySoundStop ok

012933.93 5 fnHangupCall end

012933.97 5 linedevstate 2048 0 0

012933.97 5 callstate IDLE 66288 0 0

012933.98 5 WorkingMode@Idle=

012933.99 5 tapi Reply (LineEvReply) ok 66543 0

012934.94 5 LsAwaitingCalls EV_TIMEOUT_TIMETOREINITLINE

012934.94 5 ReinitTelephony due to IDLE start

012934.95 5 tapic lineDeallocateCall(MainCall:66288) 0

012935.11 5 lineOpen(5) => 0

012935.11 5 Waiting for a call...

012935.12 5 lineOpen(5)LineHandle=66031

 

Look forward to your reply.

 

(note it didnt seem to make any difference to the outcome with or without the FP1 installed).

 

Thanks

Michael Bails

[SupportTeam]

Changing the Flash length setting on the Dialogic card doesn't make any difference (it shows on config settings - but doesnt seem to alter the output)

Did you restart the Dialogic service after making the changes?

The Dialogic service needs to be restarted before the new setting will take effect.

(Best to just restart the PC after making changes to TSP config).

 

Have you tried setting the flash length setting to very low value - eg: 1.

 

If none of the above works can you also plz try changing in VG.INI file the setting TransferControl_TelBoards to be:

 

TransferControl_TelBoards=TAPI

 

Then restart VG and try making a simple blind transfer...

[bailsson]

(Best to just restart the PC after making changes to TSP config).

 

Mate, I've been quite particular about that and neither that or switching

to the TAPI setting in VG.ini has made any difference at all.

 

In the log posted with the original query, can you confirm the length of the hookflash? - it was set at 50 in the config settings.

 

Thanks

[bailsson]

Success at last! - the solution, however, came from outside the box and may be of some interest to other users experiencing a similar problem.

 

http://www.tek-tips.com/viewthread.cfm?SQI...SPID=936&page=1

 

According to Mr Peabody a PBX expert in that forum - There are three specific timers associated with the dialing of an extension:

 

1. Delay time after flash and before 1st digit of the extension is dialed

2. Inter-digit time (delay between each digit)

3. DTMF Length (length of each DTMF)

 

All three could cause reorder tone if dialed too quickly.

 

Solution - I made these times more generous in my Dialogic Config and to my utter amazement it worked.

 

(NB I also made a point of detecting the board every time I went in to change the config settings).

 

(pps. i'll need to arrange a re-register my Voice Guide now that it is on a new PC)

 

Many Thanks

[SupportTeam]

In the log posted with the original query, can you confirm the length of the hookflash? - it was set at 50 in the config settings.

 

The length of the hookflash can be roughly estimated from the timestamps in the log file's messages. In the log file we can see:

 

012922.61 5 tapic lineGenerateDigits(66288,!,50) => 0

012923.45 5 generate LINEGENERATETERM_DONE

 

so about 840 milliseconds elapsed between VoiceGuide instructing Dialogic to issue a hookflash and Dialogic informing VG that hookflash has completed.

 

We've found that usually there is about a 200-300ms delay taken up by Dialogic's own internal processing of the hookflash command (this is most likely due to Dialogic's internal guard times between various events) so based on the trace I'd say that the hookflash has lasted a bit over half a second...

 

Half a second is a long hookflash - most PBX will hang up is the hookflash is half a second.

 

The Dialogic's default setting of 50 will produce a half a second hookflash - that is why the Dialogic's "Flash time" setting in the TSP usually needs to be set to a setting of about 10 (sometimes even 8 or lower) in order for the hookflash to be recognised...

 

Dialogic's "Flash time" setting is in 10ms units - so a setting of 10 indicates to Dialogic to send 100ms long hookflashes...

[SupportTeam]

Solution - I made these times more generous in my Dialogic Config and to my utter amazement it worked.

Could perhaps post the settings that you currently have on your system?

You can just press the "Save as text" button in the bottom right corner of the Dialogic TSP configuration applet and then post the resulting text file here...

[bailsson]

Oops sorry about the delay, Dialogic TSP config file follows. Times are a little on the generous side, but I'm not game to tweak em just yet.

 

Many Thanks for your help

 

Michael B

d41cfg.txt