Can't I Just Use A Pbx Blind Transfer To Make A 3 Way Conference C

[Guest galonga]

our pbx just requires to send a flash > number to call and flash 7 to do a conference call

 

so can't we just type those codes in the pbx blind transfer phone field?

 

we tried that and it seems to work: the first phone rings, then the 2nd, and we are able to talk to the 2nd. however, the 1st rings just once and then stops, so we think it's just a flash time issue.

 

we have an ISA dialogic board and what we are trying to do is record the sales calls, but we've found the conference call option too confusing so we wonder if that method would work?

 

thank you for your support

[SupportTeam]

If you select "PBX Blind Transfer" then VoiceGuide will do the hookflash and then dial the number specified and then hangup.

 

If you do not want VoiceGuide to hangup then you need to select the "3-Way Call" option - VoiceGuide will then stay on the line after dialing the number after the hookflash.

 

You can just use a Play module to send the hookflash and digits. See if specifying something like this as the 'sound file to play' the Play module will work:

 

!,1234,!,7

 

What Dialogic card are you using?

[Guest galonga]

We tried the play module and got exactly the same result as the regular hookflash method we were trying: that is the 1st caller gets a ring, is able to speak for like 1/2 a second, then the call is hung and the 2nd caller rings and is able to talk as much as he wants.

 

As for the 3 way call, the 1st phone rings briefly (no use trying to pick it up), then the 2nd phone rings, then you hear a mix of a busy tone + the 2nd caller speaking + the pbx hold on music , then nobody hears anything even though the call is happening as shown by the pbx: so it's a mess.

 

What we are trying to accomplish is just to record the conversation. Our board is a D/41D-k.

 

 

 

If you select "PBX Blind Transfer" then VoiceGuide will do the hookflash and then dial the number specified and then hangup.

 

If you do not want VoiceGuide to hangup then you need to select the "3-Way Call" option - VoiceGuide will then stay on the line after dialing the number after the hookflash.

 

You can just use a Play module to send the hookflash and digits. See if specifying something like this as the 'sound file to play' the Play module will work:

 

!,1234,!,7

 

What Dialogic card are you using?

 

[SupportTeam]

Which version of VoiceGuide are you using on this system?

 

Please post the scripts which you are using and the traces from VoiceGuide when the scripts are running.

 

 

 

Enable logging by setting the log levels to 10 in VG.INI as per below:

[Log]

 

VoiceGuide=10

Then restart VG and make a test call which demonstrates the problem.

 

Trace files will be created in VG's \log\ subdirectory.

 

Please post the traces and the VoiceGuide script used.

 

When posting traces/scripts please .ZIP them up and post them as attachments.

[Guest galonga]

We are using version 5.2.5049

 

For this test, we put the number 35!25!7 in the phone number and chose "PBX Blind Transfer"

 

35 is the 1st phone number, !25 is the pbx code to check if the other phone # is available and !7 is the code to add it to the conference: that's how it works. BTW, the PBX 3 way conference call works if we dial those codes above using regular phones.

 

When we run that, the 1st phone rings quickly, then the 2nd phone rings, and then after some seconds the caller can only hear the 2nd phone.

 

I'm sending the code and logs attached as requested. Thanks.

 

 

 

Which version of VoiceGuide are you using on this system?

 

Please post the scripts which you are using and the traces from VoiceGuide when the scripts are running.

 

 

 

Enable logging by setting the log levels to 10 in VG.INI as per below:

[Log]

 

VoiceGuide=10

Then restart VG and make a test call which demonstrates the problem.

 

Trace files will be created in VG's \log\ subdirectory.

 

Please post the traces and the VoiceGuide script used.

 

When posting traces/scripts please .ZIP them up and post them as attachments.

0925vgm.zip

[SupportTeam]

We are using version 5.2.5049

Please change to VoiceGuide v6 (or v7). You will never get call transfers to work properly if you are trying to control the Dialogic card through it's TAPI drivers.

 

For this test, we put the number 35!25!7 in the phone number and chose "PBX Blind Transfer"

 

