similar to: X100P Fxo card headaches

I've spent a week playing with Asterisk 1.6 and I love it. What a brilliant piece of software! Progress and learning have been reasonably good. I have external SIP provider calls coming in and have put together a little call platform and I'm stunned at the flexibility. There is one issue for me. I took me a while to click that ZAPTEL now equals Dahdi, but now I'm there I have an

As best i could figure it out, I've installed dahdi and rc4. My TDM400P doesn't answer fxo or fxs. /etc/dahdi/system.conf: loadzone = us defaultzone=us fxoks=1,2 fxsks=4 /etc/asterisk/chan_dahdi.conf: [house-phones] context=internal ; Uses the [internal] context in extensions.conf signalling=fxo_ks ; fxo_ks Use FXO signalling for an FXS chanel dahdichan => 1 ;

Hi, I have a X101P card and am running Asterisk SVN-trunk-r226890. The X101P card seems to be identified properly: debian:/usr/src/dahdi-tools# dahdi_hardware pci:0000:01:01.0 wcfxo+ e159:0001 Wildcard X101P debian:/usr/src/dahdi-tools# dahdi_cfg -vv DAHDI Tools Version - SVN-trunk-r7409 DAHDI Version: SVN-trunk-r7445 Echo Canceller(s): MG2 Configuration ======================

Hello, After installing on Ubuntu 10.04 using the tutorial on http://hmontoliu.blogspot.com/2010/03/installing-asterisk-and-freepbx-on.html I have a running instance of Asterisk. PROBLEM: result of dahdi_cfg: DAHDI Tools Version - 2.2.1 DAHDI Version: 2.2.1 Echo Canceller(s): MG2 Configuration ====================== Channel map: Channel 01: FXS Kewlstart (Default) (Echo Canceler: mg2)

Hi I have been having a rough time getting a Sangoma A200/Remora FXO/ FXS Analog AFT card set up properly. The main issue is that the card has four ports and as far as I can tell Asterisk is only seeing two. On the two that it recognizes the "Green" FXS ports are not green, they just are not lit. The "RED" FXO ports are indeed red, but from what I have read your not

Calling out on PSTN over a TDM400P seems to generate a Red Alarm - whatever that is. I have another extension on the PSTN, and I can dial out over that. zttool shows no alarms. asterisk*CLI> zap show status Description Alarms IRQ bpviol CRC4 Fra Codi Options LBO Wildcard TDM400P REV I Board 1 OK 0 0 0 CAS Unk YEL 0 db

Hi Guys, An 8 channel Astribank is connected to Trixbox 2.8 and I ran freepbx-module-zapauto but I get the following when running these commands and can't make calls out: [Trixbox]# dahdi_genconf xpporder /usr/sbin/dahdi_genconf: warning - OLD DRIVER: missing '/sys/bus/xpds/devices/00:0:0/timing_priority'. Fall back to /proc pbx*CLI> dahdi show channels Chan Extension Context

Hello list, hope someone can help me - I'm going crazy using the FXO port a SPA3012. I would like the SPA 3012 to act as a simple FXO port to an Asterisk, that is, once it detects a call, it should simply send it over to the local Asterisk server. No intelligent routing, PIN, anything else.... I configured it like this: PSTN-To-VoIP Gateway Setup PSTN-To-VoIP Gateway Enable: yes PSTN

I am unable to dial out over a Wildcard TDM400P. This was working previously, so must have messed up the config somehow. I'm running Asterisk 1.6.0.15, with FreePBX 2.5.2.2. When I dial, I see: -- Executing [s at macro-dialout-trunk:19] Dial("DAHDI/1-1", "DAHDI/g0/9239220,300,") in new stack == Everyone is busy/congested at this time (1:0/1/0) It looks like the

