Quote from: jimates on March 07, 2011, 08:42:49 AM
Which ever unit connects last is the one that rings.
I figured that would happen - it's the last one to register that Google Voice sends the calls to. I think the only way to get what you want is to set up a master/slave relationship between the two units. When a Google Voice calls comes into the "master" unit, you set the X_InboundCallRoute to send it to both the local phone port and to the OBiTALK number of the "slave" device - I am not sure of the exact syntax for doing that off the top of my head, but I'm sure it's doable. Also, you would want to route incoming OBiTALK network calls FROM the slave device calls fitting the pattern 1 XXX XXX XXXX to SP1 (assuming Google Voice is on SP1).
On the slave device, you could route outgoing calls fitting the above pattern to the OBiTALK number of the master device. So basically there would probably be three settings that would have to be changed:
The X_InboundCallRoute setting for SP1 on the master device
The InboundCallRoute for the OBiTALK service on the master device
The PHONE port outbound call route on the slave device
I'm not 100% sure that incoming caller ID would pass through from the master to the slave device on incoming calls, but my guess is that it would. As I say, the only thing I don't know offhand is the exact patterns those settings would need to be, particularly since you'd only want to accept outgoing Google calls from the "slave" unit and not just anyone that happens to send a call to your OBiTALK number, and also I'm not sure how to preserve the original dialed number in such a scenario so that you can pass it through to the master device. Of course you can always call the "master" unit, get the device's auto attendant menu, and make your call that way, but I'm just thinking it may be possible for you to dial a call in the usual manner on the "slave" device, and have it forward that call to the "master" device, so the operation is more transparent to the "slave" device user.