Polycom reply: ----------> Yes it was implemented. We have 2 ways of setting up BLF. The first uses the attendant.uri parameter. If you use BLF through that method we currently do not support the automata resource type and so you cnnot configure 1 touch call park/pickup.
If you configure each resource to be monitored individually using: attendant.resourceList.1.address="[email protected]" attendant.resourceList.2.address="[email protected]" attendant.resourceList.3.address="[email protected]" then you can configure them to have the one touch transfer behavior by adding: attendant.resourceList.3.type="automata" which would make the default action for the 3rd BLF resource (x8000) be blind transfer instead of a new call. Only 1 of the 2 forms of BLF may be configure at a time. This is present in firmware 3.2.0 and newer ----------> Then, we only support the RLS (attendant.uri parameter) method of BLF. So, this is not compatible with sipXecs Ke Liu [email protected] Telephone (613) 763 6367 / ESN 393 6367 ------------------------------------------------------------------------ ----------- > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Josh Patten > Sent: Monday, March 08, 2010 10:47 AM > To: [email protected] > Subject: Re: [sipX-dev] Polycom 3.2 One Touch Transfer (automata) > > *bump* > > Josh Patten > Assistant Network Administrator > Brazos County IT Dept. > (979) 361-4676 > > > On 3/2/2010 3:45 PM, Josh Patten wrote: > > I was wondering about the introduction of one touch transfer in > > firmware > > 3.2 for Polycoms. I found out there is not a way to set the > option in > > the configuration files because if attendant.uri is set then the > > automata settings are ignored. > > > > Here is a reference from a year ago from Paul Mossman and > Dale Worley. > > > http://www.mail-archive.com/[email protected]/msg04784.html > > Did this ever go beyond discussion? > > > > > _______________________________________________ > sipx-dev mailing list [email protected] List > Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > sipXecs IP PBX -- http://www.sipfoundry.org/ > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
