Hello,
I have been working with the sipxtapi for a short period.
I have re-discovered an existing bug when playing audio files - no
MEDIA_PLAYFILE_STOP event is ever received. I have worked around this
with a function to calculate the play time of a file and then wait for
that period before performing other actions.
I have now discovered a new bug (I think).
If a sipxCallAudioPlayFileStart call is made and then a second one made
- after the first file play has finished - then the call will never
receive a CALLSTATE_DESTROYED event
It is necessary to prefix the second (sipxCallAudioPlayFileStart( call
with a sipxCallAudioPlayFileStop call. In this case the
CALLSTATE_DESTROYED event is received.
The simplest workaround is simply to always code:
sipxCallAudioPlayFileStop ( _hCall ); // Somehow required for
correct operation
if (sipxCallAudioPlayFileStart( _hCall, _szFile, loop, local, remote )
== SIPX_RESULT_SUCCESS)
{
...
Is this a (new) bug?
I have also run valgrind on my application and so there seem to be a
number of memory management problems within the api.
What is the memory safety of the present release of the API?
Thanks
Jeremy
_______________________________________________
sipxtapi-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
