function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Paul MartinPaul Martin 

Open CTI onClickToDial

I have created the "Sample HTMLPage Using Open CTI" from the Open CTI Developers guide and added the "onClickToDial" Method.

When I click multiple numbers, i.e. go down through a list of contacts and click the phone number associated with the contact

The Phone numbers returned by the Method are ok until I click a number above the last number I click in the list.

Once I do this it appears the Method no longer works correctly.  I have tried multiple patterns which return multiple results.  The only consistency is the fact the phone numbers returned will not be correct unless you happen to get the pattern I tested below... Once this pattern happens, you will have the phone number be correct when you click to dial the phone number that is being repeated (1234567892).

i.e.  I have the following phone numbers in a list of contact.  All Contacts are different
1234567890
1234567891
1234567892
1234567893
1234567894

1st Click to Dial: 1234567890 Returns: 1234567890
2nd Click to Dial: 1234567891 Returns: 1234567891
3rd Click to Dial: 1234567892 Returns: 1234567892
4th Click to Dial: 1234567893 Returns: 1234567893
5th Click to Dial: 1234567894 Returns: 1234567894
Go back to the top of the list
6th Click to Dial: 1234567890 Returns: 1234567890
7th Click to Dial: 1234567891 Returns: 1234567892
8th Click to Dial: 1234567892 Returns: 1234567892
9th Click to Dial: 1234567893 Returns: 1234567892
10th Click to Dial: 1234567894 Returns: 1234567892
All other Click to Dial attempts result in phone number "1234567892" being returned until I refresh the page.  After refreshing the page, the pattern may change.

Has anyone else seen this issue...  Not sure how this has not been noticed until now.

I tried this with Open CTI API 25 and 32... Same results

Is there a specific sequence of API calls that have to be performed... maybe a History refresh after every Click to Dial

Any help would be appreciated

Thanks

Lachlan DeckLachlan Deck
This is still an issue in 37.0. Any fix in the works?
jarsjars
We are seeing the same behavior.

This is a terrible user experience issue, surprised it hasn't been fixed by Salesforce after all this time!
The only "workaround" we know to work (which is not!) is to refresh the page!