Hey all - we have two TDM400P cards in an SMP Redhat9 box, with 4 FXO ports each running thel latest Asterisk CVS. Users connect to this to share POTS lines using analog phones connected to Sipura SPA-2000 boxes. All works reasonably well, except every day (or more) a line will get "locked up". No other way to describe it really -- the line just stops working, so if someone tries to dial out, and they happen to get assigned that port, all they hear is silence. The only way to unlock the port is to stop asterisk, and unload and reload the zaptel drivers (service zaptel restart), and then restart asterisk. I've seen other posts on the list referring to similar (same?) issues, but no resolutions. I have been staying current with the CVS version biweekly in hopes the problem will get resolved at some point. I have contacted Digium support (via email) about the issue. Has anyone made any headway with this problem? Thanks, Al -- Alok K. Dhir <adhir@symplicity.com> Symplicity Corporation http://solutions.symplicity.com 703 351 6987 (w) | 703 351-6357 (f)
> I've seen other posts on the list referring to similar (same?) issues, > but no resolutions. I have been staying current with the CVS version > biweekly in hopes the problem will get resolved at some point. I have > contacted Digium support (via email) about the issue. > > Has anyone made any headway with this problem? >Al, I had similar issues with my TDM400P (loaded with 4 FXO, or TDM04B as configured). I tried switching modules around on the board, upgrading CVS, etc....nothing helped. Ultimately Digium told me that it was a hardware problem in the board revision that I had. They had me email them the serial numbers from the board and each FXO module - it was determined that I needed a new board. The new board that they sent me has a jumper wire connected between two points on the backside of the card. (That's how I know the new card is somehow different from the old). I installed the new card into my customers * box almost 3 weeks ago - so far everything has been working great with no problems reported. Marty
On Wed, Aug 25, 2004 at 10:08:19AM -0400, Alok K. Dhir wrote:> Hey all - we have two TDM400P cards in an SMP Redhat9 box, with 4 FXO > ports each running thel latest Asterisk CVS. > > Users connect to this to share POTS lines using analog phones connected > to Sipura SPA-2000 boxes. All works reasonably well, except every day > (or more) a line will get "locked up". No other way to describe it > really -- the line just stops working, so if someone tries to dial out, > and they happen to get assigned that port, all they hear is silence. > > The only way to unlock the port is to stop asterisk, and unload and > reload the zaptel drivers (service zaptel restart), and then restart > asterisk.I wish I could do this. The times I've had ports lockup I was able to unload the drivers, but I would get complaints on reload, so I had to restart the computer. That *really* aggitates me.> I've seen other posts on the list referring to similar (same?) issues, > but no resolutions. I have been staying current with the CVS version > biweekly in hopes the problem will get resolved at some point. I have > contacted Digium support (via email) about the issue. > > Has anyone made any headway with this problem?-- -M There are 10 kinds of people in this world: Those who can count in binary and those who cannot.
> Well, I had the TDM act strange this afternoon and spontaneously dropthe> line. And as I expected, it locked up this evening. It seems to have > hung > the machine. > > This system has not gone more than 4 days without a soft boot since Iput> the > TDM400 into it. I've had it for 3.5 years and I'd never have toreboot> it. > I'd have *months* of uptime. > > I think there's something wrong with this card. I can't imagineanyone> tolerating every-other-day reboots with a TDM card... >I thought I would repost this info, since it seems relevant to this thread and may have been missed before this thread started... I too have had problems with the TDM400P (TDM04B as configured) - symptoms ranging from one of the ports not being answered (no indication of an incoming call on the CLI), to calls dropping and outbound callers dialing and getting dead air. Sometimes a unload/load of the modules was sufficient to get things working again, other times a full reboot was required. Ultimately it was determined to be a design bug in the either the TDM400P itself or the FXO modules plugged into it. Digium acknowledged that it was known issue and sent me a replacement card and modules. The card had been modified, evident from the jumper wire that been soldered between two points on the back of the card. I haven't had problems since installing the new card. I would recommend contacting Digium support and sending them the serial numbers from the card and modules... Here's my original post for reference: http://lists.digium.com/pipermail/asterisk-users/2004-August/060008.html Marty
Michael George wrote:> To follow up on this, I heard back from Digium and they asked the > configuration of my TDM. It was: FXO,FXS,FXS,FXS. They said they have had > report of this configuration being a problem and that I should change it to > FXS,FXS,FXS,FXO. > > Before the change the system would either hang or lock up a port within 3 > days. After the change I have over 10 days of uptime again. > > Thanks, Digium!!Interesting. I am waiting to hear from Digium with similar issues, on two cards, one with 4 x FXO and one with 2 x FXO. Regrads, Richard
On Thu, Sep 09, 2004 at 07:53:22PM +1200, Richard Scobie wrote:> > > Michael George wrote: > > >To follow up on this, I heard back from Digium and they asked the > >configuration of my TDM. It was: FXO,FXS,FXS,FXS. They said they have > >had > >report of this configuration being a problem and that I should change it > >to > >FXS,FXS,FXS,FXO. > > > >Before the change the system would either hang or lock up a port within 3 > >days. After the change I have over 10 days of uptime again. > > > >Thanks, Digium!! > > Interesting. I am waiting to hear from Digium with similar issues, on > two cards, one with 4 x FXO and one with 2 x FXO.Are the FXOs on the 2x on ports 1-2 or 3-4? Maybe it has to do with *any* FXO on port 1... Please get back with the list with your findings. -- -M There are 10 kinds of people in this world: Those who can count in binary and those who cannot.
I just downloaded it now off the CVS and it will no longer compile
> > Are the FXOs on the 2x on ports 1-2 or 3-4? Maybe it has to > do with *any* FXO on port 1... > > Please get back with the list with your findings. >My experience led to a replacement from Digium, but the card is a TDM400P with 4 FXO...now that I think of it, during troubleshooting there was some correlation to the first port on the card (port 1)...not the first module - I swapped module positions to varying locations on the card without success, but then again they are all FXO...Maybe *is* possible that the TDM400P doesn't like an FXO module in port 1 as you are suggesting...Like I said, in the end I got a new revision board from digium, all 4 ports are still FXO and working great now... Marty