Return to LanScape's home page Go back a page...       Active TopicsActive Topics   Display List of Forum MembersMember List   Knowledge Base SearchSearch   HelpHelp  RegisterRegister  LoginLogin

LanScape VOIP Media Engine™ - Technical Support
 LanScape Support Forum -> LanScape VOIP Media Engine™ - Technical Support
Subject Topic: Trouble running .NET sample VoipMediaEngineConsoleTest Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: August 28 2007 at 1:49pm | IP Logged Quote support

To: All VOIP Media Engine Developers.
Subject: Running .NET sample VoipMediaEngineConsoleTest.

There have been some questions regarding running the VoipMediaEngineConsoleTest C# sample .NET application that comes with the media engine. We wanted to post this response to the support forum in an effort to help those who may be a bit confused. This post originally was sent out to a customer via email.



Hi Maxwell,

Your 128 line product image looks ok. Here is what we did to verify the product image and the C# sample code:

1)
Installed your product image (xxxxxx-xxxxx.zip) to a "plain vanilla" Compaq laptop.

2)
Copied the license file "LanScapeVME.cs" from the product distribution to the following install folder:
"C:\Program Files\LanScape\VOIP Media Engine\5.12\Software Examples .NET\C#\VoipMediaEngineConsoleTest\VoipMediaEngineConsoleTes t"

The above path assumes you allowed the media engine to install to its default location.

3)
Updated the reference to the LMEVoipManaged.dll managed code wrapper DLL in the C# project.

4)
Changed a few lines in the "MainProgram.cs" source code module. Please see the attached file. You can perform a quick diff of your original file with this one to see the lines we changed.

5)
Performed a "rebuild all" of the project.

6)
Ran the Debug version in VS2005 debugger. All looked ok. Then ran the the release build from a DOS box. All looked ok.


If you perform similar steps as those outlined above, you should be ok too.

On thing that can get messy is if you have multiple versions of the native code media engine DLL on your host machine. Make sure the test app is dynamically linking to the v5.12.4.7 DLL image. A good way to determine the version of the media engine DLL before your code starts to use it is to place the following code immediately before the InitializeMediaEngine()API proc as follows:

Code:

.
.
.
// Telephony Engine version information.
//
BoolStatus = MediaEngine.GetMediaEngineVersionInfo(VersionInfo);

status = MediaEngine.InitializeMediaEngine(0, 0);
.
.
.



After calling the GetMediaEngineVersionInfo() API proc, the VersionInfo.MediaEngineVersion structure member should have the string "5.12.4.7". If you get some other version string, then locate the other DLL image and get rid of it.

That should be it. Let us know your results.


Support






Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 

If you wish to post a reply to this topic you must first login
If you are not already registered you must first register

  Post ReplyPost New Topic
Printable version Printable version

Forum Jump
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum






Contact LanScape Hear what the Lawyers have to say How youm may use this site Read your privacy rights