0000006: More info about fax/voice msg - Mantis BugTracker for CapiSuite

Notes
(0000004) gernot 2003-03-23 12:28	Let's see: o the # of pages for faxes -> missing in CapiSuite core, but will be implemented o length in sec of a voice msg -> already available as return value of audio_receive, but not used in default scripts. Will add this soon, too. o add hostname in front of <a href="file://<prefix>/var/spool">file://<prefix>/var/spool</a>... 'cause when mail are send it other hosts it's most likely that the file:// in not valid on the remote host -> Just looked this up in RFC 1738. This is indeed allowed, but I don't see the sense in this. How should a file be accessed when you don't know a protocol to do so? But more important: are you sure most MUAs will handle this correctly when <prefix> is the localhost?

(0000005) ach 2003-03-23 12:32	[...] o add hostname in front of <a href="file://<prefix>/var/spool">file://<prefix>/var/spool</a>... 'cause when mail are send it other hosts it's most likely that the file:// in not valid on the remote host -> Just looked this up in RFC 1738. This is indeed allowed, but I don't see the sense in this. How should a file be accessed when you don't know a protocol to do so? But more important: are you sure most MUAs will handle this correctly when <prefix> is the localhost? [...] Sorry for the confusion. <prefix> is the one you specify during configure run. I meant something like 'It was moved to '<hostname>' to file:<prefix>/var/...' I intentionaly avoid the file://host/path construct because I also have no idea how such an URL should be handled. Achim

(0000038) gernot 2003-06-22 23:31	Thomas Niesel also wants following infos in messages: - fax resolution - number of pages - duration of transfer

(0000039) ach 2003-06-23 15:59	Okay let's add this too: Addressee Subject/Comment Would help quite a lot when searching later for send/received facsimile.

(0000041) gernot 2003-06-26 13:55	Last addition of ach (2003-06-23 15:59) implemented in CVS

(0000043) gernot 2003-07-06 13:44	The rest will have to wait until CapiSuite 0.5, because the current exception handling scheme in the Python scripts doesn't give me the ability to implement it. Think about the following code fragment in incoming.py: faxInfo=capisuite.fax_receive(blabla, ...) faxText="Pages: "+str(faxInfo[0])+... The problem is that a fax reception is running endlessly until the connection is dropped. There's no way to do this in other ways because the only way for the CAPI driver to tell me the end of the reception is to issue a DISCONNECT_B3_IND message which means the fax connection is finished. So, a CallGoneError exception will be thrown at the end of each fax receive. That means that a fax_receive() command can never finish and a return value can never be passed. My idea is to change all script commands to only throw an exception when the call is gone at the beginning of the execution of this command. This is also more sensible as this is really an error while a connection loss after a fax receive is no error case normally. But as this implies some deeper thoughts about side effects and changes the Python script semantics a little bit, I'll keep this for the next "bigger" release...

(0000082) gernot 2003-12-31 16:06	Well, took some time, but now the change is finally done and it seems to work now (took me quite some weaks to find a SIGABRT I introduced with the structural change :-( ). As far as I can see, all wished features should be implemented now in CVS. Would be nice to hear your feedback. BTW: "Guadn Rutsch!" ;-)

Issue History
Date Modified	Username	Field	Change

Relationships