Daniel Sigurgeirsson wrote: > Thanks, I did that and now I receive the following log messages > (subtype 95 is CP_RECORD_AUDIO_CONNECTION_START): > > "2007-05-21T13:50:49.281000Z":415:CP:DEBUG:dabslapp:Call-22:00001198:sipXtapi:"CpCall::handleMessage > message type: 5 subtype 95\n" > "2007-05-21T13:50:49.281000Z":416:SIPXTAPI:DEBUG:dabslapp::00000000:sipXtapi:"EXIT > > FUNC (tid=5404) sipxCallAudioRecordFileStart\n" > "2007-05-21T13:50:49.281000Z":417:MP:DEBUG:dabslapp:MpMedia:00000FE0:sipXtapi:"MprRecorder::progressReport(2) > (No event)\n" > "2007-05-21T13:50:49.296000Z":418:MP:DEBUG:dabslapp:MpMedia:00000FE0:sipXtapi:"MprRecorder::enable > (No file designated!)\n" > "2007-05-21T13:50:49.296000Z":419:MP:DEBUG:dabslapp:MpMedia:00000FE0:sipXtapi:"MprRecorder::progressReport(2) > (No event)\n" > "2007-05-21T13:50:49.296000Z":420:MP:DEBUG:dabslapp:MpMedia:00000FE0:sipXtapi:"MprRecorder::enable > (No file designated!)\n" > > This time, no file is created (but it was created before the patch). > Actually, I had to apply the patch by hand and therefore I cannot rule > out that I might have forgotten something. I assume that it was the > latest patch (2007-03-15) from > http://track.sipfoundry.org/browse/XMR-99 that had to be applied? > > Regards, > Daníel >
If you had to apply the patch by hand then something is wrong. Call recording patch should apply cleanly to the latest revision, as I just did it for my internal sipxtapi few days ago. If you are interested I could put source code of my internal branch on wxCommunicator sourceforge website. I fixed many more bugs in sipxtapi that aren't in sip foundry yet (especially locking problems, and problems with 2 instances of sipxtapi). I just compiled wxCommunicator with that branch and call recording works. My branch corresponds to r9581 with many additional fixes. Jaro _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
