« Back to Call Detail Records Questions

origcause_value and destcause_value swapped

Combination View Flat View Tree View
Threads [ Previous | Next ]
origcause_value and destcause_value swapped
Answer
2/11/11 1:01 PM
Hi,
 
we analysed CDRs of calls to busy targets on 2 different CUCM clusters. We expect to have a destcause_value of 17 (=User busy) in this case.
 
On one cluster (our lab) this works as expected but on the customers CUCM the descause_value is 0 but the origcause_value is 17!!
 
How can it be that the originating party ends a call in status User busy?
 
Thanks,
Roland
Flag

RE: origcause_value and destcause_value swapped
Answer
2/14/11 11:03 PM as a reply to Roland Russwurm.
"How can it be that the originating party ends a call in status User busy?"-

If I understood the scenario correctly it is not, and is indicating that the record didn't end because of busy status, but rather that this record was generated because of it. I'm not sure if you can fit the results in a post here, but I'm betting you find all such records show as originating from 'non-phone' devices.
Flag