"system_telephonysearch" would be really useful but needs documenting and a little updating Merged

For any third party that wants to integrate telephony to our CRM (we've had one request but we might want to encourage more), or for our own integration of TAPI or Twilio,  "system_telephonysearch"  would be really useful.

However there are a couple of issues (and maybe a better, alternate plan at the end):

1. It's not available through the API - this should be quick to fix

2. The system_telephonysearch has duplicates in it. I think (but we should check) that we need an upgrade script to delete all entries in telephonysearch " where addphoneid=0 and objecttype='contact' ". This is because we used to populate the "PrimePhone" from the contact into telephonysearch. But then as part of 365 we now always duplicate "PrimePhone" from the contact into addphone ... which means for many records it is there twice.

3. we should check that setting a new primephone on a contact doesnt then create more duplicates this way (I dont think it does as i think the trigger on contact that used to update telephonysearch has been removed)

4. re-instate a division trigger to update telephonysearch when the division phone number is set, updated or deleted (as division phone numbers dont get added to addphone).

OR ALTERNATIVELY, update addphone so that it includes the divisionID, and allow the contactID to be null, and then put all the division numbers into addphone too... and put the useful indexes and things like the stripped out phonenumberdigits field and reversephonenumber fields into addphone and drop this special search table (you could just use addphone) ... and probably reduce the total number of triggers too.