Hi, On 12/22/07, Jeremy A <[EMAIL PROTECTED]> wrote: > Looking at the patch you supplied it seem to refer to Tones (DTMF?) > rather than playing a file. In my case I'm trying to play a file with > sipxCallAudioPlayFileStart. > Does your patch cover that case?
It should. Words TONES is just a naming confusion. > I am using the 'standard' version published in May - not svn. > sipXcalllib has a version number of 2.9 and sipXmediaLib - Version 2.6.2 > > I also have access to svn (and some extra time now over Christmas) Is it > worthwhile changing to the svn version? I see there a lot of changes in > sipXmediaLib for instance and I'm not sure if it is safe to change just > yet. If it is good to change, how do I get a 'safe' version from svn? Yes, I strongly recommend you to update to svn version - a lot of things were fixed since this release. And I think latest svn is more stable then it. Right now we're using policy, similar to ffmpeg's one - we're trying to keep svn in good shape at any time. That is if some commit break something, it is followed by commit, fixing it. And recent svn should be working fine. > Finally I have a problem with remote DTMF events seeming to kill local > audio output. I've not quite characterised it yet but is it a known problem? I do not completely understand what do you mean "kill local audio output". What are you refering to as "local audio output"? If you mean problem, similar to one with playing file - similar approach of fixing it could be used. -- Regards, Alexander Chemeris. SIPez LLC. SIP VoIP, IM and Presence Consulting http://www.SIPez.com tel: +1 (617) 273-4000 _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
