Re: [Asterisk-Users] Terrible crackling on analogue line and X100Pcard

2005-04-10 Thread Stuart Ford
Rich Adamson ...
Okay. There are two fairly small integrated circuits on the board.
Can you post the part numbers on those chips?
Not at the moment, unfortunately. The card is in a datacentre 200 miles 
away. However, and while I appreciate that you can't read anything from 
this, but this is the card:

http://i24.ebayimg.com/01/i/02/c3/8b/43_1.JPG
(the same Ebay vendor is selling dozens of them)
NMI = non maskable interrupt (or somthing like that). Those messages
would suggest there is a problem with that card and the wcfxo driver.
Right.
The mode is FCC is saying the zaptel drivers are assuming a
card that matches US telco standards. Again, without the chip set
numbers, I can't tell if that card will work correctly in the UK.
If it does not support UK standards, not likely you'll ever get
the echo to go away.
Sounds like I've bought a hooky card then :(
Okay, then there is about a 90% chance the card's chip set was
designed for the US telco standards. I'll be able to tell more
once you post those part numbers.
It's going to be a couple of weeks before I can do that, unfortunately.
Are you using a opermode=UK or anything like that in /etc/zaptel.conf?
No. Should I try that or do you not think it'll make that much difference in 
light of the findings above?

It would appear you have several interrupts that aren't being used.
Have you tried looking at the bios setup to see if you can disable
any unused interrupts (like 3 for com1 port)?
Yes I tried all that. Even freeing up other interrupts caused the system to 
fail to boot. I didn't understand it.

If there is nothing in the bios relative to configuring interrupts, then
you only choice is to move the card to other slots in hope of
finding one that assigns a different interrupt.
Now that I didn't try.
There is at least a better then 50% chance sharing the interrupt
between the wcfxo driver and the raid controller (#11) is causing
at least some of the crackling noise. You might try establishing
a call and do a large file copy (to exercise the disk) to see if
disk activity causes the noise.
I tried this and it made no noticeable difference. The crackling's always 
quite bad to start with, and since RAID controllers are basically small 
computers themselves it probably stands to reason that activity will be 
pretty much constant.

[zttest]
Is that good?
Yes, that looks good.
That's something at least!
You might try going back to an earlier version (or cvs head) to
see if that has any impact on the noise.
I think that in light of what you've advised above I don't think this is the 
problem. I also completely disagree with regressing to former versions of 
software to hack something into working, since I might actually need a 
feature or bugfix that's provided by the later version in order to have 
something else working!

So, here's what I think I'll do:
1) I'm going to start with buying a genuine X100P, to eliminate the 
possibility of cheapness affecting things. However, as I said, I'm having 
tremendous trouble sourcing one. Does anyone know of any outlets in the UK 
who supply them? I've seen them for sale on several US websites, but I'm 
going to assume that they'll only work with US telcos?

2) Once I've got one, I'll have another stab at the interrupt mess again. 
I'll try to move the card between PCI slots and have another, more 
structured, session with the BIOS.

Sound like a plan?
Thanks
Stuart 

___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
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] Terrible crackling on analogue line and X100Pcard

2005-04-10 Thread Rich Adamson
   [DC]
  
   Well mine is legitimate digium
  
   And I'm in the usa
  
  
   Here is the output but I have no idea what that means?
  
   [EMAIL PROTECTED] root]# cat /proc/interrupts
  CPU0
 0: 490763  XT-PIC  timer
 1:  2  XT-PIC  keyboard
 2:  0  XT-PIC  cascade
 8:  1  XT-PIC  rtc
 9:4885971  XT-PIC  wcfxo
