Hello again!
I decided to test Anveo on the 110 before swapping it out for the newly-arrived 202. Glad I did, as I think it helped me understand some of the behaviors, as well as some of the earlier posts.
At the risk of being simplistic, let me start by restating what's probably obvious to most people on the forum:
1) When my alarm is tested (or set off), it dials out to an 800 number using whatever it's physically connected to [regardless of whether the SP is e.g. Google Voice or Anveo].
2) If that connection is to an OBi ATA, that means it will use whatever primary SP is associated with that physical port (just like any non-prefixed outbound call).
3) On the other hand, in cases where Anveo is configured as one of the SPs, 911 (or 933) calls will go out over a primary line, EVEN IF Anveo is actually set up as non-primary.
OK - kindly advise if any of the above is incorrect.
So far, so good. Whenever GV is designated as the primary line on the 110, the alarm dials out just fine [Anveo is non-primary]. Results are less consistent the other way around, depending on which of my two GV accounts is used for SP2.
My hypothesis is that the alarm can only dial out with Anveo as primary if the phone number of the non-primary (in this case GV) line is actually listed under "Your Phone Number" on Anveo's "Web Call" page. Otherwise, Anveo's call log still shows that the number was dialed, but the alarm test fails.
This may be unimportant if Point 3 above is correct, because then I'll just associate a dedicated, non-published GV number with the alarm; and let Anveo route 911 calls wherever it wants. Nonetheless, I'd still like to know if I'm understanding correctly.
And I'm still a bit confused about what this means for physically setting up the 202. I don't mind if my two published GV numbers can't be used simultaneously; so long as the third unpublished GV account is constantly accessible to the alarm.
Thanks for taking the time to read, correct and advise!