ā02-20-2014 04:39 AM - edited ā03-16-2019 09:49 PM
Hello.
We are configuring billing on a third-party server for a hospitality projects.
All is fine so far. However we saw that calls with zero duration (such as missed calls, busy tones etc) are tagged with a wrong timestamp of 1/1/70.
Since we are passing this over to the hotel PMS, they are having trouble interpret it and often their interface crashes.
Has someone encountered any similar issue?
Our System version: 9.1.1.20000-5
Solved! Go to Solution.
ā02-20-2014 05:23 AM
I only see the 1970 date in fields like Call Connection time. And for a missed/busy call, that's the best you can do as the call didn't connect, so the call can't have a connection time. Either the field has the 1970 date, or it has NULL in it. Either way, if your third party software can't cope with it, it's broken as this is all as per Cisco's spec.
The use of the 1970 date is (OK, a time of zero) is clearly documented
GTG
Please rate all helpful posts.
ā02-21-2014 02:16 AM
The other option, of course, is to disable zero duration records in CallManager:
System -> Service Parameters -> (Server) -> CallManager -> CDR Log Calls with Zero Duration Flag
GTG
Please rate all helpful posts.
ā02-20-2014 05:23 AM
I only see the 1970 date in fields like Call Connection time. And for a missed/busy call, that's the best you can do as the call didn't connect, so the call can't have a connection time. Either the field has the 1970 date, or it has NULL in it. Either way, if your third party software can't cope with it, it's broken as this is all as per Cisco's spec.
The use of the 1970 date is (OK, a time of zero) is clearly documented
GTG
Please rate all helpful posts.
ā02-21-2014 02:09 AM
Developers are working to have the system remove the zero call durations when sending to PMS.
Weird why CUCM should do something like that for zero duration calls
ā02-21-2014 02:12 AM
As I said, the 1970 date only appears in the call connect field, and a missed call never connects!
GTG
Please rate all helpful posts.
ā02-21-2014 02:16 AM
The other option, of course, is to disable zero duration records in CallManager:
System -> Service Parameters -> (Server) -> CallManager -> CDR Log Calls with Zero Duration Flag
GTG
Please rate all helpful posts.
ā02-23-2014 09:08 PM
Hello Gordon.
We tried to disable the zero duration records in callmanager to no avail.
So the developers rewrote the code to remove the records containing 1970 and now we are no more sending these to PMS.
By the way, is this feature new as from CUCM 9.1? we has been installing this 3rd party server since CUCM 6.1.5 and this is the first time we encounter this issue.
Thanks for your kind help.
ā02-23-2014 11:44 PM
It's there in CUCM 3.x!
From http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/cdr_def/3_x/CDR.html#wp33440
The dateTimeConnect field is defined as:
"Identifies the date and time that the call connected. UTC specifies the time. If the call is never answered, this value shows zero."
GTG
Please rate all helpful posts.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide