[Asterisk-Users] X100P - Busydetect / calls being disconnected - Australia; tip.

2003-09-26 Thread Shaun Ewing
Hi All,

This isn't really a question, but it's an issue I experienced that was
driving me crazy for a few days, so I thought it might be good for the
archives.

Basically what was happening was everytime a particular customer called
(long distance), the line would disconnect immediately after answering.

I thought it might have been the phone, so I swapped the phone with
another - still happened.

I thought that there was some remote possibility that the phone company was
reversing the line on answering long distance calls, so I switched to fxs_ls
instead of fxs_ks - no difference.

Various things were tried to no avail, until I made a long distance call
over a different carrier to our usual carrier (we use Optus, I made the call
over Telstra). When the remote end answered, my end disconnected.

What was happening was, when the call is answered, 5 quick chirps are sent
down the line. However, because of the bug in the Cisco 7960 causing the
first 1/2 a second or so of a conversation to be cut off - I didn't hear
these chirps and as such I didn't think of the next bit:

Basically, because I had busycount set to 3 and busydetect set to yes, these
chirps were being detected by the busydetect function and causing the call
to be disconnected. I raised the busycount to something safe (8) and this no
longer happened.

This has me worried for a while, especially as I'd just disconnected the old
PBX a few days ago and spent a nice amount of money on Cisco 7960 and 7940
IP phones (and will probably be ordering more in the near future).

Anyway, I'm pleased to report that everything is now working perfectly and
I'm extremely happy with Asterisk. I'd contribute, but alas I'm not much of
a C programmer.

-Shaun

___
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [Asterisk-Users] X100P - Busydetect / calls being disconnected - Australia; tip.

2003-09-26 Thread Martin Pycko
Because of the nature of busydetect algorithm busycount shouldn't be set
to less than 8. It's 10 by default.

Just imagine that you dial a number that is attached to some speed dial
key. It'll surely cause hangup if busydetect  8.

Martin

On Sat, 27 Sep 2003, Shaun Ewing wrote:

 Hi All,

 This isn't really a question, but it's an issue I experienced that was
 driving me crazy for a few days, so I thought it might be good for the
 archives.

 Basically what was happening was everytime a particular customer called
 (long distance), the line would disconnect immediately after answering.

 I thought it might have been the phone, so I swapped the phone with
 another - still happened.

 I thought that there was some remote possibility that the phone company was
 reversing the line on answering long distance calls, so I switched to fxs_ls
 instead of fxs_ks - no difference.

 Various things were tried to no avail, until I made a long distance call
 over a different carrier to our usual carrier (we use Optus, I made the call
 over Telstra). When the remote end answered, my end disconnected.

 What was happening was, when the call is answered, 5 quick chirps are sent
 down the line. However, because of the bug in the Cisco 7960 causing the
 first 1/2 a second or so of a conversation to be cut off - I didn't hear
 these chirps and as such I didn't think of the next bit:

 Basically, because I had busycount set to 3 and busydetect set to yes, these
 chirps were being detected by the busydetect function and causing the call
 to be disconnected. I raised the busycount to something safe (8) and this no
 longer happened.

 This has me worried for a while, especially as I'd just disconnected the old
 PBX a few days ago and spent a nice amount of money on Cisco 7960 and 7940
 IP phones (and will probably be ordering more in the near future).

 Anyway, I'm pleased to report that everything is now working perfectly and
 I'm extremely happy with Asterisk. I'd contribute, but alas I'm not much of
 a C programmer.

 -Shaun

 ___
 Asterisk-Users mailing list
 [EMAIL PROTECTED]
 http://lists.digium.com/mailman/listinfo/asterisk-users


___
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [Asterisk-Users] X100P - Busydetect / calls being disconnected - Australia; tip.

2003-09-26 Thread Shaun Ewing

- Original Message - 
From: Martin Pycko [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, September 27, 2003 2:36 AM
Subject: Re: [Asterisk-Users] X100P - Busydetect / calls being
disconnected - Australia; tip.


 Because of the nature of busydetect algorithm busycount shouldn't be set
 to less than 8. It's 10 by default.

 Just imagine that you dial a number that is attached to some speed dial
 key. It'll surely cause hangup if busydetect  8.

 Martin

Aah, thanks for the tip Martin; that I wasn't aware of. Maybe I'll try 10
:-)

-Shaun

___
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users