10:  34309  XT-PIC  eth0
11:4885856  XT-PIC  wcfxo
12:4886150  XT-PIC  ztdummy, usb-uhci
14:   7662  XT-PIC  ide0
   NMI:  0
   ERR:  0
  
  The digium card used in the US will match the telco impedance specs.
  
  Your x100p card is on interrupt 9 by itself (not shared with any
  other i/o device). That's a good thing.
  
  Those two items rule out a number of items in terms of what
  might be causing the crackling noise.
  
  What * version are you using Dean? Have you tried other versions?
  
  [DC] 
 I use [EMAIL PROTECTED] V 0.8
 [DC] this has been an ongoing problem so not sure if it is related to
 version (as I've used asterisk head up until about 6 months ago and
 version 0.4,0.6 and now 0.8 version of [EMAIL PROTECTED]
 [DC] 

There has been some development going on (and some maintenance)
relative to iax, rtp, jitterbuffer, etc. Maybe something did or didn't
get moved into stable impacting this.

My next step would be to implement cvs-head to see if that corrects
the problem. Don't know of any other way to ID the issue other then
that.


___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
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] Terrible crackling on analogue line and X100Pcard

2005-04-10 Thread Rich Adamson
  Okay. There are two fairly small integrated circuits on the board.
  Can you post the part numbers on those chips?
 
 Not at the moment, unfortunately. The card is in a datacentre 200 miles 
 away. However, and while I appreciate that you can't read anything from 
 this, but this is the card:
 
 http://i24.ebayimg.com/01/i/02/c3/8b/43_1.JPG
 
 (the same Ebay vendor is selling dozens of them)
 
  NMI = non maskable interrupt (or somthing like that). Those messages
  would suggest there is a problem with that card and the wcfxo driver.
 
 Right.
 
  The mode is FCC is saying the zaptel drivers are assuming a
  card that matches US telco standards. Again, without the chip set
  numbers, I can't tell if that card will work correctly in the UK.
  If it does not support UK standards, not likely you'll ever get
  the echo to go away.
 
 Sounds like I've bought a hooky card then :(
 
  Okay, then there is about a 90% chance the card's chip set was
  designed for the US telco standards. I'll be able to tell more
  once you post those part numbers.
 
 It's going to be a couple of weeks before I can do that, unfortunately.
 
  Are you using a opermode=UK or anything like that in /etc/zaptel.conf?
 
 No. Should I try that or do you not think it'll make that much difference in 
 light of the findings above?
 
  It would appear you have several interrupts that aren't being used.
  Have you tried looking at the bios setup to see if you can disable
  any unused interrupts (like 3 for com1 port)?
 
 Yes I tried all that. Even freeing up other interrupts caused the system to 
 fail to boot. I didn't understand it.
 
  If there is nothing in the bios relative to configuring interrupts, then
  you only choice is to move the card to other slots in hope of
  finding one that assigns a different interrupt.
 
 Now that I didn't try.
 
  There is at least a better then 50% chance sharing the interrupt
  between the wcfxo driver and the raid controller (#11) is causing
  at least some of the crackling noise. You might try establishing
  a call and do a large file copy (to exercise the disk) to see if
  disk activity causes the noise.
 
 I tried this and it made no noticeable difference. The crackling's always 
 quite bad to start with, and since RAID controllers are basically small 
 computers themselves it probably stands to reason that activity will be 
 pretty much constant.
 
 [zttest]
  Is that good?
 
  Yes, that looks good.
 
 That's something at least!
 
  You might try going back to an earlier version (or cvs head) to
  see if that has any impact on the noise.
 
 I think that in light of what you've advised above I don't think this is the 
 problem. I also completely disagree with regressing to former versions of 
 software to hack something into working, since I might actually need a 
 feature or bugfix that's provided by the later version in order to have 
 something else working!
 
 So, here's what I think I'll do:
 
 1) I'm going to start with buying a genuine X100P, to eliminate the 
 possibility of cheapness affecting things. However, as I said, I'm having 
 tremendous trouble sourcing one. Does anyone know of any outlets in the UK 
 who supply them? I've seen them for sale on several US websites, but I'm 
 going to assume that they'll only work with US telcos?
 
 2) Once I've got one, I'll have another stab at the interrupt mess again. 
 I'll try to move the card between PCI slots and have another, more 
 structured, session with the BIOS.
 
 Sound like a plan?

