Re: [asterisk-users] Problem configuring TDM400

2009-07-06 Thread Dave Fullerton
jonas kellens wrote:
 On Fri, 2009-07-03 at 11:58 +0100, Mike wrote:
 
 tempest:~# lspci
 00:00.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN
 interface
 
 I don't think this is you TDM-card...
 
 This is mine :
 
 04:05.0 Ethernet controller: Digium, Inc. TDM400P (rev 11)
 Subsystem: Digium, Inc. TDM400P
 Flags: bus master, medium devsel, latency 32, IRQ 90
 I/O ports at d100 [size=256]
 Memory at ff74 (32-bit, non-prefetchable) [size=1K]
 Expansion ROM at 8000 [disabled] [size=128K]
 Capabilities: [c0] Power Management version 2
 
 I don't think your XEN VM can see your TDM-card. You will need to ad a
 module to your XEN-kernel to be able to speak to your TDM pci-card.
 Don't know if this module exists...
 

My TDM400P appears as his does:

00:14.0 Communication controller: Tiger Jet Network Inc. Tiger3XX 
Modem/ISDN interface

-Dave



___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [asterisk-users] Problem configuring TDM400

2009-07-06 Thread Dave Fullerton
Mike wrote:
 Folks,
 
 I have a Xen Asterisk VM with a TDM400 card.  When I try to run
 dahdi_cfg, I get:
 
 tempest:~# dahdi_cfg -vvv
 DAHDI Tools Version - 2.2.0
 
 DAHDI Version: 2.2.0
 Echo Canceller(s): 
 Configuration
 ==
 
 
 Channel map:
 
 Channel 01: FXO Kewlstart (Default) (Echo Canceler: none) (Slaves: 01)
 Channel 03: FXS Kewlstart (Default) (Echo Canceler: none) (Slaves: 03)
 Channel 04: FXS Kewlstart (Default) (Echo Canceler: none) (Slaves: 04)
 
 3 channels to configure.
 
 DAHDI_CHANCONFIG failed on channel 1: No such device or address (6)
 
 The card appears to be detected:
 
 tempest:~# lspci
 00:00.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN
 interface
 
 I have the kernel modules loaded:
 
 tempest:~# lsmod
 Module  Size  Used by
 wctdm  35024  0 
 dahdi 185352  1 wctdm
 crc_ccitt   2848  1 dahdi
 autofs418500  0 
 ipv6  236612  10 
 ext3  106664  1 
 jbd43092  1 ext3
 mbcache 8260  1 ext3
 dm_mirror  16288  0 
 dm_log  9444  1 dm_mirror
 dm_snapshot15108  0 
 dm_mod 47304  3 dm_mirror,dm_log,dm_snapshot
 raid1  19200  0 
 md_mod 69180  1 raid1
 thermal_sys11624  0
 
 [ 1327.030178] dahdi: Telephony Interface Registered on major 196
 [ 1327.030253] dahdi: Version: 2.2.0
 
 I have Googled for this problem and found a lot of people reporting the
 issue but nobody really having much of an answer!  I've seen the issue a
 few times.  The strange thing is that I did have things working but then
 I rebotoed the box and it seems to have given up.
 
 I have a fairly straight forward DAHDI config file which has served me
 perfectly well in the past.
 
 tempest:~# cat /etc/dahdi/system.conf
 # Autogenerated by /usr/sbin/dahdi_genconf on Fri Jul  3 09:56:12 2009
 # If you edit this file and execute /usr/sbin/dahdi_genconf again,
 # your manual changes will be LOST.
 # Dahdi Configuration File
 #
 # This file is parsed by the Dahdi Configurator, dahdi_cfg
 #
 # Global data
 
 loadzone= uk
 defaultzone = uk
 
 fxoks=1
 fxsks=3,4
 
 I have tried only bringing up certain channels but that still fails.
 
 Does anyone have any idea what could be wrong?
 
 Mike.
 

Did do all the device files show up in /dev/dahdi/ ?

You should have something close to this:

