× Questions about A400/800/1200 Analog Interface Card

A400E keeps hanging up and redialing

3 years 3 months ago #10826 by harrisp32@hotmail.com
My system: Centos 6.5, Asterisk 13.7.0, Freepbx 12.0.76.2, Dahdi ver 2.10.0.1 echo canceler: oslec. The telephone line is a uk based BT analog line.

Hello

I have a A400E card installed on my system: lspci
Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface
Subsystem: OpenVox Communication Co. Ltd. Device 0001
Flags: bus master, medium devsel, latency 32, IRQ 19
I/O ports at d000
Memory at e9100000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
Kernel driver in use: wctdm
Kernel modules: wctdm, hisax, netjet

Here's the problem, when I make a call to the A400E from my mobile, the Asterisk CLI shows the call coming in, but the sip phone only rings once then hangs and then rings again and on it goes until I hang up on the mobile. The following cli shows where it hangs just after a WARNING, which I suspect is the problem but don't know how to fix it.

Executing [s@macro-dial-one:44] Dial("DAHDI/1-1", "SIP/210,,Ttr") in new stack
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
-- Called SIP/210
-- SIP/210-00000008 is ringing
[2016-02-05 11:00:03] WARNING[3953][C-00000007]: chan_dahdi.c:7285 handle_alarms: Detected alarm on channel 1: Red Alarm
== Spawn extension (macro-dial-one, s, 44) exited non-zero on 'DAHDI/1-1' in macro 'dial-one'
== Spawn extension (macro-exten-vm, s, 9) exited non-zero on 'DAHDI/1-1' in macro 'exten-vm'
== Spawn extension (ext-local, 210, 2) exited non-zero on 'DAHDI/1-1'
-- Executing [h@ext-local:1] Macro("DAHDI/1-1", "hangupcall,") in new stack
-- Executing [s@macro-hangupcall:1] GotoIf("DAHDI/1-1", "1?theend") in new stack
-- Goto (macro-hangupcall,s,3)
-- Executing [s@macro-hangupcall:3] Hangup("DAHDI/1-1", "") in new stack
== Spawn extension (macro-hangupcall, s, 3) exited non-zero on 'DAHDI/1-1' in macro 'hangupcall'
== Spawn extension (ext-local, h, 1) exited non-zero on 'DAHDI/1-1'
-- Hanging up on 'DAHDI/1-1'
-- Hungup 'DAHDI/1-1'
[2016-02-05 11:00:05] NOTICE[2114]: sig_analog.c:2661 analog_publish_channel_alarm_clear: Alarm cleared on channel 1
[2016-02-05 11:00:06] WARNING[2114]: chan_dahdi.c:7285 handle_alarms: Detected alarm on channel 1: Red Alarm
== Starting post polarity CID detection on channel 1
-- Starting simple switch on 'DAHDI/1-1'
[2016-02-05 11:00:09] WARNING[3970][C-00000008]: chan_dahdi.c:7285 handle_alarms: Detected alarm on channel 1: Red Alarm
[2016-02-05 11:00:09] WARNING[3970][C-00000008]: sig_analog.c:2524 _analogss_thread: Hangup received waiting for ring. Exiting simple switch
-- Hanging up on 'DAHDI/1-1'
-- Hungup 'DAHDI/1-1'

The config is as follows:

System Settings: vi /etc/dahdi/system.conf
fxsks=1
echocanceller=oslec,1
loadzone=uk
defaultzone=uk

Global Settings: vi /etc/asterisk/chan_dahdi.conf
[general]
; generated by module
#include chan_dahdi_general.conf
; for user additions not provided by module
#include chan_dahdi_general_custom.conf
[channels]
language=en
busydetect=yes
busycount=10
usecallerid=yes
callwaiting=no
usecallingpres=no
threewaycalling=no
transfer=no
cancallforward=yes
callreturn=no
echocancel=yes
echocancelwhenbridged=no
echotraining=no
immediate=no
faxdetect=no
rxgain=0.0
txgain=0.0
cidsignalling=v23
cidstart=polarity
; for user additions not provided by module
#include chan_dahdi_channels_custom.conf
; include dahdi groups defined by DAHDI module of FreePBX
#include chan_dahdi_groups.conf

From above: #include chan_dahdi_groups.conf
signalling=fxs_ks
context=from-analog
group=0
channel=>1

And: vi /etc/asterisk/dahdi-channels.conf
; Span 1: WCTDM/4 "Wildcard TDM400P REV E/F Board 5" (MASTER)
;;; line="1 WCTDM/4/0 FXSKS (In use) (EC: OSLEC - INACTIVE)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 1
callerid=
group=
context=default

Modprobe Settings: /etc/modprobe.d/dahdi.conf
options wctdm opermode=UK
install wctdm /sbin/modprobe --ignore-install wctdm && /usr/sbin/dahdi_cfg
3 years 3 months ago #10833 by hua
Hello,

Where did the dahdi driver comes from, please make sure there is no connection issue between the card and the PSTN lines. Please add my Skype ASAP.

skype: upper.hua

Best regards
upper
3 years 3 months ago #10836 by harrisp32@hotmail.com
Thank you for your reply. I have sorted it now, it was a lead problem.

Many thanks

Paul
Time to create page: 0.032 seconds
Powered by Kunena Forum