Sounds reasonable for starters.

Somewhere in your plan I'd really suggest implementing another version
at least on a temp basis as one mechanism to rule out a problem with
your current version. It's not that hard really.

Also, keep in mind the x100p cards were designed years ago as a modem
(not a voip/pstn interface). Having been around this list for over a
year now, I don't remember hearing/seeing anyone say they found a x100p
card or compatible that truly supports the UK standards. I'd have to 
guess the OEMs targeted the US modem market at that time, so mucking
around with other x100p compatibles are just as likely to result in
time consuming frustration.

Some of the compatible cards use an Intel chipset. If you look at the
Intel specs, Intel had two different chipsets on their cards; one
targeted for the US market, and the other for limited non-US markets.
Even if you find a card targeted for the non-US market, I wouldn't
bet a nickle the interrupt issues shown in your output will be 
addressed.

The TDM400 card (with appropriate modules) is the replacement for the
x100p, and the chipset in use on those modules _do_ support many different
international standards. The early versions of the TDM card had several
problems (output of dmesg showed Wildcard TDM400P REV E/F as an example),
however the current version (Wildcard TDM400P REV H) seems to be far
more stable. (I just replaced my old card yesterday with a new one
provided by digium as an 

Re: [Asterisk-Users] Terrible crackling on analogue line and X100Pcard

2005-04-10 Thread John Novack

Rich Adamson wrote:
snip
The TDM400 card (with appropriate modules) is the replacement for the x100p, and the chipset in use on those modules _do_ support many different international standards. The early versions of the TDM card had several problems (output of dmesg showed Wildcard TDM400P REV E/F as an example),
however the current version (Wildcard TDM400P REV H) seems to be far more stable. (I just replaced my old card yesterday with a new one provided by digium as an in-warrantee RMA replacement.)
 

The card I have reports from software that it is an E/F but it clearly 
says on the board it is revision H.
Curious.

FWIW, I use the clone card for FXO, and have no problems with any 
crackle. The echo problem resolves itself after a few seconds of 
training but I am using it on a VERY short loop to connect to an 
electromechanical step by step switch

John Novack
 

___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
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] Terrible crackling on analogue line and X100Pcard

2005-04-10 Thread Rich Adamson
 The TDM400 card (with appropriate modules) is the replacement for the x100p, 
 and the chipset 
in use on those modules _do_ support many different international standards. 
The early versions 
of the TDM card had several problems (output of dmesg showed Wildcard TDM400P 
REV E/F as an 
example),
 however the current version (Wildcard TDM400P REV H) seems to be far more 
 stable. (I just 
replaced my old card yesterday with a new one provided by digium as an 
in-warrantee RMA 
replacement.)
   
 
 The card I have reports from software that it is an E/F but it clearly 
 says on the board it is revision H.
 Curious.
 
 FWIW, I use the clone card for FXO, and have no problems with any 
 crackle. The echo problem resolves itself after a few seconds of 
 training but I am using it on a VERY short loop to connect to an 
 electromechanical step by step switch

Its my understanding (but possibly wrong) the E/F version was the
first release of the TDM card which I purchased direct from digium
a few days before it was announced.

The a few weeks/months after the release, they were RMA'ing those
boards to make a modification to them (adding a jumper or something
to it). The card still reported itself as E/F.

Then sometime after that, another release of the card quitely
happened, but I don't have any knowledge of what the changes were.

Somtime after that (and maybe even some other releases of the card),
the Rev H came out (which is what digium is currently shipping), and
it reports itself as Rev H as well (when using cvs head).

