Ticket #1542 (new Feature Requests)

Opened 6 years ago

Last modified 4 years ago

Use indications.conf warning sounds instead of messages

Reported by: vgster Assigned to:
Priority: trivial Milestone: Undetermined
Component: Core Version:
Keywords: Cc:
Confirmation: Confirmed Distro:
Backend Engine: Asterisk 1.2.x Distro Ver:
Backend Ver: SVN Revision (if applicable):

Description

Instead of the 'All circuits are currently busy' message give the option of either playing messages or setting the relevant sound from indications.conf for each dial status. I have a few users who when they dial a number that isn't in use are getting this all circuits message and reporting the PBX as being at fault.

Attachments

extensions_additional.conf.patch (0.6 kB) - added by acumensystems on 12/09/08 12:05:21.
functions.inc.php.patch (0.7 kB) - added by acumensystems on 03/13/09 10:01:07.

Change History

01/12/07 16:39:40 changed by vgster

  • engine changed from All to Asterisk 1.2.x.
  • engine_version changed.
  • svn_rev changed.

Give the user the option of picking what tone to play for each dialstatus.

06/05/07 07:05:40 changed by mbrevda

see also: #1974

08/02/07 22:57:18 changed by vgster

  • confirmation set to Unreviewed.
  • version changed from 2.2rc1 to 2.3-branch.

08/24/07 18:11:44 changed by wvroger

  • milestone set to 3.0.

11/14/07 21:24:17 changed by p_lindheimer

  • confirmation changed from Unreviewed to Confirmed.
  • version deleted.
  • milestone changed from 2.4 to 3.0.

07/15/08 21:12:19 changed by p_lindheimer

  • milestone changed from 2.5 to 3.0.

12/09/08 12:05:21 changed by acumensystems

  • attachment extensions_additional.conf.patch added.

12/09/08 12:07:08 changed by acumensystems

The priority case here is the lack of a legitimate CONGESTION signal actually causing congestion indications. I have added a case for the CONGESTION state to undertake this, which provides the user with proper distinction between incorrect and busy numbers. This is provided in extensions_additional.conf.patch.

12/09/08 16:54:50 changed by p_lindheimer

the attached patch is not correct. When a trunk receives congestion it should not fail, it should allow the dialplan to see if other trunks can complete the call. (Also - please don't provide patches to extensions_additional.conf files as those are auto-generated...)

The real issue at hand here is if all trunks fail, what do you play. IN the case of only one trunk present, it is clearly the cause code from that trunk (which might be congestion as suggested here). If multiple trunks are tried and they all fail, then you need to determine the 'best' reason they failed (assuming they all don't agree)...

12/09/08 17:06:42 changed by acumensystems

Phillipe,

Sensible points. I would write the patch for modules/core/functions.inc.php but if you don't agree on the approach then that's irrelevant :)

In terms of our context, the trunk failover is useless without a separate Asterisk patch for chan_iax.c which removes the 30s delay between IAX2 timeouts (i.e. failing over between unavailable trunks).

The case we are trying to deal with is that a number is unallocated/totally unavailable- in which case we want to fail immediately. All carriers we use in the real world send Congestion only for this state.

With intra-company trunking the case could be different, but i guess the real point is that in the long run, FreePBX could deal with some use options choosing what action to take on trunk failure under certain conditions.

I will patch this for our own internal use. Let me know if you want me to write a more detailed patch for FreePBX extensions control on the back of it however.

Regards

03/13/09 10:00:50 changed by acumensystems

Phillipe This is confirmed but we have seen no movement on it. I have patched the extensions source instead - please let me know if you are happy to include, as we find it's currently very misleading for users. Leo

03/13/09 10:01:07 changed by acumensystems

  • attachment functions.inc.php.patch added.

03/13/09 10:23:17 changed by p_lindheimer

acumensystems,

the problem is this is WRONG. We do not give up when a trunk reports congestion, that is one of the specific reasons we go to the next trunk, it means (amongst potentially other things) that the trunk is congested but not that the number is not good. A congested trunk could be caused because all available channels are being used, or your carrier is having problems getting the call out and another trunk may not have that problem.

If there is other potential information that we could check returned from some trunks that would further qualify the failure as being final (number does not exist) then we would be glad to look at the proposal and modifications.

If you want to submit suggestions for the final macro-outisbusy we can entertain those as we are already investigation some options that would allow other messages to be played (and even specific messages if the route is an Emergency route.)

08/17/09 19:22:00 changed by p_lindheimer

  • milestone changed from 2.6 to 2.7.