asterisk users - Apr 2009 - [UK SPECIFIC] DAHDI and a OpenVox Card

Hi,

Built a new server at the weekend and install Asterisk 1.6.0.9 and IAX and SIP
work great :) The one problem I am having is getting the OpenVox (TDM400 type
card) to work.  It is successfully identified using WCTDM kernel module and
dahdi_scan picks it up just fine.  The issue is when I try and setup
dahdi_channel.conf as it fails everytime.  When running asterisk -rvvvv I see
the port pick up the ring but the it shows a RED Alarm failure.  Does anybody
have a working configuration they would be happy to share with me please ?

Best Regards,

-- 
SplatNIX IT Services :: Innovation through collaboration

On Mon, Apr 27, 2009 at 07:37:05AM +0100, --[ UxBoD ]--
wrote:
> Hi,
> 
> Built a new server at the weekend and install Asterisk 1.6.0.9 and 
> IAX and SIP work great :) The one problem I am having is getting the 
> OpenVox (TDM400 type card) to work.  It is successfully identified 
> using WCTDM kernel module and dahdi_scan picks it up just fine.  
> The issue is when I try and setup dahdi_channel.conf as it fails 
> everytime.  
What is dahdi_channel.conf ?

What is the output of:

  lsdahdi
  asterisk -rx 'dahdi show channels'
> When running asterisk -rvvvv I see the port pick up the ring but the 
> it shows a RED Alarm failure.  
RED alarm: nothing connected to the port (applies to FXO as well as to
digital ports - E1, T1, J1, BRI).

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir

----- "Tzafrir Cohen" <tzafrir.cohen at xorcom.com> wrote:
> On Mon, Apr 27, 2009 at 07:37:05AM +0100, --[ UxBoD ]-- wrote: 
> > Hi, 
> > 
> > Built a new server at the weekend and install Asterisk 1.6.0.9 and 
> > IAX and SIP work great :) The one problem I am having is getting the 
> > OpenVox (TDM400 type card) to work. It is successfully identified 
> > using WCTDM kernel module and dahdi_scan picks it up just fine. 
> > The issue is when I try and setup dahdi_channel.conf as it fails 
> > everytime. 
> 
> What is dahdi_channel.conf ? 
> 
> What is the output of: 
> 
> lsdahdi 
> asterisk -rx 'dahdi show channels' 
> 
> > When running asterisk -rvvvv I see the port pick up the ring but the 
> > it shows a RED Alarm failure. 
> 
> RED alarm: nothing connected to the port (applies to FXO as well as to 
> digital ports - E1, T1, J1, BRI). 
> 
> 
Sorry for the delay! Okay here is the information requested :-

dahdi_chan.conf
---------------
[channels]
group=0
language=en
context=inbound-dahdi
signalling=fxs_ks
dahdichan => 1

lsdahdi
-------
[root at voip asterisk]# lsdahdi 
### Span  1: WCTDM/4 "Wildcard TDM400P REV E/F Board 5" (MASTER) 
  1 FXO        FXSKS       (In use) (SWEC: MG2)  RED
  2 EMPTY                   
  3 EMPTY                   
  4 EMPTY    

[root at voip asterisk]# asterisk -rx 'dahdi show channels'
   Chan Extension  Context         Language   MOH Interpret        Blocked   
State
 pseudo            default                    default                         In
Service
      1            inbound-dahdi   en         default                         In
Service


Cable is plugged in fine, but when it tries to pick up the call I get :-

[May  1 07:15:03] NOTICE[10601]: chan_dahdi.c:8164 handle_init_event: Alarm
cleared on channel 1
[May  1 07:15:04] WARNING[10601]: chan_dahdi.c:4664 handle_alarms: Detected
alarm on channel 1: Red Alarm

Would be really nice to get this working and complete my VoIP installation :(

Best Regards,

-- 
SplatNIX IT Services :: Innovation through collaboration

----- "--[ UxBoD ]--" <uxbod at splatnix.net> wrote: 
----- "Gordon Henderson" <gordon+asterisk at drogon.net> wrote:
> On Fri, 1 May 2009, Tzafrir Cohen wrote: 
> 
> > Is this a place where you get a polarity reversal event on call
startup?
> 
> In the UK we do. (Well on BT lines - I've a funny feeling some 
> Telewest/NTL lines use Bell signaling). 
> 
> On an incoming call we get: 
> 
> Polarity reversal. 
> FSK Caller ID burst 
> Ringing 
> 
> I've not upgraded any analogue systems to dahdi yet, but from what
I've
> read so-far, there's not much difference between the config files
(other
> than their names and locations), but a typical /etc/zaptel.conf file looks 
> like: 
> 
> fxoks=1 
> fxsks=4 
> loadzone=uk 
> defaultzone=uk 
> 
> This has one FXO and one FXS port. 
> 
> The corresponding zapata.conf is: 
> 
> [trunkgroups] 
> [channels] 
> usecallerid=yes 
> cidsignalling=v23 
> cidstart=polarity 
> hidecallerid=no 
> callwaiting=no 
> threewaycalling=yes 
> transfer=yes 
> echocancel=yes 
> ;echotraining=yes ; off for oslec 
> ;echocancelwhenbridged=yes 
> immediate=no 
> faxdetect=no 
> 
> ; Channel 1: Local analogue line 
> context=internal 
> group=0 
> signalling=fxo_ks 
> sendcalleridafter=2 
> rxgain=0 
> txgain=0 
> mailbox=202 
> callerid=The Red Phone <202> 
> channel => 1 
> 
> ; Channel 4: PSTN line 
> context=incoming-zap-ddi 
> group=1 
> usecallerid=yes 
> faxdetect=none 
> signalling=fxs_ks 
> rxgain=8 
> txgain=8 
> callerid=asreceived 
> channel => 4 
> 
> Hope this is may be some use. 
> 
> Gordon 
> 
> _______________________________________________ 
> 
Could of bugs I have found relating to this issue but it appears to have been
resolved :(

http://bugs.digium.com/view.php?id=12531&nbn=13
http://bugs.digium.com/view.php?id=14163&nbn=3

Best Regards,

-- 
SplatNIX IT Services :: Innovation through collaboration

Hi everyone,

I just found this thread, which is amazing as I'm on my first go with 
asterisk and so far I've been pulling my hair out for the last week :-)

I have 2 questions which were raised while this fault was being debugged.


1)

Gordon says:-

 > Is this a place where you get a polarity reversal event on call startup?

In the UK we do. (Well on BT lines - I've a funny feeling some
Telewest/NTL lines use Bell signaling).

On an incoming call we get:

    Polarity reversal.
    FSK Caller ID burst
    Ringing




Well I've got an NTL phone line, can anyone tell me what to use for that?



2)

Do I still need the same 2pin cable? Because I've been to Maplins too 
and bought one that I thought was right, but this one is a 4pin too.

Can anyone tell me which pins on their 2pin cable are connected at each 
end? I'll bodge my cable until it works and then get a proper one once 
I'm sure.


Thanks in advance.

Dunc