Problem With Voiceguide.commandlink In 7 Resolved

[Guest ILAsoft]

Could not find a solution to my problem anywhere- running 7.0.2 and VoiceGuide.CommandLink not working. Accidentally replaced it with vgServices.CommandLink... That worked!

 

If VoiceGuide.CommandLink is not working for you, try vgServices.CommandLink

 

Enjoy!

 

Ilya Pupko

First Advantage Corporation

IT PM & Technical Lead

[SupportTeam]

That is correct. In v7 the COM object is called vgServices.

 

The translation is done automatically inside VoiceGuide's VBScript modules before running them, so old VoiceGuide scripts work without any modifications.

 

But external programs using the VoiceGuide's COM interface would need to change the COM object name from "VoiceGuide" to "vgServices" to work with v7.

[Guest ILAsoft]

The translation is done automatically inside VoiceGuide's VBScript modules before running them, so old VoiceGuide scripts work without any modifications.

 

Just FYI: the translation was not working inside VG either. I had to do it manually...

[SupportTeam]

OK, thanks for the tip, we'll have a look at this.

[ktruk]

Support: why change it? Aren't you just asking for upgrade trouble? Does it need to change?

[SupportTeam]

The decision was made to not use the actual product name (VoiceGuide) in the interface names in v7.

 

The migration of VoiceGuide's 'Run VBScript' module based VBScripts themselves would not be affected as VoiceGuide will be making the translation of VBScripts from VoiceGuide.CommandLink to vgServices.CommandLink before running them.

 

External programs using the COM interface will need to be modified at this stage to use the vgServices.CommandLink interface name.

 

What is probably going to happen given the user feedback about this v7 change is to include the VoiceGuide.CommandLink named interface for backward compatibility in v7 as well - whilst directing all new users to use the vgServices.CommandLink COM interface.

[Guest ILAsoft]

Similar problem: $RV_LINESINUSE (referred to in the help file) doesn't get converted by the latest version of VG (left as $RV_LINESINUSE). Please advise.

[SupportTeam]

Looks like $RV_LINESINUSE was not yet included in v7.

 

Please send an email to support@voiceguide.com with a link to this thread and your registration details and a v7 build which supports $RV_LINESINUSE will be provided to you immediately.

 

Otherwise $RV_LINESINUSE should be supported in the next v7 release.

[Guest ILAsoft]

While my company is arguing with the vendor, proving that we did purchase the correct license so that I can get a version that works and can continue working on that piece of code, I moved on to testing the transfer piece...

 

 

First I tried the hookflash, and am I right to understand that I will never get that to work as I'm using a 23 (24) line T1 and it only works on Analog? Also, the dial and conference (which would require additional license for the Dialer?) did not work for me either, and that one I don't understand at all... Please advise:

 

183848.279 16 70 calling FindFreeLine

183848.279 16 0 Search for free lines in list [dxxxB1C1,dxxxB1C2,dxxxB1C3,dxxxB1C4] in LineID range [0-70] src=XferDialAndConf

183848.279 16 4 dial reserving: found [dxxxB1C1] in selection list [,dxxxB1C1,dxxxB1C2,dxxxB1C3,dxxxB1C4,]

183848.279 16 70 dial found free dev=1 (LineId=4)

183848.279 16 70 dial sCidSentThisCall= (pre RV replace)

183848.279 16 70 ERROR 7.0.2788.33800 RvProcessAndReplace : Object reference not set to an instance of an object.

at ..(Int32 iLineId, String& strIn)

183848.279 16 70 dial sCidSentThisCall= (post RV replace)

183848.279 16 70 no on-hold file specified to play

183848.279 16 4 state dialing ,13035551234, (for conference with dtiB1T23)

183848.279 16 70 setting CONNECT_IMMEDIATELY as iXferType = XT_DC_BLIND

183848.279 16 4 lineMakeCall(,13035551234,,CONNECT_IMMEDIATELY) =>

183848.279 16 70 timer set 60 EV_TIMEOUT_GOTOMODULE

