Hello All, I found an old thread from October 2010 entitled "valet_park timeout and spot announcement" (http://lists.freeswitch.org/pipermail/freeswitch-users/2010-October/064143.h...) I also found this tread from March 2011 entitled "valet parking improvements" (http://lists.freeswitch.org/pipermail/freeswitch-dev/2011-March/004778.html) Could anyone tell me whether : 1/ Timeouts have made it into the tree ? As far as I can tell they have not ? 2/ Are there perhaps now better way to achieve the same goal ? (e.g. looking at the console, I see a variable generated called valet_ticket ?) Basically I don't want to run into the same problems Jeremy did, i.e : "If the call is transferred somewhere else first or picked up from the first park on a different extension and then parked again, it doesn't recall the second parker." Thanks Bob
LOOK CLOSER! They are in there! ;) /b On Jan 12, 2012, at 10:51 AM, Bob Smith wrote:
1/ Timeouts have made it into the tree ? As far as I can tell they have not ? 2/ Are there perhaps now better way to achieve the same goal ? (e.g. looking at the console, I see a variable generated called valet_ticket ?)
Btw here are the variables valet_parking_timeout - Timeout in Seconds valet_parking_orbit_exten - Extensions to transfer to when timeout happens. valet_parking_orbit_dialplan - What dialplan (defaults to current sessions dialplan) valet_parking_orbit_context - What context (defaults to current sessions context) /b On Jan 12, 2012, at 6:23 PM, Brian West wrote:
LOOK CLOSER! They are in there! ;)
/b
On Jan 12, 2012, at 10:51 AM, Bob Smith wrote:
1/ Timeouts have made it into the tree ? As far as I can tell they have not ? 2/ Are there perhaps now better way to achieve the same goal ? (e.g. looking at the console, I see a variable generated called valet_ticket ?)
participants (2)
-
Bob Smith
-
Brian West