thr3ads.net - asterisk users - [Asterisk-Users] Busy message on ISDN cards? [Dec 2004]

If this information is useful, please help other people find it:
Share via:

Andrew Furey

2004-Dec-13 22:43 UTC

[Asterisk-Users] Busy message on ISDN cards?

Hi all,

I'm new to asterisk and not too knowledgeable on ISDN, so please be gentle
:)

I have a dual-channel Eicon Diehl Diva card in a Debian Woody box with
kernel 2.4.27, connecting to a Telstra (Australia) Onramp Home Highway
ISDN line. I'm pretty certain the card and line both work since
they've been used in this machine for PPP before this (but with an
older kernel with DoV patches, which are no longer to be used).


If I do

# modprobe hisax type=11,11 protocol=2,2 id="HiSax"

it responds (in the syslog) with:

kernel: ISDN subsystem Rev:
1.1.4.1/1.1.4.1/1.1.4.1/1.1.4.1/1.1.4.1/1.1.4.1 loaded
kernel: HiSax: Linux Driver for passive ISDN cards
kernel: HiSax: Version 3.5 (module)
kernel: HiSax: Layer1 Revision 1.1.4.1
kernel: HiSax: Layer2 Revision 1.1.4.1
kernel: HiSax: TeiMgr Revision 1.1.4.1
kernel: HiSax: Layer3 Revision 1.1.4.1
kernel: HiSax: LinkLayer Revision 1.1.4.1
kernel: HiSax: Total 2 cards defined
kernel: HiSax: Card 1 Protocol EDSS1 Id=HiSax (0)
kernel: HiSax: Eicon.Diehl Diva driver Rev. 1.1.4.2
kernel: PCI: Found IRQ 9 for device 00:09.0
kernel: PCI: Sharing IRQ 9 with 00:04.2
kernel: Diva: IPAC PCI card configured at 0xd0862000 IRQ 9
kernel: Diva: IPAC PCI space at 0xd0860000
kernel: Diva: IPAC version 1
kernel: Eicon.Diehl Diva: IRQ 9 count 1697
kernel: Eicon.Diehl Diva: IRQ 9 count 1705
kernel: HiSax: DSS1 Rev. 1.1.4.1
kernel: HiSax: 2 channels added
kernel: HiSax: MAX_WAITING_CALLS added

so it appears to be detected. I'm using the following modem.conf:

[interfaces]
context=remote
driver=i4l
language=en
type=autodetect
dialtype=tone
mode=immediate

group=1
msn=91234567
incomingmsn=*
device => /dev/ttyI0


Starting asterisk with -vvvvc returns:

 == Parsing '/etc/asterisk/modules.conf': Found
[chan_modem.so] => (Generic Voice Modem Driver)
 == Parsing '/etc/asterisk/modem.conf': Found
 == Loading modem driver chan_modem_i4l.so => (ISDN4Linux Emulated Modem
Driver)


But if I define a test extension such as:

TRUNK=Modem/g1
exten => 2468,1,Dial(${TRUNK}/91234567:0412345678)

and try to dial it, the console says:

Dec 14 13:29:17 WARNING[15375]: chan_modem_i4l.c:608 i4l_dial:
Outgoing MSN andrew not allowed (see outgoingmsn=,, in modem.conf)
    -- Called g1/91234567:0412345678
    -- Modem[i4l]/ttyI0 is busy
    -- Hungup 'Modem[i4l]/ttyI0'

I gather than "busy" is used for pretty much everything except for no
connection, but are there any suggestions of where to look?

Thanks in advance,

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

Hatzis, Michael

2004-Dec-14 15:20 UTC

head link

[Asterisk-Users] Busy message on ISDN cards?

I had the same problem even though it was with capi, this may help. Have
you set your msn as Andrew or your line number??

Try this

exten => 2468,1,Dial(${TRUNK}/91234567:0412345678:1)

Regards

 

Michael Hatzis

 0421 476 211


-----Original Message-----
From: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Andrew
Furey
Sent: Tuesday, 14 December 2004 4:43 PM
To: asterisk-users@lists.digium.com
Subject: [Asterisk-Users] Busy message on ISDN cards?

Hi all,