r...@jaguar:~# ls -l /dev/dahdi/
total 0
crw-rw 1 asterisk asterisk 196,   1 2009-07-05 09:32 1
crw-rw 1 asterisk asterisk 196,   2 2009-07-05 09:32 2
crw-rw 1 asterisk asterisk 196,   3 2009-07-05 09:32 3
crw-rw 1 asterisk asterisk 196,   4 2009-07-05 09:32 4
crw-rw 1 asterisk asterisk 196, 254 2009-07-05 09:32 channel
crw-rw 1 asterisk asterisk 196,   0 2009-07-05 09:32 ctl
crw-rw 1 asterisk asterisk 196, 255 2009-07-05 09:32 pseudo
crw-rw 1 asterisk asterisk 196, 253 2009-07-05 09:32 timer


-Dave

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


[asterisk-users] Problem configuring TDM400

2009-07-03 Thread Mike
Folks,

I have a Xen Asterisk VM with a TDM400 card.  When I try to run
dahdi_cfg, I get:

tempest:~# dahdi_cfg -vvv
DAHDI Tools Version - 2.2.0

DAHDI Version: 2.2.0
Echo Canceller(s): 
Configuration
==


Channel map:

Channel 01: FXO Kewlstart (Default) (Echo Canceler: none) (Slaves: 01)
Channel 03: FXS Kewlstart (Default) (Echo Canceler: none) (Slaves: 03)
Channel 04: FXS Kewlstart (Default) (Echo Canceler: none) (Slaves: 04)

3 channels to configure.

DAHDI_CHANCONFIG failed on channel 1: No such device or address (6)

The card appears to be detected:

tempest:~# lspci
00:00.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN
interface

I have the kernel modules loaded:

tempest:~# lsmod
Module  Size  Used by
wctdm  35024  0 
dahdi 185352  1 wctdm
crc_ccitt   2848  1 dahdi
autofs418500  0 
ipv6  236612  10 
ext3  106664  1 
jbd43092  1 ext3
mbcache 8260  1 ext3
dm_mirror  16288  0 
dm_log  9444  1 dm_mirror
dm_snapshot15108  0 
dm_mod 47304  3 dm_mirror,dm_log,dm_snapshot
raid1  19200  0 
md_mod 69180  1 raid1
thermal_sys11624  0

[ 1327.030178] dahdi: Telephony Interface Registered on major 196
[ 1327.030253] dahdi: Version: 2.2.0

I have Googled for this problem and found a lot of people reporting the
issue but nobody really having much of an answer!  I've seen the issue a
few times.  The strange thing is that I did have things working but then
I rebotoed the box and it seems to have given up.

I have a fairly straight forward DAHDI config file which has served me
perfectly well in the past.

tempest:~# cat /etc/dahdi/system.conf
# Autogenerated by /usr/sbin/dahdi_genconf on Fri Jul  3 09:56:12 2009
# If you edit this file and execute /usr/sbin/dahdi_genconf again,
# your manual changes will be LOST.
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Global data

loadzone= uk
defaultzone = uk

fxoks=1
fxsks=3,4

I have tried only bringing up certain channels but that still fails.

Does anyone have any idea what could be wrong?

Mike.


signature.asc
Description: Digital signature
___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Re: [asterisk-users] Problem configuring TDM400

2009-07-03 Thread jonas kellens
On Fri, 2009-07-03 at 11:58 +0100, Mike wrote:

 tempest:~# lspci
 00:00.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN
 interface

I don't think this is you TDM-card...

This is mine :

04:05.0 Ethernet controller: Digium, Inc. TDM400P (rev 11)
Subsystem: Digium, Inc. TDM400P
Flags: bus master, medium devsel, latency 32, IRQ 90
I/O ports at d100 [size=256]
Memory at ff74 (32-bit, non-prefetchable) [size=1K]
Expansion ROM at 8000 [disabled] [size=128K]
Capabilities: [c0] Power Management version 2

I don't think your XEN VM can see your TDM-card. You will need to ad a
module to your XEN-kernel to be able to speak to your TDM pci-card.
Don't know if this module exists...

Jonas.
___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users