Summary:	ASTERISK-00355: Digium cards lock up when using dialing out over sip
Reporter:	paluszak (paluszak)	Labels:
Date Opened:	2003-10-04 18:37:57	Date Closed:	2004-09-25 02:46:18
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	I have a TDM40B card with four FXS interfaces.  I have set up iconnecthere so that I can place a call using the SIP connection over the internet from my handset connected to the FXS port of the TDM40P.  When I place a call I get a few seconds into the call and then the conversation goes dead.  What is worse is that all four ports on the TDM card go dead.  I have to reboot the server to get them back working. In August I had this working.  I put any VOIP work aside for a few weeks and mostly placed calls over the X100P.  I wanted to get QOS working on my linux firewall before I went tried to use sip again.  Since it was last working, I made the following changes: -- updated the linux kernel from 2.4.20-8 to 2.4.20-20 -- installed a Grandstream phone -- installed the latest CVS as of 10/3/03 -- installed and configured QOS on the firewall (works great) This problem does not occur if I use my iax connection to iaxtel. I'm hoping that someone else has already reported this.   Let me know what other tests and information would be needed help troubleshoot this problem.
Comments:	By: Brian West (bkw918) 2003-10-04 20:50:21 Sounds like bad hardware.  How did you configure QoS?  What method are you using?  Priority queuing?  RSVP?  what? By: paluszak (paluszak) 2003-10-04 21:11:04 I'm not sure how to diagnose the hardware.  Any tips would be appreciated.  Are these boards prone to failure? Re: QOS I used the HTB Linux queuing discipline (qdisc).  From their I created three classes.  The first class I reserved for VOIP traffic.  The third class I set aside very little space, but allowed it to steal unused space.  I put smtp and pop3 in their.  All the other traffic goes into the second class.  For each of these three classes I used the sfq qdisc. The IAX protocol was easy.  I just set the tos in iax.conf and added a tc filter to put that tos in the first class.  Only a few other packets get lumped in so I didn't bother trying to filter on port.  It was when I tried to configure QOS for SIP that I encountered this bug, that this posting is for.  So I wasn't able to test SIP.  For now, I only do egress filtering as that is the limiting factor on my cable modem. If you want sample commands and configs let me know and I will post it to the mailing list. By: Brian West (bkw918) 2003-10-05 01:35:18 no I know how to setup QoS... Not sure how to trouble shoot your problem.  Try the mailing list since mine works fine.... By: Mark Spencer (markster) 2003-10-05 19:52:40 Is this a Rev C or Rev E/F freshmaker? By: paluszak (paluszak) 2003-10-05 20:54:41 Syslog writes the following information messages Oct  3 22:07:14 voip kernel: PCI: Found IRQ 7 for device 01:0a.0 Oct  3 22:07:14 voip kernel: Freshmaker version: 62 Oct  3 22:07:14 voip kernel: Freshmaker passed register test Oct  3 22:07:14 voip kernel: Module 0: Installed -- AUTO Oct  3 22:07:14 voip kernel: Module 1: Installed -- AUTO Oct  3 22:07:14 voip kernel: Module 2: Installed -- AUTO Oct  3 22:07:14 voip kernel: Module 3: Installed -- AUTO Oct  3 22:07:14 voip kernel: Found a Wildcard FXS: Wildcard S400P Prototype (4 modules) Can you gleam the information you need from these messages? The first time the card locked up, I just rebooted.  The second time it happened I didn't want to reboot so I tried to remove the drivers and reload them.  The following is what I got: Oct  4 00:45:49 voip kernel: Freed a Wildcard Oct  4 00:46:44 voip kernel: Freed a Wildcard Oct  4 00:46:44 voip kernel: PCI: Found IRQ 10 for device 01:08.0 Oct  4 00:46:44 voip kernel: PCI: Sharing IRQ 10 with 00:01.0 Oct  4 00:46:44 voip kernel: wcfxo: DAA mode is 'FCC' Oct  4 00:46:44 voip kernel: Found a Wildcard FXO: Wildcard X101P Oct  4 00:46:47 voip kernel: PCI: Enabling device 01:0a.0 (0000 -> 0003) Oct  4 00:46:47 voip kernel: PCI: Found IRQ 7 for device 01:0a.0 Oct  4 00:46:47 voip kernel: Freshmaker version: ff Oct  4 00:46:47 voip kernel: 00 != ff Oct  4 00:46:47 voip kernel: 01 != ff Oct  4 00:46:47 voip kernel: 02 != ff Oct  4 00:46:47 voip kernel: 03 != ff Oct  4 00:46:47 voip kernel: 04 != ff Oct  4 00:46:47 voip kernel: 05 != ff Oct  4 00:46:47 voip kernel: 06 != ff Oct  4 00:46:47 voip kernel: 07 != ff Oct  4 00:46:47 voip kernel: 08 != ff Oct  4 00:46:47 voip kernel: 09 != ff Oct  4 00:46:47 voip kernel: 0a != ff Oct  4 00:46:47 voip kernel: 0b != ff Oct  4 00:46:47 voip kernel: 0c != ff Oct  4 00:46:47 voip kernel: 0d != ff Oct  4 00:46:47 voip kernel: 0e != ff Oct  4 00:46:47 voip kernel: 0f != ff Oct  4 00:46:47 voip kernel: 10 != ff Oct  4 00:46:47 voip kernel: 11 != ff Oct  4 00:46:47 voip kernel: 12 != ff Oct  4 00:46:47 voip kernel: 13 != ff Oct  4 00:46:47 voip kernel: 14 != ff Oct  4 00:46:47 voip kernel: 15 != ff Oct  4 00:46:47 voip kernel: 16 != ff Oct  4 00:46:47 voip kernel: 17 != ff Oct  4 00:46:47 voip kernel: 18 != ff Oct  4 00:46:47 voip kernel: 19 != ff Oct  4 00:46:47 voip kernel: 1a != ff Oct  4 00:46:47 voip kernel: 2a != ff Oct  4 00:46:47 voip kernel: 2c != ff Oct  4 00:46:47 voip kernel: 3f != ff Oct  4 00:46:47 voip kernel: 54 != ff Oct  4 00:46:47 voip kernel: 6a != ff Oct  4 00:46:47 voip kernel: 7a != ff Oct  4 00:46:47 voip kernel: 8d != ff Oct  4 00:46:47 voip kernel: a1 != ff Oct  4 00:46:47 voip kernel: b7 != ff Oct  4 00:46:47 voip kernel: c9 != ff Oct  4 00:46:47 voip kernel: db != ff Oct  4 00:46:47 voip kernel: ee != ff The interesting thing is it freed okay, but on loading it found the card but couldn't find the revision "Freshmaker version: ff". If it helps to track down the revision I purchased the card on 7/8/03. I pulled the card and on the back is the serial number CID123168. If this doesn't help let me know where to find the revision number and I will get it to you.  Thanks for your help. By: Mark Spencer (markster) 2003-10-05 23:27:45 You need to call Digium at 877-LINUX-ME and choose sales to request an RMA.  You have Rev C (the label is under the modules, but you can know just by the color of the boards -- Rev C is green, Ref E/F are blue)