Preview Tool

Cisco Bug: CSCvj11231 - Visual VoiceMail on 88xx series phones shows incorrect day expression in Visual VoiceMail applet

Last Modified

Dec 03, 2018

Products (13)

  • Cisco IP Phone 8800 Series
  • Cisco IP Phone 8865
  • Cisco IP Phone 8851
  • Cisco IP Phone 7841
  • Cisco IP Conference Phone 7832
  • Cisco IP Phone 7821
  • Cisco IP Phone 8811
  • Cisco IP Phone 8845
  • Cisco IP Phone 8861
  • Cisco IP Phone 7861
View all products in Bug Search Tool Login Required

Known Affected Releases

11.7(1) 12.0(1)

Description (partial)

Under certain conditions Visual Voicemail may show incorrect day expression on IP Phones, for instance "Yesterday" instead of "Today".

TUI and WEB is not impacted.

Timezone set at CUC: IST (GMT+5.30)
Timezone set at CUCM: IST (GMT+5.30)

Suppose if the timezone for CUC and CUCM is set to  GMT+5.30(IST)  and dropping a message after 18:30 ,we observed message time in Visual Voice mail  shows  18:31(tomorrow) instead of  18:31(today).

we send two set of time from CUC with each message i.e arrivalTime and localArrivalTime, in which arrivalTime contains the GMT (i.e 13:01)and localArrivalTime contains local time  (i.e 18.31).

Below is the phone logs:

3607 INF Apr 05 18:31:00.017707 (696:23680) JAVA-MessageListUpdaterThread_28|MethodInvoker: - GetMessages Request :

3608 INF Apr 05 18:31:00.017798 (696:23680) JAVA-MessageListUpdaterThread_28|MethodInvoker: - GetMessages Response: <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv=""><soapenv:Body><ns1:GetMessagesResponse xmlns:ns1="urn:Messaging"><ns1:MessageEnvelopes><ns1:MsgEnvelope><ns1:MsgId>51de75a8-3009-4c90-ba17-3fdbfcf73977</ns1:MsgId><ns1:Subject>test message 2</ns1:Subject><ns1:From>white, walter</ns1:From><ns1:To>"white, walter" <></ns1:To><ns1:Read>true</ns1:Read><ns1:CallerId>1004</ns1:CallerId><ns1:CallerName>white, walter</ns1:CallerName><ns1:ArrivalTime>1522760506</ns1:ArrivalTime><ns1:LocalArrivalTime>1522780306</ns1:LocalArrivalTime><ns1:Priority>Normal</ns1:Priority><ns1:Sensitivity>Normal</ns1:Sensitivity><ns1:Size>236886</ns1:Size><ns1:Duration>21580</ns1:Duration><ns1:IMAPUid>34</ns1:IMAPUid><ns1:FromSub>true</ns1:FromSub><ns1:FromVmIntSub>false</ns1:FromVmIntSub><ns1:Type>0</ns1:Type></ns1:MsgEnvelope><ns1:MsgEnvelope><ns1:MsgId>5d2aaaed-b1fb-4f8e-9f

3609 INF Apr 05 18:31:00.017838 (696:23680) JAVA-fc-8371ba921072</ns1:MsgId><ns1:Subject>test</ns1:Subject><ns1:From>white, walter</ns1:From><ns1:To>"white, walter" <></ns1:To><ns1:Read>true</ns1:Read><ns1:CallerId>1004</ns1:CallerId><ns1:CallerName>white, walter</ns1:CallerName><ns1:ArrivalTime>1522758665</ns1:ArrivalTime><ns1:LocalArrivalTime>1522778465</ns1:LocalArrivalTime><ns1:Priority>Normal</ns1:Priority><ns1:Sensitivity>Normal</ns1:Sensitivity><ns1:Size>236876</ns1:Size><ns1:Duration>21580</ns1:Duration><ns1:IMAPUid>33</ns1:IMAPUid><ns1:FromSub>true</ns1:FromSub><ns1:FromVmIntSub>false</ns1:FromVmIntSub><ns1:Type>0</ns1:Type></ns1:MsgEnvelope></ns1:MessageEnvelopes></ns1:GetMessagesResponse></soapenv:Body></soapenv:Envelope>

3645 DEB Apr 05 18:31:00.019047 (696:23680) JAVA-MessageListUpdaterThread_28|MessagingHandler: - strLocalArrivalTime= 1522780306

3646 DEB Apr 05 18:31:00.020004 (696:23680) JAVA-MessageListUpdaterThread_28|MessagingHandler: - arrivalDate is : Wed Apr 04 00:01:46 GMT+05:30 2018

·        From the above logs we can see that the phone picked Local Arrival Time and converted into  TimeZone what we set at CUCM

 1522780306 (in unix epoch time) converted to Wed Apr 04 00:01:46 GMT+05:30 2018
(For converting Unix epoch time to date

·        That is why it is showing wrong date on Visual Voicemail as the date crossed the current day while converting Unix epoch time.

·        It should have picked the arrivalTime from Unity Connection response XML which is in GMT to get the correct local date

 1522760506 will be converted as Tuesday, April 3, 2018 6:31:46 PM GMT+05:30<>;
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.