Jump to content


< Back to Forum


 

Loop Drop & Say Numbers Issues


  • Please log in to reply

#1 chazmanian 07 January 2016 - 07:24 AM

I just recently purchased and installed Voiceguide 7.5.1 on Windows 10. I am having 2 issues:

 

1. The Say Numbers is repeating the numbers in a very distorted sound (using ones that came with the system). I can put the same wav file in a different control and they sound fine. I tried this in version 7.5.0 and have the same problem.

 

2. The system is not detecting the loop drop. I tried setting the config value to 1 as suggested in other threads but to no avail.

 

I have attached the log files.

 

Please let me know if you need any other information.

 

 



#2 SupportTeam 07 January 2016 - 03:27 PM

The sound files that are played concatenated together should all be in the same format.

 

ktTel trace shows that the sound files played as part of confirmation of the entered number are in variety of formats.

 

System default format is selected at VoiceGuide install time and it is best if all other sound files are in same format.

 

That format usually is u-Law 8kHz 8-bit.

 

other formats can be used (see http://www.voiceguid.../soundfiles.htm ) but as stated before, it needs to ensured that in situations where sound files are concatenated one after another then they all must be in same format.

 

Also, please note that Windows 10 is not supported by Dialogic drivers yet.

 

This could be reason for look current drop issue.

 

Recommend installing on a different version of Windows and see if you get different results for loop current drop detection. VoiceGuide will react to loop current drop if it is detected and reported by the Dialogic card.



#3 chazmanian 08 January 2016 - 03:13 AM

I am using the sound files that come with voice guide system. As I stated before, the they play fine in the other controls, it is the speak number control that is not working. Could it be something else?

 

The dialogic sample program cbansr recognizes the loop drop. Do you have any other suggestions?



#4 SupportTeam 08 January 2016 - 03:45 AM

Trace shows that during number confirmation the following files are played:

 

154207.775   7   5   3       q_tel +     cmd_PlayStart 973406 ,c:\AutoAdmin\wav\SayYouEnteredMemberID.wav,c:\AutoAdmin\1.wav,C:\Program Files (x86)\VoiceGuide\system\voice\2.wav,c:\AutoAdmin\3.wav,c:\AutoAdmin\4.wav,c:\AutoAdmin\5.wav,c:\AutoAdmin\6.wav,c:\AutoAdmin\7.wav,c:\AutoAdmin\8.wav,c:\AutoAdmin\9.wav,C:\Program Files (x86)\VoiceGuide\system\voice\GetNbrsConfirmMenu.wav []
 

 

The file c:\AutoAdmin\wav\SayYouEnteredMemberID.wav is not a VoiceGuide sound file, and ktTel traces hows that it is not in ULaw format:

 

725 154207.789  9552           wav: format=1, channels=1, hz=8000, bytes/sec=16000, bytes/sample=2, bits/sample=16, DataBlockSize=36770  c:\AutoAdmin\wav\SayYouEnteredMemberID.wav
 

Also, the number files that were placed in c:\AutoAdmin\are not in 8-bit format, which strictly speaking means that they are not in uLaw format:

 

734 154207.856  9552           wav: format=7, channels=2, hz=8000, bytes/sec=16000, bytes/sample=2, bits/sample=8, DataBlockSize=13240  c:\AutoAdmin\3.wav
735 154207.856  9552           convert to 8 bit as sample_rate = 8000 Hz (!=11025)
736 154207.856  9552           BytesPerSample=2 ptrVoiceData_Current=0xe8490c0 (16bit->8bit conversion) data_size_div2=6619,
737 154207.874  9552           wav: format=7, channels=2, hz=8000, bytes/sec=16000, bytes/sample=2, bits/sample=8, DataBlockSize=11952  c:\AutoAdmin\4.wav
738 154207.874  9552           convert to 8 bit as sample_rate = 8000 Hz (!=11025)
739 154207.874  9552           BytesPerSample=2 ptrVoiceData_Current=0xe84c490 (16bit->8bit conversion) data_size_div2=5975,
740 154207.885  9552           wav: format=7, channels=2, hz=8000, bytes/sec=16000, bytes/sample=2, bits/sample=8, DataBlockSize=11952  c:\AutoAdmin\5.wav
741 154207.885  9552           convert to 8 bit as sample_rate = 8000 Hz (!=11025)
742 154207.885  9552           BytesPerSample=2 ptrVoiceData_Current=0xe84f358 (16bit->8bit conversion) data_size_div2=5975,
743 154207.889  9552           wav: format=7, channels=2, hz=8000, bytes/sec=16000, bytes/sample=2, bits/sample=8, DataBlockSize=14856  c:\AutoAdmin\6.wav
744 154207.889  9552           convert to 8 bit as sample_rate = 8000 Hz (!=11025)
745 154207.890  9552           BytesPerSample=2 ptrVoiceData_Current=0xe852220 (16bit->8bit conversion) data_size_div2=7427,
746 154207.894  9552           wav: format=7, channels=2, hz=8000, bytes/sec=16000, bytes/sample=2, bits/sample=8, DataBlockSize=12952  c:\AutoAdmin\7.wav
747 154207.894  9552           convert to 8 bit as sample_rate = 8000 Hz (!=11025)
748 154207.894  9552           BytesPerSample=2 ptrVoiceData_Current=0xe855c40 (16bit->8bit conversion) data_size_div2=6475,
749 154207.895  9552           wav: format=7, channels=2, hz=8000, bytes/sec=16000, bytes/sample=2, bits/sample=8, DataBlockSize=9416  c:\AutoAdmin\8.wav
750 154207.895  9552           convert to 8 bit as sample_rate = 8000 Hz (!=11025)
751 154207.895  9552           BytesPerSample=2 ptrVoiceData_Current=0xe858ef0 (16bit->8bit conversion) data_size_div2=4707,
752 154207.895  9552           wav: format=7, channels=2, hz=8000, bytes/sec=16000, bytes/sample=2, bits/sample=8, DataBlockSize=14456  c:\AutoAdmin\9.wav
753 154207.895  9552           convert to 8 bit as sample_rate = 8000 Hz (!=11025)
754 154207.895  9552           BytesPerSample=2 ptrVoiceData_Current=0xe860150 (16bit->8bit conversion) data_size_div2=7227,

 

probably best if the number files are removed from the c:\AutoAdmin directory, to allow for the default system number files (from C:\Program Files (x86)\VoiceGuide\system\voice\ ) to be used.

 

 

Regarding Loop Current:

 

The ktTel trace shows that the loop current ON event is reported by Dialogic card at call answer time:

 

552 154150.385  9828   5 ev    TDX_CST (CST Event Received)
553 154150.385  9828   5       TDX_CST DE_LCON data=4607
554 154150.385  9828   5       evDialogic call
555 154150.385  9828   5 r     Dialogic
556 154150.386  9828   5 r     Dialogic  TDX_CST 134 (4607 0 0 DE_LCON  )

 

so we would expect that a loop current OFF event should be detected by Dialogic card and reported as well.

 

VoiceGuide will react to a Loop Current Drop (OFF) event if one is supplied by Dialogic card.

 

VoiceGuide's ktTel trace will show if the Loop Current Drop (OFF) event is fired by Dialogic card/drivers or not.

 

When you did tests with VoiceGuide were calls arriving into system the same way as when they were arriving when cbansr sample was used?

 

 

As stated before, Windows 10 is not supported by Dialogic drivers yet, so currently we do not recommend using Windows 10.



#5 chazmanian 08 January 2016 - 04:35 AM

Yes when the tests were done, the calls arrived into the system the same way with cbansr  and VoiceGuide.

 

I think the logs were misleading with all of the tests I was doing in trying to alleviate the issues.

 

I will roll the OS back to windows 7 and will post back what the results are.