Bringing this issue up again as it still doesn't appear to be fixed.
Closest one is this previous thread (https://www.pbxforums.com/threads/blf-issue-green-button-even-if-extension-is-not-registered.6500/)
FusionPBX sends "Subscription-State: active" headers for nonexistent extensions
Based on my reading of the RFC https://datatracker.ietf.org/doc/html/rfc3265#section-3.2.2 it should be a "terminated" with a reason of some kind
This would also fix the previous thread linked above as Yealinks are expecting correct usage of the Subscription-State header
Looked through the freeswitch documentation, and it appears to do "Subscription-State: terminated;reason=noresource"
Does anyone know what setting in fusion needs to be changed (or added) to support correct Notification Subscription States per RFC?
Closest one is this previous thread (https://www.pbxforums.com/threads/blf-issue-green-button-even-if-extension-is-not-registered.6500/)
FusionPBX sends "Subscription-State: active" headers for nonexistent extensions
Based on my reading of the RFC https://datatracker.ietf.org/doc/html/rfc3265#section-3.2.2 it should be a "terminated" with a reason of some kindThis would also fix the previous thread linked above as Yealinks are expecting correct usage of the Subscription-State header
Looked through the freeswitch documentation, and it appears to do "Subscription-State: terminated;reason=noresource"
Does anyone know what setting in fusion needs to be changed (or added) to support correct Notification Subscription States per RFC?