Comprehensive Custom Ringtone Guide

[Brad303]

Hi all,

I've spent a few hours playing around with custom ring tones on a VVX 450 running 6.3.1.11465 and decided to write a guide to hopefully save others some of the headaches I encountered getting them up and running.

The UC Administrator Guide documents most of the settings, but as is all too common with Poly phone configs, putting the pieces together isn't quite as simple or intuitive as one might hope.

The guide is broken down into 3 parts, all of which are included as provisioning configuration files in the attached zip.

• custom-ringtones-simple.cfg outlines the basic settings to load a custom audio file as a ringtone on the phone and enable it.
• custom-ringtones-advanced.cfg goes into more detail, demonstrating how to use multiple sampled audio files, as well as building ringer patterns.
• custom-ringtones-chords.cfg shows you how to build custom ringtones using synthesized chords instead of sampled audio files.

There are extensive comments in each file that should clear up any confusion, but feel free to reply to this thread with any questions, corrections, comments, or feedback.

The zip also contains the sampled wav files I used in the examples, so you should be able to upload the files into the "ringtones" directory on your provisioning server, and enable the example configs in the CUSTOM_FILES parameter.

During my extensive testing, I found a number of quirks in how the phone behaves, which appear to be in conflict with the Administrator Guide. Whether these are bugs or undocumented "features", I'm not sure. I'll be following up with another post detailing my findings in the hopes of clarifying the correct and intended behavior.

I hope this helps!

Brad

[SteffenBaierUK]

Hello @Brad303 ,

Welcome to the Poly Community.

Thanks for being part fo the community and I have added a link to our original FAQ:

Oct 25, 2011 Question: How can I change my Ringtone or Ring in a special manner for a certain incoming call?

Resolution: Please check => here <=

Best Regards

Steffen Baier

[Brad303]

Hi Steffen,

By chance, did you look at the files I attached?

While the custom-ringtones-simple.cfg file does indeed contain what's already in the FAQ, the custom-ringtones-advanced.cfg covers using multiple sampled audio files and ringer instructions (which was not working properly in 6.3.1.11465). custom-ringtones-chords.cfg shows administrators how to create custom chords and implement them as ringtones (which also is not working as described in the Administrator Guide).

I spent no small amount of time not only working out how all of this works, but documenting it for future reference.

Simply linking to the FAQ would indicate that my post itself wasn't read, let alone the attached files. I know you're the only Poly guy here, Steffan, and I appreciate all the help you've given me and others over the years, but please do take another look at my submission.

Brad

P.S. I've been on the forum for years, but my old account was associated with a company I no longer work for.

[SteffenBaierUK]

Hello @Brad303 ,

Welcome back to the Poly Community.

Yes, I did check it and looked at it too. This is the reason I added it to the FAQ for anyone struggling. I was waiting for a follow-up to outline issues in our documentation so I can work with the doc team on this.

Best Regards

Steffen Baier

[Brad303]

My apologies, Steffan! I didn't see the mention in the FAQ when I first looked, but I see it's there now.

As far as the differences between the documentation and what actually happens, I have rather extensive notes in the three files as to the behavior. To recap:

• Sampled audio files less than 1s repeat after a 4s interval
• Sampled files >1s and <2s play once with a 4s interval, then play continuously
• Sampled files >2s play continuously
• Only the last sampled audio file in the pattern plays
• The branch pattern instruction is ignored; the pattern repeats regardless with both chords and sampled audio files

I verified that I wasn't approaching the memory limitation when testing, so I think the above behaviors are simply bugs in the code. The files I provided should make it trivial for an engineer to duplicate the issues.

Brad