I'm new to asterisk and not too knowledgeable on ISDN, so please be
gentle :)

I have a dual-channel Eicon Diehl Diva card in a Debian Woody box with
kernel 2.4.27, connecting to a Telstra (Australia) Onramp Home Highway
ISDN line. I'm pretty certain the card and line both work since
they've been used in this machine for PPP before this (but with an
older kernel with DoV patches, which are no longer to be used).


If I do

# modprobe hisax type=11,11 protocol=2,2 id="HiSax"

it responds (in the syslog) with:

kernel: ISDN subsystem Rev:
1.1.4.1/1.1.4.1/1.1.4.1/1.1.4.1/1.1.4.1/1.1.4.1 loaded
kernel: HiSax: Linux Driver for passive ISDN cards
kernel: HiSax: Version 3.5 (module)
kernel: HiSax: Layer1 Revision 1.1.4.1
kernel: HiSax: Layer2 Revision 1.1.4.1
kernel: HiSax: TeiMgr Revision 1.1.4.1
kernel: HiSax: Layer3 Revision 1.1.4.1
kernel: HiSax: LinkLayer Revision 1.1.4.1
kernel: HiSax: Total 2 cards defined
kernel: HiSax: Card 1 Protocol EDSS1 Id=HiSax (0)
kernel: HiSax: Eicon.Diehl Diva driver Rev. 1.1.4.2
kernel: PCI: Found IRQ 9 for device 00:09.0
kernel: PCI: Sharing IRQ 9 with 00:04.2
kernel: Diva: IPAC PCI card configured at 0xd0862000 IRQ 9
kernel: Diva: IPAC PCI space at 0xd0860000
kernel: Diva: IPAC version 1
kernel: Eicon.Diehl Diva: IRQ 9 count 1697
kernel: Eicon.Diehl Diva: IRQ 9 count 1705
kernel: HiSax: DSS1 Rev. 1.1.4.1
kernel: HiSax: 2 channels added
kernel: HiSax: MAX_WAITING_CALLS added

so it appears to be detected. I'm using the following modem.conf:

[interfaces]
context=remote
driver=i4l
language=en
type=autodetect
dialtype=tone
mode=immediate

group=1
msn=91234567
incomingmsn=*
device => /dev/ttyI0


Starting asterisk with -vvvvc returns:

 == Parsing '/etc/asterisk/modules.conf': Found
[chan_modem.so] => (Generic Voice Modem Driver)
 == Parsing '/etc/asterisk/modem.conf': Found
 == Loading modem driver chan_modem_i4l.so => (ISDN4Linux Emulated Modem
Driver)


But if I define a test extension such as:

TRUNK=Modem/g1
exten => 2468,1,Dial(${TRUNK}/91234567:0412345678)

and try to dial it, the console says:

Dec 14 13:29:17 WARNING[15375]: chan_modem_i4l.c:608 i4l_dial:
Outgoing MSN andrew not allowed (see outgoingmsn=,, in modem.conf)
    -- Called g1/91234567:0412345678
    -- Modem[i4l]/ttyI0 is busy
    -- Hungup 'Modem[i4l]/ttyI0'

I gather than "busy" is used for pretty much everything except for no
connection, but are there any suggestions of where to look?

Thanks in advance,

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

Andrew Furey

2004-Dec-27 00:33 UTC

head link

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

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
accountcodecontext=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

Andrew Furey

2005-Jan-19 02:50 UTC

head link

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

> 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[snip]
>   == received CONNECT_CONF PLCI = 0x101 INFO = 0
>     -- DISCONNECT_IND ID=001 #0x000f LEN=0014
>   Controller/PLCI/NCCI            = 0x101
>   Reason                          = 0x3301

Well, after much head-banging, we finally worked out that the Fritz
card itself was faulty. Returned it under warranty for a replacement,
and all works perfectly (line synchronisation, outgoing calls,
iincoming calls). Argh...

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

Reasonably Related Threads

Search for more reasonably related threads

asterisk users - Dec 2004 - Busy message on ISDN cards?

[Asterisk-Users] Busy message on ISDN cards?

[Asterisk-Users] Busy message on ISDN cards?

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

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

Reasonably Related Threads