Ok here is all I got from the logs. I use the same hardware for other 
customers, except that they do not have fxs ports but then again I do not even 
use the FXS ports on this setup.


Thanks in advance,
Loic.

cat /var/log/asterisk/messages
[2008-12-30 21:42:08] NOTICE[5399] chan_dahdi.c: Got DAHDI_EVENT_REMOVED. 
Destroying channel 1
[2008-12-30 21:42:08] NOTICE[5399] chan_dahdi.c: Got DAHDI_EVENT_REMOVED. 
Destroying channel 2
[2008-12-30 21:42:08] NOTICE[5399] chan_dahdi.c: Got DAHDI_EVENT_REMOVED. 
Destroying channel 4
[2008-12-30 21:42:08] NOTICE[5399] chan_dahdi.c: Got DAHDI_EVENT_REMOVED. 
Destroying channel 5

From /var/log/syslog
Dec 30 21:42:08 wedekindpbx1 kernel: [ 3746.344509] usb 7-5: USB disconnect, 
address 2
Dec 30 21:42:08 wedekindpbx1 kernel: [ 3746.344611] ERR-xpp_usb: XBUS-00: 
xusb_listen: usb_submit_urb failed: -19
Dec 30 21:42:08 wedekindpbx1 kernel: [ 3746.353325] INFO-xpp: XBUS-00: [] 
Disconnecting
Dec 30 21:42:08 wedekindpbx1 kernel: [ 3746.353373] Zaptel: Master changed to 
XBUS-00/XPD-01
Dec 30 21:42:08 wedekindpbx1 kernel: [ 3746.353382] Zaptel: Master changed to 
XBUS-00/XPD-02
Dec 30 21:42:08 wedekindpbx1 kernel: [ 3746.353391] Zaptel: Master changed to 
XBUS-00/XPD-03
Dec 30 21:42:08 wedekindpbx1 kernel: [ 3746.353516] INFO-xpp_usb: xusb-0 
(usb-0000:00:1d.7-5) []: now disconnected
Dec 30 21:42:08 wedekindpbx1 kernel: [ 3746.632514] usb 7-5: new high speed USB 
device using ehci_hcd and address 3
Dec 30 21:42:08 wedekindpbx1 kernel: [ 3746.783133] usb 7-5: configuration #1 
chosen from 1 choice
Dec 30 21:42:08 wedekindpbx1 kernel: [ 3746.911834] usb 7-5: reset high speed 
USB device using ehci_hcd and address 3
Dec 30 21:42:08 wedekindpbx1 kernel: [ 3747.062188] INFO-xpp_usb: XUSB: Xorcom 
LTD -- Astribank -- FPGA
Dec 30 21:42:08 wedekindpbx1 kernel: [ 3747.062291] INFO-xpp: XBUS-01: [] 
Activating
Dec 30 21:42:08 wedekindpbx1 kernel: [ 3747.062325] NOTICE-xpp: XBUS-01: 
GLOBAL_REGISTER_REPLY_handler: non-existing address (00):
Dec 30 21:42:08 wedekindpbx1 kernel: [ 3747.062330] NOTICE-xpp: XBUS-01: 
GLOBAL_REGISTER_REPLY_handler: non-existing address (00):
Dec 30 21:42:08 wedekindpbx1 kernel: [ 3747.071539] INFO-xpp: XBUS-01: 
DESCRIPTOR: 2 cards, protocol revision 30
Dec 30 21:42:08 wedekindpbx1 kernel: [ 3747.071549] INFO-xpp: XBUS-01:     CARD 
0 type=3.0 ports=4 (1x4), port-dir=0xF0
Dec 30 21:42:08 wedekindpbx1 kernel: [ 3747.071557] INFO-xpp: XBUS-01:     CARD 
1 type=1.1 ports=8 (8x1), port-dir=0xFF
Dec 30 21:42:09 wedekindpbx1 init_card_3_30: XBUS-01/UNIT-0: Non Interactive 
startup
Dec 30 21:42:09 wedekindpbx1 init_card_3_30: XBUS-01/UNIT-0: Starting 
'/usr/share/zaptel/init_card_3_30'
Dec 30 21:42:09 wedekindpbx1 init_card_3_30: XBUS-01/UNIT-0: init_xhfc(0)
Dec 30 21:42:15 wedekindpbx1 init_card_3_30: XBUS-01/UNIT-0: Ending 
'/usr/share/zaptel/init_card_3_30'
Dec 30 21:42:15 wedekindpbx1 kernel: [ 3753.955210] INFO-xpp: XBUS-01/XPD-00: 
Initialized: BRI_TE
Dec 30 21:42:15 wedekindpbx1 kernel: [ 3753.955220] INFO-xpp: XBUS-01/XPD-01: 
Initialized: BRI_TE
Dec 30 21:42:15 wedekindpbx1 kernel: [ 3753.955227] INFO-xpp: XBUS-01/XPD-02: 
Initialized: BRI_TE
Dec 30 21:42:15 wedekindpbx1 kernel: [ 3753.955233] INFO-xpp: XBUS-01/XPD-03: 
Initialized: BRI_TE
Dec 30 21:42:15 wedekindpbx1 init_card_1_30: XBUS-01/UNIT-1: Non Interactive 
startup
Dec 30 21:42:15 wedekindpbx1 init_card_1_30: XBUS-01/UNIT-1: Starting 
'/usr/share/zaptel/init_card_1_30'
Dec 30 21:42:15 wedekindpbx1 init_card_1_30: Use of uninitialized value in 
concatenation (.) or string at /usr/share/zaptel/init_card_1_30 line 386.
Dec 30 21:42:15 wedekindpbx1 init_card_1_30: Use of uninitialized value in 
concatenation (.) or string at /usr/share/zaptel/init_card_1_30 line 386.
Dec 30 21:42:15 wedekindpbx1 init_card_1_30: XBUS-01/UNIT-1: From : 
DEBUG_INIT_FXS= INIT_FXS_SKIP_CALIB=
Dec 30 21:42:17 wedekindpbx1 init_card_1_30: XBUS-01/UNIT-1: Calibrating 
'/usr/share/zaptel/init_card_1_30'
Dec 30 21:42:35 wedekindpbx1 init_card_1_30: XBUS-01/UNIT-1: Continue 
'/usr/share/zaptel/init_card_1_30'
Dec 30 21:42:36 wedekindpbx1 init_card_1_30: XBUS-01/UNIT-1: Ending 
'/usr/share/zaptel/init_card_1_30'
Dec 30 21:42:37 wedekindpbx1 kernel: [ 3775.622144] INFO-xpp: XBUS-01/XPD-10: 
Initialized: FXS


