[Asterisk-bsd] missing destination extension in chan_capi, incoming calls fail

[Michael Iedema]

Hello everyone,

A user of AskoziaPBX is having trouble receiving incoming calls from
another PBX connected via ISDN, outgoing calls are working. One MSN is
assigned to the s0 bus coming from that PBX and connected to his
system's port which is configured to use point-to-multipoint, terminal
equipment signaling.

When he attaches a telephone to this line everything works correctly.

The appropriate Asterisk logs which show no destination being set or
recognized are:

Mar 5 18:08:13 --
capi_handle_connect_indication:6065:ENTRY=:PLCI=0x0b00:PBX_CHAN=**Unknown**:
-- Incoming call from '302' to '', CIP=0x0010, sending_complete=no
Mar 5 18:08:13 ==
cd_start_pbx:5950:ENTRY=0:PLCI=0x0b00:PBX_CHAN=CAPI/0/-6: == Started
PBX
Mar 5 18:08:13 == Starting CAPI/0/-6 at isdn-unit-0-incoming,,1 failed
so falling back to exten 's'
Mar 5 18:08:13 == Starting CAPI/0/-6 at isdn-unit-0-incoming,s,1 still
failed so falling back to context 'default'
Mar 5 18:08:13 pbx.c:2470 in __ast_pbx_run: Channel 'CAPI/0/-6' sent
into invalid extension 's' in context 'default', but no invalid
handler
Mar 5 18:08:13 == cd_free:2150:ENTRY=0:PLCI=0x0b00:PBX_CHAN=CAPI/0/-6: ==
Mar 5 18:08:13 > CAPI: Command=INFO_IND, 0x8492: no call descriptor
for PLCI=0x0b00, MSGNUM=0x0000:
Mar 5 18:08:13 > CAPI: Command=DISCONNECT_IND, 0x848c: no call
descriptor for PLCI=0x0b00, MSGNUM=0x0000:


I could work around this problem by generating 's' extensions in the
isdn-unit-0-incoming context but this still does not explain to me why
there is no destination information present. Perhaps this is simply
the case if only one MSN is assigned to an s0 bus?

The system is FreeBSD 6.2-p10, Asterisk 1.4.17 and isdn4bsd revision 606.

Attachments (via link, sending bounced once due to size):
 - extensions.conf
 - capi.conf
 - isdn trace of failed call

http://www.askozia.com/tmp/capi_problem_debug_info.zip


Any help on this is greatly appreciated,
-Michael