Discussion:
CAPI doesn't detect reject
(too old to reply)
a***@web.de
2006-03-08 11:07:17 UTC
Permalink
Hi there,

I have configured "dialout with callback" on my client (coso remote)
which runs capiplugin and pppd (CAPI). The other side is running
isdnctrl and ipppd (isdn4linux) and is configured for "callback on
incoming call with reject". It detects the incoming call, issues a
reject properly but the reject won't be detected by CAPI on the client.
The client pppd properly is waiting for the callback ("capiplugin:
waiting for callback...") but just finishes with a DISCONNECT_IND
reason 0x3490 (Normal call clearing, should be 3495?) some time (20sec)
later. Only after that it accepts the incoming callback. But this is an
unacceptable long time to establish the connection.
Does someone have an idea whats going wrong here?
See the config below. Can post logs as well.

Regards,
Thomas

Client config for capiplugin:
======================

# Callback with D-channel signaling
plugin capiplugin.so
number 34
msn 31
controller 1
cli 34
coso remote
dialmax 1
sync
10.0.0.1:10.0.0.2
ipcp-accept-local
ipcp-accept-remote
auth
require-pap
remotename tetris
/dev/null

Other side isdnctrl config:
=====================

Current setup of interface 'ippp0':

EAZ/MSN: 34
Phone number(s):
Outgoing: 31
Incoming: 31
Dial mode: manual
Secure: on
Callback: in
Reject before Callback: on
Callback-delay: 2
Dialmax: 1
Hangup-Timeout: 300
Incoming-Hangup: on
ChargeHangup: off
Charge-Units: 0
Charge-Interval: 0
Layer-2-Protocol: hdlc
Layer-3-Protocol: trans
Encapsulation: syncppp
Slave Interface: None
Slave delay: 10
Master Interface: None
Pre-Bound to: Nothing
PPP-Bound to: Nothing
a***@web.de
2006-03-08 11:28:09 UTC
Permalink
Forgot to mention these infos:

Client with CAPI:
- Eicon Diva Server 4BRI ISDN pci card
- CAPI kernel drivers http://www.melware.de/de/index.html
- capi4k-utils-2005-07-18
- ppp-2.4.2

Other side:
- isdn4linux:
- isdnctrl version 3.1pre4
- ipppd version i2.2 patch level 12
a***@web.de
2006-03-10 14:53:53 UTC
Permalink
Problem solved myself.
A buggy ipppd on the other side caused the problems.

Loading...