[cdr format problem]

1283934474 = now - beginning of UNIX time...

 

Next version will have it fixed. Until then, just ignore anything that is bigger than the max call duration.

 

Ok, thanks

[cdr format problem]

We tested it on the one of the recent versions - http://pbxnsip.com/protect/pbxctrl-4.2.0.3920.exe and did not see this issue. Can you try this version on a test machines?

 

We try this version on two different installation, on both we still receive something like 1283934474 instead of 0.

[cdr format problem]

we will check it out. What version are you using?

 

We use 4.1.0.4026 (Win32)

[cdr format problem]

And we have some new problem. If we set cdr_format like $w$20e$20c$15d, then output like

20100908122803 214 89035123123 4

but if call no answer then we get

20100908122744 214 89035123123 1283934470

you see duration of call is 1283934474, but must be 0.

Can we change this?

[cdr format problem]

Ok. Thanks.

[cdr format problem]

We change cdr_format in pbx.xml and restart pbxnsip but in output CDR (CSV,xml or email) we don't see any changes. Change cdr_file_name or cdr_field_seperator worked well. What can we do to change output CDR?