Line port use breaking Call Return (*69) feature?

<< < (2/2)

RyanG:
Your understanding is correct. I did make the change so that all outgoing calls, including *69 ones, would use SP1 and not the PSTN line since I cannot make long distance calls on my PSTN line. I can make 911 on the PSTN line though and this is the reason I want it connected to Obi.

Let me demonstrate something else that I have a question about and may shed some more light.

With PSTN line connected to obi line port, I call my GV number. I look in the call history and see this:

Call 2   03/19/2012    22:43:23   
Terminal ID   LINE1   PHONE1
Peer Name      
Peer Number      
Direction   Inbound   Inbound
22:43:23   Ringing   <------Note that it's ringing on LINE1
22:43:25   End Call

I disconnect PSTN line from obi line port and make another call. Here's what the history shows:

Call 1   03/19/2012    22:45:22   
Terminal ID   GoogleVoice1   PHONE1
Peer Name      
Peer Number   18185701293   
Direction   Inbound   Inbound
22:45:22   Ringing   
22:45:24      Call Connected
22:45:37   End Call

Can you figure why it rang on LINE1 even though I called my GV number and *not* my PSTN? I want it to ring on GoogleVoice1 if it call my GV number.

RonR:
Do you have Google Voice set to ring your PSTN number in addition to Google Chat?  That could account for the symptoms you're describing.

RyanG:
Brilliant! Thank you Ron!

My GV account was set to ring both my land line number and Google Chat. I unchecked the land line number and that fixed the Call Return problem.

Another problem this fixed is whenever I have the land line connected and receive a call, I'd always hear a brief tone followed by two sharp beeps (similar to the Obi call waiting notification). It would never happen when I didn't have the land line connected. I believe this was happening because Google was ringing my Google Chat subsequently which got routed to Obi as a call.

Navigation

[0] Message Index

[*] Previous page