similar to: TDM400P and Adtran 616 problems

Displaying 20 results from an estimated 110 matches similar to: "TDM400P and Adtran 616 problems"

2004 Jul 28
0
X101P problem with latest FreeBSD zaptel drivers
Any other FreeBSD users experiencing this particular problem? I have an X101P board plugged into a PC running 5.2.1 and using the latest (0.6) zaptel port right from the port tree. zttool shows a RED alarm on the card but the phone line appears to be okay (plugging an analog phone into the "Phone" port produces a dialtone on the phone). I've even tried switching the line polarity and
2006 Jun 27
1
Meetme + Sangoma issue?
New server, running 1.2.9.1 with a Sangoma 4 port T1 card, wanpipe rev 2.8.4. I get this message after using a MeetMe room a few times: Jun 27 18:37:23 WARNING[1054] chan_zap.c: Unable to open '/dev/zap/pseudo': No such file or directory Jun 27 18:37:23 ERROR[1054] chan_zap.c: Unable to dup channel: No such file or directory Jun 27 18:37:23 WARNING[1054] app_meetme.c: Unable to open
2004 May 19
1
FreeBSD + Zaptel + Asterisk
I've been lurking on the list for quite a while now, and I hadn't seen much from people using FreeBSD, so I figured I'd post something. Yes, the driver in the ports tree for the digium card works! I'd heard reports that it crashes the box/etc, but I have yet to encounter that. I've had all the fun I can stand making it answer the phone, dial numbers/etc. The makefile for the
2010 May 19
1
Multiple language output - Correct in RGui, wrong in .txt after sink()
I have the following problem with outputting multilingual data to a file. I get (except for Korean) what I expect as result in the RGui, but when I use sink() to output to a text file loose the characters in the foreign languages. I post a small example below. Since I am not sure how well my email system as the list copes with all the different characters I have additionally created a pdf
2013 Oct 28
0
[virtio-net] BUG: sleeping function called from invalid context at kernel/mutex.c:616
On 10/24/2013 07:20 AM, Fengguang Wu wrote: > Yes it reduces the sleeping function bug: > > /kernel/x86_64-lkp-CONFIG_SCSI_DEBUG/7c4ed2767afb813493b0a8fb18d666cd44550963 > > +------------------------------------------------------------------------------------+-----------+--------------+--------------+ > |
2013 Jun 21
0
[Bug 616] Duplicate rules for multi-homed hostnames. IPv4 and IPv6 inconsistent treatment.
https://bugzilla.netfilter.org/show_bug.cgi?id=616 Phil Oester <netfilter at linuxace.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |netfilter at linuxace.com --- Comment #3 from Phil Oester <netfilter at linuxace.com> 2013-06-21
2013 Jul 08
0
[Bug 616] Duplicate rules for multi-homed hostnames. IPv4 and IPv6 inconsistent treatment.
https://bugzilla.netfilter.org/show_bug.cgi?id=616 --- Comment #4 from Phil Oester <netfilter at linuxace.com> 2013-07-08 23:33:07 CEST --- As noted, #2 is solved already. Also, /128 will no longer print (commit 945353a2). But your #1 makes little sense to me: discovery.razor.cloudmark.com/22. How do you know that EVERY IP returned from a DNS lookup is always going to be a /22 mask?
2013 Jul 09
0
[Bug 616] Duplicate rules for multi-homed hostnames. IPv4 and IPv6 inconsistent treatment.
https://bugzilla.netfilter.org/show_bug.cgi?id=616 --- Comment #5 from - <kd6lvw at yahoo.com> 2013-07-09 03:45:06 CEST --- Re: Comment #4. One doesn't know what the addresses are until they are retrieved from the DNS. The point is that the routines which generate the rules are NOT checking the values AFTER the CIDR netmask is applied to eliminate POST-MASK duplicate answers. The
2013 Jul 09
0
[Bug 616] Duplicate rules for multi-homed hostnames. IPv4 and IPv6 inconsistent treatment.
https://bugzilla.netfilter.org/show_bug.cgi?id=616 --- Comment #6 from Phil Oester <netfilter at linuxace.com> 2013-07-09 03:50:27 CEST --- Yes, I fully understand what is happening in the one specific example you have provided. However you need to answer what happens if Cloudmark suddenly decides to add an IP _OUTSIDE_ of that /22 that is assigned to them. Let's say they open a new
2013 Jul 09
0
[Bug 616] Duplicate rules for multi-homed hostnames. IPv4 and IPv6 inconsistent treatment.
https://bugzilla.netfilter.org/show_bug.cgi?id=616 --- Comment #7 from - <kd6lvw at yahoo.com> 2013-07-09 09:35:30 CEST --- Re: Comment #6 - It is up to the author of the ruleset to determine policy. It is the duty of the software to properly execute that policy. Here, the software fails to do so because it produces duplicate redundant rules which are never used. Note that iptables-save
2013 Jul 09
0
[Bug 616] Duplicate rules for multi-homed hostnames. IPv4 and IPv6 inconsistent treatment.
https://bugzilla.netfilter.org/show_bug.cgi?id=616 --- Comment #8 from Phil Oester <netfilter at linuxace.com> 2013-07-09 15:56:45 CEST --- (In reply to comment #7) > It is the duty of the software to properly execute that policy. Here, the > software fails to do so because it produces duplicate redundant rules which are > never used. And where is it documented that the software
2013 Jul 09
0
[Bug 616] Duplicate rules for multi-homed hostnames. IPv4 and IPv6 inconsistent treatment.
https://bugzilla.netfilter.org/show_bug.cgi?id=616 --- Comment #9 from - <kd6lvw at yahoo.com> 2013-07-09 19:56:29 CEST --- RE: Comment #7: "It seems your best solution is to add a single rule with 208.83.136.0/22." Yet, it adds THREE rules, two of which will never fire, thus the problem and bug report. Extend your quota example: When the first rule reaches the quota, it will
2013 Jul 09
0
[Bug 616] Duplicate rules for multi-homed hostnames. IPv4 and IPv6 inconsistent treatment.
https://bugzilla.netfilter.org/show_bug.cgi?id=616 Phil Oester <netfilter at linuxace.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX --- Comment #10 from Phil Oester
2013 Jul 09
0
[Bug 616] Duplicate rules for multi-homed hostnames. IPv4 and IPv6 inconsistent treatment.
https://bugzilla.netfilter.org/show_bug.cgi?id=616 --- Comment #11 from - <kd6lvw at yahoo.com> 2013-07-09 21:48:05 CEST --- I fully disagree that the addition of duplicate rules that will never be reached is part of the design. As a waste of memory allocation, it is inefficient and therefore incorrect. The use of a hostname in place of an IP address literal should not have any effect in
2003 Jul 12
0
[Bug 616] proxycommand breaks hostbased authentication.
http://bugzilla.mindrot.org/show_bug.cgi?id=616 Summary: proxycommand breaks hostbased authentication. Product: Portable OpenSSH Version: 3.6.1p2 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-bugs at mindrot.org ReportedBy: stuart
2005 Sep 08
1
FW: Adtran TA 616
Has anybody had any luck getting an Adtran Total Access 616 working via the Ethernet port/MGCP to an * box? The voice lines don't seem to be coming up and I wasn't sure if I had something missing. Here's my mgcp.conf file: [general] port = 2427 bindaddr = 0.0.0.0 [10.189.189.31] context=nicktest host=10.189.189.31 canreinvite=no line => aaln/1 line => aaln/2
2006 Apr 19
2
[PATCH][XM-TEST] Fix for 15_create_smallmem_pos.py test - Bug 616
Hi, Here''s the first step toward dealing with the small memory issue. The 15_create_smallmem_pos.py test was hanging because it created a 16 MB domain and never got to the point where it could set a console limit. The OOM messages flooded the console on creation and the select in Console.py always had something to read. Since there was no limit and it never timed out, the test would
2009 Oct 20
1
[Bug 616] New: Duplicate rules for multi-homed hostnames. IPv4 and IPv6 inconsistent treatment.
http://bugzilla.netfilter.org/show_bug.cgi?id=616 Summary: Duplicate rules for multi-homed hostnames. IPv4 and IPv6 inconsistent treatment. Product: iptables Version: unspecified Platform: i386 OS/Version: All Status: NEW Severity: minor Priority: P4 Component: iptables
2013 Oct 22
0
[virtio-net] BUG: sleeping function called from invalid context at kernel/mutex.c:616
On 10/20/2013 10:34 AM, Fengguang Wu wrote: > Greetings, > > I got the below dmesg and the first bad commit is > > commit 3ab098df35f8b98b6553edc2e40234af512ba877 > Author: Jason Wang <jasowang at redhat.com> > Date: Tue Oct 15 11:18:58 2013 +0800 > > virtio-net: don't respond to cpu hotplug notifier if we're not ready > > We're
2005 Jun 29
2
X100P connected as extension to Panasonic 616 EASA-PHONE
Hi all. I`ve installed a X100P on my box and is working well with incoming and outgoing calls as a trunk with one PTSN line. I want to connect the X100P to my Panasonic 616 EASA-PHONE as an internal extension to permit to users to make calls to SIP devices from analog phones, the problem is when I dial the ext number where the X100P is connected I get busy tone. What config I need to change to