login | register
Thu 28 of Aug, 2008 [03:51 UTC]

voip-info.org

Discuss [1] History

Asterisk Sirrix ISDN channels

Created by: sirrix,Last modification on Thu 05 of Apr, 2007 [09:21 UTC]

Asterisk Channels provided by the Sirrix channel driver chan_sirrix for

1. Sirrix.PCI4S0 card providing 4 S0-ports (NT and TE), hardware switching, a full featured ISDN stack and optional encryption of ISDN connections.

Image



2. Sirrix.PCI2E1 card providing 2 PRI ports, hardware switching, hardware echo cancellation with conference bridge, a full featured ISDN stack and optional encryption of ISDN connections.

Image
Both cards are manufactured by Sirrix AG, Saarbrücken. The 32 bit cards fit in a 3.3 & 5V slot.



PCM Connector Description




Configuration


The sirrix.conf configuration file is organized in groups of settings. Each group is defined by its groupname (arbitrary) and contains one or more settings for that group.

Definition of used types

Global settings

Group definition

Usage in extensions.conf

Incoming calls (in to Asterisk)

Example of a sirrix.conf.



Further options for control


The Sirrix Channel driver provides additional Dialplan commands, Channel Varibles and CLI commands for control.

Asterisk Dialplan-Applications

Asterisk CLI commands

Asterisk Channel Variables

AOC Engine




Interaction with Asterisk Database


Asterisk CallerID Name DB

Asterisk CallForward DB



Notes


  • In conjunction with the PPPD dialplan command, the Sirrix.PCI4S0 can be used to provide PPP (RAS) dialin and dialout on ISDN channels.
  • Drivers for the Sirrix card can requested by e-mail from support (at) sirrix (dot) com



Rev. 871

Comments

Comments Filter
222

333Timing and Multiple BRI Cards

by MmmToop, Tuesday 06 of June, 2006 [06:54:34 UTC]
Multiple Sirrix cards can be installed in a machine. These cards however need to be linked via a serial cable/ HD cable to the pins at the back of the card. Like any ISDN interface these devices are sensitive to timing issues: 1. You need to clear conflicting interrupts (do cat /proc/interrupts or lspci -v test) 2. You need to make sure you have set up the Master/s correctly.

Simple Debug Method (Bit hazy around why it works...but it does ; ) :
  • Set *each* individual line as Master & ONLY run one line @ a time & make a call. No science here but I think it has something to do with the Network assigning a NEID to the device...they 'establish' the link
  • Choose a line for your timing Master
  • Try keep the Master in a different call group
  • Activate all the lines
  • If one doesn’t come up i.e act=0 then you should remove that from the group & consult your Network provider