search for: noticeable

Hello, I'm running the 1/14/04 CVS and am having problems with faxes. I've tried faxing through both a Cisco ATA186 and Sipura SPA2000. I have Asterisk, the ATA186 and Sipura all hard coded to G711ulaw. When the fax machine trains, I get a stream of errors in the log file. The log is attached below. If you have any suggestions they would be GREATLY appreciated. Thank you!!! Jan 21

I?d like to report the ZFS related crash/bug described below. How do I go about reporting the crash and what additional information is needed? I?m using my own very simple test app that creates numerous directories and files of randomly generated data. I have run the test app on two machines, both 64 bit. OpenSolaris crashes a few minutes after starting my test app. The crash has occurred on

Hi. Just migrated to zfs on opensolaris. I copied data to the server using rsync and got this message: Oct 10 17:24:04 zetta ^Mpanic[cpu1]/thread=ffffff0007f1bc80: Oct 10 17:24:04 zetta genunix: [ID 683410 kern.notice] BAD TRAP: type=e (#pf Page fault) rp=ffffff0007f1b640 addr=fffffffecd873000 Oct 10 17:24:04 zetta unix: [ID 100000 kern.notice] Oct 10 17:24:04 zetta unix: [ID 839527 kern.notice]

Hardware Supermicro X7DAE (AHCI BIOS) dual Intel Woodcrest processors, 6 x Western Digital Raptor SATA drives. I have installed b62 running 64 bit succesfully on a PATA drive. The BIOS is configured to access the SATA drives in native mode using hte AHCI Bios. I have 6 SATA II drives accessed via the Solaris AHCI driver. I have created a ZFS file system across all 6 drives. This works fine until

Hi all. One of our server had a panic and now can''t mount the zpool anymore! Here is what I get at boot: Mar 21 11:09:17 SERVER142 ^Mpanic[cpu1]/thread=ffffffff90878200: Mar 21 11:09:17 SERVER142 genunix: [ID 603766 kern.notice] assertion failed: ss->ss_start <= start (0x670000b800 <= 0x67 00009000), file: ../../common/fs/zfs/space_map.c, line: 126 Mar 21 11:09:17 SERVER142

This just started happening to me. It''s a striped non mirrored pool (I know I know). A zfs scrub causes a panic under a minute. I can also trigger a panic by doing tars etc. x86 64-bit kernel ... any ideas? Just to help rule out some things, I changed the motherboard, memory and cpu and it still happens ... I also think it happens on a 32-bit kernel. genunix: [ID 335743 kern.notice] BAD

Hello, I am running asterisk 1.4. For argument's sake I have 4 telephones. 2 support video, 2 do not. Calls between phones work fine and codecs are properly negociated. I have videosupport=yes in sip.conf and when the two video phones communicate I have video. I call meet me with this command EXEC MEETME 1234|d SIP looks like this : -- AGI Script Executing Application: (MeetMe)

Hi list someone is trying to hack my server . Is there any way by whcih I can stop hacking of my server except iptables ? I want to stop on the basis of sip.conf account only. bcoz I can't apply iptables rules on server it's remote server of server provider and we used it for making voip call for customers. for the time been i have close all sip accounts. but can't stop for more then

Out of the blue i started receiving the following error on my PRI line which connects my asterisk server to a Norstar 0x32 key system. The asterisk zaptel.conf file was configure as follows and this config worked for 6 months until friday. Nothing was changed on either system prior to friday. here is teh zaptel.conf span=1,0,0,esf,b8zs bchan=1-23 dchan=24 span=2,0,0,esf,b8zs bchan=25-47 dchan=48

Ok, this is not a OpenSolaris question, but it is a Solaris and ZFS question. I have a pool with three mirrored vdevs. I just got an error message from FMD that read failed from one on the disks,(c1t6d0). All with instructions on how to handle the problem and replace the devices, so far everything is good. But the zpool still thinks everything is fine. Shouldn''t zpool also show

Hi. I tried to send this to the mailing list, but it never showed up in the archives, so I''m trying the forum instead... I recently installed the Crossbow Beta October 31 2008 on my SunFire T1000, and let me first say that I''m very pleased with the functionality it provides. What''s not so pleasing is the fact that after installing this, the computer now get very

Hi everyone, I have a PRI conection on an * system running Asterisk 1.0.9, libpri 1.0.9 and zaptel 1.0.9.2 connected to an AXE 10 (APZ 21220 System 64) in the network side. I know the system and the wildcard I´m using are ok because I´ve used them before with other PRI connections (to a Siemens EWSD) without any problem. First the PRI didn´t work (I got the TE110P alarmed with red). After

Hello list, I have nat=no and qualify=no in my sip peer definition and still my CLI is flooded with : [Mar 12 10:17:26] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (30ms / 2000ms) [Mar 12 10:17:26] NOTICE[20278]: chan_sip.c:12985 handle_response_peerpoke: Peer 'mysippeer' is now Reachable. (24ms / 2000ms) [Mar 12 10:17:26]

I receive this error on the asterisk console and it is pretty much ALWAYS coming up. Sometimes there will be a break where it does not display. We had our PRI provider test the lines and they claim that there is no signalling problem. It doesn't matter if there are no calls or if there are 10 calls in progress the error is still displayed. I also get an annoying popping or clicking sound

<copied from opensolaris-dicuss as this probably belongs here.> I kept on trying to migrate my pool with children (see previous threads) and had the (bad) idea to try the -d option on the receive part. The system reboots immediately. Here is the log in /var/adm/messages Feb 8 16:07:09 amber unix: [ID 836849 kern.notice] Feb 8 16:07:09 amber ^Mpanic[cpu1]/thread=ffffff014ba86e40: Feb 8

Say, I just picked this up on my messages! There are a whole host of these requests! Anyone know whow there people are? Is there a way to report them? Any suggestions as to how to block them? [Aug 23 10:34:16] NOTICE[1010] chan_sip.c: Registration from '"912" <sip:1 at 41.1.1.1>' failed for '184.106.217.112' - Wrong password [Aug 23 10:34:16] NOTICE[1010]

I am getting quite a lot of these notices: Feb 1 10:22:01 NOTICE[2487] cdr.c: CDR on channel 'mISDN/3-2' not posted Feb 1 10:22:01 NOTICE[2487] cdr.c: CDR on channel 'mISDN/3-2' lacks end Feb 1 10:22:06 NOTICE[2471] cdr.c: CDR on channel 'mISDN/3-1' not posted Feb 1 10:22:06 NOTICE[2471] cdr.c: CDR on channel 'mISDN/3-1' lacks end Feb 1 10:22:17 NOTICE[1591]

Howdy, We are using ZFS on one of our Solaris 10 servers, and the box paniced this evening with the following stack trace: Nov 24 04:03:35 foo unix: [ID 100000 kern.notice] Nov 24 04:03:35 foo genunix: [ID 802836 kern.notice] fffffe80004a14d0 fffffffffb9b49f3 () Nov 24 04:03:35 foo genunix: [ID 655072 kern.notice] fffffe80004a1550 zfs:space_map_remove+239 () Nov 24 04:03:35 foo genunix: [ID

Apr 23 02:02:21 SERVER144 offline or reservation conflict Apr 23 02:02:21 SERVER144 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk at g60001fe100118db00009119074440055 (sd82): Apr 23 02:02:21 SERVER144 i/o to invalid geometry Apr 23 02:02:21 SERVER144 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk at g60001fe100118db00009119074440055 (sd82): Apr 23 02:02:21 SERVER144

Hello List. Last month i started to face a strange issue on an asterisk server 1.8.9.3 built on Centos 5.3 x86_64 dedicated server. out of the blue UDP stops responding .. and keep getting the following output: ---------------------------------- Opening message for the problem -------------------------------------------------- [Mar 21 09:57:04] ERROR[6748] netsock2.c: