Has anybody found a way to convert the "dateTimeDisconnect" field into a readable date? I have that field as the number of seconds since midnight Jan 1, 1970. I am using Access 2002 with an ODBC connection to the calldetailrecord table in sql on CCM.
You can use this formula in Excel to change a date of that format into a more readable date:
C3 is the cell containing the raw dateTimeOrigination, dateTimeConnect, or dateTimeDisconnect field values.
Alternatively, you can use a SQL statement to convert the date/time value to a more readable format. A query like this would work against the CallManager database:
CAST(CAST(dateTimeOrigination AS FLOAT) / CAST(86400 AS FLOAT) +
DATEDIFF(day, 'Jan 1,1900', 'Jan 1,1970') AS datetime) AS dateTimeOrigination_dt,
CAST(CAST(dateTimeConnect AS FLOAT) / CAST(86400 AS FLOAT) +
DATEDIFF(day, 'Jan 1,1900', 'Jan 1,1970') AS datetime) AS dateTimeConnect_dt,
CAST(CAST(dateTimeDisconnect AS FLOAT) / CAST(86400 AS FLOAT) +
DATEDIFF(day, 'Jan 1,1900', 'Jan 1,1970') AS datetime) AS dateTimeDisconnect_dt,
order by datetimeorigination
Note that the dates/times in CallManager are stored in UTC timezone, so to change them to your timezone you would need to modify the query to reflect that (apply a modifier to the date/time fields in the calculation based on your timezone).
It is giving me this error: Syntax error (missing operator) in query expression 'dbo_CallDetailRecord.dateTimeOrigination CAST(CAT(dateTimeOrigination AS FLOAT / CAST(86400 AS FLOAT + DATEDIFF(day, 'Jan 1,1990', Jan 1,1970') AS datetime)'.
Here's the functions I wrote for Access to convert UTC time to/from normal time. I also included the function to convert the IPs into dotted notation. They works pretty well for me. I know the timezone offset function is brute force but it works.
Public Function Normal_Time(UTC As Long) As Date
UTC = UTC + TimeZoneOffset(UTC) * 3600 ' Time Zone Correction
Yes, MS Access thinks a bit differently than SQL Server!
Try this query in MS Access, I'm no Access guru, but it should work!
CVDate(Format( ((dbo.dateTimeOrigination/86400) + DateDiff("d", #Jan 1,1900#,#Jan 1,1970#)) ,"dd mm yyyy hh:mm:ss")) AS dateTimeOrigination_dt
OR (dbo.CallDetailRecord.callingPartyNumber Like '*6480206'));
Check the date/time values returned to ensure that they are accurate (and that my conversion to Access is correct), though remember that this query does not take timezone into consideration so the values will be reported in UTC 'timezone'.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...