2talk and Yealink BLF

Forums › VoIP › 2talk and Yealink BLF

hasole

384 posts

Ultimate Geek

#167413 12-Mar-2015 19:18

has anyone got this going? I've been messing with this t26p and not having much luck.

chevrolux

4962 posts

Uber Geek
+1 received by user: 2638
Inactive user

#1257408 12-Mar-2015 19:41

I've had it working on later model t4x phones but it works in exactly the same way on any model.

One thing to make sure is you are registering to the problem number and not an 'extension' number you may have set on it. The other stipulation is that everything is on the same network, as in you will not be able to monitor a soft phone on a mobile network when your t26 is sitting on your 'landline' connection.

CYaBro

4708 posts

Uber Geek
+1 received by user: 1182

ID Verified

Trusted

#1257451 12-Mar-2015 20:23

Make sure you've enabled BLF on the line/s, or the whole account, via the 2talk cloudPBX setting.

In the Yealink webconfig go to the Advanced section for the accounts/lines you want to be able to monitor with BLF and enable 'Subscribe for MWI'. (Pretty sure this is the setting that is required, I haven't actually done proper testing after I got it working :))
On the phone you want the BLF go to the DSSKey tab, set the type to BLF, and in the Value box put in the full 2talk number you want to monitor.
Make sure the correct line is selected and I think the extension box can be empty but you may need to create an extension number in the 2talk cloudPBX for each line and then put the appropriate extension number in here.

That should be it.
You may need to reboot the phones for it to start working.
The LED for that DSSKey should be green when the line is free and red when it is busy.

You can also transfer calls to those BLF numbers using those DSSKeys now and by default it will be a blind transfer but you can change this in the Yealink webconfig settings under Features - Transfer.

Opinions are my own and not the views of my employer.

hasole

384 posts

Ultimate Geek

#1257579 13-Mar-2015 06:50

Thanks a lot!

Never would've found the mwi. All working now.

cyril7

9073 posts

Uber Geek
+1 received by user: 2499

ID Verified

Trusted

Subscriber

#1871898 24-Sep-2017 11:36

Hi, just had this unlocked as I have an issue with exactly this, using T27G handsets, have enabled BLF in the 2Talk interface, all handsets are on the same account behind the same router. Have set the DSS key to BLF, entered the full 028.. number in the value, and also have the extension number in the ext field (might try remove that). Oh and should mention subscribe for MWI is enabled on handsets that are to monitor activity.

In the past I have had BLF working just fine with Cisco SPA50x handsets with extention consoles, and this is the first time I have tried the yealinks, which other than this have proven to be great handsets, there are >40 in this current deployment, most are T19 and W52, but main reception phones are T27G with E20 expansion units.

One odd thing that is across all handsets, the phones show in their web interface that they are registerd, and are all making and receiving calls, infact have been successfully working all last week, but all of them show as offline in the 2Talk web interface, this may infact be the core of the issue.

So any thoughts.

Cheers Cyril

chevrolux

4962 posts

Uber Geek
+1 received by user: 2638
Inactive user

#1871940 24-Sep-2017 12:48

One odd thing that is across all handsets, the phones show in their web interface that they are registerd, and are all making and receiving calls, infact have been successfully working all last week, but all of them show as offline in the 2Talk web interface, this may infact be the core of the issue.

Definitely would raise a ticket on that. Two weeks ago there was a big database issue that mucked up a whole lot of features. The most obvious symptom for me was not seeing any lines online in our portal (we use them mainly as a SIP trunk provider rather than Cloud PBX). But more importantly, it affected the use of feature codes (got confirmation of the feature code being dialed but nothing actually got set).

cyril7

9073 posts

Uber Geek
+1 received by user: 2499

ID Verified

Trusted

Subscriber

#1872006 24-Sep-2017 13:34

Hi Sam, longtime no hear, yep that was my next step to raise a ticket, hopefully they have logs that can reveal why its not showing as registered, and my guess is once that is sorted it will start pumping out the BLF notifications. But just checking in case someone here might have seen this behavior before.

Cheers

Cyril

New World

Shop on-line at New World now for your groceries (affiliate link).

CamH

615 posts

Ultimate Geek
+1 received by user: 327

Subscriber

#1872008 24-Sep-2017 13:38

It'd be interesting to hear how you get on with this - we had BLF working at a client on Yealink phones that suddenly stopped about 6 months ago. Haven't been able to get it working since.

CYaBro

4708 posts

Uber Geek
+1 received by user: 1182

ID Verified

Trusted

#1872044 24-Sep-2017 14:09

I’ve found that all you need to do is enable blf in the 2talk cloud settings.
Try disable and enable it again too if you’re having issues with it.
Then set the dss keys to blf, put in the full phone number for the extension and I put *89 in the extension field, as that allows you to press the button to answer a call if that extension is ringing.
That’s all you should need to do.
It can take a few minutes for the led to light up after it’s been configured.

Opinions are my own and not the views of my employer.

CamH

615 posts

Ultimate Geek
+1 received by user: 327

Subscriber

#1872048 24-Sep-2017 14:20

Thank you so much! I disabled and re-enabled in the 2talk panel and it just started working. Office phones lit up again and all is working!

cyril7

9073 posts

Uber Geek
+1 received by user: 2499

ID Verified

Trusted

Subscriber

#1872065 24-Sep-2017 14:58

Thanks for the tip will try tomorrow when back onsite

S