Update to Asterisk 1.8.22.0: this is a bug fix update.

The Asterisk Development Team has announced the release of Asterisk 1.8.22.0.

The release of Asterisk 1.8.22.0 resolves several issues reported by the
community and would have not been possible without your participation.
Thank you!

The following is a sample of the issues resolved in this release:

* --- Fix Sorting Order For Parking Lots Stored In Static Realtime

* --- Make ParkAndAnnounce return to priority + 1 when return context
      is not defined

* --- When a session timer expires during a T.38 call, re-invite with
      correct SDP

* --- Fix several unreleased mutex locks that cause problem with
      processing calls

* --- Fix crash when AMI redirect action redirects two channels out of
      a bridge.

For a full list of changes in this release, please see the ChangeLog:

http://downloads.asterisk.org/pub/telephony/asterisk/ChangeLog-1.8.22.0

Thank you for your continued support of Asterisk!
Updated comms/asterisk18 to 1.8.22.0
Update to latest release. This is supposedly the last version which requires
Java 5. Changes from 9.4 to 9.5:

The bulk of the open source parts of Saxon (the parts maintained by Saxonica) are now licensed under Mozilla Public License version 2.0, replacing MPL 1.0.

There have been some other changes to third-party open source components, notably the introduction of a new regular expression engine derived from Jakarta (Apache license), and the dropping of the old Base64 conversion code (Netscape license).

Users interested in building the product from source code need to be aware that the build process now includes a preprocessing phase that generate separate Java code for the EE, PE, and HE editions. The raw (before preprocessing) source code is published in the Subversion repository, but for building Saxon-HE, a more convenient place to start is the post-preprocessing Java code issued on SourceForge as a source.zip download.

A consequence of this change is that the JAR files for Saxon-HE, Saxon-PE, and Saxon-EE contain different class files having the same names. Therefore, the JAR files for different editions should not co-exist on the classpath. If you use internal Saxon APIs in an application, you may need to check that the methods you call are available in all three editions. This won't be a problem for interfaces that are clearly user-facing, but it could be an issue for applications that penetrate deeper into the internals.

More changes here:
http://www.saxonica.com/documentation/index.html#!changes
* Remove PKGSRC_SHOW_PATCH_ERRORMSG, because it is not used in pkgsrc/mk.
* Set PATCH_DEBUG when PKG_DEVELOPER=yes.

No objection to
http://mail-index.netbsd.org/tech-pkg/2013/05/06/msg011276.html .
Updated textproc/saxon to 9.5.0.1j