Andrew Sayman wrote:
Here is my setup:
* is on a NAT'd subnet, but also has an externally routable IP address.
I have a Snom360 that's external to this and behind NAT.
The Snom360 can call other phones in * subnet (by their internal
extension numbers) and voice is transmitted fine; however
Here is my setup:
* is on a NAT'd subnet, but also has an externally routable IP address.
I have a Snom360 that's external to this and behind NAT.
The Snom360 can call other phones in * subnet (by their internal extension
numbers) and voice is transmitted fine; however, when I attempt to check
Eric Wieling aka ManxPower wrote:
Andrew Sayman wrote:
Okay, so I believe I've gotten rid of the IRQ conflict, and it's still
not working.
All analog FXO ports are considered answered when the dialing is
finished.
Thanks for this bit of information.
I went back with a Vonage modem (I'm
Elwin Andriol wrote:
Don't know if this will help you any further, but. After some trouble
with IRQ sharing mayhem we solved our little problem by tinkering the
linux kernel. I forgot the names of the actual modules, but after
disabling modules for APIC support and something about IRQ sharing
Okay, so I believe I've gotten rid of the IRQ conflict, and it's still
not working.
What concerns me is that even channels with absolutely nothing connected
to the slots will say answered.
The log output looks like this:
-- Executing Dial(SIP/2000-401a, Zap/2/w9w15554014809) in new stack
I have a TDM04B installed that isn't working 100% with Asterisk. I'm
using the cvs-head of the zaptel drivers and asterisk with FC3 on a 2.6
kernel.
I have successfully created a call on one of the channels, but there are
a few problems. Even on channels with no analog line connected to them,
Noah Miller wrote:
Depending on your BIOS and motherboard, you may be able to use
another IRQ if you move the card to a different PCI slot.
- Noah
This is a computer meant to be rack-mounted that I'm trying to install
this on. I certainly don't see any space for another PCI slot, so I
