Mango,
I did some testing of call forwards that may shed some light on what works and what doesn't. I setup a outbound test call on SP2, then with another phone, not on the OBi, I called the DID registered on SP2.
On the OBi ITSP Profile I had
X_Use302ToCallForward disabled. It is enabled by default. The only way I could get Call Forward on Busy to work is to forward by bridging the call out SP1, not SP2 or not by any other VG tied to SP2. Otherwise the OBi returns the sip 486 Busy Here that you reported. It did work if I forwarded to a number out the other SPx.
I was calling from CallCentric to a
voip.ms DID. If I enabled the default
X_Use302ToCallForward on the ITSP Profile the call forwarding worked because the calling server accepted the sip 302 Moved Temporarily. To the incoming call the OBi returned Sip 302 Moved Temporarily with the forward number in the Contact field and the
voip.ms calling server honored the request and completed the call. The number I was forwarding to was a toll free 1-800+ number. I also tried it to a 1+ pstn number. It also worked and the per minute charge showed up in the
voip.ms history file. I further tried it to a pure sip uri forward. The OBi returned the 302 Moved to
voip.ms server, but
voip.ms sent a 503 Service Unavailable to the original call who got a busy signal.
