View Single Post
  #3  
Old 08-07-2013, 08:07 AM
davis124 davis124 is offline
Brainiac
 
Join Date: Oct 2011
Location: Omaha, NE
Posts: 50
davis124 has 12 reputation points
Exclamation

Alrighty...

Looks like another error in Avaya documentation, according to their own Internal information. I found a Insite Article: SOLN229827

PROBLEM CLARIFICATION

Can't dial with call type analysis table from phone's contacts list

CAUSE

According to the CM system feature guide, the phone signals for Call Type Digit Analysis when the user places a call from the phone’s call log or from the contacts or corporate directory. The telephone sends to Communication Manager the information stored in the call log, or from the list of contacts or the corporate directory. Communication Manager uses the Call Type Digit Analysis Table to analyze the stored number, determines a corresponding dialable number, and makes the call.

The telephone assumes the numbers in the Contacts application are in dialable format and all other numbers in the Redial buffer(s), Call Logs, and browser ‘click-to-dial’ links, are not in dialable format.

Per 3.2 administration guide: https://downloads.avaya.com/css/P8/documents/100169217 log dialing digit analysis is requested for all calls originated by the Redial buffer(s), the local Call Logs, and all web-based dialing.

This feature is not applicable for contacts dialing.

SOLUTION

This feature is not applicable for contacts dialing; phone working per design


According to phone specifications MR 54395+54389 COMPAS 111781+141818 COMPAS 141818 96xx 3.1 test plan for smart enbloc dialing: The telephone assumes the numbers in the Contacts application are in dialable format and all other numbers in the Redial buffer(s), Call Logs, and browser ‘click-to-dial’ links, are not in dialable format.


So Contact Dialing is NOT supported via EnBloc Dialing, does anyone know if there is a suitable work around? I can't seem to get the Contact Lists to use the Enhanced Dialing Rules found in the 46xxsettings file either.


James E. Davis
Reply With Quote