We've discovered that when a hunt group dials an extension, the find me/follow me settings for that extension are ignored. When the extension is dialed internally or a call is routed directly to the extension, the find me/follow me works fine. Is that the expected behavior for some reason, or is this a bug?
Submitted by eeman on Sat, 01/24/2009
Permalink
Submitted by tealnet on Sun, 01/25/2009
Permalink
I understand. The problem
I understand. The problem we had with the "other numbers" is that the original caller id is not passed when using that feature. So when the calls come through to our cell phones, we don't know who it is. I think I saw some other posts about that but I don't know that there has been a resolution.
This is expected behavior and by design. A ring group is an intent to ring a series of phones concurrently allowing the first to answer to receive the call. If a phone should respond with a SIP 'temporarily moved' message or the findme/followme app playsback audio changing the call status to answered; the other phones stop ringing. The net effect of this is that when one member of a hunt group creates a forward for their phone/extension they prevent the remaining members from having a chance to answer the call. That one member 'hijacks' the entire ring group via the forward. Therefore the tl-userexten macro has been written to determine if the call is part of a ringgroup and divert to tl-userexten-rg-base instead of tl-userexten-base.
a findme/followme is, by definition, a hunt-list of its own and trying to nest hunt-lists is a good way to infinite-loop yourself.
to side-step these complications the 'other numbers to ring' section was included in the hunt list so that external numbers (such as cell phones) could be added to the ring-groups.