35 is the 1st phone number, !25 is the pbx code to check if the other phone # is available and !7 is the code to add it to the conference: that's how it works. BTW, the PBX 3 way conference call works if we dial those codes above using regular phones.

 

When we run that, the 1st phone rings quickly, then the 2nd phone rings, and then after some seconds the caller can only hear the 2nd phone.

Sounds like hookflash time is too long. Please read: http://www.voiceguide.com/vghelp/source/ht...lltransfers.htm

 

[Guest galonga]

Sounds like hookflash time is too long. Please read: http://www.voiceguide.com/vghelp/source/ht...lltransfers.htm

 

 

That was our idea from the beginning: what we don't understand is that if that was the case shouldn't ALL transfers fail? Unless conference calls need a better timing or something like that?

[SupportTeam]

When the issued hookflash is too long for the PBX/Switch then the PBX/Switch hangup the call.

 

This is what you are seeing here. The number dialed after the hookflash is just treated by the PBX/Switch like a normal outgoing call.

[Guest galonga]

we tried different flash values (higher and lower) in the Phone and Modem Options in window's control panel, and the only thing that seemed to change was the ring time: lower values seemed to make the 1st phone ring a smaller time

 

the board is in an old k6 mainboard running windows 2003

 

btw: we did restart voiceguide after each new value

 

 

When the issued hookflash is too long for the PBX/Switch then the PBX/Switch hangup the call.

 

This is what you are seeing here. The number dialed after the hookflash is just treated by the PBX/Switch like a normal outgoing call.

 

[SupportTeam]

Please change to using VoiceGuide v6 and set the hookflash length in VoiceGuide's Config.xml file.

[Guest galonga]

in order to use v6 we'd have to pay for an update (at least that's what we got from sales)

 

considering that we would only do that because with version 5 we'll never get call transfers to work properly doesn't seem fair

 

if you can arrange a patch to fix that or a free update (remember we are not interested in updating: we are only doing it because you said so) then it'll be fair

 

 

 

 

Please change to using VoiceGuide v6 and set the hookflash length in VoiceGuide's Config.xml file.

 

[SupportTeam]

v5 codes work with v6. The same code can be used in v5 and v6.

 

The UniqueIDs generated by v5 and v6 would also be the same.

 

Maybe you were enquiring about an upgrade to v7?

 

If you can email to support@voiceguide.com your email address (reference this thread) we can lookup the emails on the system and see what emails were sent to you and what they contained.

[Guest galonga]

we downloaded and installed version 6, messed around with just about any flash time there is, and it made absolutely no difference as with version 5

 

one thing we have not still been answered is if it is possible indeed to use a regular blind transfer (or the "play" function) to do a conference call, or we HAVE to use the conference call to do that

 

we did try with both options however and the option that showed less worse results was the blind call

 

if we do use the conference call, we still have to type !35!25!7 as we'd do with the blind call I imagine?

 

 

v5 codes work with v6. The same code can be used in v5 and v6.

 

The UniqueIDs generated by v5 and v6 would also be the same.

 

Maybe you were enquiring about an upgrade to v7?

 

If you can email to support@voiceguide.com your email address (reference this thread) we can lookup the emails on the system and see what emails were sent to you and what they contained.

 

[SupportTeam]

OK, let take this step by step.

 

First step would be to get the hookflash timing right.

 

Use a script which just does this:

 

1. after answering the call plays some sound file

2. does a hookflash

3. plays some other sound file

4. hangs up.

 

This will let you see if the hookflash works or not.

 

If the hookflash works then the caller will be placed 'on-hold' by the PBX and will not hear the second sound file played (caller will hear some music instead or whatever the PBX is playing to calls placed on-hold).

 

A sample script is attached.

 

When the hookflash is working we can then move onto the dialing of other numbers etc.

 

 

 

hookflash_test.vgs

[Guest galonga]

ok, this is what happens:

 

1 - callers hears "1.wav"

2 - caller then hears a little bit of the PBX's on hold sound

