asterisk users - Jan 2004 - CAPI: Early-B3 working with AVM-B1?

Hi,

I tested the capi_chan with latest cvs of * and I have problems with
Early-B3. The following dialstring works for me (without Early B3):
	exten => _0X.,1,Dial(CAPI/@22715291:${EXTEN:1}|30)
But if I add the 'b' for using Early-B3
	exten => _0X.,1,Dial(CAPI/@22715291:b${EXTEN:1}|30)
nothing changes (no dialtone). If in this example the called party
discards the call, there is no signalling to my SIP-Phones. In this case
"capi debug" tells a lot of:

--------
    -- CONNECT_B3_ACTIVE_IND ID=001 #0xb2f4 LEN=0013
  Controller/PLCI/NCCI            = 0x10101
  NCPI                            = default

       > sent CONNECT_B3_ACTIVE_RESP (NCCI=0x10101)
       > sent DATA_B3_RESP (NCCI=0x10101)
       > sent DATA_B3_RESP (NCCI=0x10101)
       > sent DATA_B3_RESP (NCCI=0x10101)
       > sent DATA_B3_RESP (NCCI=0x10101)
       > sent DATA_B3_RESP (NCCI=0x10101)
       > sent DATA_B3_RESP (NCCI=0x10101)
       > sent DATA_B3_RESP (NCCI=0x10101)
       > sent DATA_B3_RESP (NCCI=0x10101)
       > sent DATA_B3_RESP (NCCI=0x10101)
       > sent DATA_B3_RESP (NCCI=0x10101)
       > sent DATA_B3_RESP (NCCI=0x10101)
       > sent DATA_B3_RESP (NCCI=0x10101)
... until I stop the call from SIP phone (the originating site)

    -- CAPI Hangingup
       > activehangingup
       > sent DISCONNECT_B3_REQ NCCI=0x10101
    -- DISCONNECT_B3_CONF ID=001 #0x001a LEN=0014
  Controller/PLCI/NCCI            = 0x10101
  Info                            = 0x0

  == DISCONNECT_B3_IND NCCI=0x10101
       > sent DISCONNECT_B3_RESP NCCI=0x10101
       > sent DISCONNECT_REQ PLCI=0x101
    -- DISCONNECT_CONF ID=001 #0x001b LEN=0014
  Controller/PLCI/NCCI            = 0x101
  Info                            = 0x0

  == DISCONNECT_IND PLCI=0x101 REASON=0x3495
       > sent DISCONNECT_RESP PLCI=0x101
    -- removed pipe for PLCI = 0x101
-------
Hardware is a AVM-B1 (active BRI card)

What am I doing wrong, or where can I start debugging?

Thanks,

Karsten

Hi,

here is an update to my own post to this list.

Following an information from Philipp, I testet this with an passive AVM
card, but the same things happen. What am I doing wrong?

Is there something wrong with my extension.conf?
----
without Early B3:
	exten => _0X.,1,Dial(CAPI/@22715291:${EXTEN:1}|30)
with Early B3:
	exten => _0X.,1,Dial(CAPI/@22715291:b${EXTEN:1}|30)
----

Thanks,

Karsten

Hi Karsten,

are you sure your MSN is correct? If not T-Com will replace it
with your "main" MSN and probably will ignore the CLIR setting.

best regards

kapejod
-- 
Klaus-Peter Junghanns

CEO, CTO
Junghanns.NET GmbH
Breite Strasse 13a - 12167 Berlin - Germany
fon: (de) +49 30 79705390
fon: (uk) +44 870 1244692
fax: (de) +49 30 79705391
iaxtel: 1-700-157-8753
http://www.Junghanns.NET/asterisk/


Am Do, 2004-01-22 um 09.00 schrieb Karsten Wemheuer:
> Hi,
> 
> here is an update to my own post to this list.
> 
> Following an information from Philipp, I testet this with an passive AVM
> card, but the same things happen. What am I doing wrong?
> 
> Is there something wrong with my extension.conf?
> ----
> without Early B3:
> 	exten => _0X.,1,Dial(CAPI/@22715291:${EXTEN:1}|30)
> with Early B3:
> 	exten => _0X.,1,Dial(CAPI/@22715291:b${EXTEN:1}|30)
> ----
> 
> Thanks,
> 
> Karsten
> 
> 
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users

Hi Klaus-Peter,

Klaus-Peter Junghanns wrote:
> Hi Karsten,
> 
> are you sure your MSN is correct? If not T-Com will replace it
> with your "main" MSN and probably will ignore the CLIR setting.
> 
> best regards
> 
> kapejod
Thanks for the reply, but in this thread my problem is the "Early-B3",
not CLIR.

The MSN I used, is one of my own (not the first one), they are correct
and will be signaled to my mobile when testing, but I got no "ring"
signal. The mobile shows the correct number. If I press the red button
to discard the call, there are many messages in the debug (see my first
post in this thread). I thought it was a problem of the card, cause
Philipp told me, it works for him with  "Fritz!"-card. So I tested
again
with aN ISA Fritz! card with the same result...

Hope You have any ideas...

Thanks
Karsten

Hi,

I make some more tests and the results are a little bit strange...

My testbed consists of an active card and I used linphone as client. The
results are as described here in my previous posts. But today I tested
with xTen Lite as client... And it works. I take some sniffer traces and
the difference between the two clients is, that the client xten sends
RTP packets to * after resceiving "SIP Status 183 Session Progress"
from
*. After a while RTP packets in the opposite direction (which seems to
be the ringing from the far end) are transferred. In case of Linphone no
RTP packets are transferred at all.

a) Linphone as client:
	Linphone		Asterisk
	Invite		--->
			<---		100 Trying
			<---		183 Session Progress
	.... nothing happens until:
			<---		200 OK	
			
b) xTen as client:
	xTen				Asterisk
	Invite		--->
			<---		100 Trying
			<---		183 Session Progress
	RTP data	--->
	RTP data	--->
	....
	RTP data	--->
			<---		RTP data
			<---		200 OK	

So is it possible, that * waits for any RTP data from the client?

Thanks
Karsten