CSV Trouble

[Bill H]

Using Windows 3.3.1.3177 (Win32)

 

There is no Carriage Retrun Line Feed (CRLF) at the end of the CSV output string.

 

Is the delimiter missing or am I doing something wrong here???

 

 

Set CDR Type for File:Disk

 

Set CDR String for $w$e$c$d

 

First CSV shows up as 20090616220804,49,8323801,16

 

Second shows up as 20090616220804,49,8323801,1620090616220829,49,8451234,14

 

No CRLF causes new reord to be appended.

 

Using Wordpad to view CSV file.

 

Excell doesn't parse it without the CRLF.

[pbx support]

I think we have a newline(\n) instead of crlf (\r\n). If that is causing the issue, we can introduce a CRLF in the next version.

 

 

Using Windows 3.3.1.3177 (Win32)

 

There is no Carriage Retrun Line Feed (CRLF) at the end of the CSV output string.

 

Is the delimiter missing or am I doing something wrong here???

 

 

Set CDR Type for File:Disk

 

Set CDR String for $w$e$c$d

 

First CSV shows up as 20090616220804,49,8323801,16

 

Second shows up as 20090616220804,49,8323801,1620090616220829,49,8451234,14

 

No CRLF causes new reord to be appended.

 

Using Wordpad to view CSV file.

 

Excell doesn't parse it without the CRLF.

[Bill H]

I think we have a newline(\n) instead of crlf (\r\n). If that is causing the issue, we can introduce a CRLF in the next version.

 

 

The CSV file looks OK in the CS-410 and can be parsed by Excel.

 

The trouble only seems to be in the Windows Versions.

 

In the CSV from CS-410 I see the characters || at the end of the line.

 

These characters are probably the unprintable values for newline and return.

 

I have tried this on 3 different Windows systems and they all have the same trouble.

 

We have told our customer about the CSV Feature and are now counting on the CSV feature to provide daily cdr info.

 

Now we are commited to something that either has a trouble or is setup wrong somehow.

 

Please look into this in a timely manner as I am sure others will discover the trouble too.

[pbx support]

The CSV file looks OK in the CS-410 and can be parsed by Excel.

 

The trouble only seems to be in the Windows Versions.

 

In the CSV from CS-410 I see the characters || at the end of the line.

 

These characters are probably the unprintable values for newline and return.

 

I have tried this on 3 different Windows systems and they all have the same trouble.

 

We have told our customer about the CSV Feature and are now counting on the CSV feature to provide daily cdr info.

 

Now we are commited to something that either has a trouble or is setup wrong somehow.

 

Please look into this in a timely manner as I am sure others will discover the trouble too.

 

That is interesting. V3.x has an issue here. Will fix it and upload the new version. BTW, what are you running on CS410?

[Bill H]

That is interesting. V3.x has an issue here. Will fix it and upload the new version. BTW, what are you running on CS410?

 

The CS-410 is running the new Version: 4.0.0.3204 (Linux)

 

Thanks for your prompt response.

[pbx support]

The CS-410 is running the new Version: 4.0.0.3204 (Linux)

 

Thanks for your prompt response.

 

There is an updated version ready for the download http://pbxnsip.com/protect/pbxctrl-3.4.0.3198.exe. This has the CRLF fix for the CDR.

[Bill H]

There is an updated version ready for the download http://pbxnsip.com/protect/pbxctrl-3.4.0.3198.exe. This has the CRLF fix for the CDR.

 

Thnak you.

 

I will try it later tonight and let you know how it worked out.

[Bill H]

Thanks, it works OK now.

[andrewgroup]

release 3194 seemed to introduce problems with the monitor extension buttons on snom 3xx phones. Rolled back to 3.2.0.3143 to stabilize the ext light troubles. (Will try 3198 later)