| Author |
|
juice
Vetran
Joined: December 05 2006
Location: United States
Posts: 139
|
| Posted: May 17 2007 at 12:55pm | IP Logged
|
|
|
I recently began moving some IVR prompt playback stuff out of the received audio callback (where it only sent data when it received data) to a more proper place - into its own thread. Everything seems to be working, still need more testing/tweaking, etc... However, looking at the console window, a strange error message pops up occasionally. I am 100% positive that the error message is getting printed out from inside LanScape itself, so there is no visible way to handle it nor do I even know what the error means - there is no reference to it in the documentation that could be found. Note, this is with using the 5.12.3.30 LanScape engine.
If you need some more info or some example code that seems to be causing this let me know. Some more information:
Number of lines initiated with LanScape:
4
Description:
The problem seems to happen mostly when changing the current list of prompts (by pressing a dtmf # key), which simply closes the open wave file, and proceeds to open a new one to start streaming. If I do nothing, and leave the original list of prompts to playback, I don't see the warning.
|
| Back to Top |
|
| |
juice
Vetran
Joined: December 05 2006
Location: United States
Posts: 139
|
| Posted: May 17 2007 at 2:02pm | IP Logged
|
|
|
I should also note that this happened in a debug build/session. When testing the release build (utililizing more lines), the error/warning did not pop up. So, I guess I am just wondering if this warning is safe to ignore, what causes it, and if this is a recent warning introduced by a recent upgrade to 5.12.3.30 LanScape engine.
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: May 18 2007 at 10:39am | IP Logged
|
|
|
juice,
Oh, for sure, send us what you see in the console window!!!
Also tell us exactly what sample app this occurs with and how you reproduce it.
Do you have a support FTP account set up with us yet? If so, we would like you to upload the code so we can test it here.
Support
|
| Back to Top |
|
| |
juice
Vetran
Joined: December 05 2006
Location: United States
Posts: 139
|
| Posted: May 18 2007 at 6:03pm | IP Logged
|
|
|
Thanks for the quick response. I have not seen it in any of the demos, maybe because the demos do not have console windows - or maybe because there is only something wrong in my code only :). It does not appear to always happen, but I can work on creating some sample code to try to reproduce the issue outside of the larger project I am working on.
Though, it would be easier to try to reproduce it in standalone application if you could perhaps give me a hint of what might cause that error. Not a lot is going on in my app, just one line is connected, I call an update method from a thread to write data to the transmit buffer, and occasionally I see that pop up on the console.
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: May 18 2007 at 8:51pm | IP Logged
|
|
|
juice,
Tell us what you are seeing.
Is a dialog of some sort being displayed?
What do you mean by "on the console"? The console of what?
What is the text or error that is being displayed?
Give us something more solid and we will help you.
Support
|
| Back to Top |
|
| |
juice
Vetran
Joined: December 05 2006
Location: United States
Posts: 139
|
| Posted: May 21 2007 at 12:21pm | IP Logged
|
|
|
By console window, I simply mean the dos prompt/box console that is displayed by a Win32 console application - (sorry not to clarify earlier, I thought console was generally understood to be the dos window). I see this:
warning LSP Low
warning LSP Low
warning LSP Low
warning LSP Low
...
And it comes around occasionally. I do not print this to the console window. This is coming from either standard error or standard out, but it doesn't really matter which one. I think it is related to the dtmf detector, as it seems to happen most when dtmf was pressed. At first I thought it was when I was changing the list of audio prompts to be played (which was a result of dtmf tones), but this also happens when there is no audio being played. Also as stated above, I only see this in debug build.
The only other reference that Google shows me is an Asterisk error message, but do description of what it is. The only reason I am sure it is coming from LanScape, is because I see that string "warning LSP Low" in the LanScape dll - and not in any other libraries in this application.
I will still attempt to recreate the issue with a very simple app. Unfortunately, the current source is not able to be given - and is part of a much larger app.
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: May 21 2007 at 1:03pm | IP Logged
|
|
|
juice,
OK, now that's good solid information we can use to track this down. Good job. We will repost as soon as we find something. Performing a hex or string dump of the media engine dll to look for the string you are seeing is perfect. It could be that a benign piece of “QA/test code” may have been left in the production build.
Support
|
| Back to Top |
|
| |
juice
Vetran
Joined: December 05 2006
Location: United States
Posts: 139
|
| Posted: May 21 2007 at 1:11pm | IP Logged
|
|
|
I agree that it may in fact be benign (and left in unintentionally), as is my first guess - since it only happens in debug build, and does not noticeably cause any issues.
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: May 21 2007 at 1:53pm | IP Logged
|
|
|
juice,
Well that was it. A QA debug/trace message was left in the build and the message was displayed using the standard C library routine printf() to stdout.
The message is actually part of the G729/G729A codec support that is linked into the media engine build. The message was indicating that a computational limit of the LSP computed coefficients for the codec was being reached. It’s a benign console out message. If you are curious what LSP means, check out this Wikipedia definition:
Line spectral pairs:
http://en.wikipedia.org/wiki/Line_spectral_pairs
At any rate, you can safely ignore the message going to your stdout. It will be gone the next time you guys purchase a media engine update/upgrade.
Thanks for spotting this and taking the time to report it.
Support
|
| Back to Top |
|
| |
juice
Vetran
Joined: December 05 2006
Location: United States
Posts: 139
|
| Posted: May 21 2007 at 6:47pm | IP Logged
|
|
|
Thanks for the information. I'm glad that it is benign, I was worried I was doing something wrong :-)
|
| Back to Top |
|
| |
Active Topics 
Member List 
Search 
Help 
Register 
Login
LanScape Support Forum -> LanScape VOIP Media Engine™ - Technical Support
Topic: warning LSP Low
