[asterisk-bugs] [JIRA] (DAHLIN-350) x100p se Card not supported in current version of Dahdi

[Malcolm Davenport (JIRA)]

    [ https://issues.asterisk.org/jira/browse/DAHLIN-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=230524#comment-230524 ] 

Malcolm Davenport commented on DAHLIN-350:
------------------------------------------

We can't, sorry.  We're not familiar with those products.  And, because of their provenance - entities that do not participate in any way in the development or maintenance of DAHDI - we're going to steer clear.

> x100p se Card not supported in current version of Dahdi
> -------------------------------------------------------
>
>                 Key: DAHLIN-350
>                 URL: https://issues.asterisk.org/jira/browse/DAHLIN-350
>             Project: DAHDI-Linux
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 2.5.0.2
>         Environment: Linux Ubuntu Server 14.04 LTS
>            Reporter: Jonah
>            Assignee: Wendell Thompson
>
> I am unable to get the x100p se card to work with Asterisk and Dahdi on Ubuntu Server 14.04LTS.
> The card is from www.x100p.com, where the website claims to that the card is "The Only Authentic X100P FXO PCI for DigiumTM Asterisk available Today!"
> I realise that is their claim and not yours, but I only quote it as it gives an impression this card should or did work recently?
> In terms of diagnosis I had a lot of help from linux4life on the Asterisk IRC channel who reported to me that this card is not supported.
> He was kind enough to put an email together for me to send on to the card vendor:
> "Hello,
> I worked with Jonah attempting to get this card working. apparently there is a problem with this card and it's compatibility with the latest version of DAHDI. dahdi_hardware can see the card as well as lspci. However, when the dahdi module wcfxo attempts to initialize the card there are numerous errors reported regarding the DAA. Jonah can provide you with a copy of the errors reported by dmesg.
> [761493.393498] FXO PCI Master abort
> [761493.393508] FXO PCI Master abort
> [761493.393517] FXO PCI Master abort
> [761493.393526] FXO PCI Master abort
> [761493.393536] FXO PCI Master abort
> [761493.393545] FXO PCI Master abort
> [761493.393554] FXO PCI Master abort
> [761493.393564] FXO PCI Master abort
> [761493.393573] FXO PCI Master abort
> [761493.393583] FXO PCI Master abort
> [761493.393592] FXO PCI Master abort
> [761493.393601] FXO PCI Master abort
> [761493.393611] FXO PCI Master abort
> [761493.393620] FXO PCI Master abort
> [761493.393630] FXO PCI Master abort
> [761493.393639] FXO PCI Master abort
> [761493.393648] FXO PCI Master abort
> [761493.393658] FXO PCI Master abort
> [761493.393667] FXO PCI Master abort
> [761493.393673] NOTICE-wcfxo: WCFXO/0: Unknown DAA chip revision: REVB=0
> [761493.393675] Failed to initailize DAA, giving up...
> [761493.393676] FXO PCI Master abort
> [761493.393686] FXO PCI Master abort
> [761493.393861] wcfxo: probe of 0000:04:00.0 failed with error -5
> [761493.401507] dahdi_dummy: Trying to load High Resolution Timer
> [761493.401509] dahdi_dummy: Initialized High Resolution Timer
> [761493.401510] dahdi_dummy: Starting High Resolution Timer
> [761493.401511] dahdi_dummy: High Resolution Timer started, good to go
> If you have any questions related to my efforts, please feel free to contact me via email: gmalsack at gmail.com
> "



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