183848.279 16 70 outbound leg is dti device. Connect immediately.

183848.279 16 70 conf TwoCalls_Bridge 70<=>4 (dtiB1T23<=>dtiB1T1)

183848.279 16 70 play PlaySoundStop ok

183848.279 16 4 play PlaySoundStop ok

183848.279 16 70 rvns add [TsRoutedTo]{4}

183848.279 16 4 rvns add [TsRoutedTo]{70}

183848.279 16 4 rvns add [Conf_DevName_1]{dtiB1T23}

183848.279 16 4 rvns add [Conf_LineId_1]{70}

183848.279 16 4 rvns add [Conf_LineNbr_1]{23}

183848.279 16 4 rv add [Conf_DevName_2]{dtiB1T1}

183848.279 16 4 rv add [Conf_LineId_2]{4}

183848.279 16 4 rv add [Conf_LineNbr_2]{1}

183848.279 16 70 rvns add [Conf_DevName_1]{dtiB1T23}

183848.279 16 70 rvns add [Conf_LineId_1]{70}

183848.279 16 70 rvns add [Conf_LineNbr_1]{23}

183848.279 16 70 rv add [Conf_DevName_2]{dtiB1T1}

183848.279 16 70 rv add [Conf_LineId_2]{4}

183848.279 16 70 rv add [Conf_LineNbr_2]{1}

183848.279 16 70 TsRoute dtiB1T23<=>dtiB1T1 call

183848.279 16 70 TsRoute dtiB1T23<=>dtiB1T1 SC_FULLDUP:

183848.279 16 70 state [Transfer Test] bridged with dtiB1T1 (incoming leg)

183848.279 16 4 state [Transfer Test] bridged with dtiB1T23 (outgoing leg)

183848.388 8 4 ev Dialogic 2086,GCEV_DISCONNECTED,2086,0,0,GCRV_CCLIBSPECIFIC,event caused by cclib specific failure,Unknown error

183848.388 8 4 ScriptEventCode GCEV_DISCONNECTED, code=2086, state=1911

183848.388 8 4 LsXfer_8_WaitEndCall_OutLeg : 2086(), [GCEV_DISCONNECTED], 2086,0,0,GCRV_CCLIBSPECIFIC,event caused by cclib specific failure,Unknown error

183848.388 8 4 hanging up this line as event is of disconnect or busy or idle type

183848.388 8 4 rv add [Hangup Time]{8/29/2007 6:38:48 PM}

183848.388 8 4 state Hanging up call... [xfer_8]

183848.388 8 4 HangupCall_Common hCall=0

183848.388 8 4 play PlaySoundStop ok

Edited 09/12/2007 06:39 AM by ILAsoft
changed number to 13035551234

[SupportTeam]

While my company is arguing with the vendor, proving that we did purchase the correct license so that I can get a version that works and can continue working on that piece of code,

That must mean that you have purchased VoiceGuide through one of our resellers, and not from our site directly (?) If you continue to have problems please contact sales@voiceguide.com with information form where you have purchased the license and what issues have you encountered.

 

am I right to understand that I will never get that to work as I'm using a 23 (24) line T1 and it only works on Analog?

Yes. Hookflash works only on Analog. It will not work on T1 ISDN lines.

 

The Dial and Conference should work, and in the trace provided we can see that VoiceGuide did make an outgoing call on line dxxxB1C1:

 

183848.279 16 4 lineMakeCall(,13035551234,,CONNECT_IMMEDIATELY) =>

 

but soon after that the Dialogic card received the "DISCONNECTED" ISDN message:

 

183848.388 8 4 ev Dialogic 2086,GCEV_DISCONNECTED,2086,0,0,GCRV_CCLIBSPECIFIC,event caused by cclib specific failure,Unknown error

 

The "ktTel" trace would be able to show us more information on this "DISCONNECTED" ISDN message.

 

Have you tried placing outgoing calls to the 13035551234number directly to establish whether this T1 line can connect you to this number?

 

