New Year, New Question

Status
Not open for further replies.
Nov 30, 2017
34
4
8
60
Toronto, Canada
Happy New year group, let health, and prosperity be in abundance.

I am trying to put dss/blf on my Yealink T-46 and T-29.
1) in device I program a line, then key 10, then type BLF. Value in this case 23
2) recycle the power, my key is now identified,and my light is green. and I can "one touch" to ext 23 by pressing said button.

BUT
light does not turn red when extension in use.

Any answers would be helpful.

thanks again,

Howard
 

Adrian Fretwell

Well-Known Member
Aug 13, 2017
1,417
376
83
In case it helps I have BLF working on a T23G, it was provisioned from FusionPBX
below are a couple of screenshots from the Devices page and the phone itself:
Device-settings-T23G.png

Phone-setttings-T23G.png
 
Nov 30, 2017
34
4
8
60
Toronto, Canada
Happy New year group, let health, and prosperity be in abundance.

I am trying to put dss/blf on my Yealink T-46 and T-29.
1) in device I program a line, then key 10, then type BLF. Value in this case 23
2) recycle the power, my key is now identified,and my light is green. and I can "one touch" to ext 23 by pressing said button.

BUT
light does not turn red when extension in use.

Any answers would be helpful.

thanks again,

Howard

thanks Adrian,

I had this variation, and my keys are solid green, the dss works, but when the person is on the phone, it is not red. Is there something in default settings in Fusion that maybe has to be changed?
 

Adrian Fretwell

Well-Known Member
Aug 13, 2017
1,417
376
83
I'm not aware of any default settings that need to be changed. You could try a packet trace to see if the notify message for BLF is being sent to the phone.

The packet below, captured on the fusion box using ngrep, shows the notify message being sent to extension 215 when I made a call to voicemail on extension 213.
Code:
U 2018/01/10 17:37:56.827276 185.xx.xx.33:5060 -> 92.xx.xx.16:40452
NOTIFY sip:215@192.168.6.41:5060 SIP/2.0.
Via: SIP/2.0/UDP 185.xx.xx.33:5060;rport;branch=z9hG4bK93t1BFeBX48aH.
Route: <sip:92.xx.xx.16:40452>;transport=udp.
Max-Forwards: 70.
From: <sip:203@sip.lan-tec.co.uk:5060>;tag=sbZ1sHesNDy0.
To: "215" <sip:215@sip.lan-tec.co.uk:5060>;tag=799734314.
Call-ID: 0_2160116464@192.168.6.41.
CSeq: 42053751 NOTIFY.
Contact: <sip:203@185.xx.xx.33:5060>.
User-Agent: FusionPBX.
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE.
Supported: timer, path, replaces.
Event: dialog.
Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer.
Subscription-State: active;expires=1538.
Content-Type: application/dialog-info+xml.
Content-Length: 577.
.
<?xml version="1.0"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="270" state="full" entity="sip:203@sip.lan-tec.co.uk">
<dialog id="e1802ae4-d313-40eb-955c-ef4645e7d964" direction="initiator">
<state>confirmed</state>
<local>
<identity display="203">sip:203@sip.lan-tec.co.uk</identity>
<target uri="sip:203@sip.lan-tec.co.uk">
<param pname="+sip.rendering" pvalue="yes"/>
</target>
</local>
<remote>
<identity display="*97">sip:*97@sip.lan-tec.co.uk</identity>
<target uri="sip:**203@sip.lan-tec.co.uk"/>
</remote>
</dialog>
</dialog-info>
 
Status
Not open for further replies.