FonarevM Posted September 3, 2010 Report Share Posted September 3, 2010 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? Quote Link to comment Share on other sites More sharing options...
pbx support Posted September 6, 2010 Report Share Posted September 6, 2010 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? If you are using v4, the cdr_format is used only for the "Simple TCP" based CDRs. Everything else has fixed CDR fields. Quote Link to comment Share on other sites More sharing options...
FonarevM Posted September 8, 2010 Author Report Share Posted September 8, 2010 Ok. Thanks. Quote Link to comment Share on other sites More sharing options...
FonarevM Posted September 8, 2010 Author Report Share Posted September 8, 2010 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? Quote Link to comment Share on other sites More sharing options...
pbx support Posted September 8, 2010 Report Share Posted September 8, 2010 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? we will check it out. What version are you using? Quote Link to comment Share on other sites More sharing options...
FonarevM Posted September 8, 2010 Author Report Share Posted September 8, 2010 we will check it out. What version are you using? We use 4.1.0.4026 (Win32) Quote Link to comment Share on other sites More sharing options...
pbx support Posted September 8, 2010 Report Share Posted September 8, 2010 We use 4.1.0.4026 (Win32) 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? Quote Link to comment Share on other sites More sharing options...
FonarevM Posted September 15, 2010 Author Report Share Posted September 15, 2010 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. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted September 15, 2010 Report Share Posted September 15, 2010 We try this version on two different installation, on both we still receive something like 1283934474 instead of 0. 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. Quote Link to comment Share on other sites More sharing options...
FonarevM Posted September 16, 2010 Author Report Share Posted September 16, 2010 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 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.