Just notice this in the 3.2 admin guide: Note: If attendant.uri is set, then the individually addressed users configured by attendant.resourceList and attendant.behaviors attributes are ignored.
Is one touch transfer not possible with Broadsoft eventlist BLF then? I'm confused. Josh Patten Assistant Network Administrator Brazos County IT Dept. (979) 361-4676 On 2/26/2010 2:08 PM, Josh Patten wrote: > I would do this one myself by editing files in /etc/sipxpbx/polycom but > the X part of attendant.resourceList.x.type must be a number > corresponding to the BLF key, which can really get hairy if the users > changes their BLF settings if it isn't managed in the speed dials area. > If there were a setting to just set all the BLF entries on a phone to > one type or the other then that would be great too but I'm not seeing one.. > > Josh Patten > Assistant Network Administrator > Brazos County IT Dept. > (979) 361-4676 > > > On 2/26/2010 1:35 PM, Josh Patten wrote: > >> Awwwwww....Was kinda excited about that >> >> In any case, would it be possible to add the >> attendant.resourceList.x.type configuration option? Should I open a ticket? >> >> Josh Patten >> Assistant Network Administrator >> Brazos County IT Dept. >> (979) 361-4676 >> >> >> On 2/26/2010 1:09 PM, Scott Lawrence wrote: >> >> >>> On Fri, 2010-02-26 at 12:35 -0600, Eric Varsanyi wrote: >>> >>> >>> >>>> I'm working on some sipxconfig/polycom plugin changes that will let >>>> you supply raw polycom config by uploading a managed file and >>>> selecting that file from each phone (or group of phones). For phones >>>> with this attribute set the file is included in the top level list of >>>> config files in the 'root' config file (the one built for each mac >>>> address). I'm doing it to get the EFK and some fancy sound effects >>>> functionality (w/o writing pages of EFK related UI which seems over >>>> the top). >>>> >>>> This might help if I ever get it done and accepted :) >>>> >>>> >>>> >>> Not to discourage you or anything, but the likelihood that we'd take a >>> change that allowed an externally produced phone configuration file to >>> be loaded or merged with one produced by sipXconfig is very very small. >>> There's no way to test such a feature, and while you may be competent to >>> use it, most who tried would not be. >>> >>> >>> >>> >>> >>> >> _______________________________________________ >> sipx-users mailing list [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users >> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users >> sipXecs IP PBX -- http://www.sipfoundry.org/ >> >> > _______________________________________________ > sipx-users mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > sipXecs IP PBX -- http://www.sipfoundry.org/ > _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
