Thanks, I think I'll disable it and see. I use Phone Power on SP1 and GV on SP2. I don't think Phone Power tries to manage the obi100 directly--the setup was done via the Obi site's link.
It's just clearly simpler to make changes locally and know what I set is what is happening. The digit map I got with Phone Power was awful. Several things were repeated in the same string. I always had a 10 second or so wait after dialing before the call went out.
I wanted outbound calls to go via GV so they showed in my GV call history. 911 outbound needs to be via PhonePower. I ended up with:
outbound call route: {911:sp1},{([1-9]x?*(Mpli)):pp},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**9:>(Mpp)):pp},{(Mpli):pli} Only thing I changed in this was removing 933 as that doesn't do anything with Phone Power.
Primary Line: SP2 Service
Profile A Digit Map: (911S0|*xxS1|**xx.S1|***xx.S1|1xxxxxxxxxx|<1336>[2-9]xxxxxx|<1>[2-9]xxxxxxxxx|)
Profile B Digit Map: completely blank I read that the obi looks at a combination of the above so I figure why put the same string in both. I guess I'll see if it works.
All inbound calls are from GV and forwarded to my obi via PhonePower instead of GV as it adds Caller Name. If GV stops handling outbound calls then I'll just change the primary line to SP1.
P.S. I really wish Obi would put something a bit more descriptive in those little help messages that show when hovering over the blue question mark.