On Thu, Feb 3, 2011 at 12:19 PM, Josh M. Patten <[email protected]>wrote:
> As some of you already know our software development team is in the early > planning stages of extending the current park service to include valet > parking. Before we undertake this endeavor I thought it would be a good idea > to get some insight from the developers or those that are familiar with the > code. > > > > We planned on using FreeSWITCH to accomplish this but there are a few > problems with doing this: > > > > · The mod_valet plugin is woefully incomplete. The missing > functionality is: > > o Ability to transfer parked call to the original parker after timeout > > o Ability to transfer parked call to a predefined extension after > timeout > > o Ability to transfer call back to original parker by pressing 0 or a > different predefined key > > o Ability to transfer call back to a predefined extension by pressing 0 > or a different predefined key > > o Call is not released by FreeSWITCH when retrieved (media still travels > through FreeSWITCH) > > o Unable to monitor park slots via BLF > > o # key is hardcoded to disconnect the call > > · Attended Xfers to FreeSWITCH with this module fail on the first > attempt. See http://track.sipfoundry.org/browse/XX-9317 > > > > I was toying with the idea of having the software devs consider writing > this up the same way that voicemail and authorization codes are written, > using FreeSWITCH sockets and whatnot, but that still leaves three problems: > > > > · The attended Xfer issue mentioned above > > · Call is not released by FreeSWITCH when retrieved (media still > travels through FreeSWITCH) > > · Unable to monitor park slots via BLF > Please also see http://track.sipfoundry.org/browse/XX-8473 "I would like to see this implemented as a replacement for the current park server in sipxecs, provided they can be monitored via BLF. I understand the same "method" used to monitor mod_fifo can be added to mod_valet so these are monitorable. So in this instance, it would then be monitorable via BLF (RFC4235, supporting dialogue events, yay!). However, sipxconfig needs to be able to create these in mod_valet, and create and rtrack the RLS value (user id) so they are able to be found using BLF monitoring like any line." > > > Any insight on how this should be approached would be greatly appreciated. > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ >
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
