[Asterisk-Users] Re: Busy message on ISDN cards?

[Andrew Furey]

Something of an update...

At the recommendation of a consultant I called in last week, I've now
switched to an AVM Fritz! PCI card, using CAPI. At this stage I'm only
using the one card so I don't need the patches to run multiple cards
yet.

Upon loading the modules (capi/capifs and fcpci), I get:

CAPI-driver Rev 1.1.4.1: loaded
capifs: Rev 1.1.4.1
capi20: started up with major 68
kcapi: capi20 attached
capi20: Rev 1.1.4.2: started up with major 68 (middleware+capifs)
fcpci: AVM FRITZ!Card PCI driver, revision 0.5.2
fcpci: (fcpci built on Dec 24 2004 at 14:17:43)
fcpci: Loading...
fcpci: Driver 'fcpci' attached to stack
kcapi: driver fcpci attached
fcpci: Auto-attaching...
PCI: Found IRQ 5 for device 00:12.0
fcpci: Stack version 3.11-02
kcapi: Controller 1: fritz-pci attached
kcapi: card 1 "fritz-pci" ready.
fcpci: Loaded.
kcapi: notify up contr 1
capi: controller 1 up

Also this looks correct:

netmagic:~# cat /proc/capi/controllers/1
name             fritz-pci
io               0xD800
irq              5
type             A1
class            14
ver_driver       3.11-02
ver_cardtype     fritz-pci
protocol         DSS1
linetype         point to multipoint

And in the asterisk output:

 [chan_capi.so] => (Common ISDN API for Asterisk)
  == Parsing '/etc/asterisk/capi.conf': Found
    -- This box has 1 capi controller(s).
    -- CAPI[contr1] supports DTMF
    -- CAPI[contr1] supports supplementary services
       > HOLD/RETRIEVE
       > TERMINAL PORTABILITY
       > ECT
       > 3PTY
       > CF
       > CD
       > MCID
       > CCBS
       > MWI
       > CCNR
  == ast_capi_pvt(92130800,*,demo,0,2) (1,2,64)
  == ast_capi_pvt(92130800,*,demo,0,2) (1,2,64)
    -- listening on contr1 CIPmask = 0x1fff03ff
  == Registered channel type 'CAPI' (Common ISDN API Driver (0.3.5)
aLaw CVS HEAD)


Of course I'm not using modem.conf any more, but capi.conf contains:

[general]
nationalprefix=0
internationalprefix=00
rxgain=0.8
txgain=0.8

[interfaces]

msn=91234567
incomingmsn=*
outgoingmsn=91234567
controller=1
softdtmf=1
accountcode=
context=demo
devices=2


The secondary problem I reported earlier (Outgoing MSN andrew not
allowed) seems to have fixed itself. But when I try to call, I get:

*CLI>     -- Executing Dial("SIP/andrew-4e2d",
"Capi/91234567:0412345678") in new stack
    -- data = 91234567:0412345678
    -- capi request omsn = 91234567
  == found capi with omsn = 91234567
  == CAPI Call CAPI[contr1/91234567]/0     -- Called 91234567:0412345678
    -- CONNECT_CONF ID=001 #0x0004 LEN=0014
  Controller/PLCI/NCCI            = 0x101
  Info                            = 0x0

    -- CONNECT_CONF ID=001 #0x0004 LEN=0014
  Controller/PLCI/NCCI            = 0x101
  Info                            = 0x0

  == received CONNECT_CONF PLCI = 0x101 INFO = 0
    -- DISCONNECT_IND ID=001 #0x000f LEN=0014
  Controller/PLCI/NCCI            = 0x101
  Reason                          = 0x3301

  == DISCONNECT_IND PLCI=0x101 REASON=0x3301
    -- CAPI Hangingup
  == No one is available to answer at this time
    -- Timeout on SIP/andrew-4e2d


Sometimes the reason is given as 0x3302 instead. I should also mention
that unlike the Eicon cards, plugging an Onramp into the Fritz card
does not cause the Onramp to synchronise... the LED just keeps
flashing.

I noted that the output above lists the card as "point-to-multipoint".
Finding a couple of pages which suggested that both the card and the
line need to be in this mode, I rang Telstra on Friday, who said that
the line was currently in point-to-point mode, but they would change
it to point-to-multipoint immediately. Of course there's no one there
until Wednesday to check if it's actually been done, but there's no
apparent change from before (the existing PBX can synchronise but the
Fritz card can't).

Any further ideas?

Thanks,
Andrew

-- 
Linux supports the notion of a command line or a shell for the same
reason that only children read books with only pictures in them.
Language, be it English or something else, is the only tool flexible
enough to accomplish a sufficiently broad range of tasks.
                          -- Bill Garrett