# Asterisk Release Candidate 22.8.0-rc1

**URL:** <https://community.asterisk.org/t/asterisk-release-candidate-22-8-0-rc1/111643>\
**Category:** Development\
**Created:** [January 15, 2026, 5:07pm UTC](https://community.asterisk.org/t/asterisk-release-candidate-22-8-0-rc1/111643 "2026-01-15T17:07:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![asteriskteam](https://sea1.discourse-cdn.com/asterisk/user_avatar/community.asterisk.org/asteriskteam/32/1845_2.png) [@asteriskteam](https://community.asterisk.org/u/asteriskteam)\
**Post date:** [January 15, 2026, 5:07pm UTC](https://community.asterisk.org/t/asterisk-release-candidate-22-8-0-rc1/111643/1 "2026-01-15T17:07:00Z")

</div>

The Asterisk Development Team would like to announce  
release candidate 1 of asterisk-22.8.0.

The release artifacts are available for immediate download at

> **[Release Asterisk Release 22.8.0-rc1 · asterisk/asterisk](https://github.com/asterisk/asterisk/releases/tag/22.8.0-rc1)**
>
> The Asterisk Development Team would like to announce
> release candidate 1 of asterisk-22.8.0.
> The release artifacts are available for immediate download at
> https://github.com/asterisk/asterisk/relea...

and

> **[Index of /pub/telephony/asterisk/](https://downloads.asterisk.org/pub/telephony/asterisk/)**

Repository: [GitHub - asterisk/asterisk: The official Asterisk Project repository.](https://github.com/asterisk/asterisk)  
Tag: 22.8.0-rc1

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

Thank You!

## Change Log for Release asterisk-22.8.0-rc1

### Links:

- [Full ChangeLog](https://downloads.asterisk.org/pub/telephony/asterisk/releases/ChangeLog-22.8.0-rc1.html)
- [GitHub Diff](https://github.com/asterisk/asterisk/compare/22.7.0...22.8.0-rc1)
- [Tarball](https://downloads.asterisk.org/pub/telephony/asterisk/asterisk-22.8.0-rc1.tar.gz)
- [Downloads](https://downloads.asterisk.org/pub/telephony/asterisk)

### Summary:

- Commits: 56
- Commit Authors: 19
- Issues Resolved: 40
- Security Advisories Resolved: 0

### User Notes:

- 
#### cli.c: Allow ‘channel request hangup’ to accept patterns.

The ‘channel request hangup’ CLI command now accepts  
multiple channel names, POSIX Extended Regular Expressions, glob-like  
patterns, or a combination of all of them. See the CLI command ‘core  
show help channel request hangup’ for full details.

- 
#### 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.

- 
#### res\_pjsip\_messaging: Add support for following 3xx redirects

A new pjsip endpoint option follow\_redirect\_methods was added.  
This option is a comma-delimited, case-insensitive list of SIP methods  
for which SIP 3XX redirect responses are followed. An alembic upgrade  
script has been added for adding this new option to the Asterisk  
database.

- 
#### taskprocessors: Improve logging and add new cli options

New CLI command has been added -  
core show taskprocessor name

- 
#### ccss: Add option to ccss.conf to globally disable it.

A new “enabled” parameter has been added to ccss.conf. It defaults  
to “yes” to preserve backwards compatibility but CCSS is rarely used so  
setting “enabled = no” in the “general” section can save some unneeded channel  
locking operations and log message spam. Disabling ccss will also prevent  
the func\_callcompletion and chan\_dahdi modules from loading.

- 
#### Makefile: Add module-list-\* targets.

Try “make module-list-deprecated” to see what modules  
are on their way out the door.

- 
#### app\_mixmonitor: Add ‘s’ (skip) option to delay recording.

This change introduces a new ‘s()’ (skip) option to the MixMonitor  
application. Example:  
MixMonitor(${UNIQUEID}.wav,s(3))  
This skips recording for the first 3 seconds before writing audio to the file.  
Existing MixMonitor behavior remains unchanged when the ‘s’ option is not used.

- 
#### app\_queue.c: Only announce to head caller if announce\_to\_first\_user

When announce\_to\_first\_user is false, no announcements are played to the head caller

### 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…

```auto
  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})

```

- 
#### pjsip: Move from threadpool to taskpool

The threadpool\_\* options in pjsip.conf have now  
been deprecated though they continue to be read and used.  
They have been replaced with taskpool options that give greater  
control over the underlying taskpool used for PJSIP. An alembic  
upgrade script has been added to add these options to realtime  
as well.

- 
#### app\_directed\_pickup.c: Change some log messages from NOTICE to VERBOSE.

In an effort to reduce log spam, two normal progress  
“pickup attempted” log messages from app\_directed\_pickup have been changed  
from NOTICE to VERBOSE(3). This puts them on par with other normal  
dialplan progress messages.

### Developer Notes:

- 
#### ccss: Add option to ccss.conf to globally disable it.

A new API ast\_is\_cc\_enabled() has been added. It should be  
used to ensure that CCSS is enabled before making any other ast\_cc\_\* calls.

- 
#### chan\_websocket: Add ability to place a MARK in the media stream.

Apps can now send a `MARK_MEDIA` command with an optional  
`correlation_id` parameter to chan\_websocket which will be placed in the  
media frame queue. When that frame is dequeued after all intervening media  
has been played to the core, chan\_websocket will send a  
`MEDIA_MARK_PROCESSED` event to the app with the same correlation\_id  
(if any).

- 
#### chan\_websocket: Add capability for JSON control messages and events.

The chan\_websocket plain-text control and event messages are now  
deprecated (but remain the default) in favor of JSON formatted messages.  
See [WebSocket - Asterisk Documentation](https://docs.asterisk.org/Configuration/Channel-Drivers/WebSocket) for  
more information.  
A “transport\_data” parameter has been added to the

### Commit Authors:

- Alexei Gradinari: (1)
- C. Maj: (1)
- Daouda Taha: (1)
- George Joseph: (11)
- Joe Garlick: (2)
- Joshua C. Colp: (1)
- Justin T. Gibbs: (1)
- Kristian F. Høgh: (1)
- Maximilian Fridrich: (2)
- Michal Hajek: (1)
- Mike Bradeen: (2)
- Nathaniel Wesley Filardo: (1)
- Naveen Albert: (4)
- Peter Krall: (1)
- Sean Bright: (17)
- Sven Kube: (1)
- Tinet-mucw: (2)
- phoneben: (5)
- sarangr7: (1)

---

<div class="post-metadata">

**Author:** ![mbradeen](https://sea1.discourse-cdn.com/asterisk/user_avatar/community.asterisk.org/mbradeen/32/5279_2.png) [@mbradeen](https://community.asterisk.org/u/mbradeen)\
**Post date:** [January 15, 2026, 5:09pm UTC](https://community.asterisk.org/t/asterisk-release-candidate-22-8-0-rc1/111643/2 "2026-01-15T17:09:05Z")

</div>

Closed on January 15, 2026, 5:09pm UTC


