similar to: Please help me!!

Hi to all, I've a segmentation fault while using asterisk relatime conf with mysql db. I've cretate sip_buddies and extensions tables into db and edit res_mysql.conf, extconf.conf without any issues. So when I start asterisk and my phone try to register using sip user configured in my db, asterisk stops with Segmentation fault error. Follow post gdb backtrace 0 0x400337c0 in

I to all, I've a segmentation fault while using asterisk relatime conf with mysql db. I've cretate sip_buddies and extensions tables into db and edit res_mysql.conf, extconf.conf without any issues. So when I start asterisk and my phone try to register using sip user configured in my db, asterisk stops with Segmentation fault error. Follow post gdb backtrace 0 0x400337c0 in

asterisk-users-bounces@lists.digium.com wrote: > Vadim Berezniker wrote: > >> That's not a solution, but just a workaround. >> 1.2.1 has a bug where it always uses an empty context when searching >> for a mailbox when using realtime config. >> At around line 546 of apps/app_voicemail.c there is a line that says >> var =

Hello list, I have been running Asterisk CVS for a good while. When I try to install 1.0.3, asterisk won't start. Below are the last few lines of output before Asterisk crashes. I ran "make samples" to start with a fresh setup. [app_read.so] => (Read Variable Application) == Registered application 'Read' [app_alarmreceiver.so] => (Alarm Receiver for Asterisk) ==

Can anyone help me with this: - root@foxy:~ > asterisk root@foxy:~ > asterisk -r Asterisk CVS-v1-0-12/28/04-11:37:32, Copyright (C) 1999-2004 Digium. Written by Mark Spencer <markster@digium.com> ========================================================================= Connected to Asterisk CVS-v1-0-12/28/04-11:37:32 currently running on foxy (pid = 1751) foxy*CLI> foxy*CLI>

Sorry to ask such a basic question: I have a * box with 2 nics in the following setup: Internet | 192.168.5.253 (firewall) | 192.168.5.xxx network (gw 192.168.5.253) | 192.168.5.10 (* nic 1) 192.168.6.10 (* nic 2) | 192.168.6.xxx network The netmask for both networks is 255.255.255.0 The 192.168.6.xxx networks has a 48 port switch solely for the use of cicso 7940 phones, the 192.168.5.xxx is

Paste your extensions.conf section that is relevant. -Matthew ----- Original Message ----- From: "Greg - Cirelle Enterprises" <gcirino@cirelle.com> To: <asterisk-dev@lists.digium.com> Sent: Monday, December 27, 2004 4:32 PM Subject: [Asterisk-Dev] realtime voicemail > Let me clarify my last message. > > If I put in the wrong password I get polled > again for

Hi, I've just had to enable the requirecalltoken=no option in iax.conf for one of my IAX2 trunks, and I don't think it works properly in the realtime version. I've created the requirecalltoken field in my (Postgres via ODBC) database, type text, and have variously tried it with 'yes', 'no' and 'auto' in the field. But the setting never seems to be used and

On a multicore Linux platform I'm running a simple c test program, to evaluate xapian performance, and inspect advantages in multiple indexing. I'm starting two threads, and each thread writes to his database. main th -> indexing thread_1 -> db1 (dispatcher) -> indexing thread_2 -> db2 I use sched_setaffinity to bind each indexing thread to a specific core.

I have been testing with asterisk 1.4.11 and have found a segmentation fault while using voicemail. It happens when I try to forward a voicemail. As soon as I press the option the server crashes. I ran asterisk up inside gdb and got the following stack trace ==================================================================== Program received signal SIGSEGV, Segmentation fault. 0x00140adf in

http://bugzilla.mindrot.org/show_bug.cgi?id=967 Summary: Command only sessions hangs on target system. Product: Portable OpenSSH Version: 3.8.1p1 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-bugs at mindrot.org ReportedBy:

This is the next patch series for scrub userland tools. Change log v1->v2: - commands now reachable as "btrfs scrub ..." instead of "btrfs filesystem scrub ..." - ability to scrub a single device instead of a whole file system - superfluous command line options removed - resume is now a separate command ("scrub resume") instead of "scrub start -r" -