[asterisk-bugs] [JIRA] (DAHLIN-218) [patch] a driver for single-port FXO cards based on Si3052 chip + Si3011/17/18 DAA (Motorola 52-6116-2A, PM560MS etc.)

Keith Morgan (JIRA) noreply at issues.asterisk.org
Fri May 31 09:32:50 CDT 2019


     [ https://issues.asterisk.org/jira/browse/DAHLIN-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Keith Morgan closed DAHLIN-218.
-------------------------------

    Resolution: Won't Fix

> [patch] a driver for single-port FXO cards based on Si3052 chip + Si3011/17/18 DAA (Motorola 52-6116-2A, PM560MS etc.)
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: DAHLIN-218
>                 URL: https://issues.asterisk.org/jira/browse/DAHLIN-218
>             Project: DAHDI-Linux
>          Issue Type: New Feature
>          Components: NewFeature
>    Affects Versions: 2.4.0
>            Reporter: Maciej Szmigiero
>         Attachments: dahdi_fxo_modes_si3052.patch, dahdi-gencfg.patch, fxo_si3052.c, fxo_si3052.h
>
>
> Attached here is a driver for single-port FXO cards based on Si3052 chip + Si3011/17/18 DAA. They are marketed as Motorola 52-6116-2A, PM560MS and many others.
> Driver is written from scratch to take advantage of international features some of the DAAs have. There is also patch for wcfxo module to support these cards circulating on Net, but it runs the card in backwards-compatible mode and doesn't allow most of the POTS settings to be tweaked. 
> Tested features:
> * Sending and receiving voice,
> * Ringer detection and validation,
> * DTMF detection,
> * Caller ID reception (only ETSI FSK mode tested, but different ones should work too in principle),
> * ULAW/ALAW mode,
> * Busy pattern hangup detecion,
> * Line disconnection detection (only when offhook due to hardware limitation).
> Usage:
> * Put fxo_si3052.c and fxo_si3052.h files in drivers/dahdi directory of dahdi-linux package,
> * Add "obj-$(DAHDI_BUILD_ALL)$(CONFIG_DAHDI_WCFXO) += fxo_si3052.o" line (without quotes) to Kbuild file in the same directory (drivers/dahdi) near the top of the file.
> * Patch fxo_modes.h file in the same directory with dahdi_fxo_modes_si3052.patch (command: "patch -p0 <dahdi_fxo_modes_si3052.patch" w/o quotes).
> * Compile and install dahdi-linux package as usual.
> * Patch dahdi-tool package with dahdi-gencfg.patch (command: "patch -p0 <dahdi-gencfg.patch" w/o quotes).
> * Compile and install dahdi-tools package as usual.
> * Load required modules (including fxo_si3052). For fxo_si3052 you have to set the region name to one of those listed in fxo_modes.h file (this file is also used for wctdm driver, so region names are the same). For example: "modprobe fxo_si3052 region_param=ARGENTINA" (w/o quotes) would load the module with proper settings for Argentina. Also add "use_ulaw=1" if you plan to use ULAW instead of ALAW (default).
> * Generate config file for the card with dahdi_genconf, configure with dahdi_cfg, write config files for Asterisk, all just like with the wcfxo driver.
> If CallerID detection doesn't work the problem might be with too long minimum ringer time. Default is 512ms, but sometimes first ring signal is shorter and is not detected as ring, so CallerID detection is not started by Asterisk. In this case check ringer length and add appropriate "min_ringer_time" parameter (for example "min_ringer_time=150" for 150ms). Valid values are 100, 150, 200, 256, 384, 512 and 1024 ms.
>  
> Comments and suggestions are welcome.
> U
> ****** ADDITIONAL INFORMATION ******
> mhej opened a review request for this one. For further discussion see:
> https://reviewboard.asterisk.org/r/977/



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list