[ASTPPCOM-384] DID MAX Count Excced - SWITCH_CONGESTION should be USER_BUSY Created: 08/Apr/18  Updated: 05/Jan/22  Resolved: 05/Jan/22

Status: Done
Project: ASTPP Community
Component/s: None
Affects Version/s: None
Fix Version/s: v5.0

Type: Improvement
Reporter: countrdd Assignee: Samir Doshi
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 10m
Original Estimate: Not Specified

Issue Links:
Cloners

 Description   

On line 219 of astpp.xml.lua - If the DID max count is exceeded, the system is doing a Hangup SWITCH_CONGESTION. This is really deceiving when looking at reporting.

I believe it should be SET to USER_BUSY, that way the calling party will get a BUSY signal instead of the FAST BUSY that is assocaited with SWITCH_CONGESTION. The switch is not really congested.

Also, this would be nice because you could look at the CDRS for the DID call that you see a USER_BUSY, you could do report to show which of your customers should increase the number of call paths.

 Comments   
Comment by (Community) DN (Inactive) [ 09/Apr/18 ]

[~countrdd]
The maxchannels flag is for limiting CC and as per here, https://wiki.freeswitch.org/wiki/Hangup_Causes
SWITCH_CONGESTION | This cause indicates that the switching equipment generating this cause is experiencing a period of high traffic.
and as CC threshold reaches means traffic is high for that DID then expected or allowed.

However if you think 'USER_BUSY' is more appropriate for your use case, you have found the right spot change it with USER_BUSY and it should be good to go.

Comment by countrdd [ 09/Apr/18 ]

I have another request in as well for the outbound (Issue 281) CC that Samir thought would be a nice feature as well.
SO maybe This and 381 could be a selection box setting in Global Setting that could be

Inbound CC – Switch_Congestion or USER_BUSY
Outbound CC – Switch Congestion or the FILE You want played.

From: devang nathwani <notifications@github.com>
Reply-To: iNextrix/ASTPP <reply@reply.github.com>
Date: Monday, April 9, 2018 at 12:24 AM
To: iNextrix/ASTPP <ASTPP@noreply.github.com>
Cc: Dustian Countryman <countrdd@leillc.net>, Mention <mention@noreply.github.com>
Subject: Re: [iNextrix/ASTPP] DID MAX Count Excced - SWITCH_CONGESTION should be USER_BUSY (ASTPPCOM-384)

@countrdd<https://github.com/countrdd>
The maxchannels flag is for limiting CC and as per here, https://wiki.freeswitch.org/wiki/Hangup_Causes
SWITCH_CONGESTION | This cause indicates that the switching equipment generating this cause is experiencing a period of high traffic.
and as CC threshold reaches means traffic is high for that DID then expected or allowed.

However if you think 'USER_BUSY' is more appropriate for your use case, you have found the right spot change it with USER_BUSY and it should be good to go.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<https://github.com/iNextrix/ASTPP/issues/384#issuecomment-379626967>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ADVysnvzHShO3paUacfxS2KKk--SzY6Iks5tmuJ_gaJpZM4TLnX6>.

Comment by Samir Doshi [ 08/Sep/18 ]

Hi (Community) DN

Please look at this point and do needful.

Comment by Sameer Patel (Inactive) [ 05/Aug/20 ]

Devang Nathwani Please change the status if issue is fixed.

Comment by Sandip Dhamecha (Inactive) [ 05/Aug/20 ]

I don't apply changes to the community version. I have resolved this issue for the Enterprise version only.

http://myitpl.inextrix.com:8791/ITPLATP/ASTPP/-/merge_requests/1377

 

Generated at Sat Feb 10 07:16:38 CET 2024 using Jira 8.13.3#813003-sha1:22ebedbb75c99b147c66f14e031dd8a2d214753a.