Having trouble placing or receiving calls or using your voicemail system on Ooma Telo VoIP Phones? Post your questions here.
#90515 by AzJazz
Fri Dec 09, 2011 8:45 am
thunderbird wrote:Also have you gone into Ooma Setup and clicked on the Bluetooth tab and added check marks to both boxes that are shown?


Hi, T-Bird! Yes, both boxes are already enabled in my Bluetooth setup.
#90518 by thunderbird
Fri Dec 09, 2011 9:03 am
AzJazz wrote:I am having the same issue as lavulavu and lightstorm. By pressing *15 in front of the phone number I can have the call transferred to my Bluetooth Headset.

However, once connected to the BT headset, I can not get a passcode properly recognized when I type it in on the phone handset.

Even if I add the passcode to a manually entered number before pressing "dial", the call gets transferred to the BT headset before the passcode is sent to the conference call.

I can get all this to work with a Telo Handset, but my Telo Handset is out-of-commission for a little while until I finish soldering a new connector onto my replacement battery pack.

Has anybody figured out a way to do this with a regular phone? Is there any other way to transfer a call from a regular phone handset other than the *15 prefix?

Cheers,

AzJazz

Something to try:
I wonder if when you dial *15 if you also add the passcode right after *15 at the same time.

If dialing *15 and the passcode in one string doesn't work:
My phone also allows me to add pauses, which could be entered between *15 and the passcode.

Example *15 pause, pause, passcode.

I would try one pause, then two pauses, then three pauses to find the correct timing.
#90617 by AzJazz
Mon Dec 12, 2011 12:22 pm
thunderbird wrote:Something to try:
I wonder if when you dial *15 if you also add the passcode right after *15 at the same time.

If dialing *15 and the passcode in one string doesn't work:
My phone also allows me to add pauses, which could be entered between *15 and the passcode.

Example *15 pause, pause, passcode.

I would try one pause, then two pauses, then three pauses to find the correct timing.


Thanks for the suggestions thunderbird, but unfortunately that didn't work.

Ooma's Bluetooth transfer implementation seems to work like this:

1) Enter *15+Phone Number+Passcode on the non-Telo phone.
2) Press "Dial" on the phone.
3) The Ooma Telo station rings the BT headset, waiting until the BT headset connects. (Note: The phone keeps dialing as if nothing has happened, of course). This is important - The call has NOT started yet. The Ooma Telo is just negotiating the connection to the BT headset at this time.
4) Press the "Answer" button on the BT headset.
5) Ooma Telo transfers the connection to the BT headset, and - This is important - the phone disconnects from the call, so that only the BT headset is connected. So, any pre-dialed numbers get lost at this point.
6) Ooma Telo then starts dialing the phone number originally entered above. The call completes on the BT headset. The passcode seems to get lost, even if it was actually dialed by the phone after the pauses.

Sigh.
#90623 by thunderbird
Mon Dec 12, 2011 2:28 pm
AzJazz wrote:
thunderbird wrote:Something to try:
I wonder if when you dial *15 if you also add the passcode right after *15 at the same time.

If dialing *15 and the passcode in one string doesn't work:
My phone also allows me to add pauses, which could be entered between *15 and the passcode.

Example *15 pause, pause, passcode.

I would try one pause, then two pauses, then three pauses to find the correct timing.


Thanks for the suggestions thunderbird, but unfortunately that didn't work.

Ooma's Bluetooth transfer implementation seems to work like this:

1) Enter *15+Phone Number+Passcode on the non-Telo phone.
2) Press "Dial" on the phone.
3) The Ooma Telo station rings the BT headset, waiting until the BT headset connects. (Note: The phone keeps dialing as if nothing has happened, of course). This is important - The call has NOT started yet. The Ooma Telo is just negotiating the connection to the BT headset at this time.
4) Press the "Answer" button on the BT headset.
5) Ooma Telo transfers the connection to the BT headset, and - This is important - the phone disconnects from the call, so that only the BT headset is connected. So, any pre-dialed numbers get lost at this point.
6) Ooma Telo then starts dialing the phone number originally entered above. The call completes on the BT headset. The passcode seems to get lost, even if it was actually dialed by the phone after the pauses.

Sigh.

First why does the Bluetooth headset have a passcode? Is it the inital link passcode that you enter in Ooma Setup when the first pairing is done at http://172.27.35.1/bluetooth.lp ?
#90632 by thunderbird
Mon Dec 12, 2011 4:39 pm
lbmofo wrote:I think AzJazz is talking about passcode to join a bridge?

Check this out: viewtopic.php?t=8074

