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: need help about the upgraded sdk Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
will
Junior
Junior


Joined: February 07 2005
Location: Canada
Posts: 48
Posted: February 20 2006 at 1:03pm | IP Logged Quote will

Hi, Support,

when we tried to compile the old softphone against the upgraded sdk, we found out some api's signature definitions have been changed, such as the following compiling error we got:

SetAudioOutDataType' : function does not take 2 parameters
C:\Program Files\LanScape\VOIP Media Engine\5.11\Software Examples\SingleLine Phone\SingleLine PhoneDlg.cpp(1913) : error C2660: 'SetTxIvrDataType' : function does not take 2 parameters


and also some data structure definations have been changed, for example,

"AUDIO_BW_MULAW_8K = 0," was used in previous AUDIO_BANDWIDTH defination, but in the following new defination, it is actually the same thing, but with "AUDIO_BW_ULAW_8K = 0," which has different name, this caused all of the references to this data structure in our old versioned code have to be changed. So is there a quicker way fro your point of view that we can adopt to port our old versioned code on the new sdk?

thanks,
will


typedef enum
{
     AUDIO_BW_ULAW_8K = 0,
     AUDIO_BW_ALAW_8K,
     AUDIO_BW_G729,
     AUDIO_BW_G729A,
     AUDIO_BW_ILBC_20MS,
     AUDIO_BW_ILBC_30MS,
     AUDIO_BW_PCM_8K,
     AUDIO_BW_PCM_11K,
     AUDIO_BW_PCM_22K,
     AUDIO_BW_UNDEFINED

}AUDIO_BANDWIDTH;



Back to Top View will's Profile Search for other posts by will
 
will
Junior
Junior


Joined: February 07 2005
Location: Canada
Posts: 48
Posted: February 20 2006 at 7:57pm | IP Logged Quote will

Hi, Support,

I disabled all of the previous api calls which have conflicts with the upgraded sdk, and made the compilation go through, then when we start the softphone, it stays at "System initializing...pls wait" status and could not start the engine, after we click to close the softphone, it also shows the following error message:
"Error: The following telephoney error was detected:SipBandwidth error:Error 13"

We guess upgrading is mainly done in the LMEVoip.dll, and some new features and modifications are put in the SipTelephonyApi.h and we also browsed the registry, we noticed a new key has been added in addition to that for version 5.10, so actually the softphone should just go to InstallDir key in te registration to follow the value:C:\Program Files\LanScape\VOIP Media Engine\5.11\ to find the right Dll to start the engine, if we undersdand correctly.

your help are very appreciated.

regards,

will
Back to Top View will's Profile Search for other posts by will
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: February 21 2006 at 8:50am | IP Logged Quote support

Will,

Sorry for the delay. Our office was closed yesterday for holiday.

1)
Yes there have been some minor changes to the API that will cause some source code changes. Please read the "VOIP Media Engine Version History.pdf" file that is part of your install image. The changes that need to be made to application source code are simple and will not take a long time. There have been changes made to 2 enumerations and simplifications made to 3 IVR procs and 2 audio out procs. To change these in your code will not take long. Just build your app and where the compiler generates errors, change the code. Also make sure your project is using the v5.11 SipTelephonyApi.h header file. The procs that have changed are:

OpenRxIvrChannel()
SetTxIvrDataType()
GetTxIvrSampleBlockSize()
SetAudioOutDataType()
GetAudioOutSampleBlockSize()

And th3 2 enumerations that changed are:
AUDIO_BANDWIDTH
MEDIA_FORMAT_AUDIO


2)
To make sure that you do not have conflict with an earlier installed version (i.e. 5.10), make sure the environment PATH of the host machine is set such that it references the v5.11 DLL Bin directory before the v5.10 Bin directory. Alternatively, you could just rename the v5.10 DLL to some other name so it will never be found while you do your 5.11 testing.


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