[chan-capi-users] Call Deflection stopped working

[Armin Schindler]

On Fri, 16 Jan 2009, Christoph Lukas wrote:
> [..]
>> Why don't you use a newer version of chan_capi ?
>
> I made some backported packages for Debian etch a while ago and did not
> have any need to upgrade. :)
>
>>> Does anybody see why this happens?
>>
>> chan_capi aborts the deflect command if the controller reports (during
>> capi controller profile read) that deflect is not supported. In your case
>> the controller doesn't report this feature. You can check this using
>> shell command 'capiinfo'. In the last section "Supplementary services
>> support" you should see "Call Deflection".
>
> Calling capiinfo from the command line I get:
>
> Number of Controllers : 1
> Controller 1:
> Manufacturer:
> CAPI Version: 2.0
> Manufacturer Version: 49.23
> Serial Number: 1000001
> BChannels: 0
> Global Options: 0x00000000
> B1 protocols support: 0x00000000
> B2 protocols support: 0x00000000
> B3 protocols support: 0x00000000
>
>  0100
>  0000
>  00000000
>  00000000
>  00000000
>  00000000
>  00000000 00000000 00000000 00000000 00000000 00000000
>  00000000 00000000 00000000 00000000 00000000
>
> Supplementary services support: 0x000003ff
>   Hold / Retrieve
>   Terminal Portability
>   ECT
>   3PTY
>   Call Forwarding
>   Call Deflection
>   MCID
>   CCBS
>
> Looks like the controller is reporting that it is capable of 'Call
> Deflection'. Or did I get something wrong?

Yes, this feature is reported. But the basic features are all 0x0
which is totaly wrong. I have seen this before with Fritz driver, but I 
cannot tell why.

> Is it possible to debug the 'chan_capi controller profile read' to find
> out what's going on?

Not necessary, the profile above is just wrong and must be fixed.
Anyway, when you load the chan_capi module while core verbose is higher
(e.g. 5) you see some of the profile settings.

Armin