Number of things could be at play here - first thing to check is to make sure the handler's transfer rules are correct. It's a good idea to set the alternate transfer rule to active and set it to ring the phone you want. Assign an extension to the call handler (this can be removed later -just for testing) and then call into the opening greeting - dial the extension and make sure it sends the call to the right phone. If that's already working then the problem gets much simpler. If not, let us know and we'll go a different route.
Assumig the "straight" transfer is working, I'm assuming the problem is transfer over ride. When a call forwards into Unity or Connection (they both behave the same) the first call handler it hits it will force the transfer rule for that handler to be skipped. This is done to prevent deadly transfer loops which can (and have in the past) taken systems down. Not good. So if you have "1234" assigned to you call handler and you have calls forwarding in from 1234 and you want to then "boomerang" the call back out you'll have to use two call handlers to do it. Call handler with extension 1234 in that case would have an alternate greeting set to active and has it's source set to "blank" and an after greeting action set to "ring phone for" another call handler that is setup to ring the phone.
This has the effect of clearing the "new call" flag so Connection is allowed to process transfer rules on the next call handler it hits.
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...