Ok, that's done. Now after this the should compile and run : in En.rc MAIN_MENU is defined now like this : MAIN_MENU MENU { POPUP "&File" { MENUITEM "&New...", 0x100 En.rc is included by #include "En.rc" in rsrc.rc. And gcc complies about it when compiling : [syl@snoop notepad]$ make gcc -c -I. -I. -I../../include -I../../include -g -O2 -Wall

Still trying to upgrade to 1.6.0.9 for 1.4. It worked - it worked all day yesterday, but this morning: -- Executing [646xxxyyyy at longdistance:1] Answer("SIP/172-08276a60", "") in new stack .......... -- Executing [646xxxyyy at longdistance:6] Dial("SIP/172-08276a60", ""DAHDI/g2"/1646xxxyyyy") in new stack May 27 09:56:57]

I am having a problem with a new PRI turn-up on dahdi 2.5.0 and asterisk 1.8.5 that I have not seen before. The PRI is setup as B8ZS, ESF and the span shows up and ok. This PRI is merely a crossover T1 going into an old DC0 class 5 switch. I am getting the following errors over and over again [Aug 16 10:26:10] NOTICE[8002]: chan_dahdi.c:3043 my_handle_dchan_exception: PRI got event: HDLC Bad FCS

Hi, On a (bogus) system equiped with a Digium HA8 and 8 BRI ports, I'm reading this: # asterisk -rx "dahdi show status" Description Alarms IRQ bpviol CRC4 Fra Codi Options LBO HA8-0000 RED 109 0 0 CCS AMI YEL 0 db (CSU)/0-133 feet (DSX-1) HA8-0000 UNCONFI 109 0

Hi all, Not sure if I''m the only one with this problem... We''re on edge for both rails and rspec, and i just did an update... Some apparently innocuous rails stuff was updated, and then half my specs broke due to an error in rspec_on_rails: ArgumentError in ''UserController without logged in user should show the index page'' wrong number of arguments (2

Hi all, I''m trying to run a Story Runner integration test that uploads a file through Attachment-fu. I''ve tried various ways of specifying the file data, from custom mocks: class MockFile < Struct.new (:original_filename, :read, :content_type); end fdata = MockFile.new "test_upload.txt", "Test Upload", "text/plain" to

Fyi, I made the following renames: * RailsExample -> RailsExampleGroup * FunctionalExample -> FunctionalExampleGroup * ControllerExample -> ControllerExampleGroup * ViewExample -> ViewExampleGroup * HelperExample -> HelperExampleGroup * ModelExample -> ModelExampleGroup This was done to keep the naming consistent with ExampleGroup.

Another day, another apparant unexplained hardware incompatibility. I have a TE412P and a TDM400B living quite happily in a whitebox using an Intel motherboard: http://www.intel.com/design/servers/boards/se7230nh1-e/index.htm I tried to move to an IBM x3650 system. It uses a slightly newer chipset, but apparantly it's in the same family. The SE-7230 board has been EOL'd and the

On Thu, Jul 9, 2009 at 5:40 AM, Daniel Tenner<daniel.rspec at tenner.org> wrote: > Hi all, > Like everyone (?), I use nested contexts to keep my specs well organised and > tidy. > However, I have a problem. I have various sets of specs that needs to > perform very time-expensive operations to set up the fixtures that will be > examined in the tests. Two specific examples:

I am posting here since you guys are my last hope. I am trying to configure a Polycom Soundpoint IP 335 with MWI. Is there any way to eliminate the scrolling messages and Msgs softkey? I am trying to get it where it's just the light that indicates the new messages. I don't know if Asterisk has to send a different notification or what have you. Thanks, --Eric -------------- next

So, tweaking configs, rebuilding this and that... restarting, twiddling, it works (yeah!), but fails on re-boot to work at all. Consistently, though. I believe it comes down to this: I can call out only *after* I've received a call. So, cold boot. Then: modprobe dahdi modprobe wctc4xxp modprobe wcfxo dahdi: Telephony Interface Registered on major 196 dahdi: Version: 2.1.0.3