Busy Here (486)

[VinnieI]

Hi all,

First time posting here so apologies if any formatting or whatnot is incorrect.

Essentially, I have an issue with regards to inbound calls on a main number not going through and returning a Busy Here (486) error code. The number in question makes outbound calls fine, it's just inbound that seems to be the issue.

It's set up as follows: Calls to the Main Trunk Number are routed to a ring group, in said ring group are 2 extensions which are online, registered etc and are also receiving calls fine if their respective DIDs are dialled individually. The ring group also has a destination if no answer set to another extension which is working fine too...

If the main ring group number is dialled however, it returns a user busy in the logs as well as the automated response.

It's in a multi-company configuration.

Any help would be greatly appreciated

 

[lancerichards]

Hi @VinnieI

It sounds like on the Trunk you have the Default Route set to End Call



Set the Default route to Ring Group then select your Ring Group



You can also check where it's routing under Reports > Call Log

Best,
Lance

 

[leejor]

If you call the ring group directly, from an extension, does the call proceed correctly?
If so, then I would make use of the 3CX Activity Log, which should show exactly what is happening with the external call.

 

[VinnieI]

Hi folks!

Thank you for your replies! Turns out I was being a bit of an idiot! I'll pop the solution here anyway as I couldn't find much help by way of Google prior to posting here...

Solution: DID was already in use!

 

[AWS2P]

it happens , only humans

 

[leejor]

When you created the (second) DID rule, did it not tell you that a rule already existed?