Problem With Call Transfer

[ktruk]

Hi, I'm having a problem with transferring calls behind a UK PBX, using a dialogic D4PCI both blind transfer and announced transfer seem to ring once, then give up. The hook-flash is set to 100ms and seems to work, but the ext just rings, once, then hangs up. The debug trace below seems to show that some sort of timer is expiring immediately. I believe the PBX just needs a flash, ext num to work, so no fancy dial strings, but thinking that maybe the Dlg is seeing the on-hold signal as disconnect-tone, but can't seem to pin this down. I am a reg user of latest version (5.2.3066). Any clues please?

 

Debug:

220105.67 7 LsPlayMsg EV_PLAY_FINISHED

220105.69 7 timer set 10 EV_TIMEOUT_HANGUP

220105.69 7 timer set 0 EV_TIMEOUT_GOTOMODULE

220105.69 7 ScriptEventCode 9002 iLineState=1101

220105.69 7 LsPlayMsgFinished EV_TIMEOUT_GOTOMODULE

220105.69 7 timer clear

220105.69 7 timer set 0.4 EV_TIMEOUT_READYTOBEGINTRANSFER

220106.13 7 timer fired EV_TIMEOUT_READYTOBEGINTRANSFER

220106.13 7 ScriptEventCode 9012 iLineState=1900

220106.13 7 LsXferStart EV_TIMEOUT_READYTOBEGINTRANSFER

220106.13 7 timer set 30 EV_TIMEOUT_ANNOUNCED_TRANSFER_ATTEMPT_TOOK_TOO_LONG

220106.13 7 [Transfer Call 21] Blind Transfer to 20 (Generate)

220106.14 7 tapic lineGenerateDigits(65929,!,100) => 0

220106.83 7 generate LINEGENERATETERM_DONE

220106.83 7 timer set 1 EV_TAPI_GENERATE

220107.89 7 timer fired EV_TAPI_GENERATE

220107.89 7 ScriptEventCode 9602 iLineState=1900

220107.89 7 LsXferStart EV_TAPI_GENERATE

220107.89 7 timer set 1 EV_HOOKFLASHFINISHED

220108.98 7 timer fired EV_HOOKFLASHFINISHED

220108.98 7 ScriptEventCode 9200 iLineState=1905

220108.98 7 LsXferPlayVts EV_HOOKFLASHFINISHED

220108.00 7 tapic lineGenerateDigits(65929,20,100) => 0

220109.33 7 generate LINEGENERATETERM_DONE

220109.33 7 timer set 1 EV_TAPI_GENERATE

220109.94 7 callstate DISCONNECTED 65929 0 0

220109.94 7 ScriptEventCode 9250 iLineState=1905

220109.94 7 LsXferPlayVts EV_REMOTEPARTY_DISCONNECT

220109.94 7 rv add [Hangup Time]{11/03/2005 22:01:09}

220109.95 7 Hanging up call...

220109.95 7 RecSoundStop ok

220109.95 7 PlaySoundStop err=0

220109.95 7 timer set 2 EV_TIMEOUT_WAITFORIDLEAFTERLINEDROP

220109.95 7 fnHangupCall end

220109.00 7 linedevstate 2048 0 0

220109.00 7 callstate IDLE 65929 0 0

220109.00 7 WorkingMode@Idle=

220109.00 7 timer clear

220109.00 7 timer set 1 EV_TIMEOUT_TIMETOREINITLINE

220110.02 7 tapi Reply (LineEvReply) ok 65793 0

220111.08 7 timer fired EV_TIMEOUT_TIMETOREINITLINE

220111.08 7 ScriptEventCode 9008 iLineState=900

220111.08 7 LsAwaitingCalls EV_TIMEOUT_TIMETOREINITLINE

220111.08 7 ReinitTelephony due to IDLE

220111.08 7 tapic lineDeallocateCall(MainCall:65929) 0

220111.23 7 lineOpen(7)=>

220111.23 7 Waiting for a call...

220111.23 7 LineHandle=65844

220111.23 7 timer set 3 EV_TIMEOUT_ATERIDLE_ALLOWOUT

