Call Trannsferring Using Avm Fritz Pci Isdn Card

[jbrings]

Have made a script - autoattendant type - I then used the modeul TRANFER CALL to an internal extension. We are using a LUCENT ARGENT BRANCH PBX.

 

It rings once at the detaination number and then the calling party goes to the start of the script again.

 

Any ideas?

[SupportTeam]

Looks like the transfer fails and the PBX just rings the extension again in those cases...

 

Could you please send us 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.)

[jbrings]

event log attached:

1112vgm.txt

[SupportTeam]

Have passed this report on to makers of ComISDN - the error appears to come from the TSP - and it's the ComISDN TSP that would control how the call transfer would be conducted.

[SupportTeam]

After speaking with makers of ComISDN we have come up with the changes that we believe should fix the call transfer issue which you have encountered.

 

Please update your v5.1.3 installation of VoiceGuide with the attached VGMULTI.EXE, then update the ComISDN TSP with the version released yesterday:

 

http://www.comisdn.com/ComISDN_20031112_FV.zip

 

(if above link does not work please go to http://www.comisdn.com and select Download)

 

If after updating both you are still encountering the problem please provide the VoiceGuide Trace log again.

 

Some notes from makers of ComISDN:

 

Here is a summary of the procedure for users experiencing problems

with call transfer (you can use this information on your WEB site) :

 

- Make sure that your telephone network (PBX or telecom operator) supports

call transfer. If provided by your telecom operator, make sure that this

service is activated for your line (this service may be available as an

option).

 

- Make sure that your ISDN device supports call transfer.

 

- Make sure that your telephone network and your ISDN device are configured

to use the same ISDN protocol (in Europe, most of the time this will be

Euro-ISDN (DSS1))

 

- Users may need to install the latest CAPI drivers.

 

- Users may need to update their PBX firmaware.

 

- Some legacy PBX only support "Implicit" call transfer ; Implicit call

transfer gives predictable results when a single Active call (CONNECTED) is

attached to the ISDN interface (this will always be the case with an ISDN

telephone for example) ; however, when more than one Active call is attached

to the ISDN interface, transfer may occur to the wrong active call (at the

ISDN network level, "Implicit" call transfer specify only the Held call to

be used, not the Active call ...).

To use this setting, in the ComISDN configuration dialogs, select your

"Interface", click on "Properties", then under the "Features" tab, select

"Call Hold = Network", "Call Transfer (ECT) = Network - Implicit", "Three

Party Conference (3PTY) = Network".

 

- Some legacy PBX only support call transfer when the consultation call is

in the CONNNECTED state. By default, ComISDN will operate "blind transfer"

when the call is in the Alerting state (RINGBACK).

To blind transfer only when the call is in the Active state (CONNECTED), in

the ComISDN configuration dialogs, select your "Interface", click on

"Properties", then under the "Features" tab, close to "Call Transfer (ECT)",

uncheck "Enabled on alerting". You will need to reboot (or unload and load

back the TSP) for the new settings to take effect.

 

- When the call transfer service (ECT) is not provided by the telephone

network, users may configure ComISDN to use "Hardware" based call transfer ;

this requires an ISDN device with "LineInterconnect" capabilities. You will

need to reboot (or unload and load back the TSP) for the new settings to

take effect.

To use this setting, in the ComISDN configuration dialogs, select your

"Interface", click on "Properties", then under the "Features" tab, select

"Call Hold = Hardware", "Call Transfer (ECT) = Hardware", "Three Party

Conference (3PTY) = Hardware". You will need to reboot (or unload and load

back the TSP) for the new settings to take effect.

 

- Some PBX may reject call transfer attempt with 2 external outbound calls

(security limitation, as both calls are charged and as call disconnection is

not supervised by an internal station).

 

- If still experiencing some problems, users should contact their PBX

manufacturer (or telecom operator) or the ISDN device manufacturer.

several other possibilities :

 

- User may need to download the latest AVM drivers.

 

- PBX may not support call transfer.

 

- PBX and ISDN terminal are not configured to operate with the same ISDN

protocol (in Europe, most of the time this will be Euro-ISDN (DSS1)) ->

check and configure according to recommended settings.

 

- PBX may support only "Implicit Call Transfer" -> under the configuration

dialogs, for the interface property, in the features tab :

. "Call Hold" should be set to "Network"

. "Call Transfer (ECT)" should be set to "Network - Implicit"

. "Three Party Conference (3PTY)" should be set to "Network"

Reboot your computer for the new settings to take effect.

If this did not fixed the problem :

. do not forget to revert "Call Transfer (ECT)" to "Network"

. be aware that "Implicit" transfer is a transfer operation requested to

your PBX with only reference to the held call, no reference to the ACTIVE

[DIALTONE | DIALING | PROCEEDING | RINGBACK | CONNECTED] call. So if your

ISDN interface has more than one ACTIVE call, the PBX may transfer to the

incorrect ACTIVE call. Implicit transfer was certainly designed for ISDN

telephones which usualy deal only with a single ACTIVE call. Explicit

transfer should be used with ISDN interfaces.

VgMulti.zip

[jbrings]

I have made all the changes as advised. Still no joy. Rings twice and hangs up.

 

Any more ideas? See call log attached.

 

Appreciate your efforts.

call_transfer.txt