You can use Dialogic's ISDIAG tool to test this.

 

It is possible that you may need to make some modifications to the outgoing ISDN SETUP message to be able to place outgoing calls. Please see: http://www.voiceguide.com/vghelp/source/ht...igisdnsetup.htm

Edited 09/12/2007 06:39 AM by SupportTeam

[Guest ILAsoft]

I was able to schedule a call through the dialer and it came through. The dial option in VG didn't even really come through at all- it was just "hanging" for a while and then would hangup... Am I just setting-up the transfer wrong?

 

[Transfer Test]

Type=Transfer Call

DispSize=69

Txt=Transfer call to the selected extension.

strXferDestExt=,13035551234,

iXferType=31

sXfer2ndLegLinesListFile=dxxxB1C1,dxxxB1C2,dxxxB1C3,dxxxB1C4

iXferBridgeCallsWhen=6

sXferPlayWhileDialing=

sXferAnnounceMsg=C:\Program Files\VoiceGuide\System\voice\aa_xfernoanswer.wav

sXferOptions=

on {success} goto [Hangup]

on {fail} goto [say Thanks...]

on {timeout 60} goto [Hangup]

 

I've attached both logs. Lines around 511 - 599 in vgEngine and 2392-2398 in ktTel are the ones from the scheduled call out of Dialer and then down below are the ones from VG transfer itself...

 

Please advise...

Edited 09/12/2007 06:40 AM by ILAsoft

[SupportTeam]

Could you please do the dial and conference transfer test again (the supplied ktTel trace appears to be missing some information...) and post the traces as before.

[Guest ILAsoft]

Here are complete logs from today's try- it's still failing...

 

Please advise as soon as possible, the script is complete and ready for go live, just waiting for the transfer functionality.

 

Thanks!

[SupportTeam]

The call into the system arrived on the last channel of the T1 and the outgoing call was attempted on the first channel.

 

Lets try sending the call out on a different channel and see it that makes any difference

 

Can you try specifying a list of channels on that T1 which can be used for the outgoing calls which does not include the first channel. Eg. specify this for the channel list:

 

dtiB1T8,dtiB1T9,dtiB1T10,dtiB1T11

 

or this will select channels 8-11 as well:

 

dxxxB3C1,dxxxB3C2,dxxxB3C3,dxxxB3C4

[Guest ILAsoft]

Used "dxxxB3C1,dxxxB3C2,dxxxB3C3,dxxxB3C4" with the same result- VG hangs-up after several second of trying to transfer me...

[SupportTeam]

Would it be possible for us to have a look at this machine using a remote access service like logmein.com?

 

If that machine can access the internet then please go to www.logmein.com from that machine and setup remote access using the logmein.com ervice and please forward the login details by email to support@voiceguide.com

[SupportTeam]

Looks like the issue on this system was that the telephone number specified in the "Dial and Conference" transfer included some commas as part of the telephone number.

 

Including commas (or other non-numeric characters) in a telephone number used to dial out on an ISDN line will cause the call to fail as the telephone company’s switch will treat such a number as an invalid.

 

Commas can only be used on analog lines. On analog lines commas can be used to indicate that a pause should be used before dialing the following digit.

 

Guess this issue would have been easier to spot if we were looking at the actual VoiceGuide script, rather then at traces. Traces have many commas to separate functions arguments etc. so a couple of extra ones which were in the wrong place went unnoticed...

[Guest ILAsoft]

Issue resolved, thanks to the VoiceGuide Support [support@voiceguide.com]:

Please do not use any commas and or other non-numeric characters and try the transfer again.

 

Even though the help file on transfer mentions that "When specifying the number you can use the commas ',' to indicate pauses in the dialing sequence", it seems to be the case only for PBX transfers, not Dialogic.

[SupportTeam]

Just to clarify:

 

Commas can only be used on analog lines. On ISDN lines using a comma within the telephone number will result in an error and the call will fail.

 

We will add an appropriate note in the Help file regarding this as well.