220111.25 0 dial start any summary:|7:rdy=0|8:dok=0|9:dok=0|10:dok=0|

220114.53 7 timer fired EV_TIMEOUT_ATERIDLE_ALLOWOUT

220114.53 7 ScriptEventCode 9013 iLineState=900

220115.25 0 dial start any summary:|7:idx=0|8:dok=0|9:dok=0|10:dok=0|

[SupportTeam]

Maybe your PBX does not allow 'blind' transfers?

 

Some PBXs require that the destination extension pick up the phone before the person/machine doing the transferring can hang up.

 

Have you tried using 'Announced' transfers?

[ktruk]

PBX blind transfers are supported.

 

After much investigation, and rereading all the VG notes, the clue was in the HELP file ! Which states that if the hook-flash is too long the PBX hangs up the 1st ext, while calling the second. This is the issue!

 

Now, I need a 100ms hook-flash. If I can get a 100ms hook-flash out of my dialogic card, then all will be fine. This is the real problem....

 

I am using a second-hand "D4PCI Euro" card with SR5.5.1 drivers (build 2600) and have been setting the TSP values and restarting the computer from power-up. I have set a range of hook-flashes in the dialog TSP settings file but exactly the same result. I have set a values of 1, 2, 5, 10, 20, 50 with 10 supposed to give 100ms. NONE of the values have resulted in the HF time changing. I have even resorted to hooking up an oscilloscope to the line and can confirm that the HF never changes from 500ms. When I hook a plain handset, set for TimedBreak recall then a 100ms Recall (flash) works fine.

 

I have been thru the VG.INI file and noted that the transfer mode is set to "GENERATE" and that the HF time of 100 set in the VG is "ignored by dialogic cards".

 

The TSP has a check box for "perfect call" this is cleared.

The "globalCall package was installed when the card was installed".

The DCM configuration parameteres are set as follows:

 

------------------------

FirmwareFile = ""

ParameterFile = ""

TSFFileSupport = ""

DisconnectTone="Yes"

 

Country = "United Kingdom"

Protocol = "PROT_BTCALLSTREAM"

Digital Signalling = "TS16_SIG"

Analog Signalling = "SIG_HF"

FreqRes = "FREQRES_HIGH"

DialPulseDetection = "DPD_NONE" (was generic, tried both)

 

TSFFile = ""

 

DCM Version: MS Windows 2000 5.1 Build 2600

SR5.1.1 Version DNA5, Build 30, No Service Packs

 

-------------------------

 

Now, I know this is not a VG problem, but I could do with a pointer on the Dialogic side. I have no Dialogic support available to me. I have attached a text file with my TSP settings. I wondered in the Minimal LCOFF value affects this? it was set to 50 but the dialogic help suggests 5 - Again I tried both, but to no avail.

 

I have also played with the PBX settigs, but decided to clear all of them. Again, no changes to the HookFlash time.

 

I really need to get this working - any help you can offer with this appreciated !!

 

The first most basic question is: Does D4PCI-Euro support 100ms flash, and if so , how?!

d41cfg.txt

[ktruk]

Oh, by the way, I am using Windows XP. Your help-file notes that I may need to use the PRM file to set hook-flash time. So, I am looking into this. I have 4 "UK" prm files on my system: UK_41D, UK_41E, UK_41H & UK_300.

 

Is there any way I can lookup which one is being used? or is there a way to set it in the drivers somewhere?

 

Thx - Tim.

[ktruk]

Okay, I set a one-parameter PRM in the DCM. I copied one of my "country files" to a temp file, deleted all parameters except PARAMETER 52 which is set to 10. I saved the file, set the filename in the ParameterFile = setting in the Misc Tab of the DCM and bingo - it works.

 

My reasoning for the above, is that the default parameters will be set somewhere else and this one parameter will overide the hook-flash time without affecting the others whatever they are and wherever they are set.

 

If there is anything wrong with this, can someone let me know?

 

Otherwise I have blind-transfers working, all I need next is the announced transfer...

 

Thx - Tim.

[ktruk]

Why is this such a struggle? Wouldn't it be great if there was some sort of idiots guide to setting transfers? I have waded thru dozens of posts and so many problems... so many hours!

 

