Checking Caller Id

[fluffybunny]

I have upgraded to VG version 7 from version 6 and I have a problem now checking if CALLER ID is present.

 

I know the caller ID is not present and I am using the example in the help file to check this. i.e. I am using an Evaluate Expression mudule and the expression to evaluate is

 

$RV_CIDNUMBER

 

I have defined two paths, {true} and {false}, but the program is throwing up a program error saying the following :

 

045651.125 8 1 rv add [$RV_STARTTIME]{5/11/2007 4:56:51 AM}

045651.125 8 1 rv add [$RV_DEVICEID]{1}

045651.125 8 1 rv add [DlgcVoice]{dxxxB1C1}

045651.125 8 1 rv add [DlgcNetwork]{dxxxB1C1}

045651.125 8 1 rv add [$RV_CIDNAME]{}

045651.125 8 1 rvns add [PathApp]{C:\Program Files\VoiceGuide\}

045651.125 8 1 rvns add [scriptsPath]{e:\escrow\}

045651.125 8 1 rv add [$RV_CIDNUMBER]{}

045651.125 8 1 RunModule iLineId=1, iModuleIdx=57

045651.125 8 1 timer clear

045651.125 8 1 fn RunModule start [Evaluate,[Check_CLI],57]

045651.125 8 1 state [Check_CLI] Evaluate [$RV_CIDNUMBER]

045651.125 8 1 rv replace start: [$RV_CIDNUMBER]

045651.125 8 1 rvns [PathSysVoice]{C:\Program Files\VoiceGuide\system\voice\}[PathApp]{C:\Program Files\VoiceGuide\}[PathDataVm]{C:\Program Files\VoiceGuide\data\}[PathVgSys]{C:\Program Files\VoiceGuide\system\}[$RV_STARTTIME]{5/11/2007 4:56:51 AM}[$RV_DEVICEID]{1}[DlgcVoice]{dxxxB1C1}[DlgcNetwork]{dxxxB1C1}[$RV_CIDNAME]{}[PathApp]{C:\Program Files\VoiceGuide\}[scriptsPath]{e:\escrow\}[$RV_CIDNUMBER]{}

045651.125 8 1 rv replace end: []

045651.125 8 1 ERROR 7.0.2665.39473 RunModule : : String cannot be of zero length.

Parameter name: oldValue

at System.String.Replace(String oldValue, String newValue)

at ..(Int32 iLineId, Int32 iModuleIdx)

045651.125 8 1 rv add [Hangup Time]{5/11/2007 4:56:51 AM}

045651.125 8 1 state Hanging up call... [RunModule error]

045651.125 8 1 HangupCall_Common hCall=0

045651.140 8 1 rec RecSoundStop ok

 

 

 

I've also tried putting the $RV_CIDNUMBER in quotes but that didnt work, and I also tried to evaluate the expression 0$RV_CIDNUMBER>0 but that didnt work either.

 

How do I check if caller ID is present or not?

 

I am using VG version 7.0.2665.39473

 

Many thanks

 

Simon

[fluffybunny]

I know the caller ID is not present and I am using the example in the help file to check this. i.e. I am using an Evaluate Expression mudule and the expression to evaluate is

 

$RV_CIDNUMBER

 

 

Actually, I'm not so sure the Calling Line ID is not there. The phone company seems to think that they are supplying the Calling Line ID so it could be that VG isn't picking it up. I have tried extending the number of rings before answer to 2, 3 and 4 but with no luck.

 

Many thanks in advance.

[SupportTeam]

Could you please update to v7.0 RC2 (available from our Downloads page) and repeat the test.

 

Please post both the ktTel and vgEngine traces (especially the ktTel).

 

This new version 7.0 is installed with options to use A-Law or u-Law sound files, although it will still accept the PCM sound files.

VG's 'system' sound files will be installed as A-Law or u-Law according to selection made.

So you will need to change your sound files to match (or copy over old PCM sound files to VG's \system\voice\).

 

 

BTW.

 

You can use SOX ( from: sox.sourceforge.net ) to easily change format from PCM to A-Law or u-Law

 

here is a line from a batch file which will do the conversion for all .WAV files in current directory and will place output in subdirectory voice_ULaw:

 

FOR %%X IN (*.WAV) DO sox %%X -r 8000 -U -b -V -c 1 "voice_ULaw\%%X"

 

for A-Law use:

 

FOR %%X IN (*.WAV) DO sox %%X -r 8000 -A -b -V -c 1 "voice_ALaw\%%X"

[fluffybunny]

Many thanks for that. I'll upgrade as suggested. Do I need to uninstall the previous release first, and also should I be sleecting A-Law or u-Law voice files?

 

Many thanks

[SupportTeam]

Do I need to uninstall the previous release first,

Yes.

 

should I be sleecting A-Law or u-Law voice files?

Does not really matter if system is used on Analog lines. Only really can matter when digital T1/E1 lines are used.

 

u-Law is generally used in U.S. and A-Law is generally used in rest of the world.