asterisk users - Apr 2005 - Zaptel and Boostringer

Hi All,

For some time now I've had issues with ringing voltages on my TDM400P.
Numerous folks have told me that using "modprobe wcfxs boostringer=1" 
when loading the module will force the driver to use boosted ring voltage. For
some strange reason this has never worked for me. Today I got creative...
another way to do it is to edit wcfxs.c (in the zaptel CVS) and find the
following block of declarations:

static int debug = 0;
static int robust = 0;
static int timingonly = 0;
static int lowpower = 0;
static int boostringer = 0;
static int _opermode = 0;
static char *opermode = "FCC";
static int fxshonormode = 0;

set boostringer=1 instead of 0 and recompile Zaptel. The FXS ports will be
forced to generate 89V ring signals from now on.

Now if I can just stop the FXO ports from dropping calls....

Thanks,

Ian

Ian Pattison, Senior Analyst
Technology Associates Inc.
Tel: 905-459-2100 ext. 204
Mobile: 416-568-6548
E-mail: ianp@technologyassociates.ca 
WWW: http://www.technologyassociates.ca

-------------- next part --------------
BEGIN:VCARD
VERSION:2.1
FN:Ian Pattison
EMAIL;WORK;PREF:ianp@technologyassociates.ca
TEL;WORK:416-657-2464 ext. 204
N:Pattison;Ian
TITLE:Senior Analyst
ADR;INTL;WORK;PARCEL;POSTAL:;;9052 Creditview Rd.;Brampton;Ontario;L6V
1A1;Canada
LABEL;INTL;WORK;PARCEL;POSTAL;ENCODING=QUOTED-PRINTABLE:Ian Pattison=0A9052
Creditview Rd.=0ABrampton, Ontario  L6V 1A1=0ACanada
LABEL;DOM;WORK;PARCEL;POSTAL;ENCODING=QUOTED-PRINTABLE:Ian Pattison=0A9052
Creditview Rd.=0ABrampton, Ontario  L6V 1A1
TEL;CELL:416-568-6548
TEL;PREF:416-657-2464 ext. 204
TEL;WORK:905-459-2100 ext. 204
ORG:Technology Associates Inc.
END:VCARD

On April 30, 2005 02:56 pm, Ian Pattison wrote:
> For some time now I've had issues with ringing voltages on my TDM400P.
> Numerous folks have told me that using "modprobe wcfxs
boostringer=1"  when
> loading the module will force the driver to use boosted ring voltage. For
> some strange reason this has never worked for me. Today I got creative...
> another way to do it is to edit wcfxs.c (in the zaptel CVS) and find the
> following block of declarations:
It would do you well to figure out WHY your system is not passing parameters 
properly; 'boostringer=1' is supposed to set that boostringer variable. 
The
fact that it isn't indicates a deeper seated problem with your kernel, 
modprobe, or your distribution.

-A.