9641 missed call log not working

[tele234]

Have customer with CM 5.2.1 and they have many 9641 telephones administered as 9650 - however the missed call log is not working and the sets have H.323 SP 3 loaded and customer is going to install SP 4, however the SP did not mention in the release notes that it corrects miss call log. I am thinking the issue is in the 46xxsetting.txt file - however I am not sure. I am unable to find anything pertaining to this on Avaya support.

 

[montyzummer]

you need to give a bit more information as to the exact issue but underneath are the call log settings , it culd also be something to do with the ars access code.


## PHNSCRALL specifies whether separate screens will be displayed for call appearances and features.
## Value Operation
## 0 Separate screens will be displayed for call appearances and features (default)
## 1 A consolidated screen will be displayed that includes call appearances and features
## This parameter is supported by:
## 96x1 H.323 R6.0 and later
## SET PHNSCRALL 1
##
## EOEDITDIAL specifies whether a # character will be inserted at the end of Edit Dialing strings.
## Value Operation
## 0 # will not be inserted
## 1 # will be inserted (default)
## This parameter is supported by:
## 96x0 H.323 R3.2 and later
## SET EOEDITDIAL 0
##
## FBONCASCREEN specifies whether features will be displayed on the same screen as call appearances
## when the value of PHNSCRALL is 0.
## Value Operation
## 0 Features will not be displayed on the same screen as call appearances (default)
## 1 As many features as will fit will be displayed on the same screen as call appearances,
## in addition to being displayed on a separate feature screen.
## This parameter is supported by:
## 96x1 H.323 R6.0 and later
## 96x0 H.323 R3.0 and later
## SET FBONCASCREEN 1
##
##################### CALL LOG SETTINGS ####################
##
## CLDISPCONTENT specifies whether the name, the number, or both will be displayed for Call Log entries.
## Value Operation
## 0 Both the name and the number will be displayed
## 1 Only the name will be displayed (default)
## 2 Only the number will be displayed
## This parameter is supported by:
## 96x1 H.323 R6.0 and later (only supports values of 0 or 1)
## 96x1 SIP R6.0 and later (only supports values of 0 or 1)
## 96x0 H.323 R3.2 and later
## SET CLDISPCONTENT 0
##
############## CALL LOG SETTINGS (H.323 ONLY) ##############
##
## CLDELCALLBK specifies whether a Call Log entry will be deleted when a callback is initiated
## by pressing the Call softkey from the entry's Details screen.
## Value Operation
## 0 Entries will not be deleted when a callback in initiated (default)
## 1 Entries will be deleted when a callback in initiated
## This parameter is supported by:
## 96x1 H.323 R6.0 and later
## 96x0 H.323 R3.0 and later
## SET CLDELCALLBK 1
##
## LOGMISSEDONCE specifies whether Call Log will display more than one
## missed Call Log entry from the same caller.
## Value Operation
## 0 Multiple Call Log entries will be displayed per caller (default)
## 1 Only one missed Call Log entry will be displayed per caller
## This parameter is supported by:
## 96x1 H.323 R6.0 and later
## 96x0 H.323 R3.0 and later
## SET LOGMISSEDONCE 1
##
## LOGUNSEEN specifies whether incoming calls that did not cause alerting will be logged
## as missed calls (e.g., calls that are forwarded because the phone is busy).
## Value Operation
## 0 Unseen calls will not be logged (default)
## 1 Unseen calls will be logged
## This parameter is supported by:
## 96x1 H.323 R6.0 and later
## 96x0 H.323 R3.0 and later
## SET LOGUNSEEN 1
##
## LOGBACKUP specifies whether Call Log entries will be backed up to,
## and restored from, the backup/restore file.
## Value Operation
## 0 Call Log entries will not be backed up and restored
## 1 Call Log entries will be backed up and restored (default)
## This parameter is supported by:
## 96x1 H.323 R6.0 and later
## 96x0 H.323 R3.0 and later
## SET LOGBACKUP 0
##
## CLBACKUPTIMESTAT specifies whether Call Log entries will be backed up only after
## a minimum interval as specified by the value of CLBACKUPTIME.
## Note that this parameter only has an effect if the value of LOGBACKUP is 1.
## Value Operation
## 0 Call Log entries will be backed up as they are created (default)
## 1 Call Log entries will be backed up after the interval specified by CLBACKUPTIME
## This parameter is supported by:
## 96x0 H.323 R3.1.3 and later
## SET CLBACKUPTIMESTAT 1
##
## CLBACKUPTIME specifies the minimum interval, in minutes, between backups of the Call Log,
## if the values of LOGBACKUP and CLBACKUPTIMESTAT are both 1.
## Valid values are 10 through 60; the default value is 15.
## This parameter is supported by:
## 96x0 H.323 R3.1.3 and later
## SET CLBACKUPTIME 20

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[tele234]

Thanks however I was able to test with user and have better details:
1. if Caller hangs up before modular messaging answers then the missed call log shows entry.
2. If caller goes to voice mail - then the answered log is showing Modular Messaging with no caller number, the log just says Modular Messaging!
3. Now in the message header I we can hear all the caller details so that is working.
4. On an other system the call history log shows the caller ID of who called, and it was answered by messaging.

Just now the answered log is showing modular messaging and not the caller ID of who I calling.

 

[montyzummer]

can you not compare the 46xx settings file from the working switch and look for differences?

APSS (SME)
ACSS (SME)
ACIS (UC)

 

[tele234]

Monty - thank you will try that suggestion - compare the 46xxsettings file. I will try

 

[tele234]

it was the 46xxsettings.txt file logunseen was not enabled now working