<< Both of the X100Ps seem to randomly hang-up both incoming and outgoing calls.>>
I think most people who use X100P cards (clone or originals) have had your experience. So far as I can tell, the cause is always an interrupt problem. Specifically that affected X100P cards share an interrupt with one or more other devices. Have you checked for shared interrupts using the command: cat /proc/interrupts to see if any interrupts are shared? In my case we have 3 X100P. At first hang-ups occurred all the time on all cards. A quick review showed that all three cards were sharing interrupts: one with eth0 device and the other two with each other. After some trial and error I now have a workable system. Two of the cards work fine however one, it seems, must share with eth0 and continues to hangup. The rules seem to be: 1) If at all possible, try to arrange to have the X100P cards on their own interrupt. 2) If this is not possible, have them share with devices that are not used or don't generate many interrupts. For example one of my cards shares with an unused USB device and this seems to be fine. Finally, choose a motherboard that offers flexibility in the use of interrupts. Being a thrifty sort, I bought the cheapest mother board I could. It appears that one of the compromises the board designers made has been to share three interrupts across 5 PCI *and* the built-in eth0 device. As a consequence it is hard (impossible) to arrange use of the slots so that there is no interrupt sharing. By contrast, a friend is reusing an old HP machine and each PCI slot (and so each X100P) seems to have its own interrupt. In any case there are no problems - presumably because there are no interrupt conflicts. Bill Seddon -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vassilis Konstantinou Sent: January 09, 2005 9:14 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: [Asterisk-Users] X100P random hangups - Please help with suggestions This one is driving me crazy. So any suggestions will be very welcome. My setup: Suse Linux 9.0 (Pentium 4, 1GB) Asterisk: current stable (1.0.3?) - tried the head CVS before Christmas but did not fix it 2 X100P clones - one for a UK BT line, one connected to an ATA186 configured for a UK BT Broabband-Voice service (MGCP) 1 ATA186 (SIP) connected to two dect internal phones (configured as extensions 5000-5001) The problem: Both of the X100Ps seem to randomly hang-up both incoming and outgoing calls. There is no fixed dureation but it always happens. Sometimes as soon as a call is answered and sometimes at any point up to 10-15 minutes. All calls through my true VOIP lines (I use sipcall in UK and fwd) are fine and never disconnect during the call. The X100Ps seem to detect the "real" hangup properly (of course). Things I have tried: 1) The latest CVS (up to early December). No change 2) The current stable. No change 3) Playing with the rxgain in the zapata.conf file (no change) 4) Using the Loopstart instead of Kewlstart. No false hangups here BUT as expected lots of line noise. Is this a good clue to what is happening? Are there any parameters I can tweak to make the Kewlstart driver a bit more reliable? Please help. This is driving me (and the people using the system crazy). Vassilis My current zapata.conf is attached below: ======================== ;; ; Zapata telephony interface ; ; Configuration file [channels] ; ; Default language ; group => 1 language=en ; ; Default context ; context=incoming switchtype=national usedistinctiveringdetection=no useincomingcalleridonzaptransfer=yes rxwink=300 usecallerid=yes hidecallerid=no callwaiting=no usecallingpres=no callwaitingcallerid=no threewaycalling=no transfer=yes cancallforward=no callreturn=no echocancel=yes echocancelwhenbridged=yes echotraining=yes relaxdtmf=yes rxgain=0.0 txgain=1.5 ; ; Specify whether the channel should be answered immediately or ; if the simple switch should provide dialtone, read digits, etc. ; immediate=no ;musiconhold=default callprogress=no progzone=uk ; usecallerid = yes ; we want Caller*ID support cidsignalling = v23 ; UK (BT) Caller*ID uses the V.23 std cidstart = history ; use the Zaptel history (X100P) busydetect=no signalling=fxs_ks channel => 1 ;BT Broadband Voice - Uses US ID and busysignal on Hangup busydetect=yes busycount=6 cidstart = ring ; ring starts Caller*ID cidsignalling = bell ; Cid US signalling=fxs_ks channel => 2 _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users