[Bayonne-devel] capi20

[Michael Stöckel]

Hi,

Half a year later I try again to get a running bayonne with capi20.

The --test fails again in step 3:

debug: *** start of trap test
CAPI: postEvent 402
CAPI: idleHandler 402
CAPI: ringHandler 100
CAPI: Contr1 0: ringing
starting script test::test3
CAPI: Contr1 0: attach script
CAPI: stepHandler 100
CAPI: Contr1 0: step fffb sleep(0)
CAPI: setTimer 36
CAPI: postEvent 403
CAPI: stepHandler 403
ALERT_CONF ID=003 #0x0004 LEN=0014
  Controller/PLCI/NCCI            = 0x0
  Info                            = 0x2002
CAPI: Contr1 0: step 3 sleep(0)
CAPI: setTimer 36
CAPI: Contr1 0: step fffb sleep(2)
CAPI: TrunkStep
CAPI: stepHandler 303
CAPI: sleepHandler 100
CAPI: Contr1 0: sleep
CAPI: setTimer 2000
CAPI: postEvent 506
debug: *** test trap failed
CAPI: sleepHandler 401
CAPI: stepHandler 100
CAPI: Contr1 0: step fffb exit()
CAPI: setTimer 36
CAPI: Contr1 0: exit
CAPI: Exit

but if I run an additional debug command:
e.g.:

::test3
        sleep 0
        debug "*** test3/0"
-dtmf   sleep 0
        sleep 2
        exit

it suceeds:

starting script test::test3
CAPI: Contr1 0: attach script
CAPI: stepHandler 100
CAPI: Contr1 0: step fffb sleep(0)
CAPI: setTimer 36
CAPI: postEvent 403
CAPI: stepHandler 403
ALERT_CONF ID=003 #0x0004 LEN=0014
  Controller/PLCI/NCCI            = 0x0
  Info                            = 0x2002
CAPI: Contr1 0: step fffb debug(***, test3/0)
CAPI: Contr1 0: *** test3/0
CAPI: setTimer 36
CAPI: Contr1 0: step 3 sleep(0)
CAPI: setTimer 36
CAPI: Contr1 0: step fffb sleep(2)
CAPI: TrunkStep
CAPI: stepHandler 303
CAPI: sleepHandler 100
CAPI: Contr1 0: sleep
CAPI: setTimer 2000
CAPI: postEvent 506
debug: *** test trap successful


Next, if I start bayonne --test tams, I get a "failed recording:

CAPI: setTimer 4294967295
CAPI: CapiTone
CAPI: Contr1 0: step 7 record(tams/,%session.startdate%session.starttime)
CAPI: TrunkStep
CAPI: stepHandler 303
CAPI: recordHandler 100
CAPI: Contr1 0: record
CAPI: CapiRecord
CAPI: Initial tams/
CAPI: setTimer 60000
CAPI: Run
CAPI: Contr1 0: failed recording
CAPI: postEvent 105
CAPI: recordHandler 105
CAPI: stepHandler 100
CAPI: Contr1 0: reset
CAPI: Stop

I'm using .al-files because .au was too slow.

I have a running capi-application, a call recorder like tams, which is
working,
but I'm also not sure if capi is error-free at all on this server.

How ever, does someone has an hint were these errors are located?

Thanks

Michael