asterisk users - Jun 2004 - chan_capi and DDI (Anlagenanschluss)

Hi all !

We have 3 NTBAs which are all going to our existing PBX. Our areacode is 
06003 and our DDI enabled number 9141.

I want to exchange that PBX with Asterisk, but still struggle to get it 
working.

My CAPI.CONF is currently like this:

[general]
nationalprefix=0
internationalprefix=00
rxgain=0.800000
txgain=0.800000

[interfaces]
context=in-capi
msn=60039141
incomingmsn=*
controller=1
softdtmf=1
isdnmode=ptp
devices=2

And a snippet from my EXTENSION.CONF:

exten=88,1,Dial(CAPI/60039141:0170811xxxx,60,T)

to dial my cellphone. Unfortunately, this won't work.




With this setup, I can't even dial out. With "capi debug", I see
this:

  -- Executing Dial("SIP/hschurig-c63f",
"CAPI/60039141:0170811xxxx|60|T")
in new stack
  -- data = 60039141:01708112001
  -- capi request omsn = 60039141
== found capi with omsn = 60039141
== CAPI Call CAPI[contr1/60039141]/1     -- creating pipe for PLCI=-1
     > sent CONNECT_REQ MN =0x5
  -- Called 60039141:01708112001
  -- CONNECT_CONF ID=001 #0x0005 LEN=0014
Controller/PLCI/NCCI            = 0x101
Info                            = 0x0

  -- CONNECT_CONF ID=001 #0x0005 LEN=0014
Controller/PLCI/NCCI            = 0x101
Info                            = 0x0

== received CONNECT_CONF PLCI = 0x101 INFO = 0
  -- DISCONNECT_IND ID=001 #0x0019 LEN=0014
Controller/PLCI/NCCI            = 0x101
Reason                          = 0x3302

== DISCONNECT_IND PLCI=0x101 REASON=0x3302
     > sent DISCONNECT_RESP PLCI=0x101
  -- CAPI Hangingup
  -- removed pipe for PLCI = 0x101
== No one is available to answer at this time


Is there any source where I can lookup what "REASON=0x3302" means?

-- 
M&N Solutions GmbH       http://www.mn-solutions.de
Holger Schurig
Dieselstr. 18
61191 Rosbach v.d.H?he
Tel: (+49) 6003 9141 0   Fax: (+49) 6003 9141 49

Holger Schurig wrote:
> Hi all !
> 
> We have 3 NTBAs which are all going to our existing PBX. Our areacode is 
> 06003 and our DDI enabled number 9141.
> 
> I want to exchange that PBX with Asterisk, but still struggle to get it 
> working.
> 
> My CAPI.CONF is currently like this:
> 
> [general]
> nationalprefix=0
> internationalprefix=00
> rxgain=0.800000
> txgain=0.800000
> 
> [interfaces]
> context=in-capi
> msn=60039141
At least for PTMP (Mehrger?teanschluss) the MSN does not contain the 
areacode.

Try

msn=9141

and see if it helps.
--
rgds
pos

> At least for PTMP (Mehrger?teanschluss) the MSN does not contain the
> areacode.
Thanks for the info. Somewhere in the list archive I saw a hint to use the 
areacode as well. Now tried it without and had the same (non)success:

  -- Executing Dial("SIP/hschurig-ced5",
"CAPI/9141:0170811xxxx|60|T") in
new stack
  -- data = 9141:0170811xxxx
  -- capi request omsn = 9141
== found capi with omsn = 9141
== CAPI Call CAPI[contr1/9141]/1     -- creating pipe for PLCI=-1
     > sent CONNECT_REQ MN =0x5
  -- Called 9141:01708112001
  -- CONNECT_CONF ID=001 #0x0005 LEN=0014
Controller/PLCI/NCCI            = 0x101
Info                            = 0x0

  -- CONNECT_CONF ID=001 #0x0005 LEN=0014
Controller/PLCI/NCCI            = 0x101
Info                            = 0x0

== received CONNECT_CONF PLCI = 0x101 INFO = 0
  -- DISCONNECT_IND ID=001 #0x001c LEN=0014
Controller/PLCI/NCCI            = 0x101
Reason                          = 0x3302

== DISCONNECT_IND PLCI=0x101 REASON=0x3302
     > sent DISCONNECT_RESP PLCI=0x101
  -- CAPI Hangingup
  -- removed pipe for PLCI = 0x101
== No one is available to answer at this time



BTW: at a different NTBA (which is a PTMP for an ISDN router) I can call 
out and receive calls, so the chan_capi + fcpci + capi chain is known to 
work.

> BTW: at a different NTBA (which is a PTMP for an ISDN router) I can call 
> out and receive calls, so the chan_capi + fcpci + capi chain is known to 
> work.
Did you configure your CAPI driver to run in PTP mode? (not PTMP mode)


Regards,
Julian Pawlowski
________________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt neu bei WEB.DE FreeMail: http://freemail.web.de/?mc=021193

> Did you configure your CAPI driver to run in PTP mode? (not PTMP mode)
Hmm, I guess you brought me on the rigth track.

# cat /proc/capi/controllers/1
name             fritz-pci
io               0xA800
irq              5
type             A1
class            10
ver_driver       3.11-02
ver_cardtype     fritz-pci
protocol         DSS1
linetype         point to multipoint

How can I change this?

> The modules are from Linux 2.4.26, fcpci is from 03.11.02.
I remember that it's not possible to have an AVM Fritz card on an PTP mode
ISDN line.
I think cards with HFC chipset are able to do so. Of cause you could also use an
active card with CAPI driver ;-)


Regards,
Julian Pawlowski
________________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt neu bei WEB.DE FreeMail: http://freemail.web.de/?mc=021193

Klaus-Peter Junghanns wrote:
> you can use the AVM Fritz card in P2P mode, if you use the new mISDN
> capi layer with chan_capi.
That's a good idea in principle but in my opinion it's sometimes too
buggy at the moment so productive usage is not recommendable. I made those
experiences when I tried PBX4Linux with it and think that it's often die
mISDN driver itself who makes trouble....


Regards
Julian Pawlowski

__________________________________________________________________
Zeigen Sie Emotionen mit der WEB.DE Bild-SMS! Das Bild ist gratis,
Sie bezahlen nur den Versand. http://freemail.web.de/?mc=021196