File Character Length Problem Saving Vm

[Guest ChrisAC]

I've discovered a new problem moving from 5.x TAPI (with voice modems) to 6.0 Dialogic (with D/4PCIUS) SR 5.1 with FP1

 

I custom name recorded vm's similar to this.

 

0001_0606154819_1_1_D&R Equipment Co. Inc._2025551212.wav

 

Works ok, however, I had a message last week from "The Willard Intercontinental Hotel". While the VG call manager showed no entry, the ..Data\VmSave folder listed:

 

example

0001_0606154819_1_1_The Willard Intercontinental Hotel_20255512

 

The filename must have reached a maximum character limit and truncated the remaining characters (including the most important part .wav)

 

I added ".wav" to the end of the filename, & I was able to hear the vm.

 

So, I figured no problem, I'll just re-think my file naming scheme.

 

Here is the real problem that I don't know how to fix.

 

I dialed into VG blocking my callerID. The D/4PCIUS did not recognize CID like "Private Name" or "Private Number", it instead reports:

 

152827.968 001 dlgc  CLIDINFO_GENERAL=[06/06 15:28         P                   P]
152827.984 001       CLIDINFO_CALLID error [129]:[Caller ID private or blocked]
152827.984 001 dlgc  CLIDINFO_FRAMETYPE=[0x80]

 

Later in the log while trying to record a vm this happens:

 

152838.843 001       open save file call (create)
152838.843 001 dlgc  open save file(strFname=C:\Program Files\VoiceGuide\data\VmSave01_0606152838_1_1_06/06 15:28         P                   P_06/06 15:28         P                   P.pcm) => -1, [dx_fileerrno=22, EINVAL, Invalid argument.]
152838.843 001 ocxfn RecStop(hLine=1, lRecId=223531, lParam1=0, lParam2=0, strParam1=, strParam2=)

 

The above is trying to save a filename of more than 100 characters.

 

The call is immediately dropped, nothing is recorded, but the function FileMoreThenMinLength in vglmhangup.vgs

 

function FileMoreThenMinLength(sVmbId, sFilename)

if "$RV[VmLmRec_RecLen100ms]" = "" then

'[VmLmRec_RecLen100ms] not set...

VG.Admin_TraceLogAdd iLineId, 1, "vm RV[VmLmRec_RecLen100ms] not set."

FileMoreThenMinLength = True

msgbox "function FileMoreThenMinLength is true" 'This triggers a halt in the code for me.

exit function

. . .

 

The rest of the scripts run, and vg believes that a message was left.

 

Question 1 (the most important)

Can I tweak the Dialogic or VoiceGuide to recognize [Caller ID private or blocked] as something other than:

 

06/06 15:28         P                   P_06/06 15:28         P                   P

 

Question 2

What is the maximum character pathname\filename.wav Voiceguide or Dialogic will permit?

 

I'll attempt to zip the tw & vgm logs here.

 

Thank you very much,

 

Chris C

Logs.zip

[SupportTeam]

Thank you for the traces and full description of the issue. This allowed us to quickly trace both problems and fix them. Please update to attached version, and let us know if it fixed the problems on your system.

 

 

To update:

 

Run these command from Command Prompt in the Windows' System32 directory to unregister ktTel.ocx:

 

regsvr32 - u ktTel.ocx

 

Then copy new ktTel.ocx into Windows' System32 directory (remove or overwrite previous OCX's from system entirely, do not just rename it)

 

Then run this command from Command Prompt in the Windows' System32 directory to register the new ktTel.ocx:

 

regsvr32 ktTel.ocx

 

Then copy the new vgMulti.exe into VG's directory (overwriting existing).

 

 

 

In additon of resolving the issue the attached version differs from v6.0.3310 in following ways:

 

 

NEW : $RV_STATUSDISPLAYED added.

NEW : Unlimited Length Result Variables can now be loaded into the Dialer's OutDialQueue database.

CHG : VOX intermediate files are no longer created at all.

CHG : EV_TIMEOUT_MAKECALL_NORESPONSE on outgoing calls set to 10 seconds more then Dialogic's Call Progress timeout.

This is to ensure Dialogic's Call Progress timeout always occurs first.

FIX : Rings reported by the telephony card immediately after hangup are ignored as such events are usually caused by

impedance mismatches between line and telephony card, and not a genuine incoming call.

FIX : Result Variables can now contain the "}" character.

FIX : Escalation calls are now dialed immediately when "RETRY" is specified for Answering Machine script and the retry counter is 0.

FIX : DialoutProcessFailedDial error which was preventing immediate escalation fixed.

FIX : Record Pause/Resume can now use the same DTMF key.

FIX : Blocked CallerID messages from some phone companies were not handled properly. These are now reported as "PRIVATE" etc. for the CallerID number field.

FIX : Made changes which fixed RobbedBit On Springware cards (D/240JCT, D/480JCT) probles at one site.

FIX : Bug which was limiting recorded WAV filename limit of 100 characters fixed.

FIX : Bug which was causing errors if zero length .WAV fies were played.

vg6.0.3323.zip

[Guest ChrisAC]

Thanks,

 

I'll test the new .exe & .ocx when I get to my office in about 3 hours. I'll confirm the fixes then.

 

Also,

 

. . .

FIX : Rings reported by the telephony card immediately after hangup are ignored as such events are usually caused by

impedance mismatches between line and telephony card, and not a genuine incoming call.

 

I was getting some of those ghost rings too, very cool fix (hopefully)

 

Regards,

 

Chris

 

ps. are you really posting at 09:00 PM your time? If so, it's like I've jumped into the future.

[Guest ChrisAC]

Thank you for the traces and full description of the issue. This allowed us to quickly trace both problems and fix them. Please update to attached version, and let us know if it fixed the problems on your system.

