Polycom IP 320 Administrator's Manual page 321

Attribute
call.serverMissedCall.x.enabled
Attribute
call.missedCallTracking.x.enabled
Missed Call Configuration <serverMissedCall/>
The phone supports a per-registration configuration of which events will
cause the locally displayed "missed calls" counter to be incremented.
In the following table, x is the registration number. IP 32x/33x, 430: x=1-2; IP
450: x=1-3; IP 550, 560: x=1-4; VVX 1500: x=1-6; IP 650, 670: x=1-34; IP 6000: x=1;
IP 7000: x=1.
Permitted
Values
0 or 1
Missed Call Tracking <missedCallTracking/>
You can enable/disable missed call tracking on a per-line basis.
In the following table, x is the registration number. IP 32x/33x, 430: x=1-2; IP
450: x=1-3; IP 550, 560: x=1-4; VVX 1500: x=1-6; IP 650, 670: x=1-34; IP 6000: x=1;
IP 7000: x=1.
Permitted
Values
0 or 1
Default Interpretation
0 If set to 0, all missed-call events will increment
the counter.
If set to 1, only missed-call events sent by the
server will increment the counter.
NOTE: This feature is supported with the
Sylantro call server only.
Default Interpretation
1 If set to 1 or Null, missed call tracking is
enabled.
If call.missedCallTracking.x.enabled is
set to 0, then missedCall counter is not
updated regardless of what
call.serverMissedCalls.x.enabled is set
to (and regardless of how the server is
configured). There is no Missed Call List
provided under Menu > Features of the phone.
If call.missedCallTracking.x.enabled is
set to 1 and call.serverMissedCalls.x.enabled
is set to 0, then the number of missedCall
counter is incremented regardless of how the
server is configured.
If call.missedCallTracking.x.enabled is
set to 1 and
call.serverMissedCalls.x.enabled is set
to 1, then the handling of missedCalls depends
on how the server is configured.
Configuration Files
A - 141