Description:
When querying extension answering rules (/restapi/v1.0/account/{accountId}/extension/{extensionId}/answering-rule) for Call Queues and Department extensions, the missedCall settings object is omitted or not populated in the response. We request that the missedCall object and its associated routing action settings be fully populated for Call Queue answering rules via the API.

Current Problem:
In the Admin Portal, administrators can view and configure missed call handling and overflow behavior for call queues. However, when auditing or exporting these configurations via the REST API across our 270+ call queues, the missedCall section is missing from the answering rules payload. This prevents API scripts from confirming whether a queue has missed call routing configured.

Proposed Solution:
Ensure the missedCall object (including actionType and destination details) is consistently returned in the answering rules response for extension types Department and CallQueue, matching the schema returned for user extensions and the settings configured in Service Web.

Business Impact:
We rely on automated API audits to verify routing logic and failover policies across all call queues. Populating the missedCall object in the API response allows automated validation of missed call routing without requiring manual checks in the Admin Portal.