speedvoip
Vetran
Joined: August 07 2008
Location: Canada
Posts: 156
|
| Posted: November 04 2008 at 2:10am | IP Logged
|
|
|
Hi Support:
I have noticed there is important notes at media engine software developer reference as follows:
Thread Deadlock Information: Internally the VOIP Media Engine™ is fully multi-threaded. The event callback mechanism is non-reentrant. Some media engine API procedures cannot be called from within the main media engine callback procedure. As a general rule: Any API procedure that can generate additional events cannot be called in the "main event handler" when processing the current event. If you call an API procedure that generates additional events while you are executing in the callback procedure, your VOIP application can deadlock. This is by design. Any API procedure that generates events back to your application must be executed by some other thread in your application. Some of the media engine API procedures that will generate events are: MakeCall, MakeCallUri, TerminateCall, GoOffHook, AbortIncomingCall, BusyOutLine, HoldLine, ConferenceLine, TransferLine, TransferLineUri, EnableSipRegisterServer and DisableSipRegisterServer.
Pls give me more detailed info about event callback mechanism. On the other hand, internally how media engine to implement event notification?
__________________
VoIP Anti-Blocking Guru
|
Active Topics 
Member List 
Search 
Help 
Register 
Login
LanScape Support Forum -> LanScape VOIP Media Engine™ - Pre-Sales Technical Support
Topic: On Event Callback