This current Rev H has several additional components on the card
and the fxo modules have printing on them showing x100. I'd have
to guess this particular board probably has some revisions 
involving the Tiger Jet interface. Its the same old Tiger Jet chip,
but the area around the chip is laid out differently suggesting
a redesign of the printed circuit board itself and involves more
components.

That's about the best I can summarize for it.

Now I'm waiting to see if this one goes out to lunch every week
or two.


___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
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] Terrible crackling on analogue line and X100Pcard

2005-04-09 Thread Stuart Ford
Dean Collins wrote ...

 Using 2 digium genuine x100p's in a dell with riser card.

 I'm wondering if it is something to do with the riser because 
 it doesn't seem to matter if I swap various cords, positions, etc.

Right, that's interesting. My card too is in a Dell (2550) with a riser
card. That's a pig! Has *anything* you've done improved it at all?

Stuart



___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
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] Terrible crackling on analogue line and X100Pcard

2005-04-09 Thread Stuart Ford
Rich Adamson wrote ...
What country are you in, and does the chipset on the compat card
support the telco standards in your country?
I'm in the UK. The card was bought in the UK, but from Ebay, so I suppose it 
could have originated from anywhere. The card dials and answers calls 
without a problem, so it must be doing *something* right.

I didn't *mean* to cheap out over this - I tried to buy a genuine Digium 
part, but they don't seem to do it any more and I can't find it for sale 
anywhere. The Ebay vendor claimed it was 100% compatible.

The card reports itself as:
00:02.0 Communication controller: Individual Computers - Jens Schoenfeld 
Intel 537

When the wcfxo module loads, dmesg reports:
Zapata Telephony Interface Registered on major 196
PCI: Found IRQ 11 for device :00:02.0
Uhhuh. NMI received. Dazed and confused, but trying to continue
You probably have a hardware problem with your RAM chips
wcfxo: DAA mode is 'FCC'
Found a Wildcard FXO: Generic Clone
Registered tone zone 4 (United Kingdom)
The 3rd and 4th lines are suspicous, but I've no idea what they mean. Does 
it refer to the system RAM or some sort of special RAM on the card? What is 
NMI?

If the chipset doesn't match your telco standards, there is a high
probability you won't get rid of the echo. If it does match, then try
echotraining=800
echocancel=yes
I already use those parameters in zapata.conf, they make no difference :(
Regarding the crackling noise, have you checked for shared
interrupts (cat /proc/interrupts)?
This is the output:
  CPU0
 0:  211266080  XT-PIC  timer
 2:  0  XT-PIC  cascade
 7: 488230  XT-PIC  eth0
10:2113812  XT-PIC  eth1
11:  211520617  XT-PIC  aacraid, wcfxo
14: 11  XT-PIC  ide0
NMI:  1
ERR: 60
It's sharing an interrupt with the RAID controller. I did try to separate 
the interrupts when I installed the card, but any combination other than 
that automatically assigned by the BIOS caused the Linux kernel to fail to 
even uncompress at boot time, much less boot the system, which struck me as 
a pretty alarming failure.

If you run cat /proc/interrupts every ten seconds, do you see
calculated interrupt values of about 1,000?
I don't know what you mean here.
Go to /usr/src/zaptel directory and run
./zttest
Do you get something close to 100% over some period of time?
Yep:
# ./zttest
Opened pseudo zap interface, measuring accuracy...
99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793%
99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793%
Is that good?
What version of asterisk are you running?
1.0.7 plus Zaptel of the same version.
Thanks
Stuart 

___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
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] Terrible crackling on analogue line and X100Pcard

2005-04-09 Thread dean collins

 
 What country are you in, and does the chipset on the compat card
 support the telco standards in your country?
 
 If the chipset doesn't match your telco standards, there is a high
 probability you won't get rid of the echo. If it does match, then try
  echotraining=800
  echocancel=yes
 
 Regarding the crackling noise, have you checked for shared
 interrupts (cat /proc/interrupts)?
 
 If you run cat /proc/interrupts every ten seconds, do you see
 calculated interrupt values of about 1,000?
 
 Go to /usr/src/zaptel directory and run
  ./zttest
 Do you get something close to 100% over some period of time?
 
 What version of asterisk are you running?
 

