Outdial_new Issues, Have Problems With <vg> Vars

[Guest newpop1]

Hello, I have this entry, the SPEAKTEXT variable does not come into VG properly. In the script I have a SAY module to say what is in the SPeakText variable but it says some of the text and then at the end start saying "backslash voiceguide" and other weird things that are not even in the outdial entry. I tried removing the "()" and period but same result. Is there a limite on <RV> size? Help? (ver. 5.2.3063)

 

Thanks

 

<OutDialEntry><PhoneNumber>9999999</PhoneNumber><OnAnswer>g:\Program Files\VoiceGuide\Scripts\MVDriverLine\CallReminderHuman.vgs</OnAnswer><RV>[speakText]{Juliet cries these words into the night, having just met and fallen in love with Romeo of the Montague family, sworn enemy of her own (Capulet) family. This famous line has been misunderstood through popular history, with comedic interpretations show}[PhoneNumber]{999999999}[cId]{1}[LoginName]{NAMEJERE}[CallTime]{0819}[sentT

me]{0952}</RV>

</OutDialEntry>

[SupportTeam]

Firstly, please update to latest version of VoiceGuide.

 

If the problem persists please post the trace:

 

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 newpop1]

1)HELP!!!! Hello, I upgraded to latest version of VG for TAPI as requested and now VG won't display my 8 lines anymore, only 4 are displayed and we are getting errors now. We have 2 4-line dialogic boards and I looked at how the OLD vg.ini we manually setup and we modified the VG.ini and even replaced it with the old config and still VG won't display all lines when we do DISPLAY ALL LINES. Config wizard will display all 8 Analog lines, but VG only shows the first 4 TAPI devices. Also, there are errors in the LOG file I attached.

 

We went from having a small issue to having our system down, please help with the VG config first.

 

2)As far as the outdial_new.txt, it did not help at all to upgrade to the new version. If you see variable SPEAKTEXT in the LOG, shows with weird stuff at the end that the say module says. In addition if we add more RV variables AFTER "SpeakText", they never load into the script.

 

Thanks

 

<OutDialEntry>

<PhoneNumber>15551112601</PhoneNumber>

<OnAnswer>g:\Program Files\VoiceGuide\Scripts\MVDriverLine\CallReminderHuman.vgs</OnAnswer>

<RV>[PhoneNumber]{15551112601}[cId]{1}[LoginName]{USERNAME}[CallTime]{0819}[sentT

me]{1710}[speakText]{Juliet cries these words into the night, having just met and fallen in love with Romeo of the Montague family, sworn enemy of her own Capulet family This famous line has been misunderstood through popular history, with comedic interpretations show}</RV>

</OutDialEntry>

vg.zip

[Guest newpop1]

One more thing, after I upgraded the other server I am getting "registration invalid", VG won't load anymore, how do I get this back, I do not have the original name and serial number? Can you please email us the registration code? it is for the 4 line Ent edition and we bought it under [removed]. Can you please email the registration code again? We are down at this time, please help.

 

Thanks

Edited 04/22/2007 03:17 AM by newpop1
registration details removed

[Guest newpop1]

Hello, I got VG to run again and to register properly but only by installing the latest 6 version and using the dialogic mode instead of TAPI. One server is working ok, but the primary is having the following problem. It has a dialogic board with 4 lines. Script defined in config.xml file answers line ok and scripts works as it used to. Then it hangs up, says waiting for call and then I see that the script runs again and picks up the line. I attached the log it created. 2 of the 4 lines have this behavior. This was not happening with previous 5 version and TAPI. In fact the other PC which has the same dialogic boards and same script, are working fine.

 

Any ideas on how to make this work? After this is figured out I want to come back to the outdial_new problem. I just have to restore service to our users asap.

 

Thanks

Loop.zip

[SupportTeam]

Could you please post a copy of VoiceGuide's 'tw' Trace Logs which captures the problem, this will allow us to see what happened.

 

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

[Log]

ktTel=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.

 

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

 

 

 

 

 

