On 29 Mar 2010, at 08:13, Tzafrir Cohen wrote:
> On Sun, Mar 28, 2010 at 09:16:48PM -0500, Tim Panton wrote:
>>
>> On 28 Mar 2010, at 10:13, Tzafrir Cohen wrote:
>>
>>> On Sat, Mar 27, 2010 at 04:48:41PM -0500, Tim Panton wrote:
I'm having trouble getting a xorcom set up.
A larg
On Sun, Mar 28, 2010 at 09:16:48PM -0500, Tim Panton wrote:
>
> On 28 Mar 2010, at 10:13, Tzafrir Cohen wrote:
>
> > On Sat, Mar 27, 2010 at 04:48:41PM -0500, Tim Panton wrote:
> >> I'm having trouble getting a xorcom set up.
> >>
> >> A large part of the problem is that the box is a _long_ way
This is what I get on my unit but my is working:
dahdi_hardware -v
Failed running '/usr/sbin/astribank_tool': at
/usr/lib/perl5/site_perl/5.8.8/Dahdi/Xpp/Mpp.pm line 181.
usb:001/003 xpp_usb+ e4e4:1162 Astribank-modular FPGA-firmware
LABEL=[usb:X1036340] connect...@usb-:0
On 28 Mar 2010, at 10:13, Tzafrir Cohen wrote:
> On Sat, Mar 27, 2010 at 04:48:41PM -0500, Tim Panton wrote:
>> I'm having trouble getting a xorcom set up.
>>
>> A large part of the problem is that the box is a _long_ way away and
>> I can't get to/at it easily, so while I could probably fix th
I've never seen e4e4:1164 before.
What does this output?:
lsusb|sed -e 's/:/ /g'| grep e4e4| awk '{print "astribank_tool -n -D
/proc/bus/usb/"$2"/"$4}'| bash
reset the astribank:
#(if you use freepbx)
amportal stop
#(if you start asterisk that way)
/etc/init.d/asterisk stop
/etc/init.d/dahdi stop
On Sat, Mar 27, 2010 at 04:48:41PM -0500, Tim Panton wrote:
> I'm having trouble getting a xorcom set up.
>
> A large part of the problem is that the box is a _long_ way away and
> I can't get to/at it easily, so while I could probably fix this in a few
> hours if the machine were in front of me,
On 27 Mar 2010, at 21:48, JD Austin wrote:
> Xorcom hardware uses three layers; you must resolve issues in the
> following order:
>
> 1. USB
> 2. Dahdi
> 3. Asterisk
>
> I suspect you're having trouble with the usb layer.
> Run lsusb
> It will display a line like this if the firmware isn
Xorcom hardware uses three layers; you must resolve issues in the
following order:
1. USB
2. Dahdi
3. Asterisk
I suspect you're having trouble with the usb layer.
Run lsusb
It will display a line like this if the firmware isn't loaded:
Bus 001 Device 004: ID e4e4:1161
If it is e4e4:1162
I'm having trouble getting a xorcom set up.
A large part of the problem is that the box is a _long_ way away and
I can't get to/at it easily, so while I could probably fix this in a few
hours if the machine were in front of me, I'm struggling over a slow
unreliable laggy link.
Ok, enough whinin
