Certified Asterisk Release certified-20.7-cert8

Asterisk Asterisk News
1

The Asterisk Development Team would like to announce
the release of Certified asterisk-20.7-cert8.

The release artifacts are available for immediate download at

and

Repository: GitHub - asterisk/asterisk: The official Asterisk Project repository.
Tag: certified-20.7-cert8

This release resolves issues reported by the community
and would have not been possible without your participation.

Thank You!

Change Log for Release asterisk-certified-20.7-cert8

Links:

Summary:

  • Commits: 7
  • Commit Authors: 3
  • Issues Resolved: 7
  • Security Advisories Resolved: 0

User Notes:

  • res_sorcery_memory_cache: Reduce cache lock time for sorcery memory cache populate command

    The AMI command sorcery memory cache populate will now
    return an error if there is an internal error performing the populate.
    The CLI command will display an error in this case as well.

  • res_geolocation: Fix multiple issues with XML generation.

    Geolocation: Two new optional profile parameters have been added.

    • pidf_element_id which sets the value of the id attribute on the top-level
      PIDF-LO device, person or tuple elements.
    • device_id which sets the content of the <deviceID> element.
      Both parameters can include channel variables.

Upgrade Notes:

  • res_geolocation: Fix multiple issues with XML generation.

    Geolocation: In order to correct bugs in both code and
    documentation, the following changes to the parameters for GML geolocation
    locations are now in effect:
    • The documented but unimplemented crs (coordinate reference system) element
      has been added to the location_info parameter that indicates whether the 2d
      or 3d reference system is to be used. If the crs isn’t valid for the shape
      specified, an error will be generated. The default depends on the shape
      specified.
    • The Circle, Ellipse and ArcBand shapes MUST use a 2d crs. If crs isn’t
      specified, it will default to 2d for these shapes.
      The Sphere, Ellipsoid and Prism shapes MUST use a 3d crs. If crs isn’t
      specified, it will default to 3d for these shapes.
      The Point and Polygon shapes may use either crs. The default crs is 2d
      however so if 3d positions are used, the crs must be explicitly set to 3d.
    • The geoloc show gml_shape_defs CLI command has been updated to show which
      coordinate reference systems are valid for each shape.
    • The pos3d element has been removed in favor of allowing the pos element
      to include altitude if the crs is 3d. The number of values in the pos
      element MUST be 2 if the crs is 2d and 3 if the crs is 3d. An error
      will be generated for any other combination.
    • The angle unit-of-measure for shapes that use angles should now be included
      in the respective parameter. The default is degrees. There were some
      inconsistent references to orientation_uom in some documentation but that
      parameter never worked and is now removed. See examples below.
      Examples…
      location_info = shape="Sphere", pos="39.0 -105.0 1620", radius="20"
  location_info = shape="Point", crs="3d", pos="39.0 -105.0 1620"
  location_info = shape="Point", pos="39.0 -105.0"
  location_info = shape=Ellipsoid, pos="39.0 -105.0 1620", semiMajorAxis="20"
                semiMinorAxis="10", verticalAxis="0", orientation="25 degrees"
  pidf_element_id = ${CHANNEL(name)}-${EXTEN}
  device_id = mac:001122334455
  Set(GEOLOC_PROFILE(pidf_element_id)=${CHANNEL(name)}/${EXTEN})

Developer Notes:

Commit Authors:

  • George Joseph: (4)
  • Mike Bradeen: (2)
  • Sean Bright: (1)