@p2voice:
Circle of trust is primarily for Obi Endpoint-Obi Endpoint(via obitalk) trusted communication.
ObiEndpoint=Softphone or Obi Device.
Trusted callers is primarily for Google Chat users and Cellphone/landline/googlevoice numbers(Or in other words end points that can reach any of your trunks{sp1/sp2/li etc}).
In your specific case, he doesn't even have to call google voice and then get attendant to then subsequently call out. in his obitalk account, he can add your device as "default gateway" against his softphone number(your Obi device will show up in the dropdown when added to COT).
Once added,to make a call via ObiON, he can directly call the final destination number. it will go through the default trunk configured in your Obi.
you can get more fancy and provide options for the user to use ANY(not just default) of the trunk and gateways configured in your Obi.
to do that: you can change the Obitalk inbound call route to something like this:
the below is a sample for understanding:
{(Mcot)>(Msp2):sp2},{(Mcot)>(<**1:>(Msp1)):sp1},{(Mcot)>(<**2:>(Msp2)):sp2},{(Mcot)>(<**3:>(Mvg3)):vg3},{(Mcot)>(<**4:>(Mvg4)):vg4},{(Mcot)>(<**6:>(Mvg6)):vg6},{(Mcot)>(<**7:>(Mvg7)):vg7},{(Mcot)>(<**8:>(Mli)):li},{(Mcot)>(<**9:>(Mpp)):pp},{(Mcot):aa},{ph}
Where MCot= user defined digitmap that contains your friends number
This way he can use all your Trunks and Gateways that you may have configured in your OBi Device
using **1 <Number>, **2<Number> etc.
Note that when your friend makes a call via Obion, the call comes in via obitalk network and the ObitalkInboundCallroute in your obi device determines what to do with the call.this is where you can write your different rules to enable more functionality for your friend.