Got it. I'm going to implement the changes this Friday, so we'll see what happens.
But this leads me to two more questions.
First, will the protocol you described translate to a second 202? Right now, we're talking about routing from a 202 to a 100. But let's expand on the scenario, assuming both OBIs are 202s:
Phone 1, Line 1 -> Obi 1, Line 1
P1, L2 -> Obi 1, L2
P2, L1 -> Obi 2, L1
P2, L2 -> Obi 2, L2
(Recalling that lines 1 & 2 are actually connected to two separate GV numbers and would be so on both Obis).
So, I want to transfer from P1 to P2, and remain on the correct line (i.e. P1, L1 transfers to P2, L1, etc). What would be the SPx code to get that specfic? (And if I can't, that's okay, but it would be nifty if I could).
Second, and less complicated I think, is to transfer on busy P1, L1 to P1, L2, and vice versa (P1, L2 to P1, L1) thus creating a rollover/hunt effect. I understand I'd have to kill call waiting, but I assume I'd also have to reduce max sessions to 1 (or else there'd never be a busy signal to trigger the event, right?). I would think that the Obi could internally re-route the call to the second phone port without worrying about call forwarding (which GV doesn't support between GV numbers anyway).
(You have no idea how helpful this has been. If you're ever in Eugene, the first several pints of great local beer are on me!).
- Martin