<br><br><div class="gmail_quote">2010/5/9 Tzafrir Cohen <span dir="ltr"><<a href="mailto:tzafrir.cohen@xorcom.com" target="_blank">tzafrir.cohen@xorcom.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>On Sat, May 08, 2010 at 08:02:49PM +0200, Olivier wrote:<br>
> 2010/5/8 Olivier <<a href="mailto:oza_4h07@yahoo.fr" target="_blank">oza_4h07@yahoo.fr</a>><br>
><br>
> > Hi,<br>
> ><br>
> > I'm trying to dial from one Asterisk box to a Patton 4638 BRI gateway.<br>
> > I'm only getting this :<br>
> > [May 8 15:08:24] WARNING[16797]: app_dial.c:1547 dial_exec_full: Unable to<br>
> > create channel of type 'DAHDI' (cause 0 - Unknown)<br>
> ><br>
> > My setup is :<br>
> > Asterisk 1.6.1.18<br>
> > libpri 1.4.10.2<br>
> > 1 Junghanns QuadBRI PCI-E express with :<br>
> > - driver<br>
> > <a href="http://webservices.jnetdns.de/%7Ejunghanns.net/downloads/jnet-dahdi-drivers-1.0.1.tar.gz" target="_blank">http://webservices.jnetdns.de/~junghanns.net/downloads/jnet-dahdi-drivers-1.0.1.tar.gz</a><br>
> > - every jumper set to TE mode<br>
> ><br>
> ><br>
> > When typing "pri show spans", Asterisk replies nothing :<br>
> > brs-dev*CLI> pri show spans<br>
> > brs-dev*CLI> pri show version<br>
> > libpri version: 1.4.10.2<br>
> > brs-dev*CLI> dahdi show version<br>
> > DAHDI Version: 2.3.0 Echo Canceller: KB1<br>
<br>
</div>KB1? I wonder why this is preffered to mg2.<br></blockquote><div><br>I agree with you but in JNET sample config files, as KB1 was mentioned, I also kept the same value.<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><br>
> ><br>
> > Each LED is green but dahdi_scan says :<br>
> > # dahdi_scan<br>
> > [1]<br>
> > active=yes<br>
> > alarms=OK<br>
> > description=quadBRI PCI ISDN Card 1 Span 1 [TE] (ca<br>
> > name=ztqoz/1/1<br>
> > manufacturer=<br>
> > devicetype=<br>
> > location=<br>
> > basechan=1<br>
> > totchans=3<br>
> > irq=0<br>
> > type=digital-<br>
<br>
</div>This means that the driver's 'type' field is not set. As are "irq",<br>
manufacturer, devicetype and location. Those should be rather simple to<br>
fix.<br>
<div><br>
> > syncsrc=0<br>
> > lbo=399-533 feet (DSX-1)<br>
> > coding_opts=AMI<br>
> > framing_opts=CCS<br>
> > coding=AMI<br>
> > framing=CCS<br>
> ><br>
> ><br>
> > 1. Is this syncsrc=0 normal (we're in TE mode) ?<br>
> > 2. Am I correct to hope "pri show spans" to display something ?<br>
> > 3. Suggestions ?<br>
<br>
</div>Hmmm... not sure.<br>
<div><br>
> ><br>
> > Regards<br>
> ><br>
> > I should have said I've tried unsuccessfully with both dahdi 2.2.1.1 and<br>
> 2.3.<br>
> I'm really wondering if PCI-E QuadBRI are supported.<br>
<br>
</div>It's not supported?</blockquote><div><br>I don't know ... but using JNET drivers and dahdi doesn't work for me.<br>I'm still getting on and on empty answers to "pri show spans".<br> <br></div>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">If so, can you provide its full vendor ID and<br>
product ID? How does the device appear on 'lspci -vn' (that is: not only<br>
vendor ID and procut ID, but also the subvendor ID and subproduct ID.<br></blockquote><div><br># lspci<br>...<br>06:04.0 ISDN controller: Cologne Chip Designs GmbH ISDN network Controller [HFC-4S] (rev 01)<br><br><br># lspci -vn<br>
...<br>06:04.0 0204: 1397:08b4 (rev 01)<br> Subsystem: 1397:b752<br> Flags: medium devsel, IRQ 11<br> I/O ports at ec00 [size=8]<br> Memory at feaff000 (32-bit, non-prefetchable) [size=4K]<br> Capabilities: [40] Power Management version 2<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
The newer "jnet" dirvers finally use hardhdlc rather than the faked<br>
soft-hdlc used in previous versions. Sadly they still use the<br>
non-standard probing method.<br></blockquote><div>I'm not very aware to probing methods but do you imply JNET drivers should be probed using a specific command (ie /etc/init.d/dahdi should be changed to adapt to JNET drivers ?).<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
--<br>
Tzafrir Cohen<br>
icq#16849755 <a href="mailto:jabber%3Atzafrir.cohen@xorcom.com" target="_blank">jabber:tzafrir.cohen@xorcom.com</a><br>
+972-50-7952406 mailto:<a href="mailto:tzafrir.cohen@xorcom.com" target="_blank">tzafrir.cohen@xorcom.com</a><br>
<a href="http://www.xorcom.com" target="_blank">http://www.xorcom.com</a> <a href="http://iax:guest@local.xorcom.com/tzafrir" target="_blank">iax:guest@local.xorcom.com/tzafrir</a><br>
<br>
--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
<a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
</blockquote></div><br>