RE: [Asterisk-Users] X101P FXO with RED alarm
> (Article auto-converted from unnecessary HTML to nice plain text.) > > I ordered an X100P but when I installed the card in it sound it found a > Wild Card X101P. Whats the difference between > the 2 and is there certain considerations I have to take or certain > things to install to make sure the X101P works fine? Thanks. > I have a X101P, which I received after having ordered a X100P back in January. I don't know what the difference is (if any), but I can say that I've never had any trouble from my card. The X101P is probably just a slightly updated X100P. If you find some documentation that mentions the X100P then you should assume that they apply to the X101P as well. I have always made that assumption and haven't been proven wrong yet. -- _/ _/ _/_/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/_/_/ _/ K e v i n W a l s h _/ _/_/ _/ _/ _/_/ _/_/[EMAIL PROTECTED] _/ _/ _/_/_/_/ _/_/_/_/ _/_/ ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] X101P FXO with RED alarm
Hi, I ordered an X100P but when I installed the card in it sound it found a Wild Card X101P. Whats the difference between the 2 and is there certain considerations I have to take or certain things to install to make sure the X101P works fine? Thanks. Kevin Walsh wrote: Richard Airlie [[EMAIL PROTECTED]] wrote: On Mon, Jul 12, 2004 at 05:34:12PM +0100, Chris Stenton wrote: 1. don't run 0.5 zaptel driver with asterisk-head it will panic the kernel. 2. I am pretty sure that the current BSD zaptel driver only supports the fxs modules and the x100p card. My understanding was that the x100p and x101p were just the 'same thing', it didn't occur to me that there would be differences at driver level. That was my understanding too. I have a X101P but assumed that there were only minor board-level revisions between that and an X100P. -- Andrew Elchuk Technical Associate Cronus Technologies 248 - 111 Research Drive Saskatoon, SK S7N 2X8 Tel: (306) 652-5798 ext. 112 Fax: (306) 652-5799 Toll Free: 1-877-655-5798 http://www.cronustech.com
RE: [Asterisk-Users] X101P FXO with RED alarm
Richard Airlie [EMAIL PROTECTED] wrote: > On Mon, Jul 12, 2004 at 05:34:12PM +0100, Chris Stenton wrote: > > 1. don't run 0.5 zaptel driver with asterisk-head it will panic the > > kernel. > > 2. I am pretty sure that the current BSD zaptel driver only supports > > the fxs modules and the x100p card. > > > My understanding was that the x100p and x101p were just the 'same thing', > it didn't occur to me that there would be differences at driver level. > That was my understanding too. I have a X101P but assumed that there were only minor board-level revisions between that and an X100P. -- _/ _/ _/_/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/_/_/ _/ K e v i n W a l s h _/ _/_/ _/ _/ _/_/ _/_/[EMAIL PROTECTED] _/ _/ _/_/_/_/ _/_/_/_/ _/_/ ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] X101P FXO with RED alarm
Also, OpenBSD is more secure... my 5c Alex. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard Airlie Sent: Wednesday, 14 July 2004 9:29 AM To: [EMAIL PROTECTED] Subject: Re: [Asterisk-Users] X101P FXO with RED alarm On Mon, Jul 12, 2004 at 06:29:43PM +0100, Kevin Walsh wrote: > I don't really understand why people struggle with *BSD when > everything "just works" on GNU/Linux. I see this sort of thing all > the time, on lots of open source projects. Well, portability isn't really a bad thing. For me, I'm already using FreeBSD for other tasks, and would like to use it for telephony as well. best, Richard. ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] X101P FXO with RED alarm
On Mon, Jul 12, 2004 at 06:29:43PM +0100, Kevin Walsh wrote: > I don't really understand why people struggle with *BSD when everything > "just works" on GNU/Linux. I see this sort of thing all the time, on > lots of open source projects. Well, portability isn't really a bad thing. For me, I'm already using FreeBSD for other tasks, and would like to use it for telephony as well. best, Richard. ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] X101P FXO with RED alarm
On Mon, Jul 12, 2004 at 05:34:12PM +0100, Chris Stenton wrote: > Richard, > > 1. don't run 0.5 zaptel driver with asterisk-head it will panic the kernel. > 2. I am pretty sure that the current BSD zaptel driver only supports the fxs > modules and the x100p card. Thanks Chris. My understanding was that the x100p and x101p were just the 'same thing', it didn't occur to me that there would be differences at driver level. regards, Richard ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] X101P FXO with RED alarm
Jason Williams [EMAIL PROTECTED] wrote: > On Sun, 11 Jul 2004 23:02:56 +0100, Richard Airlie <[EMAIL PROTECTED]> wrote: > > On Sat, Jul 10, 2004 at 05:55:21PM +0100, Kevin Walsh wrote: > > > First things first. Scrap the "ports" and build from the latest > > > CVS source. 0.9 is far to old and buggy, and suspect the same of > > > the Zaptel driver you have, although I don't use *BSD myself. > > > > > I cvsup'd to the latest source yesterday and tried to build zaptel, > > but it failed right away. (trying to include linux/*.h) > > > You need to get zaptel built correctly with your kernel otherwise it > will never run correctly. > The easiest way to do that would be to dump *BSD and install GNU/Linux. I don't really understand why people struggle with *BSD when everything "just works" on GNU/Linux. I see this sort of thing all the time, on lots of open source projects. If you have lots of free time then by all means spend a large chunk of it doing battle with *BSD. If not then save yourself the effort and just install GNU/Linux. The Gentoo distro, with Linux 2.6.7, works for me. -- _/ _/ _/_/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/_/_/ _/ K e v i n W a l s h _/ _/_/ _/ _/ _/_/ _/_/[EMAIL PROTECTED] _/ _/ _/_/_/_/ _/_/_/_/ _/_/ ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] X101P FXO with RED alarm
Richard, 1. don't run 0.5 zaptel driver with asterisk-head it will panic the kernel. 2. I am pretty sure that the current BSD zaptel driver only supports the fxs modules and the x100p card. Chris - Original Message - From: "Richard Airlie" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, July 11, 2004 11:02 PM Subject: Re: [Asterisk-Users] X101P FXO with RED alarm > On Sat, Jul 10, 2004 at 05:55:21PM +0100, Kevin Walsh wrote: > > Richard Airlie [EMAIL PROTECTED] wrote: > > > First things first. Scrap the "ports" and build from the latest > > CVS source. 0.9 is far to old and buggy, and suspect the same of > > the Zaptel driver you have, although I don't use *BSD myself. > > I cvsup'd to the latest source yesterday and tried to build zaptel, > but it failed right away. (trying to include linux/*.h) > I didn't try building asterisk as it seems like the problem is with > zaptel -- i.e. I should be able to load the zaptel driver and not > see a red alarm, irrespective of my asterisk version, right?. > > > Secondly, the red alarm does tend to mean that the line is not > > connected, but I got what you're describing when I moved Asterisk to > > a new machine. Try the X100P card in a different PCI slot. That > > cleared it for me, for whatever reason. > > Thanks for that, I gave it a try but unfortunately it's made no > difference. > > I am suspecting the problem is either with the zaptel driver in > ports (which is the only version I can get to build) or i've got > a hardware issue. > > For what it's worth I can plug a phone into the back of the FXO > and get dial tone, so I guess that proves that the cabling is OK? > > best, > Richard. > ___ > Asterisk-Users mailing list > [EMAIL PROTECTED] > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users > ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] X101P FXO with RED alarm
On Sun, 11 Jul 2004 23:02:56 +0100, Richard Airlie <[EMAIL PROTECTED]> wrote: > On Sat, Jul 10, 2004 at 05:55:21PM +0100, Kevin Walsh wrote: > > Richard Airlie [EMAIL PROTECTED] wrote: > > > First things first. Scrap the "ports" and build from the latest > > CVS source. 0.9 is far to old and buggy, and suspect the same of > > the Zaptel driver you have, although I don't use *BSD myself. > > I cvsup'd to the latest source yesterday and tried to build zaptel, > but it failed right away. (trying to include linux/*.h) You need to get zaptel built correctly with your kernel otherwise it will never run correctly. Jason ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] X101P FXO with RED alarm
On Sat, Jul 10, 2004 at 05:55:21PM +0100, Kevin Walsh wrote: > Richard Airlie [EMAIL PROTECTED] wrote: > First things first. Scrap the "ports" and build from the latest > CVS source. 0.9 is far to old and buggy, and suspect the same of > the Zaptel driver you have, although I don't use *BSD myself. I cvsup'd to the latest source yesterday and tried to build zaptel, but it failed right away. (trying to include linux/*.h) I didn't try building asterisk as it seems like the problem is with zaptel -- i.e. I should be able to load the zaptel driver and not see a red alarm, irrespective of my asterisk version, right?. > Secondly, the red alarm does tend to mean that the line is not > connected, but I got what you're describing when I moved Asterisk to > a new machine. Try the X100P card in a different PCI slot. That > cleared it for me, for whatever reason. Thanks for that, I gave it a try but unfortunately it's made no difference. I am suspecting the problem is either with the zaptel driver in ports (which is the only version I can get to build) or i've got a hardware issue. For what it's worth I can plug a phone into the back of the FXO and get dial tone, so I guess that proves that the cabling is OK? best, Richard. ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] X101P FXO with RED alarm
Eric Wieling [EMAIL PROTECTED] wrote: > You may need the 3-wire (UK) to 2-wire (US) adapters for the jack the > X100P is plugged into. I've heard you can get them most anywhere. > No - steal the RJ->BT cord off the back of a modem if the X100P didn't come with a BT plug. It'll work without any adapters. Most PC shops will sell you a RJ->BT cord - or try Maplin/Tandy etc. -- _/ _/ _/_/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/_/_/ _/ K e v i n W a l s h _/ _/_/ _/ _/ _/_/ _/_/[EMAIL PROTECTED] _/ _/ _/_/_/_/ _/_/_/_/ _/_/ ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [Asterisk-Users] X101P FXO with RED alarm
Richard Airlie [EMAIL PROTECTED] wrote: > I've just added an X101P FXO card to my asterisk machine. The card is > detected ok but zttool always shows it in a RED alarm state, which I > understand means that it doesn't detect the line. > > I've connected the card via the line socket to my analogue line using > the cable that came with the card (and have also tried other cables too) > but I always get a RED alarm. > > I'm located in the UK, running FreeBSD-5.2, with zaptel-0.5 drivers > and asterisk-0.9.0_1 (both built from ports). > First things first. Scrap the "ports" and build from the latest CVS source. 0.9 is far to old and buggy, and suspect the same of the Zaptel driver you have, although I don't use *BSD myself. Secondly, the red alarm does tend to mean that the line is not connected, but I got what you're describing when I moved Asterisk to a new machine. Try the X100P card in a different PCI slot. That cleared it for me, for whatever reason. -- _/ _/ _/_/_/_/ _/_/ _/_/_/ _/_/ _/_/_/ _/_/ _/_/_/_/_/ _/ K e v i n W a l s h _/ _/_/ _/ _/ _/_/ _/_/[EMAIL PROTECTED] _/ _/ _/_/_/_/ _/_/_/_/ _/_/ ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] X101P FXO with RED alarm
You may need the 3-wire (UK) to 2-wire (US) adapters for the jack the X100P is plugged into. I've heard you can get them most anywhere. On Sat, 2004-07-10 at 09:40, Richard Airlie wrote: > Hi, > I've just added an X101P FXO card to my asterisk machine. The card is > detected ok but zttool always shows it in a RED alarm state, which I > understand means that it doesn't detect the line. > > I've connected the card via the line socket to my analogue line using > the cable that came with the card (and have also tried other cables too) > but I always get a RED alarm. > > I'm located in the UK, running FreeBSD-5.2, with zaptel-0.5 drivers > and asterisk-0.9.0_1 (both built from ports). > > My zaptel.conf: > fxsks=1 > loadzone=uk > defaultzone=uk > > My zapata.conf > [channels] > signalling=fxs_ks > context=default > channel => 1 > > Output of ztcfg -vv: > Keyword: [fxsks], Value: [1] > Keyword: [loadzone], Value: [uk] > Keyword: [defaultzone], Value: [uk] > > Zaptel Configuration > == > > > Channel map: > > Channel 01: FXS Kewlstart (Default) (Slaves: 01) > > 1 channels configured. > > Asterisk sees the zap channel (or at least it shows up with 'zap show > channels') but always sees it as busy, presumably because of the > red alarm. The other thing of note is that when the zaptel driver is > loaded, attempting to play MOH causes the entire system to lock up > and require a reboot. (Without the driver loaded it works, but is of > course choppy because of the lack of a timing source). > > Anyone have any ideas about what's going on? > > Richard. > ___ > Asterisk-Users mailing list > [EMAIL PROTECTED] > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users -- Eric Wieling * BTEL Consulting * 504-899-1387 x2111 "In a related story, the IRS has recently ruled that the cost of Windows upgrades can NOT be deducted as a gambling loss." ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
