Topic: Sail-647 and ISDN Support ?

[fpausp]

Hi,

Is Sail-647 supporting ISDN ? I tried to probe my (cheap) HFC-Card:

Code: [Select]


Found following card...
03:06.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 225
I/O ports at 4000 [size=8]
Memory at de200000 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 1

Database requested /lib/modules/2.6.9-67.0.7.ELsmp/extra/zaphfc.ko ...
Load module zaphfc not found - ignoring card (perhaps it uses mISDN?)


No Telephony Boards found on second pass ...

Signalling asterisk daemon to load ZTDUMMY for timing purposes






Regards

fpausp

[SARK devs]

Yes... and no.

SAIL does support ISDN but you have to have a special version of Asterisk.   To cut a long story short, ISDN2 is not common in the USA so Digium have never really put much effort into supporting it.  Instead, two German companies; Junghanns and Beronet, each built their own asterisk modifications to support ISDN2.  Junghanns did it by extensively patching Zaptel and the Asterisk core.  It is called "bristuff".  Beronet did it by building (in conjunction with others) a new channel driver.  It is called mISDN.  SAIL supports both of these (you will need SAIL -646 or later for mISDN - which you already have).

We have a special set of rpms for Bristuff.  For mISDN you can simply install mISDN from ATrpms and then create the necessary .conf files which it requires.   You can see from the output you posted that SAIL has detected your HFC card, it then looked for the Junghanns bristuff HFC driver (zaphfc) and didn't find it so it has ignored the card and suggested that you run mISDN to handle it (mISDN does it's own card detection so SAIL bypasses the card if it thinks that you may be using mISDN).

Code: [Select]

Database requested /lib/modules/2.6.9-67.0.7.ELsmp/extra/zaphfc.ko ...
Load module zaphfc not found - ignoring card (perhaps it uses mISDN?)


When Digium finally got around to producing an ISDN2E card (the B410P) they chose the mISDN drivers rather than the Junghanns equivalents.  Our recommendation for new ISDN2 users is to install mISDN.

I will attempt to get a short mISDN how-to up onto the docs site this weekend.

Also, our next .iso (which will probably run sail-650) will have mISDN included as standard.

Kind Regards

[fpausp]

Hi,

Any news from mISDN-Howto ?

regards
fpausp

[SARK devs]

Here's a really quick howto for you..

install mISDN from ATrpms...

Code: [Select]

yum install misdn --enablerepo=atrpms
yum install misdn-kmdl-`uname -r`
configure your card (misdn does all the hard work for you) by doing...

Code: [Select]

mISDN config
start misdn by doing

Code: [Select]

mISDN start
you also need to configure misdn.conf for asterisk....

Here's one you can use for a single HFC card running in PTP TE mode (just copy and paste it into misdn.conf).

Code: [Select]

[general]
debug=0
ntdebugflags=0
ntdebugfile=/var/log/misdn-nt.log
bridging=no
l1watcher_timeout=0
stop_tone_after_first_digit=yes
dynamic_crypt=no
crypt_prefix=**
crypt_keys=test,muh

[default]
context=mainmenu
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=no
pp_l2_check=no
reject_cause=16
need_more_infos=no
nttimeout=no
method=standard
dialplan=0
localdialplan=0
cpndialplan=0
early_bconnect=yes
incoming_early_audio=no
nodialtone=no
presentation=-1
screen=-1
echocancel=yes
echocancelwhenbridged=no
echotraining=no
jitterbuffer=4000
jitterbuffer_upper_threshold=0
hdlc=no
max_incoming=-1
max_outgoing=-1

;
;  Uncomment the protocols you wish to use (careful with the port numbers).
;

[TEPP]
context=default
ports=1 ptp
msns=*

;[TEPMP]
;context=default
;ports=1
;msns=1234,5678

;[NTPP]
;context=default
;ports=1 ptp
;msns=*

