Ring groups to act on SIP_FORKED_ID_BUSY parameter

[jonpennell]

Currently, if an extension has multiple devices registered and is being called via a ring group, the call must be declined by every registered device to send busy here back. This behaviour should be modified by the SIP_FORKED_ID_BUSY parameter but it does not work.

Currently with SIP_FORKED_ID_BUSY set correctly, calls to an extension work correctly, declining the call on any registered device send the caller to the busy destination and stop all devices from ringing immediately. The same is true if the extension participates in a call queue - but not in a ring group.

This actually feels like a "bug" rather than an idea for improvement but previous posts on the subject have had little or no follow-up

 

[jonpennell]

OK - I get that few people would even know the SIP_FORKED_ID_BUSY parameter existed. But come on please, someone at 3cx take a quick look at this. Surely it's a bug that calls direct to an extension or calls where the extension is an agent in a queue follow the SIP_FORKED_ID_BUSY setting but calls where the extension is in a ring group don't?!?

This is causing me a major headache... I can't use call queues because the polling interval is so short a declined call rings back before an agent can logout of the queue and I can't use ring groups because declining the call on one device registered to an extension leaves all the other devices ringing.