Hello,

I assume that you use xen for virtualization.
In Case of xen 3.0.4 you have to do the following in dom0

assume that the pci_id of the hfc-pci card is: 00:07.0:

# Cologne Chip Designs GmbH ISDN network controller [HFC-PCI] (rev 02) [TE]
echo -n 0000:00:07.0 > /sys/bus/pci/drivers/pciback/new_slot
echo -n 0000:00:07.0 > /sys/bus/pci/drivers/pciback/bind
echo -n 0000:00:07.0 >/sys/bus/pci/drivers/pciback/permissive

the "permissive" should do the trick. it allows the domU much more on the 
pcibus...

 

kind regards

F.Heese
P.S.: in Xen 3.0.3 (I think ...) it was:
echo Y > /sys/bus/pci/drivers/pciback/permissive

Am Mittwoch, 4. Juli 2007 07:58:17 schrieb Steven Noels:
> Hi all,
>
> I'm trying to get misdn/Asterisk/Freepbx running inside a virtualized
> Debian etch machine, and everything looks pretty fine so far, however
> Asterisk reports all channels being busy when trying to dial out.
> Could someone help me how to debug this problem?
>
> asterisk:~# uname -r
> 2.6.18-4-xen-686
>
> asterisk:~# lspci -v
> 00:00.0 Network controller: Cologne Chip Designs GmbH ISDN network
> controller [HFC-PCI] (rev 02)
>          Subsystem: Cologne Chip Designs GmbH ISDN Board
>          Flags: bus master, medium devsel, latency 16, IRQ 18
>          I/O ports at ac00 [disabled] [size=8]
>          Memory at ff6ffc00 (32-bit, non-prefetchable) [size=256]
>          Capabilities: [40] Power Management version 1
>
> asterisk:~# misdn-init scan
> [OK] found the following devices:
> card=1,hfcpci
> [ii] run "/usr/sbin/misdn-init config" to store this information to /
> etc/misdn-init.conf
>
> asterisk:~# misdn-init config
> [OK] /etc/misdn-init.conf created. It's now safe to run "/usr/sbin/
> misdn-init start"
> [ii] make your port (1) available in asterisk by editing "/etc/
> asterisk/misdn.conf"
>
> asterisk:~# misdn-init start
> -----------------------------------------
> Loading module(s) for your misdn-cards:
> -----------------------------------------
> /sbin/modprobe --ignore-install hfcpci protocol=0x2 layermask=0xf
> /sbin/modprobe mISDN_dsp debug=0x0 options=0 poll=128 dtmfthreshold=100
> [i] creating device node: /dev/mISDN
>
> asterisk:~# ls -al /dev/mISDN
> crw-r--r-- 1 asterisk asterisk 46, 0 Jul  3 20:07 /dev/mISDN
>
> asterisk:~# cat /etc/misdn-init.conf
> card=1,hfcpci
> te_ptmp=1
> poll=128
> dsp_poll=128
> dsp_options=0
> dtmfthreshold=100
> debug=0
>
> asterisk:~# cat /etc/asterisk/misdn.conf
> [general]
> misdn_init=/etc/misdn-init.conf
> debug=0
> ntdebugflags=0
> ntdebugfile=/var/log/misdn-nt.log
> bridging=no
> stop_tone_after_first_digit=yes
> append_digits2exten=yes
> dynamic_crypt=no
> crypt_prefix=**
> crypt_keys=test,muh
>
> [default]
> context=misdn
> language=en
> musicclass=default
> senddtmf=yes
> far_alerting=no
> allowed_bearers=all
> nationalprefix=0
> internationalprefix=00
> rxgain=0
> txgain=0
> te_choose_channel=no
> pmp_l1_check=yes
> reject_cause=16
> need_more_infos=no
> method=standard
> dialplan=0
> localdialplan=0
> cpndialplan=0
> early_bconnect=yes
> incoming_early_audio=no
> nodialtone=no
> presentation=-1
> screen=-1
> jitterbuffer=4000
> jitterbuffer_upper_threshold=0
> hdlc=no
>
> [extern]
> ports=1
> context=from-pstn
> msns=*
>
>
> I'm a bit unsure about the last stance here but documentation is
> pretty sparse.
>
> I have a suspiciously looking error in my syslog as well:
>
> Jul  4 05:45:15 asterisk kernel: MDL_ERROR|REQ (tei_l2)
>
> when restarting Asterisk. I've also explicitly unloaded the hisax
> module, re-init-ed msidn, restarted Asterisk: same error.
>
> Many thanks!
>
> </Steven>


_______________________________________________
Misdn-asterisk mailing list
[email protected]
http://lists.beronet.com/cgi-bin/mailman/listinfo/misdn-asterisk

Reply via email to