Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

486 User Busy should not be a failed call notification

Discussion in 'Ideas' started by justint, Oct 16, 2017.

486 User Busy should not be a failed call notification 5 5 5votes
5/5, 5 votes

  1. justint

    Joined:
    May 6, 2011
    Messages:
    4
    Likes Received:
    0
    Have alerts turned on for many of my customers so I can monitor the PBX for any issues. I do like to have the failed call alert turned on so I can see if a user is dialing a number incorrectly or if the calls are failing and I need to resolve an issue. This can get very annoying however when a user keeps redialing a number because the line is busy and I end up with 5, 10, or even more 486 User Busy alerts in my inbox. Busy calls should be a separate option in the notification setup menu for admins like myself that don't care about these alerts.
     
  2. infohit

    Joined:
    Nov 21, 2017
    Messages:
    21
    Likes Received:
    8
    In v15.5 you can go to Settings -> Parameters and search for "RESPONSE_ERROR_CODES". Simply remove 486 from the list there. This should solve your problem :)
     
    HH60 likes this.