4.3.96

Changes for 4.3.96

Changes to branch 4.3 after version 4.3.95.

Commits

• KZOO-59: calculate account CID name - by James Aimonetti

  Prior, the caller's CID name would be returned from

  kz_attributes:get_account_external_cid/1 along with the calculated

  account CID number. Particularly for DISA callers, this meant their

  CID name was passed through (often their mobile number) instead of

  being set to the account's external CID name.

  This change calculates the CID name and number of the account and

  returns them both if configured.

• add validate_resource to cb_conferences - 4.3 - by lazedo

• KZOO-60: permit conference feature code - by James Aimonetti

  Rather than needing to know the extension to dial for a conference,

  allow a feature code to capture the conference ID from the dialed

  number. Useful for clients that are provisioned dynamically (like

  WebRTC devices) that have full control over the dialed number (as

  opposed to typical desk phones which only dial digits).

• add support for authn with jsonnrpc - 4.3 - by lazedo

• KZOO-57: calculate presence id for route requests - by lazedo

  When a device registers, the calculated presence_id is cached and

  passed along on subsequent INVITEs. If a user hotdesks into the

  device, the cached presence_id (likely the SIP username of the device)

  will continue to be used on call events related to that device.

  This causes issues with applications (like Qubicle) that track a

  user's calls based on the user's presence_id being present on dialog

  update events (confirmed and terminated).

  Instead, provide a uniform way to calculate a device's presence_id and

  use it for setting CCVs on the route response in callflow and in

  registrar for authn responses.

• KZOO-57: calculate presence id for route requests - by James Aimonetti

  When a device registers, the calculated presence_id is cached and

  passed along on subsequent INVITEs. If a user hotdesks into the

  device, the cached presence_id (likely the SIP username of the device)

  will continue to be used on call events related to that device.

  This causes issues with applications (like Qubicle) that track a

  user's calls based on the user's presence_id being present on dialog

  update events (confirmed and terminated).

  Instead, provide a uniform way to calculate a device's presence_id and

  use it for setting CCVs on the route response in callflow and in

  registrar for authn responses.

• fix hold media path in get_fs_key_and_value - by lazedo