. . .

 

O.K.

 

updated the .ocx & the VG build .3323

 

Called into the system with the CID blocked & it seems to work o.k. now.

 

Thank You.

 

I found something else related though. The CallerID "Out of Area" also needs fixing for the US (maybe). Unfortunately, I can't test since I can't "force" an Out Of Area call. Take a look at this snip.

 

095055.968 001 ev    TDX_CST DE_RINGS data=1 ringcount=2 (hli=0x1b1bd8, hli->chdev=1, hli->linedev=1)
095055.968 001 dlgc  CLIDINFO_CMPLT=>[€06070950OO]
095055.968 001 dlgc  CLIDINFO_GENERAL=[06/07 09:50         O                   O]
095055.968 001       CLIDINFO_CALLID error [130]:[Unable to provide service]
095055.984 001 dlgc  CLIDINFO_FRAMETYPE=[0x80]
095055.984     dlgc  caller id frame type: CLASSFRAME_MDM or CLIPFRAME_MDM or ACLIPFRAME_MDM

 

and

 

095055.999 001       in CLASSFRAME_MDM: _CMPLT=[€06070950OO] _GENERAL=[06/07 09:50         O                   O] _CALLID=[]   datetime=[06070950] dn=[] ddn=[] name=[] absence1=[O] absence2=[O] qualifier=[] redirect=[] calltype=[] netmsg=[]
095055.999 001       strCallerID_GENERAL trigger (CLASSFRAME_MDM)
095055.999 001       pbx display not supported on this card
095055.999 001 ev    OnFireCallerIdArrived (hli=0x1b1bd8) (06/07 09:50         O                   O,06/07 09:50         O                   O,06/07 09:50         O                   O)

 

This looks like a similar fix, but the "Out of Area" has two modes (Verizon USA East) On a telephone, it can be either,

 

CIDNAME: Out Of Area

CIDNUMBER: Out Of Area

 

or

 

CIDNAME: Out Of Area

CIDNUMBER: 3018533700

 

I have a later log where such a call arrived. The Dialogic reported it as:

 

102713.046 002 dlgc  CLIDINFO_CMPLT=>[€06071027
3018533700O]
102713.046 002 dlgc  CLIDINFO_GENERAL=[06/07 10:27         3018533700          O]
102713.046 002 dlgc  CLIDINFO_CALLID=[3018533700]
102713.046 002 dlgc  CLIDINFO_FRAMETYPE=[0x80]
102713.046     dlgc  caller id frame type: CLASSFRAME_MDM or CLIPFRAME_MDM or ACLIPFRAME_MDM
102713.062 002 dlgc  MCLASS_DATETIME=[06071027] => 0
102713.062 002 dlgc  MCLASS_DN=[3018533700] => 0
102713.062 002 dlgc  MCLASS_DDN=[] => -1
102713.062 002 dlgc  MCLASS_ABSENCE1=[] => -1
102713.062 002 dlgc  MCLASS_REDIRECT=[] => -1
102713.062 002 dlgc  MCLASS_QUALIFIER=[] => -1
102713.062 002 dlgc  MCLASS_NAME=[] => -1
102713.062 002 dlgc  MCLASS_ABSENCE2=[O] => 0
102713.078 002 dlgc  CLIP_CALLTYPE=[] => -1
102713.078 002 dlgc  CLIP_NETMSG=[] => -1
102713.078 002       in CLASSFRAME_MDM: _CMPLT=[€06071027
3018533700O] _GENERAL=[06/07 10:27         3018533700          O] _CALLID=[3018533700]   datetime=[06071027] dn=[3018533700] ddn=[] name=[] absence1=[] absence2=[O] qualifier=[] redirect=[] calltype=[] netmsg=[]
102713.078 002       strCallerID_DN trigger (CLASSFRAME_MDM)
102713.078 002       pbx display not supported on this card
102713.078 002 ev    OnFireCallerIdArrived (hli=0x1c57c8) (3018533700,,)

 

I'm not sure if I was running the build .3323 at this time, (may have been .3320b) but I was running the ktTel.ocx v2.4.2.0

 

I can't test, I can only wait for another "Out of Area" call to arrive to analyze the logs. I don't even know if an "Out of Area" caller can leave a message. Perhaps I can locate a caller from "Out of Area" and ask them to test. (Usually, "Out of Area" are sales solicitations, but sometimes, callers using TELCO's other than Verizon will report ID's "Out of Area").

 

Anyway, I will work at my end to provide further testing so I may produce proper logs. It may not really be a problem, I need to find an out of area caller to try to leave a message.

 

Care to Call?

 

Thanks again for all the support, hopefully when I get good at this, I can give back to the forum.

 

Chris C

[SupportTeam]

The out of area should have been handled by the new OCX as well, so we'd need to see the fuller trace to confirm whether the new or the old OCX was used.

 

Here is a new OCX which reports that part of the trace a bit different, to let us better see what is happening an confirm how the Out Of Area case is handled.

 

The 3rd trace provided seems to report the CallerID number to VoiceGuide, so all looks fine with that 3rd trace(?).

ktTel_2.4.3.a.zip

[Guest ChrisAC]

The out of area should have been handled by the new OCX as well, so we'd need to see the fuller trace to confirm whether the new or the old OCX was used.

 

Here is a new OCX which reports that part of the trace a bit different, to let us better see what is happening an confirm how the Out Of Area case is handled.

 

The 3rd trace provided seems to report the CallerID number to VoiceGuide, so all looks fine with that 3rd trace(?).

 

I installed the new .ocx. I'm wating for an "Out of Area" CIDNAME & CIDNUMBER to come in. I'll reply again at that time.

 

Thanks again,

 

Chris