Posted: Sat Mar 15, 2008 6:56 pm Post subject: [Asterisk-bsd] missing destination extension in chan_capi, i
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
Posted: Sun Mar 16, 2008 8:22 am Post subject: [Asterisk-bsd] missing destination extension in chan_capi, i
Hi Michael,
With regard to chan_capi there is an "immediate" option which will make an "s"
out of empty destination numbers. That might be your problem, to make the
dialplan match against an empty number:
if (cd->flags.sending_complete_received || start_immediate) {
/* number is complete, try to start the PBX */
cd_start_pbx(pp_cd, start_immediate ? "s" :
&(cd->dst_telno[0]));
cd = *pp_cd;
}
capi.conf NOTE:
USB devices currently start at controller unit 63.
--HPS
On Saturday 15 March 2008, Michael Iedema wrote:
Quote:
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
Posted: Mon Mar 17, 2008 9:04 am Post subject: [Asterisk-bsd] missing destination extension in chan_capi, i
On 3/16/08, Hans Petter Selasky <hselasky@c2i.net> wrote:
Quote:
Hi Michael,
With regard to chan_capi there is an "immediate" option which will make an "s"
out of empty destination numbers. That might be your problem, to make the
dialplan match against an empty number:
if (cd->flags.sending_complete_received || start_immediate) {
/* number is complete, try to start the PBX */
cd_start_pbx(pp_cd, start_immediate ? "s" :
&(cd->dst_telno[0]));
cd = *pp_cd;
}
Thanks for the tip!
I've added immediate=yes to the generated configs and am now
generating an 's' extension for the provider's incoming extension.
I'll post back again once some users can test these changes.
Regards,
-Michael
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--
Posted: Wed Mar 26, 2008 10:37 am Post subject: [Asterisk-bsd] missing destination extension in chan_capi, i
On Mon, Mar 17, 2008 at 9:56 AM, Michael Iedema <michael@askozia.com> wrote:
Quote:
On 3/16/08, Hans Petter Selasky <hselasky@c2i.net> wrote:
> Hi Michael,
>
> With regard to chan_capi there is an "immediate" option which will make an "s"
> out of empty destination numbers. That might be your problem, to make the
> dialplan match against an empty number:
>
> if (cd->cep) {
>
> start_immediate = (cd->options.immediate && (cd->dst_telno[0] ==
> 0));
>
> if (cd->flags.sending_complete_received || start_immediate) {
>
> /* number is complete, try to start the PBX */
>
> cd_start_pbx(pp_cd, start_immediate ? "s" :
> &(cd->dst_telno[0]));
> cd = *pp_cd;
> }
>
Thanks for the tip!
I've added immediate=yes to the generated configs and am now
generating an 's' extension for the provider's incoming extension.
I'll post back again once some users can test these changes.
Unfortunately, still no luck here. Incoming calls using PTP-TE mode
are still failing for multiple people. We've tried:
- setting immediate=yes / no
- setting isdnmode=did / msn
Every time, there is no destination extension set. Since these are
incoming calls which are failing, I can rule out mistakes in the
Dial() settings. I have a stack of capi.conf, extensions.conf and
d-channel traces from a few different people but cannot locate what's
going wrong. The latest of these submissions is here[1].
More documentation about how capi.conf and isdnconfig should be
configured using PTP-TE mode specifically would be great if there are
some floating around. Any and all help is appreciated.
Posted: Thu Mar 27, 2008 12:23 pm Post subject: [Asterisk-bsd] missing destination extension in chan_capi, i
On Wed, Mar 26, 2008 at 7:12 PM, Hans Petter Selasky <hselasky@c2i.net> wrote:
Quote:
Hi,
Could you send me your updated "extensions.conf" ?
Does the following extension exist: 'ISDN Out-incoming' ?
I think it is something in the dialplan that is wrong.
--HPS
That log was copied from the web interface which replaces the internal
names with the user given names. I've disabled it in future releases.
The context is below:
; incoming provider : ISDN Out
[ISDN-PROVIDER-159382343347c6f0e545af0-incoming]
When there is only one destination for incoming calls from that line,
things work with immediate=yes. That sets an 's' extension and
AskoziaPBX generates an 's' extension to be used. For multiple
destinations, no number is sent and AskoziaPBX does not generate 's'
extensions as the call must be routed.
I will have access next week to a PTP line to do my own testing but
for now here are his extensions.conf and interface status info.
ISDN Unit 0 (HFC PCI Card)
Attached yes
PH State F3: Deactivated
Dialtone enabled
Description HFC-2BDS0 128K PCI ISDN adapter
Type passive ISDN (Basic Rate, 2xB)
Driver Type DRVR_DSS1_P2P_TE (point-to-point, terminal equipment)
Channels 0x3
Serial 0xabcd
Power Save off
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum