[asterisk-r2] problems with digium mfcr2 and Siemens EWSD

[Moises Silva]

Laura, you need to become a hacker to try to fix this :-)

I don't want to commit such a fix to the svn tree since it has not
been tested and a more proper feature would require a new
configuration option to set the non R2 bits. This is the small change
you need to do to the source code of openr2:

Index: src/r2proto.c
===================================================================
--- src/r2proto.c	(revision 197)
+++ src/r2proto.c	(working copy)
@@ -350,8 +350,9 @@
 	/* set default standard CAS signals */
 	memcpy(r2context->cas_signals, standard_cas_signals,
sizeof(standard_cas_signals));

-	/* Default Non-R2 bit required to be on is D */
-	r2context->cas_nonr2_bits = 0x1;    /* 0001 */
+	/* Default Non-R2 bit required to be on is D , but this line has
been modified to test
+	   an issue in the asterisk-r2 mailing list to NOT set the D bit */
+	r2context->cas_nonr2_bits = 0x0;    /* 0000 */

 	/* Default R2 bits are A and B */
 	r2context->cas_r2_bits = 0xC; /*  1100 */

Basically, you just need to openr2 src/r2proto.c and search the
cas_nonr2_bits member and modify its initialization, currently is 0x1
(which means the bit D will be on) and that's why you see 1001 as the
bit pattern when Asterisk is running. It seems your PABX does not like
the bit D to be on, so we can just turn it off and see how it goes.

Please post back here results,

-- 
Moises Silva
Software Developer
Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON
L3R 9T3 Canada
t. 1 905 474 1990 x 128 | e. moy at sangoma.com