;[NTPMP]
;context=default
;ports=1
;msns=1234,5678

OK you can start asterisk.  There is nothing to do in PCI Cards because mISDN has already done it.  All you need to do is to define one PTT-DiD group for each inbound DiD number you have and you need to create an outbound route which uses TEPP as its trunk (TEPP will appear in the trunk drop down).

You should also read up on mISDN on voip-info and visit the misdn site so that you understand what I've just shown you.

This is still Beta code so YMMV.

Kind Regards 

[fpausp]

Hi All,

Today i tried to install mISDN but i had no luck with atrpms  .

Code: [Select]


[root@server ~]# uname -r
2.6.9-67.0.7.ELsmp


[root@server ~]# yum install misdn --enablerepo=atrpms
==============================================================
WARNING: Additional commands may be required after running yum
==============================================================
Loading "installonlyn" plugin
Loading "fastestmirror" plugin
Loading "smeserver" plugin
Setting up Install Process
Setting up repositories
Loading mirror speeds from cached hostfile
Reading repository metadata in from local files
Excluding Packages from atrpms - EL4
Finished
Parsing package install arguments
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Package misdn.i386 0:1.1.8-3.el4 set to be updated
--> Running transaction check
--> Processing Dependency: misdn-kmdl-1.1.8-3.el4 for package: misdn
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please wait.
---> Package misdn-kmdl-2.6.9-78.EL.i686 0:1.1.8-3.el4 set to be updated
--> Running transaction check
--> Processing Dependency: /boot/vmlinuz-2.6.9-78.EL for package: misdn-kmdl-2.6.9-78.EL
Importing Additional filelist information for dependency resolution
--> Finished Dependency Resolution
Error: Missing Dependency: /boot/vmlinuz-2.6.9-78.EL is needed by package misdn-kmdl-2.6.9-78.EL
================================================================
No new rpms were installed. No additional commands are required.
================================================================



Does anybody have the files, or a link for me (2.6.9-67.0.7.ELsmp) please  ?


Regards
fpausp

[SARK devs]

Those rpms have probably already been withdrawn by ATrpms.

Best

S

[jester]

Hi,
Using the mISDN kernel modules provided by Selintra (see other post HERE) i have trouble getting things to work. I followed the mISDN Driver setup page and everything is set up accordingly.

But the lines are crackly and no call gets picked up by asterisk. I've been trying to read up on voip-info and misdn.org (and googling around) but i'm kinda lost in abbreviations and tech-talk. I've found post about using a isdn-cross cable, but i thought that was for connection your PBX to a phone?! I'm trying to troubleshoot this, here is what i get using "misdnportinfo" and "misdn show port 1" in the Asterisk CLI>

Code: [Select]

# misdnportinfo

Port  1: TE-mode BRI S/T interface line (for phone lines)
 -> Protocol: DSS1 (Euro ISDN)
 -> Layer 4 protocol 0x04000001 is detected, but not allowed for TE lib.
 -> childcnt: 2
 * Port NOT useable for PBX (maybe there is already a PBX running?)
--------

mISDN_close: fid(3) isize(131072) inbuf(0x8fc7060) irp(0x8fc7060) iend(0x8fc7060)


Code: [Select]

CLI> misdn show port 1
BEGIN STACK_LIST:
  * Port 1 Type TE Prot. PMP L2Link DOWN L1Link:DOWN Blocked:0  Debug:0


My current set-up:

• Straight-ISDN-cable from my Dutch Provider (KPN) Wall-plug to a NT1-box.
• From the NT1-box one straight-ISDN-cable to a little PBX/Converter box with a normal phone (non ISDN) attached
• From the NT1-box a second straight-ISDN-cable to the Asterisk/SAIL server with an HFC ISDN-card

My objective is to pick up one or two of the msn's with the Asterisk/SAIL server and do stuff with it. Can someone see where i'm going wrong here?!

Thanx in advance!
jester.