Hookflash Problem

[Marcel]

We're in the possession of a Music Telecom (now AI-LOGIX) telephony board, model: MTPCI-4, with VG 4 line Enterprise Edition version 4.8.47 with the hotfix.

It's installed on a Windows 2000 service pack 3 system that is connected to a Tenovis Integral PBX. Everything works fine except for the hookflash so we can't let the VG system put people on hold. We contacted AI-LOGIX for instructions on how to modify the hookflash length to a 150 ms value, cause that's the hookflash length our PBX needs. We've been told by AI-LOGIX that this can be done in the 'dspview' application. This piece of software that ships with the card is for testing & configuring the MTPCI-4. If we change the hookflash length here to 150 ms it is set back to 500 ms after we start VG, so it seems VG is responsible for doing this.

No matter what we do VG always seems to put the hookflash length back to 500 ms during the startup of VG.

 

 

A simple case example of our hookflash problem:

 

Mod1 -Play Module- plays a soundfile and goes to Mod2 after pressing digit 1.

Mod2- Transfer Module- should -Blind- transfer the call to line 14 on the same PBX. It only has a succes path to Mod3.

 

Mod3- Hangup Module- hangs up the call.

 

The result of this script is always a hangup of the call in Mod2 instead of the call being put on hold.

After that line 14 does ring however! So it really looks like a hookflash problem.

 

 

Below you can see the Event Trace Log that was generated during run time of this case example:

 

62413 4 tapie ring 0

62424 4 tapie callstate OFFERING 66255 0 4

62424 4 tapie linedevstate 2048 0 0

62424 4 tapie callinfo MEDIAMODE

66610 4 tapie ring 1

66610 4 Answer the call

66610 4 lineAnswer(66255) => 66256

67240 4 tapie callstate CONNECTED 66255,1,0

67240 4 WorkingModeTAPI=

67240 4 WorkingModeScript=

67250 4 tapi Reply 66256 0

67250 4 [Mod1] Playing

67250 4 [Mod1] Playing (C:\Program Files\VoiceGuide\Scripts\Internet Portal\IpWelcome.wav)

67321 4 PlaySoundStart ok [C:\Program Files\VoiceGuide\Scripts\Internet Portal\IpWelcome.wav]

67331 4 RunModule PLAY end

67331 4 tapie callinfo MEDIAMODE

67331 4 tapie callinfo MEDIAMODE

72328 4 tapie monitordigits 49 2

72338 4 LsPlayMsg [1]

77425 4 PlaySoundStop ok

77435 4 wb(66725000)

77846 4 LsXferStart EV_TIMEOUT_READYTOBEGINTRANSFER

77876 4 [Mod2] Blind Transfer to 14 (Generate)

77896 4 tapic lineGenerateDigits(66255,!) => 0

78537 4 tapie generate LINEGENERATETERM_DONE

79498 4 LsXferStart EV_TAPI_GENERATE

80499 4 LsXferPlayVts EV_HOOKFLASHFINISHED

80510 4 tapic lineGenerateDigits(66255,14) => 0

80910 4 tapie generate LINEGENERATETERM_DONE

81912 4 LsXferPlayVts EV_TAPI_GENERATE

82913 4 LsXferPlayVts EV_TIMEOUT_HANGUP

82913 4 PlaySoundStop ok

82923 4 Hanging up call...

82933 4 PlaySoundStop ok

82943 4 fnHangupCall end

83013 4 tapie linedevstate 2048 0 0

83013 4 tapie linedevstate 2048 0 0

83023 4 tapie callstate IDLE 66255 0 0

83023 4 WorkingMode@Idle=

83063 4 tapi Reply 66153 0

83944 4 LsAwaitingCalls EV_TIMEOUT_TIMETOREINITLINE

83964 4 Initialise telephony (due to IDLE)

84075 4 tapic lineDeallocateCall(MainCall:66255) 0

84115 4 Waiting for a call...

84115 4 hLine=66221

 

 

 

Big bumps on our head because of this issue!

We can't seem to figure it out.

 

Help would really be appreciated!!!!!!

 

Marcel.

[SupportTeam]

We may have to go back to AI-LOGIX on this one...

 

When VoiceGuide calls the TAPI function lineGenerateDigits (which you can see in the trace) it does not set the "dwDuration" parameter - and when that parameter is not set then the default length should be used by the TAPI driver...

 

We can see from the trace that the AI-LOGIX's TAPI driver took over 600ms to return from playing the hookflash:

 

77896 4 tapic lineGenerateDigits(66255,!) => 0

78537 4 tapie generate LINEGENERATETERM_DONE

 

Yet when playing the extension "14" it returned in 400ms - so when adding the standard gap of 100ms of silence that most devices insert in between playing successive DTMF tones it looks like the digits 1 and 4 were 150ms long each:

 

80510 4 tapic lineGenerateDigits(66255,14) => 0

80910 4 tapie generate LINEGENERATETERM_DONE

 

So it looks like you have succeeded in using the 'dspview' application to set the length of the DTMF tones being played, but not the hookflash...

So we may need to ask AI-LOGIX for better instructions on how to set the hookflash itself..

 

 

I'll attach the AI-LOGIX own TAPI driver reference document which confirms that when the "dwDuration" parameter is not set then the default length should be used by the TAPI driver. (look for section on lineGenerateDigits)

tapidevman.zip

[Marcel]

We got in contact with AI-LOGIX and I've been told that the default 500 ms hookflash length is hardcoded on the card itself.

So this value can ONLY be altered thru the TAPI.

Since Voice Guide doesn't give this hookflash parameter during the TAPI call I believe we got a serious problem here because the default 500 ms hookflash value that the MTPCI-4 card uses just won't work for our PBX that needs a 40 ms or a 120 ms hookflash.

 

Gosh, we sure hope there's a workaround for this issue cause all the inbound calls get hung-up instead of put on hold whenever the transfer module or the '!' in a play module is used.

 

Please help us!!!

 

Marcel

[SupportTeam]

Sounds like we'll have to make ensure that when using AI-LOGIX cards a call to lineGenerateDigits which asks to play the hookflash tone will also specify the hookflash length...

 

That shouldn't be hard to do - I'll ask our programmers to allow the length parameter in that call to be settable by the user (ie: you).

What is your email address?

[Marcel]

My e-mailaddress is: powdersnow@chello.nl

 

Sounds good, hope to hear from you soon.

 

Thank you for the support!

 

Marcel.

[SupportTeam]

Please add the following lines to the VG.INI's [PBX] section:

 

;Preferred Legnths of hookflash and DTMF tones.

;will be used if Generate method is selected. In milliseconds.

DurationHookflash=150

DurationDtmfTone=100

 

Then update your v4.9.0 installation with the vgmulti.exe attached.

 

This version (and v4.9.1 onwards) will use the settings in VG.INI file above as parameters to the TAPI lineGenerate function.

VgMulti_4.9.0_can_set_Generate_length.zip

[SupportTeam]

powdersnow@chello.nl wrote:

 

Dear Jenny,

 

Sorry for our delayed reaction after your prompt responses!

 

Yes, the solution you provided us with made it possible to use

the hookflash in combination with the MTPCI-4 board.

 

Thanks a lot for the excellent support!

 

Kind regards,

 

Johan

You-S-Me