[Asterisk-Users] RE: *, Fritz!PCI and strange behavior

[Chris Wilson]

Hi Patrick and others,

On Tue, 4 Nov 2003, Patrick Lidstone (Personal E-mail) wrote:

> > - Very often, after * runs for a while, it stops recognizing incoming
> >   ISDN calls and refuses to send out ISDN calls.
> 
> I have this. If I try to dial out, I get an "all channels are busy at 
> this time" error, when they are not.

How did you get this error displayed? All I get with CAPI DEBUG is a 
reason code.

> >The funny thing is, 
> >   restarting * or CAPI doesn't work - I have to shutdown both, unplug
> >   and replug the ISDN cable, and then after startup everything works
> >   again. At first, I thought that it might be a bad cable, so I taped
> >   down everything in order to prevent it from moving. This
> > didn't help.
> >   I really do not understand why the thing with the cable is 
> > necessary.
> 
> Straight asterisk restart always clears this condition for me.

We just experienced a problem which looked something like this. Nobody 
could call in or out through the Fritz cards until we restarted Asterisk. 
The CAPI debug output looked like this:

  == CONNECT_IND (PLCI=0x101,DID=510,CID=221,CIP=0x1,CONTROLLER=0x1)
  == DISCONNECT_IND PLCI=0x101 REASON=0
  == CONNECT_IND (PLCI=0x101,DID=510,CID=(null),CIP=0x4,CONTROLLER=0x1)
  == DISCONNECT_IND PLCI=0x101 REASON=0

where CONNECT_IND was immediately followed by DISCONNECT_IND. There was 
none of the normal output:

    -- data = 514:901482320681
    -- capi request omsn = 514
  == found capi with omsn = 514

or CONNECT_CONF/CONNECT_B3_REQ/DISCONNECT_B3_IND.

Reason code 0 looks very suspicious. /var/log/messages showed:

Nov  6 13:11:42 voip kernel: kcapi: appl 1 ncci 0x10102 up
Nov  6 13:12:19 voip kernel: kcapi: appl 1 ncci 0x10102 down
Nov  6 13:13:35 voip kernel: kcapi: appl 1 ncci 0x10101 up
Nov  6 13:13:41 voip kernel: kcapi: appl 1 ncci 0x10101 down
Nov  6 13:13:49 voip kernel: kcapi: appl 1 ncci 0x10101 up
Nov  6 13:13:58 voip kernel: kcapi: appl 1 ncci 0x10101 down
Nov  6 13:15:26 voip kernel: kcapi: appl 1 ncci 0x10101 up
Nov  6 13:15:56 voip kernel: kcapi: appl 1 ncci 0x10101 down

Does anybody have any ideas?

> > Any light that you can shine on this would be most helpful. OBTW: the 
> > answer "don't use a Fritz" is not applicable here - I'm trying to 
> > assess the feasibility of making a <300$ ISDN SoHo PBX...
> 
> I think the problem may be related to call progress indication from the
> ISDN line. I have UK ISDN2e (packaged as Business Highway - which
> includes what is effectively a telco-owned TA with two analogue ports).
> I have noticed that outgoing channels getting tied up corresponds to
> placing a call which is terminated prematurely (e.g. hangup before
> completing dialing) or dialing a call which can't be completed because
> the dialed PSTN subscriber number is invalid. I've learned to live with
> it - but it would be great to get to the bottom of it.

Sorry, forgot to run "show channels" and "capi info". Will try to remember 
next time.

Cheers, Chris.
-- 
   ___ __     _
 / __// / ,__(_)_  | Chris Wilson -- UNIX Firewall Lead Developer |
/ (_ / ,\/ _/ /_ \ | NetServers.co.uk http://www.netservers.co.uk |
\ _//_/_/_//_/___/ | 21 Signet Court, Cambridge, UK. 01223 576516 |