Landline Call Forwarding
jimates:
Tack,
The Obi takes the incoming land line call and uses your GV service to forward the call to your GV number. Since the call from the Obi is an outgoing call it carries the caller id of the service used to place the call (GV). GV receives the call with it's own caller id and (because of settings you your GV account) sends the call directly to the IVR.
You can change the settings in your GV account so that it will treat the incoming call the same as all other calls.
On your GV page click on your phone number.
Click "edit" for the GoogleChat phone.
Select "NO" for voicemail access.
"YES" is the default setting for all mobile phones and googlechat listed in your phones list. You will also need to change the settings for the mobile phones if you want to call your Obi (google voice number).
Tack:
Firstly, Ron's been very responsive and helpful to me on multiple occasions, so, even if there is a more concise answer, here, I welcome and appreciate all his support.
Regarding your comment on changing Google settings, I am not sure this would achieve what I wanted, but you may correct me if I am wrong. It was merely my desire to have landline calls arrive at my Google phone, complete with their origianl incoming caller ID's, and either be answered by me on Google or find their way into Google voicemail, if unanswered.
Even with your suggestion, I am assuming that since Obi is bridging by using Google Voice to make the transfer, then, Google Voice would see it's own caller ID, not the outside, even if voicemail access was turned off. Yes?
In the end, I think this entire problem is going to be obviated because I am going to utilize voip.ms for main communications, pricipally because I, and my callees, have found the obi-outward voice quality of Google Voice to be substandard. I can hear them all perfectly, but they hear me a bit choppily. I think this problem is likely to be extinguished with voip,ms. (We'll see.)
Thanks again.
jimates:
Correct, Obi does not pass the caller id of the original call, all calls would carry the GV caller id.
RonR:
Quote from: jimates on July 28, 2011, 07:40:30 pm
The Obi takes the incoming land line call and uses your GV service to forward the call to your GV number. Since the call from the Obi is an outgoing call it carries the caller id of the service used to place the call (GV). GV receives the call with it's own caller id and (because of settings you your GV account) sends the call directly to the IVR.
When you call your own Google Voice number from your Google Voice trunk, no call is placed through the PSTN. The call never leaves Google Voice. It's as I stated in Reply #7 : Google Voice is being asked to a call a telephone number which it recognizes as the telephone number of the account initiating the call. Google Voice treats this case as a request to check voicemail.
If you doubt this, call your own Google Voice number from your Google Voice trunk. Then log into your Google Voice account and look at the Call History. You'll find there was no call Placed and no call Received.
Quote from: jimates on July 28, 2011, 07:40:30 pm
You can change the settings in your GV account so that it will treat the incoming call the same as all other calls.
On your GV page click on your phone number.
Click "edit" for the GoogleChat phone.
Select "NO" for voicemail access.
You'll find this has no effect for the reason stated above.
What were you saying about posting useless statements? :)
jimates:
The op was about bridging land line calls to GV. This is being done by routing the land line call TO GV using the GV service resulting in delivery to the IVR.
Picking up the phone and calling your GV using the GV service gives the same results, but is not exactly the same (only the same as the last half of the route).
Yes, I made a mistake about the changes at GV to solve the problem.
Tuck has so many posts about the same problem all over this board. I just think a little explanation along with the advise would be appropriate when it is obvious there is a misunderstanding about how it is working to start with.
Navigation
[0] Message Index
[#] Next page
[*] Previous page