Caller ID Superfecta

I don't want to screw up the database and the install/upgrade process. If one of you knows well the way everything is linked together, please jump in to add this checkbox in the scheme general option.

svn rev 203, update to previous rev to:
- improve the display in debug mode (reencode in utf8 for display)
- convert html entities returned by a few sources to ascii

Please test this version.
If no bugs are found, I would suggest to release it as is (with the $charsetIA5 forced to true as it should work with all phones).
The ability to choose between IA5 and extended ASCII could be a feature for a future release but is not a priority.

Would the forced IA5 be better in each data source - instead of global?

No, it should be global as it is related to the phones on your PBX not the source you are querying.

I can think of no way to set this on a per-phone basis. Thats where it would be the most effective....

I am leaning to do as you suggest. Release without interface change, hard coded to forced the change. The worst result is that some phones do not use all their capabilltieis, best result is that ALL phones will at least display something.

QS: Pass Accepted for build 2.2.2

The filter will be hard coded to enabled, pending future releases that expose the setting in the ui.

Sorry I've been absent the past couple of weeks...been busy trying to get my house on the market. If anyone is looking to buy a house in the St. Louis area, mine is for sale at 211hawksrest.com :) (website is not 100% complete as of this writing, but will be soon)

Back to business. I'm re-opening this to remind me to implement this feature for the next release.

Couple of thoughts, currently are no completely global variable, the closest they come is variables for an entire scheme. I could added a global variable for this option, but we may want it in individual schemes and here is why:
Admittedly this is a weak argument, but I thought I'd bring it up. Someone could have a set of phones enabled with extended characters sets that are used as part of a call group for international calls, and phones that were meant for US calls. They could have inbound routes and CID schemes set up for those inbound international calls that route to the phones with extended character sets, and use a second CID scheme for inbound calls that go do the IA5 display phones.

It's not a big issue to have it by scheme as long as the value is present with the default setting, it just fill the database.
Also we will have to redo a full source test when IA5 is disabled to make sure that everything is still working properly. My preliminary tests were ok but I haven't done the same extensive debug session than when IA5 was enabled.

Also, right now it's not a fully IA5 compliant filter I've coded, but just a basic accent removal. There are two or three minor differences between ASCII and IA5 and I should implement these changes later on. But I'm not even sure that our phones will see the difference.

By looking at the database and the install/upgrade script, I'm not sure that there's a full cleanup of all the pre-scheme era database info. There may be some unused values that are filled by the script. Maybe need to open a new ticket for that.

This ticket hasbeen closed as part of 2.2.2. I have copied this ticket to a new ticket in `future versions` to document the next phase of this upgrade. Please make no further notations here unless its about 2.2.2.