search for: codesets

I got the following compile error in R-1.9.0 on NetBSD 1.5: <-- snip --> ... gcc -I../../src/extra/zlib -I../../src/extra/bzip2 -I../../src/extra/pcre -I. -I../../src/include -I../../src/include -I/usr/local/include -DHAVE_CONFIG_H -O2 -mcpu=v8 -c main.c -o main.o main.c: In function `setup_Rmainloop': main.c:463: `CODESET' undeclared (first use in this function)

...ASCII. > > To verify I put together a small testprogram that does a setlocale > followed by nl_langinfo(CODESET) and for the 'C' locale it returns an > empty string while 'da' returns ISO8859-1 as expected. > I worked some more on this and comparing locales and their codesets between Solaris 2.6 and 7 I'm reasonably sure that an empty codeset value means ascii on Solaris 2.6. So to ensure proper operation and get rid of the error in the testsuite I've added "" as a valid alias for ascii in dangerous_locales(). With this change in place the testsuite...

You should run the 4ESS protocol ("a" on the Definity command "change DS1 board#) as the Definity may not send Display Name for the NI-2 protocol (settings "b" or "d") Remember to make the Asterisk zapata settings consistent with the Definity. On the Definity trunk group form Page 1, change "Codeset to send Display" to "0 (zero)", also make

Hi, Michael Felt wrote on Mon, Aug 20, 2018 at 05:00:17PM +0200: > ./nl_langinfo > setlocale -> "C" > nl_langinfo -> "ISO8859-1" Thanks, that is helpful. So i think i was wrong and Damien was right. This means that OpenSSH returns truncated messages when non-ASCII bytes occur in them, even when the user requests LC_CTYPE=POSIX. That's not good. While

Hi, Michael Felt wrote on Mon, Aug 20, 2018 at 11:28:26AM +0200: > On 20/08/2018 10:33, Michael Felt wrote: >> On 17/08/2018 17:15, Ingo Schwarze wrote: >>> Darren Tucker wrote on Fri, Aug 17, 2018 at 07:16:03AM -0700: >>>> On 13 August 2018 at 15:06, Val Baranov <val.baranov at duke.edu> wrote: >>>>> test_utf8: ........................

I just saw the following in the release notes for the new firmware for the later 3ware cards; Improved CIFS performance The firmware has been tuned to greatly increase performance with CIFS (Common Internet File System) protocol. However, this has resulted in performance with the Linux ext3 file system that is slower than earlier releases. We recommend that you use other Linux file systems, such

Below is a snipped debug on our PRI. We are getting number only for the CallerID but the telco says they are sending us Name and Number. We are getting the Name in a second frame but Asterisk is not passing it to the device it rings. The message below says "Presenation allowed of network provided number" which leads me to believe Asterisk thinks it should not be displaying it. Can anyone

I'm not a big fan of Line Side for Asterisk applications.... the individual channels have to be reserved (reminds me of the "old" days in telephony) and I don't like that... rather make it a tie trunk and use ARS/AAR routing in the Definity... much more general application. This also makes routing on the Asterisk a lot simpler. Easy to make the changes.... will advise if

Ok, so I've made progress on 2BCT (2 B-Channel Transfer). I'm assuming that the debug info below shows that XO doesn't have 2BCT enabled on my line, but if anybody can confirm that'll let me be way more indignant. J -- Native bridging DAHDI/1-1 and DAHDI/3-1 > Protocol Discriminator: Q.931 (8) len=28 > Call Ref: len= 2 (reference 801/0x321) (Terminator) >

OpenSSH 7.5 has just been released. It will be available from the mirrors listed at http://www.openssh.com/ shortly. OpenSSH is a 100% complete SSH protocol 2.0 implementation and includes sftp client and server support. OpenSSH also includes transitional support for the legacy SSH 1.3 and 1.5 protocols that may be enabled at compile-time. Once again, we would like to thank the OpenSSH community

In case you're ok with not version-controlling files imported via autogen, ... >From 72c829395bb6a4800516d4f535e18af48195585b Mon Sep 17 00:00:00 2001 From: Jim Meyering <meyering at redhat.com> Date: Mon, 3 Aug 2009 11:00:22 -0400 Subject: [PATCH] Remove files imported via autogen.sh. * m4/.gitignore: Ignore these files. * m4/codeset.m4: Remove file. * m4/gettext.m4: Likewise. *

Hi I have done everything richard told to do ECT . below is my trace, anyone can help ? -- DAHDI/i1/09123278669-4 answered DAHDI/i1/88050048-3 -- Native bridging DAHDI/i1/88050048-3 and DAHDI/i1/09123278669-4 PRI Span: 1 Adding facility ie contents to send in FACILITY message: PRI Span: 1 ASN.1 dump PRI Span: 1 Context Specific/C [1 0x01] <A1> Len:11 <0B> PRI Span: 1

Here's a propsed heavy-duty solution for your UTF-8 problems. I'm including a patch in this message, but I'll put the new files on my web site at http://rano.org/tmp/xiph_files.tar.gz I've tested this by running vorbiscomment with and without -DHAVE_ICONV=1 in vorbis-tools/share/Makefile. It seems to work. Changed files: acinclude.m4: Add a test for nl_langinfo(CODESET). This

Hey users, i've got a question about calling line id in libpri - zaptel with switchtype "q.sig". My Q.Sig partner is a Siemens F900 (HiPoint). If I enable span debug i see messages from type "CONNECT" with some kind of bit field: < Protocol Discriminator: Q.931 (8) len=87 < Call Ref: len= 2 (reference 86/0x56) (Terminator) < Message type: CONNECT (7) < [1c

Hi I've a bug in vorbis-tools's libutf8 - some share/*.[ch] files don't include config.h; as a result, utf8.c:convert_set_charset doesn't try charset = nl_langinfo(CODESET) which would correctly return UTF-8, because HAVE_LANGINFO_CODESET isn't defined (it's defined in config.h, but config.h is not included). So, the bugfix is simple - just include config.h everywhere

Anyone know why zaptel would ignore a facility message from an ISDN PRI. I am trying to get Callerid name to work. The carrier says it on and I see it in the pri debug but asterisk never gets it. Any help would be appreciated. Thanks John Bittner Simlab.net Protocol Discriminator: Q.931 (8) len=9 > Call Ref: len= 2 (reference 572/0x23C) (Terminator) > Message type: ALERTING (1) >

I there, I have some trouble to do working caller id name for outgoing calls on the PRI we just installed. Caller id name work on incoming calls only. Caller id number work on incoming and outgoing calls. The provider, Goup Telecom, said that's in what i'm sending. They said that I send the cid name in ascii code and to do it working, I need to send it in hex. So I take some traces

Hi there, I am using the RODBC library to connect to an Empress database. I have installed the ODBC data source with the server DNs number and port, and named the source "Trawl". It is the odbcDriverConnect that seems to have the problem, and I suspect one of the settings in my Data Source is wrong, or that my syntax to identify the database is wrong. I have not set CodeSet or ODBC

I am hoping someone could shed some light and point me in the right direction? I'm attempting to get callerid work between an Avaya Definity PBX and Asterisk via TE110P connected via T1/PRI Crossover PRI. From the Definity side I've searched endlessly and came with an example which we modeled as close as we can, but still no luck. While doing PRI intense debug span 1 in I see a couple

Hi, Few changes in hivex, sent as series to be clearly identified as hivex ones. After these patches, what about a new release of it? The last one is basically one year old, and the changes after 1.3.11 make hivex build and work fine on FreeBSD (and maybe more non-Linux OSes). Thanks, Pino Toscano (3): Fix shebang in perl scripts Update gnulib to latest. Update .gitignore with more