Yealink Forums

Full Version: BLF no work in Unify OpenScape Business
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hello, I need help to configure DSS keys, the BLF does not work, I am connecting a T29G phone V 46.83.0.35 to Unify OpenScape Business X5 V2 R5.

someone has already done it, I need help.
Hi Mario,

This is Evan from Yealink Support Team, nice to know you here!

This is a known issue. Yealink phones and Unify PBX are incompatible in the event type of BLF.

For Unify OpenScape PBX, the event type of BLF notify is keyset-info, it is a special signaling.
For Yealink or other brand phones, the event type of BLF subscribe is dialog or presence.

When the phones send a BLF subscribe with dialog out, it won't be recognized and access won't be granted. And the phone will get the 403 Forbidden from Unify server side.

For the present, we can’t support it, sorry. Is there any project that MUST need this feature ? Mandatory feature request?

Please let me know if anything I could help.

Best Regards,
Evan
(07-31-2018 02:06 AM)Evan_Yealink Wrote: [ -> ]Hi Mario,

This is Evan from Yealink Support Team, nice to know you here!

This is a known issue. Yealink phones and Unify PBX are incompatible in the event type of BLF.

For Unify OpenScape PBX, the event type of BLF notify is keyset-info, it is a special signaling.
For Yealink or other brand phones, the event type of BLF subscribe is dialog or presence.

When the phones send a BLF subscribe with dialog out, it won't be recognized and access won't be granted. And the phone will get the 403 Forbidden from Unify server side.

For the present, we can’t support it, sorry. Is there any project that MUST need this feature ? Mandatory feature request?

Please let me know if anything I could help.

Best Regards,
Evan

Hi Evan

I find myself in a similar situation as Mario, we also have a customer on Unify Openscape Business who likes the T46 Handsets and when testing we are unable to get the BLF to notify when an extension is busy or allow us to use the pickup functionality which is core to this customers business.

Do you know if this has been progressed since Mario's initial ticket, if not is there anyway we can request this as a change request.

The customer is holding off purchasing the T46 handsets until we have this issue resolved otherwise we may need to supply them with Unify handsets.

Thanks in advance


Kind Regards
Michael
(01-22-2019 05:25 PM)Mikester123 Wrote: [ -> ]
(07-31-2018 02:06 AM)Evan_Yealink Wrote: [ -> ]Hi Mario,

This is Evan from Yealink Support Team, nice to know you here!

This is a known issue. Yealink phones and Unify PBX are incompatible in the event type of BLF.

For Unify OpenScape PBX, the event type of BLF notify is keyset-info, it is a special signaling.
For Yealink or other brand phones, the event type of BLF subscribe is dialog or presence.

When the phones send a BLF subscribe with dialog out, it won't be recognized and access won't be granted. And the phone will get the 403 Forbidden from Unify server side.

For the present, we can’t support it, sorry. Is there any project that MUST need this feature ? Mandatory feature request?

Please let me know if anything I could help.

Best Regards,
Evan

Hi Evan

I find myself in a similar situation as Mario, we also have a customer on Unify Openscape Business who likes the T46 Handsets and when testing we are unable to get the BLF to notify when an extension is busy or allow us to use the pickup functionality which is core to this customers business.

Do you know if this has been progressed since Mario's initial ticket, if not is there anyway we can request this as a change request.

The customer is holding off purchasing the T46 handsets until we have this issue resolved otherwise we may need to supply them with Unify handsets.

Thanks in advance


Kind Regards
Michael

Hi Michael, how are you today?

Thanks for your feedback this issue,now can you please report your question to our ticket system with the issue detailed description? Then we can assign a support engineer to follow up your question, I think it will be better/faster to fix this issue.

You can access to our ticket website, then create a new ticket here.
https://ticket.yealink.com

Best Regards,
Evan You
Reference URL's