Call forward and follow me does not work when an extension is called from a hunt group.

[GoogleCodeExporter]

When a bridge is executed as user/EXTENSION@${domain_name} as it is in the hunt 
groups the dial plan for the follow me/forwarding is never executed.  The way 
to fix this would be to modify the dial string for the extension when a feature 
that requires the usage of the dialplan is enabled to use loopback.  e.g. 
<param name="dial-string" value="loopback/2014/default/XML"/>

I'm not sure how best to implement this.  This could be another field to the 
extensions table that is set by anything that would need to loopback to work 
properly.  I'm open to suggestions.

Original issue reported on code.google.com by sjthomas...@gmail.com on 11 Sep 2011 at 6:27

[GoogleCodeExporter]

It used to be that loopback complicated the call detail records by adding an 
additional entry for loopback + the actual call. Which is why loopback has been 
avoided. Before committing this change need to test CDR records when using 
loopback and make sure it doesn't make the CDR difficult to understand.

P.S. Hunt Groups will be loosing their prominence when it I've added ability to 
add external numbers as part of Call Groups.

Original comment by markjcrane@gmail.com on 12 Sep 2011 at 11:42

[GoogleCodeExporter]

Yes, when testing I noticed that it did complicate the CDR records.  I'll leave 
it alone for now as I'm able to work around by using the SIP url option on the 
hunt group if an extension need to be able to forward. 

Original comment by sjthomas...@gmail.com on 13 Sep 2011 at 5:19

• Changed state: WontFix