According to documentation (OBi Device Administration Guide v31.03.11, p.113-114) there are no restriction/exceptions to what terminal arguments are/work in InboundCallRoute.
In plain words, there is no mention on those pages that terminal arguments of the form
cid>target (where
cid is a literal string or $1) are not allowed or do not work when target is another OBi device.
I just wasted a lot of my time scratching my had as to why the documented feature does not work as advertised
until I stumbled on this thread.
This means that, according to official documentation, we are dealing with a bug that needs to be fixed, or documentation is disseminating false and unreliable information.
I for one hope we are dealing with a bug that will be dealt with promptly, otherwise I wasted money on a dozen OBi's that are now useless. An here I was under impression I was making an informed decision by reading the official documentation