3 - caller then hears "2.wav"

4 - caller then hears "2.wav" again

5 - call hangs up

 

If you can find out what this means it will mean a lot to us: we REALLY need to record buyer's calls

 

 

 

OK, let take this step by step.

 

First step would be to get the hookflash timing right.

 

Use a script which just does this:

 

1. after answering the call plays some sound file

2. does a hookflash

3. plays some other sound file

4. hangs up.

 

This will let you see if the hookflash works or not.

 

If the hookflash works then the caller will be placed 'on-hold' by the PBX and will not hear the second sound file played (caller will hear some music instead or whatever the PBX is playing to calls placed on-hold).

 

A sample script is attached.

 

When the hookflash is working we can then move onto the dialing of other numbers etc.

 

[SupportTeam]

It's strange that the caller hears only a little bit of the 'on-hold' sound.

 

For nhow long is the caller placed on-hold? Less the one second? 2-3 seconds?

 

Only one hookflash would have been sent by the Dialogic card to the PBX, which would have been what places the caller on hold. Not sure why the PBX would then not keep caller on hold permanently.

 

When you issue the hookflash from the PBXs analog extension does the caller get put on hold only for a very short time as well? ie. does the caller then hears only a little bit of the PBX's on hold sound as well?

 

What Brand/Model is that PBX?

[Guest galonga]

The caller hears more or less 1 second of the PBX on hold music.

 

We are sending attached the log files, should you need them.

 

The PBX is made is an "IntelBras" Pointer 4x16: I don't think you know that brand, but it is well considered in Brazil.

 

 

 

It's strange that the caller hears only a little bit of the 'on-hold' sound.

 

For nhow long is the caller placed on-hold? Less the one second? 2-3 seconds?

 

Only one hookflash would have been sent by the Dialogic card to the PBX, which would have been what places the caller on hold. Not sure why the PBX would then not keep caller on hold permanently.

 

When you issue the hookflash from the PBXs analog extension does the caller get put on hold only for a very short time as well? ie. does the caller then hears only a little bit of the PBX's on hold sound as well?

 

What Brand/Model is that PBX?

0928tw.zip

[SupportTeam]

When you issue the hookflash from the PBXs analog extension does the caller get put on hold only for a very short time as well? ie. does the caller then hears only a little bit of the PBX's on hold sound as well?

[Guest galonga]

Running your script and calling directly the PBX extension number for the dialogic card leads to this

1 - Caller hears 1.wav

2 - Caller gets a busy signal

3 - Caller then hears nothing

 

No PBX On Hold sound is heard ever.

 

I'm sending the logs attached.

 

 

When you issue the hookflash from the PBXs analog extension does the caller get put on hold only for a very short time as well? ie. does the caller then hears only a little bit of the PBX's on hold sound as well?

 

[SupportTeam]

Running your script and calling directly the PBX extension number for the dialogic card leads to this

...weren't you calling the PBX extension directly beforehand? How were you dialing into the system in the previous tests?

 

1 - Caller hears 1.wav

2 - Caller gets a busy signal

3 - Caller then hears nothing

This suggests the hookflahs is too long and the PBX has hung up the call...

 

[Guest galonga]

Running your script and calling directly the PBX extension number for the dialogic card leads to this

...weren't you calling the PBX extension directly beforehand? How were you dialing into the system in the previous tests?

 

we were using our script (the one we sent you): it works fine

 

 

1 - Caller hears 1.wav

2 - Caller gets a busy signal

3 - Caller then hears nothing

This suggests the hookflahs is too long and the PBX has hung up the call...

 

 

as said, our idea since the beginning. however, once again, shouldn't that affect ALL transfers instead of just some particular ones like the one in your script and conferences?

[SupportTeam]

Most PBXs do not allow transfers on outgoing calls.

 

Were you trying to do the transfer after making an outgoing call beforehand?

 

What happens when you issue the hookflash from a normal telephone attached to the PBX? Does the caller get placed on hold (permanently) and can hear the PBXs on hold music?