Jump to content

Yealink not being able to place a call on a Park Orbit account


Carlos Montemayor

Recommended Posts

Hi,

 

I have not been able to place a call in Park Orbit using a Yealink phone. Curiously, if I do place a call on Park Orbit using a snom phone, the Yealink can pick up the call with no problem. Is there a feature that I should change on the Yealink so it can place a call on Park Orbit? I am using the latest firmware on the Yealink and the phone was configured using plug and play.

 

 

Link to comment
Share on other sites

Oh, no, no, no. I am using *85 all along. I meant, that under the exact same circumstances, *85 works fine with a snom 710 but not on the Yealink. Also, if the call is already parked (by the snom, which is the one that could do it) the Yealink has no problem to pick it up by using *86.

 

Checking on the park orbit preference, it is blank. Nothing is in the box.

 

What should I do?

Link to comment
Share on other sites

It works with the snom 710 but not with the Yealink. I have tried with and without dialing the exact park orbit. In my case, I used account 66, so I tried *8566 ok which did nor worked. As I said earlier, *8666 ok, did work (pulling the call out of the park orbit.

 

If it were not that pulling the call out of park orbit (as well as listening to voice messages) was working using the Yealink, I would say that the probable cause of the problem would be a wrong DTMF configuration. I cannot say that because retrieving the call and other DTMF managed functions do work. So, I would suspect of something that has to do with DTMF but that only happens during a call being on hold (the procedure indicates to first put the call on hold and then dialing *85). The other thing would be the permissions. I have not written anything there, although it does not prevent the snom 710 of doing the park.

 

What should I do?

Link to comment
Share on other sites

  • 2 weeks later...

Is there something we can change in the configuration of the phone? or a workaround? Is it something that could be fixed in a future firmware release?

 

Thanks

 

Have you tried just transferring to the park orbit? If the park orbit was 123 then transfer to 123, that is how I have grandstreams do it.

Link to comment
Share on other sites

  • 4 weeks later...

Had not tried before, but I just did after reading your post. It hurts not to have thought of that, but mighty glad that you did. It works!!

 

It only misses the message (the one that tells you that you have placed the call on park orbit), which would be nice but that is something one can live without.

 

Thanks!!

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...