I would worry that something is amuck at a much lower level than asterisk if you can't get the drivers to load on SMP kernels. I have many systems out there with A10xD boards on SMP without difficulties. You will need to specify if the machine is Intel/AMD, OS 32/64, what init options are being passed to the kernel (if any) and if the card is PCI/PCI-e. At the user level we don't care, but when it comes to debugging apparent hardware interactions the support people from Dell and Sangoma will need to know.
I once had a devil of a time getting a PRI card to work in an existing box alongside an FXO card (new client, IRQ driven card, no history, didn't build the box). It turned out they had noapic on the boot parms. I was a bit apprehensive to remove it as someone put it there for a reason, however nobody could tell me why it was there. Removing it solved the problem by allowing the advanced interrupt capabilities required. - dbc. -----Original Message----- From: Peter MacFarlane [mailto:[EMAIL PROTECTED] Sent: March-23-08 6:42 PM To: [email protected] Subject: Re: [on-asterisk] A couple of problems I don't mean to dis Sangoma. I have respect for them as well. I always prefer their products and very helpful support. It just seems odd that there was a problem with the SMP kernel. Maybe it was a CentOS problem, which would not surprise me. I should probably e-mail them and see if they have any record of the support session. I just don't want to have to bill my client for a long follow-up. Anyway, the problem has been isolated to the PRI side. I am told there are only have eight channels active right now and all calls are recorded. There is no distortion in the recordings at all which leads us to believe that it is occurring on the outgoing side of the PRI channels only. Has anyone run into to this at all? I don't really know how competent the service provider is either, but after sending all of the clients of our only local independent ISP (recently taken over) a notice indicating they had one month to transfer all of their mailboxes to the new domain, I can't say they are too bright. One has to wonder how well their T1s work as well. I will see what diagnostics I can find. Thanks, Peter M. David Cook wrote: > Peter, I have nothing but good things to say about Sangoma's level of > support and have not had a problem with SMP kernels. > > Have you contacted them before posting this? What was their response? > > I have a soft spot for these guys specifically because of the excellent > level of support they provide. Their policy is that they will get their card > working in any commercially available box. > > Disclaimer: I have no financial ties to them, but I do admit to using their > product quite extensively. > > - dbc. > > -----Original Message----- > From: Peter MacFarlane [mailto:[EMAIL PROTECTED] > Sent: March-21-08 5:20 PM > To: [email protected] > Subject: Re: [on-asterisk] A couple of problems > > Thanks. Since its a big new Dell server (don't ask), I can't imagine > there being a hardware problem. Might be a problem with the Sangoma > drivers I suppose, since the single core kernel has to be booted to get > them working. I thought Sangoma support was better than that. Guess > I'll have to keep digging around for clues, maybe on the Trixbox forum. > Wish I had installed the card. Then I might know more about what > happened there. > > Peter M. > > Drew Gibson wrote: > >> Hi Peter, >> >> glad you got the 800 issue sorted but, sorry, but I don't have much >> experience with PRI either. So I can't help much if it's something >> there. Another thing to look for would be system issues like disk IO >> (swapping, bad sector read/writes). This would show up in "top" as high >> IO WAIT (%wa) in the top part of the screen. The whole system can come >> to a halt waiting on IO. See if there is anything coincident with the >> dropouts. Can't see how that would be outbound only but it might give >> some clues. And it should help pass the time until someone who knows >> what their doing comes along! :-) >> >> good luck, >> >> regards, >> >> Drew >> >> >> Peter MacFarlane wrote: >> >>> The phones are all on the one shared network. This doesn't sound >>> like a thruput problem at all. I know what that ones sounds like by >>> transferring an ISO while my wife was trying to talk on the phone. >>> I'm thinking maybe a frequency shift problem in the PRI channel but I >>> was wondering if anyone ran into something like this before. The PRI >>> is the only thing that's really different about this installation >>> AFAIK. If there's nothing obvious to check, I will keep looking. >>> >>> The 800 number problem was resolved it the Trixbox forums. It seems >>> they were not putting the full CID on the outgoing trunks (area code >>> was missing). Apparently that is required on the PRI lines somehow. >>> Which is probably why I've never run into the problem before. >>> >>> Thanks, >>> Peter M. >>> >>> Drew Gibson wrote: >>> >>>> Hi Peter, >>>> >>>> 1. Is the network shared at any point with the computer or data >>>> network? eg computer plugged into the phone or all plugged into same >>>> switch. >>>> >>>> 2. Is it only 800 numbers? What about others, internal, local, long >>>> distance? Are the 800 numbers handled differently in the dialplan? >>>> >>>> regards, >>>> >>>> Drew >>>> >>>> >>>> >>>> Peter MacFarlane wrote: >>>> >>>>> Hi all: >>>>> >>>>> Time to turn to the Pros it seems. I haven't posted in a while so >>>>> I was wondering if you could point me in the right direction for >>>>> couple of problems. This is a server that was installed after I >>>>> was laid off so I really had no input into its configuration. >>>>> Things just moved along with a new Dell server and Sangoma TDM >>>>> card. At least they took my advice on the echo cancellation. For >>>>> the most part things are working fine (Trixbox). I'm lacking on >>>>> details right now but these are the things that are happening: >>>>> >>>>> 1. You can be talking to one of the operators and all of a sudden >>>>> their voice distorts for a few seconds, kind of like listening to a >>>>> siteband signal on HAM radio or short wave. Its there, but the >>>>> frequency is shifted higher and its undiscernable. And then it >>>>> clears up. They don't hear this at all so its outgoing only. >>>>> >>>>> 2. They can't dial 800 numbers. The digits are never right I am >>>>> told. Is this a matter of playing with the RFC and Inband settings >>>>> in sip.conf? >>>>> >>>>> Any input would be appreciated. Let me know if you need more >>>>> details. I wish I had more time to work on * servers. They are >>>>> sooooo cool. After that analog DID line conversion project I >>>>> completed, the server was abandoned because too many people were >>>>> mistaking the card generated ring tone for a fax machine and >>>>> hanging up before the call got into the queue. How's that for >>>>> stupid? People just can't handle change I guess. The ring from >>>>> the old TASCOM PBX was just as freaky. >>>>> >>>>> Peter MacFarlane >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>>> >>>>> >>>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>> >>>> >>>> >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
