Guess this one stumped the forum. Thought I'd close the loop on the resolution in case anyone comes across this again.
The situation was a re-configuration of SP2 for CallCentric 911 on a 2 year old Obi110 that had previously had CallCentric 911 configured. While I could never figure out the fault (outbound call routing and digit maps were correct), best I could figure some conflict arose when I checked the "this device is capable of 911" (paraphrasing) box on the SP2 config wizard in Obitalk WebGUI. I guess when I had done the manual call routing configuration a couple years back that maybe I did that in the device portal and not in ObiTalk, and thus this 911 reconfiguration caused a config conflict resulting in the immediate call drop behavior.
At any rate, simple fix.
1. I deleted my CallCentrc config on SP2
2. Then went into ObiExpert config in ObiTalk and reset all configs for "Voice Service --> SP2" and "Physical Interfaces --> Phone" back to "ObiTalk settings" (by pushing the little "revert all to ObiTalk settings" button at the bottom of the page and then pressing "submit")
3. Exited ObiExpert and went back into the ObiTalk portal and configured CallCentric as usual for 911 service on SP2.
Everything worked fine after that.
