On Wed, Jan 27, 2010 at 12:16 PM, Eric Varsanyi <[email protected]> wrote:
> Agreed the EFK stuff would be "easy" to add (I might try to add that one > the right way while I'm doing this other thing). I might also try to > officially add the ability to set the SAF (ringtone) files, that seems > simple enough (just a form with 16 text entries). > > The progress tones/chords/sound effect system is deep enough that it would > likely be as much custom UI to do just it as we have today for everything > else :). > > FWIW with 3.2 the shared line stuff is actually working about as I'd expect > it to (with 3.1.x the phones were easily confused by playing with shared > lines). > hooray! :>) > Aside from the 'beep' appearing on intercom calls I have yet to pin any > problem in my test sandbox on 3.2.2 (unlike the SPA3102 which was the cause > of just about every problem I had). > > -Eric > > On Jan 27, 2010, at 11:09 AM, Tony Graziano wrote: > > No, by modifying the velocity template you are on the right track. I might > mention there may be some known issues with 3.2 firmware from polycom. > > I think it might be less problematic (but what do i know) to add the > configuration parameters directly to sipx. It will certainly cause fewer > issues with end users. > > I for one would like to see some built-in EFK functionality for blind > transfer/park, etc. > > On Wed, Jan 27, 2010 at 12:03 PM, Eric Varsanyi <[email protected]> wrote: > >> Thanks! Good to get some feedback I'm not just missing something obvious. >> >> What I'm doing now since I'm running from SVN is I've changed the source >> for the velocity template mac-address.cfg-vm so when I do 'svn update's my >> changes stick. I am of course running all this in a sandbox and I have a >> pre-production VM (well, its still all pre-production but I have the setup >> anyway) to test with before rolling out changes. The pre-production VM is >> what led me to want to make configurations portable between machines >> (export/import functionality). Right now I just use a separate VLAN and >> stuck some NAT magic into the router between the real network and the >> sandbox so I can ssh/https to the test box yet leave it instantly clonable >> to the production side. >> >> Another way I think might work with minimal changes to the current UI >> would be to have a setting that's just a textbox and accepts a block of raw >> config XML that will be inserted up front (into the xxxxxx-sipx-sip.cfg >> file). This would most definitely be an 'advanced' setting :). This way one >> could use the existing group configuration layering to good effect with >> changes like this. If there's any support for this idea I'll give it a try. >> >> -Eric >> >> On Jan 27, 2010, at 10:54 AM, Tony Graziano wrote: >> >> I think there is a way to manually edit the polycom template that sipx >> produces that would make this work for you, but on system updates, your >> custom modifications could be overwritten (template replaced) and would have >> to be re-re-entered before generating new profiles. Additionally firmware >> updates could also change the syntax so reading about the changes would be >> required before implementing. I would suggest a test system (vmware or xen) >> would be adequate with one or two phones to provide a test environment >> before copying your changes to a production system. >> >> The same approach could be used for the EFK (Enhanced Function Key) >> programming. >> >> At the same time, it sounds like a good candidate for an enhancement >> request. >> On Wed, Jan 27, 2010 at 11:43 AM, Eric Varsanyi <[email protected]> wrote: >> >>> I'm doing this on SVN 17748 with Polycom 3.2.2 firmware so I thought this >>> would not be appropriate for -users. >>> >>> The direct question is: is there really a more appropriate way (than >>> manual configuration as describe below) to get custom "ringtones" onto the >>> polycoms and update call progress tones? I just want a different, non >>> factory, ring available for folks local directories and to assign to >>> different shared lines. Where we use intercom support I want the intercom to >>> start silently if so configured in the UI (as of 3.2.2 the default INTERCOM >>> progress tone is a 500ms beep even if you ask for silent in the UI). >>> >>> What I'm doing now that is working for me, but seems "against the grain": >>> >>> (in the top level velocity template file added the first CONFIG_FILES >>> element for -local): >>> >>> <APPLICATION >>> APP_FILE_PATH="sip.ld" >>> CONFIG_FILES="[PHONE_MAC_ADDRESS]-local.cfg, >>> [PHONE_MAC_ADDRESS]-sipx-sip.cfg, [PHONE_MAC_ADDRESS]-sipx-phone.cfg, >>> [PHONE_MAC_ADDRESS]-sipx-device.cfg, polycom_phone1.cfg, polycom_sip.cfg" >>> MISC_FILES="" >>> OVERRIDES_DIRECTORY="" >>> CONTACTS_DIRECTORY="" >>> LOG_FILE_DIRECTORY=""> >>> >>> In the xxxx-local.cfg file (which for testing I've manually stuck in the >>> tftpboot directory, I'm assuming I can add it as an unmanaged file through >>> the UI later): >>> >>> <?xml version="1.0"?> >>> <!-- SIP Application Configuration File --> >>> <!-- $RCSfile: sip.cfg,v $ $Revision: 1.558.2.3.2.11.2.2 $ --> >>> <sip> >>> <tones> >>> <chord_sets> >>> <CALLPROGRESS> >>> <INTERCOM tone.chord.callProg.10.freq.1="550" >>> tone.chord.callProg.10.level.1="-19" tone.chord.callProg.10.onDur="1" >>> tone.chord.callProg.10.offDur="0" tone.chord.callProg.10.repeat="1"/> >>> </CALLPROGRESS> >>> </chord_sets> >>> </tones> >>> <sampled_audio saf.1="" saf.2="ring13.wav" saf.3="ring14.wav" saf.4="" >>> saf.5="" saf.6="" saf.7="" saf.8="" saf.9="" saf.10="" saf.11="" saf.12="" >>> saf.13="" saf.14="" saf.15="" saf.16="" saf.17="" saf.18="" saf.19="" >>> saf.20="" saf.21="" saf.22="" saf.23="" saf.24=""/> >>> </sip> >>> >>> The wiki page talking about config file updates is wonderful but it >>> doesn't address things that are either inappropriate for the UI (a whole >>> sound effects/progress tone editor seems out of scope of the project) or are >>> for whatever reason just not supported (fancy softkey support, ability to >>> map the 'flexible' key on the Ip 335's). >>> >>> I tried searching the issues database for something like this but I >>> didn't directly see an open issue asking for the ability to merge in local >>> manual changes, this really makes me think I'm just trying to do this all >>> wrong. >>> >>> Thanks, >>> -Eric Varsanyi >>> >>> _______________________________________________ >>> 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/ >>> >> >> >> >> -- >> ====================== >> Tony Graziano, Manager >> Telephone: 434.984.8430 >> Fax: 434.984.8431 >> >> Email: [email protected] >> >> LAN/Telephony/Security and Control Systems Helpdesk: >> Telephone: 434.984.8426 >> Fax: 434.984.8427 >> >> Helpdesk Contract Customers: >> http://www.myitdepartment.net/gethelp/ >> >> Why do mathematicians always confuse Halloween and Christmas? >> Because 31 Oct = 25 Dec. >> >> >> > > > -- > ====================== > Tony Graziano, Manager > Telephone: 434.984.8430 > Fax: 434.984.8431 > > Email: [email protected] > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > Fax: 434.984.8427 > > Helpdesk Contract Customers: > http://www.myitdepartment.net/gethelp/ > > Why do mathematicians always confuse Halloween and Christmas? > Because 31 Oct = 25 Dec. > > > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
_______________________________________________ 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/
