dslepnev Posted April 8, 2009 Report Posted April 8, 2009 Hello, I have configured CDR's output to CSV file. But I found that not all records are stored in the file. For example: Below call from extension to PSTN. It's ok. 20090321101329, 213, 989267901766, 0 Here is incoming call from trunk gateway to pbxnsip. Here is no sourse number and called number. 20090321110155, , , 1 Ok, I have modified CDR_FORMAT value in pbx.xml to "$w$20e$20c$5d$10c$10i$20F$20T$o$v$x$y" It helps but, not clear: 20090408203235, , , 3, ,ea19da5462,345@test;user=phone>, <sip:111@test>,,attendant As you can see when I try to take sourse and destination number from SIP headers they have also additional data with phone number. Advice please, how I need to configure cdr_format to see in the CDR call from extension and call from PSTN (Trunk) onto extension? Quote
pbx support Posted April 8, 2009 Report Posted April 8, 2009 Hello, I have configured CDR's output to CSV file. But I found that not all records are stored in the file. For example: Below call from extension to PSTN. It's ok. 20090321101329, 213, 989267901766, 0 Here is incoming call from trunk gateway to pbxnsip. Here is no sourse number and called number. 20090321110155, , , 1 Ok, I have modified CDR_FORMAT value in pbx.xml to "$w$20e$20c$5d$10c$10i$20F$20T$o$v$x$y" It helps but, not clear: 20090408203235, , , 3, ,ea19da5462,345@test;user=phone>, <sip:111@test>,,attendant As you can see when I try to take sourse and destination number from SIP headers they have also additional data with phone number. Advice please, how I need to configure cdr_format to see in the CDR call from extension and call from PSTN (Trunk) onto extension? Can you first verify whether you have the correct data under <pbx install dir>/cdr? This folder contains CDRs in the XML format. You should be able to locate the corresponding file and verify. If that file shows the correct data, then we may have some issue in the CSV format. Quote
dslepnev Posted April 9, 2009 Author Report Posted April 9, 2009 Can you first verify whether you have the correct data under <pbx install dir>/cdr? This folder contains CDRs in the XML format. You should be able to locate the corresponding file and verify. If that file shows the correct data, then we may have some issue in the CSV format. I have checked XML files in the cdr folder. Here is all information collected correctly. Everything is ok, but not with CSV. Quote
pbx support Posted April 9, 2009 Report Posted April 9, 2009 I have checked XML files in the cdr folder. Here is all information collected correctly. Everything is ok, but not with CSV. Hmm, let me take a look at it by placing the same exact pattern here. BTW, you can take one of $c out ($20c and $10c) from the pattern Quote
pbx support Posted April 9, 2009 Report Posted April 9, 2009 Hmm, let me take a look at it by placing the same exact pattern here. BTW, you can take one of $c out ($20c and $10c) from the pattern Seem to work ok here. Can you tell me the OS and call scenario, say, whether it is coming thought the AA or Hunt/Agent group etc? Quote
dslepnev Posted April 10, 2009 Author Report Posted April 10, 2009 Seem to work ok here. Can you tell me the OS and call scenario, say, whether it is coming thought the AA or Hunt/Agent group etc? OS: Windows XP, pbxnsip version 3.2.0.3144 (Win32). Call scenario: PSTN --E1-->AC Mediant 1000 --SIP-->pbxnsip AA (111) --> Hunt group (444). from Mediant it's looks like a call to specified phone number of AA (111). Quote
pbx support Posted April 10, 2009 Report Posted April 10, 2009 OS: Windows XP, pbxnsip version 3.2.0.3144 (Win32).Call scenario: PSTN --E1-->AC Mediant 1000 --SIP-->pbxnsip AA (111) --> Hunt group (444). from Mediant it's looks like a call to specified phone number of AA (111). Is it possible for you to verify whether a normal call works fine, i.e., PSTN--E1--AC--SIP--pbxsnip AA--extension? Quote
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.