Log Digit (Smart Enbloc) Dialing help?!?!

[davis124]

I am hoping someone in this group can help me understand a feature that appears to have been introduced in CM 4.x that allows the IP Phones (And in CM 5.x DCP phones) to start doing ENBLOC dialing from their Call Logs and Contact Lists. I am trying to impliment this feature according to the Avaya documents, and for some reason it's not working. I am looking to find folks that have successfully implimented THIS feature and not the Enhanced Dialing Rules found in the 46xxsettings file (As we have found those rules do not work well in our type of dial plan).


We are running CM 5.2.1, with SP 11 and all of the test IP Phones in question have the latest firmware loads on them.


According to the 96xx Adminstrators Guide here is the feature I am looking to get more information and some help in setting up:

Log Digit (Smart Enbloc) Dialing


Avaya Communication Manager (CM) Releases 4.0 and up give the call server the potential to provide a superior level of enhanced "log digit analysis." This feature (also called smart enbloc dialing) allows the call server to supplement the number the telephone dials based on the callserver’s knowledge of the entire dialing plan. With the server supporting log digit dialing analysis, the telephone does not attempt to enhance a number as described for enhanced local dialing, and the call server assumes responsibility for analysis and action. Smart enbloc provides a more accurate dialing method because the telephone signals to the call server thatlog dialing digit analysis is requested for all calls originated by the Redial buffer(s), the local CallLog/History applications, and all web-based dialing.


So after reading that information, it points me to the Feature Description and Implimentation guide which also "Seems pretty straightforward:


Enbloc Dialing and Call Type Digit Analysis


Use the Enbloc Dialing and Call Type Digit Analysis feature to allow users to automatically place outgoing calls based on the telephone number information in the telephone’s call log,without the user having to modify the telephone number.


Detailed description of Enbloc Dialing and CallType Digit Analysis


Enbloc Dialing is the ability of Communication Manager software to receive in one message all of the digits necessary to set up a call, or any time the terminal makes a request rather thanreceiving digits one at a time. Call Type Digit Analysis is the ability for Communication Manager to decide how to route a callbased on all of the digits in a telephone number in a call log. The system administrator maintains the Call Type Digit Analysis Table, which is similar to AAR and ARS Routing Tables. A 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 corporatedirectory. Communication Manager uses the Call Type Digit Analysis Table to analyze the stored number, determines a corresponding dialable number, and makes the call.The Enbloc Dialing and Call Type Digit Analysis feature is available with Communication Manager 4.0, or later. It works in conjunction with Avaya terminals (proprietary signaling protocol): DCP, IP (H.323) and IP (SIP) terminals (96xx H.323 IP telephones, Avaya one-X Mobile Edition for S60 3rd Edition Dual-Mode SIP phones).When the Communication Manager software finds a match between a dialed digit-string and an entry on the Call Type Digit Analysis Table:


1. Communication Manager deletes and inserts digits according to the first priority administered for that string. Numbers on the Table indicate priority.


2. Communication Manager tests the modified digit string against the administered call type ext, udp, aar, or ars.

Note: ext covers the extension entries in the dialplan analysis tables, and udp covers the entries in the uniform-dialplan tables. The value in the UDP Extension SearchOrder field on the dialplan parameters form determines the order for checking thetables.


3. If the modified digit string matches a digit analysis entry for the administered call type, inboth digits and string length, Communication Manager routes the call.


4. If the modified digit string matches no entries for the administered call type,Communication Manager deletes and inserts digits according to the next priorityadministered for that string, and continues to test the modified digit string against the administered call type.


5. When Communication Manager finds no match between a dialed digit-string and an entryon the Call Type Digit Analysis Table, it routes the call using the system dial plan.


6. An IP phone receives notice that entries exist in the Call Type Digit Analysis Table when the phone registers. If there are no entries when the phone registers, the telephone will not use call type even when an entry is added after the telephone is registered. The telephone processes new entries after it unregisters and reregisters.



So it sounds very straight forward, all except the fact that even with CallType Digit Analysis entries in the table, and a IP Phone rebooted the phones do not seem to use Enbloc dialing (AKA Notice the entries). So at this point none of the IP Phones we are testing with will put the ARS code in front of the outbound numbers as we need them to do.


James E. Davis

[davis124]

Well playing around with it some more has netted some interesting results...

I have now got the Call Log to use this table, and show the IP Phone trying to make a match on the CallType in traces.

What appears to be still failing (Or at least according to the Feature Description guide) is Contacts still want to try and dial an extension instead of a number.

More updates when I get them...

[davis124]

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

[psmillie]

As of release 6.6.2 of the IP H.323 Firmware there is a new parameter in the 46xxsettings.txt file which controls whether Enbloc dialling is applied to numbers from the Contacts List. The parameter is called CTASTAT. The default value is 1, which means to not apply Enbloc dialling to Contacts. The alternative value of 2, which means apply Enbloc dialling to Contacts.