Polycom has mentioned the feature serverMissedCall in it's polycom sound point phone data sheets, although it is only actually supported by the Sylantro (and now Broadsoft) platform.
The admin guide explains how to turn it on, but not how to make the feature work, for example what kind of SIP NOTIFY payload it would accept.
Despite repeated searches on the "Event: missed-call-summary", I have yet to find any documentation explaining how the payload etc... works.
Is there any documentation polycom provide on the details of what is valid data that will be accepted as part of the missed-call-summary SIP NOTIFY event?
as you have already written this feature was developed with our Partner Broadsoft and is under NDA.
It is only supported on that Platform.
UCS Admin Guide 3.3.0:
NOTE: This feature is supported with theBroadSoft® Synergy (used to be Sylantro) callserver only.
Thanks for the response, I didn't realized that it was under NDA (at one point one of the techbulletins had a URL to broadsoft website explaining the feature, that link never worked but at least didn't give the impression that it was under NDA, I can't find the tech bulleting anymore).
But this specific issue is a very common one.
It is very common for some phones to have their own extensions and also be part of a "Ring all" huntgroup.
In those cases, the phone does not distinguish between a hunt-group missed call and a direct missed call, which could lead people to see too many missed calls (every call answered by someone else in the hunt group) on the phone, overshadowing the important ones.
Most other manufacturers suppport the "Call Answered Elsewhere" Reason header, which makes the phone not list the hunt-group calls as a missed call.
Does polycom have a similar open feature that the common system integraters can use?
I am not fully aware of the Roadmap for future releases and if the Call Answered Elsewhere Feature is implemented in any of the upcoming Releases.
Best Idea at this moment is to work with your Polycom Reseller and get the to raise a Feature Request.
That way the interest for certain features gets highlighted to the relevant product managers.
In this case you should use the missedCallTracking command instead of the serverMissedCall command.
(IP331 2-line example here).
<missedCallTracking call.missedCallTracking.1.enabled="0" call.missedCallTracking.2.enabled="0"/>
This should do the same thing (Stop the called list from populating and popping up the missed call display message - but it will also get rid of the SUBSCRIBE messages sent every minute to the SIP server.
As for the Hunt Group issue - you could create a second extension for every user, use the second extension as the member of any HuntGroups the user is part of and disable missedCallTracking on that line only. (I usually just add an additional digit to the users main extension to get the HG extension - easier to maintain that way).
Its not ideal (and a pain if the PBX is licensed per extension (rather than user)) but it should work well otherwise - especially on smaller sites.