[Asterisk-Users] TE410P not working

2005-09-30 Thread Simone Cittadini
I'm trying to install a TE410P this is what happens with compiled zaptel 1.0.9, 1.2-beta and 1.0.9 from http://updates.xorcom.com/iso/ this is my zaptel.conf (checked with the provider the values): span=1,1,0,ccs,hdb3,crc4 bchan=1-15,17-31 dchan=16 loadzone=it defaultzone=it then I modprobe

Re: [Asterisk-Users] te410p not working after cvs-head update

2005-06-06 Thread Asterisk
Hmm, I did a cvs co -D 04/30/05 zaptel, and this version works fine - the TE410P comes up no problems. Seems to be the same issue as the #4155 bug. Julian. Asterisk wrote: Thanks Kevin, but I have done all you suggested. There is a closed bug on the bug tracking system (#4155) which seems

[Asterisk-Users] te410p not working after cvs-head update

2005-06-05 Thread Asterisk
I have a TE410P running on CentOS 4 which (fortunately) is my test system. This card has been working flawlessly for the past few weeks. Today I did a cvs update to the latest head files, and the card is now not working. When I try a zaptel start, a series of messages appears on the console:

RE: [Asterisk-Users] te410p not working after cvs-head update

2005-06-05 Thread Kevin Bockman
From: Asterisk I have a TE410P running on CentOS 4 which (fortunately) is my test system. This card has been working flawlessly for the past few weeks. Today I did a cvs update to the latest head files, and the card is now not working. When I try a zaptel start, a series of messages

Re: [Asterisk-Users] te410p not working after cvs-head update

2005-06-05 Thread Asterisk
When I posted, I meant to say that I updated to CVS-HEAD on all parts of * (asterisk, libpri,zaptel etc). Julian. Asterisk wrote: I have a TE410P running on CentOS 4 which (fortunately) is my test system. This card has been working flawlessly for the past few weeks. Today I did a cvs update

Re: [Asterisk-Users] te410p not working after cvs-head update

2005-06-05 Thread Asterisk
Thanks Kevin, but I have done all you suggested. There is a closed bug on the bug tracking system (#4155) which seems to suggest a problem with 1st gen cards and the 2nd gen driver. Looks as if I need to speak to tech support (again - the te410P was a bugger to get going in a HP proliant