[Asterisk-Users] Busy message on ISDN cards?

[Hatzis, Michael]

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 at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Andrew
Furey
Sent: Tuesday, 14 December 2004 4:43 PM
To: asterisk-users at 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 at 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