Which RFC describes as-feature-event event package ?

[oliv]

Hello,

Admin Guide (v84) mentions "send a SUBSCRIBE message with event “as-feature-event” to the server" for account.X.feature_key_sync.enable parameter.

Which RFC (as in https://www.iana.org/assignments/sip-eve...ents.xhtml) describes this event package ?

Best regards

[complex1]

(01-15-2019 01:43 PM)oliv Wrote:  Hello,

Admin Guide (v84) mentions "send a SUBSCRIBE message with event “as-feature-event” to the server" for account.X.feature_key_sync.enable parameter.

Which RFC (as in https://www.iana.org/assignments/sip-eve...ents.xhtml) describes this event package ?

Best regards

Hi,

As far as I know has this something to do with a Broadsoft PBX and is not written down in a RFC.
But I'm not sure.

Hope this will help.

[oliv]

(01-15-2019 07:31 PM)complex1 Wrote:  Hi,

As far as I know has this something to do with a Broadsoft PBX and is not written down in a RFC.
But I'm not sure.

Hope this will help.

Hi,

I've not found any written documentation of this feature, yet.
Maybe something approaching but written by normalization bodies (IETF, ...) does exist ?

[jolouis]

Google is your friend here. For example:

http://lists.digium.com/pipermail/asteri...48470.html

Follow that thread and you end up with this relevant quote:

Quote:The spec contains a lot more than this. This specific part is a derivate of
ECMA-323 which is public.

It can be found here:

http://interop.broadsoft.com/files/BW-SI...faceSpec-R
170.pdf

Section 8 is the relevant one.

I'm sure that link is out of date (the thread is from 2011) but you could probably google further to find more details/a more recent copy. As mentioned in this discussion the whole purpose is basically to support Broadcom's version of syncing DND and forward states between phones and servers. It's a nice idea but in reality many already implement this simply using the on/off dial codes for DND/Call forward that Yealink have supported for many many years now.

The one advantage to the Broadcom approach is that in theory the server can push those states to the phone (i.e. the server can take the phone out of DND directly rather than just monitoring the state of DND), but note that nothing in the Yealink documentation says THAT part is actually implemented in their firmware, so might still be a pipe dream for niche use anyway...