[email protected] wrote: > Send sipx-dev mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://list.sipfoundry.org/mailman/listinfo/sipx-dev > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of sipx-dev digest..." > > ------------------------------------------------------------------------ > > [please change the subject line when replying] > ------------------------------------------------------------------------ > > Today's Topics: > > 1. Re: Importing a file (Tony Graziano) > 2. Re: Enable TLS for polycom (Douglas Hubler) > 3. erlang spec file (Matt White) > 4. Re: erlang spec file (Douglas Hubler) > 5. Re: erlang spec file (Matt White) > > > ------------------------------------------------------------------------ > > Subject: > Re: [sipx-dev] Importing a file > From: > Tony Graziano <[email protected]> > Date: > Thu, 20 Jan 2011 06:30:27 -0500 > To: > sipXecs developer discussions <[email protected]> > > To: > sipXecs developer discussions <[email protected]> > > > Re: [sipx-dev] Importing a file > From: > Tony Graziano <[email protected] > <mailto:[email protected]>> > Date: > Mon, 29 Nov 2010 01:40:16 -0500 > To: > [email protected] <mailto:[email protected]> > > To: > [email protected] <mailto:[email protected]> > > > The file extension is not important. Your import file > contained data that > could be imported in the correct format. I don't think a jira > is in order > (but maybe a typing class is, ;>) ). > > If you would like an example of the priper format, perform an > export. > > > Hi Graziano, > What you said was correct.Then why config UI > allow to import .ods file ...please check the screenshot.. > Regards > Venkateshwaran T > > You fail to interpret the intent of the design. > > The file name and extension are UNIMPORTANT. A CSV file can be saved > as "any" extension type. In your case, there are extra characters in > the files that are the cause of the strange characters in the import job. > > To better understand this, do an export of a clean system with a few > users/lines, then open it in a text editor. In my use cases, I use > excel or google docs (spreadsheet), and export the file as a csv file. > It's clear the ODS file you have is using encode characters, and is > not actually a valid CSV file, but because the data is inside the > delimiters, it is parsing it exactly as it is told to do so. > > Example: I do an export, then login to google docs and import it. I > make the changes I need (if any), then save and choose "File>download > as>csv" > > I think your ODS file is a spreadsheet, but it not formatted for CSV. > I know there was an ODS to CSV in github with OO (or whatever they > call it these days, LibreOffice i think). I know LibreOffice has a CSV > export function: > > http://help.libreoffice.org/Calc/Importing_and_Exporting_CSV_Files > > In the end, this is the same thing we've discussed before. The issue > is not with the file type, rather it is with the encoding. Your app is > not encoding the file properly. Use a properly encoded file (the > extension STILL DOES NOT MATTER). > > > > ------------------------------------------------------------------------ > > Subject: > Re: [sipx-dev] Enable TLS for polycom > From: > Douglas Hubler <[email protected]> > Date: > Thu, 20 Jan 2011 07:57:28 -0500 > To: > sipXecs developer discussions <[email protected]> > > To: > sipXecs developer discussions <[email protected]> > > Hi Douglas, So need not to re-open it.. Regards Venkateshwaran T > you're right, patch was missed. I just applied it, it will be in the > tomorrow's build. > > On Thu, Jan 20, 2011 at 4:32 AM, Kumaran > <[email protected]> wrote: > >> Hi All, >> This is regarding the issue : XX-9209. It seems to be not resolved, because >> if I check the drop down menu of Outbound Proxy Transport under Registration >> --TLS option is not present.Please guide us in this regard and Please check >> the screen shot attached >> Regards >> Venkateshwaran T >> >> _______________________________________________ >> sipx-dev mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-dev/ >> >> > > > > ------------------------------------------------------------------------ > > Subject: > [sipx-dev] erlang spec file > From: > "Matt White" <[email protected]> > Date: > Thu, 20 Jan 2011 08:17:23 -0500 > To: > <[email protected]> > > To: > <[email protected]> > > > The spec file from the current 4.4 sources has a typo in the erlang > spec file. It's missing the "v" for version. > > |%if| |0||%{?sles_ersion}| |!=| |0 > > should be: > > | > |%if| |0||%{?sles_version}| |!=| |0 > > which obviously breaks SLES builds ;-) > > -M > | > > > > ------------------------------------------------------------------------ > > Subject: > Re: [sipx-dev] erlang spec file > From: > Douglas Hubler <[email protected]> > Date: > Thu, 20 Jan 2011 08:51:37 -0500 > To: > sipXecs developer discussions <[email protected]> > > To: > sipXecs developer discussions <[email protected]> > > > ok, i'll get it in and upload srpm right away > > On Thu, Jan 20, 2011 at 8:17 AM, Matt White <[email protected]> wrote: > >> The spec file from the current 4.4 sources has a typo in the erlang spec >> file. It's missing the "v" for version. >> >> %if 0%{?sles_ersion} != 0 >> >> should be: >> >> %if 0%{?sles_version} != 0 >> >> which obviously breaks SLES builds ;-) >> >> -M >> >> >> >> _______________________________________________ >> sipx-dev mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-dev/ >> >> > > > > ------------------------------------------------------------------------ > > Subject: > Re: [sipx-dev] erlang spec file > From: > "Matt White" <[email protected]> > Date: > Thu, 20 Jan 2011 11:01:22 -0500 > To: > <[email protected]>,<[email protected]> > > To: > <[email protected]>,<[email protected]> > > > >>> Douglas Hubler <[email protected]> 01/20/11 8:52 AM >>> > >>ok, i'll get it in and upload srpm right away > >> > > Thanks, so far the srpms compile on SLES 11 x64 almost without issue. > The only package I'm still working on is sipxtools. The only other > building issues have been with other project rpms like freeswitch. > All the sipx packages have been building fine. > > So it looks like getting other builds from the current srpms will be > fairly clean and easy. > ------------------------------------------------------------------------ > > _______________________________________________ > sipx-dev mailing list > [email protected] > http://list.sipfoundry.org/mailman/listinfo/sipx-dev >
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
