Topic: problem with ISDN card

[Robyn]

Hi

I'm having some trouble with an Eicon Diva card.  The card is a Diva 2.01 PCI which is on the approved list.  The card seems to install OK but my SME (5.5) can't to use it.  I'm using the same card with IPCOP with no troubles.

Extract from logs
**********************************
May 27 15:00:57 server1 kernel: CSLIP: code copyright 1989 Regents of the University of California
May 27 15:00:57 server1 kernel: ISDN subsystem Rev: 1.114.6.7/1.94/1.140.6.3/1.85.6.2/1.21/1.5.6.2 loaded
May 27 15:00:57 server1 kernel: HiSax: Linux Driver for passive ISDN cards
May 27 15:00:57 server1 kernel: HiSax: Version 3.5 (module)
May 27 15:00:57 server1 kernel: HiSax: Layer1 Revision 2.41.6.1
May 27 15:00:57 server1 kernel: HiSax: Layer2 Revision 2.25
May 27 15:00:57 server1 kernel: HiSax: TeiMgr Revision 2.17
May 27 15:00:57 server1 kernel: HiSax: Layer3 Revision 2.17.6.1
May 27 15:00:57 server1 kernel: HiSax: LinkLayer Revision 2.51
May 27 15:00:57 server1 kernel: HiSax: Approval certification failed because of
May 27 15:00:57 server1 kernel: HiSax: unauthorized source code changes
May 27 15:00:57 server1 kernel: HiSax: Total 1 card defined
May 27 15:00:57 server1 kernel: HiSax: Card 1 Protocol EDSS1 Id=HiSax (0)
May 27 15:00:57 server1 kernel: HiSax: Eicon.Diehl Diva driver Rev. 1.25.6.3
May 27 15:00:57 server1 kernel: Diva: IPAC PCI card configured at 0xc8914000 IRQ 10
May 27 15:00:57 server1 kernel: Diva: IPAC PCI PCI space at 0xc8912000
May 27 15:00:57 server1 kernel: Diva: IPAC version 1
May 27 15:00:57 server1 kernel: Eicon.Diehl Diva: IRQ 10 count 0
May 27 15:00:57 server1 kernel: Eicon.Diehl Diva: IRQ 10 count 6
May 27 15:00:57 server1 kernel: HiSax: DSS1 Rev. 2.30
May 27 15:00:57 server1 kernel: HiSax: 2 channels added
May 27 15:00:57 server1 kernel: HiSax: MAX_WAITING_CALLS added
May 27 15:00:58 server1 kernel: PPP: version 2.3.7 (demand dialling)
May 27 15:00:58 server1 kernel: PPP line discipline registered.
May 27 15:00:58 server1 kernel: PPP BSD Compression module registered
May 27 15:00:58 server1 ippp: Configuring ippp interfaces:
May 27 15:00:58 server1 ippp:  diald
May 27 15:01:00 server1 ipppd[870]: Found 2 devices: ,
May 27 15:01:00 server1 ipppd[873]: ipppd i2.2.12 (isdn4linux version of pppd by MH) started
May 27 15:01:00 server1 ipppd[873]: init_unit: 0
May 27 15:01:00 server1 kernel: ippp, open, slot: 0, minor: 0, state: 0000
May 27 15:01:00 server1 kernel: ippp_ccp: allocated reset data structure c6868000
May 27 15:01:00 server1 ipppd[873]: Connect[0]: /dev/ippp0, fd: 7
May 27 15:01:00 server1 ippp:
May 27 15:01:00 server1 rc: Starting ippp:  succeeded
May 27 15:01:00 server1 ipppd[873]: init_unit: 1
May 27 15:01:00 server1 kernel: ippp, open, slot: 1, minor: 0, state: 0000
May 27 15:01:00 server1 kernel: ippp_ccp: allocated reset data structure c71c0000
May 27 15:01:00 server1 ipppd[873]: Connect[1]: /dev/ippp0, fd: 8
**********************************

so the card seems to be recognised OK BUT when it goes to dial...

**********************************
May 27 15:16:08 server1 diald[905]: Calling site 0.0.0.0
May 27 15:16:10 server1 chat[1748]: abort on (BUSY)
May 27 15:16:10 server1 chat[1748]: abort on (ERROR)
May 27 15:16:10 server1 chat[1748]: abort on (NO CARRIER)
May 27 15:16:10 server1 chat[1748]: abort on (NO DIALTONE)
May 27 15:16:10 server1 chat[1748]: abort on (Invalid Login)
May 27 15:16:10 server1 chat[1748]: abort on (Login incorrect)
May 27 15:16:10 server1 chat[1748]: report (CONNECT)
May 27 15:16:10 server1 chat[1748]: send (ATZ^M)
May 27 15:16:10 server1 chat[1748]: expect (OK)
May 27 15:16:10 server1 chat[1748]: ^M
May 27 15:16:10 server1 chat[1748]: OK
May 27 15:16:10 server1 chat[1748]:  -- got it
May 27 15:16:10 server1 chat[1748]: send (ATe0v0q0s0=255+iS1/2+iM4+iP9+iB10^M)
May 27 15:16:10 server1 chat[1748]: expect (OK)
May 27 15:16:10 server1 chat[1748]: ^M
May 27 15:16:10 server1 chat[1748]: ATe0v0q0s0=255+iS1/2+iM4+iP9+iB10^M^M
May 27 15:16:10 server1 chat[1748]: 4^M
May 27 15:16:55 server1 chat[1748]: alarm
May 27 15:16:55 server1 chat[1748]: Failed
May 27 15:16:55 server1 diald[905]: Connect script failed.
**********************************

the string "ATe0v0q0s0=255+iS1/2+iM4+iP9+iB10^M" is used to set up the card for DOV (aka Tollmizer).  Its taken directly from the Eicon web site and its the same string that I use in IPCOP.

so I tried Minicom but the card doesnt seem to be recognised
**********************************
ati
Linux ISDN
OK
atz
OK
atz9
ERROR
***********************************


any suggestions very welcome

thanks

[Charlie]

Robyn wrote:

> so I tried Minicom but the card doesnt seem to be recognised
> **********************************
> ati
> Linux ISDN
> OK
> atz
> OK
> atz9
> ERROR

The card is recognized, I think, or it wouldn't say OK. You'll need to use an init string which the driver will accept via minicom.

Charlie

[David Barr]

I have the same problem using a Trust PCI ISDN card.  The card works fine on Redhat 7,8 and 9, but when using it on SME server 5.6 it doesn't dial up.  How do I find out the init string to use?

Any comments?

David

[Dave Liquorice]

As you are using v5.6 have you checked the bugs page....  or even browsed back to last night in this  very group?

Cheers
Dave.