[Asterisk-Users] CAPI unable to handle busy()

Karsten Wemheuer kwem at gmx.de
Mon Jan 2 06:06:55 MST 2006


Hello,

first of all, I say "Happy New Year" to this list!

While using asterisk 1.2.1 with bristuff-0.3.0-PRE-1d (which includes
chan_capi 0.4.0-PRE1), I ran into the following problem.

I want to signal "busy" to an incoming call, but that doesn't work.

The dialplan looks like this:
	exten => 22715292,1,Busy
(The extension is ok and works fine, if I use other applications like
Dial)

The result is:
   -- creating pipe for PLCI=0x101 msn = 22715292
       > sent ALERT_REQ PLCI = 0x101
    -- Executing Busy("CAPI/contr1/22715292-13", "") in new stack
    -- started pbx on channel (callgroup=0)!

The caller hears still ringing signal.

If I replace "Busy" with "Busy(2)", the following happens:
    -- creating pipe for PLCI=0x101 msn = 22715292
       > sent ALERT_REQ PLCI = 0x101
    -- Executing Busy("CAPI/contr1/22715292-14", "2") in new stack
    -- started pbx on channel (callgroup=0)!
  == Spawn extension (incoming, 22715292, 1) exited non-zero on
'CAPI/contr1/22715292-14'
    -- CAPI Hangingup
    -- removed pipe for PLCI = 0x101
But again, the calling site gets no busy-signalling.

If I use hangup(17) instead of busy() (which should be the same as 17 is
the value for the busy condition), I get the following result:
   -- creating pipe for PLCI=0x101 msn = 22715292
       > sent ALERT_REQ PLCI = 0x101
    -- Executing Hangup("CAPI/contr1/22715292-15", "17") in new stack
  == Spawn extension (incoming, 22715292, 1) exited non-zero on
'CAPI/contr1/22715292-15'
    -- CAPI Hangingup
       > sent CONNECT_RESP for PLCI = 0x101
    -- removed pipe for PLCI = 0x101
    -- started pbx on channel (callgroup=0)!
Jan  2 14:00:36 ERROR[1143]: chan_capi.c:1237 pipe_frame: wrote -1 bytes
instead of 48

The calling site will see a normal call clearing.

Hardware is a FritzPCI! (AVM).

If I do the same things with a HFC-based card and chan_zap, both version
(busy() and hangup(17)) are working fine.

Any helping hints are welcome!

Thanks!

Karsten




More information about the asterisk-users mailing list