I had almost the same problem- it was needed to record everything, even if
the record path doesn't exist - it was requested to create the needed path.
For this purpose I've used event_socket command api system ..., precisely,
api system mkdir -p path
And after this command I've started recording.
While I was testing the mod dptools record application using invalid file
paths, i noted that the mod dptools record application terminated the
call.
I am currently looking for a way to change this behaviour.
Any suggestions? Can this be done?
___
Okay, I'll ask the obvious question. Why are you passing record invalid file
paths and why should it not fail if you do?
Mike
On Nov 18, 2009, at 2:38 PM, William Kendi ... wrote:
While I was testing the mod dptools record application using invalid file
paths, i noted that the mod dptools
Actually, I am integrating FreeSWITCH with a weird IVR Framework, and the
current behaviour of the mod dptools record application breaks some rules
of the weird IVR Framework that must be integrated with FreeSWITCH.
In order to integrate FreeSWITCH with the weird IVR Framework, the mod
dptools
