search for: edss1

...an SIP to Analog- or ISDN-Converter. The point is, I _need_ to deliver calls to extensions in the connected PABX directly (in ISDN-speech "DDI" (DirectDialIn)) without intervention of an operator. Is this technically possible, and if yes HOW? Tips for Hardware-Converters (SIP->ISDN(EDSS1), SIP->Analog) are also appreciated. Cheers, Peter

...wiki help seems to be for the Fritz card only...??? I have ticked the suggested boxes in 'menuconfig', explored the capi4linux websites - etc... but am missing some magic. I've "modprobe capi", if I don't "modprobe hisax type=11" to get- HiSax: Card 1 Protocol EDSS1 Id=HiSax (0) HiSax: Eicon.Diehl Diva driver Rev. 1.1.4.2 ... then whet am I meant to do instead? Obviously no *.... (load_module: CAPI not installed!) A pointer in the right direction please? ie - does the Dumb EICON card work with capi?, do I need the server eicon card instead?, is CAPI only wo...

Hello all. I have installed and functioning asterisk-1.2.9.1 where I effected one upgrade in asterisk-1.0.9, is interconnected with a PABX Siemens HiPath 4000 in ISDN PRI with protocol QSIG, the one that is happening he is that the calls originated for PABX Siemens and destined to SIP phones asterisk are being without audio, nor Ring, is dumb. They could help in this case me? Best Regards Josu?

If I want to send outgoing DTMF over a BRI interface, can I do it with 'isdn4linux' or must I use the 'capi' library? -- . . ___. .__ Posix Systems - Sth Africa /| /| / /__ mje@posix.co.za - Mark J Elkins, Cisco CCIE / |/ |ARK \_/ /__ LKINS Tel: +27 12 807 0590 Cell: +27 82 601 0496 -------------- next part -------------- A non-text attachment was

...ersion 3.5 (module) HiSax: Layer1 Revision 2.46.2.5 HiSax: Layer2 Revision 2.30.2.4 HiSax: TeiMgr Revision 2.20.2.3 HiSax: Layer3 Revision 2.22.2.3 HiSax: LinkLayer Revision 2.59.2.4 HiSax: Warning - no protocol specified HiSax: using protocol EURO HiSax: Total 1 card defined HiSax: Card 1 Protocol EDSS1 Id=HiSax (0) HiSax: Traverse Tech. NETjet-S driver Rev. 2.13.2.4 ACPI: PCI interrupt 0000:01:07.0[A] -> GSI 18 (level, low) -> IRQ 201 NETjet-S: TJ300 card configured at 0x2000 IRQ 201 NETjet-S: ISAC version (0): 2086/2186 V1.1 NETjet-S: IRQ 201 count 0 NETjet-S: IRQ 201 count 6 HiSax: DSS1 R...

...rnel: HiSax: Version 3.5 (module) kernel: HiSax: Layer1 Revision 1.1.4.1 kernel: HiSax: Layer2 Revision 1.1.4.1 kernel: HiSax: TeiMgr Revision 1.1.4.1 kernel: HiSax: Layer3 Revision 1.1.4.1 kernel: HiSax: LinkLayer Revision 1.1.4.1 kernel: HiSax: Total 2 cards defined kernel: HiSax: Card 1 Protocol EDSS1 Id=HiSax (0) kernel: HiSax: Eicon.Diehl Diva driver Rev. 1.1.4.2 kernel: PCI: Found IRQ 9 for device 00:09.0 kernel: PCI: Sharing IRQ 9 with 00:04.2 kernel: Diva: IPAC PCI card configured at 0xd0862000 IRQ 9 kernel: Diva: IPAC PCI space at 0xd0860000 kernel: Diva: IPAC version 1 kernel: Eicon.Diehl...

...: Layer1 Revision 1.1.4.1 HiSax: Layer2 Revision 1.1.4.1 HiSax: TeiMgr Revision 1.1.4.1 HiSax: Layer3 Revision 1.1.4.1 HiSax: LinkLayer Revision 1.1.4.1 HiSax: Approval certification failed because of HiSax: unauthorized source code changes HiSax: Total 1 card defined HiSax: Card 1 Protocol EDSS1 Id=HiSax (0) HiSax: Traverse Tech. NETjet-S driver Rev. 1.1.4.1 PCI: Found IRQ 10 for device 05:0b.0 NETjet-S: PCI card configured at 0x1000 IRQ 10 NETjet-S: ISAC version (0): 2086/2186 V1.1 NETjet-S: IRQ 10 count 0 NETjet-S: IRQ 10 count 4 HiSax: DSS1 Rev. 1.1.4.1 HiSax: 2 channels added...

Hello all, I'm new to asterisk. Our company wants to setup an asterisk server and will eventually move to IP centric phones, but they don't want to just throw away the old Siemens PBX, so during the process we want to integrate it with asterisk. Is it possible? and how? thanks. Lito -------------- next part -------------- An HTML attachment was scrubbed... URL:

----- Original Message ----- From: Karl Heyes <karl@pts.tele2.co.uk> To: <icecast@xiph.org> Sent: Friday, January 31, 2003 5:29 PM Subject: Re: [icecast] Re: Compiling ices <p>> On Fri, 2003-01-31 at 06:39, Marc Remijn wrote: > ... > > > Kernel output: > > > > invalid operand: 0000 > > CPU: 0 > > EIP: 0010:[<d08e25b1>]