Mantis BugTracker for CapiSuite
  

Viewing Issue Simple Details Jump to Notes ] View Advanced ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0000044 [CapiSuite] core crash always 2003-08-05 19:34 2003-08-17 22:12
Reporter arweb View Status public  
Assigned To gernot
Priority urgent Resolution open  
Status assigned   Product Version
Summary 0000044: Segmentation fault on capisuite_call_voice and capisuite_call_faxG3
Description I have setup a script like the following:
------ START ------
import capisuite
def callIncoming(call, service, call_from, call_to):
answer(call, 0)
capisuite.call_voice(call, 0, myMSN, hisMSN, 15)
------ STOP ------

Answering the call works problem-free...i can do any event but calling someone else, because this leads to an immediate segmentation fault without any capisuite log message!

What may the problem be? What "controller (int) ISDN controller ID to use" value should i use (what rules does that value follow)?

Any help appreciated - thanks in advance!
Additional Information
Attached Files

- Relationships

- Notes
(0000051)
gernot
2003-08-10 14:04

Well, there 2 errors in your script:

- You have to pass "capi", not a call reference as first paramter to capisuite.call_voice(). This should be the reason for the segv. See http://www.capisuite.de/capisuite/reference/group__python.html [^]#a10

- 0 is no valid controller id. Controller numbering starts at "1". Just added this information to the function description in CVS.

Regarding the SEGV, I'm not sure if I can do something to prevent this. I'll think about this...
 
(0000054)
arweb
2003-08-13 12:01

First of all thanks for your reply, but there is still a question remaining concerning this capi reference:
* What is the concrete value or variable to pass as "capi reference"?
  You named the string "capi", which did, like i expected, not work.
  Error Message: "First parameter must be the capi reference."
 
(0000056)
gernot
2003-08-17 22:12

The problem is, you don't have this capi parameter (I meant no string, but a variable - have a look in idle.py) in incoming.py currently :-((

So there's currently no way to do this in 0.4.3. But I'll try to do this quite soon - I'll put it to my TODO for 0.5
 

- Issue History
Date Modified Username Field Change


Mantis 0.19.2
Copyright © 2000 - 2004 Mantis Group
130 total queries executed.
22 unique queries executed.