Restored from backup lost all dahdi support...

Status
Not open for further replies.

agidi1

Joined
Jan 13, 2008
Messages
152
Reaction score
0
Hi guys

We just restored on new hardware a small pbx, same versions, same openvox FXO card

But it seems the new one, does not load anything dahdi related.

I can't zap restart
or can't ./dahdi_genconf

The board is recognized with its ports.
We are running 1.6.2-37

if i do help on cli, it does not show any of the zap or dahdi commands

Could it be not loading? or missing?

any commands to make it reload?

all ideas appreciated
thanks
 
I'm sure the experts will chime in on this soon, but while i'm here, i'll throw in some of my hunches. =0)

- Possible they didn't get backed up if the config files were manually edited.
- Possible the configuration wont load do to different hardware
- Possible the configuration wont work do to addressing conflict from differing hardware configurations

Hope you get it worked out.

Andrey
 
OK i found the problem, Im still lost at the solution


[root@pbx ~]# /etc/init.d/dahdi start
Loading DAHDI hardware modules:
wct4xxp: [ OK ]
wcte12xp: [ OK ]
wct1xxp: [ OK ]
wcte11xp: [ OK ]
wctdm24xxp: [ OK ]
wcfxo: [ OK ]
wctdm: [ OK ]
wcb4xxp: [ OK ]
wctc4xxp: [ OK ]
xpp_usb: [ OK ]
opvxa1200: [ OK ]
ystdm8xx: [ OK ]
ystdm16xx: [ OK ]
ap400: [ OK ]
dahdi_dynamic_eth: [ OK ]
dahdi_dynamic_ethmf: [ OK ]
ax1600p: [ OK ]
rxt1: [ OK ]
r1t1: [ OK ]
rcbfx: [ OK ]

Running dahdi_cfg: DAHDI_CHANCONFIG failed on channel 2: Invalid argument (22)
Did you forget that FXS interfaces are configured with FXO signalling
and that FXO interfaces use FXS signalling?
[FAILED]


This box has one openvox 4 port FXO card with ONE FXO module on channel one.
dahdi-channels.conf
; Autogenerated by ./dahdi_genconf on Sat Jul 2 13:32:20 2011
; If you edit this file and execute ./dahdi_genconf again,
; your manual changes will be LOST.
; Dahdi Channels Configurations (chan_dahdi.conf)
;
; This is not intended to be a complete chan_dahdi.conf. Rather, it is intended
; to be #include-d by /etc/chan_dahdi.conf that will include the global settings
;

; Span 1: WCTDM/4 "Wildcard TDM400P REV E/F Board 5" (MASTER)
;;; line="1 WCTDM/4/0 FXSKS"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 1
callerid=
group=1
context=default
 
OK got it working, I'm documenting it for the forums

Do a [root@pbx ~]# dahdi_genconf
then amportal restart

did the trick
thanks!
 
Awesome, good deal. Nice job. =0)

Andrey
 
I have a problem same, please help me

DAHDI_CHANCONFIG failed on channel 1: Invalid argument (22)
Selected signaling not supported
Possible causes:
FXO signaling is being used on a FXO interface (use a FXS signaling variant)
RBS signaling is being used on a E1 CCS span
Signaling is being assigned to channel 16 of an E1 CAS span
[root@Elastix ~]# dahdi_genconf
Empty configuration -- no spans
Empty configuration -- no spans
 
Status
Not open for further replies.

Forum statistics

Threads
111,860
Messages
589,437
Members
164,700
Latest member
Apollo Cloud