CallForwardOnBusyEnable Broken Obi202 - Solved (Firmware Bug)

[PlummerBob]

When CallForwardOnBusyEnable is checked and the forwarding number is set to ph.  The 1st incoming call will connect fine on ph2, the 2nd incoming call will show a "486 Busy Here" on the voip providers end.  I tried this callcentric and voip.ms.  Both are showing this on their end of their logs.  I am using FW 3741.  Has anyone else encountered this problem before and how did you resolve it?

[PlummerBob]

Problem is not present on FW 3.0.0 (Build: 3460).  Nothing changed. except flashing older firmware.

[PlummerBob]

I have contacted Obitalk support regarding this matter and they have confirmed the bug.  The temporary workaround for the affected firmwares is to set the CallFowardOnBusyNumber to the following format phX(Y) for where X is the physical port number and Y is any number, i.e "ph2(1)"