I wonder if this is intended behaviour or not..
2 linegroups (top down)
each linegroup has >1 members, but only one is idle, the rest are on a call
the idle member is 1 extension that is in both linegroups
and has busy-trigger set to 2 (this is a Jabber device)
Now, when 2 calls are placed, one to each of the huntpilots, the Jabber receives 2 incoming calls,
This is very confusing for the Jabber user!
I would expect that the 1st call would make the Jabber ring, but then the Jabber is not idle
and thus the 2nd call should go elsewhere (whatever is configured for the hunt).
When we set busy-trigger to 1 it works, but then the customer loses call-waiting for their normal internal calls
It's not the max. calls parameter, that triggers the amount of calls, it's the busy trigger parameter. You'll find this one just above the max. calls.
So you set the busy-trigger to 1 or to 2?If it is set to 2 the 2nd call might end to the same phone, depending what distribution alghorythm you choosed.
well, both, on 2 there are 2 huntgroup calls coming,
when it's 1 it's working fine, but then there is no call waiting anymore
I would not expect this dual call delivery on longest-idle, circular, top-down,
as the phone is not idle