Daniel Sigurgeirsson wrote:
>  Hi,
>  
> sipxCallAudioPlayFileStart is asyncronous so it will return immediately,
> and will not wait until the file has been played fully. Sipxtapi is
> supposed to fire events when playback has finised (or is terminated),
> but this doesn't work properly in the current version, I believe there
> is some rewrite going on regarding events and how notifications are
> passed from various libraries back to the main sipxtapi part, perhaps
> someone can shed a light on the status of that?
>  

In current sipxtapi, events arent fired from sipxmedialib, so the fault
isnt in sipxtapi itself, but sipxmedialib. In sipxtapi refactoring, I
only touched sipxtapi code and changed the way sipxtacklib/sipxcalllib
fire events to sipxtapi. This means these events will still not be
fired, but it will be next task.

> Another thing, apparently you must also call the corresponding
> sipxCallAudioStop function inbetween, otherwise sipxtapi doesn't
> correctly decrement the count of files being played, and hence the call
> will never be torn down properly. I also believe this will change, once
> the modifications from Jaroslav will be incorporated into the main trunk
> (what is the status of that BTW?)
>  

I didn't remove the counter yet, I want to check sipxmedialib before I
do so. So in the first version counters will be present. There have been
lots of modifications really, and I want to make sure first, that all
sipxtapi unittests run.

I didn't have time to work on sipxtapi this weekend, as I was quite
busy, but I should have time in the next few days, so I should get all
unittests run. Then you can use it and alert me to any weird behaviour
you discover. I will only maintain this new version, as it has much
cleaner code than the old one.

Jaro

_______________________________________________
sipxtapi-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/

Reply via email to