[Asterisk-Users] Working Asterisk with Austrian ISDN p2p
Marcus Hofbauer
marcus.hofbauer at gmail.com
Wed Mar 1 06:54:59 MST 2006
Which chan_capi Version should I apply this patch to?
I'm using chan_capi-cm-0.6.4. If I try to patch I get this message ...
patching file chan_capi.c
Hunk #1 FAILED at 3354.
1 out of 1 hunk FAILED -- saving rejects to file chan_capi.c.rej
2006/3/1, Armin Schindler <armin at melware.de>:
> Hmm, an Austrian PtP line was already reported to work (I cannot test this),
> but the logic of chan_capi seems to be incomplete for that case.
> Can you please try the following patch:
>
> diff -u -r1.117.2.37 chan_capi.c
> --- chan_capi.c 10 Feb 2006 16:16:00 -0000 1.117.2.37
> +++ chan_capi.c 1 Mar 2006 09:49:39 -0000
> @@ -3354,8 +3354,7 @@
> pbx_builtin_setvar_helper(i->owner, "ANI2", buffer);
> pbx_builtin_setvar_helper(i->owner, "SECONDCALLERID", buffer);
> */
> - if ((i->isdnmode == CAPI_ISDNMODE_MSN) && (i->immediate)) {
> - /* if we don't want to wait for SETUP/SENDING-COMPLETE in MSN mode */
> + if (i->immediate) {
> start_pbx_on_match(i, PLCI, HEADER_MSGNUM(CMSG));
> }
> return;
>
> On Wed, 1 Mar 2006, Marcus Hofbauer wrote:
> > this is wat i get from asterisk with capi debug ...
> >
> > CAPI Debugging Enabled
> > CONNECT_IND ID=001 #0x5207 LEN=0041
> > Controller/PLCI/NCCI = 0x102
> > CIPValue = 0x10
> > CalledPartyNumber = default
> > CallingPartyNumber = <21 83>69910204082
> > CalledPartySubaddress = default
> > CallingPartySubaddress = default
> > BC = <80 90 a3>
> > LLC = default
> > HLC = <91 81>
> > AdditionalInfo = default
> >
> > -- CONNECT_IND (PLCI=0x102,DID=,CID=6991XXXXXXX,CIP=0x10,CONTROLLER=0x2)
> > == ISDN1: Incoming call '006991XXXXXXX' -> ''
> > INFO_IND ID=001 #0x5208 LEN=0016
> > Controller/PLCI/NCCI = 0x102
> > InfoNumber = 0x18
> > InfoElement = <89>
> >
> > INFO_RESP ID=001 #0x5208 LEN=0012
> > Controller/PLCI/NCCI = 0x102
> >
> > -- ISDN1: info element CHANNEL IDENTIFICATION 89
> > INFO_IND ID=001 #0x5209 LEN=0016
> > Controller/PLCI/NCCI = 0x102
> > InfoNumber = 0x18
> > InfoElement = <89>
> >
> > INFO_RESP ID=001 #0x5209 LEN=0012
> > Controller/PLCI/NCCI = 0x102
> >
> > -- ISDN1: info element CHANNEL IDENTIFICATION 89
> > INFO_IND ID=001 #0x520a LEN=0017
> > Controller/PLCI/NCCI = 0x102
> > InfoNumber = 0x8
> > InfoElement = <82 e5>
> >
> > INFO_RESP ID=001 #0x520a LEN=0012
> > Controller/PLCI/NCCI = 0x102
> >
> > -- ISDN1: info element CAUSE 82 e5
> > DISCONNECT_IND ID=001 #0x520b LEN=0014
> > Controller/PLCI/NCCI = 0x102
> > Reason = 0x34e5
> >
> > DISCONNECT_RESP ID=001 #0x520b LEN=0012
> > Controller/PLCI/NCCI = 0x102
> >
> > > CAPI INFO 0x34e5: Message not compatible with call state
> > -- ISDN1: DISCONNECT_IND on incoming without pbx, doing hangup.
> > == ISDN1: CAPI Hangingup
> > == ISDN1: Interface cleanup PLCI=0x102
> > > CAPI devicestate requested for ISDN1/
> >
> > On 01/03/06, Ralf Schlatterbeck <ralf at zoo.priv.at> wrote:
> > > On Wed, Mar 01, 2006 at 08:13:13AM +0100, Marcus Hofbauer wrote:
> > > > I'm looking for someone who has successfuly setup an asterisk in
> > > > austria with isdn in p2p mode and chan_capi.
> > > >
> > > > There is is a special problem in austria with DID. If someone is
> > > > dialing the phone number of the asterisk pbx like 12345-0, zero is
> > > > passed as an DID, but in Austria u can dial 12345, and the DID which
> > > > is passed is empty.
> > > >
> > > > It seems that asterisk cant handle this. Any ideas?
> > >
> > > p2p + DID + chan_capi + mISDN is -- at least for me -- currently not
> > > working (at least not in Austria). I'm in the process of sorting this
> > > out with Karsten Keil and Armin Schindler. You might want to check their
> > > progress:
> > > - The asterisk mailing-list thread:
> > > http://lists.digium.com/pipermail/asterisk-users/2006-February/148042.html
> > > - My bug-report to the mISDN Bug-Tracker:
> > > https://www.isdn4linux.de/mantis/view.php?id=40
> > > (needs registration in the mantis bug-tracker)
> > >
> > > If you have an active card (using a manufacturers capi implementation)
> > > it could work. In this case you need the "s" extension configured in
> > > asterisk for the context where incoming isdn calls are handled. Then if
> > > an empty DID arrives, the s-extension handles that call.
> > >
> > > Ralf
> > > --
> > > Ralf Schlatterbeck
> > > email: ralf at zoo.priv.at FAX: +43/2243/26465/23
> > >
> > > _______________________________________________
> > > --Bandwidth and Colocation provided by Easynews.com --
> > >
> > > Asterisk-Users mailing list
> > > To UNSUBSCRIBE or update options visit:
> > > http://lists.digium.com/mailman/listinfo/asterisk-users
> > _______________________________________________
> > --Bandwidth and Colocation provided by Easynews.com --
> >
> > Asterisk-Users mailing list
> > To UNSUBSCRIBE or update options visit:
> > http://lists.digium.com/mailman/listinfo/asterisk-users
> >
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> Asterisk-Users mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
>
--
|** realität ist da wo der pizzamann herkommt **|
More information about the asterisk-users
mailing list