In that case can't the bridge call be established using the phone to dial the phone number and passcode, then use *15 to transfer the established call, from the phone to the Bluetooth headset???
#90650 by AzJazz
Tue Dec 13, 2011 2:10 am
thunderbird wrote:
lbmofo wrote:I think AzJazz is talking about passcode to join a bridge?

Check this out: viewtopic.php?t=8074

In that case can't the bridge call be established using the phone to dial the phone number and passcode, then use *15 to transfer the established call, from the phone to the Bluetooth headset???


Hi, guys!

Yes, the "passcode" is to join a conference call. My Bluetooth headset is already paired with the Ooma Telo base station.

Thunderbird, I tried variations on your suggestion of making the call first, then dialing *15. I still couldn't get it to work. Either the *15 was just "*15" tones heard by the call already in progress, or the "*15" attempted to do a BT transfer from my second Ooma phone number/line. Neither way worked for the call on "Line 1".

AzJazz
#90651 by thunderbird
Tue Dec 13, 2011 4:56 am
AzJazz wrote:
thunderbird wrote:
lbmofo wrote:I think AzJazz is talking about passcode to join a bridge?

Check this out: viewtopic.php?t=8074

In that case can't the bridge call be established using the phone to dial the phone number and passcode, then use *15 to transfer the established call, from the phone to the Bluetooth headset???


Hi, guys!

Yes, the "passcode" is to join a conference call. My Bluetooth headset is already paired with the Ooma Telo base station.

Thunderbird, I tried variations on your suggestion of making the call first, then dialing *15. I still couldn't get it to work. Either the *15 was just "*15" tones heard by the call already in progress, or the "*15" attempted to do a BT transfer from my second Ooma phone number/line. Neither way worked for the call on "Line 1".

AzJazz

Ooma Quotes: "In Ooma Setup, click the Bluetooth tab. Do both of the check boxes have a check mark?

The Bluetooth Settings page allows you to manage the Bluetooth configuration of the Ooma Telo. In order to use these settings, you must have an Ooma Bluetooth Adapter installed, and have an active subscription to Ooma Premier.

For more information about configuring Bluetooth devices with your Telo, please see the Bluetooth Setup Guide.

Headset Bluetooth transfer

https://www.ooma.com/app/support/bluetooth-setup-guide", End of Ooma Quotes.

I noticed that some people are also having problems joining a conference call without using a Bluetooth headset.
If nothing works, contact Ooma Customer Support:

Customer Support
Email: support@oomacare.com
Phone: 1-888-711-OOMA (6662)
Monday-Friday 7am-7pm PST
Saturday-Sunday 8am-5pm PST

Please let the Ooma Forum know how you come out.
#90769 by AzJazz
Wed Dec 14, 2011 2:51 pm
I called Ooma Tech Support yesterday. Based on their request, I did a couple of failed connection attempts to a conference call while my BT headset was connected, and notified Ooma of the times of the calls.

They are analyzing and investigating. I hope that they will notify me of what they found. I will call back in a few days to see if there are any updates.

I'll let you (all) know what I hear.

Cheers,

AzJazz
#90963 by AzJazz
Wed Dec 21, 2011 11:42 am
Ladies and Gentlemen ... We have a solution! Ooma Technical Support worked hard with me to find this solution (Thanks, Claudina - and others - who helped me with this!)

Notes:
  • This may only work for Premium accounts, since it requires a second line. I have not checked if the BT adapter is supported on Basic subscriptions.
  • I am using a Jawbone Icon BT headset. I do not know if this problem is related to the BT headset model, but it certainly was a problem with mine.
  • If you continue to have problems with this, contact Ooma Technical Support.
Here is what you need to do:

  1. From your regular telephone handset: Press *05.
    Note: Your BT headset will ring.
  2. From your BT Headset: Answer the BT headset.
    Note: This will initiate a intercom between your telephone handset and the BT Headset on Telo Line 1
  3. From your regular telephone handset: Press "Flash/Talk".
    Note: This will transfer the telephone handset to Telo Line 2. You should hear a dial tone in your telephone handset.
  4. From your regular telephone handset: Dial the number you want to reach.
    Let the call answer. You do not need to dial any access codes at this time.
  5. From the Telo Base Station: Press the "1" and "2" buttons simultaneously.
    Note: This will put Telo Line 1 and Telo Line 2 into a local conference call.
  6. You can now continue to enter whatever DTMF codes you need into your telephone handset.

Let us know if this works for you!

Cheers,

AzJazz

Who is online

Users browsing this forum: No registered users and 10 guests