I use an OBi202 with
VoIP.ms. You may find my notes helpful (link at bottom)...
>>Phone 1 – keep
voip.ms DID for incoming calls and e911....route outgoing calls to google voice so we are not paying for these calls. Can I make my outgoing caller ID be my incoming DID number?
See my notes for Google Voice concerns.
You can route sp1/VoIP.ms inbound to PH1. You could set PH1 Primary Line to TG1 = sp2,sp1 where sp1 is
VoIP.ms and sp2 is GV1. Then be sure the trunk digit maps are properly defined... sp1 allows
VoIP.ms dialing; sp2 allows GV dialing. Outbound will default to sp2/GV1 and failover to sp1/VoIP.ms. 911 will only be defined in the sp1 digit map and will only go out sp1. All good.
Unfortunately, GV will not let you spoof your CallerID (nor block CallerIDs). This is a problem for your plan. At best, you may want 2 GV accounts, 1 for your outbound and 1 for their inbound/outbound... but this does not fix your outbound CallerID problem. Maybe you can afford using only
VoIP.ms and they only use GV1 except for your 911... then no spoofing required... but they may not be able to block telemarketing calls on GV.
>>Phone 2 - get a new phone number from Google Voice for my in-laws and use this for incoming and outgoing calls...however I would like to route e911 to use the
voip.ms e911 that will be configured for phone 1 above.
Similar to above... route sp3/GV2 inbound to PH2. Set PH2 Primary Line to TG2 = sp3,sp1 where sp1 is
VoIP.ms and sp3 is GV2. Then be sure the trunk digit maps are properly defined... sp1 allows
VoIP.ms dialing; sp3 allows GV dialing (same digit map as for sp2). Outbound will default to sp3/GV2 and failover to sp1/VoIP.ms. 911 will only be defined in the sp1 digit map and will only go out sp1. All good.
>>Does this configuration make sense? Any suggestions on improving or configuring this would be greatly appreciated!
Yes, except not being able to spoof the GV CallerID is a problem... as you have found out already, you want to keep your solution(s) separate and independent... except for 911.
Consider using the trunk groups for outbound... they provide automatic failover and routing... very cool, imo.
>>I followed the
voip.ms configuration sample and they recommended disabling obitalk and configuring it manually.
I also do not use the OBiTALK Cloud. However, after OBi2 Series v3.0.1 Build 4367, you must use OBiTALK Provisioning to configure for GV.
OE