busy tone for occupied extensions....

Status
Not open for further replies.

Rubik

New Member
Jan 31, 2018
16
1
3
47
Hi All,

would really appreciate your help

I am trying to create a busy tone for occupied extensions (extension that is occupied with another call)

so when a caller dial's-in to any extension that is preoccupied with another call, the caller will get a busy tone (current he gets a message that "the extension xxx is unavailable....")

I have tried to play with the "call limit" function in the dial plan, but it only works on the inbound calls and not per extension

any idea how should I tackle this problem?

thank you
 

DigitalDaz

Administrator
Staff member
Sep 29, 2016
3,038
556
113
So what this implies it is going to voicemail, if you do not want voicemail, turn it off in the extension settings.
 

Rubik

New Member
Jan 31, 2018
16
1
3
47
So what this implies it is going to voicemail, if you do not want voicemail, turn it off in the extension settings.
Thank you for the answer @DigitalDaz

I've tried that (disabling voicemail) but the problem is that I am still getting the message "the extension does not answer..." instead of busy tone.
any additional thoughts?

Best Regards

Rubi
 

DigitalDaz

Administrator
Staff member
Sep 29, 2016
3,038
556
113
Is this definitely giving you this for a busy and not a timeout?

Can you check with ngrep or sngrep and see what the phone is sending back?
 

Rubik

New Member
Jan 31, 2018
16
1
3
47
Dear @DigitalDaz

I've tested it and it definitely get's "busy" , here is a snapshot from my Wireshark

Screen Shot 2018-02-13 at 11.57.07.png

the issue is that I am trying to avoid the "the extension xxx is unavailable" voice message have a busy tone played instead which for some reason is not working
btw I have fusionpbx version 4.2 installed on Debian 8
 

Sherbet

New Member
Mar 8, 2018
3
0
1
33
I am having the very same issue. Turning voicemail off gives said message instead of playing a busy tone.
Is there any advice available?
 

DigitalDaz

Administrator
Staff member
Sep 29, 2016
3,038
556
113
I have just checked for a phone that is not registered and get the same, this is a very, very serious issue IMHO and must be undone.immediately.

For both 486 and what should be no answer this has now been turned into a 200OK and most importantly, A CHARGEABLE call.

Both of these return codes should end up with no charge to the caller but this complete behaviour change and something that is probably violating the SIP RFC has now made these calls chargeable.

This is also probably a violation of the law in some countries.
 

DigitalDaz

Administrator
Staff member
Sep 29, 2016
3,038
556
113
I'm hoping this is just a bug and not intentional, a quick look at the code makes me think that it is a bug.
 

Sherbet

New Member
Mar 8, 2018
3
0
1
33
Still have not come across a fix for this, and theres no ability to raise issues on the github.
Are you aware of a workaround?
 

DigitalDaz

Administrator
Staff member
Sep 29, 2016
3,038
556
113
The developer kindly adjusted this behaviour as soon as it was brought to his attention.

This has now been fixed in 4.4 and master.

It was intentional but I don't think the developer had realised the unintended consequences of adding what he thought was a helpful message, no one else had pointed this out until now.
 

DigitalDaz

Administrator
Staff member
Sep 29, 2016
3,038
556
113
Right, this has definitely now been fixed an tested, in order to apply the fix you will need to go into each domain and delete the 900 voicemail entry.

Then do an advanced/upgrade and step through them one at a time, the dialplan entry to delete is in the image below:

486fix.jpg
 

Kenny Riley

Active Member
Nov 1, 2017
243
39
28
36
Is there a more efficient way to delete a dialplan from all domains rather than going through each domain one at a time?
 
Status
Not open for further replies.