 Relationships |
|
| Anonymous | Login | Signup for a new account | 2010-02-27 10:40 CET |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | |||||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| 0000098 | [CapiSuite] core | major | always | 2004-10-14 20:17 | 2005-02-18 12:31 | |||||||
| Reporter | guest | View Status | public | |||||||||
| Assigned To | gernot | |||||||||||
| Priority | normal | Resolution | reopened | |||||||||
| Status | feedback | Product Version | ||||||||||
| Summary | 0000098: Receiving faxes send by tobit software doesn´t work | |||||||||||
| Description |
Fax sent by Tobit Software can´t be received: the call dropped with 0x3490,0x3314. The Tobis server says that no fax machine is present on the other side. We tried to use a voice number (the reconnect in fax mode works, but receive failes) or a fax number, always the same result. Configuration: SuSe 9.0 with kernel 2.4, avm fritz-card PCI. Sending faxes to Tobis software works fine, capisuite 0.44 (I don´t tried out 0.5 because there are many open bugs, so it seems to be unstable). Thanks Erik Kerger (erik@kedo.com) |
|||||||||||
| Additional Information |
Entry in capisuite.log: Tue Sep 14 12:56:51 2004 Connection 0x826b2c0: Connection object created for incoming call PLCI 101 from 004191950390 to 76 CIP 0x4 Tue Sep 14 12:56:51 2004 Connection 0x826b2c0: call from 004191950390 to 76 for soja connecting with fax Tue Sep 14 12:56:55 2004 Connection 0x826b2c0: accepting with service 1 Tue Sep 14 12:57:34 2004 Connection 0x826b2c0: connection lost with cause 0x3490,0x3314 Tue Sep 14 12:57:34 2004 Connection 0x826b2c0: Connection object deleted |
|||||||||||
| Attached Files | ||||||||||||
|
|
||||||||||||
|
Relationships |
|
|
Notes |
|
|
(0000201) gernot 2004-10-29 23:27 |
I don't believe that this has anything to do with the Tobit fax software on top of the machine. Instead, I think, this is a problem with one of the CAPI drivers - either of the sending or the receiving side. Updating CapiSuite to 0.5 will definitely not help as this is a low level problem of the fax transfer itself, so I would expect that this can only be fixed by updating drivers. Did you try to update the CAPI drivers of either the client and/or the server? Is it possible that there's a resource conflict (e.g. shared IRQ) in one machine? |
|
(0000233) gernot 2005-01-29 16:27 |
No feedback in > 1 month. Closing bug. If this issue is still valid and you're still interested in a fix, please either ask your questions on the mailing list or reopen the bug. Thanks. |
|
(0000235) guest 2005-02-18 12:31 [ Edit ][ Delete ] |
The avm capi driver (delivered with SuSE 9.0 / kernel 2.4) was used, and there is no update from avm available. I just tested sending a fax from a new machine (SuSE 9.2 / Kernel 2.6, avm driver too), and I got the same errors as I´ve got with tobit. So You are right, it depends on the capi driver. A solution would be to force the dariver to fall back to older fax modes in this case, but I don´t know if it is possible with capi drivers. If not, please close this issue. Thanks. |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2004-10-14 20:17 | guest | New Issue | |
| 2004-10-29 23:24 | gernot | Status | new => assigned |
| 2004-10-29 23:24 | gernot | Assigned To | => gernot |
| 2004-10-29 23:27 | gernot | Note Added: 0000201 | |
| 2004-10-29 23:30 | gernot | Status | assigned => feedback |
| 2005-01-29 16:27 | gernot | Status | feedback => resolved |
| 2005-01-29 16:27 | gernot | Resolution | open => unable to duplicate |
| 2005-01-29 16:27 | gernot | Note Added: 0000233 | |
| 2005-01-29 16:28 | gernot | Status | resolved => closed |
| 2005-02-18 12:31 | guest | Status | closed => feedback |
| 2005-02-18 12:31 | guest | Resolution | unable to duplicate => reopened |
| 2005-02-18 12:31 | guest | Note Added: 0000235 | |
