[asterisk-bugs] [DAHDI-linux 0014261]: [patch] Generate VMWI neon pulses from FXS module to light NEON lamp on newer 'non intellegent phone'

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14261 
====================================================================== 
Reported By:                alecdavis
Assigned To:                dbailey
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   14261
Category:                   wctdm
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             2009-01-16 15:03 CST
Last Modified:              2009-01-26 03:52 CST
====================================================================== 
Summary:                    [patch] Generate VMWI neon pulses from FXS module to
light NEON lamp on newer 'non intellegent phone'
Description: 
Add Message Waiting Indicator method to light NEON lamp on low cost phones
with integrated Neon Lamp

Using /etc/dahdi/chan_dahdi.conf keyword mwisendtype=hvac

====================================================================== 

---------------------------------------------------------------------- 
 (0098724) alecdavis (reporter) - 2009-01-26 03:52
 http://bugs.digium.com/view.php?id=14261#c98724 
---------------------------------------------------------------------- 
please remove wctdm_neon_support.diff.txt and wctdm_neon_support.diff2.txt

wctdm.c_neon_support.diff3.txt changes the normal linefeed polarity to
reversed if 'neon' is enabled, as 'neon' generation requires linefeed to be
Forward Active before setting reqisters.

This allows mwisendtype of 'lrev' and 'neon', the LED on the phone with
only LineReversal is modulated if 'neon' is enabled. 

The POLARITY macro now has another term to XOR.

Further consideration required below:

I wonder should there be a user configurable channel parameter
'reversepolarity' to operate the FXS line in reverse linefeed, as does the
global module parameter 'reversepolarity'. The internal variable name would
perhaps be 'fxs.user_reversepolarity'. We cannot just use
'fxs.reversepolarity' as this is intended later to be used for 'Line
Reversal Alert Signal' type application.

Then if the user configured (in chan_dahdi.conf) 'reversepolarity=yes' or
'mwisendtype=neon' the new internal channel variable
'fxs.user_reversepolarity' would be set, thus operating the linefeed in
reverse, unless a message is waiting.

Taking 'user_reversepolarity' even further, for installation ease,
consider the case when 'neon' may be configured at a later stage for a 2nd
phone, 'lrev' should also set 'user_reversepolarity', that way no switches
need to be changed on the customers phones, (some are dip switches, and
hard to get at!). 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-26 03:52 alecdavis      Note Added: 0098724                          
======================================================================