capisuite with CIPvalue 17 result in undeliverable faxes

Bug #150688 reported by NotTheEvilOne
2
Affects Status Importance Assigned to Milestone
capisuite (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: capisuite

The standard seems to be problematic in the way of configurating "CIPvalue" or the machine type correctly. At least here many machines seem to be misconfigured. They identify themselves as CIPvalue 4.

Please have a look at the following discussion (in German) for slightly more information:
http://osdir.com/ml/linux.suse.isdn/2006-08/msg00024.html

The following patch will resolv this issue.

diff -r -u -b -B src.orig/backend/connection.cpp src/backend/connection.cpp
--- src.orig/backend/connection.cpp 2003-07-20 14:08:44.000000000 -0500
+++ src/backend/connection.cpp 2004-11-12 20:35:22.035045216 -0600
@@ -85,7 +85,7 @@
                                CIPvalue=16;
                        break;
                        case FAXG3:
- CIPvalue=17;
+ CIPvalue=4;
                        break;
                        default:
                                throw CapiExternalError("unsupported service given","Connection::Connection()");

Tags: patch
Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 RC or later?

Changed in capisuite:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in capisuite:
status: Incomplete → Invalid
Revision history for this message
NotTheEvilOne (ntoe) wrote :

As long as this patch mentioned in the description is not applied this bug is valid for each new release of *Ubuntu. I just checked "capisuite_0.4.5.orig.tar.gz" and "capisuite_0.4.5-8ubuntu3.diff.gz" and can confirm that the bug is still in Ubuntu Jaunty ...

Changed in capisuite (Ubuntu):
status: Invalid → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.