--
Loïc DIDELOT
MIXvoip S.a.
[email protected]
http://www.mixvoip.com

----- Original Message -----
From: "Tzafrir Cohen" <[email protected]>
To: [email protected]
Sent: Tuesday, December 30, 2008 7:37:43 PM GMT +01:00 Amsterdam / Berlin / 
Bern / Rome / Stockholm / Vienna
Subject: Re: [asterisk-users] Xorcom BRI state NOTOPEN

On Tue, Dec 30, 2008 at 05:34:32PM +0100, Loic Didelot wrote:
> Hello,
> I recently got a problem I have never seen during my previous
> installations.
> 
> I have a Xorcom device with 4 BRI and 8 FXS ports. I use ubuntu Linux
> and asterisk 1.4.22. Everything works fine but after some time zap
> channels disappear in asterisk.
> 
> 
> r...@pbx1:~# cat /proc/zaptel/*
> Span 1: XBUS-00/XPD-00 "Xorcom XPD #00/00: BRI_TE" AMI/CCS NOTOPEN
> 
>          1 XPP_BRI_TE/00/00/0 Clear NOTOPEN
>          2 XPP_BRI_TE/00/00/1 Clear NOTOPEN
>          3 XPP_BRI_TE/00/00/2 HDLCFCS (In use) NOTOPEN

A Xorcom Astribank span will have the NOTOPEN alarm if the device itself
has been disconnected.

Do you see any kernel messages at the time of the disconnect? I expect
to see something about a USB device disconnected.

> Span 2: XBUS-00/XPD-01 "Xorcom XPD #00/01: BRI_TE" AMI/CCS NOTOPEN
> 
>          4 XPP_BRI_TE/00/01/0 Clear NOTOPEN
>          5 XPP_BRI_TE/00/01/1 Clear NOTOPEN
>          6 XPP_BRI_TE/00/01/2 HDLCFCS (In use) NOTOPEN
> Span 3: XBUS-00/XPD-02 "Xorcom XPD #00/02: BRI_TE" AMI/CCS NOTOPEN
> 
>          7 XPP_BRI_TE/00/02/0 Clear NOTOPEN
>          8 XPP_BRI_TE/00/02/1 Clear NOTOPEN
>          9 XPP_BRI_TE/00/02/2 HDLCFCS (In use) NOTOPEN
> Span 4: XBUS-00/XPD-03 "Xorcom XPD #00/03: BRI_TE" (MASTER) AMI/CCS
> NOTOPEN
> 
>         10 XPP_BRI_TE/00/03/0 Clear NOTOPEN
>         11 XPP_BRI_TE/00/03/1 Clear NOTOPEN
>         12 XPP_BRI_TE/00/03/2 HDLCFCS (In use) NOTOPEN
> Span 5: XBUS-00/XPD-10 "Xorcom XPD #00/10: FXS" NOTOPEN
> 
>         13 XPP_FXS/00/10/0 FXOKS NOTOPEN
>         14 XPP_FXS/00/10/1 FXOKS NOTOPEN
>         15 XPP_FXS/00/10/2 FXOKS NOTOPEN
>         16 XPP_FXS/00/10/3 FXOKS NOTOPEN
>         17 XPP_FXS/00/10/4 FXOKS NOTOPEN
>         18 XPP_FXS/00/10/5 FXOKS NOTOPEN
>         19 XPP_FXS/00/10/6 FXOKS NOTOPEN
>         20 XPP_FXS/00/10/7 FXOKS NOTOPEN

This is really odd. I would have expected at least FXS/FXO channels to
be immediately destroyed in response to ZT_EVENT_REMOVED / 
DAHDI_EVENT_REMOVED generated on that channel at disconnect time.

What is the output of:

  zaptel_hardware -v

at this time?

-- 
               Tzafrir Cohen
icq#16849755              jabber:[email protected]
+972-50-7952406           mailto:[email protected]
http://www.xorcom.com  iax:[email protected]/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

_______________________________________________
-- 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

Reply via email to