I updated the OBi100 to 1.3.0 (Build: 2532), but the problem is not resolved.
With the following call forking order in the OBi110 (200123456):
Voice Services -> SP1 Service -> X_InboundCallRoute : {ph,vg5(pap2),pp(ob300123456),tg1(18708470000)}
and a calling number into SP1 of 17607058888, the OBi100 appears to receive the call with a COT of 200123456 and the wrong CallerID.
With the following InboundCallRoute in the OBi100:
Voice Services -> OBiTALK Service -> InboundCallRoute : {200123456:ph},{aa}
the PHONE Port rings with a CallerID of 200123456 and the Call History shows a Peer Number of 200123456.
With the following call forking order in the OBi110 (200123456):
Voice Services -> SP1 Service -> X_InboundCallRoute : {ph,vg5(pap2),tg1(18708470000),pp(ob300123456)}
and a calling number into SP1 of 17607058888, the OBi100 appears to receive the call with a COT of 200123456 and no CallerID.
With the following InboundCallRoute in the OBi100:
Voice Services -> OBiTALK Service -> InboundCallRoute : {200123456:ph},{aa}
the PHONE Port rings with no CallerID and the Call History shows a Peer Number of 17607058888.