214525.43 2 state Hanging up call... [Default Handler 20: DISCONNECT_TAPI1]

214525.45 2 HangupCall_Common hCall=2

214525.46 2 rec RecSoundStop ok

214525.46 2 play PlayStop ok

214525.46 2 timer set 2 EV_TIMEOUT_WAITFORIDLEAFTERLINEDROP

214525.46 2 fnHangupCall end

214525.46 2 event TDX_CST, iCode=134 state=900

214525.48 2 LsAwaitingCalls EV_UNKNOWN_134

214525.48 2 tw PlayEnd 2 442093

214525.48 2 play end id=442093, (current ID)

214525.48 2 event EV_PLAY_FINISHED, iCode=8001 state=900

214525.48 2 LsAwaitingCalls EV_PLAY_FINISHED

214525.48 2 tw DialogicEvent 129,TDX_PLAY,442093,0,0,,,

214525.49 2 event TDX_PLAY, iCode=129 state=900

214525.49 2 LsAwaitingCalls EV_UNKNOWN_129

214525.51 2 tw DialogicEvent 135,TDX_SETHOOK,0,0,0,DX_ONHOOK,,

214525.51 2 event TDX_SETHOOK, iCode=135 state=900

214525.51 2 LsAwaitingCalls EV_UNKNOWN_135

214525.51 2 event callstate IDLE 2 1,0,0

214525.52 2 WorkingMode@Idle=

214525.52 2 set LineState().hCall = 0 LineEvCallState-LINECALLSTATE_IDLE

214525.52 2 timer clear

214525.52 2 rec RecSoundStop ok

214525.54 2 play PlayStop ok

214525.54 2 rv add [CallEndTime]{4/21/2007 9:45:25 PM}

214525.54 2 on-hangup script:[]

214525.54 2 timer set 0.1 EV_TIMEOUT_TIMETOREINITLINE

214525.60 2 timer fired EV_TIMEOUT_TIMETOREINITLINE

214525.60 2 event EV_TIMEOUT_TIMETOREINITLINE, iCode=9008 state=900

214525.60 2 init atidle reinit : start

214525.60 2 init atidle reinit iConferenceOtherLegLid=-1

214525.60 2 init atidle reinit : reset all LineState variables

214525.60 2 timer set 2 EV_TIMEOUT_AFTERIDLE_ALLOWOUT

214525.62 2 state Waiting for a call...

214525.65 2 event callstate OFFERING 2 2,0,0

214525.65 2 script interpretor: VgMulti v6.0.3310

214525.65 2 fired OFFERING event to listeners

214525.65 2 set LineState().hCall = 2 in LINECALLSTATE_OFFERING

214525.66 2 cid CallerID vars set (in 'offering' event) [,,]

214525.66 2 call AnswerTheCallIfAllowed from LINECALLSTATE_OFFERING

214525.66 2 rings=0, min rings before answer=1 (iCallerIdHasArrived=0)

214525.66 2 tw ring 1

214525.66 2 ring time since last ring event (sec): 0.00

214525.66 2 rings=1, min rings before answer=1 (iCallerIdHasArrived=0)

214525.68 2 should answer as number of rings reached

214525.68 2 rv clear all

214525.68 2 init LineState ResetAtStartOfNewCall.

214525.68 2 answering the call (,,,0)

214525.68 2 timer clear

214525.70 2 tw DialogicEvent 134,TDX_CST,0,0,0,DE_RINGS,ET_RON,

214525.71 2 event TDX_CST, iCode=134 state=6001

214525.71 2 LsModuleTransition : 134, [TDX_CST]

214526.32 2 tw DialogicEvent 135,TDX_SETHOOK,0,0,0,DX_OFFHOOK,CALL_INBOUND,

214526.32 2 event TDX_SETHOOK, iCode=135 state=6001

214526.34 2 LsModuleTransition : 135, [TDX_SETHOOK]

214526.34 2 event callstate CONNECTED 2 256,0,0