[DC] 

Well mine is legitimate digium

And I'm in the usa


Here is the output but I have no idea what that means?

[EMAIL PROTECTED] root]# cat /proc/interrupts
   CPU0
  0: 490763  XT-PIC  timer
  1:  2  XT-PIC  keyboard
  2:  0  XT-PIC  cascade
  8:  1  XT-PIC  rtc
  9:4885971  XT-PIC  wcfxo
 10:  34309  XT-PIC  eth0
 11:4885856  XT-PIC  wcfxo
 12:4886150  XT-PIC  ztdummy, usb-uhci
 14:   7662  XT-PIC  ide0
NMI:  0
ERR:  0



Cheers,
Dean 

___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
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] Terrible crackling on analogue line and X100Pcard

2005-04-09 Thread Rich Adamson
  What country are you in, and does the chipset on the compat card
  support the telco standards in your country?
  
  If the chipset doesn't match your telco standards, there is a high
  probability you won't get rid of the echo. If it does match, then try
   echotraining=800
   echocancel=yes
  
  Regarding the crackling noise, have you checked for shared
  interrupts (cat /proc/interrupts)?
  
  If you run cat /proc/interrupts every ten seconds, do you see
  calculated interrupt values of about 1,000?
  
  Go to /usr/src/zaptel directory and run
   ./zttest
  Do you get something close to 100% over some period of time?
  
  What version of asterisk are you running?
  
 
 [DC] 
 
 Well mine is legitimate digium
 
 And I'm in the usa
 
 
 Here is the output but I have no idea what that means?
 
 [EMAIL PROTECTED] root]# cat /proc/interrupts
CPU0
   0: 490763  XT-PIC  timer
   1:  2  XT-PIC  keyboard
   2:  0  XT-PIC  cascade
   8:  1  XT-PIC  rtc
   9:4885971  XT-PIC  wcfxo
  10:  34309  XT-PIC  eth0
  11:4885856  XT-PIC  wcfxo
  12:4886150  XT-PIC  ztdummy, usb-uhci
  14:   7662  XT-PIC  ide0
 NMI:  0
 ERR:  0

The digium card used in the US will match the telco impedance specs.

Your x100p card is on interrupt 9 by itself (not shared with any
other i/o device). That's a good thing.

Those two items rule out a number of items in terms of what
might be causing the crackling noise.

What * version are you using Dean? Have you tried other versions?


___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
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] Terrible crackling on analogue line and X100Pcard

2005-04-09 Thread Rich Adamson
  What country are you in, and does the chipset on the compat card
  support the telco standards in your country?
 
 I'm in the UK. The card was bought in the UK, but from Ebay, so I suppose it 
 could have originated from anywhere. The card dials and answers calls 
 without a problem, so it must be doing *something* right.

Okay. There are two fairly small integrated circuits on the board.
Can you post the part numbers on those chips?

 The card reports itself as:
 
 00:02.0 Communication controller: Individual Computers - Jens Schoenfeld 
 Intel 537
 
 When the wcfxo module loads, dmesg reports:
 
 Zapata Telephony Interface Registered on major 196
 PCI: Found IRQ 11 for device :00:02.0
 Uhhuh. NMI received. Dazed and confused, but trying to continue
 You probably have a hardware problem with your RAM chips
 wcfxo: DAA mode is 'FCC'
 Found a Wildcard FXO: Generic Clone
 Registered tone zone 4 (United Kingdom)
 
 The 3rd and 4th lines are suspicous, but I've no idea what they mean. Does 
 it refer to the system RAM or some sort of special RAM on the card? What is 
 NMI?

NMI = non maskable interrupt (or somthing like that). Those messages
would suggest there is a problem with that card and the wcfxo driver.
 