Anyway, I have blind transfer working as stated previously, but when I setup for Announced transfer, then the D4PCI hears the dial tone after hook-flash on the transferred line as disconnect, so hangs the line, connecting both calls without announcement. I cannot seem to get a setting where it won't do this. So, for debugging, I set different disconnect tones in the TSP to "disable" it, and now, the announcement loops on the called ext. So, is there a way to overcome this disconnect tone, like in the TSP or something in the VG.INI for transfers?

 

My PBX manual states that:

DialTone is: 440hz +/-5% and 350hz +/- 5% continuous

NU Tone: 425Hz +/- 15Hz. <--- is this disconnect?

 

Can you recommend any settings in the TSP to pick the NU tone only? (is NU=Number Unobtainable?) - I am using settings similar to the settings in the attached file higher up in the post.

 

Now, my SystemPhone Handset is swallowing the "1" digit to accept the call, but there is no mention of why or what it is doing with it, in fact any digit is swallowed, but if I press 1, the calling phone is hungup, after this I can hear any subsequent digits, so I guess the Handset is doing this on purpose! Switching to a "non-systemphone" and pressing "1" does accept the call.

 

So, it looks like I am up and running after a fashion. If you can help differentiate between Dial Tone and Disconnect tone , I would be very grateful.

 

Thx - Tim.

[SupportTeam]

Glad to hear the hookflash transfers are working. Looks like what was happening before was that the 500ms hookflash was causing the call to be hung up and subsequent dialing was just calling the extension direct as if it were a new call...

 

As far as tone detection:

 

The Dial tone has a similar frequency component to NU tone - so there can be a false detection of NU tone when Dial tone is present, but not the other way around (Dial tone would not be falsely detected when NU tone is played as there is no 350Hz component)

 

I'd set the 'tone ON' length of the Dial tone to be shorter then the 'tone ON' length of the NU tone.

 

That way if the Dial tone is present then the tone detection system will return "Dial" before returning "NU"...

[ktruk]

Thx for followup. Where/how do I set this? I only have 2 tabs in the TSP each with 2 freq settings. I thought this only set disconnect? You say set shorter time for Dial-tone, but which tab? and both tones are continuous, so on/off time. Help! bushed and clueless right now! chrz - tim.

[SupportTeam]

Looks like you will need to set up a .TSF file to specify the Dial tone...

 

Anyway, I thought that the transfer was working OK after the hookflash was adjusted... if it is working then why do you still want to set up the tones configs?

[ktruk]

Because I have had to "break" the disconnect tone detection in order for it not to hangup. However, this means it doesn't hangup for any script, not just transfers, which is no good. However, it proves that the announced transfers/conferences work in theory, which what I needed to know.

 

So, my next challenge is: get the disconnect tone set to allow timely hangups while rejecting dial-tone to allow transfers.

 

Oh lordy, when I think I could have had this done in a few hours... its been DAYS!

 

So, how do I go about creating a TSF (Tone Set File?)? And will this definately allow me to accept disconnect tones, while rejecting dial tones? And does this work with the TAPI VG ? Or should I be using Dialogic VG?

 

And finally, what is "Perfect Call"? (yes I know not directly related!)

 

Thx again - Tim.

[SupportTeam]

Because I have had to "break" the disconnect tone detection in order for it not to hangup.

With hookflash transfers you would at most hear the dial tone for a split second (just after hookflash and before 1st digit of destination extension is dialed).

 

If you are getting the 'disconnect' tone mistakenly detected during that time then you should ensure that the ON time for that tone is set to at least a second.

 

Perfect Call is Dialogic's system of determining if the outgoing call has been answered and by what it has been answered - a Human or an Answering Machine.

[ktruk]

It doesn't seem to be "split-second" timing but I do agree with your reasoning. Here is the bit of debug-trace:

 

130739.45 8 timer clear

130739.45 8 timer set 0.4 EV_TIMEOUT_READYTOBEGINTRANSFER

130739.88 8 timer fired EV_TIMEOUT_READYTOBEGINTRANSFER

130739.88 8 ScriptEventCode 9012 iLineState=1900