214526.34 2 LineEvCallState_Connected hDevice=2 params=256,0,0

214526.34 2 WorkingModes tapi= script= LineState().iState=6001

214526.34 2 Inband detection not enabled

214526.35 2 StartLoadedVgs at 4/21/2007 9:45:26 PM (VgMulti v6.0.3310)

214526.35 2 set LineState().iVgsIdx=1

214526.35 2 set sScriptToRunOnHangup=[] in StartLoadedVgs

214526.35 2 init StartLoadedVgs_InitLineState start

214526.35 2 rv add [$RV_STARTTIME]{4/21/2007 9:45:26 PM}

214526.35 2 rv add [$RV_DEVICEID]{2}

214526.37 2 rv add [DlgcNetworkResource]{dxxxB1C2}

214526.37 2 rv add [DlgcVoiceResource]{dxxxB1C2}

214526.37 2 rv add [$RV_CIDNAME]{}

214526.37 2 rvns add [PathApp]{G:\Program Files\VoiceGuide\}

214526.37 2 rvns add [scriptsPath]{G:\Program Files\VoiceGuide\Scripts\MVDriverLine\}

214526.37 2 rv add [$RV_CIDNUMBER]{}

214526.38 2 fn RunModule start [Get Numbers,[GetDivision],1,,]

214526.38 2 tw DialogicEvent 134,TDX_CST,82,0,0,DE_LCON,,

214526.38 2 event TDX_CST, iCode=134 state=6001

214526.38 2 LsModuleTransition : 134, [TDX_CST]

214526.38 2 timer clear

214526.38 2 state [GetDivision] Number Input

214526.40 2 state [GetDivision] Playing (enterDivisionNumber.wav)

[Guest newpop1]

Here are the two files, tw and log from test call. Out of the 4 lines line 2 and 3 after script is done, they pick up again and stay on first module saying a wav file and hang up after a few mins and then they run the script again without anyone ringing the line.

 

I also spoke too soon on my other server that I also upgraded to ver 6. It has similar behavior. It has 2 4-line Dialogic cards and when it dials out using the outdial_new.txt, after the call/script is done, module hangs the call and then it automatically runs the main script that it defined for answering and never hangs up the call, waits a few mins, then hangs the call and then runs the script again and gets stuck on first module saying a wav file. Even though the module has a time out of 6 secs, it never hangs up the call. weird.

 

These both servers were ok in version 5 under TAPI.

 

Thanks

newlogs.zip

[Guest newpop1]

I forgot to add that if I click on the offending line and select HANG UP button from toolbar, the line will remain waiting for call properly then until next call happens.

[Guest newpop1]

I just tested and take my last reply back, actually the only way to have VG stop the cycle is to close VG and start again. Clicking on the hang up icon does hang up the line, but it automatically starts the script immediately.

 

Thanks

[SupportTeam]

OK, Looks like there is something unusual happening with those lines in that the Dialogic card is reporting that is has detected a new ring soon after the line is put 'on-hook'.

 

The issue has been logged and I'm told that we'll have a fix for this available for you tomorrow.

 

In the meantime, have you tried setting for the call to be answered after 2 or more rings instead of after 1?

 

Does this issue happen after the second call is ended as well ie. does this hangup-answer lookup continue forever, or doe the second time the script ends (due to timeout awaiting caller input) there is no new call detected?

 

 

225648.021 002 ocxfn LineDrop(sLineId=2, sOpt=0)

225648.021 002 dx_sethook(2) call

225648.021 002 dx_sethook 2 DX_ONHOOK ok

225648.037 002 ocxev DoFireDialogic completed

225648.037 002 ocxev PlayEnd(dwLineId=2, dwPlayId=725125)

225648.037 002 ocxev DoFireDialogic(dwIdx=30, 2, 129, [TDX_PLAY], 725125, 0, 0, [], [], []) (dwIdx=30)

225648.052 002 ocxev DoFireDialogic completed

225648.068 002 ev TDX_SETHOOK (SetHook Completed)

