Questions regarding the 96xx & 96x1 Call History Logs

[davis124]

Hello Everyone -

I have a couple of questions for the group regarding the 96xx and 96x1 Call History Logs...

1. Why does the 9621 and 9641 call log on the first part of the screen turnicates the number to 6 digits even though it recorded the entire 10 digit string? When you drill down on the entry it will show the complete number (If it was an outside caller)... Is there a fix for this? The 9650 I have for testing will show the entire number on the first screen (I know it's a different phone) so I am just wondering if this is a bug, over sight, or a "Working As Designed" issue from Avaya.

2. On all my phones when a Long Distance number comes in, we get the display and the Call History Log records the correct number. When we go to dial it two things will happen:

• If we have the PHNLD set to 1 in the 46xxsettings file, Long Distance will dial out fine, but with this setting to 1 it will attempt to dial 10 digit local calls as Long Distance call by adding the 1.

• If we turn off the PHNLD, then the Long Distance call fails because it didn't insert the 1, but our local calls work fine (Not routing out the Long Distance trunks) because we are no longer inserting a 1

I want to know HOW do you set this up so the phone will determine that the call is Long Distance and add the one, while maintain the local 10 digit dialing rules we need for Local Calling (By not adding a 1). Below is a copy of how we currently have our ENHANCED LOCAL DIALING RULES setup in the 46xxsettings file.

############# ENHANCED LOCAL DIALING RULES ###############
##
## These settings affect certain dialing behaviors, such as
## dialing numbers from the incoming Call Log or from web pages
##
## Dialing Algorithm Status
## Controls whether algorithm defined by parameters in
## this section is used during certain dialing behaviors.
## 0 disables algorithm.
## 1 enables algorithm, but not for Contacts
## 2 enables algorithm, including Contacts (96xx SIP only)
SET ENHDIALSTAT 2
##
## Country Code
## For United States the value is '1'
SET PHNCC 1
##
## Internal extension number length
## If your extension is 12345, your dial plan length is 5.
## On 46xx phones, the maximum extension length is 10.
## On 96xx phones, the maximum extension length is 13.
## This value must match the extension length set on your
## call server.
SET PHNDPLENGTH 5
##
## International access code
## For the United States, the value is 011.
SET PHNIC 011
##
## Long distance access code
SET PHNLD ""
##
## National telephone number Length
## For example, 800-555-1111 has a length of 10.
SET PHNLDLENGTH 10
##
## Outside line access code
## The number you press to make an outside call.
SET PHNOL *9
##

Thanks for any and all your help on this!

James E. Davis

[mskinner]

1. Why do we truncate? Because we allocate a specific piece of display real estate for Number, and for Name, and we don't overlap.

2. The phone can't tell a 10-digit local number (extension?) from a 10-digit US National number, and so assumes the 10 digits are a US National number, which needs a 1 in front.

[davis124]

Thanks for getting back to me on this -

So your answers have fostered more questions and an observation:

1. Why do we truncate? Because we allocate a specific piece of display real estate for Number, and for Name, and we don't overlap.

Is there any plans or ways to customize this to show the entire number on these phones? It's alittle silly to show 6 digits of an outside number, I understand the real estate issue but giving the end user/admin the control to show what is displayed would be good. At the preset time I get a lot of Unavailable names and 6 digits for outside numbers. Just a thought and question...

2. The phone can't tell a 10-digit local number (extension?) from a 10-digit US National number, and so assumes the 10 digits are a US National number, which needs a 1 in front.

I have found more info on this just by poking around and talking with others, there seems to be a dependency with the CM command CHANGE CALLTYPE ANALYSIS and how these phones make calls out of the logs... Does Avaya have a good all in one document that talks about how to setup the CALLTYPE ANALYSIS as well as the 46xxsettings.txt file to get these phones to call out of its logs correctly? The feature and/or Admin guide isn't the best at describing this command (Or at least what I have read)

I have been able to play around with that CM command and get Long Distance calls to flow with a 1, but it's going to be harder to do with the local area since we have to dial some numbers 10 digit and others 11 digit all in the same area code.

Thanks,

James

[faizanaqeel]

96xx Call logs show - Unavailable

Hi,
can anyone help me in removing this unavailable from this call logs . as my customer is very annoyed with this Unavailable coming in the call logs he only wants the number.. if its not a saved contact,

i was just wondering if it cannot be removed then can we like change the layout how it shows.. like we can see the number only...

thanks,
FA