Blf issue, green button even if extension is not registered

Status
Not open for further replies.
C

cargreg

New Member
Apr 26, 2018
27
2
3
37
Hi Guys,
i have an issue with the blf, why i saw on my expansion module all extension green even if just 3 are registered?
i'm using fusionpbx 5.0.4 and FreeSWITCH Version 1.10.8-release.14~64bit (-release.14 64bit) on Centos 7.

i have those 3 extensions registered

100@mydomain.it Yealink T42s
101@mydomain.it Yealink T21P E2
102@mydomain.it Yealink T29G, with expansion module.

On the expansion module i see all the extension registered

1666346059195.jpeg

I check the subscribe message send by pbx for example for extension 106


SUBSCRIBE sip:106@pbx_public_ip:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 192.168.1.179:12532;branch=z9hG4bK4125755917;rport
From: "102" <sip:102@mydomain.it:5060>;tag=3398765466
To: <sip:106@mydomain.it:5060>;tag=0TDEIxapeyAC
Call-ID: 0_1685820664@192.168.1.179
CSeq: 11 SUBSCRIBE
Contact: <sip:102@192.168.1.179:12532;transport=TCP>
Proxy-Authorization: Digest username="102", realm="mydomain.it", nonce="02f35500-531a-47b2-9f8d-a7b03703cbc6", uri="sip:106@pbx_public_ip:5060;transport=tcp",
esponse="56e1becd9cca3bec9f37d7dda2b3ae02", algorithm=MD5, cnonce="0a4f113b", qop=auth, nc=00000003
Accept: application/dialog-info+xml
Max-Forwards: 70
User-Agent: Yealink SIP-T29G 46.83.0.120
Expires: 120
Event: dialog
Content-Length: 0

SIP/2.0 202 Accepted
Via: SIP/2.0/TCP 192.168.1.179:12532;branch=z9hG4bK4125755917;rport=12532;received=my_public_ip
From: "102" <sip:102@mydomain.it:5060>;tag=3398765466
To: <sip:106@mydomain.it:5060>;tag=0TDEIxapeyAC
Call-ID: 0_1685820664@192.168.1.179
CSeq: 11 SUBSCRIBE
Contact: <sip:106@pbx_public_ip:5060;transport=tcp>
Expires: 120
User-Agent: FreeSWITCH
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: path, replaces
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=120
Content-Length: 0

NOTIFY sip:102@192.168.1.179:12532;transport=TCP SIP/2.0
Via: SIP/2.0/TCP pbx_public_ip;rport;branch=z9hG4bK3r4D6XyXtN6jS
Route: <sip:my_public_ip:12532>;transport=TCP
Max-Forwards: 70
From: <sip:106@mydomain.it:5060>;tag=0TDEIxapeyAC
To: "102" <sip:102@mydomain.it:5060>;tag=3398765466
Call-ID: 0_1685820664@192.168.1.179
CSeq: 1267810351 NOTIFY
Contact: <sip:106@pbx_public_ip:5060;transport=tcp>
User-Agent: FreeSWITCH
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: 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=120
Content-Type: application/dialog-info+xml
Content-Length: 166

<?xml version="1.0"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="5" state="full" entity="sip:106@mydomain.it">
</dialog-info>

It's normal that freeswitch send me state full?


My /etc/freeswitch/autoload_configs/lua.conf.xml configuration file is

<!-- FusionPBX: Run FAX server queue poller -->
<!--<param name="startup-script" value="app/fax/resources/scripts/fax_queue_monitor.lua"/>-->

<!-- FusionPBX: Support BLF for call flow -->
<!-- There 2 way to handle this
1 - Monitor - ignore SUBSCRIBE and just send NOTIFY each X seconds
2 - Event handler - handle each SUBSCRIBE request
-->
<!--<param name="startup-script" value="call_flow_monitor.lua"/>-->
<!--<param name="startup-script" value="blf_subscribe.lua flow"/>-->

<!-- FusionPBX: Support BLF for DND -->
<!--<param name="startup-script" value="blf_subscribe.lua dnd"/>-->

<!-- FusionPBX: Support BLF for Call Forward -->
<!--<param name="startup-script" value="blf_subscribe.lua forward"/>-->

