Preview Tool

Cisco Bug: CSCvw01449 - Do not Disturb (DND) device feature status set issue for CUCM

Last Modified

Oct 09, 2020

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases


Description (partial)

Following is the technical logs details in order to verify different DND phone status issue w.r.t CUCM 14 and 12.5.

2.1.1 Successful Scenario with CUCM 12.5 

CUCM System Version =
Contact Phone DN = 48002

From following CTI logs it can be seen that when console user tries to change DND status of contact/phone application called the LINE_DEVSPECIFICFEATURE API. So in order to get DND status, CT driver is providing all TAPI events to the application which can be verified from logs i.e. DND status is enabled successfully.

//CTI logs
28/09/2020 14:57:12.679 "T:10" "D" [-9]:CTD: 1:CTAPISetDoNotDisturb
28/09/2020 14:57:12.679 "T:10" "D" [-9]:CTD: 1:CTAPISetDoNotDisturb - Device>'[SEP04C5A4B167B1:48002:1]'
28/09/2020 14:57:12.679 "T:10" "D" [-9]:CTD: 1:CTAPISetDoNotDisturb - DndInd=0
28/09/2020 14:57:12.680 "T:10" "D" [-9]:CTD: 1:CTAPISetDoNotDisturb - lineDevSpecificFeature(PHONEBUTTONFUNCTION_DONOTDISTURB)=10012h

28/09/2020 14:57:12.685 "T:37" "D" [-9]:CTD: 1:Line TAPI ( t=469687, d=0, m=C, i=2A, p1=10012, p2=0, p3=80000266 )
28/09/2020 14:57:12.685 "T:37" "D" [-9]:CTD: 1:LINE_REPLY [SUCCESS]=10012h
28/09/2020 14:57:12.685 "T:37" "D" [-9]:CTD: 1:CTAPIProcessLineReply.Enter [LockEvenList] > InvokeID=10012h, Status=0h
28/09/2020 14:57:12.685 "T:37" "D" [-9]:CTD: 1:CTAPIProcessLineReply.In [IsAvailable] > InvokeID=10012h, Status=0h
28/09/2020 14:57:12.685 "T:37" "D" [-9]:CTD: 1:CTAPIProcessLineReply.Out [IsAvailable] > InvokeID=10012h, Status=0h
28/09/2020 14:57:12.685 "T:37" "D" [-9]:CTD: 1:CTAPIProcessLineReply - [Node not found] > InvokeID=10012h, Status=0h
28/09/2020 14:57:12.685 "T:37" "D" [-9]:CTD: 1:CTAPIProcessLineReply.Leave [UnLockEventList] > InvokeID=10012h, Status=0h
28/09/2020 14:57:12.989 "T:37" "D" [-9]:CTD: 1:Line TAPI ( t=470000, d=10045, m=5, i=2A, p1=1A, p2=1, p3=1 )
28/09/2020 14:57:12.989 "T:37" "D" [-9]:CTD: 1:LINE_DEVSPECIFICFEATURE(DONOTDISTURB.STATUS_CHANGED.DoNotDisturbOperation_ENABLE) > Address=48002, hLine=10045h
28/09/2020 14:57:12.990 "T:37" "D" [-9]:CTD: 1:LINE_DEVSPECIFICFEATURE > Device=48002, OldDND=0, NewDND=1
28/09/2020 14:57:12.990 "T:37" "D" [-9]:CTD: 1:DFE - DDID:[SEP04C5A4B167B1:48002:1], D:48002, P:101, E:30, S:1, EC:14

2.1.1 UNSuccessful Scenario with CUCM 14

CUCM System Version =
Contact Phone DN = 1012

From following CTI logs it can be seen that when console user tries to change DND status of contact/phone application cannot get any response from LINE_DEVSPECIFICFEATURE API, resulting DND status remains Disabled which can be verified from following logs.

//CTI logs
28/09/2020 14:33:39.312 "T:10" "D" [-9]:CTD: 1:CTAPISetDoNotDisturb
28/09/2020 14:33:39.312 "T:10" "D" [-9]:CTD: 1:CTAPISetDoNotDisturb - Device>'[SEP381C1ABBFC73:1012:1]'
28/09/2020 14:33:39.312 "T:10" "D" [-9]:CTD: 1:CTAPISetDoNotDisturb - DndInd=0
28/09/2020 14:33:39.313 "T:10" "D" [-9]:CTD: 1:CTAPISetDoNotDisturb - lineDevSpecificFeature(PHONEBUTTONFUNCTION_DONOTDISTURB)=101FFh

28/09/2020 14:33:39.315 "T:37" "D" [-9]:CTD: 1:Line TAPI ( t=1100250, d=0, m=C, i=A, p1=101FF, p2=0, p3=80000299 )
28/09/2020 14:33:39.315 "T:37" "D" [-9]:CTD: 1:LINE_REPLY [SUCCESS]=101FFh
28/09/2020 14:33:39.315 "T:37" "D" [-9]:CTD: 1:CTAPIProcessLineReply.Enter [LockEvenList] > InvokeID=101FFh, Status=0h
28/09/2020 14:33:39.315 "T:37" "D" [-9]:CTD: 1:CTAPIProcessLineReply.In [IsAvailable] > InvokeID=101FFh, Status=0h
28/09/2020 14:33:39.315 "T:37" "D" [-9]:CTD: 1:CTAPIProcessLineReply.Out [IsAvailable] > InvokeID=101FFh, Status=0h
28/09/2020 14:33:39.315 "T:37" "D" [-9]:CTD: 1:CTAPIProcessLineReply - [Node not found] > InvokeID=101FFh, Status=0h
28/09/2020 14:33:39.315 "T:37" "D" [-9]:CTD: 1:CTAPIProcessLineReply.Leave [UnLockEventList] > InvokeID=101FFh, Status=0h

//No response from LINE_DEVSPECIFICFEATURE API from TAPI side

CUCM System Version =
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.