The mode is FCC is saying the zaptel drivers are assuming a
card that matches US telco standards. Again, without the chip set
numbers, I can't tell if that card will work correctly in the UK.
If it does not support UK standards, not likely you'll ever get
the echo to go away.

  If the chipset doesn't match your telco standards, there is a high
  probability you won't get rid of the echo. If it does match, then try
  echotraining=800
  echocancel=yes
 
 I already use those parameters in zapata.conf, they make no difference :(

Okay, then there is about a 90% chance the card's chip set was
designed for the US telco standards. I'll be able to tell more
once you post those part numbers. 

Are you using a opermode=UK or anything like that in /etc/zaptel.conf?
 
  Regarding the crackling noise, have you checked for shared
  interrupts (cat /proc/interrupts)?
 
 This is the output:
 
CPU0
   0:  211266080  XT-PIC  timer
   2:  0  XT-PIC  cascade
   7: 488230  XT-PIC  eth0
  10:2113812  XT-PIC  eth1
  11:  211520617  XT-PIC  aacraid, wcfxo
  14: 11  XT-PIC  ide0
 NMI:  1
 ERR: 60
 
 It's sharing an interrupt with the RAID controller. I did try to separate 
 the interrupts when I installed the card, but any combination other than 
 that automatically assigned by the BIOS caused the Linux kernel to fail to 
 even uncompress at boot time, much less boot the system, which struck me as 
 a pretty alarming failure.

It would appear you have several interrupts that aren't being used.
Have you tried looking at the bios setup to see if you can disable
any unused interrupts (like 3 for com1 port)?

If there is nothing in the bios relative to configuring interrupts, then
you only choice is to move the card to other slots in hope of
finding one that assigns a different interrupt.

There is at least a better then 50% chance sharing the interrupt
between the wcfxo driver and the raid controller (#11) is causing
at least some of the crackling noise. You might try establishing
a call and do a large file copy (to exercise the disk) to see if
disk activity causes the noise.
 

  Go to /usr/src/zaptel directory and run
  ./zttest
  Do you get something close to 100% over some period of time?
 
 Yep:
 
 # ./zttest
 Opened pseudo zap interface, measuring accuracy...
 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793%
 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793%
 
 Is that good?

Yes, that looks good.

  What version of asterisk are you running?
 
 1.0.7 plus Zaptel of the same version.

You might try going back to an earlier version (or cvs head) to
see if that has any impact on the noise.


___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
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] Terrible crackling on analogue line and X100Pcard

2005-04-09 Thread dean collins
  [DC]
 
  Well mine is legitimate digium
 
  And I'm in the usa
 
 
  Here is the output but I have no idea what that means?
 
  [EMAIL PROTECTED] root]# cat /proc/interrupts
 CPU0
0: 490763  XT-PIC  timer
1:  2  XT-PIC  keyboard
2:  0  XT-PIC  cascade
8:  1  XT-PIC  rtc
9:4885971  XT-PIC  wcfxo
   10:  34309  XT-PIC  eth0
   11:4885856  XT-PIC  wcfxo
   12:4886150  XT-PIC  ztdummy, usb-uhci
   14:   7662  XT-PIC  ide0
  NMI:  0
  ERR:  0
 
 The digium card used in the US will match the telco impedance specs.
 
 Your x100p card is on interrupt 9 by itself (not shared with any
 other i/o device). That's a good thing.
 
 Those two items rule out a number of items in terms of what
 might be causing the crackling noise.
 
 What * version are you using Dean? Have you tried other versions?
 
 [DC] 
I use [EMAIL PROTECTED] V 0.8
[DC] this has been an ongoing problem so not sure if it is related to
version (as I've used asterisk head up until about 6 months ago and
version 0.4,0.6 and now 0.8 version of [EMAIL PROTECTED]
[DC] 

Cheers,
Dean 


___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users