130739.88 8 LsXferStart EV_TIMEOUT_READYTOBEGINTRANSFER

130739.88 8 timer set 15 EV_TIMEOUT_ANNOUNCED_TRANSFER_ATTEMPT_TOOK_TOO_LONG

130739.88 8 [CSTransferCall] Announced Conference to 30 (Generate)

130739.89 8 tapic lineGenerateDigits(66270,!,100) => 0

130740.16 8 generate LINEGENERATETERM_DONE

130740.16 8 timer set 1 EV_TAPI_GENERATE

130741.20 8 timer fired EV_TAPI_GENERATE

130741.20 8 ScriptEventCode 9602 iLineState=1900

130741.20 8 LsXferStart EV_TAPI_GENERATE

130741.20 8 timer set 0.1 EV_HOOKFLASHFINISHED

130741.31 8 timer fired EV_HOOKFLASHFINISHED

130741.31 8 ScriptEventCode 9200 iLineState=1905

130741.31 8 LsXferPlayVts EV_HOOKFLASHFINISHED

130741.33 8 tapic lineGenerateDigits(66270,30,100) => 0

130741.67 8 generate LINEGENERATETERM_DONE

130741.67 8 timer set 1 EV_TAPI_GENERATE

130742.52 8 callstate DISCONNECTED 66270 0 0

 

Now, am I reading this right? Timing wise from the 41.20 point the flash has been generated and then 41.31 to timeout from vg.ini has cleared, then at 41.67 to extention digits are issued... then at 42.52 disconnect issued? (ie: 1.3 seconds elapsed from hook-flash start?)

 

If above correct, then I need my TSP set for at least 1.5 seconds of disconnect tone or more? - Anyway of "speeding" this up - say not using generate?

[ktruk]

Okay, pushing disconnect tone out to 3 seconds allows me to get transfers and disconnect detection - so its working now.

 

But 3 seconds is a long time on toll-free calls !! And 3 seconds disconnect on all calls add up to a lot of time, so, bottom-line here, what is the fastest way to effect a reliable transfer? while lowering the disconnect timing? Shaving just a second off would help! What settings in the VG.INI and Dialogic TSP or PRM files can I set to reduce this overhead please?

 

Thx - Tim.

[SupportTeam]

The time from start of dialing the hookflash till end of dialing the destination extension/number digits is 1.8 seconds:

130739.89 8 tapic lineGenerateDigits(66270,!,100) => 0

130740.16 8 generate LINEGENERATETERM_DONE

....

130741.33 8 tapic lineGenerateDigits(66270,30,100) => 0

130741.67 8 generate LINEGENERATETERM_DONE

 

The 1 second pause after dialing the hookflash is built in as you need to give the PBX/Switch some time after dialing the hookflash and before dialing the destination extension/number number.

 

hookflash transfers will always take a minimum of 1.5 seconds - that's their limitation. For fast immediate transfers you should be using "Dial and Conference" - connection time there is only as long as it takes to dial the destination extension/number digits, and if using Digital lines then the connection is instant.

[ktruk]

Well what is the "PauseAfterHookFlash" VG.INI setting for then? My testing seems to contradict your fixed 1 second statement. Looking at a debug trace suggests that a timer is set using this timeout, which controls the delay. Anyway, the other options are closed to me at this time, and this is working now, even if it less than perfect.

[SupportTeam]

Well what is the "PauseAfterHookFlash" VG.INI setting for then?

You can see in the trace above which of the delays is regulated by PauseAfterHookFlash:

 

130741.20 8 timer set 0.1 EV_HOOKFLASHFINISHED

130741.31 8 timer fired EV_HOOKFLASHFINISHED

 

Changing the PauseAfterHookFlash value will alter that delay (restart of VG is needed after changing setting in VG.INI file in order for the new values to be used).

 

The delay immediately after the hookflash;

 

130740.16 8 timer set 1 EV_TAPI_GENERATE

130741.20 8 timer fired EV_TAPI_GENERATE

 

is set in the current version to 1 second and you cannot change that.

 

The upcoming update to VG will drop the 1 second delay and allow you to just the PauseAfterHookFlash VG.INI setting.