asterisk users - Aug 2005 - Error when answering CAPI

Hi,

    I've a Fritz card which was working fine, recently I changed 
hardware and my nightmare started. Now when I call someone through the 
chan_capi (0.3.5 or 0.4.0) it works fine but when I receive calls I 
always get hungup. Can someone please give some help? Here are the logs:

*CLI>
    -- CONNECT_IND ID=001 #0x0000 LEN=0049
  Controller/PLCI/NCCI            = 0x101
  CIPValue                        = 0x1
  CalledPartyNumber               = <a1>1138121122
  CallingPartyNumber              = A<83>1181114000
  CalledPartySubaddress           = default
  CallingPartySubaddress          = default
  BC                              = <80 90 a3>
  LLC                             = default
  HLC                             = default
  AdditionalInfo                  = default

  == CONNECT_IND 
(PLCI=0x101,DID=1138121122,CID=1181114000,CIP=0x1,CONTROLLER=0x1)
    -- creating pipe for PLCI=0x101 msn = *
    -- INFO_IND ID=001 #0x0001 LEN=0026
  Controller/PLCI/NCCI            = 0x101
  InfoNumber                      = 0x70
  InfoElement                     = <a1>1138121122

    -- INFO_IND ID=001 #0x0001 LEN=0026
  Controller/PLCI/NCCI            = 0x101
  InfoNumber                      = 0x70
  InfoElement                     = <a1>1138121122

       > sent INFO_RESP (PLCI=0x101)
       > sent CONNECT_RESP for PLCI = 0x101
    -- INFO_IND ID=001 #0x0002 LEN=0016
  Controller/PLCI/NCCI            = 0x101
  InfoNumber                      = 0x18
  InfoElement                     = <89>

    -- INFO_IND ID=001 #0x0002 LEN=0016
  Controller/PLCI/NCCI            = 0x101
  InfoNumber                      = 0x18
  InfoElement                     = <89>

       > sent INFO_RESP (PLCI=0x101)
    -- DISCONNECT_IND ID=001 #0x0003 LEN=0014
  Controller/PLCI/NCCI            = 0x101
  Reason                          = 0x0

  == DISCONNECT_IND PLCI=0x101 REASON=0
       > sent DISCONNECT_RESP PLCI=0x101
    -- CAPI Hangingup
       > activehangingup
    -- removed pipe for PLCI = 0x101


capi.conf
======;
; CAPI config
;
;
[general]
nationalprefix=0
internationalprefix=00
rxgain=0.8
txgain=0.8

[interfaces]

; mode: ptmp (point-to-multipoint) or ptp (point-to-point)
isdnmode=ptp
; allow incoming calls to this list of MSNs, * == any
incomingmsn=*
; capi controller number
controller=1
; dialout group
group=1
; enable/disable software dtmf detection, recommended for AVM cards
softdtmf=1
; accountcode to use in CDRs
accountcode; context for incoming calls
context=from-pstn
; _VERY_PRIMITIVE_ echo suppression
;echosquelch=1
; EICON DIVA SERVER echo cancelation
;echocancel=yes
;echotail=64
; call group
;callgroup=1
; deflect incoming calls to 12345678 if all B channels are busy
;deflect=12345678
; number of concurrent calls on this controller (2 makes sense for 
single BRI)
devices => 2

On Wed, 24 Aug 2005, Humberto Aicardi wrote:
> Hi,
> 
>    I've a Fritz card which was working fine, recently I changed
hardware and
> my nightmare started. Now when I call someone through the chan_capi (0.3.5
or
> 0.4.0) it works fine but when I receive calls I always get hungup. Can
someone
> please give some help? Here are the logs:
> 
> *CLI>
>  -- CONNECT_IND ID=001 #0x0000 LEN=0049
> Controller/PLCI/NCCI            = 0x101
...

The logs are incomplete to say something. I don't remember if a higher 
verbose level will show the necessary parts.
I suggest you use chan_capi-cm from sourceforge.
With verbose level 5 and 'capi debug' it shows everything you need.

Armin

On 8/25/05, Humberto Aicardi <news@aicardi.com.br>
wrote:
>     I've a Fritz card which was working fine, recently I changed
AVM Fritz Passive card? If so, then it doesn't work very well in
Pointto Point. Ask your Telco for a Point to Multipoint and change the
setting in capi.conf./

Note:
I am not sure if this will resolve your issue, but I have come across
a few people who have had similar propblems with AVM Fritz Passive.
Its a good card, but only for Point to Multipoint.

-r