225648.068 002 ocxev DoFireDialogic(dwIdx=31, 2, 135, [TDX_SETHOOK], 0, 0, 0, [DX_ONHOOK], [], []) (dwIdx=31)

225648.068 002 ocxev DoFireDialogic completed

225648.068 002 te LINE_CALLSTATE(2, 0x2, 0x1, 0x0, 0x0) LINE_CALLSTATE-LINECALLSTATE_IDLE

225648.099 002 ocxfn RecStop(hLine=2, lRecId=0, lParam1=0, lParam2=0, strParam1=, strParam2=)

225648.099 002 dx_stopch call in RecStop

225648.099 002 dx_stopch 2 ok

225648.099 002 ocxfn PlayStop(hLine=2, lPlayId=0(0x0), lParam1=0, lParam2=0, strParam1=, strParam2=)

225648.099 002 dx_stopch call in PlayStop

225648.099 002 dx_stopch 2 ok

225648.162 002 ocxfn RingsBeforeAnswer(lLineId=2, lRings=0, lParam1=0, strParam2=)

225648.193 002 ev TDX_CST (CST Event Received)

225648.193 002 ev TDX_CST DE_RINGS data=0 ringcount=1 (hli=0x1d7c00, hli->chdev=2, hli->linedev=2)

[Guest newpop1]

Hello, I modified and set the ringsbeforeanswer to 2 instead of 1 and that solved the script cycle issue in both pcs.!! great. What it was doing, you start VG, then call comes in, script runs as usual, caller hangs up VG goes and hangs up call as normal, and then immediately would start the script as if a call would have come in and would stay there for a long time and then hang up and start cycle again. Only in 2 lines in one PC, and 4 lines in the other. But for now seems the issue was resolved. Thanks!.

 

Did you say that there is a fix for this I need to apply? Also, I now want to go back to the Outdial_new.xml, with version 6, behavior is diffferent but still, from XML file we pass variable:

 

We pass:

 

SPEAKTEXT:

Juliet cries these words into the night, having just met and fallen in love with Romeo of the Montague family, sworn enemy of her own Capulet family This famous line has been misunderstood through popular history, with comedic interpretations show

 

We get in script:

 

SPEAKTEXT:

Juliet cries these words into the night, having just met and fallen in love with Romeo of the Montague family, sworn enemy of her own Capulet family T[OutDial_RetriesLeft]{2

 

Below is the XML

 

<OutDialEntry>

<PhoneNumber>111111</PhoneNumber>

<OnAnswer>g:\Program Files\VoiceGuide\Scripts\MVDriverLine\CallReminderHuman.vgs</OnAnswer>

<RV>[PhoneNumber]{111111}[cId]{1}[LoginName]{USERNAME}[CallTime]{0819}[sentTime]{

710}[speakText]{Juliet cries these words into the night, having just met and fallen in love with Romeo of the Montague family, sworn enemy of her own Capulet family This famous line has been misunderstood through popular history, with comedic interpretations show}</RV>

</OutDialEntry>

 

Need me to upload the logs?

 

Thanks for the help so far....

[Guest newpop1]

Here is the log that shows the VG fails to pass the SPEAKTEXT variable properly and seems to be an issue of length, the text is 250 chars. Let me know.

 

Thanks

outerror.zip

[SupportTeam]

The field in the OutDial database which stores the RV information is by default set to store maximum 255 chars.

 

Attached version of VgMulti sets this field to be a 'Memo' - ie: unlimited length.

 

Update your VoiceGuide install with attached .exe, delete the OutDialQue database in VG's \data\ subdirectory and then restart VG.

 

VG will create a new version of the OutDialQue database and you should now be able to specify unlimited length RV data.

 

This version of VG also will ignore any Rings reported by the telephony card immediately after the hangup is made as such events are usually caused by impedance mismatches between line and telephony card, and not a genuine incoming call.

VgMulti_3317.zip

[Guest newpop1]

That new exe did the trick, message goes out just fine. Thanks so much!!!