<!-- FusionPBX: Support MWI indicator-->
<!-- There 2 way to handle this
1 - Monitor - ignore SUBSCRIBE and just send NOTIFY each X seconds
2 - Event handler - handle each SUBSCRIBE request
-->
<!--<param name="startup-script" value="app/voicemail/resources/scripts/mwi.lua"/>-->
<!--<param name="startup-script" value="app/voicemail/resources/scripts/mwi_subscribe.lua"/>-->

<!-- Subscribe to events -->
<hook event="PHONE_FEATURE_SUBSCRIBE" subclass="" script="app.lua feature_event"/>

The blf seem to works well except it shows all available extensions

Can anyone help me?
 
C

cargreg

New Member
Apr 26, 2018
27
2
3
37
as describen in thise post https://www.pbxforums.com/threads/freeswitch-blf-problem.5078/ i tried to disable send-presence-on-register, but the behavior not changed
[ ] 738 REGISTER 102@mydomain.it 102@mydomain.it 4 my_public_ip:5060 192.168.10.153:5060
[ ] 739 SUBSCRIBE 102@mydomain.it 102@mydomain.it 2 my_public_ip:60291 192.168.10.153:5060
[ ] 740 SUBSCRIBE 102@mydomain.it *97@mydomain.it 4 my_public_ip:60291 192.168.10.153:5060
[ ] 741 SUBSCRIBE 102@mydomain.it 100@mydomain.it 6 my_public_ip:60291 192.168.10.153:5060
[ ] 742 SUBSCRIBE 102@mydomain.it 101@mydomain.it 6 my_public_ip:60291 192.168.10.153:5060
[ ] 743 SUBSCRIBE 102@mydomain.it103@mydomain.it 6 my_public_ip:60291 192.168.10.153:5060
[ ] 744 SUBSCRIBE 102@mydomain.it 104@mydomain.it 6 my_public_ip:60291 192.168.10.153:5060
[ ] 745 SUBSCRIBE 102@mydomain.it 105@mydomain.it 6 my_public_ip:60291 192.168.10.153:5060
[ ] 746 SUBSCRIBE 102@mydomain.it 106@mydomain.it 6 my_public_ip:60291 192.168.10.153:5060
 
Dast

Dast

Member
Nov 11, 2019
57
10
8
What is the value of your "yealink_blf_led_mode" setting in Default Settings -> Provision ?
 
C

cargreg

New Member
Apr 26, 2018
27
2
3
37
hi Dast,the value of yealink_blf_led_mode is 0 False,what is this parameter for?

#Configure the LED flashing mode of the BLF key (line key). The value is 0(default) or 1.
features.blf_led_mode = {$yealink_blf_led_mode}
 
C

cargreg

New Member
Apr 26, 2018
27
2
3
37
I tried to change the value but in other cases, the blf works only when there are extensions in call or when an extension have dnd enabled
 
Dast

Dast

Member
Nov 11, 2019
57
10
8
Try changing the value to 1, and enable it. Then restart the phones and wait for them to provision.
 
C

cargreg

New Member
Apr 26, 2018
27
2
3
37
Done, but now the extensions are all black except when I'm on a call and when dnd is enabled
blf_.jpg
I have tried all the values but the situation does not change
 
hfoster

hfoster

Active Member
Jan 28, 2019
684
81
28
34
I don't think FusionPBX will make a distinction between unregistered and available or 'idle' extensions. BLFs were never designed to be presence indicators (or at least it appears that way), merely whether the extension was 'busy' and the call state (ringing, answered) so as such all sorts of PBXs have differing ideas of when to turn on and off lamps.

FusionPBX has scripts that will turn lamps:
  1. Call Centre Agents
  2. Call Flows
  3. Voicemail
  4. DND and Call Forward
Meanwhile, FreeSwitch will handle:
  1. Standard presence.
I do not think there is any functionality in all of the LUA files I've looked over that makes a distinction for whether an extension is registered on not, similarly I cannot see any indication from the FreeSWITCH documentation that they have a config flag that sets unregistered extensions to 'busy'. I suspect the FreeSWITCH people are the best people to ask in this case, as creating a custom LUA to support something like ext+2001 BLFs to monitor registered extensions might be a pain.
 
M

Mikeme

Member
Apr 26, 2021
181
4
18
39
Same issue with Grandstream , once set unregistered ext' on blf key light goes green like the ext' is available but actually does not register and unavailable.
 
Status
Not open for further replies.
Top Bottom