[asterisk-users] Xorcom Bri 4 Port USB

Wed Jun 27 19:59:34 CDT 2007

Thanks Tzafrir, that did the trick.
But please note the that the bristuff patch from xorcom has broken links in it. It can't download asterisk using the URL in the script. Easy enough to fix by pointing to a known good URL.

________________________________

From: asterisk-users-bounces at lists.digium.com on behalf of Tzafrir Cohen
Sent: Mon 25/06/2007 7:09 PM
To: asterisk-users at lists.digium.com
Subject: Re: [asterisk-users] Xorcom Bri 4 Port USB

Hi

On Mon, Jun 25, 2007 at 06:38:37PM +1000, Nathan Dennis wrote:
>
> Hi,
>    I'm having some trouble setting up a Xorcom Bri 4 port. I have compiled asterisk and zaptel using the Bristuff bristuff-0.3.0-PRE-1y-g patches.
>
> So I'm running zaptel-1.2.17.1 and asterisk-1.2.18.
>
> The problem I'm having is that for one I get no LEDs showing if the unit
> is in TE and NT mode (not a issue for me but may have some impact on
> things) I have no errors in any logs I can see but once zaptel and
> asterisk are started up I get a lots of warnings in asterisk such as
> the following

What is the output of:

modinfo xpp | grep version

if this is something of the sort of 'r3495' then you indeed have an
older version of the driver where BRI support has not been matuire
enough and specifically leds display was not as it is today. In current
version (e.g: the one in zaptel 1.2.18/1.4.3) you will always see an
orange LED for NT or green led for TE on the port.

Please get the version of bristuff from:

http://updates.xorcom.com/astribank/bristuff/
http://updates.xorcom.com/astribank/bristuff/bristuff-0.3.0-PRE-1y-g-xr1.tar.gz

At least until we see a new version of bristuff.

and also see:

http://updates.xorcom.com/astribank/bristuff/INSTALL.html

Also, for the sake of those who will see the messages in a search:

>
> Jun 25 18:18:07 WARNING[2833]: chan_zap.c:2662 pri_find_dchan: No D-channels available!  Using Primary channel 3 as D-channel anyway!
>   == Primary D-Channel on span 2 down
> Jun 25 18:18:07 WARNING[2834]: chan_zap.c:2662 pri_find_dchan: No D-channels available!  Using Primary channel 6 as D-channel anyway!
>   == Primary D-Channel on span 3 down
> Jun 25 18:18:07 WARNING[2835]: chan_zap.c:2662 pri_find_dchan: No D-channels available!  Using Primary channel 9 as D-channel anyway!
>   == Primary D-Channel on span 1 down
>

This message comes from chan_zap when a span is down. If a span has
pri_{cpe,net} signalling or bri_{cpe,net} signalling (bristuff BRI ptp)
then you'll get those messages for spans that are down. If the
signalling is bri_{cpe,net}_ptmp they'll be debug messages.

> It errors for all for ports and makes no difference if I have the
> ISDN cables connected or not. I want to run in ptp mode and
> currently use a digium B410P card on the connections that work fine
> so I know that the lines work and ptp is the correct mode.
>

> Following are my configs. Any pointers you can give would be greatly appreciated.
>
> We are running Fedora 7.
> Kernel "Linux 2.6.21-1.3194.fc7 #1 SMP i686 i686 i386 GNU/Linux" (Standard Kernel with install)
> Device has jumpers all set to TE mode.
>
>
> /etc/init.d/zaptel.conf
> # Span 1: XBUS-00/XPD-00 "Xorcom XPD #0/0: BRI_TE"
> span=1,1,1,ccs,ami
> # termtype: te
> bchan=1-2
> dchan=3
>
> # Span 2: XBUS-00/XPD-08 "Xorcom XPD #0/8: BRI_TE"
> span=2,2,1,ccs,ami
> # termtype: te
> bchan=4-5
> dchan=6
>
> # Span 3: XBUS-00/XPD-10 "Xorcom XPD #0/16: BRI_TE"
> span=3,3,1,ccs,ami
> # termtype: te
> bchan=7-8
> dchan=9
>
> # Span 4: XBUS-00/XPD-18 "Xorcom XPD #0/24: BRI_TE" RED
> #span=4,4,1,ccs,ami
> # termtype: te
> #bchan=10-11
> #dchan=12
>
> # Global data
>
> loadzone        = au
> defaultzone     = au
>
>
> /etc/asterisk/zapata.conf
> [channels]
> ;       echocancel = yes
> ;       transfer = yes
> ;       threewaycalling = yes
>
> #include zapata-channels.conf
>
>
> /etc/asterisk/zapata-channels.conf
>
> ; Span 1: XBUS-00/XPD-00 "Xorcom XPD #0/0: BRI_TE"
> callerid=asreceived
> group=0
> context=from-pstn
> switchtype = euroisdn
> signalling = bri_cpe
> channel => 1-2
> callerid=
> group=
> context=default
>
> ; Span 2: XBUS-00/XPD-08 "Xorcom XPD #0/8: BRI_TE"
> callerid=asreceived
> group=0
> context=from-pstn
> switchtype = euroisdn
> signalling = bri_cpe
> channel => 4-5
> callerid=
> group=
> context=default
>
> ; Span 3: XBUS-00/XPD-10 "Xorcom XPD #0/16: BRI_TE"
> callerid=asreceived
> group=0
> context=from-pstn
> switchtype = euroisdn
> signalling = bri_cpe
> channel => 7-8
> callerid=
> group=
> context=default
>
> ; Span 4: XBUS-00/XPD-18 "Xorcom XPD #0/24: BRI_TE" RED
> ;callerid=asreceived
> ;group=0
> ;context=from-pstn
> ;switchtype = euroisdn
> ;signalling = bri_cpe
> ;channel => 10-11
> ;callerid=
> ;group=
> ;context=default

--
               Tzafrir Cohen      
icq#16849755                    jabber:tzafrir at jabber.org
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com      
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir

_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 9003 bytes
Desc: not available
Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20070628/a7bb54c6/attachment.bin 