2010-07-27 01:39:58 +00:00
|
|
|
==============================================================================
|
2008-11-21 20:42:37 +00:00
|
|
|
===
|
|
|
|
=== This file documents the new and/or enhanced functionality added in
|
|
|
|
=== the Asterisk versions listed below. This file does NOT include
|
|
|
|
=== changes in behavior that would not be backwards compatible with
|
|
|
|
=== previous versions; for that information see the UPGRADE.txt file
|
|
|
|
=== and the other UPGRADE files for older releases.
|
|
|
|
===
|
2010-07-27 01:39:58 +00:00
|
|
|
==============================================================================
|
2013-08-28 20:49:02 +00:00
|
|
|
|
2016-07-21 21:35:39 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 14 to Asterisk 15 --------------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
2017-04-04 16:44:34 +00:00
|
|
|
app_queue
|
|
|
|
------------------
|
|
|
|
* PAUSEALL/UNPAUSEALL now sets the pause reason in the queue_log if it has
|
|
|
|
been defined.
|
|
|
|
|
2017-05-23 20:42:04 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 14.5.0 to Asterisk 14.6.0 ------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
2017-06-19 22:21:29 +00:00
|
|
|
app_voicemail
|
|
|
|
------------------
|
|
|
|
* A new global option "imap_poll_logout" was added to specify whether need to
|
|
|
|
disconnect from the IMAP server after polling of mailboxes.
|
|
|
|
Default: no
|
|
|
|
|
2017-06-07 16:21:10 +00:00
|
|
|
res_pjsip
|
|
|
|
------------------
|
|
|
|
* A new endpoint option "refer_blind_progress" was added to turn off notifying
|
|
|
|
the progress details on Blind Transfer. If this option is not set then
|
|
|
|
the chan_pjsip will send NOTIFY "200 OK" immediately after "202 Accepted".
|
|
|
|
On default is enabled.
|
|
|
|
Some SIP phones like Mitel/Aastra or Snom keep the line busy until
|
|
|
|
receive "200 OK".
|
|
|
|
|
2017-06-12 14:23:56 +00:00
|
|
|
* A new endpoint option "notify_early_inuse_ringing" was added to control
|
|
|
|
whether to notify dialog-info state 'early' or 'confirmed' on Ringing
|
|
|
|
when already INUSE.
|
|
|
|
|
2017-06-15 08:12:41 +00:00
|
|
|
* The endpoint option 'dtmf_mode' has a new option 'auto_dtmf' added. This
|
|
|
|
mode works similar to 'auto' except uses DTMF INFO as fallback instead of
|
|
|
|
INBAND.
|
|
|
|
|
2017-05-23 20:42:04 +00:00
|
|
|
res_agi
|
|
|
|
------------------
|
|
|
|
* The EAGI() application will now look for a dialplan variable named
|
|
|
|
EAGI_AUDIO_FORMAT and use that format with the 'enhanced' audio pipe that
|
|
|
|
EAGI provides. If not specified, it will continue to use the default signed
|
|
|
|
linear (slin).
|
|
|
|
|
2017-05-31 15:41:45 +00:00
|
|
|
chan_pjsip
|
|
|
|
------------------
|
|
|
|
* When dialing an endpoint directly or using the PJSIP_DIAL_CONTACTS dialplan
|
|
|
|
function any contact which is considered unreachable due to qualify being
|
|
|
|
enabled will no longer be called.
|
|
|
|
|
2017-06-06 12:04:21 +00:00
|
|
|
* The asymmetric_rtp_codec option now also controls whether chan_pjsip will
|
|
|
|
send media as-is without transcoding if the codec has been negotiated in the
|
|
|
|
SDP. If set to "no" then Asterisk will only ever send the preferred codec
|
|
|
|
from the SDP, unless the remote side sends a different codec and we will
|
|
|
|
switch to match.
|
|
|
|
|
2017-06-30 13:31:52 +00:00
|
|
|
Build System
|
|
|
|
------------------
|
|
|
|
* Added a new PJPROJECT_CONFIGURE_OPTS environment variable which can be used
|
|
|
|
to pass arbitrary options to the bundled pjproject configure.
|
|
|
|
|
|
|
|
* Automatically set the bundled pjproject configure --host and --build
|
|
|
|
options to match those supplied for the asterisk configure.
|
|
|
|
|
2017-03-28 18:10:32 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 14.4.0 to Asterisk 14.5.0 ------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
2017-04-07 21:14:16 +00:00
|
|
|
res_rtp_asterisk
|
|
|
|
------------------
|
|
|
|
* Added the stun_blacklist option to rtp.conf. Some multihomed servers have
|
|
|
|
IP interfaces that cannot reach the STUN server specified by stunaddr.
|
|
|
|
Blacklist those interface subnets from trying to send a STUN packet to find
|
|
|
|
the external IP address. Attempting to send the STUN packet needlessly
|
|
|
|
delays processing incoming and outgoing SIP INVITEs because we will wait
|
|
|
|
for a response that can never come until we give up on the response.
|
|
|
|
Multiple subnets may be listed.
|
|
|
|
|
2017-05-08 21:11:19 +00:00
|
|
|
Logging
|
|
|
|
-------------------
|
|
|
|
* Added logger_queue_limit to the configuration options.
|
|
|
|
All log messages go to a queue serviced by a single thread
|
|
|
|
which does all the IO. This setting controls how big that
|
|
|
|
queue can get (and therefore how much memory is allocated)
|
|
|
|
before new messages are discarded.
|
|
|
|
The default is 1000.
|
|
|
|
|
2017-03-28 18:10:32 +00:00
|
|
|
res_pjsip_config_wizard
|
|
|
|
------------------
|
|
|
|
* Two new parameters have been added to the pjsip config wizard.
|
|
|
|
Setting 'sends_line_with_registrations' to true will cause the wizard
|
|
|
|
to skip the creation of an identify object to match incoming requests
|
|
|
|
to the endpoint and instead add the line and endpoint parameters to
|
|
|
|
the outbound registration object.
|
|
|
|
Setting 'outbound_proxy' is a shortcut for adding individual
|
|
|
|
endpoint/outbound_proxy, aor/outbound_proxy and registration/outbound_proxy
|
|
|
|
parameters.
|
|
|
|
|
2017-05-09 10:25:29 +00:00
|
|
|
res_hep_rtcp
|
|
|
|
------------------
|
|
|
|
* If the 'call-id' value is specified for the uuid_type option and a
|
|
|
|
chan_sip channel is used the resulting HEP traffic will now contain the
|
|
|
|
SIP Call-ID instead of the Asterisk channel name.
|
|
|
|
|
2017-03-28 18:10:32 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 14.3.0 to Asterisk 14.4.0 ------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
2016-09-19 09:46:27 +00:00
|
|
|
Build System
|
|
|
|
------------------
|
|
|
|
* LOW_MEMORY no longer has an effect on Asterisk ABI. Symbols that were
|
|
|
|
previously suppressed by LOW_MEMORY are now replaced by stub functions.
|
|
|
|
Asterisk built with LOW_MEMORY can now successfully load binary modules
|
|
|
|
built without LOW_MEMORY and vice versa.
|
|
|
|
|
2016-11-12 18:15:12 +00:00
|
|
|
* RADIUS backends for CEL and CDR can now also be built using the radcli
|
|
|
|
client library, in addition to the existing support for building them
|
|
|
|
using either freeradius or radiusclient-ng.
|
|
|
|
|
2016-10-27 02:40:49 +00:00
|
|
|
Core
|
|
|
|
------------------
|
|
|
|
* ASTERISK_REGISTER_FILE was no longer useful and has been removed. Sources
|
|
|
|
which use mtx_prof must now manually declare and initialize the variable.
|
|
|
|
|
2016-07-19 14:41:44 +00:00
|
|
|
chan_sip
|
|
|
|
------------------
|
|
|
|
* If an offer is received with optional SRTP (a media stream with RTP/AVP but
|
|
|
|
which contains a crypto line) chan_sip will now accept it and enable SRTP.
|
|
|
|
If you would like to do optional SRTP on outbound you will need to create
|
|
|
|
a dialplan that dials with it enabled initially and if it fails fall back to
|
|
|
|
without.
|
2016-08-07 14:58:59 +00:00
|
|
|
|
2016-08-30 03:26:03 +00:00
|
|
|
res_pjsip
|
|
|
|
------------------
|
|
|
|
* Added endpoint configuration parameter "preferred_codec_only".
|
|
|
|
This allow asterisk response to a SIP invite with the single most
|
|
|
|
preferred codec rather than advertising all joint codec capabilities.
|
|
|
|
This limits the other side's codec choice to exactly what we prefer.
|
|
|
|
|
2016-10-10 16:49:08 +00:00
|
|
|
cdr_radius
|
|
|
|
------------------
|
|
|
|
* To fix a memory leak the syslog channel is now empty if it has not been set
|
|
|
|
and used by a syslog channel in the logger.
|
|
|
|
|
|
|
|
cel_radius
|
|
|
|
------------------
|
|
|
|
* To fix a memory leak the syslog channel is now empty if it has not been set
|
|
|
|
and used by a syslog channel in the logger.
|
|
|
|
|
2016-09-13 09:08:34 +00:00
|
|
|
RTP
|
|
|
|
------------------
|
|
|
|
* New setting "rtp_pt_dynamic = 35" in asterisk.conf:
|
|
|
|
Normally the Dynamic RTP Payload Type numbers are 96-127, which allow just 32
|
|
|
|
formats. To avoid the message "No Dynamic RTP mapping available", the range
|
|
|
|
was changed to 35-63,96-127. This is allowed by RFC 3551 section 3. However,
|
|
|
|
when you use more than 32 formats and calls are not accepted by a remote
|
|
|
|
implementation, please report this and go back to rtp_pt_dynamic = 96.
|
|
|
|
|
2017-03-20 18:27:31 +00:00
|
|
|
* A new setting, "rtp_use_dynamic", has been added in asterisk.conf". When set
|
|
|
|
to "yes" RTP dynamic payload types are assigned dynamically per RTP instance.
|
|
|
|
When set to "no" RTP dynamic payload types are globally initialized to pre-
|
|
|
|
designated numbers and function similar to static payload types.
|
|
|
|
|
2016-11-21 21:43:47 +00:00
|
|
|
app_originate
|
|
|
|
------------------
|
|
|
|
* Added support to gosub predial routines on both original channel and on the
|
|
|
|
created channel using options parameter (like app_dial) B() and b(). This
|
|
|
|
allows for adding variables to newly created channel or, e.g. setting callerid.
|
|
|
|
|
2016-12-19 21:03:52 +00:00
|
|
|
CLI Commands
|
|
|
|
------------------
|
|
|
|
* 'dialplan show' output will now show [config_file:line_number] instead of
|
|
|
|
[registrar] when that information is available. Currently only extensions
|
|
|
|
registered by pbx_config when loading/reloading will use this format.
|
|
|
|
|
2016-11-06 12:30:07 +00:00
|
|
|
app_queue
|
|
|
|
------------------
|
|
|
|
* Add 'QueueUpdate' application which can be used to track outbound calls
|
|
|
|
using app_queue.
|
|
|
|
|
2017-03-07 12:25:25 +00:00
|
|
|
pbx_spool
|
|
|
|
------------------
|
|
|
|
* Asterisk will now set the AST_OUTGOING_ATTEMPT channel variable so that
|
|
|
|
attempt-specific behavior is possible. This is a 1-based number that
|
|
|
|
simply increases by 1 for each attempt.
|
|
|
|
|
2017-02-14 14:12:31 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 14.3.0 to Asterisk 14.4.0 ------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
2017-03-14 12:50:07 +00:00
|
|
|
AMI
|
|
|
|
------------------
|
|
|
|
* The 'PJSIPShowEndpoint' command's respone event of 'IdentifyDetail' now
|
|
|
|
contains a new optional parameter, 'MatchHeader', mapping to the new
|
|
|
|
configuration option 'match_header' for the corresponding 'identify' object.
|
|
|
|
It should be noted that since 'match_header' takes in a key: value pair, the
|
|
|
|
event parameter will contain a ':' as well.
|
|
|
|
|
2017-02-14 14:12:31 +00:00
|
|
|
app_record
|
|
|
|
------------------
|
|
|
|
* Added new 'u' option to Record() application which prevents Asterisk from
|
|
|
|
truncating silence from the end of recorded files.
|
|
|
|
|
2017-02-22 00:06:00 +00:00
|
|
|
res_pjsip_outbound_registration
|
|
|
|
------------------
|
|
|
|
* Outbound registrations are now refreshed when res_stun_monitor detects
|
|
|
|
a network change event has happened.
|
|
|
|
The 'pjsip send (un)register' CLI commands were updated to accept '*all'
|
|
|
|
as an argument to operate on all registrations.
|
|
|
|
The 'PJSIP(Un)Register' AMI commands were updated to also accept '*all'.
|
|
|
|
|
2017-02-13 22:50:41 +00:00
|
|
|
app_voicemail
|
|
|
|
------------------
|
|
|
|
* The 'Comedian Mail' prompts can now be overriden using the 'vm-login' and
|
|
|
|
'vm-newuser' configuration options in voicemail.conf.
|
|
|
|
|
2017-03-08 14:16:29 +00:00
|
|
|
* Added 'fromstring' field to the voicemail boxes. If set, it will override
|
|
|
|
the global 'fromstring' field on a per-mailbox basis.
|
|
|
|
|
2017-02-23 05:26:13 +00:00
|
|
|
func_channel
|
|
|
|
------------------
|
|
|
|
* Added CHANNEL(callid) to retrieve the call log tag associated with the
|
|
|
|
channel. e.g., [C-00000000] Dialplan now has access to the call log
|
|
|
|
search key associated with the channel so it can be saved in case there
|
|
|
|
is a problem with the call.
|
|
|
|
|
res_pjsip: Symmetric transports
A new transport parameter 'symmetric_transport' has been added.
When a request from a dynamic contact comes in on a transport with
this option set to 'yes', the transport name will be saved and used
for subsequent outgoing requests like OPTIONS, NOTIFY and INVITE.
It's saved as a contact uri parameter named 'x-ast-txp' and will
display with the contact uri in CLI, AMI, and ARI output. On the
outgoing request, if a transport wasn't explicitly set on the
endpoint AND the request URI is not a hostname, the saved transport
will be used and the 'x-ast-txp' parameter stripped from the
outgoing packet.
* config_transport was modified to accept and store the new parameter.
* config_transport/transport_apply was updated to store the transport
name in the pjsip_transport->info field using the pjsip_transport->pool
on UDP transports.
* A 'multihomed_on_rx_message' function was added to
pjsip_message_ip_updater that, for incoming requests, retrieves the
transport name from pjsip_transport->info and retrieves the transport.
If transport->symmetric_transport is set, an 'x-ast-txp' uri parameter
containing the transport name is added to the incoming Contact header.
* An 'ast_sip_get_transport_name' function was added to res_pjsip.
It takes an ast_sip_endpoint and a pjsip_sip_uri and returns a
transport name if endpoint->transport is set or if there's an
'x-ast-txp' parameter on the uri and the uri host is an ipv4 or
ipv6 address. Otherwise it returns NULL.
* An 'ast_sip_dlg_set_transport' function was added to res_pjsip
which takes an ast_sip_endpoint, a pjsip_dialog, and an optional
pjsip_tpselector. It calls ast_sip_get_transport_name() and if
a non-NULL is returned, sets the selector and sets the transport
on the dialog. If a selector was passed in, it's updated.
* res_pjsip/ast_sip_create_dialog_uac and ast_sip_create_dialog_uas
were modified to call ast_sip_dlg_set_transport() instead of their
original logic.
* res_pjsip/create_out_of_dialog_request was modified to call
ast_sip_get_transport_name() and pjsip_tx_data_set_transport()
instead of its original logic.
* Existing transport logic was removed from endpt_send_request
since that can only be called after a create_out_of_dialog_request.
* res_pjsip/ast_sip_create_rdata was converted to a wrapper around
a new 'ast_sip_create_rdata_with_contact' function which allows
a contact_uri to be specified in addition to the existing
parameters. (See below)
* res_pjsip_pubsub/internal_pjsip_evsub_send_request was eliminated
since all it did was transport selection and that is now done in
ast_sip_create_dialog_uac and ast_sip_create_dialog_uas.
* 'contact_uri' was added to subscription_persistence. This was
necessary because although the parsed rdata contact header has the
x-ast-txp parameter added (if appropriate),
subscription_persistence_update stores the raw packet which
doesn't have it. subscription_persistence_recreate was then
updated to call ast_sip_create_rdata_with_contact with the
persisted contact_uri so the recreated subscription has the
correct transport info to send the NOTIFYs.
* res_pjsip_session/internal_pjsip_inv_send_msg was eliminated since
all it did was transport selection and that is now done in
ast_sip_create_dialog_uac.
* pjsip_message_ip_updater/multihomed_on_tx_message was updated
to remove all traces of the x-ast-txp parameter from the
outgoing headers.
NOTE: This change does NOT modify the behavior of permanent
contacts specified on an aor. To do so would require that the
permanent contact's contact uri be updated with the x-ast-txp
parameter and the aor sorcery object updated. If we need to
persue this, we need to think about cloning permanent contacts into
the same store as the dynamic ones on an aor load so they can be
updated without disturbing the originally configured value.
You CAN add the x-ast-txp parameter to a permanent contact's uri
but it would be much simpler to just set endpoint->transport.
Change-Id: I4ee1f51473da32ca54b877cd158523efcef9655f
2017-03-07 14:33:26 +00:00
|
|
|
res_pjsip
|
|
|
|
------------------
|
|
|
|
* A new transport parameter 'symmetric_transport' has been added.
|
|
|
|
When a request from a dynamic contact comes in on a transport with this
|
|
|
|
option set to 'yes', the transport name will be saved and used for
|
|
|
|
subsequent outgoing requests like OPTIONS, NOTIFY and INVITE. It's
|
|
|
|
saved as a contact uri parameter named 'x-ast-txp' and will display with
|
|
|
|
the contact uri in CLI, AMI, and ARI output. On the outgoing request,
|
|
|
|
if a transport wasn't explicitly set on the endpoint AND the request URI
|
|
|
|
is not a hostname, the saved transport will be used and the 'x-ast-txp'
|
|
|
|
parameter stripped from the outgoing packet. To facilitate recreation of
|
|
|
|
subscriptions on asterisk restart, a new column 'contact_uri' needed to be
|
|
|
|
added to the ps_subcsription_persistence table. Since new columns were
|
|
|
|
added to both transport and subscription_persistence, an alembic upgrade
|
|
|
|
should be run to bring the database tables up to date.
|
|
|
|
|
2017-03-14 21:45:06 +00:00
|
|
|
* A new option, allow_overlap, has been added to endpoints which allows
|
|
|
|
overlap dialing functionality to be enabled or disabled. The option defaults
|
|
|
|
to enabled.
|
|
|
|
|
2017-02-16 10:22:47 +00:00
|
|
|
res_pjsip_transport_websocket
|
|
|
|
------------------
|
|
|
|
* Removed non-secure websocket support. Firefox and Chrome have not allowed
|
|
|
|
non-secure websockets for quite some time so this shouldn't be an issue
|
|
|
|
for people. Attempting to use a non-secure websocket may or may not work
|
|
|
|
when Asterisk attempts to send SIP requests to do something like initiate
|
|
|
|
call hangup.
|
|
|
|
|
2017-03-14 12:50:07 +00:00
|
|
|
res_pjsip_endpoint_identifier_ip
|
|
|
|
------------------
|
|
|
|
* A new option has been added to the 'identify' configuration object,
|
|
|
|
'match_header'. The 'match_header' attribute should contain a SIP
|
|
|
|
header: value pair that, When set, will cause inbound requests that contain
|
|
|
|
the matching SIP header/value pair to be associated with the corresponding
|
|
|
|
endpoint. This option is cumulative with the 'match' option, so that if
|
|
|
|
either option matches the request, the request is associated with the
|
|
|
|
endpoint.
|
|
|
|
|
|
|
|
In a future release, this module will be renamed to something more
|
|
|
|
appropriate, as it now matches inbound requests on more than just IP
|
|
|
|
address.
|
|
|
|
|
2017-03-07 20:13:02 +00:00
|
|
|
res_rtp_asterisk
|
|
|
|
-----------------
|
|
|
|
* The RTP layer of Asterisk now has support for RFC 5761: "Multiplexing RTP
|
|
|
|
Data and Control Packets on a Single Port." So far, the only channel driver
|
|
|
|
that supports this feature is chan_pjsip. You can set "rtcp_mux = yes" on
|
|
|
|
a PJSIP endpoint in pjsip.conf to enable the feature.
|
|
|
|
|
2016-08-07 14:58:59 +00:00
|
|
|
------------------------------------------------------------------------------
|
2016-11-24 00:27:54 +00:00
|
|
|
--- Functionality changes from Asterisk 14.2.0 to Asterisk 14.3.0 ------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
|
|
|
res_pjproject
|
|
|
|
------------------
|
|
|
|
* Added new CLI command "pjproject set log level". The new command allows
|
|
|
|
the maximum PJPROJECT log levels to be adjusted dynamically and
|
|
|
|
independently from the set debug logging level like many other similar
|
|
|
|
module debug logging commands.
|
|
|
|
|
|
|
|
* Added new companion CLI command "pjproject show log level" to allow the
|
|
|
|
user to see the current maximum pjproject logging level.
|
|
|
|
|
|
|
|
* Added new pjproject.conf startup section "log_level' option to set the
|
|
|
|
initial maximum PJPROJECT logging level.
|
|
|
|
|
2016-12-01 00:25:11 +00:00
|
|
|
res_pjsip_outbound_registration
|
|
|
|
------------------
|
|
|
|
* Statsd no longer logs redundant status PJSIP.registrations.state changes
|
|
|
|
for internal state transitions that don't change the reported public status
|
|
|
|
state.
|
|
|
|
|
2016-12-06 20:54:25 +00:00
|
|
|
res_pjsip_registrar
|
|
|
|
------------------
|
|
|
|
* The PJSIPShowRegistrationInboundContactStatuses AMI command has been added
|
|
|
|
to return ContactStatusDetail events as opposed to
|
|
|
|
PJSIPShowRegistrationsInbound which just a dumps every defined AOR.
|
|
|
|
|
|
|
|
res_pjsip
|
|
|
|
------------------
|
|
|
|
* Six existing contact fields have been added to the end of the
|
|
|
|
ContactStatusDetail AMI event:
|
|
|
|
ID, AuthenticateQualify, OutboundProxy, Path, QualifyFrequency and
|
|
|
|
QualifyTimeout. Existing fields have not been disturbed.
|
|
|
|
|
2017-01-05 12:11:43 +00:00
|
|
|
res_pjsip_endpoint_identifier_ip
|
|
|
|
------------------
|
|
|
|
* SRV lookups can now be done on provided hostnames to determine additional
|
|
|
|
source IP addresses for requests. This is configurable using the
|
|
|
|
"srv_lookups" option on the identify and defaults to "yes".
|
|
|
|
|
2017-01-19 15:05:36 +00:00
|
|
|
ARI
|
|
|
|
------------------
|
|
|
|
* The 'ari set debug' command has been enhanced to accept 'all' as an
|
|
|
|
application name. This allows dumping of all apps even if an app
|
|
|
|
hasn't registered yet.
|
|
|
|
|
|
|
|
* 'ari set debug' now displays requests and responses as well as events.
|
|
|
|
|
2016-11-24 00:27:54 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 14.1.0 to Asterisk 14.2.0 ------------
|
2016-09-19 11:13:21 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
2016-11-08 16:11:41 +00:00
|
|
|
AMI
|
|
|
|
------------------
|
|
|
|
* Events that reference a bridge may now contain two new optional fields:
|
|
|
|
- 'BridgeVideoSourceMode': the video source mode for the bridge.
|
|
|
|
Can be one of 'none', 'talker', or 'single'.
|
|
|
|
- 'BridgeVideoSource': the unique ID of the channel that is the video
|
|
|
|
source in this bridge, if one exists.
|
|
|
|
|
|
|
|
* A new event, BridgeVideoSourceUpdate, has been added with a class
|
|
|
|
authorization of CALL. The event is raised when the video source changes
|
|
|
|
in a multi-party mixing bridge.
|
|
|
|
|
|
|
|
ARI
|
|
|
|
------------------
|
|
|
|
* The bridges resource now exposes two new operations:
|
|
|
|
- POST /bridges/{bridgeId}/videoSource/{channelId}: Set a video source in a
|
|
|
|
multi-party mixing bridge
|
|
|
|
- DELETE /bridges/{bridgeId}/videoSource: Remove the set video source,
|
|
|
|
reverting to talk detection for the video source
|
|
|
|
|
|
|
|
* The bridge model in any returned response or event now contains the following
|
|
|
|
optional fields:
|
|
|
|
- video_mode: the video source mode for the bridge. Can be one of 'none',
|
|
|
|
'talker', or 'single'.
|
|
|
|
- video_source_id: the unique ID of the channel that is the video source
|
|
|
|
in this bridge, if one exists.
|
|
|
|
|
|
|
|
* A new event, BridgeVideoSourceChanged, has been added for bridges.
|
|
|
|
Applications subscribed to a bridge will receive this event when the source
|
|
|
|
of video changes in a mixing bridge.
|
|
|
|
|
2016-11-18 15:46:48 +00:00
|
|
|
* The ARI major version has been bumped. There are not any known breaking changes
|
|
|
|
in ARI. The major version has been bumped because otherwise we can end up with
|
|
|
|
overlapping version numbers between different Asterisk versions. Now each major
|
|
|
|
version of Asterisk will bring with it a change in the major version of ARI.
|
|
|
|
The ARI version in Asterisk 14 is now 2.0.0.
|
|
|
|
|
2016-09-19 11:13:21 +00:00
|
|
|
res_pjsip
|
|
|
|
------------------
|
|
|
|
* Automatic dual stack support is now implemented. Depending on DNS resolution
|
|
|
|
and the transport used for sending a message the SIP signaling and SDP will
|
|
|
|
be updated with the correct IP address and protocol version. This means that
|
|
|
|
the rtp_ipv6 and t38_udptl_ipv6 options no longer have any effect. The
|
|
|
|
res_pjsip_multihomed module has also been moved into core res_pjsip to ensure
|
|
|
|
that messages are updated with the correct address information in all cases.
|
|
|
|
|
2016-10-23 12:38:59 +00:00
|
|
|
chan_pjsip
|
|
|
|
------------------
|
|
|
|
* The default behavior for RTP codecs has been changed. The sending codec will
|
|
|
|
now match the receiving codec. This can be turned off and behavior reverted
|
|
|
|
to asymmetric using the "asymmetric_rtp_codec" endpoint option. If this
|
|
|
|
option is set then the sending and received codec are allowed to differ.
|
|
|
|
|
2016-10-20 12:27:21 +00:00
|
|
|
CLI Commands
|
|
|
|
------------------
|
|
|
|
* Three new CLI commands have been added for ARI:
|
|
|
|
- ari show apps:
|
|
|
|
Displays a listing of all registered ARI applications.
|
|
|
|
- ari show app <name>:
|
|
|
|
Display detailed information about a registered ARI application.
|
|
|
|
- ari set debug <name> <on|off>:
|
|
|
|
Enable/disable debugging of an ARI application. When debugged, verbose
|
|
|
|
information will be sent to the Asterisk CLI.
|
|
|
|
|
|
|
|
|
2016-11-10 14:33:41 +00:00
|
|
|
Queue
|
|
|
|
------------------
|
|
|
|
* A new dialplan variable, ABANDONED, is set when the call is not answered
|
|
|
|
by an agent.
|
|
|
|
|
2016-11-11 16:45:37 +00:00
|
|
|
res_ari
|
|
|
|
------------------
|
|
|
|
* The configuration file ari.conf now supports a channelvars option, which
|
|
|
|
specifies a list of channel variables to include in each channel-oriented
|
|
|
|
ARI event.
|
|
|
|
|
2016-09-19 11:13:21 +00:00
|
|
|
------------------------------------------------------------------------------
|
2016-11-24 00:27:54 +00:00
|
|
|
--- Functionality changes from Asterisk 14.0.0 to Asterisk 14.1.0 ------------
|
2016-08-07 14:58:59 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
build: Add download capability for external packages
The DPMA and g729a, silk, siren7 and siren14 codecs hosted at
http://downloads.digium.com/pub/telephony/ are now listed in the
"External" sections of the "Resource Modules" and "Codec Translators"
pages in menuselect. Any that are selected will automatically be
downloaded and installed when "make install" is run. Their LICENSE and
README (if avaialble) files will be installed to
ASTVARLIBDIR/documentation/thirdparty/<product_name>.
Example use with codecs:
The codecs/codecs.xml file is a menuselect style xml file that lists
the codecs to be included. Their support levels are 'external', which
triggers the download and install, and defaultenabled is no. Also
because codec_g729a is actually in a directory named codec_g729 on the
download server, the newly added 'member_data' element is used to
override the default of the directory name being the package name. You
can use the 'directory_name' attribute to keep default base URL
(http://downloads.digium.com/pub/telephony/) but use the new directory,
or you use the 'remote_url' attribute to specify a full URL to the
download directory. In this case, you must still follow the same
subdirectory naming conventions as that used for the packages located
at 'http://downloads.digium.com/pub/telephony'.
A new configure option '--with-externals-cache' was added and like
'--with-sounds-cache' it allows the installer to cache tarballs so
they're not downloaded every time.
To assist with the download and install process, each external package
now has a manifest.xml file that, among other things, contains a package
version and checksums for each file in the tarball. The manifest is
saved to both the cache directory and ASTMODDIR and together with the
manifest.xml on the downloads site, tells the install scripts whether
a download and/or update is needed.
bash and xmlstarlet are required for downloader operation. If they're
not installed, the external items in menuselect will be unavailable.
Change-Id: Id3dcf1289ffd3cb0bbd7dfab3cafbb87be60323a
2016-08-02 01:55:33 +00:00
|
|
|
Build System
|
|
|
|
------------------
|
|
|
|
* The res_digium_phone, codec_g729a, codec_silk, codec_siren7 and
|
|
|
|
codec_siren14 binary modules hosted at downloads.digium.com can now be
|
|
|
|
automatically downloaded and installed during the Asterisk install
|
|
|
|
process. If selected in menuselect, when 'make install' is run, the
|
|
|
|
script will check the downloads site for a new version and download
|
|
|
|
and install it if needed. The '--with-externals-cache' option to
|
|
|
|
./configure can be used to specify a location to cache the latest
|
|
|
|
tarballs so they don't have to be re-downloaded for every install.
|
|
|
|
|
2016-08-07 14:58:59 +00:00
|
|
|
app_voicemail
|
|
|
|
------------------
|
|
|
|
* Added "tps_queue_high" and "tps_queue_low" options.
|
|
|
|
The options can modify the taskprocessor alert levels for this module.
|
|
|
|
Additional information can be found in the sample configuration file at
|
|
|
|
config/samples/voicemail.conf.sample.
|
|
|
|
|
|
|
|
res_pjsip_mwi
|
|
|
|
------------------
|
|
|
|
* Added "mwi_tps_queue_high" and "mwi_tps_queue_low" global configuration
|
|
|
|
options to tune taskprocessor alert levels.
|
|
|
|
|
|
|
|
* Added "mwi_disable_initial_unsolicited" global configuration option
|
|
|
|
to disable sending unsolicited MWI to all endpoints on startup.
|
|
|
|
Additional information can be found in the sample configuration file at
|
|
|
|
config/samples/pjsip.conf.sample.
|
|
|
|
|
|
|
|
chan_pjsip
|
|
|
|
------------------
|
|
|
|
* A new dialplan function, PJSIP_SEND_SESSION_REFRESH, has been added. When
|
|
|
|
invoked, a re-INVITE or UPDATE request will be sent immediately to the
|
|
|
|
endpoint underlying the channel. When used in combination with the existing
|
|
|
|
dialplan function PJSIP_MEDIA_OFFER, this allows the formats on a PJSIP
|
|
|
|
channel to be re-negotiated and updated after session set up.
|
|
|
|
|
2016-08-16 20:36:10 +00:00
|
|
|
res_pjsip
|
|
|
|
------------------
|
|
|
|
* A new endpoint configuration parameter 'contact_user' has been added which
|
|
|
|
when set will override the default user set on Contact headers in outgoing
|
|
|
|
requests.
|
2016-08-07 14:58:59 +00:00
|
|
|
|
2016-08-05 01:11:29 +00:00
|
|
|
* If you are using a sorcery realtime backend to store global res_pjsip
|
|
|
|
options (ps_globals table) then you now have to do a res_pjsip reload for
|
|
|
|
changes to these options to take effect. If you are using pjsip.conf to
|
|
|
|
configure these options then you already had to do a reload after making
|
|
|
|
changes.
|
|
|
|
|
2016-08-29 23:08:22 +00:00
|
|
|
* Added "ignore_uri_user_options" global configuration option for
|
|
|
|
compatibility with an ITSP that sends URI user field options. When enabled
|
|
|
|
the user field is truncated at the first semicolon.
|
|
|
|
Example:
|
|
|
|
URI: "sip:1235557890;phone-context=national@x.x.x.x;user=phone"
|
|
|
|
The user field is "1235557890;phone-context=national"
|
|
|
|
Which is truncated to this: "1235557890"
|
|
|
|
|
|
|
|
Note: The caller-id and redirecting number strings obtained from incoming
|
|
|
|
SIP URI user fields are now always truncated at the first semicolon.
|
|
|
|
|
2016-10-04 23:24:54 +00:00
|
|
|
res_rtp_asterisk
|
|
|
|
------------------
|
|
|
|
* An option, ice_blacklist, has been added which allows certain subnets to be
|
|
|
|
excluded from local ICE candidates.
|
|
|
|
|
2016-08-10 20:14:09 +00:00
|
|
|
app_confbridge
|
|
|
|
------------------
|
|
|
|
* Some sounds played into the bridge are played asynchronously. This, for
|
|
|
|
instance, allows a channel to immediately exit the ConfBridge without having
|
|
|
|
to wait for a leave announcement to play.
|
|
|
|
|
2016-10-06 14:58:26 +00:00
|
|
|
app_dial
|
|
|
|
------------------
|
|
|
|
* Added the "Q" option which sets the Q.850/Q.931 cause on unanswered channels
|
|
|
|
when another channel answers the call. The default of ANSWERED_ELSEWHERE
|
|
|
|
is unchanged.
|
|
|
|
|
2016-10-16 01:05:05 +00:00
|
|
|
res_ari
|
|
|
|
------------------
|
|
|
|
* ARI events will all now include a new field in the root of the JSON message,
|
|
|
|
'asterisk_id'. This will be the unique ID for the Asterisk system
|
|
|
|
transmitting the event. The value can be overridden using the 'entityid'
|
|
|
|
setting in asterisk.conf.
|
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 13 to Asterisk 14 --------------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
2016-05-09 20:00:56 +00:00
|
|
|
AMI
|
|
|
|
-----------------
|
|
|
|
* A new event, "DialState" has been added. This is similar to "DialBegin" and
|
|
|
|
"DialEnd" in that it tracks the state of a dialed call. The difference is that
|
|
|
|
this indicates some intermediate state change in the dial attempt, such as
|
|
|
|
"RINGING", "PROGRESS", or "PROCEEDING".
|
|
|
|
|
2016-03-30 22:01:28 +00:00
|
|
|
ARI
|
|
|
|
-----------------
|
|
|
|
* A new ARI method has been added to the channels resource. "create" allows for
|
2016-05-15 17:22:42 +00:00
|
|
|
you to create a new channel and place that channel into a Stasis application.
|
|
|
|
This is similar to origination except that the specified channel is not
|
|
|
|
dialed. This allows for an application writer to create a channel, perform
|
|
|
|
manipulations on it, and then delay dialing the channel until later.
|
2016-03-30 22:01:28 +00:00
|
|
|
|
2016-05-15 17:22:42 +00:00
|
|
|
* To complement the "create" method, a "dial" method has been added to the
|
|
|
|
channels resource in order to place a call to a created channel.
|
2016-03-30 22:18:39 +00:00
|
|
|
|
ARI: Add the ability to play multiple media URIs in a single operation
Many ARI applications will want to play multiple media files in a row to
a resource. The most common use case is when building long-ish IVR prompts
made up of multiple, smaller sound files. Today, that requires building a
small state machine, listening for each PlaybackFinished event, and triggering
the next sound file to play. While not especially challenging, it is tedious
work. Since requiring developers to write tedious code to do normal activities
stinks, this patch adds the ability to play back a list of media files to a
resource.
Each of the 'play' operations on supported resources (channels and bridges)
now accepts a comma delineated list of media URIs to play. A single Playback
resource is created as a handle to the entire list. The operation of playing
a list is identical to playing a single media URI, save that a new event,
PlaybackContinuing, is raised instead of a PlaybackFinished for each non-final
media URI. When the entire list is finished being played, a PlaybackFinished
event is raised.
In order to help inform applications where they are in the list playback, the
Playback resource now includes a new, optional attribute, 'next_media_uri',
that contains the next URI in the list to be played.
It's important to note the following:
- If an offset is provided to the 'play' operations, it only applies to the
first media URI, as it would be weird to skip n seconds forward in every
media resource.
- Operations that control the position of the media only affect the current
media being played. For example, once a media resource in the list
completes, a 'reverse' operation on a subsequent media resource will not
start a previously completed media resource at the appropiate offset.
- This patch does not add any new operations to control the list. Hopefully,
user feedback and/or future patches would add that if people want it.
ASTERISK-26022 #close
Change-Id: Ie1ea5356573447b8f51f2e7964915ea01792f16f
2016-04-18 23:17:08 +00:00
|
|
|
* All operations that initiate playback of media on a resource now support
|
|
|
|
a list of media URIs. The list of URIs are played in the order they are
|
|
|
|
presented to the resource. A new event, "PlaybackContinuing", is raised when
|
|
|
|
a media URI finishes but before the next media URI starts. When a list is
|
|
|
|
played, the "Playback" model will contain the optional attribute
|
|
|
|
"next_media_uri", which specifies the next media URI in the list to be played
|
|
|
|
back to the resource. The "PlaybackFinished" event is raised when all media
|
|
|
|
URIs are done.
|
|
|
|
|
2016-05-18 11:19:58 +00:00
|
|
|
* Stored recordings now allow for the media associated with a stored recording
|
|
|
|
to be retrieved. The new route, GET /recordings/stored/{name}/file, will
|
|
|
|
transmit the raw media file to the requester as binary.
|
|
|
|
|
2016-05-15 17:22:42 +00:00
|
|
|
|
2016-05-09 20:00:56 +00:00
|
|
|
* "Dial" events have been modified to not only be sent when dialing begins and ends.
|
|
|
|
They now are also sent for intermediate states, such as "RINGING", "PROGRESS", and
|
|
|
|
"PROCEEDING".
|
|
|
|
|
2014-12-22 02:35:05 +00:00
|
|
|
Applications
|
|
|
|
------------------
|
|
|
|
|
2015-11-18 08:25:15 +00:00
|
|
|
BridgeAdd
|
|
|
|
------------------
|
|
|
|
* A new application in Asterisk, this will join the calling channel
|
|
|
|
to an existing bridge containing the named channel prefix.
|
|
|
|
|
2016-04-01 12:50:30 +00:00
|
|
|
ChanSpy
|
|
|
|
------------------
|
|
|
|
* Added the 'l' option, which forces ChanSpy's audiohook to use a long queue
|
|
|
|
to store the audio frames. This option is useful if audio loss is
|
|
|
|
experienced when using ChanSpy, but may introduce some delay in the audio
|
|
|
|
feed on the listening channel.
|
|
|
|
|
2016-07-19 18:39:38 +00:00
|
|
|
Codecs
|
|
|
|
------------------
|
|
|
|
* Added format attribute negotiation for the iLBC audio codec. Format attribute
|
|
|
|
negotiation is provided by the res_format_attr_ilbc module. iLBC 20 is the
|
|
|
|
default now. Falls back to iLBC 30, when the remote party requests this.
|
|
|
|
|
2014-12-22 02:35:05 +00:00
|
|
|
ConfBridge
|
|
|
|
------------------
|
|
|
|
* Added the ability to pass options to MixMonitor when recording is used with
|
|
|
|
ConfBridge. This includes the addition of the following configuration
|
|
|
|
parameters for the 'bridge' object:
|
|
|
|
- record_file_timestamp: whether or not to append the start time to the
|
|
|
|
recorded file name
|
|
|
|
- record_options: the options to pass to the MixMonitor application
|
|
|
|
- record_command: a command to execute when recording is finished
|
|
|
|
Note that these options may also be with the CONFBRIDGE function.
|
|
|
|
|
2015-12-26 21:29:04 +00:00
|
|
|
ControlPlayback
|
|
|
|
------------------
|
|
|
|
* Remote files can now be retrieved and played back. See the Playback
|
|
|
|
dialplan application for more details.
|
|
|
|
|
2016-05-03 16:11:20 +00:00
|
|
|
FollowMe
|
|
|
|
------------------
|
|
|
|
* It is now possible to disable the prompt from a callee by setting
|
|
|
|
'enable_callee_prompt = no' in followme.conf.
|
|
|
|
|
2015-12-26 21:29:04 +00:00
|
|
|
Playback
|
|
|
|
------------------
|
|
|
|
* Remote files can now be retrieved and played back via the Playback and other
|
|
|
|
media playback dialplan applications. This is done by directly providing
|
|
|
|
the URL to play to the dialplan application:
|
|
|
|
same => n,Playback(http://1.1.1.1/howler-monkeys-fl.wav)
|
|
|
|
Note that unlike 'normal' media files, the entire URI to the file must be
|
|
|
|
provided, including the file extension. Currently, on HTTP and HTTPS URI
|
|
|
|
schemes are supported.
|
|
|
|
|
2016-05-15 17:22:42 +00:00
|
|
|
Queue
|
|
|
|
-------------------
|
|
|
|
* Added field ReasonPause on QueueMemberStatus if set when paused, the reason
|
|
|
|
the queue member was paused.
|
|
|
|
|
|
|
|
* Added field LastPause on QueueMemberStatus for time when started the last
|
|
|
|
pause for a queue member.
|
|
|
|
|
|
|
|
* Show the time when started the last pause for queue member on CLI for command
|
|
|
|
'queue show'.
|
|
|
|
|
2015-03-14 01:53:13 +00:00
|
|
|
SMS
|
|
|
|
------------------
|
|
|
|
* Added the 'n' option, which prevents the SMS from being written to the log
|
|
|
|
file. This is needed for those countries with privacy laws that require
|
|
|
|
providers to not log SMS content.
|
|
|
|
|
2014-12-22 02:35:05 +00:00
|
|
|
|
2014-08-28 16:06:55 +00:00
|
|
|
Channel Drivers
|
|
|
|
------------------
|
2014-08-10 22:02:03 +00:00
|
|
|
|
2014-12-18 20:09:21 +00:00
|
|
|
chan_dahdi
|
|
|
|
------------------
|
|
|
|
* The CALLERID(ani2) value for incoming calls is now populated in featdmf
|
|
|
|
signaling mode. The information was previously discarded.
|
2016-05-15 17:22:42 +00:00
|
|
|
|
2015-04-29 19:29:10 +00:00
|
|
|
* Added the force_restart_unavailable_chans compatibility option. When
|
|
|
|
enabled it causes Asterisk to restart the ISDN B channel if an outgoing
|
|
|
|
call receives cause 44 (Requested channel not available).
|
2014-12-18 20:09:21 +00:00
|
|
|
|
2015-01-20 16:59:30 +00:00
|
|
|
chan_iax2
|
|
|
|
------------------
|
|
|
|
* The iax.conf forcejitterbuffer option has been removed. It is now always
|
|
|
|
forced if you set iax.conf jitterbuffer=yes. If you put a jitter buffer
|
|
|
|
on a channel it will be on the channel.
|
2016-05-15 17:22:42 +00:00
|
|
|
|
2015-04-10 12:23:42 +00:00
|
|
|
* A new configuration parameters, 'calltokenexpiration', has been added that
|
|
|
|
controls the duration before a call token expires. Default duration is 10
|
|
|
|
seconds. Setting this to a higher value may help in lagged networks or those
|
|
|
|
experiencing high packet loss.
|
2015-01-20 16:59:30 +00:00
|
|
|
|
2016-08-24 09:44:15 +00:00
|
|
|
* Plaintext auth mode is deprecated and removed from possible default modes.
|
|
|
|
|
2016-06-01 21:57:36 +00:00
|
|
|
chan_rtp (was chan_multicast_rtp)
|
|
|
|
------------------
|
|
|
|
* Added unicast RTP support and renamed chan_multicast_rtp to chan_rtp.
|
|
|
|
|
|
|
|
* The format for dialing a unicast RTP channel is:
|
|
|
|
UnicastRTP/<destination-addr>[/[<options>]]
|
|
|
|
Where <destination-addr> is something like '127.0.0.1:5060'.
|
|
|
|
Where <options> are in standard Asterisk flag options format:
|
|
|
|
c(<codec>) - Specify which codec/format to use such as 'ulaw'.
|
|
|
|
e(<engine>) - Specify which RTP engine to use such as 'asterisk'.
|
|
|
|
|
|
|
|
* New options were added for a multicast RTP channel. The format for
|
|
|
|
dialing a multicast RTP channel is:
|
|
|
|
MulticastRTP/<type>/<destination-addr>[/[<control-addr>][/[<options>]]]
|
|
|
|
Where <type> can be either 'basic' or 'linksys'.
|
|
|
|
Where <destination-addr> is something like '224.0.0.3:5060'.
|
|
|
|
Where <control-addr> is something like '127.0.0.1:5060'.
|
|
|
|
Where <options> are in standard Asterisk flag options format:
|
|
|
|
c(<codec>) - Specify which codec/format to use such as 'ulaw'.
|
|
|
|
i(<address>) - Specify the interface address from which multicast RTP
|
|
|
|
is sent.
|
|
|
|
l(<enable>) - Set whether packets are looped back to the sender. The
|
|
|
|
enable value can be 0 to set looping to off and non-zero to set
|
|
|
|
looping on.
|
|
|
|
t(<ttl>) - Set the time-to-live (TTL) value for multicast packets.
|
|
|
|
|
2014-08-28 16:06:55 +00:00
|
|
|
chan_sip
|
|
|
|
------------------
|
|
|
|
* New 'rtpbindaddr' global setting. This allows a user to define which
|
2014-09-25 20:49:04 +00:00
|
|
|
ipaddress to bind the rtpengine to. For example, chan_sip might bind
|
2014-08-28 16:06:55 +00:00
|
|
|
to eth0 (10.0.0.2) but rtpengine to eth1 (192.168.1.10).
|
2016-05-15 17:22:42 +00:00
|
|
|
|
2014-11-15 16:31:24 +00:00
|
|
|
* DTLS related configuration options can now be set at a general level.
|
|
|
|
Enabling DTLS support, though, requires enabling it at the user
|
|
|
|
or peer level.
|
2016-05-15 17:22:42 +00:00
|
|
|
|
2016-02-19 10:30:15 +00:00
|
|
|
* Added the possibility to set the From: header through the the SIP dial
|
|
|
|
string (populating the fromuser/fromdomain fields), complementing the
|
|
|
|
[!dnid] option for the To: header that has existed since 1.6.0 (1d6b192).
|
|
|
|
NOTE: This is again separated by an exclamation mark, so the To: header may
|
|
|
|
not contain one of those.
|
2014-08-10 22:02:03 +00:00
|
|
|
|
2016-07-19 11:16:02 +00:00
|
|
|
* Session-Timers (RFC 4028) work for TCP (and TLS) transports as well now.
|
|
|
|
Previously Asterisk dropped calls only with UDP transports. However with
|
|
|
|
longer international calls via TCP, the SIP channel might break, because
|
|
|
|
all hops on the Internet route must stay online (have not a single power
|
|
|
|
outage, for example). Therefore with Session-Timers enabled (which are
|
|
|
|
enabled at default), you might see additional dropped calls. Consequently
|
|
|
|
please, consider to go for session-timers=refuse in your sip.conf.
|
|
|
|
|
2014-10-17 11:30:23 +00:00
|
|
|
chan_pjsip
|
|
|
|
------------------
|
|
|
|
* New 'user_eq_phone' endpoint setting. This adds a 'user=phone' parameter
|
2016-05-15 17:22:42 +00:00
|
|
|
to the request URI and From URI if the user is determined to be a phone
|
|
|
|
number.
|
|
|
|
|
|
|
|
* New 'moh_passthrough' endpoint setting. This will pass hold and unhold
|
|
|
|
requests through using SIP re-invites with sendonly and sendrecv accordingly.
|
|
|
|
|
2014-11-03 18:22:59 +00:00
|
|
|
* Added the pjsip.conf system type disable_tcp_switch option. The option
|
|
|
|
allows the user to disable switching from UDP to TCP transports described
|
|
|
|
by RFC 3261 section 18.1.1.
|
2016-05-15 17:22:42 +00:00
|
|
|
|
|
|
|
* New 'line' and 'endpoint' options added on outbound registrations. This
|
|
|
|
allows some identifying information to be added to the Contact of the
|
|
|
|
outbound registration. If this information is present on messages received
|
|
|
|
from the remote server the message will automatically be associated with the
|
|
|
|
configured endpoint on the outbound registration.
|
|
|
|
|
2014-09-14 15:41:58 +00:00
|
|
|
|
main/stasis: Allow subscriptions to use a threadpool for message delivery
Prior to this patch, all Stasis subscriptions would receive a dedicated
thread for servicing published messages. In contrast, prior to r400178
(see review https://reviewboard.asterisk.org/r/2881/), the subscriptions
shared a thread pool. It was discovered during some initial work on Stasis
that, for a low subscription count with high message throughput, the
threadpool was not as performant as simply having a dedicated thread per
subscriber.
For situations where a subscriber receives a substantial number of messages
and is always present, the model of having a dedicated thread per subscriber
makes sense. While we still have plenty of subscriptions that would follow
this model, e.g., AMI, CDRs, CEL, etc., there are plenty that also fall into
the following two categories:
* Large number of subscriptions, specifically those tied to endpoints/peers.
* Low number of messages. Some subscriptions exist specifically to coordinate
a single message - the subscription is created, a message is published, the
delivery is synchronized, and the subscription is destroyed.
In both of the latter two cases, creating a dedicated thread is wasteful (and
in the case of a large number of peers/endpoints, harmful). In those cases,
having shared delivery threads is far more performant.
This patch adds the ability of a subscriber to Stasis to choose whether or not
their messages are dispatched on a dedicated thread or on a threadpool. The
threadpool is configurable through stasis.conf.
Review: https://reviewboard.asterisk.org/r/4193
ASTERISK-24533 #close
Reported by: xrobau
Tested by: xrobau
........
Merged revisions 428681 from http://svn.asterisk.org/svn/asterisk/branches/12
........
Merged revisions 428687 from http://svn.asterisk.org/svn/asterisk/branches/13
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@428688 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2014-12-01 17:59:21 +00:00
|
|
|
Core
|
|
|
|
------------------
|
|
|
|
* The core of Asterisk uses a message bus called "Stasis" to distribute
|
|
|
|
information to internal components. For performance reasons, the message
|
|
|
|
distribution was modified to make use of a thread pool instead of a
|
|
|
|
dedicated thread per consumer in certain cases. The initial settings for
|
|
|
|
the thread pool can now be configured in 'stasis.conf'.
|
|
|
|
|
2015-04-13 13:47:01 +00:00
|
|
|
* A new core DNS API has been implemented which provides a common interface
|
|
|
|
for DNS functionality. Modules that use this functionality will require that
|
|
|
|
a DNS resolver module is loaded and available.
|
|
|
|
|
2015-05-06 13:31:33 +00:00
|
|
|
* Modified processing of command-line options to first parse only what
|
|
|
|
is necessary to read asterisk.conf. Once asterisk.conf is fully loaded,
|
|
|
|
the remaining options are processed. The -X option now applies to
|
|
|
|
asterisk.conf only. To enable #exec for other config files you must
|
|
|
|
set execincludes=yes in asterisk.conf. Any other option set on the
|
|
|
|
command-line will now override the equivalent setting from asterisk.conf.
|
main/stasis: Allow subscriptions to use a threadpool for message delivery
Prior to this patch, all Stasis subscriptions would receive a dedicated
thread for servicing published messages. In contrast, prior to r400178
(see review https://reviewboard.asterisk.org/r/2881/), the subscriptions
shared a thread pool. It was discovered during some initial work on Stasis
that, for a low subscription count with high message throughput, the
threadpool was not as performant as simply having a dedicated thread per
subscriber.
For situations where a subscriber receives a substantial number of messages
and is always present, the model of having a dedicated thread per subscriber
makes sense. While we still have plenty of subscriptions that would follow
this model, e.g., AMI, CDRs, CEL, etc., there are plenty that also fall into
the following two categories:
* Large number of subscriptions, specifically those tied to endpoints/peers.
* Low number of messages. Some subscriptions exist specifically to coordinate
a single message - the subscription is created, a message is published, the
delivery is synchronized, and the subscription is destroyed.
In both of the latter two cases, creating a dedicated thread is wasteful (and
in the case of a large number of peers/endpoints, harmful). In those cases,
having shared delivery threads is far more performant.
This patch adds the ability of a subscriber to Stasis to choose whether or not
their messages are dispatched on a dedicated thread or on a threadpool. The
threadpool is configurable through stasis.conf.
Review: https://reviewboard.asterisk.org/r/4193
ASTERISK-24533 #close
Reported by: xrobau
Tested by: xrobau
........
Merged revisions 428681 from http://svn.asterisk.org/svn/asterisk/branches/12
........
Merged revisions 428687 from http://svn.asterisk.org/svn/asterisk/branches/13
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@428688 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2014-12-01 17:59:21 +00:00
|
|
|
|
2015-05-14 22:12:41 +00:00
|
|
|
* The TLS core in Asterisk now supports X.509 certificate subject alternative
|
|
|
|
names. This way one X.509 certificate can be used for hosts that can be
|
|
|
|
reached under multiple DNS names or for multiple hosts.
|
|
|
|
|
main/logger: Add log formatters and JSON structured logs
When Asterisk is part of a larger distributed system, log files are often
gathered using tools (such as logstash) that prefer to consume information
and have it rendered using other tools (such as Kibana) that prefer a
structured format, e.g., JSON. This patch adds support for JSON formatted
logs by adding support for an optional log format specifier in Asterisk's
logging subsystem. By adding a format specifier of '[json]':
full => [json]debug,verbose,notice,warning,error
Log messages will be output to the 'full' channel in the following
format:
{
"hostname": Hostname or name specified in asterisk.conf
"timestamp": Date/Time
"identifiers": {
"lwp": Thread ID,
"callid": Call Identifier
}
"logmsg": {
"location": {
"filename": Name of the file that generated the log statement
"function": Function that generated the log statement
"line": Line number that called the logging function
}
"level": Log level, e.g., DEBUG, VERBOSE, etc.
"message": Actual text of the log message
}
}
ASTERISK-25425 #close
Change-Id: I8649bfedf3fb7bf3138008cc11565553209cc238
2015-09-21 12:26:00 +00:00
|
|
|
* The Asterisk logging system now supports JSON structured logging. Log
|
|
|
|
channels specified in logger.conf or added dynamically via CLI commands now
|
|
|
|
support an optional specifier prior to their levels that determines their
|
|
|
|
formatting. To set a log channel to format its entries as JSON, a formatter
|
|
|
|
of '[json]' can be set, e.g.,
|
|
|
|
full => [json]debug,verbose,notice,warning,error
|
|
|
|
|
2015-12-26 21:29:04 +00:00
|
|
|
* The core now supports a 'media cache', which stores temporary media files
|
|
|
|
retrieved from external sources. CLI commands have been added to manipulate
|
|
|
|
and display the cached files, including:
|
|
|
|
- 'media cache show <all>' - show all cached media files, or details about
|
|
|
|
one particular cached media file
|
|
|
|
- 'media cache refresh <item>' - force a refresh of a particular media file
|
|
|
|
in the cache
|
|
|
|
- 'media cache delete <item>' - remove an item from the cache
|
|
|
|
- 'media cache create <uri>' - retrieve a URI and store it in the cache
|
|
|
|
|
2016-08-11 17:01:33 +00:00
|
|
|
* The ability for device state hints to be automatically created as a result of
|
|
|
|
device state changes now exists in the PBX. This functionality is referred to
|
|
|
|
as "autohints" and is configurable in extensions.conf by placing "autohints=yes"
|
|
|
|
in the context. If enabled a device state hint will be automatically created
|
|
|
|
with the name of the device.
|
2016-05-15 17:22:42 +00:00
|
|
|
|
2016-06-27 19:26:54 +00:00
|
|
|
* If Asterisk is built with systemd support, and run under systemd, it will
|
|
|
|
notify systemd of its state using sd_notify. Use 'Type=notify' in
|
|
|
|
asterisk.service.
|
|
|
|
|
2014-09-09 20:15:57 +00:00
|
|
|
Functions
|
|
|
|
------------------
|
2016-05-12 20:18:22 +00:00
|
|
|
* The func_odbc global option "single_db_connection" default value has been
|
|
|
|
changed to 'no'.
|
2014-09-09 20:15:57 +00:00
|
|
|
|
2016-06-03 06:20:39 +00:00
|
|
|
|
|
|
|
Formats
|
|
|
|
------------------
|
|
|
|
* New module format_ogg_speex added which supports Speex codec inside
|
|
|
|
Ogg containers (filename extension .spx).
|
|
|
|
|
|
|
|
|
2014-09-09 20:15:57 +00:00
|
|
|
CHANNEL
|
|
|
|
------------------
|
|
|
|
* Added CHANNEL(onhold) item that returns 1 (onhold) and 0 (not-onhold) for
|
|
|
|
the hold status of a channel.
|
|
|
|
|
2014-10-26 01:21:18 +00:00
|
|
|
CURL
|
|
|
|
------------------
|
|
|
|
* The CURL function now supports a write option, which will save the retrieved
|
|
|
|
file to a location on disk. As an example:
|
|
|
|
same => n,Set(CURL(https://1.1.1.1/foo.wav)=/tmp/foo.wav)
|
|
|
|
will save 'foo.wav' to /tmp.
|
|
|
|
|
2014-11-17 16:58:52 +00:00
|
|
|
DTMF Features
|
|
|
|
------------------
|
|
|
|
* The transferdialattempts default value has been changed from 1 to 3. The
|
2016-05-15 17:22:42 +00:00
|
|
|
transferinvalidsound has been changed from "pbx-invalid" to
|
|
|
|
"privacy-incorrect". These were changed to make DTMF transfers be more
|
|
|
|
user-friendly by default.
|
2014-11-17 16:58:52 +00:00
|
|
|
|
2014-09-14 15:41:58 +00:00
|
|
|
|
|
|
|
Resources
|
|
|
|
------------------
|
|
|
|
|
2015-01-29 14:38:23 +00:00
|
|
|
res_http_media_cache
|
|
|
|
------------------
|
|
|
|
* A backend for the core media cache, this module retrieves media files from
|
|
|
|
a remote HTTP(S) server and stores them in the core media cache for later
|
|
|
|
playback.
|
|
|
|
|
2014-09-14 15:41:58 +00:00
|
|
|
res_musiconhold
|
|
|
|
------------------
|
|
|
|
* Added sort=randstart to the sort options. It sorts the files by name and
|
|
|
|
then chooses the first file to play at random.
|
2014-09-25 20:49:04 +00:00
|
|
|
* Added preferchannelclass=no option to prefer the application-passed class
|
|
|
|
over the channel-set musicclass. This allows separate hold-music from
|
|
|
|
application (e.g. Queue or Dial) specified music.
|
2014-09-14 15:41:58 +00:00
|
|
|
|
2015-04-13 13:47:01 +00:00
|
|
|
res_resolver_unbound
|
|
|
|
------------------
|
|
|
|
* Added a res_resolver_unbound module which uses the libunbound resolver library
|
|
|
|
to perform DNS resolution. This module requires the libunbound library to be
|
|
|
|
installed in order to be used.
|
|
|
|
|
|
|
|
res_pjsip
|
|
|
|
------------------
|
|
|
|
* A new SIP resolver using the core DNS API has been implemented. This relies on
|
|
|
|
external SIP resolver support in PJSIP which is only available as of PJSIP
|
|
|
|
2.4. If this support is unavailable the existing built-in PJSIP SIP resolver
|
|
|
|
will be used instead. The new SIP resolver provides NAPTR support, improved
|
|
|
|
SRV support, and AAAA record support.
|
2015-04-08 11:35:53 +00:00
|
|
|
|
2016-05-10 02:40:08 +00:00
|
|
|
res_pjsip_info_empty
|
|
|
|
--------------------
|
|
|
|
* A new module that can respond to empty Content-Type INFO packets during call.
|
|
|
|
Some SBCs will terminate a call if their empty INFO packets are not responded
|
|
|
|
to within a predefined time.
|
|
|
|
|
2015-10-21 17:22:19 +00:00
|
|
|
res_pjsip_outbound_registration
|
|
|
|
-------------------------------
|
|
|
|
* A new 'fatal_retry_interval' option has been added to outbound registration.
|
|
|
|
When set (default is zero), and upon receiving a failure response to an
|
|
|
|
outbound registration, registration is retried at the given interval up to
|
|
|
|
'max_retries'.
|
|
|
|
|
2016-05-03 21:07:23 +00:00
|
|
|
res_pjsip_outbound_publish
|
|
|
|
------------------
|
|
|
|
* Added a new multi_user option that when set to 'yes' allows a given configuration
|
|
|
|
to be used for multiple users.
|
2016-05-15 17:22:42 +00:00
|
|
|
|
2016-05-10 02:40:08 +00:00
|
|
|
|
2015-04-08 11:35:53 +00:00
|
|
|
CEL Backends
|
|
|
|
------------------
|
|
|
|
|
|
|
|
cel_pgsql
|
|
|
|
------------------
|
2015-04-28 03:01:25 +00:00
|
|
|
* Added a new option, 'usegmtime', which causes timestamps in CEL events
|
|
|
|
to be logged in GMT.
|
2015-04-08 11:35:53 +00:00
|
|
|
|
2015-05-02 03:14:31 +00:00
|
|
|
* Added support to set schema where located the table cel. This settings is
|
|
|
|
configurable for cel_pgsql via the 'schema' in configuration file
|
|
|
|
cel_pgsql.conf.
|
|
|
|
|
2016-05-15 17:22:42 +00:00
|
|
|
|
2015-04-21 22:27:16 +00:00
|
|
|
CDR Backends
|
|
|
|
------------------
|
|
|
|
|
|
|
|
cdr_adaptive_odbc
|
|
|
|
------------------
|
|
|
|
* Added the ability to set the character to quote identifiers. This
|
|
|
|
allows adding the character at the start and end of table and column
|
|
|
|
names. This setting is configurable for cdr_adaptive_odbc via the
|
|
|
|
quoted_identifiers in configuration file cdr_adaptive_odbc.conf.
|
|
|
|
|
2016-05-15 17:22:42 +00:00
|
|
|
cdr_odbc
|
|
|
|
------------------
|
|
|
|
* Added a new configuration option, "newcdrcolumns", which enables use of the
|
|
|
|
post-1.8 CDR columns 'peeraccount', 'linkedid', and 'sequence'.
|
2016-01-23 22:45:30 +00:00
|
|
|
|
2016-05-15 17:22:42 +00:00
|
|
|
cdr_csv
|
|
|
|
------------------
|
|
|
|
* Added a new configuration option, "newcdrcolumns", which enables use of the
|
|
|
|
post-1.8 CDR columns 'peeraccount', 'linkedid', and 'sequence'.
|
|
|
|
|
2016-07-06 14:29:27 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 13.10.0 to Asterisk 13.11.0 ----------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
2016-07-18 21:16:56 +00:00
|
|
|
chan_dahdi
|
|
|
|
------------------
|
|
|
|
* Added "faxdetect_timeout" option.
|
|
|
|
The option determines how many seconds into a call before faxdetect
|
|
|
|
is disabled for the call. Setting the value to zero disables the timeout.
|
|
|
|
|
2016-07-06 14:29:27 +00:00
|
|
|
res_pjsip
|
|
|
|
------------------
|
2016-07-16 01:44:52 +00:00
|
|
|
* Added "fax_detect_timeout" to endpoint.
|
|
|
|
The option determines how many seconds into a call before fax_detect
|
|
|
|
is disabled for the call. Setting the value to zero disables the timeout.
|
|
|
|
|
2016-07-06 14:29:27 +00:00
|
|
|
* Added "subscribe_context" to endpoint.
|
|
|
|
If specified, incoming SUBSCRIBE requests will be searched for the matching
|
|
|
|
extension in the indicated context. If no "subscribe_context" is specified,
|
|
|
|
then the "context" setting is used.
|
|
|
|
|
2016-06-22 12:13:39 +00:00
|
|
|
res_rtp_asterisk
|
|
|
|
------------------
|
|
|
|
* The DTLS part in Asterisk now supports Perfect Forward Secrecy (PFS).
|
|
|
|
Enabling PFS is attempted by default, and is dependent on the configuration
|
|
|
|
of the module using TLS.
|
|
|
|
- Ephemeral ECDH (ECDHE) is enabled by default. To disable it, do not
|
|
|
|
specify a ECDHE cipher suite in sip.conf, for example:
|
|
|
|
dtlscipher=AES128-SHA
|
|
|
|
- Ephemeral DH (DHE) is disabled by default. To enable it, add DH parameters
|
|
|
|
into the private key file, e.g., sip.conf dtlsprivatekey. For example:
|
|
|
|
openssl dhparam -out ./dh.pem 2048
|
|
|
|
- Because clients expect the server to prefer PFS, and because OpenSSL sorts
|
|
|
|
its cipher suites by bit strength, see "openssl ciphers -v DEFAULT".
|
|
|
|
Consider re-ordering your cipher suites in the respective configuration
|
|
|
|
file. For example:
|
|
|
|
dtlscipher=ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256
|
|
|
|
which forces PFS and requires at least DTLS 1.2.
|
|
|
|
|
2016-05-15 17:22:42 +00:00
|
|
|
------------------------------------------------------------------------------
|
2016-04-15 19:26:15 +00:00
|
|
|
--- Functionality changes from Asterisk 13.9.0 to Asterisk 13.10.0 -----------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
2016-05-25 15:34:42 +00:00
|
|
|
Core
|
|
|
|
------------------
|
|
|
|
* A channel variable FORWARDERNAME is now set which indicates which channel
|
|
|
|
was responsible for a forwarding requests received on dial attempt.
|
|
|
|
|
2016-05-12 20:18:22 +00:00
|
|
|
func_odbc
|
|
|
|
------------------
|
|
|
|
* Added new global option "single_db_connection".
|
|
|
|
Enabling this option func_odbc will use a single database connection per DSN.
|
|
|
|
This option is enabled by default.
|
|
|
|
|
2016-05-02 21:08:06 +00:00
|
|
|
res_fax
|
|
|
|
------------------
|
|
|
|
* Added FAXMODE variable to let dialplan know what fax transport was used.
|
|
|
|
FAXMODE variable is set to either "audio" or "T38".
|
|
|
|
|
2016-04-15 19:26:15 +00:00
|
|
|
res_pjsip
|
|
|
|
------------------
|
2016-05-19 19:56:26 +00:00
|
|
|
* Added "via_addr", "via_port", "call_id" to contacts.
|
|
|
|
As res_pjsip_nat rewrites contact's address, only the last Via header
|
|
|
|
can contain the source address of registered endpoint.
|
|
|
|
Also Call-Id header may contain the source address of registered endpoint.
|
|
|
|
Added new fields ViaAddress,CallID to AMI event ContactStatus
|
|
|
|
|
2016-05-13 16:46:52 +00:00
|
|
|
* Endpoint IP Access Controls
|
|
|
|
Added new configuration Endpoint options:
|
|
|
|
"acl" - list of IP ACL section names in acl.conf
|
|
|
|
"deny" - List of IP addresses to deny access from
|
|
|
|
"permit" - List of IP addresses to permit access from
|
|
|
|
"contact_acl" - List of Contact ACL section names in acl.conf
|
|
|
|
"contact_deny" - List of Contact header addresses to deny
|
|
|
|
"contact_permit" - List of Contact header addresses to permit
|
|
|
|
|
2016-04-15 19:26:15 +00:00
|
|
|
* Added "reg_server" to contacts.
|
|
|
|
If the Asterisk system name is set in asterisk.conf, it will be stored
|
|
|
|
into the "reg_server" field in the ps_contacts table to facilitate
|
|
|
|
multi-server setups.
|
2015-09-05 19:58:41 +00:00
|
|
|
|
2016-06-02 17:51:31 +00:00
|
|
|
* When starting Asterisk, received traffic will now be ignored until Asterisk
|
|
|
|
has loaded all modules and is fully booted.
|
|
|
|
|
res_hep: Provide an option to pick the UUID type
At one point in time, it seemed like a good idea to use the Asterisk
channel name as the HEP correlation UUID. In particular, it felt like
this would be a useful identifier to tie PJSIP messages and RTCP
messages together, along with whatever other data we may eventually send
to Homer. This also had the benefit of keeping the correlation UUID
channel technology agnostic.
In practice, it isn't as useful as hoped, for two reasons:
1) The first INVITE request received doesn't have a channel. As a
result, there is always an 'odd message out', leading it to be
potentially uncorrelated in Homer.
2) Other systems sending capture packets (Kamailio) use the SIP Call-ID.
This causes RTCP information to be uncorrelated to the SIP message
traffic seen by those capture nodes.
In order to support both (in case someone is trying to use res_hep_rtcp
with a non-PJSIP channel), this patch adds a new option, uuid_type, with
two valid values - 'call-id' and 'channel'. The uuid_type option is used
by a module to determine the preferred UUID type. When available, that
source of a correlation UUID is used; when not, the more readily available
source is used.
For res_hep_pjsip:
- uuid_type = call-id: the module uses the SIP Call-ID header value
- uuid_type = channel: the module uses the channel name if available,
falling back to SIP Call-ID if not
For res_hep_rtcp:
- uuid_type = call-id: the module uses the SIP Call-ID header if the
channel type is PJSIP and we have a channel,
falling back to the Stasis event provided
channel name if not
- uuid_type = channel: the module uses the channel name
ASTERISK-25352 #close
Change-Id: Ide67e59a52d9c806e3cc0a797ea1a4b88a00122c
2016-05-12 01:17:15 +00:00
|
|
|
res_hep
|
|
|
|
------------------
|
|
|
|
* Added a new option, 'uuid_type', that sets the preferred source of the Homer
|
|
|
|
correlation UUID. The valid options are:
|
|
|
|
- call-id: Use the PJSIP SIP Call-ID header value
|
|
|
|
- channel: Use the Asterisk channel name
|
|
|
|
The default value is 'call-id'. In the event that a HEP module cannot find a
|
|
|
|
valid value using the specified 'uuid_type', the module may fallback to a
|
|
|
|
more readily available source for the correlation UUID.
|
|
|
|
|
2016-06-02 17:04:45 +00:00
|
|
|
res_odbc
|
|
|
|
------------------
|
|
|
|
* A new option has been added, 'max_connections', which sets the maximum number
|
|
|
|
of concurrent connections to the database. This option defaults to 1 which
|
|
|
|
returns the behavior to that of Asterisk 13.7 and prior.
|
|
|
|
|
2016-05-04 07:40:55 +00:00
|
|
|
app_confbridge
|
|
|
|
------------------
|
|
|
|
* Added a bridge profile option called regcontext that allows you to
|
|
|
|
dynamically register the conference bridge name as an extension into
|
|
|
|
the specified context. This allows tracking down conferences on multi-
|
|
|
|
server installations via alternate means (DUNDI for example). By default
|
|
|
|
this feature is not used.
|
|
|
|
|
2016-05-27 19:49:42 +00:00
|
|
|
Codecs
|
|
|
|
------------------
|
|
|
|
* Added the associated format name to 'core show codecs'.
|
|
|
|
|
|
|
|
res_ari_channels
|
|
|
|
------------------
|
|
|
|
* Added 'formats' to channel create/originate to allow setting the allowed
|
|
|
|
formats for a channel when no originator channel is available. Especially
|
|
|
|
useful for Local channel creation where no other format information is
|
|
|
|
available. 'core show codecs' can now be used to look up suitable format
|
|
|
|
names.
|
|
|
|
|
2016-03-26 04:19:22 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 13.8.0 to Asterisk 13.9.0 ------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
|
|
|
res_parking:
|
|
|
|
- The dynamic parking lot creation channel variables PARKINGDYNAMIC,
|
|
|
|
PARKINGDYNCONTEXT, PARKINGDYNEXTEN, and PARKINGDYNPOS are now looked
|
|
|
|
for in the parker's channel instead of the parked channel. This is only
|
|
|
|
of significance if the parker uses blind transfer or the DTMF one-step
|
|
|
|
parking feature. You need to use the double underscore '__' inheritance
|
|
|
|
for these variables. The indefinite inheritance is also recommended
|
|
|
|
for the PARKINGEXTEN variable.
|
|
|
|
|
2016-04-15 16:59:42 +00:00
|
|
|
res_pjsip
|
|
|
|
------------------
|
|
|
|
* Added new global option (disable_multi_domain) to pjsip.
|
|
|
|
Disabling Multi Domain can improve realtime performace by reducing
|
|
|
|
number of database requsts.
|
|
|
|
|
2016-03-27 03:33:14 +00:00
|
|
|
chan_pjsip
|
|
|
|
------------------
|
|
|
|
* Added 'pjsip show channelstats' CLI command.
|
2016-03-26 04:19:22 +00:00
|
|
|
|
2016-04-05 21:56:39 +00:00
|
|
|
res_pjsip_outbound_publish
|
|
|
|
------------------
|
|
|
|
* Added support for setting the transport used on outbound publish
|
|
|
|
using the transport configuration option.
|
|
|
|
|
2015-12-13 19:09:42 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 13.7.0 to Asterisk 13.8.0 ------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
2016-02-24 23:25:09 +00:00
|
|
|
res_pjsip_caller_id
|
|
|
|
------------------
|
|
|
|
* Per RFC3325, the 'From' header is now anonymized on outgoing calls when
|
|
|
|
caller id presentation is prohibited.
|
|
|
|
|
2016-02-16 03:31:38 +00:00
|
|
|
res_pjsip_config_wizard
|
|
|
|
------------------
|
|
|
|
* A new command (pjsip export config_wizard primitives) has been added that
|
|
|
|
will export all the pjsip objects it created to the console or a file
|
|
|
|
suitable for reuse in a pjsip.conf file.
|
|
|
|
|
build-system: Allow building with static pjproject
Background here:
http://lists.digium.com/pipermail/asterisk-dev/2016-January/075266.html
From CHANGES:
* To help insure that Asterisk is compiled and run with the same known
version of pjproject, a new option (--with-pjproject-bundled) has been
added to ./configure. When specified, the version of pjproject specified
in third-party/versions.mak will be downloaded and configured. When you
make Asterisk, the build process will also automatically build pjproject
and Asterisk will be statically linked to it. Once a particular version
of pjproject is configured and built, it won't be configured or built
again unless you run a 'make distclean'.
To facilitate testing, when 'make install' is run, the pjsua and pjsystest
utilities and the pjproject python bindings will be installed in
ASTDATADIR/third-party/pjproject.
The default behavior remains building with the shared pjproject
installation, if any.
Building:
All you have to do is include the --with-pjproject-bundled option on
the ./configure command line (and remove any existing --with-pjproject
option if specified). Everything else is automatic.
Behind the scenes:
The top-level Makefile was modified to include 'third-party' in the
list of MOD_SUBDIRS.
The third-party directory was created to contain any third party
packages that may be needed in the future. Its Makefile automatically
iterates over any subdirectories passing on targets.
The third-party/pjproject directory was created to house the pjproject
source distribution. Its Makefile contains targets to download, patch
configure, generate dependencies, compile libs, apps and python bindings,
sanitized build.mak and generate a symbols list.
When bootstrap.sh is run, it automatically includes the configure.m4
file in third-party/pjproject. This file has a macro to download and
conifgure pjproject and get and set PJPROJECT_INCLUDE, PJPROJECT_DIR
and PJPROJECT_BUNDLED. It also tests for the capabilities like
PJ_TRANSACTION_GRP_LOCK by parsing preprocessor output as opposed to
trying to compile. Of course, bootstrap.sh is only run once and the
configure file is incldued in the patch.
When configure is run with the new options, the macro in configure.m4
triggers the download, patch, conifgure and tests. No compilation is
performed at this time. The downloaded tarball is cached in /tmp so
it doesn't get downloaded again on a distclean.
When make is run in the top-level Asterisk source directory, it will
automatically descend all the subdirectories in third_party just as it
does for addons, apps, etc. The top-level Makefile makes sure that
the 'third-party' is built before 'main' so that dependencies from the
other directories are built first.
When main does build, a new shared library (libasteriskpj) is created that
links statically to the pjproject .a files and exports all their symbols.
The asterisk binary links to that, just as it does with libasteriskssl.
When Asterisk is installed, the pjsua and pjsystest apps, and the pjproject
python bindings are installed in ASTDATADIR/third-party/pjproject. This
will facilitate testing, including running the testsuite which will be
updated to check that directory for the pjsua module ahead of the system
python library.
Modules should continue to depend on pjproject if they use pjproject APIs
directly. They should not care about the implementation. No changes to any
res_pjsip modules were made.
Change-Id: Ia7a60c28c2e9ba9537c5570f933c1ebcb20a3103
2016-01-19 03:54:28 +00:00
|
|
|
Build System
|
|
|
|
------------------
|
|
|
|
* To help insure that Asterisk is compiled and run with the same known
|
|
|
|
version of pjproject, a new option (--with-pjproject-bundled) has been
|
|
|
|
added to ./configure. When specified, the version of pjproject specified
|
|
|
|
in third-party/versions.mak will be downloaded and configured. When you
|
|
|
|
make Asterisk, the build process will also automatically build pjproject
|
|
|
|
and Asterisk will be statically linked to it. Once a particular version
|
|
|
|
of pjproject is configured and built, it won't be configured or built
|
|
|
|
again unless you run a 'make distclean'.
|
|
|
|
|
|
|
|
To facilitate testing, when 'make install' is run, the pjsua and pjsystest
|
|
|
|
utilities and the pjproject python bindings will be installed in
|
|
|
|
ASTDATADIR/third-party/pjproject.
|
|
|
|
|
|
|
|
The default behavior remains building with the shared pjproject
|
|
|
|
installation, if any.
|
|
|
|
|
2016-01-25 22:05:09 +00:00
|
|
|
app_confbridge
|
|
|
|
------------------
|
|
|
|
* Added CONFBRIDGE_INFO(muted,) for querying the muted conference state.
|
|
|
|
|
|
|
|
* Added Muted header to AMI ConfbridgeListRooms action response list events
|
|
|
|
to indicate the muted conference state.
|
|
|
|
|
|
|
|
* Added Muted column to CLI "confbridge list" output to indicate the muted
|
|
|
|
conference state and made the locked column a yes/no value instead of a
|
|
|
|
locked/unlocked value.
|
|
|
|
|
2016-02-27 00:57:17 +00:00
|
|
|
REDIRECTING(reason)
|
|
|
|
------------------
|
|
|
|
* The REDIRECTING(reason) value is now treated consistently between
|
|
|
|
chan_sip and chan_pjsip.
|
|
|
|
|
|
|
|
Both channel drivers match incoming reason values with values documented
|
|
|
|
by REDIRECTING(reason) and values documented by RFC5806 regardless of
|
|
|
|
whether they are quoted or not. RFC5806 values are mapped to the
|
|
|
|
equivalent REDIRECTING(reason) documented value and is set in
|
|
|
|
REDIRECTING(reason). e.g., an incoming RFC5806 'unconditional' value or a
|
|
|
|
quoted string version ('"unconditional"') is converted to
|
|
|
|
REDIRECTING(reason)'s 'cfu' value. The user's dialplan only needs to deal
|
|
|
|
with 'cfu' instead of any of the aliases.
|
|
|
|
|
|
|
|
The incoming 480 response reason text supported by chan_sip checks for
|
|
|
|
known reason values and if not matched then puts quotes around the reason
|
|
|
|
string and assigns that to REDIRECTING(reason).
|
|
|
|
|
|
|
|
Both channel drivers send outgoing known REDIRECTING(reason) values as the
|
|
|
|
unquoted RFC5806 equivalent. User custom values are either sent as is or
|
|
|
|
with added quotes if SIP doesn't allow a character within the value as
|
|
|
|
part of a RFC3261 Section 25.1 token. Note that there are still
|
|
|
|
limitations on what characters can be put in a custom user value. e.g.,
|
|
|
|
embedding quotes in the middle of the reason string is just going to cause
|
|
|
|
you grief.
|
|
|
|
|
|
|
|
* Setting a REDIRECTING(reason) value now recognizes RFC5806 aliases.
|
|
|
|
e.g., Setting REDIRECTING(reason) to 'unconditional' is converted to the
|
|
|
|
'cfu' value.
|
|
|
|
|
2016-01-19 01:27:57 +00:00
|
|
|
res_pjproject
|
|
|
|
------------------
|
|
|
|
* This module is the successor of res_pjsip_log_forwarder. As well as
|
|
|
|
handling the log forwarding (which now displays as 'pjproject:0' instead
|
|
|
|
of 'pjsip:0'), it also adds a 'pjproject show buildopts' command to the CLI.
|
|
|
|
This displays the compiled-in options of the pjproject installation
|
|
|
|
Asterisk is currently running against.
|
|
|
|
|
2016-02-07 23:34:20 +00:00
|
|
|
* Another feature of this module is the ability to map pjproject log levels
|
|
|
|
to Asterisk log levels, or to suppress the pjproject log messages
|
|
|
|
altogether. Many of the messages emitted by pjproject itself are the result
|
|
|
|
of errors which Asterisk will ultimately handle so the messages can be
|
|
|
|
misleading or just noise. A new config file (pjproject.conf) has been added
|
|
|
|
to configure the mapping and a new CLI command (pjproject show log mappings)
|
|
|
|
has been added to display the mappings currently in use.
|
|
|
|
|
2016-01-10 22:22:12 +00:00
|
|
|
res_pjsip
|
|
|
|
------------------
|
2016-02-11 17:01:05 +00:00
|
|
|
* Transports are now reloadable. In testing, no in-progress calls were
|
|
|
|
disrupted if the ip address or port weren't changed, but the possibility
|
|
|
|
still exists. To make sure there are no unintentional drops, a new option
|
|
|
|
'allow_reload', which defaults to 'no' has been added to transport. If
|
|
|
|
left at the default, changes to the particular transport will be ignored.
|
|
|
|
If set to 'yes', changes (if any) will be applied.
|
|
|
|
|
2016-01-10 22:22:12 +00:00
|
|
|
* Added new global option (regcontext) to pjsip. When set, Asterisk will
|
|
|
|
dynamically create and destroy a NoOp priority 1 extension
|
|
|
|
for a given endpoint who registers or unregisters with us.
|
|
|
|
|
res_pjsip: Add ability to identify by Authorization username
A feature of chan_sip that service providers relied upon was the ability to
identify by the Authorization username. This is most often used when customers
have a PBX that needs to register rather than identify by IP address. From my
own experiance, this is pretty common with small businesses who otherwise
don't need a static IP.
In this scenario, a register from the customer's PBX may succeed because From
will usually contain the PBXs account id but an INVITE will contain the caller
id. With nothing recognizable in From, the service provider's Asterisk can
never match to an endpoint and the INVITE just stays unauthorized.
The fixes:
A new value "auth_username" has been added to endpoint/identify_by that
will use the username and digest fields in the Authorization header
instead of username and domain in the the From header to match an endpoint,
or the To header to match an aor. This code as added to
res_pjsip_endpoint_identifier_user rather than creating a new module.
Although identify_by was always a comma-separated list, there was only
1 choice so order wasn't preserved. So to keep the order, a vector was added
to the end of ast_sip_endpoint. This is only used by res_pjsip_registrar
to find the aor. The res_pjsip_endpoint_identifier_* modules are called in
globals/endpoint_identifier_order.
Along the way, the logic in res_pjsip_registrar was corrected to match
most-specific to least-specific as res_pjsip_endpoint_identifier_user does.
The order is:
username@domain
username@domain_alias
username
Auth by username does present 1 problem however, the first INVITE won't have
an Authorization header so the distributor, not finding a match on anything,
sends a securty_alert. It still sends a 401 with a challenge so the next
INVITE will have the Authorization header and presumably succeed. As a result
though, that first security alert is actually a false alarm.
To address this, a new feature has been added to pjsip_distributor that keeps
track of unidentified requests and only sends the security alert if a
configurable number of unidentified requests come from the same IP in a
configurable amout of time. Those configuration options have been added to
the global config object. This feature is only used when auth_username
is enabled.
Finally, default_realm was added to the globals object to replace the hard
coded "asterisk" used when an endpoint is not yet identified.
The testsuite tests all pass but new tests are forthcoming for this new
feature.
ASTERISK-25835 #close
Reported-by: Ross Beer
Change-Id: I30ba62d208e6f63439600916fcd1c08a365ed69d
2016-03-08 00:34:31 +00:00
|
|
|
* Endpoints and aors can now be identified by the username and realm in an
|
|
|
|
incoming Authorization header. To use this feature, add "auth_username"
|
|
|
|
to your endpoint's "identify_by" list. You can combine "auth_username"
|
|
|
|
and the original "username" to test both the From/To and Authorization
|
|
|
|
headers. For endpoints, the order is controlled by the global
|
|
|
|
"endpoint_identifier_order" setting. For matching aors to an endpoint
|
|
|
|
for inbound registration, the order is controlled by this option.
|
|
|
|
|
|
|
|
* In conjunction with the "auth_username" change, 3 new options have been
|
|
|
|
added to the global configuration object that control how many unidentified
|
|
|
|
requests over a certain period from the same IP address can be received
|
|
|
|
before a security altert is generated. A new CLI command
|
|
|
|
"pjsip show unidentified_requests" will list the current candidates.
|
|
|
|
|
2015-12-13 19:09:42 +00:00
|
|
|
res_pjsip_history
|
|
|
|
------------------
|
|
|
|
* A new module, res_pjsip_history, has been added that provides SIP history
|
|
|
|
viewing/filtering from the CLI. The module is intended to be used on systems
|
|
|
|
with busy SIP traffic, where existing forms of viewing SIP messages - such
|
|
|
|
as the res_pjsip_logger - may be inadequate. The module provides two new
|
|
|
|
CLI commands:
|
|
|
|
- 'pjsip set history {on|off|clear}' - this enables/disables SIP history
|
|
|
|
capturing, as well as clears an existing history capture. Note that SIP
|
|
|
|
packets captured are stored in memory until cleared. As a result, the
|
|
|
|
history capture should only be used for debugging/viewing purposes, and
|
|
|
|
should *NOT* be left permanently enabled on a system.
|
|
|
|
- 'pjsip show history' - displays the captured SIP history. When invoked
|
|
|
|
with no options, the entire captured history is displayed. Two options
|
|
|
|
are available:
|
|
|
|
-- 'entry <num>' - display a detailed view of a single SIP message in
|
|
|
|
the history
|
|
|
|
-- 'where ...' - filter the history based on some expression. For more
|
|
|
|
information on filtering, view the current CLI help for the
|
|
|
|
'pjsip show history' command.
|
|
|
|
|
2015-12-30 16:49:03 +00:00
|
|
|
Voicemail
|
|
|
|
------------------
|
|
|
|
* app_voicemail and res_mwi_external can now be built together. The default
|
|
|
|
remains to build app_voicemail and not res_mwi_external but if they are
|
|
|
|
both built, the load order will cause res_mwi_external to load first and
|
|
|
|
app_voicemail will be skipped. Use 'preload=app_voicemail.so' in
|
|
|
|
modules.conf to force app_voicemail to be the voicemail provider.
|
|
|
|
|
2016-01-07 17:57:01 +00:00
|
|
|
res_pjsip_sdp_rtp
|
|
|
|
------------------
|
|
|
|
* A new option (bind_rtp_to_media_address) has been added to endpoint which
|
|
|
|
will cause res_pjsip_sdp_rtp to actually bind the RTP instance to the
|
|
|
|
media_address as well as using it in the SDP. If set, RTP packets will now
|
|
|
|
originate from the media address instead of the operating system's "primary"
|
|
|
|
ip address.
|
|
|
|
|
2016-01-27 16:44:10 +00:00
|
|
|
res_rtp_asterisk
|
|
|
|
------------------
|
|
|
|
* A new configuration section - ice_host_candidates - has been added to
|
|
|
|
rtp.conf, allowing automatically discovered ICE host candidates to be
|
|
|
|
overriden. This allows an Asterisk server behind a 1:1 NAT to send its
|
|
|
|
external IP as a host candidate rather than relying on STUN to discover it.
|
|
|
|
|
2015-10-20 17:06:52 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 13.6.0 to Asterisk 13.7.0 ------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
2015-11-21 12:08:49 +00:00
|
|
|
Codecs
|
|
|
|
------------------
|
|
|
|
* Added format attribute negotiation for the VP8 video codec. Format attribute
|
|
|
|
negotiation is provided by the res_format_attr_vp8 module.
|
|
|
|
|
2015-11-13 20:03:35 +00:00
|
|
|
ConfBridge
|
|
|
|
------------------
|
|
|
|
* A new "timeout" user profile option has been added. This configures the number
|
|
|
|
of seconds that a participant may stay in the ConfBridge after joining. When
|
|
|
|
the time expires, the user is ejected from the conference and CONFBRIDGE_RESULT
|
|
|
|
is set to "TIMEOUT" on the channel.
|
|
|
|
|
2015-11-03 02:24:58 +00:00
|
|
|
chan_sip
|
|
|
|
------------------
|
|
|
|
* The websockets_enabled option has been added to the general section of
|
|
|
|
sip.conf. The option is enabled by default to match the previous behavior.
|
|
|
|
The option should be disabled when using res_pjsip_transport_websockets to
|
|
|
|
ensure chan_sip will not conflict with PJSIP websockets.
|
|
|
|
|
2015-10-20 17:06:52 +00:00
|
|
|
Dialplan Functions
|
|
|
|
------------------
|
|
|
|
* The HOLD_INTERCEPT dialplan function now actually exists in the source tree.
|
|
|
|
While support for the events was added in Asterisk 13.4.0, the function
|
|
|
|
accidentally never made it in. That function is now present, and will cause
|
|
|
|
the 'hold' raised by a channel to be intercepted and converted into an
|
|
|
|
event instead.
|
|
|
|
|
2015-11-13 16:34:03 +00:00
|
|
|
res_pjsip_outbound_registration
|
|
|
|
-------------------------------
|
|
|
|
* If res_statsd is loaded and a StatsD server is configured, basic statistics
|
|
|
|
regarding the state of outbound registrations will now be emitted. This
|
|
|
|
includes:
|
2015-11-24 19:54:54 +00:00
|
|
|
- A GAUGE statistic for the overall number of outbound registrations, i.e.:
|
2015-11-13 16:34:03 +00:00
|
|
|
PJSIP.registrations.count
|
2015-11-24 19:54:54 +00:00
|
|
|
- A GAUGE statistic for the overall number of outbound registrations in a
|
2015-11-13 16:34:03 +00:00
|
|
|
particular state, e.g.:
|
|
|
|
PJSIP.registrations.state.Registered
|
2015-10-20 17:06:52 +00:00
|
|
|
|
2015-10-20 21:02:30 +00:00
|
|
|
res_pjsip
|
|
|
|
------------------
|
|
|
|
* The ability to use "like" has been added to the pjsip list and show
|
|
|
|
CLI commands. For instance: CLI> pjsip list endpoints like abc
|
|
|
|
|
2015-11-18 16:07:09 +00:00
|
|
|
* If res_statsd is loaded and a StatsD server is configured, basic statistics
|
2015-11-27 13:39:22 +00:00
|
|
|
regarding the state of PJSIP contacts will now be emitted. This includes:
|
2015-11-24 19:54:54 +00:00
|
|
|
- A GAUGE statistic for the overall number of contacts in a particular
|
2015-11-18 16:07:09 +00:00
|
|
|
state, e.g.:
|
|
|
|
PJSIP.contacts.states.Reachable
|
|
|
|
- A TIMER statistic for the RTT time for each qualified contact, e.g.:
|
|
|
|
PJSIP.contacts.alice@@127.0.0.1:5061.rtt
|
|
|
|
|
2015-12-05 16:01:55 +00:00
|
|
|
res_sorcery_memory_cache
|
|
|
|
------------------------
|
|
|
|
* A new caching strategy, full_backend_cache, has been added which caches
|
|
|
|
all stored objects in the backend. When enabled all objects will be
|
|
|
|
expired or go stale according to the configuration. As well when enabled
|
|
|
|
all retrieval operations will be performed against the cache instead of
|
|
|
|
the backend.
|
|
|
|
|
2015-11-06 13:54:59 +00:00
|
|
|
func_callerid
|
|
|
|
-------------------
|
|
|
|
* CALLERID(pres) is now documented as a valid alternative to setting both
|
|
|
|
CALLERID(name-pres) and CALLERID(num-pres) at once. Some channel drivers,
|
|
|
|
like chan_sip, don't make a distinction between the two: they take the
|
|
|
|
least public value from name-pres and num-pres. By using CALLERID(pres)
|
|
|
|
for reading and writing, you touch the same combined value in the dialplan.
|
|
|
|
The same applies to CONNECTEDLINE(pres), REDIRECTING(orig-pres),
|
|
|
|
REDIRECTING(to-pres) and REDIRECTING(from-pres).
|
|
|
|
|
2015-11-18 15:43:08 +00:00
|
|
|
res_endpoint_stats
|
|
|
|
-------------------
|
|
|
|
* A new module that emits StatsD statistics regarding Asterisk endpoints.
|
|
|
|
This includes a total count of the number of endpoints, the count of the
|
2015-11-24 19:54:54 +00:00
|
|
|
number of endpoints in the technology agnostic state of the endpoint -
|
2015-11-18 15:43:08 +00:00
|
|
|
online or offline - as well as the number of channels associated with each
|
2015-11-24 19:54:54 +00:00
|
|
|
endpoint. These are recorded as three different GAUGE statistics:
|
2015-11-18 15:43:08 +00:00
|
|
|
- endpoints.count
|
|
|
|
- endpoints.state.{unknown|offline|online}
|
|
|
|
- endpoints.{tech}.{resource}.channels
|
|
|
|
|
|
|
|
|
2015-09-05 19:58:41 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 13.5.0 to Asterisk 13.6.0 ------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
|
|
|
Dialplan Functions
|
|
|
|
------------------
|
|
|
|
* The CHANNEL function, when used on a PJSIP channel, now exposes a 'call-id'
|
|
|
|
extraction option when using with the 'pjsip' signalling option. It will
|
|
|
|
return the SIP Call-ID associated with the INVITE request that established
|
|
|
|
the PJSIP channel.
|
|
|
|
|
2015-09-04 02:19:21 +00:00
|
|
|
ARI
|
|
|
|
------------------
|
|
|
|
* Two new endpoint related events are now available: PeerStatusChange and
|
|
|
|
ContactStatusChange. In particular, these events are useful when subscribing
|
|
|
|
to all event sources, as they provide additional endpoint related
|
|
|
|
information beyond the addition/removal of channels from an endpoint.
|
|
|
|
|
|
|
|
* Added the ability to subscribe to all ARI events in Asterisk, regardless
|
|
|
|
of whether the application 'controls' the resource. This is useful for
|
|
|
|
scenarios where an ARI application merely wants to observe the system,
|
|
|
|
as opposed to control it. There are two ways to accomplish this:
|
|
|
|
(1) Via the WebSocket connection URI. A new query paramter, 'subscribeAll',
|
|
|
|
has been added that, when present and True, will subscribe all
|
|
|
|
specified applications to all ARI event sources in Asterisk.
|
|
|
|
(2) Via the applications resource. An ARI client can, at any time, subscribe
|
|
|
|
to all resources in an event source merely by not providing an explicit
|
|
|
|
resource. For example, subscribing to an event source of 'channels:'
|
|
|
|
as opposed to 'channels:12345' will subscribe the application to all
|
|
|
|
channels.
|
|
|
|
|
2015-05-21 22:21:01 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 13.4.0 to Asterisk 13.5.0 ------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
|
|
|
AMI
|
|
|
|
------------------
|
|
|
|
* A new ContactStatus event has been added that reflects res_pjsip contact
|
|
|
|
lifecycle changes: Created, Removed, Reachable, Unreachable, Unknown.
|
2015-04-21 22:27:16 +00:00
|
|
|
|
2015-06-23 19:34:29 +00:00
|
|
|
* Added the Linkedid header to the common channel headers listed for each
|
|
|
|
channel in AMI events.
|
|
|
|
|
2015-06-26 15:57:15 +00:00
|
|
|
ARI
|
|
|
|
------------------
|
|
|
|
* A new feature has been added that enables the retrieval of modules and
|
2015-07-13 15:54:51 +00:00
|
|
|
module information through an HTTP request. Information on a single module
|
2015-07-14 13:55:14 +00:00
|
|
|
can be also be retrieved. Individual modules can be loaded to Asterisk, as
|
2015-07-14 18:12:32 +00:00
|
|
|
well as unloaded and reloaded.
|
2015-06-26 15:57:15 +00:00
|
|
|
|
2015-07-08 21:39:35 +00:00
|
|
|
* A new resource has been added to the 'asterisk' resource, 'config/dynamic'.
|
|
|
|
This resource allows for push configuration of sorcery derived objects
|
|
|
|
within Asterisk. The resource supports creation, retrieval, updating, and
|
|
|
|
deletion. Sorcery derived objects that are manipulated by this resource
|
|
|
|
must have a sorcery wizard that supports the desired operations.
|
|
|
|
|
2015-07-29 19:17:09 +00:00
|
|
|
* A new feature has been added that allows for the rotation of log channels
|
|
|
|
through HTTP requests.
|
|
|
|
|
2015-07-08 21:39:35 +00:00
|
|
|
|
2015-06-12 21:58:27 +00:00
|
|
|
res_pjsip
|
|
|
|
------------------
|
|
|
|
* A new 'g726_non_standard' endpoint option has been added that, when set to
|
|
|
|
'yes' and g.726 audio is negotiated, forces the codec to be treated as if it
|
|
|
|
is AAL2 packed on the channel.
|
|
|
|
|
2015-07-09 19:17:53 +00:00
|
|
|
* A new 'rtp_keepalive' endpoint option has been added. This option specifies
|
|
|
|
an interval, in seconds, at which we will send RTP comfort noise packets to
|
|
|
|
the endpoint. This functions identically to chan_sip's "rtpkeepalive" option.
|
|
|
|
|
2015-07-18 16:16:10 +00:00
|
|
|
* New 'rtp_timeout' and 'rtp_timeout_hold' endpoint options have been added.
|
|
|
|
These options specify the amount of time, in seconds, that Asterisk will wait
|
|
|
|
before terminating the call due to lack of received RTP. These are identical
|
|
|
|
to chan_sip's rtptimeout and rtpholdtimeout options.
|
|
|
|
|
2015-03-24 19:41:36 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 13.3.0 to Asterisk 13.4.0 ------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
|
|
|
chan_pjsip
|
|
|
|
------------------
|
|
|
|
* New 'rpid_immediate' option to control if connected line update information
|
|
|
|
goes to the caller immediately or waits for another reason to send the
|
|
|
|
connected line information update. See the online option documentation for
|
|
|
|
more information. Defaults to 'no' as setting it to 'yes' can result in
|
|
|
|
many unnecessary messages being sent to the caller.
|
|
|
|
|
2015-04-10 21:06:23 +00:00
|
|
|
* The configuration setting 'progressinband' now defaults to 'no', which
|
|
|
|
matches the actual behavior of previous versions.
|
|
|
|
|
2015-04-09 22:07:50 +00:00
|
|
|
res_pjsip
|
|
|
|
------------------
|
|
|
|
* A new CLI command has been added: "pjsip show settings", which shows
|
|
|
|
both the global and system configuration settings.
|
|
|
|
|
2015-04-11 21:56:52 +00:00
|
|
|
* A new aor option has been added: "qualify_timeout", which sets the timeout
|
|
|
|
in seconds for a qualify. The default is 3 seconds. This overrides the
|
|
|
|
hard coded 32 seconds in pjproject.
|
|
|
|
|
|
|
|
* Endpoint status will now change to "Unreachable" when all contacts are
|
|
|
|
unavailable. When any contact becomes available, the endpoint will status
|
|
|
|
will change back to "Reachable".
|
|
|
|
|
2015-04-11 22:04:32 +00:00
|
|
|
* A new global option has been added: "max_initial_qualify_time", which
|
|
|
|
sets the maximum amount of time from startup that qualifies should be
|
|
|
|
attempted on all contacts.
|
|
|
|
|
2015-04-07 15:22:42 +00:00
|
|
|
res_ari_channels
|
|
|
|
------------------
|
|
|
|
* Two new events, 'ChannelHold' and 'ChannelUnhold', have been added to the
|
|
|
|
events data model. These events are raised when a channel indicates a hold
|
|
|
|
or unhold, respectively.
|
|
|
|
|
|
|
|
func_holdintercept
|
|
|
|
------------------
|
|
|
|
* A new dialplan function, HOLD_INTERCEPT, has been added. This function, when
|
|
|
|
placed on a channel, intercepts hold/unhold indications signalled by the
|
|
|
|
channel and prevents them from moving on to other channels in a bridge with
|
|
|
|
the hold initiator. Instead, AMI or ARI events are raised indicating that
|
|
|
|
the channel wanted to place someone on hold. This allows external
|
|
|
|
applications to implement their own custom hold/unhold logic.
|
|
|
|
|
ARI/PJSIP: Add the ability to redirect (transfer) a channel in a Stasis app
This patch adds a new feature to ARI to redirect a channel to another server,
and fixes a few bugs in PJSIP's handling of the Transfer dialplan
application/ARI redirect capability.
*New Feature*
A new operation has been added to the ARI channels resource, redirect. With
this, a channel in a Stasis application can be redirected to another endpoint
of the same underlying channel technology.
*Bug fixes*
In the process of writing this new feature, two bugs were fixed in the PJSIP
stack:
(1) The existing .transfer channel callback had the limitation that it could
only transfer channels to a SIP URI, i.e., you had to pass
'PJSIP/sip:foo@my_provider.com' to the dialplan application. While this is
still supported, it is somewhat unintuitive - particularly in a world full
of endpoints. As such, we now also support specifying the PJSIP endpoint to
transfer to.
(2) res_pjsip_multihomed was, unfortunately, trying to 'help' a 302 redirect by
updating its Contact header. Alas, that resulted in the forwarding
destination set by the dialplan application/ARI resource/whatever being
rewritten with very incorrect information. Hence, we now don't bother
updating an outgoing response if it is a 302. Since this took a looong time
to find, some additional debug statements have been added to those modules
that update the Contact headers.
Review: https://reviewboard.asterisk.org/r/4316/
ASTERISK-24015 #close
Reported by: Private Name
ASTERISK-24703 #close
Reported by: Matt Jordan
........
Merged revisions 431717 from http://svn.asterisk.org/svn/asterisk/branches/13
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@431718 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2015-02-12 20:34:37 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 13.2.0 to Asterisk 13.3.0 ------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
|
|
|
chan_pjsip/app_transfer
|
|
|
|
------------------
|
|
|
|
* The Transfer application, when used with chan_pjsip, now supports using
|
|
|
|
a PJSIP endpoint as the transfer destination. This is in addition to
|
|
|
|
explicitly specifying a SIP URI to transfer to.
|
|
|
|
|
|
|
|
res_ari_channels
|
|
|
|
------------------
|
|
|
|
* The ARI /channels resource now supports a new operation, 'redirect'. The
|
|
|
|
redirect operation will perform a technology and state specific redirection
|
|
|
|
on the channel to a specified endpoint or destination. In the case of SIP
|
|
|
|
technologies, this is either a 302 Redirect response to an on-going INVITE
|
|
|
|
dialog or a SIP REFER request.
|
|
|
|
|
2015-03-17 18:22:20 +00:00
|
|
|
res_pjsip
|
|
|
|
------------------
|
|
|
|
* A new 'endpoint_identifier_order' option has been added that allows one to
|
|
|
|
set the order by which endpoint identifiers are processed and checked. This
|
|
|
|
option is specified under the 'global' type configuration section.
|
|
|
|
|
2014-12-09 15:45:19 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 13.1.0 to Asterisk 13.2.0 ------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
2015-01-05 17:57:43 +00:00
|
|
|
* New 'PJSIP_AOR' and 'PJSIP_CONTACT' dialplan functions have been added which
|
|
|
|
allow examining PJSIP AORs or contacts from the dialplan.
|
|
|
|
|
2015-01-06 17:43:16 +00:00
|
|
|
res_pjsip_outbound_registration
|
|
|
|
------------------
|
|
|
|
* The 'pjsip send unregister' command now stops further registrations.
|
|
|
|
|
|
|
|
* A new command 'pjsip send register' has been added which allows you to
|
|
|
|
start or restart periodic registration. It can be used after a
|
|
|
|
'send unregister' or after a 401 permanent error.
|
|
|
|
|
2014-12-15 17:08:24 +00:00
|
|
|
res_pjsip_config_wizard
|
|
|
|
------------------
|
|
|
|
* This is a new module that adds streamlined configuration capability for
|
2015-01-06 17:43:16 +00:00
|
|
|
chan_pjsip. It's targeted at users who have lots of basic configuration
|
2014-12-15 17:08:24 +00:00
|
|
|
scenarios like 'phone' or 'agent' or 'trunk'. Additional information
|
|
|
|
can be found in the sample configuration file at
|
|
|
|
config/samples/pjsip_wizard.conf.sample.
|
|
|
|
|
2015-01-09 14:53:09 +00:00
|
|
|
res_fax
|
|
|
|
-----------
|
|
|
|
* The T.38 negotiation timeout was previously hard coded at 5000 milliseconds
|
|
|
|
and is now configurable via the 't38timeout' configuration option in
|
|
|
|
res_fax.conf and via the fax options dialplan function 'FAXOPT(t38timeout)'.
|
|
|
|
The default remains at 5000 milliseconds.
|
|
|
|
|
2015-01-16 21:46:09 +00:00
|
|
|
PJSIP Transports
|
|
|
|
----------
|
|
|
|
* The ca_list_path transport parameter has been added for TLS transports. This
|
|
|
|
option behaves similarly to the old sip.conf option "tlscapath". In order to
|
2015-01-16 22:14:38 +00:00
|
|
|
use this, you must be using PJProject version 2.4 or higher.
|
2015-01-16 21:46:09 +00:00
|
|
|
|
2014-12-09 15:45:19 +00:00
|
|
|
ARI
|
|
|
|
------------------
|
|
|
|
* The Originate operation now takes in an originator channel. The linked ID of
|
|
|
|
this originator channel is applied to the newly originated outgoing channel.
|
|
|
|
If using CEL this allows an association to be established between the two so
|
|
|
|
it can be recognized that the originator is dialing the originated channel.
|
|
|
|
|
2014-12-11 20:32:21 +00:00
|
|
|
* "language" (the default spoken language for the channel) is now included in
|
|
|
|
the standard channel state output for suitable events.
|
|
|
|
|
2015-01-07 18:54:06 +00:00
|
|
|
* The POST channels/{id} operation and the POST channels/{id}/continue operation
|
|
|
|
now have a new "label" parameter. This allows for origination or continuation
|
|
|
|
to a labeled priority in the dialplan instead of requiring a specific priority
|
|
|
|
number. The ARI version has been bumped to 1.7.0 as a result.
|
|
|
|
|
2014-12-11 20:32:21 +00:00
|
|
|
AMI
|
|
|
|
------------------
|
|
|
|
* "Language" (the default spoken language for the channel) is now included in
|
|
|
|
the standard channel state output for suitable events.
|
|
|
|
|
2015-01-09 18:16:54 +00:00
|
|
|
* AMI actions that return a list of events have been made to return consistent
|
|
|
|
headers for the action response event starting the list and the list complete
|
|
|
|
event. The AMI version has been bumped to 2.7.0 as a result.
|
|
|
|
|
2014-11-17 16:58:52 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 13.0.0 to Asterisk 13.1.0 ------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
2014-12-08 16:54:43 +00:00
|
|
|
AMI
|
|
|
|
------------------
|
|
|
|
* Event NewConnectedLine is emitted when the connected line information on
|
|
|
|
a channel changes.
|
|
|
|
|
|
|
|
ARI
|
|
|
|
------------------
|
|
|
|
* Event ChannelConnectedLine is emitted when the connected line information
|
|
|
|
on a channel changes.
|
|
|
|
|
|
|
|
Core Transfers
|
2014-11-17 16:58:52 +00:00
|
|
|
-----------------
|
|
|
|
|
|
|
|
The features.conf general section has three new configurable options:
|
|
|
|
* transferdialattempts
|
2015-04-21 22:45:43 +00:00
|
|
|
* transferretrysound
|
|
|
|
* transferinvalidsound
|
2014-11-17 16:58:52 +00:00
|
|
|
For more information on what these options do, see the Asterisk wiki:
|
2015-04-21 22:45:43 +00:00
|
|
|
https://wiki.asterisk.org/wiki/x/W4fAAQ
|
2014-11-17 16:58:52 +00:00
|
|
|
|
2014-11-19 12:50:47 +00:00
|
|
|
Channel Drivers
|
|
|
|
------------------
|
|
|
|
|
|
|
|
chan_pjsip
|
|
|
|
------------------
|
|
|
|
* New 'media_encryption_optimistic' endpoint setting. This will use SRTP
|
|
|
|
when possible but does not consider lack of it a failure.
|
2014-09-14 15:41:58 +00:00
|
|
|
|
2014-12-02 21:54:05 +00:00
|
|
|
res_pjsip_endpoint_identifer_ip
|
|
|
|
------------------
|
|
|
|
* New CLI commands have been added: "pjsip show identif(y|ies)", which lists
|
|
|
|
all configured PJSIP identify objects
|
|
|
|
|
2013-11-01 22:48:14 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 12 to Asterisk 13 --------------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
Overview
|
accountcode: Slightly change accountcode propagation.
The previous behavior was to simply set the accountcode of an outgoing
channel to the accountcode of the channel initiating the call. It was
done this way a long time ago to allow the accountcode set on the SIP/100
channel to be propagated to a local channel so the dialplan execution on
the Local;2 channel would have the SIP/100 accountcode available.
SIP/100 -> Local;1/Local;2 -> SIP/200
Propagating the SIP/100 accountcode to the local channels is very useful.
Without any dialplan manipulation, all channels in this call would have
the same accountcode.
Using dialplan, you can set a different accountcode on the SIP/200 channel
either by setting the accountcode on the Local;2 channel or by the Dial
application's b(pre-dial), M(macro) or U(gosub) options, or by the
FollowMe application's b(pre-dial) option, or by the Queue application's
macro or gosub options. Before Asterisk v12, the altered accountcode on
SIP/200 will remain until the local channels optimize out and the
accountcode would change to the SIP/100 accountcode.
Asterisk v1.8 attempted to add peeraccount support but ultimately had to
punt on the support. The peeraccount support was rendered useless because
of how the CDR code needed to unconditionally force the caller's
accountcode onto the peer channel's accountcode. The CEL events were thus
intentionally made to always use the channel's accountcode as the
peeraccount value.
With the arrival of Asterisk v12, the situation has improved somewhat so
peeraccount support can be made to work. Using the indicated example, the
the accountcode values become as follows when the peeraccount is set on
SIP/100 before calling SIP/200:
SIP/100 ---> Local;1 ---- Local;2 ---> SIP/200
acct: 100 \/ acct: 200 \/ acct: 100 \/ acct: 200
peer: 200 /\ peer: 100 /\ peer: 200 /\ peer: 100
If a channel already has an accountcode it can only change by the
following explicit user actions:
1) A channel originate method that can specify an accountcode to use.
2) The calling channel propagating its non-empty peeraccount or its
non-empty accountcode if the peeraccount was empty to the outgoing
channel's accountcode before initiating the dial. e.g., Dial and
FollowMe. The exception to this propagation method is Queue. Queue will
only propagate peeraccounts this way only if the outgoing channel does not
have an accountcode.
3) Dialplan using CHANNEL(accountcode).
4) Dialplan using CHANNEL(peeraccount) on the other end of a local
channel pair.
If a channel does not have an accountcode it can get one from the
following places:
1) The channel driver's configuration at channel creation.
2) Explicit user action as already indicated.
3) Entering a basic or stasis-mixing bridge from a peer channel's
peeraccount value.
You can specify the accountcode for an outgoing channel by setting the
CHANNEL(peeraccount) before using the Dial, FollowMe, and Queue
applications. Queue adds the wrinkle that it will not overwrite an
existing accountcode on the outgoing channel with the calling channels
values.
Accountcode and peeraccount values propagate to an outgoing channel before
dialing. Accountcodes also propagate when channels enter or leave a basic
or stasis-mixing bridge. The peeraccount value only makes sense for
mixing bridges with two channels; it is meaningless otherwise.
* Made peeraccount functional by changing accountcode propagation as
described above.
* Fixed CEL extracting the wrong ie value for the peeraccount. This was
done intentionally in Asterisk v1.8 when that version had to punt on
peeraccount.
* Fixed a few places dealing with accountcodes that were reading from
channels without the lock held.
AFS-65 #close
Review: https://reviewboard.asterisk.org/r/3601/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@419520 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2014-07-24 22:48:38 +00:00
|
|
|
------------------
|
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
Asterisk 13 is the next Long Term Support (LTS) release of Asterisk. As such,
|
|
|
|
the focus of development for this release of Asterisk was on improving the
|
|
|
|
usability and features developed in the previous Standard release, Asterisk 12.
|
|
|
|
Beyond a general refinement of end user features, development focussed heavily
|
|
|
|
on the Asterisk APIs - the Asterisk Manager Interface (AMI) and the Asterisk
|
|
|
|
REST Interface (ARI) - and the PJSIP stack in Asterisk. Some highlights of the
|
|
|
|
new features include:
|
|
|
|
|
|
|
|
* Asterisk security events are now provided via AMI, allowing end users to
|
|
|
|
monitor their Asterisk system in real time for security related issues.
|
|
|
|
* External control of Message Waiting Indicators (MWI) through both AMI and ARI.
|
|
|
|
* Reception/transmission of out of call text messages using any supported
|
|
|
|
channel driver/protocol stack through ARI.
|
|
|
|
* Resource List Server support in the PJSIP stack, providing subscriptions to
|
|
|
|
lists of resources and batched delivery of NOTIFY requests.
|
|
|
|
* Inter-Asterisk distributed device state and mailbox state using the PJSIP
|
|
|
|
stack.
|
|
|
|
|
|
|
|
It is important to note that Asterisk 13 is built on the architecture developed
|
|
|
|
during the previous Standard release, Asterisk 12. Users upgrading to
|
|
|
|
Asterisk 13 should read about the new features in Asterisk 12 later in this file
|
|
|
|
(see Functionality changes from Asterisk 11 to Asterisk 12), as well as the
|
|
|
|
UPGRADE-12.txt delivered with this release. In particular, users upgrading to
|
|
|
|
Asterisk 13 from a release prior to Asterisk 12 should read the specifications
|
|
|
|
on AMI, CDRs, and CEL on the Asterisk wiki:
|
|
|
|
* AMI - https://wiki.asterisk.org/wiki/x/dAFRAQ
|
|
|
|
* CEL - https://wiki.asterisk.org/wiki/x/4ICLAQ
|
|
|
|
* CDRs - https://wiki.asterisk.org/wiki/x/pwpRAQ
|
accountcode: Slightly change accountcode propagation.
The previous behavior was to simply set the accountcode of an outgoing
channel to the accountcode of the channel initiating the call. It was
done this way a long time ago to allow the accountcode set on the SIP/100
channel to be propagated to a local channel so the dialplan execution on
the Local;2 channel would have the SIP/100 accountcode available.
SIP/100 -> Local;1/Local;2 -> SIP/200
Propagating the SIP/100 accountcode to the local channels is very useful.
Without any dialplan manipulation, all channels in this call would have
the same accountcode.
Using dialplan, you can set a different accountcode on the SIP/200 channel
either by setting the accountcode on the Local;2 channel or by the Dial
application's b(pre-dial), M(macro) or U(gosub) options, or by the
FollowMe application's b(pre-dial) option, or by the Queue application's
macro or gosub options. Before Asterisk v12, the altered accountcode on
SIP/200 will remain until the local channels optimize out and the
accountcode would change to the SIP/100 accountcode.
Asterisk v1.8 attempted to add peeraccount support but ultimately had to
punt on the support. The peeraccount support was rendered useless because
of how the CDR code needed to unconditionally force the caller's
accountcode onto the peer channel's accountcode. The CEL events were thus
intentionally made to always use the channel's accountcode as the
peeraccount value.
With the arrival of Asterisk v12, the situation has improved somewhat so
peeraccount support can be made to work. Using the indicated example, the
the accountcode values become as follows when the peeraccount is set on
SIP/100 before calling SIP/200:
SIP/100 ---> Local;1 ---- Local;2 ---> SIP/200
acct: 100 \/ acct: 200 \/ acct: 100 \/ acct: 200
peer: 200 /\ peer: 100 /\ peer: 200 /\ peer: 100
If a channel already has an accountcode it can only change by the
following explicit user actions:
1) A channel originate method that can specify an accountcode to use.
2) The calling channel propagating its non-empty peeraccount or its
non-empty accountcode if the peeraccount was empty to the outgoing
channel's accountcode before initiating the dial. e.g., Dial and
FollowMe. The exception to this propagation method is Queue. Queue will
only propagate peeraccounts this way only if the outgoing channel does not
have an accountcode.
3) Dialplan using CHANNEL(accountcode).
4) Dialplan using CHANNEL(peeraccount) on the other end of a local
channel pair.
If a channel does not have an accountcode it can get one from the
following places:
1) The channel driver's configuration at channel creation.
2) Explicit user action as already indicated.
3) Entering a basic or stasis-mixing bridge from a peer channel's
peeraccount value.
You can specify the accountcode for an outgoing channel by setting the
CHANNEL(peeraccount) before using the Dial, FollowMe, and Queue
applications. Queue adds the wrinkle that it will not overwrite an
existing accountcode on the outgoing channel with the calling channels
values.
Accountcode and peeraccount values propagate to an outgoing channel before
dialing. Accountcodes also propagate when channels enter or leave a basic
or stasis-mixing bridge. The peeraccount value only makes sense for
mixing bridges with two channels; it is meaningless otherwise.
* Made peeraccount functional by changing accountcode propagation as
described above.
* Fixed CEL extracting the wrong ie value for the peeraccount. This was
done intentionally in Asterisk v1.8 when that version had to punt on
peeraccount.
* Fixed a few places dealing with accountcodes that were reading from
channels without the lock held.
AFS-65 #close
Review: https://reviewboard.asterisk.org/r/3601/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@419520 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2014-07-24 22:48:38 +00:00
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
Many new featuers in Asterisk 13 were introduced in point releases of
|
|
|
|
Asterisk 12. Following this section - which documents the changes from all
|
|
|
|
versions of Asterisk 12 to Asterisk 13 - users should examine the new features
|
|
|
|
that were introduced in the point releases of Asterisk 12, as they are also
|
|
|
|
included in Asterisk 13.
|
|
|
|
|
|
|
|
Finally, all users upgrading to Asterisk 13 should read the UPGRADE.txt file
|
|
|
|
delivered with this release.
|
|
|
|
|
|
|
|
|
|
|
|
Build System
|
|
|
|
------------------
|
|
|
|
* Sample config files have been moved from configs/ to a sub-folder of that
|
|
|
|
directory, samples.
|
|
|
|
|
|
|
|
* The menuselect utility has been pulled into the Asterisk repository. As a
|
|
|
|
result, the libxml2 development library is now a required dependency for
|
|
|
|
Asterisk.
|
|
|
|
|
|
|
|
* A new Compiler Flag, REF_DEBUG, has been added. When enabled, reference
|
|
|
|
counted objects will emit additional debug information to the refs log file
|
|
|
|
located in the standard Asterisk log file directory. This log file is useful
|
|
|
|
in tracking down object leaks and other reference counting issues. Prior to
|
|
|
|
this version, this option was only available by modifying the source code
|
|
|
|
directly. This change also includes a new script, refcounter.py, in the
|
|
|
|
contrib folder that will process the refs log file. Note that this replaces
|
|
|
|
the refcounter utility that could be built from the utils directory.
|
|
|
|
|
|
|
|
|
|
|
|
Applications
|
|
|
|
------------------
|
|
|
|
|
|
|
|
DahdiBarge
|
Remove many deprecated modules
Billing records are fair,
To get paid is quite bright,
You should really use ODBC;
Good-bye cdr_sqlite.
Microsoft did once push H.323,
Hell, we all remember NetMeeting.
But try to compile chan_h323 now
And you will take quite a beating.
The XMPP and SIP war was fierce,
And in the distant fray
Was birthed res_jabber/chan_jingle;
But neither to stay.
For everyone did care and chase what Google professed.
"Free Internet Calling" was what devotees cried,
But Google did change the specs so often
That the developers were happy the day chan_gtalk died.
And then there was that odd application
Dedicated to the Polish tongue.
app_saycountpl was subsumed by Say;
One could say its bell was rung.
To read and parse a file from the dialplan
You could (I guess) use an application.
app_readfile did fill that purpose, but I think
A function is perhaps better in its creation.
Barging is rude, I'm not sure why we do it.
Inwardly, the caller will probably sigh.
But if you really must do it,
Don't use app_dahdibarge, use ChanSpy.
We all despise the sound of tinny robots
It makes our queues so cold.
To control such an abomination
It's better to not use Wait/SetMusicOnHold.
It's often nice to know properties of a channel
It makes our calls right
We have a nice function called CHANNEL
And so SIPCHANINFO is sent off into the night.
And now things get odd;
Apparently one could delimit with a colon
Properties from the SIPPEER function!
Commas are in; all others are done.
Finally, a word on pipes and commas.
We're sorry. We can't say it enough.
But those compatibility options in asterisk.conf;
To maintain them forever was just too tough.
This patch removes:
* cdr_sqlite
* chan_gtalk
* chan_jingle
* chan_h323
* res_jabber
* app_saycountpl
* app_readfile
* app_dahdibarge
It removes the following applications/functions:
* WaitMusicOnHold
* SetMusicOnHold
* SIPCHANINFO
It removes the colon delimiter from the SIPPEER function.
Finally, it also removes all compatibility options that were configurable from
asterisk.conf, as these all applied to compatibility with Asterisk 1.4 systems.
Review: https://reviewboard.asterisk.org/r/3698/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@418019 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2014-07-04 13:26:37 +00:00
|
|
|
------------------
|
|
|
|
* This module was deprecated and has been removed. Users of app_dahdibarge
|
|
|
|
should use ChanSpy instead.
|
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
MixMonitor
|
|
|
|
------------------
|
|
|
|
* New options to play a beep when starting a recording and stopping a recording
|
|
|
|
have been added. The option "p" will play a beep to the channel that starts
|
|
|
|
the recording. The option "P" will play a beep to the channel that stops the
|
|
|
|
recording.
|
|
|
|
|
app_queue: Add RealTime support for queue rules
This patch gives the optional ability to keep queue rules in RealTime. It is
important to note that with this patch:
(a) Queue rules in RealTime are only examined on module load/reload
(b) Queue rules are loaded both from the queuerules.conf file as well as the
RealTime backend
To inform app_queue to examine RealTime for queue rules, a new setting has been
added to queuerules.conf's general section "realtime_rules". RealTime queue
rules will only be used when this setting is set to "yes".
The schema for the database table supports a rule_name, time, min_penalty, and
max_penalty columns. min_penalty and max_penalty can be relative, if a '-' or
'+' literal is provided. Otherwise, the penalties are treated as constants.
For example:
rule_name, time, min_penalty, max_penalty
'default', '10', '20', '30'
'test2', '20', '30', '55'
'test2', '25', '-11', '+1111'
'test2', '400', '112', '333'
'test3', '0', '4564', '46546'
'test_rule', '40', '15', '50'
which would result in :
Rule: default
- After 10 seconds, adjust QUEUE_MAX_PENALTY to 30 and adjust
QUEUE_MIN_PENALTY to 20
Rule: test2
- After 20 seconds, adjust QUEUE_MAX_PENALTY to 55 and adjust
QUEUE_MIN_PENALTY to 30
- After 25 seconds, adjust QUEUE_MAX_PENALTY by 1111 and adjust
QUEUE_MIN_PENALTY by -11
- After 400 seconds, adjust QUEUE_MAX_PENALTY to 333 and adjust
QUEUE_MIN_PENALTY to 112
Rule: test3
- After 0 seconds, adjust QUEUE_MAX_PENALTY to 46546 and adjust
QUEUE_MIN_PENALTY to 4564
Rule: test_rule
- After 40 seconds, adjust QUEUE_MAX_PENALTY to 50 and adjust
QUEUE_MIN_PENALTY to 15
If you use RealTime, the queue rules will be always reloaded on a module
reload, even if the underlying file did not change. With the option disabled,
the rules will only be reloaded if the file was modified.
Review: https://reviewboard.asterisk.org/r/3607/
ASTERISK-23823 #close
Reported by: Michael K
patches:
app_queue.c_realtime_trunk.patch uploaded by Michael K (License 6621)
........
Merged revisions 420624 from http://svn.asterisk.org/svn/asterisk/branches/13
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@420625 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2014-08-11 00:14:53 +00:00
|
|
|
Queue
|
|
|
|
------------------
|
|
|
|
* Queue rules can now be stored in a database table, queue_rules. Unlike other
|
|
|
|
RealTime tables, the queue_rules table is only examined on module load or
|
|
|
|
module reload. A new general setting has been added to queuerules.conf,
|
|
|
|
'realtime_rules', which, when set to 'yes', will cause app_queue to look in
|
|
|
|
RealTime for additional queue rules to parse. Note that both the file and
|
|
|
|
the database can be used as a provide of queue rules when 'realtime_rules'
|
|
|
|
is set to 'yes'.
|
|
|
|
|
|
|
|
When app_queue is reloaded, all rules are re-parsed and loaded into memory.
|
|
|
|
There is no caching of RealTime queue rules.
|
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
ReadFile
|
Remove many deprecated modules
Billing records are fair,
To get paid is quite bright,
You should really use ODBC;
Good-bye cdr_sqlite.
Microsoft did once push H.323,
Hell, we all remember NetMeeting.
But try to compile chan_h323 now
And you will take quite a beating.
The XMPP and SIP war was fierce,
And in the distant fray
Was birthed res_jabber/chan_jingle;
But neither to stay.
For everyone did care and chase what Google professed.
"Free Internet Calling" was what devotees cried,
But Google did change the specs so often
That the developers were happy the day chan_gtalk died.
And then there was that odd application
Dedicated to the Polish tongue.
app_saycountpl was subsumed by Say;
One could say its bell was rung.
To read and parse a file from the dialplan
You could (I guess) use an application.
app_readfile did fill that purpose, but I think
A function is perhaps better in its creation.
Barging is rude, I'm not sure why we do it.
Inwardly, the caller will probably sigh.
But if you really must do it,
Don't use app_dahdibarge, use ChanSpy.
We all despise the sound of tinny robots
It makes our queues so cold.
To control such an abomination
It's better to not use Wait/SetMusicOnHold.
It's often nice to know properties of a channel
It makes our calls right
We have a nice function called CHANNEL
And so SIPCHANINFO is sent off into the night.
And now things get odd;
Apparently one could delimit with a colon
Properties from the SIPPEER function!
Commas are in; all others are done.
Finally, a word on pipes and commas.
We're sorry. We can't say it enough.
But those compatibility options in asterisk.conf;
To maintain them forever was just too tough.
This patch removes:
* cdr_sqlite
* chan_gtalk
* chan_jingle
* chan_h323
* res_jabber
* app_saycountpl
* app_readfile
* app_dahdibarge
It removes the following applications/functions:
* WaitMusicOnHold
* SetMusicOnHold
* SIPCHANINFO
It removes the colon delimiter from the SIPPEER function.
Finally, it also removes all compatibility options that were configurable from
asterisk.conf, as these all applied to compatibility with Asterisk 1.4 systems.
Review: https://reviewboard.asterisk.org/r/3698/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@418019 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2014-07-04 13:26:37 +00:00
|
|
|
------------------
|
|
|
|
* This module was deprecated and has been removed. Users of app_readfile
|
|
|
|
should use func_env's FILE function instead.
|
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
Say
|
|
|
|
------------------
|
|
|
|
* The 'say' family of dialplan applications now support the Japanese
|
|
|
|
language. The 'language' parameter in say.conf now recognizes a setting of
|
|
|
|
'ja', which will enable Japanese language specific mechanisms for playing
|
|
|
|
back numbers, dates, and other items.
|
2016-06-06 16:13:01 +00:00
|
|
|
* Counting, enumeration and dates now supports Icelandic grammar with the
|
|
|
|
'language' parameter set to 'is'.
|
2014-08-10 22:02:03 +00:00
|
|
|
|
|
|
|
SayCountPL
|
Remove many deprecated modules
Billing records are fair,
To get paid is quite bright,
You should really use ODBC;
Good-bye cdr_sqlite.
Microsoft did once push H.323,
Hell, we all remember NetMeeting.
But try to compile chan_h323 now
And you will take quite a beating.
The XMPP and SIP war was fierce,
And in the distant fray
Was birthed res_jabber/chan_jingle;
But neither to stay.
For everyone did care and chase what Google professed.
"Free Internet Calling" was what devotees cried,
But Google did change the specs so often
That the developers were happy the day chan_gtalk died.
And then there was that odd application
Dedicated to the Polish tongue.
app_saycountpl was subsumed by Say;
One could say its bell was rung.
To read and parse a file from the dialplan
You could (I guess) use an application.
app_readfile did fill that purpose, but I think
A function is perhaps better in its creation.
Barging is rude, I'm not sure why we do it.
Inwardly, the caller will probably sigh.
But if you really must do it,
Don't use app_dahdibarge, use ChanSpy.
We all despise the sound of tinny robots
It makes our queues so cold.
To control such an abomination
It's better to not use Wait/SetMusicOnHold.
It's often nice to know properties of a channel
It makes our calls right
We have a nice function called CHANNEL
And so SIPCHANINFO is sent off into the night.
And now things get odd;
Apparently one could delimit with a colon
Properties from the SIPPEER function!
Commas are in; all others are done.
Finally, a word on pipes and commas.
We're sorry. We can't say it enough.
But those compatibility options in asterisk.conf;
To maintain them forever was just too tough.
This patch removes:
* cdr_sqlite
* chan_gtalk
* chan_jingle
* chan_h323
* res_jabber
* app_saycountpl
* app_readfile
* app_dahdibarge
It removes the following applications/functions:
* WaitMusicOnHold
* SetMusicOnHold
* SIPCHANINFO
It removes the colon delimiter from the SIPPEER function.
Finally, it also removes all compatibility options that were configurable from
asterisk.conf, as these all applied to compatibility with Asterisk 1.4 systems.
Review: https://reviewboard.asterisk.org/r/3698/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@418019 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2014-07-04 13:26:37 +00:00
|
|
|
------------------
|
|
|
|
* This module was deprecated and has been removed. Users of app_saycountpl
|
|
|
|
should use the Say family of applications.
|
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
SetMusicOnHold
|
2014-04-28 14:40:21 +00:00
|
|
|
------------------
|
2014-08-10 22:02:03 +00:00
|
|
|
* The SetMusicOnHold dialplan application was deprecated and has been removed.
|
|
|
|
Users of the application should use the CHANNEL function's musicclass
|
|
|
|
setting instead.
|
2014-04-28 14:40:21 +00:00
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
WaitMusicOnHold
|
|
|
|
------------------
|
|
|
|
* The WaitMusicOnHold dialplan application was deprecated and has been
|
|
|
|
removed. Users of the application should use MusicOnHold with a duration
|
|
|
|
parameter instead.
|
2014-07-03 17:20:00 +00:00
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
VoiceMail
|
|
|
|
------------------
|
|
|
|
* VoiceMail and VoiceMailMain now support the Japanese language. The
|
|
|
|
'language' parameter in voicemail.conf now recognizes a setting of 'ja',
|
|
|
|
which will enable prompts to be played back using a Japanese grammatical
|
|
|
|
structure. Additional prompts are necessary for this functionality,
|
|
|
|
including:
|
|
|
|
- jb-arimasu: there is
|
|
|
|
- jb-arimasen: there is not
|
|
|
|
- jb-oshitekudasai: please press
|
|
|
|
- jb-ni: article ni
|
|
|
|
- jb-ga: article ga
|
|
|
|
- jb-wa: article wa
|
|
|
|
- jb-wo: article wo
|
2014-06-20 20:29:45 +00:00
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
* Add the ability to specify multiple email addresses in configuration,
|
|
|
|
separated by a |.
|
2014-07-18 15:49:46 +00:00
|
|
|
|
2014-07-03 17:34:32 +00:00
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
CDR Backends
|
|
|
|
------------------
|
2014-07-31 16:19:50 +00:00
|
|
|
|
Remove many deprecated modules
Billing records are fair,
To get paid is quite bright,
You should really use ODBC;
Good-bye cdr_sqlite.
Microsoft did once push H.323,
Hell, we all remember NetMeeting.
But try to compile chan_h323 now
And you will take quite a beating.
The XMPP and SIP war was fierce,
And in the distant fray
Was birthed res_jabber/chan_jingle;
But neither to stay.
For everyone did care and chase what Google professed.
"Free Internet Calling" was what devotees cried,
But Google did change the specs so often
That the developers were happy the day chan_gtalk died.
And then there was that odd application
Dedicated to the Polish tongue.
app_saycountpl was subsumed by Say;
One could say its bell was rung.
To read and parse a file from the dialplan
You could (I guess) use an application.
app_readfile did fill that purpose, but I think
A function is perhaps better in its creation.
Barging is rude, I'm not sure why we do it.
Inwardly, the caller will probably sigh.
But if you really must do it,
Don't use app_dahdibarge, use ChanSpy.
We all despise the sound of tinny robots
It makes our queues so cold.
To control such an abomination
It's better to not use Wait/SetMusicOnHold.
It's often nice to know properties of a channel
It makes our calls right
We have a nice function called CHANNEL
And so SIPCHANINFO is sent off into the night.
And now things get odd;
Apparently one could delimit with a colon
Properties from the SIPPEER function!
Commas are in; all others are done.
Finally, a word on pipes and commas.
We're sorry. We can't say it enough.
But those compatibility options in asterisk.conf;
To maintain them forever was just too tough.
This patch removes:
* cdr_sqlite
* chan_gtalk
* chan_jingle
* chan_h323
* res_jabber
* app_saycountpl
* app_readfile
* app_dahdibarge
It removes the following applications/functions:
* WaitMusicOnHold
* SetMusicOnHold
* SIPCHANINFO
It removes the colon delimiter from the SIPPEER function.
Finally, it also removes all compatibility options that were configurable from
asterisk.conf, as these all applied to compatibility with Asterisk 1.4 systems.
Review: https://reviewboard.asterisk.org/r/3698/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@418019 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2014-07-04 13:26:37 +00:00
|
|
|
cdr_sqlite
|
|
|
|
-----------------
|
|
|
|
* This module was deprecated and has been removed. Users of cdr_sqlite
|
|
|
|
should use cdr_sqlite3_custom.
|
|
|
|
|
2014-07-16 13:55:36 +00:00
|
|
|
cdr_pgsql
|
|
|
|
------------------
|
|
|
|
* Added the ability to support PostgreSQL application_name on connections.
|
|
|
|
This allows PostgreSQL to display the configured name in the
|
|
|
|
pg_stat_activity view and CSV log entries. This setting is configurable
|
|
|
|
for cdr_pgsql via the appname configuration setting in cdr_pgsql.conf.
|
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
|
|
|
|
CEL Backends
|
|
|
|
------------------
|
|
|
|
|
2014-07-16 13:55:36 +00:00
|
|
|
cel_pgsql
|
|
|
|
------------------
|
|
|
|
* Added the ability to support PostgreSQL application_name on connections.
|
|
|
|
This allows PostgreSQL to display the configured name in the
|
|
|
|
pg_stat_activity view and CSV log entries. This setting is configurable
|
|
|
|
for cel_pgsql via the appname configuration setting in cel_pgsql.conf.
|
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
|
|
|
|
Channel Drivers
|
2014-06-26 19:15:10 +00:00
|
|
|
------------------
|
|
|
|
|
2014-06-16 18:27:51 +00:00
|
|
|
chan_dahdi
|
|
|
|
------------------
|
|
|
|
* SS7 support now requires libss7 v2.0 or later.
|
|
|
|
|
|
|
|
* Added SS7 support for connected line and redirecting.
|
|
|
|
|
|
|
|
* Most SS7 CLI commands are reworked as well as new SS7 commands added.
|
|
|
|
See online CLI help.
|
|
|
|
|
|
|
|
* Added several SS7 config option parameters described in
|
|
|
|
chan_dahdi.conf.sample.
|
|
|
|
|
Remove many deprecated modules
Billing records are fair,
To get paid is quite bright,
You should really use ODBC;
Good-bye cdr_sqlite.
Microsoft did once push H.323,
Hell, we all remember NetMeeting.
But try to compile chan_h323 now
And you will take quite a beating.
The XMPP and SIP war was fierce,
And in the distant fray
Was birthed res_jabber/chan_jingle;
But neither to stay.
For everyone did care and chase what Google professed.
"Free Internet Calling" was what devotees cried,
But Google did change the specs so often
That the developers were happy the day chan_gtalk died.
And then there was that odd application
Dedicated to the Polish tongue.
app_saycountpl was subsumed by Say;
One could say its bell was rung.
To read and parse a file from the dialplan
You could (I guess) use an application.
app_readfile did fill that purpose, but I think
A function is perhaps better in its creation.
Barging is rude, I'm not sure why we do it.
Inwardly, the caller will probably sigh.
But if you really must do it,
Don't use app_dahdibarge, use ChanSpy.
We all despise the sound of tinny robots
It makes our queues so cold.
To control such an abomination
It's better to not use Wait/SetMusicOnHold.
It's often nice to know properties of a channel
It makes our calls right
We have a nice function called CHANNEL
And so SIPCHANINFO is sent off into the night.
And now things get odd;
Apparently one could delimit with a colon
Properties from the SIPPEER function!
Commas are in; all others are done.
Finally, a word on pipes and commas.
We're sorry. We can't say it enough.
But those compatibility options in asterisk.conf;
To maintain them forever was just too tough.
This patch removes:
* cdr_sqlite
* chan_gtalk
* chan_jingle
* chan_h323
* res_jabber
* app_saycountpl
* app_readfile
* app_dahdibarge
It removes the following applications/functions:
* WaitMusicOnHold
* SetMusicOnHold
* SIPCHANINFO
It removes the colon delimiter from the SIPPEER function.
Finally, it also removes all compatibility options that were configurable from
asterisk.conf, as these all applied to compatibility with Asterisk 1.4 systems.
Review: https://reviewboard.asterisk.org/r/3698/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@418019 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2014-07-04 13:26:37 +00:00
|
|
|
chan_gtalk
|
|
|
|
------------------
|
|
|
|
* This module was deprecated and has been removed. Users of chan_gtalk
|
|
|
|
should use chan_motif.
|
|
|
|
|
|
|
|
chan_h323
|
|
|
|
------------------
|
|
|
|
* This module was deprecated and has been removed. Users of chan_h323
|
|
|
|
should use chan_ooh323.
|
|
|
|
|
|
|
|
chan_jingle
|
|
|
|
------------------
|
|
|
|
* This module was deprecated and has been removed. Users of chan_jingle
|
|
|
|
should use chan_motif.
|
|
|
|
|
2014-10-03 21:58:03 +00:00
|
|
|
chan_pjsip
|
|
|
|
------------------
|
|
|
|
* Added the CLI command 'pjsip list ciphers' so a user can know what
|
|
|
|
OpenSSL names are available on their system for the pjsip.conf cipher
|
|
|
|
option.
|
|
|
|
|
Remove many deprecated modules
Billing records are fair,
To get paid is quite bright,
You should really use ODBC;
Good-bye cdr_sqlite.
Microsoft did once push H.323,
Hell, we all remember NetMeeting.
But try to compile chan_h323 now
And you will take quite a beating.
The XMPP and SIP war was fierce,
And in the distant fray
Was birthed res_jabber/chan_jingle;
But neither to stay.
For everyone did care and chase what Google professed.
"Free Internet Calling" was what devotees cried,
But Google did change the specs so often
That the developers were happy the day chan_gtalk died.
And then there was that odd application
Dedicated to the Polish tongue.
app_saycountpl was subsumed by Say;
One could say its bell was rung.
To read and parse a file from the dialplan
You could (I guess) use an application.
app_readfile did fill that purpose, but I think
A function is perhaps better in its creation.
Barging is rude, I'm not sure why we do it.
Inwardly, the caller will probably sigh.
But if you really must do it,
Don't use app_dahdibarge, use ChanSpy.
We all despise the sound of tinny robots
It makes our queues so cold.
To control such an abomination
It's better to not use Wait/SetMusicOnHold.
It's often nice to know properties of a channel
It makes our calls right
We have a nice function called CHANNEL
And so SIPCHANINFO is sent off into the night.
And now things get odd;
Apparently one could delimit with a colon
Properties from the SIPPEER function!
Commas are in; all others are done.
Finally, a word on pipes and commas.
We're sorry. We can't say it enough.
But those compatibility options in asterisk.conf;
To maintain them forever was just too tough.
This patch removes:
* cdr_sqlite
* chan_gtalk
* chan_jingle
* chan_h323
* res_jabber
* app_saycountpl
* app_readfile
* app_dahdibarge
It removes the following applications/functions:
* WaitMusicOnHold
* SetMusicOnHold
* SIPCHANINFO
It removes the colon delimiter from the SIPPEER function.
Finally, it also removes all compatibility options that were configurable from
asterisk.conf, as these all applied to compatibility with Asterisk 1.4 systems.
Review: https://reviewboard.asterisk.org/r/3698/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@418019 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2014-07-04 13:26:37 +00:00
|
|
|
chan_sip
|
|
|
|
------------------
|
|
|
|
* The SIPPEER dialplan function no longer supports using a colon as a
|
|
|
|
delimiter for parameters. The parameters for the function should be
|
|
|
|
delimited using a comma.
|
|
|
|
|
|
|
|
* The SIPCHANINFO dialplan function was deprecated and has been removed. Users
|
|
|
|
of the function should use the CHANNEL function instead.
|
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
|
2014-07-03 12:10:17 +00:00
|
|
|
Core
|
2014-08-10 22:02:03 +00:00
|
|
|
------------------
|
|
|
|
|
|
|
|
Account Codes
|
|
|
|
------------------
|
|
|
|
* Added functional peeraccount support. Except for Queue, the
|
|
|
|
accountcode propagation is now consistently propagated to outgoing
|
|
|
|
channels before dialing. The channel accountcode can change from its
|
|
|
|
original non-empty value on channel creation for the following specific
|
|
|
|
reasons. One, dialplan sets it using CHANNEL(accountcode). Two, an
|
|
|
|
originate method that can specify an accountcode value. Three, the
|
|
|
|
calling channel propagates its peeraccount or accountcode to the
|
|
|
|
outgoing channel's accountcode before dialing. The change has two
|
|
|
|
visible effects. One, local channels now cross accountcode and
|
|
|
|
peeraccount across the special bridge between the ;1 and ;2 channels
|
|
|
|
just like channels between normal bridges. Two, the
|
|
|
|
CHANNEL(peeraccount) value can now be set before Dial and FollowMe to
|
|
|
|
set the accountcode on the outgoing channel(s).
|
|
|
|
|
|
|
|
For Queue, an outgoing channel's non-empty accountcode will not change
|
|
|
|
unless explicitly set by CHANNEL(accountcode). The change has three
|
|
|
|
visible effects. One, local channels now cross accountcode and
|
|
|
|
peeraccount across the special bridge between the ;1 and ;2 channels
|
|
|
|
just like channels between normal bridges. Two, the queue member will
|
|
|
|
get an accountcode if it doesn't have one and one is available from the
|
|
|
|
calling channel's peeraccount. Three, accountcode propagation includes
|
|
|
|
local channel members where the accountcodes are propagated early
|
|
|
|
enough to be available on the ;2 channel.
|
|
|
|
|
|
|
|
AMI
|
|
|
|
------------------
|
|
|
|
* New DeviceStateChanged and PresenceStateChanged AMI events have been added.
|
|
|
|
These events are emitted whenever a device state or presence state change
|
|
|
|
occurs. The events are controlled by res_manager_device_state.so and
|
|
|
|
res_manager_presence_state.so. If the high frequency of these events is
|
|
|
|
problematic for you, do not load these modules.
|
|
|
|
|
|
|
|
* Added DialplanExtensionAdd and DialplanExtensionRemove AMI commands. They
|
|
|
|
work in basically the same way as the 'dialplan add extension' and
|
|
|
|
'dialplan remove extension' CLI commands respectively.
|
|
|
|
|
|
|
|
* New AMI action LoggerRotate reloads and rotates logger in the same manner
|
|
|
|
as CLI command 'logger rotate'
|
|
|
|
|
|
|
|
* New AMI Actions FAXSessions, FAXSession, and FAXStats replicate the
|
|
|
|
functionality of CLI commands 'fax show sessions', 'fax show session',
|
|
|
|
and fax show stats' respectively.
|
|
|
|
|
|
|
|
* New AMI actions PRIDebugSet, PRIDebugFileSet, and PRIDebugFileUnset
|
|
|
|
enable manager control over PRI debugging levels and file output.
|
|
|
|
|
|
|
|
* AMI action PJSIPNotify may now send to a URI instead of only to a PJSIP
|
|
|
|
endpoint as long as a default outbound endpoint is set. This also applies
|
|
|
|
to the equivalent CLI command (pjsip send notify)
|
main/stasis: Allow subscriptions to use a threadpool for message delivery
Prior to this patch, all Stasis subscriptions would receive a dedicated
thread for servicing published messages. In contrast, prior to r400178
(see review https://reviewboard.asterisk.org/r/2881/), the subscriptions
shared a thread pool. It was discovered during some initial work on Stasis
that, for a low subscription count with high message throughput, the
threadpool was not as performant as simply having a dedicated thread per
subscriber.
For situations where a subscriber receives a substantial number of messages
and is always present, the model of having a dedicated thread per subscriber
makes sense. While we still have plenty of subscriptions that would follow
this model, e.g., AMI, CDRs, CEL, etc., there are plenty that also fall into
the following two categories:
* Large number of subscriptions, specifically those tied to endpoints/peers.
* Low number of messages. Some subscriptions exist specifically to coordinate
a single message - the subscription is created, a message is published, the
delivery is synchronized, and the subscription is destroyed.
In both of the latter two cases, creating a dedicated thread is wasteful (and
in the case of a large number of peers/endpoints, harmful). In those cases,
having shared delivery threads is far more performant.
This patch adds the ability of a subscriber to Stasis to choose whether or not
their messages are dispatched on a dedicated thread or on a threadpool. The
threadpool is configurable through stasis.conf.
Review: https://reviewboard.asterisk.org/r/4193
ASTERISK-24533 #close
Reported by: xrobau
Tested by: xrobau
........
Merged revisions 428681 from http://svn.asterisk.org/svn/asterisk/branches/12
........
Merged revisions 428687 from http://svn.asterisk.org/svn/asterisk/branches/13
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@428688 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2014-12-01 17:59:21 +00:00
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
* The AMI action PJSIPShowEndpoint now includes ContactStatusDetail sections
|
|
|
|
that give information on Asterisk's attempts to qualify the endpoint.
|
|
|
|
|
2014-08-18 00:57:01 +00:00
|
|
|
* The DialEnd event will now contain a Forward header if the dial is ending
|
|
|
|
due to the call being forwarded. The contents of the Forward header is the
|
|
|
|
extension in the number to which the call is being forwarded.
|
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
CEL
|
|
|
|
------------------
|
|
|
|
* The "bridge_technology" extra field key has been added to BRIDGE_ENTER
|
|
|
|
and BRIDGE_EXIT events.
|
|
|
|
|
|
|
|
Features
|
|
|
|
------------------
|
|
|
|
* Channel variables are now substituted in arguments passed to applications
|
|
|
|
run by using dynamic features.
|
|
|
|
|
|
|
|
TLS
|
2014-07-03 12:10:17 +00:00
|
|
|
------------------
|
|
|
|
* The TLS core in Asterisk now supports Perfect Forward Secrecy (PFS).
|
|
|
|
Enabling PFS is attempted by default, and is dependent on the configuration
|
|
|
|
of the module using TLS.
|
|
|
|
- Ephemeral ECDH (ECDHE) is enabled by default. To disable it, do not
|
|
|
|
specify a ECDHE cipher suite in sip.conf, for example:
|
|
|
|
tlscipher=AES128-SHA:DES-CBC3-SHA
|
|
|
|
- Ephemeral DH (DHE) is disabled by default. To enable it, add DH parameters
|
|
|
|
into the private key file, e.g., sip.conf tlsprivatekey. For example, the
|
|
|
|
default dh2048.pem - see
|
|
|
|
http://www.opensource.apple.com/source/OpenSSL098/OpenSSL098-35.1/src/apps/dh2048.pem?txt
|
|
|
|
- Because clients expect the server to prefer PFS, and because OpenSSL sorts
|
|
|
|
its cipher suites by bit strength, see "openssl ciphers -v DEFAULT".
|
|
|
|
Consider re-ordering your cipher suites in the respective configuration
|
|
|
|
file. For example:
|
|
|
|
tlscipher=AES128+kEECDH:AES128+kEDH:3DES+kEDH:AES128-SHA:DES-CBC3-SHA:-ADH:-AECDH
|
|
|
|
will use PFS when offered by the client. Clients which do not offer PFS
|
|
|
|
fall-back to AES-128 (or even 3DES, as recommended by RFC 3261).
|
|
|
|
|
2014-06-26 19:15:10 +00:00
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
Functions
|
|
|
|
------------------
|
2014-07-22 20:22:36 +00:00
|
|
|
|
2014-06-26 12:43:05 +00:00
|
|
|
JACK_HOOK
|
|
|
|
------------------
|
|
|
|
* The JACK_HOOK function now supports audio with a sample rate higher than
|
|
|
|
8kHz.
|
|
|
|
|
Remove many deprecated modules
Billing records are fair,
To get paid is quite bright,
You should really use ODBC;
Good-bye cdr_sqlite.
Microsoft did once push H.323,
Hell, we all remember NetMeeting.
But try to compile chan_h323 now
And you will take quite a beating.
The XMPP and SIP war was fierce,
And in the distant fray
Was birthed res_jabber/chan_jingle;
But neither to stay.
For everyone did care and chase what Google professed.
"Free Internet Calling" was what devotees cried,
But Google did change the specs so often
That the developers were happy the day chan_gtalk died.
And then there was that odd application
Dedicated to the Polish tongue.
app_saycountpl was subsumed by Say;
One could say its bell was rung.
To read and parse a file from the dialplan
You could (I guess) use an application.
app_readfile did fill that purpose, but I think
A function is perhaps better in its creation.
Barging is rude, I'm not sure why we do it.
Inwardly, the caller will probably sigh.
But if you really must do it,
Don't use app_dahdibarge, use ChanSpy.
We all despise the sound of tinny robots
It makes our queues so cold.
To control such an abomination
It's better to not use Wait/SetMusicOnHold.
It's often nice to know properties of a channel
It makes our calls right
We have a nice function called CHANNEL
And so SIPCHANINFO is sent off into the night.
And now things get odd;
Apparently one could delimit with a colon
Properties from the SIPPEER function!
Commas are in; all others are done.
Finally, a word on pipes and commas.
We're sorry. We can't say it enough.
But those compatibility options in asterisk.conf;
To maintain them forever was just too tough.
This patch removes:
* cdr_sqlite
* chan_gtalk
* chan_jingle
* chan_h323
* res_jabber
* app_saycountpl
* app_readfile
* app_dahdibarge
It removes the following applications/functions:
* WaitMusicOnHold
* SetMusicOnHold
* SIPCHANINFO
It removes the colon delimiter from the SIPPEER function.
Finally, it also removes all compatibility options that were configurable from
asterisk.conf, as these all applied to compatibility with Asterisk 1.4 systems.
Review: https://reviewboard.asterisk.org/r/3698/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@418019 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2014-07-04 13:26:37 +00:00
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
Resources
|
2014-06-30 04:00:19 +00:00
|
|
|
------------------
|
2014-08-08 19:16:29 +00:00
|
|
|
|
2014-07-16 13:55:36 +00:00
|
|
|
res_config_pgsql
|
|
|
|
------------------
|
|
|
|
* Added the ability to support PostgreSQL application_name on connections.
|
|
|
|
This allows PostgreSQL to display the configured name in the
|
|
|
|
pg_stat_activity view and CSV log entries. This setting is configurable
|
|
|
|
for res_config_pgsql via the dbappname configuration setting in
|
|
|
|
res_pgsql.conf.
|
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
res_pjsip_outbound_publish
|
2014-07-22 20:01:42 +00:00
|
|
|
------------------
|
2014-08-10 22:02:03 +00:00
|
|
|
* A new module, res_pjsip_outbound_publish provides the mechanisms for sending
|
|
|
|
PUBLISH requests for specific event packages to another SIP User Agent.
|
|
|
|
|
|
|
|
res_pjsip_pubsub
|
|
|
|
------------------
|
|
|
|
* The publish/subscribe core module has been updated to support RFC 4662
|
|
|
|
Resource Lists, allowing Asterisk to act as a Resource List Server (RLS).
|
|
|
|
Resource lists are configured in pjsip.conf under a new object type,
|
|
|
|
resource_list. Resource lists can contain either message-summary or presence
|
|
|
|
events, and can be composed of specific resources that provide the event or
|
|
|
|
other resource lists.
|
|
|
|
|
|
|
|
* Inbound publication support is provided by a new object, inbound-publication.
|
|
|
|
This configures res_pjsip_pubsub to accept PUBLISH requests from a particular
|
|
|
|
resource. Which events are accepted is constructed dynamically; see
|
|
|
|
res_pjsip_publish_asterisk for more information.
|
|
|
|
|
|
|
|
res_pjsip_publish_asterisk
|
|
|
|
------------------
|
|
|
|
* A new module, res_pjsip_publish_asterisk adds support for PUBLISH requests of
|
|
|
|
Asterisk information to other Asterisk servers. This module is intended only
|
|
|
|
for Asterisk to Asterisk exchanges of information. Currently, this includes
|
|
|
|
both mailbox state and device state information.
|
|
|
|
|
2014-07-16 14:03:51 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 12.4.0 to Asterisk 12.5.0 ------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
2014-07-18 21:48:46 +00:00
|
|
|
ARI
|
|
|
|
------------------
|
|
|
|
* Stored recordings now support a new operation, copy. This will take an
|
|
|
|
existing stored recording and copy it to a new location in the recordings
|
|
|
|
directory.
|
|
|
|
|
2014-07-25 14:47:09 +00:00
|
|
|
* LiveRecording objects now have three additional fields that can be reported
|
|
|
|
in a RecordingFinished ARI event:
|
|
|
|
- total_duration: the duration of the recording
|
|
|
|
- talking_duration: optional. The duration of talking detected in the
|
|
|
|
recording. This is only available if max_silence_seconds was specified
|
|
|
|
when the recording was started.
|
|
|
|
- silence_duration: optional. The duration of silence detected in the
|
|
|
|
recording. This is only available if max_silence_seconds was specified
|
|
|
|
when the recording was started.
|
|
|
|
Note that all duration values are reported in seconds.
|
|
|
|
|
Multiple revisions 420089-420090,420097
........
r420089 | mjordan | 2014-08-05 15:10:52 -0500 (Tue, 05 Aug 2014) | 72 lines
ARI: Add channel technology agnostic out of call text messaging
This patch adds the ability to send and receive text messages from various
technology stacks in Asterisk through ARI. This includes chan_sip (sip),
res_pjsip_messaging (pjsip), and res_xmpp (xmpp). Messages are sent using the
endpoints resource, and can be sent directly through that resource, or to a
particular endpoint.
For example, the following would send the message "Hello there" to PJSIP
endpoint alice with a display URI of sip:asterisk@mycooldomain.org:
ari/endpoints/sendMessage?to=pjsip:alice&from=sip:asterisk@mycooldomain.org&body=Hello+There
This is equivalent to the following as well:
ari/endpoints/PJSIP/alice/sendMessage?from=sip:asterisk@mycooldomain.org&body=Hello+There
Both forms are available for message technologies that allow for arbitrary
destinations, such as chan_sip.
Inbound messages can now be received over ARI as well. An ARI application that
subscribes to endpoints will receive messages from those endpoints:
{
"type": "TextMessageReceived",
"timestamp": "2014-07-12T22:53:13.494-0500",
"endpoint": {
"technology": "PJSIP",
"resource": "alice",
"state": "online",
"channel_ids": []
},
"message": {
"from": "\"alice\" <sip:alice@127.0.0.1>",
"to": "pjsip:asterisk@127.0.0.1",
"body": "Watson, come here.",
"variables": []
},
"application": "testsuite"
}
The above was made possible due to some rather major changes in the message
core. This includes (but is not limited to):
- Users of the message API can now register message handlers. A handler has
two callbacks: one to determine if the handler has a destination for the
message, and another to handle it.
- All dialplan functionality of handling a message was moved into a message
handler provided by the message API.
- Messages can now have the technology/endpoint associated with them.
Various other properties are also now more easily accessible.
- A number of ao2 containers that weren't really needed were replaced with
vectors. Iteration over ao2_containers is expensive and pointless when
the lifetime of things is well defined and the number of things is very
small.
res_stasis now has a new file that makes up its structure, messaging. The
messaging functionality implements a message handler, and passes received
messages that match an interested endpoint over to the app for processing.
Note that inadvertently while testing this, I reproduced ASTERISK-23969.
res_pjsip_messaging was incorrectly parsing out the 'to' field, such that
arbitrary SIP URIs mangled the endpoint lookup. This patch includes the
fix for that as well.
Review: https://reviewboard.asterisk.org/r/3726
ASTERISK-23692 #close
Reported by: Matt Jordan
ASTERISK-23969 #close
Reported by: Andrew Nagy
........
r420090 | mjordan | 2014-08-05 15:16:37 -0500 (Tue, 05 Aug 2014) | 2 lines
Remove automerge properties :-(
........
r420097 | mjordan | 2014-08-05 16:36:25 -0500 (Tue, 05 Aug 2014) | 2 lines
test_message: Fix strict-aliasing compilation issue
........
Merged revisions 420089-420090,420097 from http://svn.asterisk.org/svn/asterisk/branches/12
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@420098 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2014-08-05 21:44:09 +00:00
|
|
|
* Users of ARI can now send and receive out of call text messages. Messages
|
|
|
|
can be sent directly to a particular endpoint, or can be sent to the
|
|
|
|
endpoints resource directly and inferred from the URI scheme. Text
|
|
|
|
messages are passed to ARI clients as TextMessageReceived events. ARI
|
|
|
|
clients can choose to receive text messages by subscribing to the particular
|
|
|
|
endpoint technology or endpoints that they are interested in.
|
|
|
|
|
|
|
|
* The applications resource now supports subscriptions to all endpoints of
|
|
|
|
a particular channel technology. For example, subscribing to an eventSource
|
|
|
|
of 'endpoint:PJSIP' will subscribe to all PJSIP endpoints.
|
|
|
|
|
2014-07-16 14:03:51 +00:00
|
|
|
res_pjsip
|
|
|
|
------------------
|
|
|
|
* The endpoint configuration object now supports 'accountcode'. Any channel
|
|
|
|
created for an endpoint with this setting will have its accountcode set
|
|
|
|
to the specified value.
|
|
|
|
|
res_hep_rtcp: Add module that sends RTCP information to a Homer Server
This patch adds a new module to Asterisk, res_hep_rtcp. The module subscribes
to the RTCP topics in Stasis and receives RTCP information back from the
message bus. It encodes into HEPv3 packets and sends the information to the
res_hep module for transmission.
Using this, someone with a Homer server can get live call quality monitoring
for all RTP-based channels in their Asterisk 12+ systems.
In addition, there were a few bugs in the RTP engine, res_rtp_asterisk, and
chan_pjsip that were uncovered by the tests written for the Asterisk Test
Suite. This patch fixes the following:
1) chan_pjsip failed to set its channel unique ids on its RTP instance on
outbound calls. It now does this in the appropriate location, in the
serialized call callback.
2) The rtp_engine was overflowing some values when packed into JSON.
Specifically, some longs and unsigned ints can't be be packed into integer
values, for obvious reasons. Since libjansson only supports integers,
floats, strings, booleans, and objects, we print these values into strings.
3) res_rtp_asterisk had a few problems:
(a) it would emit a source IP address of 0.0.0.0 if bound to that IP
address. We now use ast_find_ourip to get a better IP address, and
properly marshal the result into an ast_strdupa'd string.
(b) Reports can be generated with no report bodies. In particular, this
occurs when a sender is transmitting information to a receiver (who
will send no RTP back to the sender). As such, the sender has no report
body for what it received. We now properly handle this case, and the
sender will emit SR reports with no body. Likewise, if we receive an
RTCP packet with no report body, we will still generate the appropriate
events.
ASTERISK-24119 #close
........
Merged revisions 419823 from http://svn.asterisk.org/svn/asterisk/branches/12
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@419825 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2014-07-31 11:57:51 +00:00
|
|
|
res_hep_rtcp
|
|
|
|
------------------
|
|
|
|
* A new module, res_hep_rtcp, has been added that will forward RTCP call
|
|
|
|
statistics to a HEP capture server. See res_hep for more information.
|
|
|
|
|
2014-07-18 16:28:10 +00:00
|
|
|
Functions
|
|
|
|
------------------
|
|
|
|
* Function AUDIOHOOK_INHERIT has been deprecated. Audiohooks are now
|
|
|
|
unconditionally inhereted through masquerades. As a side benefit, more
|
|
|
|
than one audiohook of a given type may persist through a masquerade now.
|
2014-07-16 14:03:51 +00:00
|
|
|
|
2014-05-28 16:34:47 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 12.3.0 to Asterisk 12.4.0 ------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
|
|
|
AgentRequest
|
|
|
|
------------------
|
|
|
|
* Returns new AGENT_STATUS value "NOT_CONNECTED" if the agent fails to
|
|
|
|
connect with an incoming caller after being alerted to the presence
|
|
|
|
of the incoming caller. The most likely reason this would happen is
|
|
|
|
the agent did not acknowledge the call in time.
|
|
|
|
|
2014-05-30 12:42:57 +00:00
|
|
|
AMI
|
|
|
|
------------------
|
|
|
|
* New events have been added for the TALK_DETECT function. When the function
|
|
|
|
is used on a channel, ChannelTalkingStart/ChannelTalkingStop events will be
|
|
|
|
emitted to connected AMI clients indicating the start/stop of talking on
|
|
|
|
the channel.
|
|
|
|
|
|
|
|
ARI
|
|
|
|
------------------
|
|
|
|
* New event models have been aded for the TALK_DETECT function. When the
|
|
|
|
function is used on a channel, ChannelTalkingStarted/ChannelTalkingFinished
|
|
|
|
events will be emitted to connected WebSockets subscribed to the channel,
|
|
|
|
indicating the start/stop of talking on the channel.
|
|
|
|
|
|
|
|
Functions
|
|
|
|
------------------
|
|
|
|
* A new function, TALK_DETECT, has been added. When set on a channel, this
|
|
|
|
fucntion causes events indicating the starting/stoping of talking on said
|
|
|
|
channel to be emitted to both AMI and ARI clients.
|
|
|
|
|
2014-04-17 21:57:36 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 12.2.0 to Asterisk 12.3.0 ------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
|
|
|
ARI
|
|
|
|
------------------
|
|
|
|
* A new Playback URI 'tone' has been added. Tones are specified either as
|
|
|
|
an indication name (e.g. 'tone:busy') from indications.conf or as a tone
|
|
|
|
pattern (e.g. 'tone:240/250,0/250'). Tones differ from normal playback
|
|
|
|
URIs in that they must be stopped manually and will continue to occupy
|
|
|
|
a channel's ARI control queue until they are stopped. They also can not
|
|
|
|
be rewound or fastforwarded.
|
|
|
|
|
2014-05-22 16:09:51 +00:00
|
|
|
* User events can now be generated from ARI. Events can be signalled with
|
|
|
|
arbitrary json variables, and include one or more of channel, bridge, or
|
|
|
|
endpoint snapshots. An application must be specified which will receive
|
|
|
|
the event message (other applications can subscribe to it). The message
|
|
|
|
will also be delivered via AMI provided a channel is attached. Dialplan
|
|
|
|
generated user event messages are still transmitted via the channel, and
|
|
|
|
will only be received by a stasis application they are attached to or if
|
|
|
|
the channel is subscribed to.
|
|
|
|
|
2014-04-21 16:20:32 +00:00
|
|
|
chan_sip
|
|
|
|
-----------
|
|
|
|
* SIP peers can now specify 'trust_id_outbound' which affects RPID/PAI
|
|
|
|
fields for prohibited callingpres information. Values are legacy, no, and
|
|
|
|
yes. By default, legacy is used.
|
2014-04-21 17:56:26 +00:00
|
|
|
trust_id_outbound=legacy - behavior remains the same as 1.8.26.1. When
|
|
|
|
dealing with prohibited callingpres and sendrpid=pai/rpid, RPID/PAI
|
|
|
|
headers are appended to outbound SIP messages just as they are with
|
|
|
|
allowed callingpres values, but data about the remote party's identity is
|
|
|
|
anonymized.
|
|
|
|
When sendrpid=rpid, only the remote party's domain is anonymized.
|
|
|
|
trust_id_outbound=no - when dealing with prohibited callingpres, RPID/PAI
|
|
|
|
headers are not sent.
|
|
|
|
trust_id_outbound=yes - RPID/PAI headers are applied with the full remote
|
|
|
|
party information in tact even for prohibited callingpres information.
|
|
|
|
In the case of PAI, a Privacy: id header will be appended for prohibited
|
|
|
|
calling information to communicate that the private information should
|
|
|
|
not be relayed to untrusted parties.
|
2014-04-21 16:20:32 +00:00
|
|
|
|
2014-05-02 16:06:40 +00:00
|
|
|
res_parking
|
|
|
|
------------------
|
|
|
|
* Manager action 'Park' now takes an additional argument 'AnnounceChannel'
|
|
|
|
which can be used to announce the parked call's location to an arbitrary
|
|
|
|
channel in a bridge. If 'Channel' and 'TimeoutChannel' are now the two
|
|
|
|
parties in a one to one bridge, 'TimeoutChannel' is treated as having
|
|
|
|
parked 'Channel' like with the Park Call DTMF feature and will receive
|
|
|
|
announcements prior to being hung up.
|
|
|
|
|
2014-04-17 21:57:36 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 12.1.0 to Asterisk 12.2.0 ------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
Record
|
|
|
|
------------------
|
2014-02-05 17:42:26 +00:00
|
|
|
* Record application now has an option 'o' which allows 0 to act as an exit
|
|
|
|
key setting the RECORD_STATUS variable to 'OPERATOR' instead of 'DTMF'
|
2014-04-05 13:06:34 +00:00
|
|
|
|
2014-01-31 23:04:25 +00:00
|
|
|
ChanSpy
|
|
|
|
--------------------------
|
|
|
|
* ChanSpy now accepts a channel uniqueid or a fully specified channel name
|
|
|
|
as the chanprefix parameter if the 'u' option is specified.
|
|
|
|
|
2013-11-01 22:48:14 +00:00
|
|
|
ConfBridge
|
|
|
|
--------------------------
|
|
|
|
* CONFBRIDGE dialplan function is now capable of creating/modifying dynamic
|
|
|
|
conference user menus.
|
|
|
|
|
|
|
|
* CONFBRIDGE dialplan function is now capable of removing dynamic conference
|
|
|
|
menus, bridge settings, and user settings that have been applied by the
|
|
|
|
CONFBRIDGE dialplan function.
|
|
|
|
|
2013-12-09 17:29:48 +00:00
|
|
|
* The ConfBridge dialplan application now sets a channel variable,
|
|
|
|
CONFBRIGE_RESULT, upon exiting. This variable can be used to determine
|
|
|
|
how a channel exited the conference.
|
|
|
|
|
2013-11-15 22:38:52 +00:00
|
|
|
* Added conference user option 'announce_join_leave_review'. This option
|
|
|
|
implies 'announce_join_leave' with the added effect that the user will
|
|
|
|
be asked if they want to confirm or re-record the recording of their
|
|
|
|
name when entering the conference
|
|
|
|
|
2013-11-21 22:38:31 +00:00
|
|
|
Directory
|
|
|
|
--------------------------
|
|
|
|
* At exit, the Directory application now sets a channel variable
|
|
|
|
DIRECTORY_RESULT to one of the following based on the reason for exiting:
|
|
|
|
OPERATOR user requested operator by pressing '0' for operator
|
|
|
|
ASSISTANT user requested assistant by pressing '*' for assistant
|
|
|
|
TIMEOUT user pressed nothing and Directory stopped waiting
|
|
|
|
HANGUP user's channel hung up
|
|
|
|
SELECTED user selected a user from the directory and is routed
|
|
|
|
USEREXIT user pressed '#' from the selection prompt to exit
|
|
|
|
FAILED directory failed in a way that wasn't accounted for. Dang.
|
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
Monitor
|
|
|
|
------------------
|
|
|
|
* Monitor() - A new option, B(), has been added that will turn on a periodic
|
|
|
|
beep while the call is being recorded.
|
|
|
|
|
2014-01-17 14:17:04 +00:00
|
|
|
MusicOnHold
|
|
|
|
--------------------------
|
|
|
|
* MusicOnHold streams (all modes other than "files") now support wide band
|
|
|
|
audio too.
|
|
|
|
|
2013-12-09 22:17:14 +00:00
|
|
|
Page
|
|
|
|
--------------------------
|
|
|
|
* Added options 'b' and 'B' to apply predial handlers for outgoing calls
|
|
|
|
and for the channel executing Page respectively.
|
|
|
|
|
2013-11-22 16:43:21 +00:00
|
|
|
PickupChan
|
|
|
|
--------------------------
|
2013-12-09 22:17:14 +00:00
|
|
|
* PickupChan now accepts channel uniqueids of channels to pickup.
|
2013-11-22 16:43:21 +00:00
|
|
|
|
2013-11-14 20:32:45 +00:00
|
|
|
Say
|
|
|
|
--------------------------
|
|
|
|
* If a channel variable SAY_DTMF_INTERRUPT is present on a channel and set
|
|
|
|
to 'true' (case insensitive), then any Say application (SayNumber,
|
|
|
|
SayDigits, SayAlpha, SayAlphaCase, SayUnixTime, and SayCounted) will
|
|
|
|
anticipate DTMF. If DTMF is received, these applications will behave like
|
|
|
|
the background application and jump to the received extension once a match
|
|
|
|
is established or after a short period of inactivity.
|
|
|
|
|
2013-12-09 16:42:59 +00:00
|
|
|
MixMonitor
|
|
|
|
-------------------------
|
|
|
|
* A new function, MIXMONITOR, has been added to allow access to individual
|
|
|
|
instances of MixMonitor on a channel.
|
2014-08-10 22:02:03 +00:00
|
|
|
|
2014-04-15 23:21:19 +00:00
|
|
|
* A new option, B(), has been added that will turn on a periodic beep while the
|
|
|
|
call is being recorded.
|
2013-12-09 16:42:59 +00:00
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
|
2014-04-12 02:27:43 +00:00
|
|
|
Channel Drivers
|
|
|
|
-------------------------
|
|
|
|
|
|
|
|
chan_sip
|
|
|
|
-------------------------
|
|
|
|
* TEL URI support for inbound INVITE requests has been added. chan_sip will
|
|
|
|
now handle TEL schemes in the Request and From URIs. The phone-context in
|
2014-04-17 19:50:05 +00:00
|
|
|
the Request URI will be stored in the SIPURIPHONECONTEXT channel variable on
|
2014-04-12 02:27:43 +00:00
|
|
|
the inbound channel.
|
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
Core
|
|
|
|
------------------
|
|
|
|
* Exposed sorcery-based configuration files like pjsip.conf to dialplans via
|
|
|
|
the new AST_SORCERY diaplan function.
|
|
|
|
|
2014-01-24 22:34:23 +00:00
|
|
|
* Core Show Locks output now includes Thread/LWP ID if the platform
|
|
|
|
supports this feature.
|
2014-08-10 22:02:03 +00:00
|
|
|
|
2014-02-13 15:51:22 +00:00
|
|
|
* New "logger add channel" and "logger remove channel" CLI commands have
|
|
|
|
been added to allow creation and deletion of dynamic logger channels
|
|
|
|
without configuration changes. These dynamic logger channels will only
|
|
|
|
exist until the next restart of asterisk.
|
2014-01-24 22:34:23 +00:00
|
|
|
|
2014-03-19 12:54:25 +00:00
|
|
|
ARI
|
|
|
|
------------------
|
|
|
|
* The live recording object on recording events now contains a target_uri
|
|
|
|
field which contains the URI of what is being recorded.
|
|
|
|
|
|
|
|
* The bridge type used when creating a bridge is now a comma separated list of
|
|
|
|
bridge properties. Valid options are: mixing, holding, dtmf_events, and
|
|
|
|
proxy_media.
|
|
|
|
|
2014-03-14 17:56:53 +00:00
|
|
|
* A channelId can now be provided when creating a channel, either in the
|
|
|
|
uri (POST channels/my-channel-id) or as query parameter. A local channel
|
|
|
|
will suffix the second channel id with ';2' unless provided as query
|
|
|
|
parameter otherChannelId.
|
|
|
|
|
|
|
|
* A bridgeId can now be provided when creating a bridge, either in the uri
|
|
|
|
(POST bridges/my-bridge-id) or as a query parameter.
|
|
|
|
|
|
|
|
* A playbackId can be provided when starting a playback, either in the uri
|
2014-04-18 20:09:24 +00:00
|
|
|
(POST channels/my-channel-id/play/my-playback-id /
|
|
|
|
POST bridges/my-bridge-id/play/my-playback-id) or as a query parameter.
|
2014-03-14 17:56:53 +00:00
|
|
|
|
|
|
|
* A snoop channel can be started with a snoopId, in the uri or query.
|
|
|
|
|
|
|
|
AMI
|
|
|
|
------------------
|
|
|
|
* Originate now takes optional parameters ChannelId and OtherChannelId,
|
|
|
|
used to set the UniqueId on creation. The other id is assigned to the
|
|
|
|
second channel when dialing LOCAL, or defaults to appending ;2 if only
|
|
|
|
the single Id is given.
|
2014-04-17 21:57:36 +00:00
|
|
|
|
2014-04-09 21:43:23 +00:00
|
|
|
* The Mixmonitor action now has a "Command" header that can be used to
|
|
|
|
indicate a post-process command to run once recording finishes.
|
2014-03-14 17:56:53 +00:00
|
|
|
|
2014-03-28 17:41:23 +00:00
|
|
|
RealTime
|
|
|
|
------------------
|
|
|
|
* A new set of Alembic scripts has been added for CDR tables. This will create
|
|
|
|
a 'cdr' table with the default schema that Asterisk expects.
|
|
|
|
|
2014-08-10 22:02:03 +00:00
|
|
|
|
|
|
|
Functions
|
|
|
|
------------------
|
|
|
|
* A new function was added: PERIODIC_HOOK. This allows running a periodic
|
|
|
|
dialplan hook on a channel. Any audio generated by this hook will be
|
|
|
|
injected into the call.
|
|
|
|
|
|
|
|
|
|
|
|
Resources
|
|
|
|
------------------
|
|
|
|
|
2014-03-28 18:32:50 +00:00
|
|
|
res_hep
|
|
|
|
------------------
|
|
|
|
* A new module, res_hep, has been added, that acts as a generic packet
|
|
|
|
capture agent for the Homer Encapsulation Protocol (HEP) version 3.
|
|
|
|
It can be configured via hep.conf. Other modules can use res_hep to send
|
|
|
|
message traffic to a HEP capture server.
|
|
|
|
|
|
|
|
res_hep_pjsip
|
|
|
|
------------------
|
|
|
|
* A new module, res_hep_pjsip, has been added that will forward PJSIP
|
|
|
|
message traffic to a HEP capture server. See res_hep for more
|
|
|
|
information.
|
|
|
|
|
2014-03-14 16:42:54 +00:00
|
|
|
res_pjsip
|
|
|
|
------------------
|
|
|
|
* transport and endpoint ToS options (tos, tos_audio, and tos_video) may now
|
|
|
|
be set as the named set of ToS values (cs0-cs7, af11-af43, ef).
|
2014-03-06 22:39:54 +00:00
|
|
|
|
2014-03-28 17:41:23 +00:00
|
|
|
* Added the following new CLI commands:
|
|
|
|
- "pjsip show contacts" - list all current PJSIP contacts.
|
|
|
|
- "pjsip show contact" - show specific information about a current PJSIP
|
|
|
|
contact.
|
|
|
|
- "pjsip show channel" - show detailed information about a PJSIP channel.
|
|
|
|
|
|
|
|
res_pjsip_multihomed
|
|
|
|
------------------
|
|
|
|
* A new module, res_pjsip_multihomed handles situations where the system
|
|
|
|
Asterisk is running out has multiple interfaces. res_pjsip_multihomed
|
|
|
|
determines which interface should be used during message sending.
|
|
|
|
|
|
|
|
res_pjsip_pidf_digium_body_supplement
|
|
|
|
------------------
|
|
|
|
* A new module, res_pjsip_pidf_digium_body_supplement provides NOTIFY
|
|
|
|
request body formatting for presence support in Digium phones.
|
|
|
|
|
|
|
|
res_pjsip_send_to_voicemail
|
|
|
|
------------------
|
|
|
|
* A new module, res_pjsip_send_to_voicemail allows for REFER requests with
|
|
|
|
particular headers to transfer a PJSIP channel directly to a particular
|
|
|
|
extension that has VoiceMail. This is intended to be used with Digium
|
|
|
|
phones that support this feature.
|
|
|
|
|
|
|
|
res_pjsip_outbound_registration
|
|
|
|
------------------
|
|
|
|
* A new CLI command has been added: "pjsip show registrations", which lists
|
|
|
|
all configured PJSIP registrations
|
|
|
|
|
|
|
|
|
2014-01-15 16:48:02 +00:00
|
|
|
------------------------------------------------------------------------------
|
2014-01-15 16:51:08 +00:00
|
|
|
--- Functionality changes from Asterisk 12.0.0 to Asterisk 12.1.0 ------------
|
2014-01-15 16:48:02 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
2014-02-05 15:29:12 +00:00
|
|
|
AMI
|
|
|
|
------------------
|
|
|
|
* Added a new module that provides AMI control over MWI within Asterisk,
|
|
|
|
res_mwi_external_ami. Note that this module depends on res_mwi_external;
|
|
|
|
for more information on enabling this module, see res_mwi_external.
|
|
|
|
This module provides the MWIGet/MWIUpdate/MWIDelete actions, as well as
|
|
|
|
the MWIGet/MWIGetComplete events.
|
|
|
|
|
|
|
|
* The DialStatus field in the DialEnd event can now contain additional
|
|
|
|
statuses that convey how the dial operation terminated. This includes
|
|
|
|
ABORT, CONTINUE, and GOTO.
|
|
|
|
|
2014-02-06 21:24:32 +00:00
|
|
|
* AMI will now emit security events. A new class authorization has been
|
|
|
|
added in manager.conf for the security events, 'security'. The new events
|
|
|
|
are:
|
|
|
|
- FailedACL - raised when a request violates an ACL check
|
|
|
|
- InvalidAccountID - raised when a request fails an authentication
|
|
|
|
check due to an invalid account ID
|
|
|
|
- SessionLimit - raised when a request fails due to exceeding the
|
|
|
|
number of allowed concurrent sessions for a service
|
|
|
|
- MemoryLimit - raised when a request fails due to an internal memory
|
|
|
|
allocation failure
|
|
|
|
- LoadAverageLimit - raised when a request fails because a configured
|
|
|
|
load average limit has been reached
|
|
|
|
- RequestNotAllowed - raised when a request is not allowed by
|
|
|
|
the service
|
|
|
|
- AuthMethodNotAllowed - raised when a request used an authentication
|
|
|
|
method not allowed by the service
|
|
|
|
- RequestBadFormat - raised when a request is received with bad formatting
|
|
|
|
- SuccessfulAuth - raised when a request successfully authenticates
|
|
|
|
- UnexpectedAddress - raised when a request has a different source address
|
|
|
|
then what is expected for a session already in progress with a service
|
|
|
|
- ChallengeResponseFailed - raised when a request's attempt to authenticate
|
|
|
|
has been challenged, and the request failed the authentication challenge
|
|
|
|
- InvalidPassword - raised when a request provides an invalid password
|
|
|
|
during an authentication attempt
|
|
|
|
- ChallengeSent - raised when an Asterisk service send an authentication
|
|
|
|
challenge to a request
|
|
|
|
- InvalidTransport - raised when a request attempts to use a transport not
|
|
|
|
allowed by the Asterisk service
|
|
|
|
|
2014-02-05 20:56:51 +00:00
|
|
|
* Bridge related events now have two additional fields: BridgeName and
|
|
|
|
BridgeCreator. BridgeName is a descriptive name for the bridge;
|
|
|
|
BridgeCreator is the name of the entity that created the bridge. This
|
|
|
|
affects the following events: ConfbridgeStart, ConfbridgeEnd,
|
|
|
|
ConfbridgeJoin, ConfbridgeLeave, ConfbridgeRecord, ConfbridgeStopRecord,
|
|
|
|
ConfbridgeMute, ConfbridgeUnmute, ConfbridgeTalking, BlindTransfer,
|
|
|
|
AttendedTransfer, BridgeCreate, BridgeDestroy, BridgeEnter, BridgeLeave
|
|
|
|
|
2014-01-15 16:48:02 +00:00
|
|
|
ARI
|
|
|
|
------------------
|
2014-02-05 20:56:51 +00:00
|
|
|
* The Bridge data model now contains the additional fields 'name' and
|
|
|
|
'creator'. The 'name' field conveys a descriptive name for the bridge;
|
|
|
|
the 'creator' field conveys the name of the entity that created the bridge.
|
|
|
|
This affects all responses to HTTP requests that return a Bridge data model
|
|
|
|
as well as all event derived data models that contain a Bridge data model.
|
|
|
|
The POST /bridges operation may now optionally specify a name to give to
|
|
|
|
the bridge being created.
|
2014-02-05 17:21:39 +00:00
|
|
|
|
2014-01-15 16:48:02 +00:00
|
|
|
* Added a new ARI resource 'mailboxes' which allows the creation and
|
|
|
|
modification of mailboxes managed by external MWI. Modules res_mwi_external
|
2014-02-05 15:29:12 +00:00
|
|
|
and res_stasis_mailbox must be enabled to use this resource. For more
|
|
|
|
information on external MWI control, see res_mwi_external.
|
|
|
|
|
|
|
|
* Added new events for externally initiated transfers. The event
|
|
|
|
BridgeBlindTransfer is now raised when a channel initiates a blind transfer
|
|
|
|
of a bridge in the ARI controlled application to the dialplan; the
|
|
|
|
BridgeAttendedTransfer event is raised when a channel initiates an
|
|
|
|
attended transfer of a bridge in the ARI controlled application to the
|
|
|
|
dialplan.
|
|
|
|
|
|
|
|
* Channel variables may now be specified as a body parameter to the
|
|
|
|
POST /channels operation. The 'variables' key in the JSON is interpreted
|
|
|
|
as a sequence of key/value pairs that will be added to the created channel
|
|
|
|
as channel variables. Other parameters in the JSON body are treated as
|
|
|
|
query parameters of the same name.
|
2014-01-15 16:48:02 +00:00
|
|
|
|
2014-02-06 21:24:32 +00:00
|
|
|
HTTP
|
|
|
|
------------------
|
|
|
|
* Asterisk's HTTP server now supports chunked Transfer-Encoding. This will be
|
|
|
|
automatically handled by the HTTP server if a request is received with a
|
|
|
|
Transfer-Encoding type of "chunked".
|
|
|
|
|
2014-02-05 15:29:12 +00:00
|
|
|
res_pjsip
|
2014-01-15 16:48:02 +00:00
|
|
|
------------------
|
|
|
|
* Path support has been added with the 'support_path' option in registration
|
|
|
|
and aor sections.
|
|
|
|
|
2014-01-31 23:15:47 +00:00
|
|
|
* A 'debug' option has been added to the globals section that will allow
|
|
|
|
sip messages to be logged.
|
|
|
|
|
2014-02-05 15:29:12 +00:00
|
|
|
* A 'set_var' option has been added to endpoints that will automatically
|
|
|
|
set the desired variable(s) on a channel created for that endpoint.
|
|
|
|
|
|
|
|
* Several new tables and columns have been added to the realtime schema for
|
|
|
|
the res_pjsip related modules. See the UPGRADE.txt notes for updating
|
|
|
|
the database schema.
|
|
|
|
|
|
|
|
res_mwi_external
|
|
|
|
------------------
|
|
|
|
* A new module, res_mwi_external, has been added to Asterisk. This module
|
|
|
|
acts as a base framework that other modules can build on top of to allow
|
|
|
|
an external system to control MWI within Asterisk. For implementations
|
|
|
|
that make use of res_mwi_external, see res_mwi_external_ami and
|
|
|
|
res_ari_mailboxes. Note that res_mwi_external canflicts with other modules
|
|
|
|
that may produce MWI themselves, such as app_voicemail. res_mwi_external
|
|
|
|
and other modules that depend on it cannot be built or loaded with
|
|
|
|
app_voicemail present.
|
|
|
|
|
2014-03-17 22:54:32 +00:00
|
|
|
res_pjsip
|
|
|
|
------------------
|
|
|
|
* DNS functionality will now automatically be enabled if the system configured
|
|
|
|
nameservers can be retrieved. If the system configured nameservers can not be
|
|
|
|
retrieved the functionality will resort to using system resolution. Functionalty
|
|
|
|
such as SRV records and failover will not be available if system resolution
|
|
|
|
is in use.
|
2014-02-05 15:29:12 +00:00
|
|
|
|
2012-09-04 19:26:02 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 11 to Asterisk 12 --------------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
Overview
|
|
|
|
------------------
|
|
|
|
|
|
|
|
Asterisk 12 is a standard release of the Asterisk project. As such, the
|
|
|
|
focus of development for this release was on core architectural changes and
|
|
|
|
major new features. This includes:
|
|
|
|
* A more flexible bridging core based on the Bridging API
|
|
|
|
* A new internal message bus, Stasis
|
|
|
|
* Major standardization and consistency improvements to AMI
|
|
|
|
* Addition of the Asterisk RESTful Interface (ARI)
|
|
|
|
* A new SIP channel driver, chan_pjsip
|
|
|
|
In addition, as the vast majority of bridging in Asterisk was migrated to the
|
|
|
|
Bridging API used by ConfBridge, major changes were made to most of the
|
|
|
|
interfaces in Asterisk. This includes not only AMI, but also CDRs and CEL.
|
|
|
|
|
|
|
|
Specifications have been written for the affected interfaces. These
|
|
|
|
specifications are available on the Asterisk wiki:
|
|
|
|
* AMI - https://wiki.asterisk.org/wiki/x/dAFRAQ
|
|
|
|
* CEL - https://wiki.asterisk.org/wiki/x/4ICLAQ
|
|
|
|
* CDRs - https://wiki.asterisk.org/wiki/x/pwpRAQ
|
|
|
|
|
|
|
|
It is *highly* recommended that anyone migrating to Asterisk 12 read the
|
|
|
|
information regarding its release both in this file and in the accompanying
|
|
|
|
UPGRADE.txt file. More detailed information on the major changes can be found
|
|
|
|
on the Asterisk wiki at https://wiki.asterisk.org/wiki/x/0YCLAQ.
|
|
|
|
|
|
|
|
|
|
|
|
Build System
|
|
|
|
------------------
|
|
|
|
* Added build option DISABLE_INLINE. This option can be used to work around a
|
|
|
|
bug in gcc. For more information, see
|
|
|
|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47816
|
|
|
|
|
|
|
|
* Removed the CHANNEL_TRACE development mode build option. Certain aspects of
|
|
|
|
the CHANNEL_TRACE build option were incompatible with the new bridging
|
|
|
|
architecture.
|
|
|
|
|
|
|
|
* Asterisk now optionally uses libxslt to improve XML documentation generation
|
|
|
|
and maintainability. If libxslt is not available on the system, some XML
|
|
|
|
documentation will be incomplete.
|
|
|
|
|
|
|
|
* Asterisk now depends on libjansson. If a package of libjansson is not
|
|
|
|
available on your distro, please see http://www.digip.org/jansson/.
|
|
|
|
|
|
|
|
* Asterisk now depends on libuuid and, optionally, uriparser. It is
|
|
|
|
recommended that you install uriparser, even if it is optional.
|
|
|
|
|
|
|
|
* The new SIP stack and channel driver uses a particular version of PJSIP.
|
|
|
|
Please see https://wiki.asterisk.org/wiki/x/J4GLAQ for more information on
|
|
|
|
configuring and installing PJSIP for usage with Asterisk.
|
|
|
|
|
optional_api: Fix linking problems between modules that export global symbols
With the new work in Asterisk 12, there are some uses of the
optional_api that are prone to failure. The details are rather involved,
and captured on [the wiki][1].
This patch addresses the issue by removing almost all of the magic from
the optional API implementation. Instead of relying on weak symbol
resolution, a new optional_api.c module was added to Asterisk core.
For modules providing an optional API, the pointer to the implementation
function is registered with the core. For modules that use an optional
API, a pointer to a stub function, along with a optional_ref function
pointer are registered with the core. The optional_ref function pointers
is set to the implementation function when it's provided, or the stub
function when it's now.
Since the implementation no longer relies on magic, it is now supported
on all platforms. In the spirit of choice, an OPTIONAL_API flag was
added, so we can disable the optional_api if needed (maybe it's buggy on
some bizarre platform I haven't tested on)
The AST_OPTIONAL_API*() macros themselves remained unchanged, so
existing code could remain unchanged. But to help with debugging the
optional_api, the patch limits the #include of optional API's to just
the modules using the API. This also reduces resource waste maintaining
optional_ref pointers that aren't used.
Other changes made as a part of this patch:
* The stubs for http_websocket that wrap system calls set errno to
ENOSYS.
* res_http_websocket now properly increments module use count.
* In loader.c, the while() wrappers around dlclose() were removed. The
while(!dlclose()) is actually an anti-pattern, which can lead to
infinite loops if the module you're attempting to unload exports a
symbol that was directly linked to.
* The special handling of nonoptreq on systems without weak symbol
support was removed, since we no longer rely on weak symbols for
optional_api.
[1]: https://wiki.asterisk.org/wiki/x/wACUAQ
(closes issue ASTERISK-22296)
Reported by: Matt Jordan
Review: https://reviewboard.asterisk.org/r/2797/
........
Merged revisions 397989 from http://svn.asterisk.org/svn/asterisk/branches/12
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@397990 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2013-08-30 13:40:27 +00:00
|
|
|
* Optional API was re-implemented to be more portable, and no longer requires
|
|
|
|
weak reference support from the compiler. The build option OPTIONAL_API may
|
|
|
|
be disabled to disable Optional API support.
|
2013-08-28 20:49:02 +00:00
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
Applications
|
|
|
|
------------------
|
|
|
|
|
Replace chan_agent with app_agent_pool.
The ill conceived chan_agent is no more. It is now replaced by
app_agent_pool.
Agents login using the AgentLogin() application as before. The
AgentLogin() application no longer does any authentication.
Authentication is now the responsibility of the dialplan. (Besides, the
authentication done by chan_agent did not match what the voice prompts
asked for.)
Sample extensions.conf
[login]
; Sample agent 1001 login
; Set COLP for in between calls so the agent does not see the last caller COLP.
exten => 1001,1,Set(CONNECTEDLINE(all)="Agent Waiting" <1001>)
; Give the agent DTMF transfer and disconnect features when connected to a caller.
same => n,Set(CHANNEL(dtmf-features)=TX)
same => n,AgentLogin(1001)
same => n,NoOp(AGENT_STATUS is ${AGENT_STATUS})
same => n,Hangup()
[caller]
; Sample caller direct connect to agent 1001
exten => 800,1,AgentRequest(1001)
same => n,NoOp(AGENT_STATUS is ${AGENT_STATUS})
same => n,Hangup()
; Sample caller going through a Queue to agent 1001
exten => 900,1,Queue(agent_q)
same => n,Hangup()
Sample queues.conf
[agent_q]
member => Local/800@caller,,SuperAgent,Agent:1001
Under the hood operation overview:
1) Logged in agents wait for callers in an agents holding bridge.
2) Caller requests an agent using AgentRequest()
3) A basic bridge is created, the agent is notified, and caller joins the
basic bridge to wait for the agent.
4) The agent is either automatically connected to the caller or must ack
the call to connect.
5) The agent is moved from the agents holding bridge to the basic bridge.
6) The agent and caller talk.
7) The connection is ended by either party.
8) The agent goes back to the agents holding bridge.
To avoid some locking issues with the agent holding bridge, I needed to
make some changes to the after bridge callback support. The after bridge
callback is now a list of requested callbacks with the last to be added
the only active callback. The after bridge callback for failed callbacks
will always happen in the channel thread when the channel leaves the
bridging system or is destroyed.
(closes issue ASTERISK-21554)
Reported by: Matt Jordan
Review: https://reviewboard.asterisk.org/r/2657/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@394417 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2013-07-15 23:20:55 +00:00
|
|
|
AgentLogin
|
|
|
|
------------------
|
2013-08-28 20:49:02 +00:00
|
|
|
* Along with AgentRequest, this application has been modified to be a
|
|
|
|
replacement for chan_agent. The act of a channel calling the AgentLogin
|
|
|
|
application places the channel into a pool of agents that can be
|
|
|
|
requested by the AgentRequest application. Note that this application, as
|
|
|
|
well as all other agent related functionality, is now provided by the
|
|
|
|
app_agent_pool module. See chan_agent and AgentRequest for more information.
|
|
|
|
|
|
|
|
* This application no longer performs agent authentication. If authentication
|
|
|
|
is desired, the dialplan needs to perform this function using the
|
|
|
|
Authenticate or VMAuthenticate application or through an AGI script before
|
|
|
|
running AgentLogin.
|
|
|
|
|
|
|
|
* If this application is called and the agent is already logged in, the
|
|
|
|
dialplan will continue exection with the AGENT_STATUS channel variable set
|
|
|
|
to ALREADY_LOGGED_IN.
|
|
|
|
|
|
|
|
* The agents.conf schema has changed. Rather than specifying agents on a
|
|
|
|
single line in comma delineated fashion, each agent is defined in a separate
|
|
|
|
context. This allows agents to use the power of context templates in their
|
|
|
|
definition.
|
|
|
|
|
|
|
|
* A number of parameters from agents.conf have been removed. This includes
|
|
|
|
maxloginretries, autologoffunavail, updatecdr, goodbye, group, recordformat,
|
|
|
|
urlprefix, and savecallsin. These options were obsoleted by the move from
|
|
|
|
a channel driver model to the bridging/application model provided by
|
|
|
|
app_agent_pool.
|
|
|
|
|
|
|
|
AgentRequest
|
|
|
|
------------------
|
|
|
|
* A new application, this will request a logged in agent from the pool and
|
|
|
|
bridge the requested channel with the channel calling this application.
|
|
|
|
Logged in agents are those channels that called the AgentLogin application.
|
|
|
|
If an agent cannot be requested from the pool, the AGENT_STATUS dialplan
|
|
|
|
application will be set with an appropriate error value.
|
Replace chan_agent with app_agent_pool.
The ill conceived chan_agent is no more. It is now replaced by
app_agent_pool.
Agents login using the AgentLogin() application as before. The
AgentLogin() application no longer does any authentication.
Authentication is now the responsibility of the dialplan. (Besides, the
authentication done by chan_agent did not match what the voice prompts
asked for.)
Sample extensions.conf
[login]
; Sample agent 1001 login
; Set COLP for in between calls so the agent does not see the last caller COLP.
exten => 1001,1,Set(CONNECTEDLINE(all)="Agent Waiting" <1001>)
; Give the agent DTMF transfer and disconnect features when connected to a caller.
same => n,Set(CHANNEL(dtmf-features)=TX)
same => n,AgentLogin(1001)
same => n,NoOp(AGENT_STATUS is ${AGENT_STATUS})
same => n,Hangup()
[caller]
; Sample caller direct connect to agent 1001
exten => 800,1,AgentRequest(1001)
same => n,NoOp(AGENT_STATUS is ${AGENT_STATUS})
same => n,Hangup()
; Sample caller going through a Queue to agent 1001
exten => 900,1,Queue(agent_q)
same => n,Hangup()
Sample queues.conf
[agent_q]
member => Local/800@caller,,SuperAgent,Agent:1001
Under the hood operation overview:
1) Logged in agents wait for callers in an agents holding bridge.
2) Caller requests an agent using AgentRequest()
3) A basic bridge is created, the agent is notified, and caller joins the
basic bridge to wait for the agent.
4) The agent is either automatically connected to the caller or must ack
the call to connect.
5) The agent is moved from the agents holding bridge to the basic bridge.
6) The agent and caller talk.
7) The connection is ended by either party.
8) The agent goes back to the agents holding bridge.
To avoid some locking issues with the agent holding bridge, I needed to
make some changes to the after bridge callback support. The after bridge
callback is now a list of requested callbacks with the last to be added
the only active callback. The after bridge callback for failed callbacks
will always happen in the channel thread when the channel leaves the
bridging system or is destroyed.
(closes issue ASTERISK-21554)
Reported by: Matt Jordan
Review: https://reviewboard.asterisk.org/r/2657/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@394417 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2013-07-15 23:20:55 +00:00
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
AgentMonitorOutgoing
|
|
|
|
------------------
|
2013-08-28 20:49:02 +00:00
|
|
|
* This application has been removed. It was a holdover from when
|
|
|
|
AgentCallbackLogin was removed.
|
|
|
|
|
|
|
|
AlarmReceiver
|
|
|
|
------------------
|
|
|
|
* Added support for additional Ademco DTMF signalling formats, including
|
|
|
|
Express 4+1, Express 4+2, High Speed and Super Fast.
|
|
|
|
|
|
|
|
* Added channel variable ALARMRECEIVER_CALL_LIMIT. This sets the maximum
|
|
|
|
call time, in milliseconds, to run the application.
|
|
|
|
|
|
|
|
* Added channel variable ALARMRECEIVER_RETRIES_LIMIT. This sets the
|
|
|
|
maximum number of times to retry the call.
|
|
|
|
|
|
|
|
* Added a new configuration option answait. If set, the AlarmReceiver
|
|
|
|
application will wait the number of milliseconds specified by answait
|
|
|
|
after the channel has answered. Valid values range between 500
|
|
|
|
milliseconds and 10000 milliseconds.
|
|
|
|
|
|
|
|
* Added configuration option no_group_meta. If enabled, grouping of metadata
|
|
|
|
information in the AlarmReceiver log file will be skipped.
|
|
|
|
|
app_cdr,app_forkcdr,func_cdr: Synchronize with engine when manipulating state
When doing the rework of the CDR engine that pushed all of the logic into cdr.c
and made it respond to changes in channel state over Stasis, we knew that
accessing the CDR engine from the dialplan would be "slightly"
non-deterministic. Dialplan threads would be accessing CDRs while Stasis
threads would be updating the state of said CDRs - whereas in the past,
everything happened on the dialplan threads. Tests have shown that "slightly"
is in reality "very".
This patch synchronizes things by making the dialplan applications/functions
that manipulate CDRs do so over Stasis. ForkCDR, NoCDR, ResetCDR, CDR, and
CDR_PROP now all use Stasis to send their requests over to the CDR engine,
and synchronize on the channel Stasis topic via a subscription so that they
return their values/control to the dialplan at the appropriate time.
While going through this, the following changes were also made:
* DISA, which can reset the CDR when a user successfully authenticates, now
just uses the ResetCDR app to do this. This prevents having to duplicate
the same Stasis synchronization logic in that application.
* Answer no longer disables CDRs. It actually didn't work anyway - calling
DISABLE on the channel's CDR doesn't stop the CDR from getting the Answer
time - it just kills all CDRs on that channel, which isn't what the caller
would intend.
(closes issue ASTERISK-22884)
(closes issue ASTERISK-22886)
Review: https://reviewboard.asterisk.org/r/3057/
........
Merged revisions 404294 from http://svn.asterisk.org/svn/asterisk/branches/12
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@404295 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2013-12-19 00:50:01 +00:00
|
|
|
Answer
|
|
|
|
------------------
|
|
|
|
* It is now no longer possible to bypass updating the CDR on the channel
|
|
|
|
when answering. CDRs reflect the state of the channel and will always
|
|
|
|
reflect the time they were Answered.
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
BridgeWait
|
|
|
|
------------------
|
|
|
|
* A new application in Asterisk, this will place the calling channel
|
|
|
|
into a holding bridge, optionally entertaining them with some form of
|
|
|
|
media. Channels participating in a holding bridge do not interact with
|
|
|
|
other channels in the same holding bridge. Optionally, however, a channel
|
|
|
|
may join as an announcer. Any media passed from an announcer channel is
|
|
|
|
played to all channels in the holding bridge. Channels leave a holding
|
|
|
|
bridge either when an optional timer expires, or via the ChannelRedirect
|
|
|
|
application or AMI Redirect action.
|
2013-06-17 03:00:38 +00:00
|
|
|
|
2013-07-16 22:33:27 +00:00
|
|
|
ConfBridge
|
|
|
|
------------------
|
|
|
|
* All participants in a bridge can now be kicked out of a conference room
|
|
|
|
by specifying the channel parameter as 'all' in the ConfBridge kick CLI
|
2013-08-28 20:49:02 +00:00
|
|
|
command, i.e., 'confbridge kick <conference> all'
|
|
|
|
|
|
|
|
* CLI output for the 'confbridge list' command has been improved. When
|
|
|
|
displaying information about a particular bridge, flags will now be shown
|
|
|
|
for the participating users indicating properties of that user.
|
|
|
|
|
|
|
|
* The ConfbridgeList event now contains the following fields: WaitMarked,
|
|
|
|
EndMarked, and Waiting. This displays additional properties about the
|
|
|
|
user's profile, as well as whether or not the user is waiting for a
|
|
|
|
Marked user to enter the conference.
|
|
|
|
|
|
|
|
* Added a new option for conference recording, record_file_append. If enabled,
|
|
|
|
when the recording is stopped and then re-started, the existing recording
|
|
|
|
will be used and appended to.
|
|
|
|
|
2013-10-08 20:18:37 +00:00
|
|
|
* ConfBridge now has the ability to set the language of announcements to the
|
|
|
|
conference. The language can be set on a bridge profile in confbridge.conf
|
|
|
|
or by the dialplan function CONFBRIDGE(bridge,language)=en.
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
ControlPlayback
|
|
|
|
------------------
|
|
|
|
* The channel variable CPLAYBACKSTATUS may now return the value
|
|
|
|
'REMOTESTOPPED'. This occurs when playback is stopped by a remote interface,
|
|
|
|
such as AMI. See the AMI action ControlPlayback for more information.
|
|
|
|
|
|
|
|
Directory
|
|
|
|
------------------
|
|
|
|
* Added the 'a' option, which allows the caller to enter in an additional
|
|
|
|
alias for the user in the directory. This option must be used in conjunction
|
|
|
|
with the 'f', 'l', or 'b' options. Note that the alias for a user can be
|
|
|
|
specified in voicemail.conf.
|
|
|
|
|
|
|
|
DumpChan
|
|
|
|
------------------
|
|
|
|
* The output of DumpChan no longer includes the DirectBridge or IndirectBridge
|
|
|
|
fields. Instead, if a channel is in a bridge, it includes a BridgeID field
|
|
|
|
containing the unique ID of the bridge that the channel happens to be in.
|
2013-07-16 22:33:27 +00:00
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
ForkCDR
|
|
|
|
------------------
|
|
|
|
* ForkCDR no longer automatically resets the forked CDR. See the 'r' option
|
|
|
|
for more information.
|
|
|
|
|
|
|
|
* Variables are no longer purged from the original CDR. See the 'v' option for
|
|
|
|
more information.
|
|
|
|
|
|
|
|
* The 'A' option has been removed. The Answer time on a CDR is never updated
|
|
|
|
once set.
|
|
|
|
|
|
|
|
* The 'd' option has been removed. The disposition on a CDR is a function of
|
|
|
|
the state of the channel and cannot be altered.
|
|
|
|
|
|
|
|
* The 'D' option has been removed. Who the Party B is on a CDR is a function
|
2013-08-28 20:49:02 +00:00
|
|
|
of the state of the respective channels involved in the CDR and cannot be
|
|
|
|
altered.
|
2013-06-17 03:00:38 +00:00
|
|
|
|
|
|
|
* The 'r' option has been changed. Previously, ForkCDR always reset the CDR
|
|
|
|
such that the start time and, if applicable, the answer time was updated.
|
|
|
|
Now, by default, ForkCDR simply forks the CDR, maintaining any times. The
|
|
|
|
'r' option now triggers the Reset, setting the start time (and answer time
|
2013-08-28 20:49:02 +00:00
|
|
|
if applicable) to the current time. Note that the 'a' option still sets
|
|
|
|
the answer time to the current time if the channel was already answered.
|
2013-06-17 03:00:38 +00:00
|
|
|
|
|
|
|
* The 's' option has been removed. A variable can be set on the original CDR
|
|
|
|
if desired using the CDR function, and removed from a forked CDR using the
|
|
|
|
same function.
|
|
|
|
|
|
|
|
* The 'T' option has been removed. The concept of DONT_TOUCH and LOCKED no
|
|
|
|
longer applies in the CDR engine.
|
|
|
|
|
|
|
|
* The 'v' option now prevents the copy of the variables from the original CDR
|
|
|
|
to the forked CDR. Previously the variables were always copied but were
|
2013-08-28 20:49:02 +00:00
|
|
|
removed from the original. This was changed as removing variables from a CDR
|
|
|
|
can have unintended side effects - this option allows the user to prevent
|
|
|
|
propagation of variables from the original to the forked without modifying
|
|
|
|
the original.
|
2013-06-17 03:00:38 +00:00
|
|
|
|
|
|
|
MeetMe
|
|
|
|
-------------------
|
2013-08-28 20:49:02 +00:00
|
|
|
* Added the 'n' option to MeetMe to prevent application of the DENOISE
|
|
|
|
function to a channel joining a conference. Some channel drivers that vary
|
|
|
|
the number of audio samples in a voice frame will experience significant
|
|
|
|
quality problems if a denoiser is attached to the channel; this option gives
|
|
|
|
them the ability to remove the denoiser without having to unload func_speex.
|
|
|
|
|
|
|
|
MixMonitor
|
|
|
|
------------------
|
|
|
|
* The 'b' option now includes conferences as well as sounds played to the
|
|
|
|
participants.
|
|
|
|
|
|
|
|
* The AUDIOHOOK_INHERIT function is no longer needed to keep a MixMonitor
|
|
|
|
running during a transfer. If a MixMonitor is started on a channel,
|
|
|
|
the MixMonitor will continue to record the audio passing through the
|
|
|
|
channel even in the presence of transfers.
|
2013-06-17 03:00:38 +00:00
|
|
|
|
|
|
|
NoCDR
|
|
|
|
------------------
|
|
|
|
* The NoCDR application is deprecated. Please use the CDR_PROP function to
|
|
|
|
disable CDRs.
|
2013-08-28 20:49:02 +00:00
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
* While the NoCDR application will prevent CDRs for a channel from being
|
|
|
|
propagated to registered CDR backends, it will not prevent that data from
|
|
|
|
being collected. Hence, a subsequent call to ResetCDR or the CDR_PROP
|
|
|
|
function that enables CDRs on a channel will restore those records that have
|
|
|
|
not yet been finalized.
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
ParkAndAnnounce
|
|
|
|
-------------------
|
|
|
|
* The app_parkandannounce module has been removed. The application
|
|
|
|
ParkAndAnnounce is now provided by the res_parking module. See the
|
|
|
|
res_parking changes for more information.
|
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
Queue
|
|
|
|
-------------------
|
2013-08-28 20:49:02 +00:00
|
|
|
* Added queue available hint. The hint can be added to the dialplan using the
|
|
|
|
following syntax: exten,hint,Queue:{queue_name}_avail
|
|
|
|
For example, if the name of the queue is 'markq':
|
|
|
|
exten => 8501,hint,Queue:markq_avail
|
|
|
|
This will report 'InUse' if there are no logged in agents or no free agents.
|
|
|
|
It will report 'Idle' when an agent is free.
|
|
|
|
|
|
|
|
* Queues now support a hint for member paused state. The hint uses the form
|
|
|
|
'Queue:{queue_name}_pause_{member_name}', where {queue_name} and {member_name}
|
|
|
|
are the name of the queue and the name of the member to subscribe to,
|
|
|
|
respectively. For example: exten => 8501,hint,Queue:sales_pause_mark.
|
|
|
|
Members will show as In Use when paused.
|
2013-06-17 03:00:38 +00:00
|
|
|
|
2013-06-17 14:31:51 +00:00
|
|
|
* The configuration options eventwhencalled and eventmemberstatus have been
|
|
|
|
removed. As a result, the AMI events QueueMemberStatus, AgentCalled,
|
|
|
|
AgentConnect, AgentComplete, AgentDump, and AgentRingNoAnswer will always be
|
|
|
|
sent. The "Variable" fields will also no longer exist on the Agent* events.
|
2013-08-28 20:49:02 +00:00
|
|
|
These events can be filtered out from a connected AMI client using the
|
|
|
|
eventfilter setting in manager.conf.
|
2013-06-17 14:31:51 +00:00
|
|
|
|
2013-08-22 18:52:41 +00:00
|
|
|
* The queue log now differentiates between blind and attended transfers. A
|
|
|
|
blind transfer will result in a BLINDTRANSFER message with the destination
|
|
|
|
context and extension. An attended transfer will result in an
|
|
|
|
ATTENDEDTRANSFER message. This message will indicate the method by which
|
|
|
|
the attended transfer was completed: "BRIDGE" for a bridge merge, "APP"
|
|
|
|
for running an application on a bridge or channel, or "LINK" for linking
|
2013-08-28 20:49:02 +00:00
|
|
|
two bridges together with local channels. The queue log will also now detect
|
|
|
|
externally initiated blind and attended transfers and record the transfer
|
|
|
|
status accordingly.
|
2013-08-22 18:52:41 +00:00
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* When performing queue pause/unpause on an interface without specifying an
|
|
|
|
individual queue, the PAUSEALL/UNPAUSEALL event will only be logged if at
|
|
|
|
least one member of any queue exists for that interface.
|
|
|
|
|
|
|
|
* Added the 'queue_log_realtime_use_gmt' option to have timestamps in GMT
|
|
|
|
for realtime queue log entries.
|
2013-08-01 19:11:46 +00:00
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
ResetCDR
|
|
|
|
------------------
|
|
|
|
* The 'e' option has been deprecated. Use the CDR_PROP function to re-enable
|
|
|
|
CDRs when they were previously disabled on a channel.
|
2013-08-28 20:49:02 +00:00
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
* The 'w' and 'a' options have been removed. Dispatching CDRs to registered
|
|
|
|
backends occurs on an as-needed basis in order to preserve linkedid
|
|
|
|
propagation and other needed behavior.
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
SayAlphaCase
|
|
|
|
------------------
|
|
|
|
* A new application, this is similar to SayAlpha except that it supports
|
|
|
|
case sensitive playback of the specified characters. For example,
|
|
|
|
SayAlphaCase(u,aBc) will result in 'a uppercase b c'.
|
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
SetAMAFlags
|
|
|
|
------------------
|
2013-08-28 20:49:02 +00:00
|
|
|
* This application is deprecated in favor of CHANNEL(amaflags).
|
|
|
|
|
|
|
|
SendDTMF
|
|
|
|
------------------
|
|
|
|
* The SendDTMF application will now accept 'W' as valid input. This will cause
|
|
|
|
the application to delay one second while streaming DTMF.
|
|
|
|
|
|
|
|
Stasis
|
|
|
|
------------------
|
|
|
|
* A new application in Asterisk 12, this hands control of the channel calling
|
|
|
|
the application over to an external system. Currently, external systems
|
|
|
|
manipulate channels in Stasis through the Asterisk RESTful Interface (ARI).
|
2013-06-17 03:00:38 +00:00
|
|
|
|
2013-06-17 14:31:51 +00:00
|
|
|
UserEvent
|
|
|
|
------------------
|
|
|
|
* UserEvent will now handle duplicate keys by overwriting the previous value
|
2013-08-28 20:49:02 +00:00
|
|
|
assigned to the key.
|
2013-06-17 14:31:51 +00:00
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* In addition to AMI, UserEvent invocations will now be distributed to any
|
|
|
|
interested Stasis applications.
|
2013-06-17 03:00:38 +00:00
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
VoiceMail
|
2013-08-01 17:07:52 +00:00
|
|
|
------------------
|
2013-12-19 16:52:43 +00:00
|
|
|
* Mailboxes defined by app_voicemail MUST be referenced by the rest of the
|
|
|
|
system as mailbox@context. The rest of the system cannot add @default
|
|
|
|
to mailbox identifiers for app_voicemail that do not specify a context
|
|
|
|
any longer. It is a mailbox identifier format that should only be
|
|
|
|
interpreted by app_voicemail.
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* The voicemail.conf configuration file now has an 'alias' configuration
|
|
|
|
parameter for use with the Directory application. The voicemail realtime
|
|
|
|
database table schema has also been updated with an 'alias' column.
|
2013-08-01 17:07:52 +00:00
|
|
|
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
Codecs
|
2013-06-17 03:00:38 +00:00
|
|
|
------------------
|
2013-08-28 20:49:02 +00:00
|
|
|
* Pass through support has been added for both VP8 and Opus.
|
2013-01-15 23:54:34 +00:00
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* Added format attribute negotiation for the Opus codec. Format attribute
|
|
|
|
negotiation is provided by the res_format_attr_opus module.
|
|
|
|
|
|
|
|
|
|
|
|
Core
|
|
|
|
------------------
|
|
|
|
* Masquerades as an operation inside Asterisk have been effectively hidden
|
|
|
|
by the migration to the Bridging API. As such, many 'quirks' of Asterisk
|
|
|
|
no longer occur. This includes renaming of channels, "<ZOMBIE>" channels,
|
|
|
|
dropping of frame/audio hooks, and other internal implementation details
|
|
|
|
that users had to deal with. This fundamental change has large implications
|
|
|
|
throughout the changes documented for this version. For more information
|
|
|
|
about the new core architecture of Asterisk, please see the Asterisk wiki.
|
|
|
|
|
|
|
|
* Multiple parties in a bridge may now be transferred. If a participant in a
|
|
|
|
multi-party bridge initiates a blind transfer, a Local channel will be used
|
|
|
|
to execute the dialplan location that the transferer sent the parties to. If
|
|
|
|
a participant in a multi-party bridge initiates an attended transfer,
|
|
|
|
several options are possible. If the attended transfer results in a transfer
|
|
|
|
to an application, a Local channel is used. If the attended transfer results
|
|
|
|
in a transfer to another channel, the resulting channels will be merged into
|
|
|
|
a single bridge.
|
2013-06-17 14:31:51 +00:00
|
|
|
|
|
|
|
* The channel variable ATTENDED_TRANSFER_COMPLETE_SOUND is no longer channel
|
|
|
|
driver specific. If the channel variable is set on the transferrer channel,
|
|
|
|
the sound will be played to the target of an attended transfer.
|
|
|
|
|
|
|
|
* The channel variable BRIDGEPEER becomes a comma separated list of peers in
|
|
|
|
a multi-party bridge. The BRIDGEPEER value can have a maximum of 10 peers
|
|
|
|
listed. Any more peers in the bridge will not be included in the list.
|
|
|
|
BRIDGEPEER is not valid in holding bridges like parking since those channels
|
|
|
|
do not talk to each other even though they are in a bridge.
|
|
|
|
|
|
|
|
* The channel variable BRIDGEPVTCALLID is only valid for two party bridges
|
|
|
|
and will contain a value if the BRIDGEPEER's channel driver supports it.
|
|
|
|
|
2013-07-04 18:46:56 +00:00
|
|
|
* A channel variable ATTENDEDTRANSFER is now set which indicates which channel
|
|
|
|
was responsible for an attended transfer in a similar fashion to
|
|
|
|
BLINDTRANSFER.
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* Modules using the Configuration Framework or Sorcery must have XML
|
|
|
|
configuration documentation. This configuration documentation is included
|
|
|
|
with the rest of Asterisk's XML documentation, and is accessible via CLI
|
|
|
|
commands. See the CLI changes for more information.
|
2013-08-23 15:49:50 +00:00
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
AMI (Asterisk Manager Interface)
|
2013-08-23 15:49:50 +00:00
|
|
|
------------------
|
2013-08-28 20:49:02 +00:00
|
|
|
* Major changes were made to both the syntax as well as the semantics of the
|
|
|
|
AMI protocol. In particular, AMI events have been substantially improved
|
|
|
|
in this version of Asterisk. For more information, please see the AMI
|
|
|
|
specification at https://wiki.asterisk.org/wiki/x/dAFRAQ
|
|
|
|
|
|
|
|
* AMI events that reference a particular channel or bridge will now always
|
|
|
|
contain a standard set of fields. When multiple channels or bridges are
|
|
|
|
referenced in an event, fields for at least some subset of the channels
|
|
|
|
and bridges in the event will be prefixed with a descriptive name to avoid
|
|
|
|
name collisions. See the AMI event documentation on the Asterisk wiki for
|
|
|
|
more information.
|
2013-08-23 15:49:50 +00:00
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* The CLI command 'manager show commands' no longer truncates command names
|
|
|
|
longer than 15 characters and no longer shows authorization requirement
|
|
|
|
for commands. 'manager show command' now displays the privileges needed
|
|
|
|
for using a given manager command instead.
|
2013-08-23 15:49:50 +00:00
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* The SIPshowpeer action will now include a 'SubscribeContext' field for a
|
|
|
|
peer in its response if the peer has a subscribe context set.
|
2012-11-13 19:42:13 +00:00
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* The SIPqualifypeer action now acknowledges the request once it has
|
|
|
|
established that the request is against a known peer. It also issues a new
|
|
|
|
event, 'SIPQualifyPeerDone', once the qualify action has been completed.
|
2012-09-11 14:43:41 +00:00
|
|
|
|
2012-09-28 03:06:53 +00:00
|
|
|
* The PlayDTMF action now supports an optional 'Duration' parameter. This
|
|
|
|
specifies the duration of the digit to be played, in milliseconds.
|
|
|
|
|
2012-09-27 17:02:13 +00:00
|
|
|
* Added VoicemailRefresh action to allow an external entity to trigger mailbox
|
|
|
|
updates when changes occur instead of requiring the use of pollmailboxes.
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* Added a new action 'ControlPlayback'. The ControlPlayback action allows an
|
|
|
|
AMI client to manipulate audio currently being played back on a channel. The
|
2013-01-22 15:16:20 +00:00
|
|
|
supported operations depend on the application being used to send audio to
|
|
|
|
the channel. When the audio playback was initiated using the ControlPlayback
|
|
|
|
application or CONTROL STREAM FILE AGI command, the audio can be paused,
|
|
|
|
stopped, restarted, reversed, or skipped forward. When initiated by other
|
|
|
|
mechanisms (such as the Playback application), the audio can be stopped,
|
|
|
|
reversed, or skipped forward.
|
|
|
|
|
2013-03-22 14:06:46 +00:00
|
|
|
* Channel related events now contain a snapshot of channel state, adding new
|
|
|
|
fields to many of these events.
|
|
|
|
|
|
|
|
* The AMI event 'Newexten' field 'Extension' is deprecated, and may be removed
|
|
|
|
in a future release. Please use the common 'Exten' field instead.
|
|
|
|
|
|
|
|
* The AMI event 'UserEvent' from app_userevent now contains the channel state
|
|
|
|
fields. The channel state fields will come before the body fields.
|
|
|
|
|
2013-05-21 18:00:22 +00:00
|
|
|
* The AMI events 'ParkedCall', 'ParkedCallTimeOut', 'ParkedCallGiveUp', and
|
|
|
|
'UnParkedCall' have changed significantly in the new res_parking module.
|
2013-07-04 18:46:56 +00:00
|
|
|
|
|
|
|
The 'Channel' and 'From' headers are gone. For the channel that was parked
|
|
|
|
or is coming out of parking, a 'Parkee' channel snapshot is issued and it
|
|
|
|
has a number of fields associated with it. The old 'Channel' header relayed
|
|
|
|
the same data as the new 'ParkeeChannel' header.
|
|
|
|
|
|
|
|
The 'From' field was ambiguous and changed meaning depending on the event.
|
|
|
|
for most of these, it was the name of the channel that parked the call
|
|
|
|
(the 'Parker'). There is no longer a header that provides this channel name,
|
|
|
|
however the 'ParkerDialString' will contain a dialstring to redial the
|
|
|
|
device that parked the call.
|
|
|
|
|
|
|
|
On UnParkedCall events, the 'From' header would instead represent the
|
|
|
|
channel responsible for retrieving the parkee. It receives a channel
|
|
|
|
snapshot labeled 'Retriever'. The 'from' field is is replaced with
|
|
|
|
'RetrieverChannel'.
|
|
|
|
|
|
|
|
Lastly, the 'Exten' field has been replaced with 'ParkingSpace'.
|
2013-05-21 18:00:22 +00:00
|
|
|
|
|
|
|
* The AMI event 'Parkinglot' (response to 'Parkinglots' command) in a similar
|
|
|
|
fashion has changed the field names 'StartExten' and 'StopExten' to
|
|
|
|
'StartSpace' and 'StopSpace' respectively.
|
|
|
|
|
2013-03-25 16:19:55 +00:00
|
|
|
* The deprecated use of | (pipe) as a separator in the channelvars setting in
|
|
|
|
manager.conf has been removed.
|
|
|
|
|
2013-04-08 14:26:37 +00:00
|
|
|
* Channel Variables conveyed with a channel no longer contain the name of the
|
|
|
|
channel as part of the key field, i.e., ChanVariable(SIP/foo): bar=baz is now
|
|
|
|
ChanVariable: bar=baz. When multiple channels are present in a single AMI
|
|
|
|
event, the various ChanVariable fields will contain a suffix that specifies
|
|
|
|
which channel they correspond to.
|
|
|
|
|
2013-07-02 22:01:23 +00:00
|
|
|
* The NewPeerAccount AMI event is no longer raised. The NewAccountCode AMI
|
|
|
|
event always conveys the AMI event for a particular channel.
|
2013-06-17 03:00:38 +00:00
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* All 'Reload' events have been consolidated into a single event type. This
|
2013-05-24 20:44:07 +00:00
|
|
|
event will always contain a Module field specifying the name of the module
|
|
|
|
and a Status field denoting the result of the reload. All modules now issue
|
|
|
|
this event when being reloaded.
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* The 'ModuleLoadReport' event has been removed. Most AMI connections would
|
2013-05-24 20:44:07 +00:00
|
|
|
fail to receive this event due to being connected after modules have loaded.
|
|
|
|
AMI connections that want to know when Asterisk is ready should listen for
|
2013-08-28 20:49:02 +00:00
|
|
|
the 'FullyBooted' event.
|
2013-05-24 20:44:07 +00:00
|
|
|
|
|
|
|
* app_fax now sends the same send fax/receive fax events as res_fax. The
|
2013-08-28 20:49:02 +00:00
|
|
|
'FaxSent' event is now the 'SendFAX' event, and the 'FaxReceived' event is
|
|
|
|
now the 'ReceiveFAX' event.
|
2013-05-24 20:44:07 +00:00
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* The 'MusicOnHold' event is now two events: 'MusicOnHoldStart' and
|
|
|
|
'MusicOnHoldStop'. The sub type field has been removed.
|
2013-05-24 20:44:07 +00:00
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* The 'JabberEvent' event has been removed. It is not AMI's purpose to be a
|
2013-05-24 20:44:07 +00:00
|
|
|
carrier for another protocol.
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* The Bridge Manager action's 'Playtone' header now accepts more fine-grained
|
|
|
|
options. 'Channel1' and 'Channel2' may be specified in order to play a tone
|
|
|
|
to the specific channel. 'Both' may be specified to play a tone to both
|
|
|
|
channels. The old 'yes' option is still accepted as a way of playing the
|
2013-05-28 14:45:31 +00:00
|
|
|
tone to Channel2 only.
|
|
|
|
|
2013-05-21 18:00:22 +00:00
|
|
|
* The AMI 'Status' response event to the AMI Status action replaces the
|
2013-08-28 20:49:02 +00:00
|
|
|
'BridgedChannel' and 'BridgedUniqueid' headers with the 'BridgeID' header to
|
2013-05-21 18:00:22 +00:00
|
|
|
indicate what bridge the channel is currently in.
|
|
|
|
|
2013-05-24 21:21:25 +00:00
|
|
|
* The AMI 'Hold' event has been moved out of individual channel drivers, into
|
2013-08-28 20:49:02 +00:00
|
|
|
core, and is now two events: 'Hold' and 'Unhold'. The status field has been
|
2013-05-24 21:21:25 +00:00
|
|
|
removed.
|
|
|
|
|
2013-06-07 19:51:19 +00:00
|
|
|
* The AMI events in app_queue have been made more consistent with each other.
|
|
|
|
Events that reference channels (QueueCaller* and Agent*) will show
|
2013-08-28 20:49:02 +00:00
|
|
|
information about each channel. The (infamous) 'Join' and 'Leave' AMI
|
|
|
|
events have been changed to 'QueueCallerJoin' and 'QueueCallerLeave'.
|
2013-06-07 19:51:19 +00:00
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* The 'MCID' AMI event now publishes a channel snapshot when available and
|
2013-07-01 13:16:09 +00:00
|
|
|
its non-channel-snapshot parameters now use either the "MCallerID" or
|
2013-08-28 20:49:02 +00:00
|
|
|
'MConnectedID' prefixes with Subaddr*, Name*, and Num* suffixes instead
|
|
|
|
of 'CallerID' and 'ConnectedID' to avoid confusion with similarly named
|
2013-07-01 13:16:09 +00:00
|
|
|
parameters in the channel snapshot.
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* The AMI events 'Agentlogin' and 'Agentlogoff' have been renamed
|
|
|
|
'AgentLogin' and 'AgentLogoff' respectively.
|
2013-07-01 13:16:09 +00:00
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* The 'Channel' key used in the 'AlarmClear', 'Alarm', and 'DNDState' has been
|
2013-07-01 13:16:09 +00:00
|
|
|
renamed "DAHDIChannel" since it does not convey an Asterisk channel name.
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* 'ChannelUpdate' events have been removed.
|
2013-07-01 13:16:09 +00:00
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* All AMI events now contain a 'SystemName' field, if available.
|
2013-07-02 22:01:23 +00:00
|
|
|
|
2013-07-08 14:26:40 +00:00
|
|
|
* Local channel optimization is now conveyed in two events:
|
2013-08-28 20:49:02 +00:00
|
|
|
'LocalOptimizationBegin' and 'LocalOptimizationEnd'. The Begin event is sent
|
2013-07-08 14:26:40 +00:00
|
|
|
when the Local channel driver begins attempting to optimize itself out of
|
|
|
|
the media path; the End event is sent after the channel halves have
|
|
|
|
successfully optimized themselves out of the media path.
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* Local channel information in events is now prefixed with 'LocalOne' and
|
|
|
|
'LocalTwo'. This replaces the suffix of '1' and '2' for the two halves of
|
|
|
|
the Local channel. This affects the 'LocalBridge', 'LocalOptimizationBegin',
|
|
|
|
and 'LocalOptimizationEnd' events.
|
2013-07-08 14:26:40 +00:00
|
|
|
|
2013-07-21 02:11:49 +00:00
|
|
|
* The option 'allowmultiplelogin' can now be set or overriden in a particular
|
|
|
|
account. When set in the general context, it will act as the default
|
|
|
|
setting for defined accounts.
|
|
|
|
|
2013-08-02 02:32:44 +00:00
|
|
|
* The 'BridgeAction' event was removed. It technically added no value, as the
|
|
|
|
Bridge Action already receives confirmation of the bridge through a
|
|
|
|
successful completion Event.
|
|
|
|
|
|
|
|
* The 'BridgeExec' events were removed. These events duplicated the events that
|
|
|
|
occur in the Briding API, and are conveyed now through BridgeCreate,
|
|
|
|
BridgeEnter, and BridgeLeave events.
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* The 'RTCPSent'/'RTCPReceived' events have been significantly modified from
|
|
|
|
previous versions. They now report all SR/RR packets sent/received, and
|
|
|
|
have been restructured to better reflect the data sent in a SR/RR. In
|
|
|
|
particular, the event structure now supports multiple report blocks.
|
2013-08-02 02:32:44 +00:00
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* Added 'BlindTransfer' and 'AttendedTransfer' events. These events are
|
|
|
|
raised when a blind transfer/attended transfer completes successfully.
|
|
|
|
They contain information about the transfer that just completed, including
|
|
|
|
the location of the transfered channel.
|
2013-08-22 22:33:48 +00:00
|
|
|
|
2013-11-08 19:33:48 +00:00
|
|
|
* Added a 'security' class to AMI which outputs the required fields for
|
|
|
|
security messages similar to the log messages from res_security_log
|
|
|
|
|
2014-01-27 22:54:22 +00:00
|
|
|
* The AMI event 'ExtensionStatus' now contains a 'StatusText' field
|
|
|
|
that describes the status value in a human readable string.
|
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
CDR (Call Detail Records)
|
2013-01-15 23:54:34 +00:00
|
|
|
------------------
|
2013-08-28 20:49:02 +00:00
|
|
|
* Significant changes have been made to the behavior of CDRs. The CDR engine
|
|
|
|
was effectively rewritten and built on the Stasis message bus. For a full
|
2013-06-17 03:00:38 +00:00
|
|
|
definition of CDR behavior in Asterisk 12, please read the specification
|
|
|
|
on the Asterisk wiki (wiki.asterisk.org).
|
2013-05-21 18:00:22 +00:00
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
* CDRs will now be created between all participants in a bridge. For each
|
|
|
|
pair of channels in a bridge, a CDR is created to represent the path of
|
|
|
|
communication between those two endpoints. This lets an end user choose who
|
Handle hangup logic in the Stasis message bus and consumers of Stasis messages
This patch does the following:
* It adds a new soft hangup flag AST_SOFTHANGUP_HANGUP_EXEC that is set when a
channel is executing dialplan hangup logic, i.e., the 'h' extension or a
hangup handler. Stasis messages now also convey the soft hangup flag so
consumers of the messages can know when a channel is executing said
hangup logic.
* It adds a new channel flag, AST_FLAG_DEAD, which is set when a channel is
well and truly dead. Not just a zombie, but dead, Jim. Manager, CEL, CDRs,
and other consumers of Stasis have been updated to look for this flag to
know when the channel should by lying six feet under.
* The CDR engine has been updated to better handle a channel entering and
leaving a bridge. Previously, a new CDR was automatically created when a
channel left a bridge and put into the 'Pending' state; however, this
way of handling CDRs made it difficult for the 'endbeforehexten' logic to
work correctly - there was always a new CDR waiting in the hangup logic
and, even if 'ended', wouldn't be the CDR people wanted to inspect in the
hangup routine. This patch completely removes the Pending state and instead
defers creation of the new CDR until it gets a new message that requires
a new CDR.
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@393777 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2013-07-07 20:34:38 +00:00
|
|
|
to bill for what during bridge operations with multiple parties.
|
|
|
|
|
|
|
|
* The duration, billsec, start, answer, and end times now reflect the times
|
|
|
|
associated with the current CDR for the channel, as opposed to a cumulative
|
|
|
|
measurement of all CDRs for that channel.
|
2013-05-21 18:00:22 +00:00
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
* When a CDR is dispatched, user defined CDR variables from both parties are
|
|
|
|
included in the resulting CDR. If both parties have the same variable, only
|
|
|
|
the Party A value is provided.
|
2013-01-15 23:54:34 +00:00
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* Added a new option to cdr.conf, 'debug'. When enabled, significantly more
|
|
|
|
information regarding the CDR engine is logged as verbose messages. This
|
|
|
|
option should only be used if the behavior of the CDR engine needs to be
|
|
|
|
debugged.
|
|
|
|
|
|
|
|
* Added CLI command 'cdr set debug {on|off}'. This toggles the 'debug' setting
|
|
|
|
normally configured in cdr.conf.
|
|
|
|
|
|
|
|
* Added CLI command 'cdr show active {channel}'. When {channel} is not
|
|
|
|
specified, this command provides a summary of the channels with CDR
|
|
|
|
information and their statistics. When {channel} is specified, it shows
|
|
|
|
detailed information about all records associated with {channel}.
|
|
|
|
|
2013-07-20 13:10:22 +00:00
|
|
|
CEL (Channel Event Logging)
|
|
|
|
------------------
|
2013-08-28 20:49:02 +00:00
|
|
|
* CEL has undergone significant rework in Asterisk 12, and is now built on the
|
|
|
|
Stasis message bus. Please see the specification for CEL on the Asterisk
|
|
|
|
wiki at https://wiki.asterisk.org/wiki/x/4ICLAQ for more detailed
|
|
|
|
information.
|
|
|
|
|
2013-07-20 13:10:22 +00:00
|
|
|
* The 'extra' field of all CEL events that use it now consists of a JSON blob
|
|
|
|
with key/value pairs which are defined in the Asterisk 12 CEL documentation.
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* BLINDTRANSFER events now report the transferee bridge unique
|
2013-07-20 13:10:22 +00:00
|
|
|
identifier, extension, and context in a JSON blob as the extra string
|
|
|
|
instead of the transferee channel name as the peer.
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* ATTENDEDTRANSFER events now report the peer as NULL and additional
|
2013-07-20 13:10:22 +00:00
|
|
|
information in the 'extra' string as a JSON blob. For transfers that occur
|
|
|
|
between two bridged channels, the 'extra' JSON blob contains the primary
|
|
|
|
bridge unique identifier, the secondary channel name, and the secondary
|
|
|
|
bridge unique identifier. For transfers that occur between a bridged channel
|
|
|
|
and a channel running an app, the 'extra' JSON blob contains the primary
|
|
|
|
bridge unique identifier, the secondary channel name, and the app name.
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* LOCAL_OPTIMIZE events have been added to convey local channel
|
2013-07-20 13:25:05 +00:00
|
|
|
optimizations with the record occurring for the semi-one channel and
|
|
|
|
the semi-two channel name in the peer field.
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* BRIDGE_START, BRIDGE_END, BRIDGE_UPDATE, 3WAY_START, 3WAY_END, CONF_ENTER,
|
|
|
|
CONF_EXIT, CONF_START, and CONF_END events have all been removed. These
|
|
|
|
events have been replaced by BRIDGE_ENTER/BRIDGE_EXIT. The BRIDGE_ENTER
|
|
|
|
and BRIDGE_EXIT events are raised when a channel enters/exits any bridge,
|
|
|
|
regardless of whether or not that bridge happens to contain multiple
|
|
|
|
parties.
|
|
|
|
|
|
|
|
CLI
|
|
|
|
-------------------
|
|
|
|
* When compiled with '--enable-dev-mode', the astobj2 library will now add
|
|
|
|
several CLI commands that allow for inspection of ao2 containers that
|
|
|
|
register themselves with astobj2. The CLI commands are 'astobj2 container
|
|
|
|
dump', 'astobj2 container stats', and 'astobj2 container check'.
|
|
|
|
|
|
|
|
* Added specific CLI commands for bridge inspection. This includes 'bridge
|
|
|
|
show all', which lists all bridges in the system, and 'bridge show {id}',
|
|
|
|
which provides specific information about a bridge.
|
|
|
|
|
|
|
|
* Added CLI command 'bridge destroy'. This will destroy the specified bridge,
|
|
|
|
ejecting the channels currently in the bridge. If the channels cannot
|
|
|
|
continue in the dialplan or application that put them in the bridge, they
|
|
|
|
will be hung up.
|
|
|
|
|
|
|
|
* Added command 'bridge kick'. This will eject a single channel from a bridge.
|
|
|
|
|
|
|
|
* Added commands to inspect and manipulate the registered bridge technologies.
|
|
|
|
This include 'bridge technology show', which lists the registered bridge
|
|
|
|
technologies, as well as 'bridge technology {suspend|unsuspend} {tech}',
|
|
|
|
which controls whether or not a registered bridge technology can be used
|
|
|
|
during smart bridge operations. If a technology is suspended, it will not
|
|
|
|
be used when a bridge technology is picked for channels; when unsuspended,
|
|
|
|
it can be used again.
|
|
|
|
|
|
|
|
* The command 'config show help {module} {type} {option}' will show
|
|
|
|
configuration documentation for modules with XML configuration
|
|
|
|
documentation. When {module}, {type}, and {option} are omitted, a listing
|
|
|
|
of all modules with registered documentation is displayed. When {module}
|
|
|
|
is specified, a listing of all configuration types for that module is
|
|
|
|
displayed, along with their synopsis. When {module} and {type} are
|
|
|
|
specified, a listing of all configuration options for that type are
|
|
|
|
displayed along with their synopsis. When {module}, {type}, and {option}
|
|
|
|
are specified, detailed information for that configuration option is
|
|
|
|
displayed.
|
|
|
|
|
|
|
|
* Added 'core show sounds' and 'core show sound' CLI commands. These display
|
|
|
|
a listing of all installed media sounds available on the system and
|
|
|
|
detailed information about a sound, respectively.
|
|
|
|
|
|
|
|
* 'xmldoc dump' has been added. This CLI command will dump the XML
|
|
|
|
documentation DOM as a string to the specified file. The Asterisk core
|
|
|
|
will populate certain XML elements pulled from the source files with
|
|
|
|
additional run-time information; this command lets a user produce the
|
|
|
|
XML documentation with all information.
|
|
|
|
|
2012-12-14 22:34:18 +00:00
|
|
|
Features
|
|
|
|
-------------------
|
2013-08-28 20:49:02 +00:00
|
|
|
* Parking has been pulled from core and placed into a separate module called
|
|
|
|
res_parking. See Parking changes below for more details. Configuration for
|
|
|
|
parking should now be performed in res_parking.conf. Configuration for
|
|
|
|
parking in features.conf is now unsupported.
|
|
|
|
|
|
|
|
* Core attended transfers now have several new options. While performing an
|
|
|
|
attended transfer, the transferer now has the following options:
|
|
|
|
- *1 - cancel the attended transfer (configurable via atxferabort)
|
|
|
|
- *2 - complete the attended transfer, dropping out of the call
|
|
|
|
(configurable via atxfercomplete)
|
|
|
|
- *3 - complete the attended transfer, but stay in the call. This will turn
|
|
|
|
the call into a multi-party bridge (configurable via atxferthreeway)
|
|
|
|
- *4 - swap to the other party. Once an attended transfer has begun, this
|
|
|
|
options may be used multiple times (configurable via atxferswap)
|
|
|
|
|
|
|
|
* For DTMF blind and attended transfers, the channel variable TRANSFER_CONTEXT
|
|
|
|
must be on the channel initiating the transfer to have any effect.
|
|
|
|
|
2012-12-14 22:34:18 +00:00
|
|
|
* The BRIDGE_FEATURES channel variable would previously only set features for
|
|
|
|
the calling party and would set this feature regardless of whether the
|
|
|
|
feature was in caps or in lowercase. Use of a caps feature for a letter
|
|
|
|
will now apply the feature to the calling party while use of a lowercase
|
|
|
|
letter will apply that feature to the called party.
|
|
|
|
|
2013-07-01 16:01:24 +00:00
|
|
|
* Add support for automixmon to the BRIDGE_FEATURES channel variable.
|
2012-12-14 22:34:18 +00:00
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* The channel variable DYNAMIC_PEERNAME is redundant with BRIDGEPEER and is
|
|
|
|
removed. The more useful DYNAMIC_WHO_ACTIVATED gives the channel name that
|
|
|
|
activated the dynamic feature.
|
|
|
|
|
|
|
|
* The channel variables DYNAMIC_FEATURENAME and DYNAMIC_WHO_ACTIVATED are set
|
|
|
|
only on the channel executing the dynamic feature. Executing a dynamic
|
|
|
|
feature on the bridge peer in a multi-party bridge will execute it on all
|
|
|
|
peers of the activating channel.
|
2013-02-08 17:36:23 +00:00
|
|
|
|
2013-04-09 06:16:42 +00:00
|
|
|
* You can now have the settings for a channel updated using the FEATURE()
|
|
|
|
and FEATUREMAP() functions inherited to child channels by setting
|
|
|
|
FEATURE(inherit)=yes.
|
|
|
|
|
2013-07-01 16:01:24 +00:00
|
|
|
* automixmon now supports additional channel variables from automon including:
|
|
|
|
TOUCH_MIXMONITOR_PREFIX, TOUCH_MIXMONITOR_MESSAGE_START,
|
|
|
|
and TOUCH_MIXMONITOR_MESSAGE_STOP
|
|
|
|
|
|
|
|
* A new general features.conf option 'recordingfailsound' has been added which
|
|
|
|
allowssetting a failure sound for a user tries to invoke a recording feature
|
|
|
|
such as automon or automixmon and it fails.
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* It is no longer necessary (or possible) to define the ATXFER_NULL_TECH in
|
|
|
|
features.c for atxferdropcall=no to work properly. This option now just
|
|
|
|
works.
|
2012-09-04 19:26:02 +00:00
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
Logging
|
2013-05-21 18:00:22 +00:00
|
|
|
-------------------
|
2013-08-28 20:49:02 +00:00
|
|
|
* Added log rotation strategy 'none'. If set, no log rotation strategy will
|
|
|
|
be used. Given that this can cause the Asterisk log files to grow quickly,
|
|
|
|
this option should only be used if an external mechanism for log management
|
|
|
|
is preferred.
|
2013-06-17 14:31:51 +00:00
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
Realtime
|
|
|
|
------------------
|
|
|
|
* Dynamic realtime tables for SIP Users can now include a 'path' field. This
|
|
|
|
will store the path information for that peer when it registers. Realtime
|
|
|
|
tables can also use the 'supportpath' field to enable Path header support.
|
2013-06-07 16:07:18 +00:00
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
* LDAP realtime configurations for SIP Users now have the AstAccountPathSupport
|
|
|
|
objectIdentifier. This maps to the supportpath option in sip.conf.
|
2012-09-19 22:33:12 +00:00
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
Sorcery
|
|
|
|
------------------
|
2013-08-28 20:49:02 +00:00
|
|
|
* Sorcery is a new data abstraction and object persistence API in Asterisk. It
|
|
|
|
provides modules a useful abstraction on top of the many storage mechanisms
|
|
|
|
in Asterisk, including the Asterisk Database, static configuration files,
|
|
|
|
static Realtime, and dynamic Realtime. It also provides a caching service.
|
|
|
|
Users can configure a hierarchy of data storage layers for specific modules
|
|
|
|
in sorcery.conf.
|
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
* All future modules which utilize Sorcery for object persistence must have a
|
|
|
|
column named "id" within their schema when using the Sorcery realtime module.
|
|
|
|
This column must be able to contain a string of up to 128 characters in length.
|
2013-06-07 19:51:19 +00:00
|
|
|
|
2013-06-17 14:31:51 +00:00
|
|
|
Security Events Framework
|
2013-08-28 20:49:02 +00:00
|
|
|
------------------
|
|
|
|
* Security Event timestamps now use ISO 8601 formatted date/time instead of
|
|
|
|
the "seconds-microseconds" format that it was using previously.
|
|
|
|
|
|
|
|
Stasis Message Bus
|
|
|
|
------------------
|
|
|
|
* The Stasis message bus is a publish/subscribe message bus internal to
|
|
|
|
Asterisk. Many services in Asterisk are built on the Stasis message bus,
|
|
|
|
including AMI, ARI, CDRs, and CEL. Parameters controlling the operation of
|
|
|
|
Stasis can be configured in stasis.conf. Note that these parameters operate
|
|
|
|
at a very low level in Asterisk, and generally will not require changes.
|
2013-06-17 14:31:51 +00:00
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
Channel Drivers
|
2012-09-25 19:29:14 +00:00
|
|
|
------------------
|
2013-06-17 03:00:38 +00:00
|
|
|
* When a channel driver is configured to enable jiterbuffers, they are now
|
|
|
|
applied unconditionally when a channel joins a bridge. If a jitterbuffer
|
|
|
|
is already set for that channel when it enters, such as by the JITTERBUFFER
|
|
|
|
function, then the existing jitterbuffer will be used and the one set by
|
|
|
|
the channel driver will not be applied.
|
2012-09-25 19:29:14 +00:00
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
chan_agent
|
|
|
|
------------------
|
2013-08-28 20:49:02 +00:00
|
|
|
* chan_agent has been removed and replaced with AgentLogin and AgentRequest
|
|
|
|
dialplan applications provided by the app_agent_pool module. Agents are
|
|
|
|
connected with callers using the new AgentRequest dialplan application.
|
|
|
|
The Agents:<agent-id> device state is available to monitor the status of an
|
|
|
|
agent. See agents.conf.sample for valid configuration options.
|
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
* The updatecdr option has been removed. Altering the names of channels on a
|
|
|
|
CDR is not supported - the name of the channel is the name of the channel,
|
2013-08-28 20:49:02 +00:00
|
|
|
and pretending otherwise helps no one. The AGENTUPDATECDR channel variable
|
|
|
|
has also been removed, for the same reason.
|
|
|
|
|
Replace chan_agent with app_agent_pool.
The ill conceived chan_agent is no more. It is now replaced by
app_agent_pool.
Agents login using the AgentLogin() application as before. The
AgentLogin() application no longer does any authentication.
Authentication is now the responsibility of the dialplan. (Besides, the
authentication done by chan_agent did not match what the voice prompts
asked for.)
Sample extensions.conf
[login]
; Sample agent 1001 login
; Set COLP for in between calls so the agent does not see the last caller COLP.
exten => 1001,1,Set(CONNECTEDLINE(all)="Agent Waiting" <1001>)
; Give the agent DTMF transfer and disconnect features when connected to a caller.
same => n,Set(CHANNEL(dtmf-features)=TX)
same => n,AgentLogin(1001)
same => n,NoOp(AGENT_STATUS is ${AGENT_STATUS})
same => n,Hangup()
[caller]
; Sample caller direct connect to agent 1001
exten => 800,1,AgentRequest(1001)
same => n,NoOp(AGENT_STATUS is ${AGENT_STATUS})
same => n,Hangup()
; Sample caller going through a Queue to agent 1001
exten => 900,1,Queue(agent_q)
same => n,Hangup()
Sample queues.conf
[agent_q]
member => Local/800@caller,,SuperAgent,Agent:1001
Under the hood operation overview:
1) Logged in agents wait for callers in an agents holding bridge.
2) Caller requests an agent using AgentRequest()
3) A basic bridge is created, the agent is notified, and caller joins the
basic bridge to wait for the agent.
4) The agent is either automatically connected to the caller or must ack
the call to connect.
5) The agent is moved from the agents holding bridge to the basic bridge.
6) The agent and caller talk.
7) The connection is ended by either party.
8) The agent goes back to the agents holding bridge.
To avoid some locking issues with the agent holding bridge, I needed to
make some changes to the after bridge callback support. The after bridge
callback is now a list of requested callbacks with the last to be added
the only active callback. The after bridge callback for failed callbacks
will always happen in the channel thread when the channel leaves the
bridging system or is destroyed.
(closes issue ASTERISK-21554)
Reported by: Matt Jordan
Review: https://reviewboard.asterisk.org/r/2657/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@394417 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2013-07-15 23:20:55 +00:00
|
|
|
* The endcall and enddtmf configuration options are removed. Use the
|
|
|
|
dialplan function CHANNEL(dtmf-features) to set DTMF features on the agent
|
|
|
|
channel before calling AgentLogin.
|
|
|
|
|
|
|
|
chan_bridge
|
|
|
|
------------------
|
2013-08-28 20:49:02 +00:00
|
|
|
* chan_bridge has been removed. Its functionality has been incorporated
|
|
|
|
directly into the ConfBridge application itself.
|
|
|
|
|
|
|
|
chan_dahdi
|
|
|
|
------------------
|
|
|
|
* Added the CLI command 'pri destroy span'. This will destroy the D-channel
|
|
|
|
of the specified span and its B-channels. Note that this command should
|
|
|
|
only be used if you understand the risks it entails.
|
|
|
|
|
|
|
|
* The CLI command 'dahdi destroy channel' is now 'dahdi destroy channels'.
|
|
|
|
A range of channels can be specified to be destroyed. Note that this command
|
|
|
|
should only be used if you understand the risks it entails.
|
|
|
|
|
|
|
|
* Added the CLI command 'dahdi create channels'. A range of channels can be
|
|
|
|
specified to be created, or the keyword 'new' can be used to add channels
|
|
|
|
not yet created.
|
2013-06-06 22:46:54 +00:00
|
|
|
|
2013-12-19 18:16:41 +00:00
|
|
|
* The script specified by the chan_dahdi.conf mwimonitornotify option now gets
|
|
|
|
the exact configured mailbox name. For app_voicemail mailboxes this is
|
|
|
|
mailbox@context.
|
|
|
|
|
2013-12-19 16:52:43 +00:00
|
|
|
* Added mwi_vm_boxes that also must be configured for ISDN MWI to be enabled.
|
|
|
|
|
2013-10-04 21:41:58 +00:00
|
|
|
chan_iax2
|
|
|
|
------------------
|
|
|
|
* IPv6 support has been added. We are now able to bind to and
|
|
|
|
communicate using IPv6 addresses.
|
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
chan_local
|
|
|
|
------------------
|
2013-08-28 20:49:02 +00:00
|
|
|
* The /b option has been removed.
|
2013-06-06 22:46:54 +00:00
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
* chan_local moved into the system core and is no longer a loadable module.
|
2013-06-06 22:46:54 +00:00
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
chan_mobile
|
|
|
|
------------------
|
|
|
|
* Added general support for busy detection.
|
2013-06-06 22:46:54 +00:00
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
* Added ECAM command support for Sony Ericsson phones.
|
2013-06-06 22:46:54 +00:00
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
chan_pjsip
|
|
|
|
------------------
|
|
|
|
* A new SIP channel driver for Asterisk, chan_pjsip is built on the PJSIP
|
|
|
|
SIP stack. A collection of resource modules provides the bulk of the SIP
|
|
|
|
functionality. For more information on the new SIP channel driver, see
|
|
|
|
https://wiki.asterisk.org/wiki/x/JYGLAQ
|
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
chan_sip
|
|
|
|
------------------
|
|
|
|
* Added support for RFC 3327 "Path" headers. This can be enabled in sip.conf
|
|
|
|
using the 'supportpath' setting, either on a global basis or on a peer basis.
|
|
|
|
This setting enables Asterisk to route outgoing out-of-dialog requests via a
|
|
|
|
set of proxies by using a pre-loaded route-set defined by the Path headers in
|
|
|
|
the REGISTER request. See Realtime updates for more configuration information.
|
2013-06-06 22:46:54 +00:00
|
|
|
|
2013-08-21 13:41:05 +00:00
|
|
|
* The SIP_CODEC family of variables may now specify more than one codec. Each
|
|
|
|
codec must be separated by a comma. The first codec specified is the
|
|
|
|
preferred codec for the offer. This allows a dialplan writer to specify both
|
|
|
|
audio and video codecs, e.g., Set(SIP_CODEC=ulaw,h264)
|
2013-06-17 03:00:38 +00:00
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
* The 'callevents' parameter has been removed. Hold AMI events are now raised
|
|
|
|
in the core, and can be filtered out using the 'eventfilter' parameter
|
|
|
|
in manager.conf.
|
|
|
|
|
|
|
|
* Added 'ignore_requested_pref'. When enabled, this will use the preferred
|
|
|
|
codecs configured for a peer instead of the requested codec.
|
|
|
|
|
2013-09-30 15:57:11 +00:00
|
|
|
* The option "register_retry_403" has been added to chan_sip to work around
|
|
|
|
servers that are known to erroneously send 403 in response to valid
|
|
|
|
REGISTER requests and allows Asterisk to continue attepmting to connect.
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
chan_skinny
|
|
|
|
------------------
|
|
|
|
* Added the 'immeddialkey' parameter. If set, when the user presses the
|
|
|
|
configured key the already entered number will be immediately dialed. This
|
|
|
|
is useful when the dialplan allows for variable length pattern matching.
|
|
|
|
Valid options are '*' and '#'.
|
|
|
|
|
|
|
|
* Added the 'callfwdtimeout' parameter. This configures the amount of time (in
|
|
|
|
milliseconds) before a call forward is considered to not be answered.
|
|
|
|
|
|
|
|
* The 'serviceurl' parameter allows Service URLs to be attached to line
|
|
|
|
buttons.
|
|
|
|
|
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
Functions
|
2013-03-05 13:14:43 +00:00
|
|
|
------------------
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
AGENT
|
2013-06-17 03:00:38 +00:00
|
|
|
------------------
|
2013-08-28 20:49:02 +00:00
|
|
|
* The password option has been disabled, as the AgentLogin application no
|
|
|
|
longer provides authentication.
|
|
|
|
|
|
|
|
AUDIOHOOK_INHERIT
|
|
|
|
------------------
|
|
|
|
* Due to changes in the Asterisk core, this function is no longer needed to
|
|
|
|
preserve a MixMonitor on a channel during transfer operations and dialplan
|
|
|
|
execution. It is effectively obsolete.
|
2013-06-17 03:00:38 +00:00
|
|
|
|
|
|
|
CDR (function)
|
|
|
|
------------------
|
|
|
|
* The 'amaflags' and 'accountcode' attributes for the CDR function are
|
|
|
|
deprecated. Use the CHANNEL function instead to access these attributes.
|
2013-08-28 20:49:02 +00:00
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
* The 'l' option has been removed. When reading a CDR attribute, the most
|
|
|
|
recent record is always used. When writing a CDR attribute, all non-finalized
|
|
|
|
CDRs are updated.
|
2013-08-28 20:49:02 +00:00
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
* The 'r' option has been removed, for the same reason as the 'l' option.
|
2013-08-28 20:49:02 +00:00
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
* The 's' option has been removed, as LOCKED semantics no longer exist in the
|
|
|
|
CDR engine.
|
|
|
|
|
|
|
|
CDR_PROP
|
|
|
|
------------------
|
|
|
|
* A new function CDR_PROP has been added. This function lets you set properties
|
|
|
|
on a channel's active CDRs. This function is write-only. Properties accept
|
|
|
|
boolean values to set/clear them on the channel's CDRs. Valid properties
|
|
|
|
include:
|
2013-08-28 20:49:02 +00:00
|
|
|
- 'party_a' - make this channel the preferred Party A in any CDR between two
|
2013-06-17 03:00:38 +00:00
|
|
|
channels. If two channels have this property set, the creation time of the
|
|
|
|
channel is used to determine who is Party A. Note that dialed channels are
|
|
|
|
never Party A in a CDR.
|
2013-08-28 20:49:02 +00:00
|
|
|
- 'disable' - disable CDRs on this channel. This is analogous to the NoCDR
|
2013-06-17 03:00:38 +00:00
|
|
|
application when set to True, and analogous to the 'e' option in ResetCDR
|
|
|
|
when set to False.
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
CHANNEL
|
|
|
|
------------------
|
|
|
|
* Added the argument 'dtmf_features'. This sets the DTMF features that will be
|
|
|
|
enabled on a channel when it enters a bridge. Allowed values are 'T', 'K',
|
|
|
|
'H', 'W', and 'X', and are analogous to the parameters passed to the Dial
|
|
|
|
application.
|
|
|
|
|
|
|
|
* Added the argument 'after_bridge_goto'. This can be set to a parseable Goto
|
|
|
|
string, i.e., [[context],extension],priority. If set on a channel, if a
|
|
|
|
channel leaves a bridge but is not hung up it will resume dialplan execution
|
|
|
|
at that location.
|
|
|
|
|
|
|
|
JITTERBUFFER
|
|
|
|
------------------
|
|
|
|
* JITTERBUFFER now accepts an argument of 'disabled' which can be used
|
|
|
|
to remove jitterbuffers previously set on a channel with JITTERBUFFER.
|
|
|
|
The value of this setting is ignored when disabled is used for the argument.
|
|
|
|
|
|
|
|
PJSIP_DIAL_CONTACTS
|
|
|
|
------------------
|
|
|
|
* A new function provided by chan_pjsip, this function can be used in
|
|
|
|
conjunction with the Dial application to construct a dial string that will
|
|
|
|
dial all contacts on an Address of Record associated with a chan_pjsip
|
|
|
|
endpoint.
|
|
|
|
|
|
|
|
PJSIP_MEDIA_OFFER
|
|
|
|
------------------
|
|
|
|
* Provided by chan_pjsip, this function sets the codecs to be offerred on the
|
|
|
|
outbound channel prior to dialing.
|
|
|
|
|
|
|
|
REDIRECTING
|
|
|
|
------------------
|
|
|
|
* Redirecting reasons can now be set to arbitrary strings. This means
|
|
|
|
that the REDIRECTING dialplan function can be used to set the redirecting
|
|
|
|
reason to any string. It also allows for custom strings to be read as the
|
|
|
|
redirecting reason from SIP Diversion headers.
|
|
|
|
|
|
|
|
SPEECH_ENGINE
|
|
|
|
------------------
|
|
|
|
* The SPEECH_ENGINE function now supports read operations. When read from, it
|
|
|
|
will return the current value of the requested attribute.
|
|
|
|
|
2013-12-19 16:52:43 +00:00
|
|
|
VMCOUNT:
|
|
|
|
------------------
|
|
|
|
* Mailboxes defined by app_voicemail MUST be referenced by the rest of the
|
|
|
|
system as mailbox@context. The rest of the system cannot add @default
|
|
|
|
to mailbox identifiers for app_voicemail that do not specify a context
|
|
|
|
any longer. It is a mailbox identifier format that should only be
|
|
|
|
interpreted by app_voicemail.
|
|
|
|
|
2013-06-17 03:00:38 +00:00
|
|
|
|
|
|
|
Resources
|
|
|
|
------------------
|
2013-03-05 13:14:43 +00:00
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
res_agi (Asterisk Gateway Interface)
|
|
|
|
------------------
|
|
|
|
* The manager event AGIExec has been split into AGIExecStart and AGIExecEnd.
|
|
|
|
|
|
|
|
* The manager event AsyncAGI has been split into AsyncAGIStart, AsyncAGIExec,
|
|
|
|
and AsyncAGIEnd.
|
|
|
|
|
|
|
|
* The CONTROL STREAM FILE command now accepts an offsetms parameter. This
|
|
|
|
will start the playback of the audio at the position specified. It will
|
|
|
|
also return the final position of the file in 'endpos'.
|
|
|
|
|
|
|
|
* The CONTROL STREAM FILE command will now populate the CPLAYBACKSTATUS
|
|
|
|
channel variable if the user stopped the file playback or if a remote
|
|
|
|
entity stopped the playback. If neither stopped the playback, it will
|
|
|
|
indicate the overall success/failure of the playback. If stopped early,
|
|
|
|
the final offset of the file will be set in the CPLAYBACKOFFSET channel
|
|
|
|
variable.
|
|
|
|
|
|
|
|
* The SAY ALPHA command now accepts an additional parameter to control
|
|
|
|
whether it specifies the case of uppercase, lowercase, or all letters to
|
|
|
|
provide functionality similar to SayAlphaCase.
|
|
|
|
|
|
|
|
res_ari (Asterisk RESTful Interface) (and others)
|
|
|
|
------------------
|
|
|
|
* The Asterisk RESTful Interface (ARI) provides a mechanism to expose and
|
|
|
|
control telephony primitives in Asterisk by remote client. This includes
|
|
|
|
channels, bridges, endpoints, media, and other fundamental concepts. Users
|
|
|
|
of ARI can develop their own communications applications, controlling
|
|
|
|
multiple channels using an HTTP RESTful interface and receiving JSON events
|
|
|
|
about the objects via a WebSocket connection. ARI can be configured in
|
|
|
|
Asterisk via ari.conf. For more information on ARI, see
|
|
|
|
https://wiki.asterisk.org/wiki/x/0YCLAQ
|
|
|
|
|
|
|
|
res_parking
|
|
|
|
-------------------
|
|
|
|
* Parking has been extracted from the Asterisk core as a loadable module,
|
|
|
|
res_parking. Configuration for parking is now provided by res_parking.conf.
|
|
|
|
Configuration through features.conf is no longer supported.
|
|
|
|
|
|
|
|
* res_parking uses the configuration framework. If an invalid configuration is
|
|
|
|
supplied, res_parking will fail to load or fail to reload. Previously,
|
|
|
|
invalid configurations would generally be accepted, with certain errors
|
|
|
|
resulting in individually disabled parking lots.
|
|
|
|
|
|
|
|
* Parked calls are now placed in bridges. While this is largely an
|
|
|
|
architectural change, it does have implications on how channels in a parking
|
|
|
|
lot are viewed. For example, commands that display channels in bridges will
|
|
|
|
now also display the channels in a parking lot.
|
|
|
|
|
|
|
|
* The order of arguments for the new parking applications have been modified.
|
|
|
|
Timeout and return context/exten/priority are now implemented as options,
|
|
|
|
while the name of the parking lot is now the first parameter. See the
|
|
|
|
application documentation for Park, ParkedCall, and ParkAndAnnounce for more
|
|
|
|
in-depth information as well as syntax.
|
|
|
|
|
|
|
|
* Extensions are by default no longer automatically created in the dialplan to
|
|
|
|
park calls or pickup parked calls. Generation of dialplan extensions can be
|
|
|
|
enabled using the 'parkext' configuration option.
|
|
|
|
|
|
|
|
* ADSI functionality for parking is no longer supported. The 'adsipark'
|
|
|
|
configuration option has been removed as a result.
|
|
|
|
|
|
|
|
* The PARKINGSLOT channel variable has been deprecated in favor of
|
|
|
|
PARKING_SPACE to match the naming scheme of the new system.
|
|
|
|
|
|
|
|
* PARKING_SPACE and PARKEDLOT channel variables will now be set for a parked
|
|
|
|
channel even when the configuration option 'comebactoorigin' is enabled.
|
|
|
|
|
|
|
|
* A new CLI command 'parking show' has been added. This allows a user to
|
|
|
|
inspect the parking lots that are currently in use.
|
|
|
|
'parking show <parkinglot>' will also show the parked calls in a specific
|
|
|
|
parking lot.
|
|
|
|
|
|
|
|
* The CLI command 'parkedcalls' is now deprecated in favor of
|
|
|
|
'parking show <parkinglot>'.
|
|
|
|
|
|
|
|
* The AMI command 'ParkedCalls' will now accept a 'ParkingLot' argument which
|
|
|
|
can be used to get a list of parked calls for a specific parking lot.
|
|
|
|
|
|
|
|
* The AMI command 'Park' field 'Channel2' has been deprecated and replaced
|
|
|
|
with 'TimeoutChannel'. If both 'Channel2' and 'TimeoutChannel' are
|
|
|
|
specified, 'TimeoutChannel' will be used. The field 'TimeoutChannel' is no
|
|
|
|
longer a required argument.
|
|
|
|
|
|
|
|
* The ParkAndAnnounce application is now provided through res_parking instead
|
|
|
|
of through the separate app_parkandannounce module.
|
|
|
|
|
|
|
|
* ParkAndAnnounce will no longer go to the next position in dialplan on timeout
|
|
|
|
by default. Instead, it will follow the timeout rules of the parking lot. The
|
|
|
|
old behavior can be reproduced by using the 'c' option.
|
|
|
|
|
|
|
|
* Dynamic parking lots will now fail to be created under the following
|
|
|
|
conditions:
|
|
|
|
- if the parking lot specified by PARKINGDYNAMIC does not exist
|
|
|
|
- if they require exclusive park and parkedcall extensions which overlap
|
|
|
|
with existing parking lots.
|
|
|
|
|
|
|
|
* Dynamic parking lots will be cleared on reload for dynamic parking lots that
|
|
|
|
currently contain no calls. Dynamic parking lots containing parked calls
|
|
|
|
will persist through the reloads without alteration.
|
|
|
|
|
|
|
|
* If 'parkext_exclusive' is set for a parking lot and that extension is
|
|
|
|
already in use when that parking lot tries to register it, this is now
|
|
|
|
considered a parking system configuration error. Configurations which do
|
|
|
|
this will be rejected.
|
|
|
|
|
|
|
|
* Added channel variable PARKER_FLAT. This contains the name of the extension
|
|
|
|
that would be used if 'comebacktoorigin' is enabled. This can be useful when
|
|
|
|
comebacktoorigin is disabled, but the dialplan or an external control
|
|
|
|
mechanism wants to use the extension in the park-dial context that was
|
|
|
|
generated to re-dial the parker on timeout.
|
|
|
|
|
|
|
|
res_pjsip (and many others)
|
|
|
|
------------------
|
|
|
|
* A large number of resource modules make up the SIP stack based on pjsip.
|
|
|
|
The chan_pjsip channel driver users these resource modules to provide
|
|
|
|
various SIP functionality in Asterisk. The majority of configuration for
|
|
|
|
these modules is performed in pjsip.conf. Other modules may use their
|
|
|
|
own configuration files.
|
|
|
|
|
2014-01-02 19:08:19 +00:00
|
|
|
* Added 'set_var' option for an endpoint. For each variable specified that
|
|
|
|
variable gets set upon creation of a channel involving the endpoint.
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
res_rtp_asterisk
|
2013-03-12 19:08:59 +00:00
|
|
|
------------------
|
|
|
|
* ICE/STUN/TURN support in res_rtp_asterisk has been made optional. To enable
|
2013-08-28 20:49:02 +00:00
|
|
|
them, an Asterisk-specific version of PJSIP needs to be installed.
|
2013-03-12 19:08:59 +00:00
|
|
|
Tarballs are available from https://github.com/asterisk/pjproject/tags/.
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
res_statsd/res_chan_stats
|
|
|
|
------------------
|
|
|
|
* A new resource module, res_statsd, has been added, which acts as a statsd
|
|
|
|
client. This module allows Asterisk to publish statistics to a statsd
|
|
|
|
server. In conjunction with res_chan_stats, it will publish statistics about
|
|
|
|
channels to the statsd server. It can be configured via res_statsd.conf.
|
|
|
|
|
|
|
|
res_xmpp
|
2013-03-16 15:40:31 +00:00
|
|
|
------------------
|
|
|
|
* Device state for XMPP buddies is now available using the following format:
|
|
|
|
XMPP/<client name>/<buddy address>
|
|
|
|
If any resource is available the device state is considered to be not in use.
|
|
|
|
If no resources exist or all are unavailable the device state is considered
|
|
|
|
to be unavailable.
|
|
|
|
|
2013-05-10 13:13:06 +00:00
|
|
|
|
2013-07-21 18:12:00 +00:00
|
|
|
Scripts
|
|
|
|
------------------
|
|
|
|
|
2013-08-28 20:55:53 +00:00
|
|
|
Realtime/Database Scripts
|
|
|
|
------------------
|
|
|
|
* Asterisk previously included example db schemas in the contrib/realtime/
|
|
|
|
directory of the source tree. This has been replaced by a set of database
|
2013-08-29 20:22:08 +00:00
|
|
|
migrations using the Alembic framework. This allows you to use alembic to
|
2013-08-28 20:55:53 +00:00
|
|
|
initialize the database for you. It will also serve as a database migration
|
|
|
|
tool when upgrading Asterisk in the future.
|
|
|
|
|
|
|
|
See contrib/ast-db-manage/README.md for more details.
|
|
|
|
|
2013-08-28 20:49:02 +00:00
|
|
|
sip_to_res_pjsip.py
|
|
|
|
-------------------
|
|
|
|
* A new script has been added in the contrib/scripts/sip_to_res_pjsip folder.
|
|
|
|
This python script will convert an existing sip.conf file to a
|
|
|
|
pjsip.conf file, for use with the chan_pjsip channel driver. This script
|
|
|
|
is meant to be an aid in converting an existing chan_sip configuration to
|
|
|
|
a chan_pjsip configuration, but it is expected that configuration beyond
|
|
|
|
what the script provides will be needed.
|
|
|
|
|
2011-08-10 15:45:57 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 10 to Asterisk 11 --------------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
2012-06-25 17:59:34 +00:00
|
|
|
Build System
|
2012-07-22 23:37:00 +00:00
|
|
|
-------------------
|
2012-01-30 21:21:16 +00:00
|
|
|
* The Asterisk build system will now build and install a shared library
|
|
|
|
(libasteriskssl.so) used to wrap various initialization and shutdown functions
|
|
|
|
from the libssl and libcrypto libraries provided by OpenSSL. This is done so
|
|
|
|
that Asterisk can ensure that these functions do *not* get called by any
|
|
|
|
modules that are loaded into Asterisk, since they should only be called once
|
|
|
|
in any single process. If desired, this feature can be disabled by supplying
|
|
|
|
the "--disable-asteriskssl" option to the configure script.
|
2012-01-16 19:49:50 +00:00
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
* A new make target, 'full', has been added to the Makefile. This performs
|
|
|
|
the same compilation actions as make all, but will also scan the entirety of
|
|
|
|
each source file for documentation. This option is needed to generate AMI
|
|
|
|
event documentation. Note that your system must have Python in order for
|
|
|
|
this make target to succeed.
|
|
|
|
|
|
|
|
* The optimization portion of the build system has been reworked to avoid
|
|
|
|
broken builds on certain architectures. All architecture-specific
|
|
|
|
optimization has been removed in favor of using -march=native to allow gcc
|
|
|
|
to detect the environment in which it is running when possible. This can
|
|
|
|
be toggled as BUILD_NATIVE under "Compiler Flags" in menuselect.
|
|
|
|
|
|
|
|
* BUILD_CFLAGS and BUILD_LDFLAGS can now be passed to menuselect, e.g.,
|
|
|
|
make BUILD_CFLAGS="whatever" BUILD_LDFLAGS="whatever"
|
|
|
|
|
|
|
|
* Remove "asterisk/version.h" in favor of "asterisk/ast_version.h". If you
|
|
|
|
previously parsed the header file to obtain the version of Asterisk, you
|
|
|
|
will now have to go through Asterisk to get the version information.
|
|
|
|
|
|
|
|
|
|
|
|
Applications
|
2012-01-23 18:16:20 +00:00
|
|
|
-------------------
|
2012-07-22 23:37:00 +00:00
|
|
|
|
|
|
|
Bridge
|
|
|
|
-------------------
|
|
|
|
* Added 'F()' option. Similar to the dial option, this can be supplied with
|
|
|
|
arguments indicating where the callee should go after the caller is hung up,
|
|
|
|
or without options specified, the priority after the Queue will be used.
|
|
|
|
|
2012-01-23 18:16:20 +00:00
|
|
|
|
2011-11-17 18:09:13 +00:00
|
|
|
ConfBridge
|
|
|
|
-------------------
|
|
|
|
* Added menu action admin_toggle_mute_participants. This will mute / unmute
|
2012-07-22 23:37:00 +00:00
|
|
|
all non-admin participants on a conference. The confbridge configuration
|
|
|
|
file also allows for the default sounds played to all conference users when
|
|
|
|
this occurs to be overriden using sound_participants_unmuted and
|
|
|
|
sound_participants_muted.
|
|
|
|
|
|
|
|
* Added menu action participant_count. This will playback the number of
|
|
|
|
current participants in a conference.
|
|
|
|
|
|
|
|
* Added announcement configuration option to user profile. If set the sound
|
|
|
|
file will be played to the user, and only the user, upon joining the
|
|
|
|
conference bridge.
|
|
|
|
|
2013-02-19 15:41:37 +00:00
|
|
|
* Added record_file_append option that defaults to "yes", but if set to no
|
|
|
|
will create a new file between each start/stop recording.
|
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
|
|
|
|
Dial
|
|
|
|
-------------------
|
|
|
|
* Added 'b' and 'B' options to Dial that execute a Gosub on callee and caller
|
|
|
|
channels respectively before the callee channels are called.
|
|
|
|
|
|
|
|
|
|
|
|
ExternalIVR
|
|
|
|
-------------------
|
|
|
|
* Added support for IPv6.
|
|
|
|
|
2012-07-23 21:27:56 +00:00
|
|
|
* Add interrupt ('I') command to ExternalIVR. Sending this command from an
|
2012-07-22 23:37:00 +00:00
|
|
|
external process will cause the current playlist to be cleared, including
|
|
|
|
stopping any audio file that is currently playing. This is useful when you
|
|
|
|
want to interrupt audio playback only when specific DTMF is entered by the
|
|
|
|
caller.
|
|
|
|
|
|
|
|
|
|
|
|
FollowMe
|
|
|
|
-------------------
|
|
|
|
* A new option, 'I' has been added to app_followme. By setting this option,
|
|
|
|
Asterisk will not update the caller with connected line changes when they
|
|
|
|
occur. This is similar to app_dial and app_queue.
|
|
|
|
|
|
|
|
* The 'N' option is now ignored if the call is already answered.
|
|
|
|
|
|
|
|
* Added 'b' and 'B' options to FollowMe that execute a Gosub on callee
|
|
|
|
and caller channels respectively before the callee channels are called.
|
|
|
|
|
|
|
|
* The winning FollowMe outgoing call is now put on hold if the caller put it on
|
|
|
|
hold.
|
|
|
|
|
|
|
|
|
|
|
|
MixMonitor
|
|
|
|
------------------
|
|
|
|
* MixMonitor hooks now have IDs associated with them which can be used to
|
|
|
|
assign a target to StopMixMonitor. Use of MixMonitor's i(variable) option
|
|
|
|
will allow storage of the MixMontior ID in a channel variable. StopMixmonitor
|
|
|
|
now accepts that ID as an argument.
|
|
|
|
|
|
|
|
* Added 'm' option, which stores a copy of the recording as a voicemail in the
|
|
|
|
indicated mailboxes.
|
|
|
|
|
2012-08-07 12:46:36 +00:00
|
|
|
|
2012-07-30 00:05:25 +00:00
|
|
|
MySQL
|
|
|
|
-------------------
|
|
|
|
* The connect action in app_mysql now allows you to specify a port number to
|
|
|
|
connect to. This is useful if you run a MySQL server on a non-standard
|
|
|
|
port number.
|
2012-07-22 23:37:00 +00:00
|
|
|
|
2012-08-07 12:46:36 +00:00
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
OSP Applications
|
|
|
|
-------------------
|
|
|
|
* Increased the default number of allowed destinations from 5 to 12.
|
|
|
|
|
|
|
|
|
|
|
|
Page
|
|
|
|
-------------------
|
|
|
|
* The app_page application now no longer depends on DAHDI or app_meetme. It
|
|
|
|
has been re-architected to use app_confbridge internally.
|
|
|
|
|
|
|
|
|
|
|
|
Queue
|
|
|
|
-------------------
|
|
|
|
* Added queue options autopausebusy and autopauseunavail for automatically
|
|
|
|
pausing a queue member when their device reports busy or congestion.
|
|
|
|
|
|
|
|
* The 'ignorebusy' option for queue members has been deprecated in favor of
|
|
|
|
the option 'ringinuse. Also a 'queue set ringinuse' CLI command has been
|
|
|
|
added as well as an AMI action 'QueueMemberRingInUse' to set this variable on a
|
|
|
|
per interface basis. Individual ringinuse values can now be set in
|
|
|
|
queues.conf via an argument to member definitions. Lastly, the queue
|
|
|
|
'ringinuse' setting now only determines defaults for the per member
|
|
|
|
'ringinuse' setting and does not override per member settings like it does
|
|
|
|
in earlier versions.
|
|
|
|
|
|
|
|
* Added 'F()' option. Similar to the dial option, this can be supplied with
|
|
|
|
arguments indicating where the callee should go after the caller is hung up,
|
|
|
|
or without options specified, the priority after the Queue will be used.
|
|
|
|
|
|
|
|
* Added new option log_member_name_as_agent, which will cause the membername to
|
|
|
|
be logged in the agent field for ADDMEMBER and REMOVEMEMBER queue events if a
|
|
|
|
state_interface has been set.
|
|
|
|
|
2012-09-20 18:44:26 +00:00
|
|
|
* Add queue monitoring hints. exten => 8501,hint,Queue:markq.
|
2012-07-22 23:37:00 +00:00
|
|
|
|
2013-04-29 13:38:59 +00:00
|
|
|
* App_queue will now play periodic announcements for the caller that
|
|
|
|
holds the first position in the queue while waiting for answer.
|
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
SayUnixTime
|
|
|
|
------------------
|
|
|
|
* Added 'j' option to SayUnixTime. SayUnixTime no longer auto jumps to extension
|
|
|
|
when receiving DTMF. Use the 'j' option to enable extension jumping. Also
|
|
|
|
changed arguments to SayUnixTime so that every option is truly optional even
|
|
|
|
when using multiple options (so that j option could be used without having to
|
|
|
|
manually specify timezone and format) There are other benefits, e.g., format
|
|
|
|
can now be used without specifying time zone as well.
|
|
|
|
|
2011-11-17 18:09:13 +00:00
|
|
|
|
2011-12-23 21:19:52 +00:00
|
|
|
Voicemail
|
|
|
|
------------------
|
2012-07-22 23:37:00 +00:00
|
|
|
* Addition of the VM_INFO function - see Function changes.
|
|
|
|
|
2011-12-23 21:19:52 +00:00
|
|
|
* The imapserver, imapport, and imapflags configuration options can now be
|
|
|
|
overriden on a user by user basis.
|
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
* When voicemail plays a message's envelope with saycid set to yes, when
|
|
|
|
reaching the caller id field it will play a recording of a file with the same
|
|
|
|
base name as the sender's callerid if there is a similarly named file in
|
|
|
|
<astspooldir>/recordings/callerids/
|
|
|
|
|
|
|
|
* Voicemails now contains a unique message identifier "msg_id", which is stored
|
|
|
|
in the message envelope with the sound files. IMAP backends will now store
|
|
|
|
the message identifiers with a header of "X-Asterisk-VM-Message-ID". ODBC
|
|
|
|
backends will store the message identifier in a "msg_id" column. See
|
|
|
|
UPGRADE.txt for more information.
|
|
|
|
|
|
|
|
* Added VoiceMailPlayMsg application. This application will play a single
|
|
|
|
voicemail message from a mailbox. The result of the application, SUCCESS or
|
|
|
|
FAILED, is stored in the channel variable VOICEMAIL_PLAYBACKSTATUS.
|
|
|
|
|
|
|
|
|
|
|
|
Functions
|
|
|
|
------------------
|
|
|
|
* Hangup handlers can be attached to channels using the CHANNEL() function.
|
|
|
|
Hangup handlers will run when the channel is hung up similar to the h
|
|
|
|
extension. The hangup_handler_push option will push a GoSub compatible
|
|
|
|
location in the dialplan onto the channel's hangup handler stack. The
|
|
|
|
hangup_handler_pop option will remove the last added location, and optionally
|
|
|
|
replace it with a new GoSub compatible location. The hangup_handler_wipe
|
|
|
|
option will remove all locations on the stack, and optionally add a new
|
|
|
|
location.
|
|
|
|
|
|
|
|
* The expression parser now recognizes the ABS() absolute value function,
|
|
|
|
which will convert negative floating point values to positive values.
|
|
|
|
|
|
|
|
* FAXOPT(faxdetect) will enable a generic fax detect framehook for dialplan
|
|
|
|
control of faxdetect.
|
|
|
|
|
|
|
|
* Addition of the VM_INFO function that can be used to retrieve voicemail
|
|
|
|
user information, such as the email address and full name.
|
|
|
|
The MAILBOX_EXISTS dialplan function has been deprecated in favour of
|
|
|
|
VM_INFO.
|
|
|
|
|
|
|
|
* The REDIRECTING function now supports the redirecting original party id
|
|
|
|
and reason.
|
|
|
|
|
|
|
|
* Two new functions have been added: FEATURE() and FEATUREMAP(). FEATURE()
|
|
|
|
lets you set some of the configuration options from the [general] section
|
|
|
|
of features.conf on a per-channel basis. FEATUREMAP() lets you customize
|
|
|
|
the key sequence used to activate built-in features, such as blindxfer,
|
|
|
|
and automon. See the built-in documentation for details.
|
|
|
|
|
|
|
|
* MESSAGE(from) for incoming SIP messages now returns "display-name" <uri>
|
|
|
|
instead of simply the uri. This is the format that MessageSend() can use
|
|
|
|
in the from parameter for outgoing SIP messages.
|
|
|
|
|
|
|
|
* Added the PRESENCE_STATE function. This allows retrieving presence state
|
|
|
|
information from any presence state provider. It also allows setting
|
|
|
|
presence state information from a CustomPresence presence state provider.
|
|
|
|
See AMI/CLI changes for related commands.
|
|
|
|
|
2012-08-08 21:22:08 +00:00
|
|
|
* Added the AMI_CLIENT function to make manager account attributes available
|
|
|
|
to the dialplan. It currently supports returning the current number of
|
|
|
|
active sessions for a given account.
|
2012-07-22 23:37:00 +00:00
|
|
|
|
2012-08-10 22:04:32 +00:00
|
|
|
* Added support for private party ID information to CALLERID, CONNECTEDLINE,
|
|
|
|
and the REDIRECTING functions.
|
|
|
|
|
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
Channel Drivers
|
|
|
|
------------------
|
|
|
|
|
|
|
|
chan_local
|
|
|
|
------------------
|
|
|
|
* Added a manager event "LocalBridge" for local channel call bridges between
|
|
|
|
the two pseudo-channels created.
|
|
|
|
|
|
|
|
|
|
|
|
chan_dahdi
|
|
|
|
------------------
|
|
|
|
* Added dialtone_detect option for analog ports to disconnect incoming
|
|
|
|
calls when dialtone is detected.
|
|
|
|
|
|
|
|
* Added option colp_send to send ISDN connected line information. Allowed
|
|
|
|
settings are block, to not send any connected line information; connect, to
|
|
|
|
send connected line information on initial connect; and update, to send
|
|
|
|
information on any update during a call. Default is update.
|
|
|
|
|
2012-08-07 12:46:36 +00:00
|
|
|
* Add options namedcallgroup and namedpickupgroup to support installations
|
|
|
|
where a higher number of groups (>64) is required.
|
|
|
|
|
2012-08-10 22:04:32 +00:00
|
|
|
* Added support to use private party ID information with PRI calls.
|
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
|
|
|
|
chan_motif
|
|
|
|
------------------
|
|
|
|
* A new channel driver named chan_motif has been added which provides support for
|
|
|
|
Google Talk and Jingle in a single channel driver. This new channel driver includes
|
|
|
|
support for both audio and video, RFC2833 DTMF, all codecs supported by Asterisk,
|
|
|
|
hold, unhold, and ringing notification. It is also compliant with the current Jingle
|
|
|
|
specification, current Google Jingle specification, and the original Google Talk
|
|
|
|
protocol.
|
|
|
|
|
|
|
|
|
|
|
|
chan_ooh323
|
|
|
|
------------------
|
|
|
|
* Added NAT support for RTP. Setting in config is 'nat', which can be set
|
|
|
|
globally and overriden on a peer by peer basis.
|
|
|
|
|
2012-07-23 21:27:56 +00:00
|
|
|
* Direct media functionality has been added. Options in config are:
|
2012-07-22 23:37:00 +00:00
|
|
|
directmedia (directrtp) and directrtpsetup (earlydirect)
|
|
|
|
|
|
|
|
* ChannelUpdate events now contain a CallRef header.
|
|
|
|
|
|
|
|
|
|
|
|
chan_sip
|
|
|
|
------------------
|
|
|
|
* Asterisk will no longer substitute CID number for CID name in the display
|
2011-08-10 15:45:57 +00:00
|
|
|
name field if CID number exists without a CID name. This change improves
|
|
|
|
compatibility with certain device features such as Avaya IP500's directory
|
|
|
|
lookup service.
|
2012-07-22 23:37:00 +00:00
|
|
|
|
2011-12-23 20:19:33 +00:00
|
|
|
* A new setting for autocreatepeer (autocreatepeer=persistent) allows peers
|
|
|
|
created using that setting to not be removed during SIP reload.
|
2012-07-22 23:37:00 +00:00
|
|
|
|
|
|
|
* Added settings recordonfeature and recordofffeature. When receiving an INFO
|
|
|
|
request with a "Record:" header, this will turn the requested feature on/off.
|
|
|
|
Allowed values are 'automon', 'automixmon', and blank to disable. Note that
|
|
|
|
dynamic features must be enabled and configured properly on the requesting
|
|
|
|
channel for this to function properly.
|
|
|
|
|
|
|
|
* Add support to realtime for the 'callbackextension' option.
|
|
|
|
|
2012-02-08 21:28:55 +00:00
|
|
|
* When multiple peers exist with the same address, but differing
|
|
|
|
callbackextension options, incoming requests that are matched by address
|
|
|
|
will be matched to the peer with the matching callbackextension if it is
|
|
|
|
available.
|
2012-07-22 23:37:00 +00:00
|
|
|
|
2012-02-09 18:14:39 +00:00
|
|
|
* Two new NAT options, auto_force_rport and auto_comedia, have been added
|
|
|
|
which set the force_rport and comedia options automatically if Asterisk
|
|
|
|
detects that an incoming SIP request crossed a NAT after being sent by
|
|
|
|
the remote endpoint.
|
2012-07-22 23:37:00 +00:00
|
|
|
|
2013-03-01 04:32:01 +00:00
|
|
|
* The default global nat setting in sip.conf has been changed from force_rport
|
|
|
|
to auto_force_rport.
|
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
* NAT settings are now a combinable list of options. The equivalent of the
|
|
|
|
deprecated nat=yes is nat=force_rport,comedia. nat=no behaves as before.
|
|
|
|
|
2012-02-27 16:24:17 +00:00
|
|
|
* Adds an option send_diversion which can be disabled to prevent
|
2012-07-22 23:37:00 +00:00
|
|
|
diversion headers from automatically being added to INVITE requests.
|
|
|
|
|
2012-04-28 20:24:45 +00:00
|
|
|
* Add support for lightweight NAT keepalive. If enabled a blank packet will
|
|
|
|
be sent to the remote host at a given interval to keep the NAT mapping open.
|
|
|
|
This can be enabled using the keepalive configuration option.
|
2012-07-22 23:37:00 +00:00
|
|
|
|
|
|
|
* Add option 'tonezone' to specify country code for indications. This option
|
|
|
|
can be set both globally and overridden for specific peers.
|
|
|
|
|
|
|
|
* The SIP Security Events Framework now supports IPv6.
|
|
|
|
|
|
|
|
* Add a new setting for directmedia, 'outgoing', to alleviate INVITE glares
|
|
|
|
between multiple user agents. When set, for directmedia reinvites,
|
|
|
|
Asterisk will not send an immediate reinvite on an incoming call leg. This
|
|
|
|
option is useful when peered with another SIP user agent that is known to
|
|
|
|
send immediate direct media reinvites upon call establishment.
|
|
|
|
|
2012-07-16 12:35:04 +00:00
|
|
|
* Add support for WebSocket transport. This can be configured using 'ws' or 'wss'
|
|
|
|
as the transport.
|
2012-08-07 12:46:36 +00:00
|
|
|
|
2012-07-23 21:10:54 +00:00
|
|
|
* Add options subminexpiry and submaxexpiry to set limits of subscription
|
|
|
|
timer independently from registration timer settings. The setting of the
|
|
|
|
registration timer limits still is done by options minexpiry, maxexpiry
|
|
|
|
and defaultexpiry. For backwards compatibility the setting of minexpiry
|
|
|
|
and maxexpiry also is used to configure the subscription timer limits if
|
|
|
|
subminexpiry and submaxexpiry are not set in sip.conf.
|
2012-08-07 12:46:36 +00:00
|
|
|
|
2012-07-23 21:10:54 +00:00
|
|
|
* Set registration timer limits to default values when reloading sip
|
|
|
|
configuration and values are not set by configuration.
|
2011-08-10 15:45:57 +00:00
|
|
|
|
2012-08-07 12:46:36 +00:00
|
|
|
* Add options namedcallgroup and namedpickupgroup to support installations
|
|
|
|
where a higher number of groups (>64) is required.
|
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
* When a MESSAGE request is received, the address the request was received from
|
|
|
|
is now saved in the SIP_RECVADDR variable.
|
2011-08-24 09:12:23 +00:00
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
* Add ANI2/OLI parsing for SIP. The "From" header in INVITE requests is now
|
|
|
|
parsed for the presence of "isup-oli", "ss7-oli", or "oli" tags. If present,
|
|
|
|
the ANI2/OLI information is set on the channel, which can be retrieved using
|
|
|
|
the CALLERID function.
|
2012-03-06 01:56:10 +00:00
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
* Peers can now be configured to support negotiation of ICE candidates using
|
|
|
|
the setting icesupport. See res_rtp_asterisk changes for more information.
|
2012-07-16 14:02:10 +00:00
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
* Added support for format attribute negotiation. See the Codecs changes for
|
|
|
|
more information.
|
2012-07-16 14:02:10 +00:00
|
|
|
|
2012-08-08 22:41:08 +00:00
|
|
|
* Extra headers specified with SIPAddHeader are sent with the REFER message
|
|
|
|
when using Transfer application. See refer_addheaders in sip.conf.sample.
|
2012-07-16 14:02:10 +00:00
|
|
|
|
2012-08-10 22:04:32 +00:00
|
|
|
* Added support to use private party ID information with calls.
|
|
|
|
|
2013-03-11 15:22:02 +00:00
|
|
|
* Adds an option discard_remote_hold_retrieval that when set stops telling
|
|
|
|
the peer to start music on hold.
|
|
|
|
|
2012-08-10 22:04:32 +00:00
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
chan_skinny
|
|
|
|
------------------
|
|
|
|
* Added skinny version 17 protocol support.
|
|
|
|
|
|
|
|
|
|
|
|
chan_unistim
|
Massive changes in chan_unistim channel driver. Include many fixes in channel driver operation and add additional functionality:
* Added ability to use multiple lines on phone, so for one device in configuration multiple lines can be defined, it allows to have multiple calls on one phone, callwaiting and switching between calls.
* Added ability for translation on-screen menu to multiple languages. Tested on Russian languages. Supported encodings: ISO 8859-1, ISO 8859-2, ISO 8859-4, ISO 8859-5, ISO 2022-JP. Language controlled by 'language' and on-screen menu of phone
* Other described in CHANGES file
Testing done by issue tracker users: ibercom, scsiborg, idarwin, TeknoJuce, c0rnoTa.
Tested on production system by Jonn Taylor (jonnt) using phone models: Nortel i2004, 1120E and 1140E.
(closes issue ASTERISK-16890)
Review: https://reviewboard.asterisk.org/r/1243/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@358766 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2012-03-12 17:01:26 +00:00
|
|
|
--------------------
|
2014-04-28 07:43:33 +00:00
|
|
|
* Added option 'dtmf_duration' allowing playback time of DTMF tones to be set
|
|
|
|
|
|
|
|
* Modified option 'date_format' to allow options to display date in 31Jan and Jan31
|
|
|
|
formats as options 0 and 1. The previous options 0 and 1 now map to options 2 and 3
|
|
|
|
as per the UNISTIM protocol.
|
|
|
|
|
|
|
|
* Fixed issues with dialtone not matching indications.conf and mute stopping rx
|
2014-08-10 22:02:03 +00:00
|
|
|
as well as tx. Also fixed issue with call "Timer" displaying as French "Dur\E9e"
|
2014-04-28 07:43:33 +00:00
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
* Added ability to use multiple lines for a single phone. This allows multiple
|
|
|
|
calls to occur on a single phone, using callwaiting and switching between calls.
|
|
|
|
|
Massive changes in chan_unistim channel driver. Include many fixes in channel driver operation and add additional functionality:
* Added ability to use multiple lines on phone, so for one device in configuration multiple lines can be defined, it allows to have multiple calls on one phone, callwaiting and switching between calls.
* Added ability for translation on-screen menu to multiple languages. Tested on Russian languages. Supported encodings: ISO 8859-1, ISO 8859-2, ISO 8859-4, ISO 8859-5, ISO 2022-JP. Language controlled by 'language' and on-screen menu of phone
* Other described in CHANGES file
Testing done by issue tracker users: ibercom, scsiborg, idarwin, TeknoJuce, c0rnoTa.
Tested on production system by Jonn Taylor (jonnt) using phone models: Nortel i2004, 1120E and 1140E.
(closes issue ASTERISK-16890)
Review: https://reviewboard.asterisk.org/r/1243/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@358766 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2012-03-12 17:01:26 +00:00
|
|
|
* Added option 'sharpdial' allowing end dialing by pressing # key
|
2012-07-22 23:37:00 +00:00
|
|
|
|
|
|
|
* Added option 'interdigit_timer' to control phone dial timeout
|
|
|
|
|
Massive changes in chan_unistim channel driver. Include many fixes in channel driver operation and add additional functionality:
* Added ability to use multiple lines on phone, so for one device in configuration multiple lines can be defined, it allows to have multiple calls on one phone, callwaiting and switching between calls.
* Added ability for translation on-screen menu to multiple languages. Tested on Russian languages. Supported encodings: ISO 8859-1, ISO 8859-2, ISO 8859-4, ISO 8859-5, ISO 2022-JP. Language controlled by 'language' and on-screen menu of phone
* Other described in CHANGES file
Testing done by issue tracker users: ibercom, scsiborg, idarwin, TeknoJuce, c0rnoTa.
Tested on production system by Jonn Taylor (jonnt) using phone models: Nortel i2004, 1120E and 1140E.
(closes issue ASTERISK-16890)
Review: https://reviewboard.asterisk.org/r/1243/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@358766 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2012-03-12 17:01:26 +00:00
|
|
|
* Added options 'cwstyle', 'cwvolume' controlling callwaiting appearance
|
2012-07-22 23:37:00 +00:00
|
|
|
|
Massive changes in chan_unistim channel driver. Include many fixes in channel driver operation and add additional functionality:
* Added ability to use multiple lines on phone, so for one device in configuration multiple lines can be defined, it allows to have multiple calls on one phone, callwaiting and switching between calls.
* Added ability for translation on-screen menu to multiple languages. Tested on Russian languages. Supported encodings: ISO 8859-1, ISO 8859-2, ISO 8859-4, ISO 8859-5, ISO 2022-JP. Language controlled by 'language' and on-screen menu of phone
* Other described in CHANGES file
Testing done by issue tracker users: ibercom, scsiborg, idarwin, TeknoJuce, c0rnoTa.
Tested on production system by Jonn Taylor (jonnt) using phone models: Nortel i2004, 1120E and 1140E.
(closes issue ASTERISK-16890)
Review: https://reviewboard.asterisk.org/r/1243/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@358766 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2012-03-12 17:01:26 +00:00
|
|
|
* Added global 'debug' option, that enables debug in channel driver
|
2012-07-22 23:37:00 +00:00
|
|
|
|
|
|
|
* Added ability to translate on-screen menu in multiple languages. Tested on
|
2012-07-23 21:27:56 +00:00
|
|
|
Russian languages. Supported encodings: ISO 8859-1, ISO 8859-2, ISO 8859-4,
|
|
|
|
ISO 8859-5, ISO 2022-JP. Language controlled by 'language' and on-screen
|
Massive changes in chan_unistim channel driver. Include many fixes in channel driver operation and add additional functionality:
* Added ability to use multiple lines on phone, so for one device in configuration multiple lines can be defined, it allows to have multiple calls on one phone, callwaiting and switching between calls.
* Added ability for translation on-screen menu to multiple languages. Tested on Russian languages. Supported encodings: ISO 8859-1, ISO 8859-2, ISO 8859-4, ISO 8859-5, ISO 2022-JP. Language controlled by 'language' and on-screen menu of phone
* Other described in CHANGES file
Testing done by issue tracker users: ibercom, scsiborg, idarwin, TeknoJuce, c0rnoTa.
Tested on production system by Jonn Taylor (jonnt) using phone models: Nortel i2004, 1120E and 1140E.
(closes issue ASTERISK-16890)
Review: https://reviewboard.asterisk.org/r/1243/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@358766 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2012-03-12 17:01:26 +00:00
|
|
|
menu of phone
|
2012-07-22 23:37:00 +00:00
|
|
|
|
2012-07-16 07:34:12 +00:00
|
|
|
* In addition to English added French and Russian languages for on-screen menus
|
2012-07-22 23:37:00 +00:00
|
|
|
|
2012-07-23 21:27:56 +00:00
|
|
|
* Reworked dialing number input: added dialing by timeout, immediate dial on
|
Massive changes in chan_unistim channel driver. Include many fixes in channel driver operation and add additional functionality:
* Added ability to use multiple lines on phone, so for one device in configuration multiple lines can be defined, it allows to have multiple calls on one phone, callwaiting and switching between calls.
* Added ability for translation on-screen menu to multiple languages. Tested on Russian languages. Supported encodings: ISO 8859-1, ISO 8859-2, ISO 8859-4, ISO 8859-5, ISO 2022-JP. Language controlled by 'language' and on-screen menu of phone
* Other described in CHANGES file
Testing done by issue tracker users: ibercom, scsiborg, idarwin, TeknoJuce, c0rnoTa.
Tested on production system by Jonn Taylor (jonnt) using phone models: Nortel i2004, 1120E and 1140E.
(closes issue ASTERISK-16890)
Review: https://reviewboard.asterisk.org/r/1243/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@358766 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2012-03-12 17:01:26 +00:00
|
|
|
on dialplan compare, phone number length now not limited by screen size
|
2012-07-22 23:37:00 +00:00
|
|
|
|
2012-07-23 21:27:56 +00:00
|
|
|
* Added ability to pickup a call using features.conf defined value and
|
Massive changes in chan_unistim channel driver. Include many fixes in channel driver operation and add additional functionality:
* Added ability to use multiple lines on phone, so for one device in configuration multiple lines can be defined, it allows to have multiple calls on one phone, callwaiting and switching between calls.
* Added ability for translation on-screen menu to multiple languages. Tested on Russian languages. Supported encodings: ISO 8859-1, ISO 8859-2, ISO 8859-4, ISO 8859-5, ISO 2022-JP. Language controlled by 'language' and on-screen menu of phone
* Other described in CHANGES file
Testing done by issue tracker users: ibercom, scsiborg, idarwin, TeknoJuce, c0rnoTa.
Tested on production system by Jonn Taylor (jonnt) using phone models: Nortel i2004, 1120E and 1140E.
(closes issue ASTERISK-16890)
Review: https://reviewboard.asterisk.org/r/1243/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@358766 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2012-03-12 17:01:26 +00:00
|
|
|
on-screen key
|
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
|
2012-08-07 12:46:36 +00:00
|
|
|
chan_mISDN:
|
|
|
|
------------------
|
|
|
|
* Add options namedcallgroup and namedpickupgroup to support installations
|
|
|
|
where a higher number of groups (>64) is required.
|
|
|
|
|
2012-08-10 22:04:32 +00:00
|
|
|
* Added support to use private party ID information with calls.
|
|
|
|
|
2012-08-07 12:46:36 +00:00
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
Core
|
|
|
|
------------------
|
|
|
|
* The minimum DTMF duration can now be configured in asterisk.conf
|
|
|
|
as "mindtmfduration". The default value is (as before) set to 80 ms.
|
|
|
|
(previously it was only available in source code)
|
|
|
|
|
|
|
|
* Named ACLs can now be specified in acl.conf and used in configurations that
|
|
|
|
use ACLs. As a general rule, if some derivative of 'permit' or 'deny' is
|
|
|
|
used to specify an ACL, a similar form of 'acl' will add a named ACL to the
|
|
|
|
working ACL. In addition, some CLI commands have been added to provide
|
|
|
|
show information and allow for module reloading - see CLI Changes.
|
|
|
|
|
2012-07-24 16:48:45 +00:00
|
|
|
* Rules in ACLs (specified using 'permit' and 'deny') can now contain multiple
|
|
|
|
items (separated by commas), and items in the rule can be negated by prefixing
|
|
|
|
them with '!'. This simplifies Asterisk Realtime configurations, since it is no
|
|
|
|
longer necessray to control the order that the 'permit' and 'deny' columns are
|
|
|
|
returned from queries.
|
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
* DUNDi now allows the built in variables ${NUMBER}, ${IPADDR} and ${SECRET} to
|
|
|
|
be used within the dynamic weight attribute when specifying a mapping.
|
|
|
|
|
|
|
|
* CEL backends can now be configured to show "USER_DEFINED" in the EventName
|
|
|
|
header, instead of putting the user defined event name there. When enabled
|
|
|
|
the UserDefType header is added for user defined events. This feature is
|
|
|
|
enabled with the setting show_user_defined.
|
|
|
|
|
|
|
|
* Macro has been deprecated in favor of GoSub. For redirecting and connected
|
|
|
|
line purposes use the following variables instead of their macro equivalents:
|
|
|
|
REDIRECTING_SEND_SUB, REDIRECTING_SEND_SUB_ARGS, CONNECTED_LINE_SEND_SUB,
|
|
|
|
CONNECTED_LINE_SEND_SUB_ARGS. For CCSS, use cc_callback_sub instead of
|
|
|
|
cc_callback_macro in channel configurations.
|
|
|
|
|
2012-07-25 12:21:54 +00:00
|
|
|
* Asterisk can now use a system-provided NetBSD editline library (libedit) if it
|
|
|
|
is available.
|
2012-07-22 23:37:00 +00:00
|
|
|
|
2012-08-08 22:39:40 +00:00
|
|
|
* Call files now support the "early_media" option to connect with an outgoing
|
|
|
|
extension when early media is received.
|
|
|
|
|
2012-08-10 22:04:32 +00:00
|
|
|
* Added support to use private party ID information with calls.
|
|
|
|
|
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
AGI
|
|
|
|
------------------
|
|
|
|
* A new channel variable, AGIEXITONHANGUP, has been added which allows
|
|
|
|
Asterisk to behave like it did in Asterisk 1.4 and earlier where the
|
|
|
|
AGI application would exit immediately after a channel hangup is detected.
|
|
|
|
|
|
|
|
* IPv6 addresses are now supported when using FastAGI (agi://). Hostnames
|
|
|
|
are resolved and each address is attempted in turn until one succeeds or
|
|
|
|
all fail.
|
|
|
|
|
|
|
|
|
|
|
|
AMI (Asterisk Manager Interface)
|
|
|
|
------------------
|
2012-08-08 22:39:40 +00:00
|
|
|
* The originate action now has an option "EarlyMedia" that enables the
|
|
|
|
call to bridge when we get early media in the call. Previously,
|
|
|
|
early media was disregarded always when originating calls using AMI.
|
|
|
|
|
2012-07-31 21:21:57 +00:00
|
|
|
* Added setvar= option to manager accounts (much like sip.conf)
|
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
* Originate now generates an error response if the extension given is not found
|
|
|
|
in the dialplan
|
|
|
|
|
|
|
|
* MixMonitor will now show IDs associated with the mixmonitor upon creating
|
|
|
|
them if the i(variable) option is used. StopMixMonitor will accept
|
|
|
|
MixMonitorID as an option to close specific MixMonitors.
|
|
|
|
|
|
|
|
* The SIPshowpeer manager action response field "SIP-Forcerport" has been
|
|
|
|
updated to include information about peers configured with
|
|
|
|
nat=auto_force_rport by returning "A" if auto_force_rport is set and nat is
|
|
|
|
detected, and "a" if it is set and nat is not detected. "Y" and "N" are still
|
|
|
|
returned if auto_force_rport is not enabled.
|
|
|
|
|
2012-07-26 15:31:05 +00:00
|
|
|
* Added SIPpeerstatus manager command which will generate PeerStatus events
|
|
|
|
similar to the existing PeerStatus events found in chan_sip on demand.
|
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
* Hangup now can take a regular expression as the Channel option. If you want
|
2012-07-23 21:27:56 +00:00
|
|
|
to hangup multiple channels, use /regex/ as the Channel option. Existing
|
2012-07-22 23:37:00 +00:00
|
|
|
behavior to hanging up a single channel is unchanged, but if you pass a regex,
|
|
|
|
the manager will send you a list of channels back that were hung up.
|
|
|
|
|
|
|
|
* Support for IPv6 addresses has been added.
|
|
|
|
|
|
|
|
* AMI Events can now be documented in the Asterisk source. Note that AMI event
|
|
|
|
documentation is only generated when Asterisk is compiled using 'make full'.
|
|
|
|
See the CLI section for commands to display AMI event information.
|
|
|
|
|
|
|
|
* The AMI Hangup event now includes the AccountCode header so you can easily
|
|
|
|
correlate with AMI Newchannel events.
|
|
|
|
|
|
|
|
* The QueueMemberStatus, QueueMemberAdded, and QueueMember events now include
|
|
|
|
the StateInterface of the queue member.
|
|
|
|
|
|
|
|
* Added AMI event SessionTimeout in the Call category that is issued when a
|
|
|
|
call is terminated due to either RTP stream inactivity or SIP session timer
|
|
|
|
expiration.
|
|
|
|
|
|
|
|
* CEL events can now contain a user defined header UserDefType. See core
|
|
|
|
changes for more information.
|
|
|
|
|
|
|
|
* OOH323 ChannelUpdate events now contain a CallRef header.
|
|
|
|
|
|
|
|
* Added PresenceState command. This command will report the presence state for
|
|
|
|
the given presence provider.
|
|
|
|
|
|
|
|
* Added Parkinglots command. This will list all parking lots as a series of
|
|
|
|
AMI Parkinglot events.
|
|
|
|
|
|
|
|
* Added MessageSend command. This behaves in the same manner as the
|
|
|
|
MessageSend application, and is a technolgoy agnostic mechanism to send out
|
|
|
|
of call text messages.
|
|
|
|
|
|
|
|
* Added "message" class authorization. This grants an account permission to
|
|
|
|
send out of call messages. Write-only.
|
|
|
|
|
|
|
|
|
|
|
|
CLI
|
|
|
|
-------------------
|
2012-07-31 19:57:21 +00:00
|
|
|
* The "dialplan add include" command has been modified to create context a context
|
|
|
|
if one does not already exist. For instance, "dialplan add include foo into bar"
|
|
|
|
will create context "bar" if it does not already exist.
|
|
|
|
|
|
|
|
* A "dialplan remove context" command has been added to remove a context from
|
|
|
|
the dialplan
|
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
* The "mixmonitor list <channel>" command will now show MixMonitor ID, and the
|
|
|
|
filenames of all running mixmonitors on a channel.
|
|
|
|
|
|
|
|
* The debug level of "pri set debug" is now a bitmask ranging from 0 to 15 if
|
|
|
|
numeric instead of 0, 1, or 2.
|
|
|
|
|
|
|
|
* "stun show status" will show a table describing how the STUN client is
|
|
|
|
behaving.
|
|
|
|
|
|
|
|
* "acl show [named acl]" will show information regarding a Named ACL. The
|
|
|
|
acl module can be reloaded with "reload acl".
|
|
|
|
|
|
|
|
* Added CLI command to display AMI event information - "manager show events",
|
|
|
|
which shows a list of all known and documented AMI events, and "manager show
|
|
|
|
event [event name]", which shows detail information about a specific AMI
|
|
|
|
event.
|
|
|
|
|
|
|
|
* The result of the CLI command "queue show" now includes the state interface
|
|
|
|
information of the queue member.
|
|
|
|
|
|
|
|
* The command "core set verbose" will now set a separate level of logging for
|
|
|
|
each remote console without affecting any other console.
|
|
|
|
|
|
|
|
* Added command "cdr show pgsql status" to check connection status
|
|
|
|
|
|
|
|
* "sip show channel" will now display the complete route set.
|
|
|
|
|
|
|
|
* Added "presencestate list" command. This command will list all custom
|
|
|
|
presence states that have been set by using the PRESENCE_STATE dialplan
|
|
|
|
function.
|
|
|
|
|
|
|
|
* Added "presencestate change <entity> <state>[,<subtype>[,message[,options]]]"
|
|
|
|
command. This changes a custom presence to a new state.
|
|
|
|
|
|
|
|
|
|
|
|
Codecs
|
|
|
|
-------------------
|
2011-09-07 00:54:36 +00:00
|
|
|
* Codec lists may now be modified by the '!' character, to allow succinct
|
|
|
|
specification of a list of codecs allowed and disallowed, without the
|
|
|
|
requirement to use two different keywords. For example, to specify all
|
|
|
|
codecs except g729 and g723, one need only specify allow=all,!g729,!g723.
|
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
* Add support for parsing SDP attributes, generating SDP attributes, and
|
|
|
|
passing it through. This support includes codecs such as H.263, H.264, SILK,
|
|
|
|
and CELT. You are able to set up a call and have attribute information pass.
|
|
|
|
This should help considerably with video calls.
|
|
|
|
|
2012-07-23 21:27:56 +00:00
|
|
|
* The iLBC codec can now use a system-provided iLBC library if one is installed,
|
|
|
|
just like the GSM codec.
|
2012-07-22 23:37:00 +00:00
|
|
|
|
2012-08-09 14:36:37 +00:00
|
|
|
DUNDi changes
|
|
|
|
-------------
|
|
|
|
* Added CLI commands dundi show hints and dundi show cache which will list DUNDi
|
|
|
|
'DONTASK' hints in the cache and list all DUNDi cache entires respectively.
|
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
Logging
|
|
|
|
-------------------
|
|
|
|
* Asterisk version and build information is now logged at the beginning of a
|
|
|
|
log file.
|
|
|
|
|
|
|
|
* Threads belonging to a particular call are now linked with callids which get
|
|
|
|
added to any log messages produced by those threads. Log messages can now be
|
|
|
|
easily identified as involved with a certain call by looking at their call id.
|
|
|
|
Call ids may also be attached to log messages for just about any case where
|
|
|
|
it can be determined to be related to a particular call.
|
|
|
|
|
|
|
|
* Each logging destination and console now have an independent notion of the
|
|
|
|
current verbosity level. Logger.conf now allows an optional argument to
|
|
|
|
the 'verbose' specifier, indicating the level of verbosity sent to that
|
|
|
|
particular logging destination. Additionally, remote consoles now each
|
|
|
|
have their own verbosity level. The command 'core set verbose' will now set
|
|
|
|
a separate level for each remote console without affecting any other
|
|
|
|
console.
|
|
|
|
|
|
|
|
|
|
|
|
Music On Hold
|
|
|
|
-------------------
|
2012-01-23 18:34:47 +00:00
|
|
|
* Added 'announcement' option which will play at the start of MOH and between
|
|
|
|
songs in modes of MOH that can detect transitions between songs (eg.
|
|
|
|
files, mp3, etc).
|
|
|
|
|
2011-12-09 20:27:03 +00:00
|
|
|
|
2012-01-20 20:47:42 +00:00
|
|
|
Parking
|
2012-07-22 23:37:00 +00:00
|
|
|
-------------------
|
2012-01-20 20:47:42 +00:00
|
|
|
* New per parking lot options: comebackcontext and comebackdialtime. See
|
|
|
|
configs/features.conf.sample for more details.
|
2012-01-30 21:21:16 +00:00
|
|
|
|
2012-01-20 20:47:42 +00:00
|
|
|
* Channel variable PARKER is now set when comebacktoorigin is disabled in
|
|
|
|
a parking lot.
|
|
|
|
|
2012-07-23 21:27:56 +00:00
|
|
|
* Channel variable PARKEDCALL is now set with the name of the parking lot
|
2012-07-22 23:37:00 +00:00
|
|
|
when a timeout occurs.
|
2012-01-23 18:16:20 +00:00
|
|
|
|
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
CDRs
|
|
|
|
-------------------
|
2012-02-09 18:14:39 +00:00
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
CDR Postgresql Driver
|
|
|
|
-------------------
|
|
|
|
* Added command "cdr show pgsql status" to check connection status
|
2012-04-03 19:31:25 +00:00
|
|
|
|
2012-06-20 03:18:50 +00:00
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
CDR Adaptive ODBC Driver
|
|
|
|
-------------------
|
|
|
|
* Added schema option for databases that support specifying a schema.
|
2012-06-25 17:59:34 +00:00
|
|
|
|
2011-10-05 06:50:18 +00:00
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
Resource Modules
|
|
|
|
-------------------
|
2011-11-07 21:58:14 +00:00
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
Calendars
|
|
|
|
-------------------
|
2012-07-23 21:27:56 +00:00
|
|
|
* A CALENDAR_SUCCESS=1/0 channel variable is now set to show whether or not
|
2012-07-22 23:37:00 +00:00
|
|
|
CALENDAR_WRITE has completed successfully.
|
2011-12-06 20:23:13 +00:00
|
|
|
|
2012-01-11 21:56:12 +00:00
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
res_rtp_asterisk
|
|
|
|
-------------------
|
2012-01-17 17:15:05 +00:00
|
|
|
* A new option, 'probation' has been added to rtp.conf
|
|
|
|
RTP in strictrtp mode can now require more than 1 packet to exit learning
|
|
|
|
mode with a new source (and by default requires 4). The probation option
|
|
|
|
allows the user to change the required number of packets in sequence to any
|
|
|
|
desired value. Use a value of 1 to essentially restore the old behavior.
|
|
|
|
Also, with strictrtp on, Asterisk will now drop all packets until learning
|
|
|
|
mode has successfully exited. These changes are based on how pjmedia handles
|
|
|
|
media sources and source changes.
|
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
* Add support for ICE/STUN/TURN in res_rtp_asterisk. This option can be
|
|
|
|
enabled or disabled using the icesupport setting. A variety of other
|
|
|
|
settings have been introduced to configure STUN/TURN connections.
|
|
|
|
|
2012-01-25 17:23:25 +00:00
|
|
|
|
2012-02-05 10:58:37 +00:00
|
|
|
res_corosync
|
2012-07-22 23:37:00 +00:00
|
|
|
-------------------
|
2012-02-05 10:58:37 +00:00
|
|
|
* A new module, res_corosync, has been introduced. This module uses the
|
|
|
|
Corosync cluster enginer (http://www.corosync.org) to allow a local cluster
|
|
|
|
of Asterisk servers to both Message Waiting Indication (MWI) and/or
|
|
|
|
Device State (presence) information. This module is very similar to, and
|
|
|
|
is a replacement for the res_ais module that was in previous releases of
|
|
|
|
Asterisk.
|
|
|
|
|
2012-02-14 00:43:50 +00:00
|
|
|
|
2012-07-22 23:37:00 +00:00
|
|
|
res_xmpp
|
|
|
|
-------------------
|
|
|
|
* This module adds a cleaned up, drop-in replacement for res_jabber called
|
|
|
|
res_xmpp. This provides the same externally facing functionality but is
|
|
|
|
implemented differently internally. res_jabber has been deprecated in favor
|
|
|
|
of res_xmpp; please see the UPGRADE.txt file for more information.
|
|
|
|
|
|
|
|
|
|
|
|
Scripts
|
|
|
|
-------------------
|
|
|
|
* The safe_asterisk script has been updated to allow several of its parameters
|
|
|
|
to be set from environment variables. This also enables a custom run
|
|
|
|
directory of Asterisk to be specified, instead of defaulting to /tmp.
|
|
|
|
|
|
|
|
* The live_ast script will now look for the LIVE_AST_BASE_DIR variable and use
|
|
|
|
its value to determine the directory to assume is the top-level directory of
|
|
|
|
the source tree. If the variable is not set, it defaults to the current
|
|
|
|
behavior and uses the current working directory.
|
2012-07-04 21:42:05 +00:00
|
|
|
|
2010-07-23 19:16:14 +00:00
|
|
|
------------------------------------------------------------------------------
|
2011-07-21 20:26:44 +00:00
|
|
|
--- Functionality changes from Asterisk 1.8 to Asterisk 10 -------------------
|
2010-07-23 19:16:14 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
2011-06-01 21:31:40 +00:00
|
|
|
Text Messaging
|
|
|
|
--------------
|
|
|
|
* Asterisk now has protocol independent support for processing text messages
|
|
|
|
outside of a call. Messages are routed through the Asterisk dialplan.
|
|
|
|
SIP MESSAGE and XMPP are currently supported. There are options in
|
|
|
|
jabber.conf and sip.conf to allow enabling these features.
|
|
|
|
-> jabber.conf: see the "sendtodialplan" and "context" options.
|
2011-06-13 19:43:57 +00:00
|
|
|
-> sip.conf: see the "accept_outofcall_message", "auth_message_requests"
|
|
|
|
and "outofcall_message_context" options.
|
2011-06-01 21:31:40 +00:00
|
|
|
The MESSAGE() dialplan function and MessageSend() application have been
|
|
|
|
added to go along with this functionality. More detailed usage information
|
|
|
|
can be found on the Asterisk wiki (http://wiki.asterisk.org/).
|
2011-08-29 17:31:40 +00:00
|
|
|
* If real-time text support (T.140) is negotiated, it will be preferred for
|
|
|
|
sending text via the SendText application. For example, via SIP, messages
|
|
|
|
that were once sent via the SIP MESSAGE request would be sent via RTP if
|
|
|
|
T.140 text is negotiated for a call.
|
2011-06-01 21:31:40 +00:00
|
|
|
|
2011-02-09 20:11:11 +00:00
|
|
|
Parking
|
|
|
|
-------
|
|
|
|
* parkedmusicclass can now be set for non-default parking lots.
|
|
|
|
|
2010-07-29 21:06:13 +00:00
|
|
|
Asterisk Manager Interface
|
|
|
|
--------------------------
|
|
|
|
* PeerStatus now includes Address and Port.
|
2011-01-04 16:38:28 +00:00
|
|
|
* Added Hold events for when the remote party puts the call on and off hold
|
|
|
|
for chan_dahdi ISDN channels.
|
2011-02-09 22:48:02 +00:00
|
|
|
* Added new action MeetmeListRooms to list active conferences (shows same
|
|
|
|
data as "meetme list" at the CLI).
|
2011-04-13 15:49:33 +00:00
|
|
|
* DAHDIShowChannels, SIPshowpeer, SIPpeers, and IAXpeers now contains a
|
|
|
|
Description field that is set by 'description' in the channel configuration
|
|
|
|
file.
|
2011-05-06 20:44:53 +00:00
|
|
|
* Added Uniqueid header to UserEvent.
|
2011-07-05 16:46:17 +00:00
|
|
|
* Added new action FilterAdd to control event filters for the current session.
|
|
|
|
This requires the system permission and uses the same filter syntax as
|
|
|
|
filters that can be defined in manager.conf
|
2011-08-08 21:16:25 +00:00
|
|
|
* The Unlink event is now a Bridge event with Bridgestatus: Unlink. Previous
|
|
|
|
versions had some instances of the event converted, but others were left
|
2011-08-08 22:59:45 +00:00
|
|
|
as-is. All Unlink events should now be converted to Bridge events. The AMI
|
|
|
|
protocol version number was incremented to 1.2 as a result of this change.
|
2010-07-23 19:16:14 +00:00
|
|
|
|
2010-11-02 14:43:11 +00:00
|
|
|
Asterisk HTTP Server
|
|
|
|
--------------------------
|
|
|
|
* The HTTP Server can bind to IPv6 addresses.
|
|
|
|
|
2011-04-01 17:01:01 +00:00
|
|
|
chan_dahdi
|
|
|
|
--------------------------
|
|
|
|
* Busy tone patterns featuring 2 silence and 2 tone lengths can now be used
|
|
|
|
with busydetect. usage example: busypattern=200,200,200,600
|
|
|
|
|
2010-11-02 15:14:12 +00:00
|
|
|
CLI Changes
|
2011-01-04 16:38:28 +00:00
|
|
|
--------------------------
|
2010-11-02 15:14:12 +00:00
|
|
|
* New 'gtalk show settings' command showing the current settings loaded from
|
|
|
|
gtalk.conf.
|
2010-12-31 09:21:47 +00:00
|
|
|
* The 'logger reload' command now supports an optional argument, specifying an
|
|
|
|
alternate configuration file to use.
|
2011-04-04 17:32:05 +00:00
|
|
|
* 'dialplan add extension' command will now automatically create a context if
|
|
|
|
the specified context does not exist with a message indicated it did so.
|
2011-04-13 15:49:33 +00:00
|
|
|
* 'sip show peers', 'iax show peers', and 'dahdi show peers' now contains a
|
|
|
|
Description field which can be populated with 'description' in the channel
|
|
|
|
configuration files (sip.conf, iax2.conf, and chan_dahdi.conf).
|
2010-11-02 15:14:12 +00:00
|
|
|
|
2010-12-31 09:29:10 +00:00
|
|
|
CDR
|
2011-01-04 16:38:28 +00:00
|
|
|
--------------------------
|
2010-12-31 09:29:10 +00:00
|
|
|
* The filter option in cdr_adaptive_odbc now supports negating the argument,
|
|
|
|
thus allowing records which do NOT match the specified filter.
|
2011-08-22 17:05:14 +00:00
|
|
|
* Added ability to log CONGESTION calls to CDR
|
2010-12-31 09:29:10 +00:00
|
|
|
|
Media Project Phase2: SILK 8khz-24khz, SLINEAR 8khz-192khz, SPEEX 32khz, hd audio ConfBridge, and other stuff
-Functional changes
1. Dynamic global format list build by codecs defined in codecs.conf
2. SILK 8khz, 12khz, 16khz, and 24khz with custom attributes defined in codecs.conf
3. Negotiation of SILK attributes in chan_sip.
4. SPEEX 32khz with translation
5. SLINEAR 8khz, 12khz, 24khz, 32khz, 44.1khz, 48khz, 96khz, 192khz with translation
using codec_resample.c
6. Various changes to RTP code required to properly handle the dynamic format list
and formats with attributes.
7. ConfBridge now dynamically jumps to the best possible sample rate. This allows
for conferences to take advantage of HD audio (Which sounds awesome)
8. Audiohooks are no longer limited to 8khz audio, and most effects have been
updated to take advantage of this such as Volume, DENOISE, PITCH_SHIFT.
9. codec_resample now uses its own code rather than depending on libresample.
-Organizational changes
Global format list is moved from frame.c to format.c
Various format specific functions moved from frame.c to format.c
Review: https://reviewboard.asterisk.org/r/1104/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@308582 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2011-02-22 23:04:49 +00:00
|
|
|
CODECS
|
|
|
|
--------------------------
|
|
|
|
* Ability to define custom SILK formats in codecs.conf.
|
|
|
|
* Addition of speex32 audio format with translation.
|
2011-07-07 19:57:06 +00:00
|
|
|
* CELT codec pass-through support and ability to define
|
|
|
|
custom CELT formats in codecs.conf.
|
2011-07-08 20:26:07 +00:00
|
|
|
* Ability to read raw signed linear files with sample rates
|
|
|
|
ranging from 8khz - 192khz. The new file extensions introduced
|
2011-07-08 20:33:49 +00:00
|
|
|
are .sln12, .sln24, .sln32, .sln44, .sln48, .sln96, .sln192.
|
2011-10-17 16:18:48 +00:00
|
|
|
* Due to protocol limitations, channel drivers other than SIP (eg. IAX2, MGCP,
|
|
|
|
Skinny, H.323, etc) can still only support the following codecs:
|
|
|
|
Audio: ulaw, alaw, slin, slin16, g719, g722, g723, g726, g726aal2, g729, gsm,
|
|
|
|
siren7, siren14, speex, speex16, ilbc, lpc10, adpcm
|
|
|
|
Video: h261, h263, h263p, h264, mpeg4
|
|
|
|
Image: jpeg, png
|
|
|
|
Text: red, t140
|
Media Project Phase2: SILK 8khz-24khz, SLINEAR 8khz-192khz, SPEEX 32khz, hd audio ConfBridge, and other stuff
-Functional changes
1. Dynamic global format list build by codecs defined in codecs.conf
2. SILK 8khz, 12khz, 16khz, and 24khz with custom attributes defined in codecs.conf
3. Negotiation of SILK attributes in chan_sip.
4. SPEEX 32khz with translation
5. SLINEAR 8khz, 12khz, 24khz, 32khz, 44.1khz, 48khz, 96khz, 192khz with translation
using codec_resample.c
6. Various changes to RTP code required to properly handle the dynamic format list
and formats with attributes.
7. ConfBridge now dynamically jumps to the best possible sample rate. This allows
for conferences to take advantage of HD audio (Which sounds awesome)
8. Audiohooks are no longer limited to 8khz audio, and most effects have been
updated to take advantage of this such as Volume, DENOISE, PITCH_SHIFT.
9. codec_resample now uses its own code rather than depending on libresample.
-Organizational changes
Global format list is moved from frame.c to format.c
Various format specific functions moved from frame.c to format.c
Review: https://reviewboard.asterisk.org/r/1104/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@308582 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2011-02-22 23:04:49 +00:00
|
|
|
|
2011-04-21 18:11:40 +00:00
|
|
|
ConfBridge
|
|
|
|
--------------------------
|
|
|
|
* New highly optimized and customizable ConfBridge application capable of
|
|
|
|
mixing audio at sample rates ranging from 8khz-96khz.
|
|
|
|
* CONFBRIDGE dialplan function capable of creating dynamic ConfBridge user
|
|
|
|
and bridge profiles on a channel.
|
2012-07-23 21:27:56 +00:00
|
|
|
* CONFBRIDGE_INFO dialplan function capable of retrieving information
|
2011-06-15 13:45:41 +00:00
|
|
|
about a conference such as locked status and number of parties, admins,
|
|
|
|
and marked users.
|
2011-06-30 20:33:15 +00:00
|
|
|
* Addition of video_mode option in confbridge.conf for adding video support
|
|
|
|
into a bridge profile.
|
2011-07-07 19:57:06 +00:00
|
|
|
* Addition of the follow_talker video_mode in confbridge.conf. This video
|
|
|
|
mode dynamically switches the video feed to always display the loudest talker
|
|
|
|
supplying video in the conference.
|
2011-04-21 18:11:40 +00:00
|
|
|
|
2011-01-13 16:27:22 +00:00
|
|
|
Dialplan Variables
|
|
|
|
------------------
|
|
|
|
* Added ASTETCDIR, ASTMODDIR, ASTVARLIBDIR, ASTDBDIR, ASTKEYDIR, ASTDATADIR,
|
|
|
|
ASTAGIDIR, ASTSPOOLDIR, ASTRUNDIR, ASTLOGDIR which hold the equivalent
|
|
|
|
variables from asterisk.conf.
|
|
|
|
|
Add DB_KEYS.
Discussion on #asterisk on 2011-01-19:
(02:07:03 PM) boch: i wonder how to cycle all entries in a tree
(02:07:11 PM) leifmadsen: use While()
(02:07:17 PM) leifmadsen: you need to know the tree structure already though
(02:07:36 PM) boch: what you mean?
(02:09:02 PM) leifmadsen: you need to know the structure prior to looping, because you can't just return the structure from the dialplan
(02:09:43 PM) leifmadsen: the only way I can think of doing that is via something like writing the output of: asterisk -rx "database show" to a file, then looping through that to know the structure of the database and check everything
(02:09:59 PM) leifmadsen: but at that point you're better off just using either a relational database or an external script
(02:10:13 PM) boch: for example i need to know all entries in the tree
(02:10:15 PM) boch: got it
(02:10:20 PM) leifmadsen: exactly
(02:10:22 PM) leifmadsen: that's the problem
(02:10:22 PM) boch: thank you
(02:13:09 PM) mateu: yeah, i'm surprised there isn't something from the dialplan like 'database show family' so one can get all keys in a family to loop over.
(02:15:35 PM) leifmadsen: database shows everything
(02:16:22 PM) mateu: i mean something from the dial plan that mimics 'database show <family>'
(02:16:41 PM) leifmadsen: guess no one has found that important enough to program :)
(02:16:52 PM) leifmadsen: at that point you should probably just use a relational database...
(02:17:10 PM) mateu: i dunno
(02:17:16 PM) mateu: seems pretty basic to me.
(02:17:16 PM) leifmadsen: me either
(02:17:19 PM) leifmadsen: sure does
(02:17:24 PM) leifmadsen: no one has programmed it though
(02:17:28 PM) ***leifmadsen shrugs
(02:17:43 PM) mateu: ok, well at least we know how it currently stands. thanks leifmadsen
(02:28:52 PM) Corydon76-home: leifmadsen: something like HASHKEYS() ?
(02:30:11 PM) leifmadsen: Corydon76-home: ummm, I was thinking more like DUNDI_QUERY() and DUNDI_RESULT()
(02:30:31 PM) leifmadsen: although HASHKEYS() might work
(02:30:58 PM) leifmadsen: actually ya, looking at it, similar to HASHKEYS()
(02:31:01 PM) leifmadsen: DBKEYS() I guess?
(02:31:45 PM) Corydon76-home: So with no argument, retrieves families, with an argument, retrieves keys of that family?
(02:34:02 PM) leifmadsen: ya
(02:34:16 PM) leifmadsen: how would you iterate through layers of them?
(02:34:30 PM) leifmadsen: i.e. family/key/key/key ?
(02:34:43 PM) Corydon76-home: Essentially, yes
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@303198 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2011-01-21 08:13:18 +00:00
|
|
|
Dialplan Functions
|
|
|
|
------------------
|
2011-04-20 20:52:15 +00:00
|
|
|
* Addition of the JITTERBUFFER dialplan function. This function allows
|
|
|
|
for jitterbuffering to occur on the read side of a channel. By using
|
|
|
|
this function conference applications such as ConfBridge and MeetMe can
|
|
|
|
have the rx streams jitterbuffered before conference mixing occurs.
|
Add DB_KEYS.
Discussion on #asterisk on 2011-01-19:
(02:07:03 PM) boch: i wonder how to cycle all entries in a tree
(02:07:11 PM) leifmadsen: use While()
(02:07:17 PM) leifmadsen: you need to know the tree structure already though
(02:07:36 PM) boch: what you mean?
(02:09:02 PM) leifmadsen: you need to know the structure prior to looping, because you can't just return the structure from the dialplan
(02:09:43 PM) leifmadsen: the only way I can think of doing that is via something like writing the output of: asterisk -rx "database show" to a file, then looping through that to know the structure of the database and check everything
(02:09:59 PM) leifmadsen: but at that point you're better off just using either a relational database or an external script
(02:10:13 PM) boch: for example i need to know all entries in the tree
(02:10:15 PM) boch: got it
(02:10:20 PM) leifmadsen: exactly
(02:10:22 PM) leifmadsen: that's the problem
(02:10:22 PM) boch: thank you
(02:13:09 PM) mateu: yeah, i'm surprised there isn't something from the dialplan like 'database show family' so one can get all keys in a family to loop over.
(02:15:35 PM) leifmadsen: database shows everything
(02:16:22 PM) mateu: i mean something from the dial plan that mimics 'database show <family>'
(02:16:41 PM) leifmadsen: guess no one has found that important enough to program :)
(02:16:52 PM) leifmadsen: at that point you should probably just use a relational database...
(02:17:10 PM) mateu: i dunno
(02:17:16 PM) mateu: seems pretty basic to me.
(02:17:16 PM) leifmadsen: me either
(02:17:19 PM) leifmadsen: sure does
(02:17:24 PM) leifmadsen: no one has programmed it though
(02:17:28 PM) ***leifmadsen shrugs
(02:17:43 PM) mateu: ok, well at least we know how it currently stands. thanks leifmadsen
(02:28:52 PM) Corydon76-home: leifmadsen: something like HASHKEYS() ?
(02:30:11 PM) leifmadsen: Corydon76-home: ummm, I was thinking more like DUNDI_QUERY() and DUNDI_RESULT()
(02:30:31 PM) leifmadsen: although HASHKEYS() might work
(02:30:58 PM) leifmadsen: actually ya, looking at it, similar to HASHKEYS()
(02:31:01 PM) leifmadsen: DBKEYS() I guess?
(02:31:45 PM) Corydon76-home: So with no argument, retrieves families, with an argument, retrieves keys of that family?
(02:34:02 PM) leifmadsen: ya
(02:34:16 PM) leifmadsen: how would you iterate through layers of them?
(02:34:30 PM) leifmadsen: i.e. family/key/key/key ?
(02:34:43 PM) Corydon76-home: Essentially, yes
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@303198 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2011-01-21 08:13:18 +00:00
|
|
|
* Added DB_KEYS, which lists the next set of keys in the Asterisk database
|
|
|
|
hierarchy.
|
2011-05-20 16:27:12 +00:00
|
|
|
* Added STRREPLACE function. This function let's the user search a variable
|
|
|
|
for a given string to replace with another string as many times as the
|
|
|
|
user specifies or just throughout the whole string.
|
2011-05-25 15:43:28 +00:00
|
|
|
* Added option to CHANNEL(pickupgroup) allow reading and setting the pickupgroup of channel.
|
2011-09-09 07:28:42 +00:00
|
|
|
* Mark VALID_EXTEN() deprecated in favor of DIALPLAN_EXISTS()
|
2011-10-03 14:40:57 +00:00
|
|
|
* Added extensions to chan_ooh323 in function CHANNEL()
|
Add DB_KEYS.
Discussion on #asterisk on 2011-01-19:
(02:07:03 PM) boch: i wonder how to cycle all entries in a tree
(02:07:11 PM) leifmadsen: use While()
(02:07:17 PM) leifmadsen: you need to know the tree structure already though
(02:07:36 PM) boch: what you mean?
(02:09:02 PM) leifmadsen: you need to know the structure prior to looping, because you can't just return the structure from the dialplan
(02:09:43 PM) leifmadsen: the only way I can think of doing that is via something like writing the output of: asterisk -rx "database show" to a file, then looping through that to know the structure of the database and check everything
(02:09:59 PM) leifmadsen: but at that point you're better off just using either a relational database or an external script
(02:10:13 PM) boch: for example i need to know all entries in the tree
(02:10:15 PM) boch: got it
(02:10:20 PM) leifmadsen: exactly
(02:10:22 PM) leifmadsen: that's the problem
(02:10:22 PM) boch: thank you
(02:13:09 PM) mateu: yeah, i'm surprised there isn't something from the dialplan like 'database show family' so one can get all keys in a family to loop over.
(02:15:35 PM) leifmadsen: database shows everything
(02:16:22 PM) mateu: i mean something from the dial plan that mimics 'database show <family>'
(02:16:41 PM) leifmadsen: guess no one has found that important enough to program :)
(02:16:52 PM) leifmadsen: at that point you should probably just use a relational database...
(02:17:10 PM) mateu: i dunno
(02:17:16 PM) mateu: seems pretty basic to me.
(02:17:16 PM) leifmadsen: me either
(02:17:19 PM) leifmadsen: sure does
(02:17:24 PM) leifmadsen: no one has programmed it though
(02:17:28 PM) ***leifmadsen shrugs
(02:17:43 PM) mateu: ok, well at least we know how it currently stands. thanks leifmadsen
(02:28:52 PM) Corydon76-home: leifmadsen: something like HASHKEYS() ?
(02:30:11 PM) leifmadsen: Corydon76-home: ummm, I was thinking more like DUNDI_QUERY() and DUNDI_RESULT()
(02:30:31 PM) leifmadsen: although HASHKEYS() might work
(02:30:58 PM) leifmadsen: actually ya, looking at it, similar to HASHKEYS()
(02:31:01 PM) leifmadsen: DBKEYS() I guess?
(02:31:45 PM) Corydon76-home: So with no argument, retrieves families, with an argument, retrieves keys of that family?
(02:34:02 PM) leifmadsen: ya
(02:34:16 PM) leifmadsen: how would you iterate through layers of them?
(02:34:30 PM) leifmadsen: i.e. family/key/key/key ?
(02:34:43 PM) Corydon76-home: Essentially, yes
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@303198 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2011-01-21 08:13:18 +00:00
|
|
|
|
2011-01-04 16:38:28 +00:00
|
|
|
libpri channel driver (chan_dahdi) DAHDI changes
|
|
|
|
--------------------------
|
|
|
|
* Added moh_signaling option to specify what to do when the channel's bridged
|
|
|
|
peer puts the ISDN channel on hold.
|
2011-02-04 20:30:48 +00:00
|
|
|
* Added display_send and display_receive options to control how the display ie
|
|
|
|
is handled. To send display text from the dialplan use the SendText()
|
|
|
|
application when the option is enabled.
|
2011-02-07 23:33:44 +00:00
|
|
|
* Added mcid_send option to allow sending a MCID request on a span.
|
2011-01-04 16:38:28 +00:00
|
|
|
|
2011-03-04 23:22:39 +00:00
|
|
|
Calendaring
|
|
|
|
--------------------------
|
|
|
|
* Added setvar option to calendar.conf to allow setting channel variables on
|
|
|
|
notification channels.
|
2011-05-05 23:10:27 +00:00
|
|
|
* Added "calendar show types" CLI command to list registered calendar
|
|
|
|
connectors.
|
2011-03-04 23:22:39 +00:00
|
|
|
|
2011-03-11 18:54:45 +00:00
|
|
|
MixMonitor
|
|
|
|
--------------------------
|
2012-07-23 21:27:56 +00:00
|
|
|
* Added two new options, r and t with file name arguments to record
|
2011-03-11 18:54:45 +00:00
|
|
|
single direction (unmixed) audio recording separate from the bidirectional
|
|
|
|
(mixed) recording. The mixed file name argument is optional now as long
|
|
|
|
as at least one recording option is used.
|
|
|
|
|
2011-03-18 19:05:20 +00:00
|
|
|
FollowMe
|
|
|
|
--------------------------
|
|
|
|
* Added a new option, l, which will disable local call optimization for
|
|
|
|
channels involved with the FollowMe thread. Use this option to improve
|
|
|
|
compatability for a FollowMe call with certain dialplan apps, options, and
|
|
|
|
functions.
|
|
|
|
|
2011-08-24 09:12:23 +00:00
|
|
|
Meetme
|
|
|
|
--------------------------
|
|
|
|
* Added option "k" that will automatically close the conference when there's
|
|
|
|
only one person left when a user exits the conference.
|
|
|
|
|
2011-05-05 23:08:05 +00:00
|
|
|
CEL
|
|
|
|
--------------------------
|
|
|
|
* cel_pgsql now supports the 'extra' column for data added using the
|
|
|
|
CELGenUserEvent() application.
|
|
|
|
|
2011-05-06 18:04:23 +00:00
|
|
|
pbx_lua
|
|
|
|
--------------------------
|
2011-05-06 18:05:52 +00:00
|
|
|
* Support for defining hints has been added to pbx_lua. See the 'hints' table
|
|
|
|
in the sample extensions.lua file for syntax details.
|
2011-05-06 18:04:23 +00:00
|
|
|
* Applications that perform jumps in the dialplan such as Goto will now
|
2011-05-06 18:07:05 +00:00
|
|
|
execute properly. When pbx_lua detects that the context, extension, or
|
2011-07-07 19:57:06 +00:00
|
|
|
priority we are executing on has changed it will immediately return control
|
2011-05-06 18:07:05 +00:00
|
|
|
to the asterisk PBX engine. Currently the engine cannot detect a Goto to
|
|
|
|
the priority after the currently executing priority.
|
2011-05-06 19:23:23 +00:00
|
|
|
* An autoservice is now started by default for pbx_lua channels. It can be
|
|
|
|
stopped and restarted using the autoservice_stop() and autoservice_start()
|
|
|
|
functions.
|
2011-05-06 18:04:23 +00:00
|
|
|
|
2011-06-30 18:22:28 +00:00
|
|
|
res_fax
|
|
|
|
--------------------------
|
|
|
|
* The ReceiveFAXStatus and SendFAXStatus manager events have been consolidated
|
|
|
|
into a FAXStatus event with an 'Operation' header that will be either
|
|
|
|
'send', 'receive', and 'gateway'.
|
|
|
|
* T.38 gateway functionality has been added to res_fax (and res_fax_spandsp).
|
|
|
|
Set FAXOPT(gateway)=yes to enable this functionality on a channel. This
|
|
|
|
feature will handle converting a fax call between an audio T.30 fax terminal
|
|
|
|
and an IFP T.38 fax terminal.
|
|
|
|
|
2011-07-01 16:16:07 +00:00
|
|
|
SIP Changes
|
|
|
|
-----------
|
|
|
|
* Add T38 support for REJECTED state where T.38 Negotiation is explicitly rejected.
|
2011-09-20 16:56:11 +00:00
|
|
|
* Add option encryption_taglen to set auth taglen only 32 and 80 are supported currently.
|
2011-09-22 16:35:20 +00:00
|
|
|
* SIP now generates security events using the Security Events Framework for REGISTER and INVITE.
|
2011-07-01 16:16:07 +00:00
|
|
|
|
|
|
|
Queue changes
|
|
|
|
-------------
|
|
|
|
* Added general option negative_penalty_invalid default off. when set
|
|
|
|
members are seen as invalid/logged out when there penalty is negative.
|
|
|
|
for realtime members when set remove from queue will set penalty to -1.
|
|
|
|
* Added queue option autopausedelay when autopause is enabled it will be
|
|
|
|
delayed for this number of seconds since last successful call if there
|
|
|
|
was no prior call the agent will be autopaused immediately.
|
|
|
|
* Added member option ignorebusy this when set and ringinuse is not
|
|
|
|
will allow per member control of multiple calls as ringinuse does for
|
|
|
|
the Queue.
|
|
|
|
|
2011-07-01 16:36:29 +00:00
|
|
|
Applications
|
|
|
|
------------
|
|
|
|
* Added 'v' option to MeetMe to play voicemail greetings when a user joins/leaves
|
|
|
|
a MeetMe conference
|
2011-09-15 12:50:40 +00:00
|
|
|
* Added 'k' option to MeetMe to automatically kill the conference when there's only
|
|
|
|
one participant left (much like a normal call bridge)
|
2011-09-21 10:46:09 +00:00
|
|
|
* Added extra argument to Originate to set timeout.
|
2011-07-01 16:36:29 +00:00
|
|
|
|
2011-07-06 20:58:12 +00:00
|
|
|
Asterisk Database
|
|
|
|
-----------------
|
|
|
|
* The internal Asterisk database has been switched from Berkeley DB 1.86 to
|
|
|
|
SQLite 3. An existing Berkeley astdb file can be converted with the astdb2sqlite3
|
|
|
|
utility in the UTILS section of menuselect. If an existing astdb is found and no
|
|
|
|
astdb.sqlite3 exists, astdb2sqlite3 will be compiled automatically. Asterisk will
|
|
|
|
convert an existing astdb to the SQLite3 version automatically at runtime.
|
|
|
|
|
2011-07-15 21:01:41 +00:00
|
|
|
Asterisk Modules
|
|
|
|
----------------
|
|
|
|
* Modules marked as deprecated are no longer marked as building by default. Enabling
|
|
|
|
these modules is still available via menuselect.
|
|
|
|
|
2011-09-06 16:08:10 +00:00
|
|
|
IAX2 Changes
|
|
|
|
------------
|
2011-09-21 09:39:13 +00:00
|
|
|
* authdebug is now disabled by default. To enable this functionaility again
|
2011-09-06 16:08:10 +00:00
|
|
|
set authdebug = yes in iax.conf.
|
|
|
|
|
2011-09-21 09:06:22 +00:00
|
|
|
RTP Changes
|
|
|
|
-----------
|
|
|
|
* The rtp.conf setting "strictrtp" is now enabled by default. In previous
|
|
|
|
releases it was disabled.
|
|
|
|
|
2011-09-21 09:39:13 +00:00
|
|
|
PBX Core
|
|
|
|
--------
|
|
|
|
* The PBX core previously made a call with a non-existing extension test for
|
|
|
|
extension s@default and jump there if the extension existed.
|
|
|
|
This was a bad default behaviour and violated the principle of least surprise.
|
|
|
|
It has therefore been changed in this release. It may affect some
|
|
|
|
applications and configurations that rely on this behaviour. Most channel
|
|
|
|
drivers have avoided this for many releases by testing whether the extension
|
|
|
|
called exists before starting the PBX and generating a local error.
|
|
|
|
This behaviour still exists and works as before.
|
|
|
|
|
|
|
|
Extension "s" is used when no extension is given in a channel driver,
|
|
|
|
like immediate answer in DAHDI or calling to a domain with no user part
|
|
|
|
in a SIP uri.
|
|
|
|
|
2009-03-16 20:53:21 +00:00
|
|
|
------------------------------------------------------------------------------
|
2009-10-22 19:10:04 +00:00
|
|
|
--- Functionality changes from Asterisk 1.6.2 to Asterisk 1.8 ----------------
|
2009-03-16 20:53:21 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
2009-03-24 20:01:29 +00:00
|
|
|
SIP Changes
|
|
|
|
-----------
|
2011-11-21 21:09:59 +00:00
|
|
|
* Due to potential username discovery vulnerabilities, the 'nat' setting in sip.conf
|
|
|
|
now defaults to force_rport. It is very important that phones requiring nat=no be
|
|
|
|
specifically set as such instead of relying on the default setting. If at all
|
|
|
|
possible, all devices should have nat settings configured in the general section as
|
|
|
|
opposed to configuring nat per-device.
|
2009-03-24 20:01:29 +00:00
|
|
|
* Added preferred_codec_only option in sip.conf. This feature limits the joint
|
|
|
|
codecs sent in response to an INVITE to the single most preferred codec.
|
2009-04-06 16:15:30 +00:00
|
|
|
* Added SIP_CODEC_OUTBOUND dialplan variable which can be used to set the codec
|
|
|
|
to be used for the outgoing call. It must be one of the codecs configured
|
|
|
|
for the device.
|
2009-04-24 21:22:31 +00:00
|
|
|
* Added tlsprivatekey option to sip.conf. This allows a separate .pem file
|
|
|
|
to be used for holding a private key. If tlsprivatekey is not specified,
|
|
|
|
tlscertfile is searched for both public and private key.
|
2009-04-29 21:13:43 +00:00
|
|
|
* Added tlsclientmethod option to sip.conf. This allows the protocol for
|
|
|
|
outbound client connections to be specified.
|
2009-04-30 21:42:35 +00:00
|
|
|
* The sendrpid parameter has been expanded to include the options
|
|
|
|
'rpid' and 'pai'. Setting sendrpid to 'rpid' will cause Remote-Party-ID
|
|
|
|
header to be sent (equivalent to setting sendrpid=yes) and setting
|
|
|
|
sendrpid to 'pai' will cause P-Asserted-Identity header to be sent.
|
2009-06-16 01:03:22 +00:00
|
|
|
* The 'ignoresdpversion' behavior has been made automatic when the SDP received
|
|
|
|
is in response to a T.38 re-INVITE that Asterisk initiated. In this situation,
|
|
|
|
since the call will fail if Asterisk does not process the incoming SDP, Asterisk
|
|
|
|
will accept the SDP even if the SDP version number is not properly incremented,
|
|
|
|
but will generate a warning in the log indicating that the SIP peer that sent
|
|
|
|
the SDP should have the 'ignoresdpversion' option set.
|
2009-06-26 20:19:49 +00:00
|
|
|
* The 'nat' option has now been been changed to have yes, no, force_rport, and
|
|
|
|
comedia as valid values. Setting it to yes forces RFC 3581 behavior and enables
|
|
|
|
symmetric RTP support. Setting it to no only enables RFC 3581 behavior if the
|
|
|
|
remote side requests it and disables symmetric RTP support. Setting it to
|
|
|
|
force_rport forces RFC 3581 behavior and disables symmetric RTP support.
|
|
|
|
Setting it to comedia enables RFC 3581 behavior if the remote side requests it
|
|
|
|
and enables symmetric RTP support.
|
2009-09-01 23:41:06 +00:00
|
|
|
* Slave SIP channels now set HASH(SIP_CAUSE,<slave-channel-name>) on each
|
|
|
|
response. This permits the master channel to know how each channel dialled
|
2011-08-16 14:41:23 +00:00
|
|
|
in a multi-channel setup resolved in an individual way. This carries a
|
|
|
|
performance penalty and can be disabled in sip.conf using the
|
|
|
|
'storesipcause' option.
|
2009-10-06 22:49:30 +00:00
|
|
|
* Added 'externtcpport' and 'externtlsport' options to allow custom port
|
|
|
|
configuration for the externip and externhost options when tcp or tls is used.
|
2009-10-14 17:48:57 +00:00
|
|
|
* Added support for message body (stored in content variable) to SIP NOTIFY message
|
|
|
|
accessible via AMI and CLI.
|
2009-10-21 15:35:09 +00:00
|
|
|
* Added 'media_address' configuration option which can be used to explicitly specify
|
|
|
|
the IP address to use in the SDP for media (audio, video, and text) streams.
|
2009-10-27 13:30:27 +00:00
|
|
|
* Added 'unsolicited_mailbox' configuration option which specifies the virtual mailbox
|
|
|
|
that the new/old count should be stored on if an unsolicited MWI NOTIFY message is
|
|
|
|
received.
|
2009-11-02 14:57:11 +00:00
|
|
|
* Added 'use_q850_reason' configuration option for generating and parsing
|
|
|
|
if available Reason: Q.850;cause=<cause code> header. It is implemented
|
|
|
|
in some gateways for better passing PRI/SS7 cause codes via SIP.
|
2010-04-09 14:37:50 +00:00
|
|
|
* When dialing SIP peers, a new component may be added to the end of the dialstring
|
|
|
|
to indicate that a specific remote IP address or host should be used when dialing
|
|
|
|
the particular peer. The dialstring format is SIP/peer/exten/host_or_IP.
|
2010-06-08 05:29:08 +00:00
|
|
|
* SRTP SDES support for encrypting calls to/from Asterisk over SIP. The
|
|
|
|
ability to selectively force bridged channels to also be encrypted is also
|
|
|
|
implemented. Branching in the dialplan can be done based on whether or not
|
|
|
|
a channel has secure media and/or signaling.
|
2010-05-20 17:54:02 +00:00
|
|
|
* Added directmediapermit/directmediadeny to limit which peers can send direct media
|
|
|
|
to each other
|
2010-06-02 19:33:56 +00:00
|
|
|
* Added the 'snom_aoc_enabled' option to turn on support for sending Advice of
|
|
|
|
Charge messages to snom phones.
|
2010-06-16 19:03:24 +00:00
|
|
|
* Added support for G.719 media streams.
|
2010-06-17 18:36:06 +00:00
|
|
|
* Added support for 16khz signed linear media streams.
|
2010-07-08 22:08:07 +00:00
|
|
|
* SIP is now able to bind to and communicate with IPv6 addresses. In addition,
|
|
|
|
RTP has been outfitted with the same abilities.
|
2010-07-16 10:00:58 +00:00
|
|
|
* Added support for setting the Max-Forwards: header in SIP requests. Setting is
|
|
|
|
available in device configurations as well as in the dial plan.
|
2010-08-13 20:12:22 +00:00
|
|
|
* Addition of the 'subscribe_network_change' option for turning on and off
|
|
|
|
res_stun_monitor module support in chan_sip.
|
2010-09-03 17:30:04 +00:00
|
|
|
* Addition of the 'auth_options_requests' option for turning on and off
|
|
|
|
authentication for OPTIONS requests in chan_sip.
|
|
|
|
|
2011-11-21 16:40:17 +00:00
|
|
|
Configuration files
|
|
|
|
-------------------
|
|
|
|
* Add #tryinclude statement for config files. This provides the same
|
|
|
|
functionality as the #include statement however an asterisk module will
|
|
|
|
still load if the filename does not exist. Using the #include statement
|
|
|
|
Asterisk will not allow the module to load.
|
2009-03-24 20:01:29 +00:00
|
|
|
|
2009-06-17 21:56:42 +00:00
|
|
|
IAX2 Changes
|
|
|
|
-----------
|
|
|
|
* Added rtsavesysname option into iax.conf to allow the systname to be saved
|
|
|
|
on realtime updates.
|
2010-06-08 05:29:08 +00:00
|
|
|
* Added the ability for chan_iax2 to inform the dialplan whether or not
|
|
|
|
encryption is being used. This interoperates with the SIP SRTP implementation
|
|
|
|
so that a secure SIP call can be bridged to a secure IAX call when the
|
|
|
|
dialplan requires bridged channels to be "secure".
|
2010-08-13 20:12:22 +00:00
|
|
|
* Addition of the 'subscribe_network_change' option for turning on and off
|
|
|
|
res_stun_monitor module support in chan_iax.
|
|
|
|
|
2009-06-17 21:56:42 +00:00
|
|
|
|
2009-09-23 23:38:19 +00:00
|
|
|
MGCP Changes
|
|
|
|
------------
|
|
|
|
* Added ability to preset channel variables on indicated lines with the setvar
|
|
|
|
configuration option. Also, clearvars=all resets the list of variables back
|
|
|
|
to none.
|
2009-11-02 22:29:19 +00:00
|
|
|
* PacketCable NCS 1.0 support has been added for Docsis/Eurodocsis Networks.
|
|
|
|
See configs/res_pktccops.conf for more information.
|
2009-09-23 23:38:19 +00:00
|
|
|
|
2010-10-11 21:44:34 +00:00
|
|
|
XMPP Google Talk/Jingle changes
|
|
|
|
-------------------------------
|
|
|
|
* Added the externip option to gtalk.conf.
|
|
|
|
* Added the stunaddr option to gtalk.conf which allows for the automatic
|
|
|
|
retrieval of the external ip from a stun server.
|
|
|
|
|
2009-03-17 21:28:04 +00:00
|
|
|
Applications
|
2009-03-17 18:06:55 +00:00
|
|
|
------------
|
2010-03-02 21:58:03 +00:00
|
|
|
* Added 'p' option to PickupChan() to allow for picking up channel by the first
|
|
|
|
match to a partial channel name.
|
2009-12-04 20:21:11 +00:00
|
|
|
* Added .m3u support for Mp3Player application.
|
2009-03-17 18:06:55 +00:00
|
|
|
* Added progress option to the app_dial D() option. When progress DTMF is
|
2009-06-27 09:51:45 +00:00
|
|
|
present, those values are sent immediately upon receiving a PROGRESS message
|
2009-03-17 18:06:55 +00:00
|
|
|
regardless if the call has been answered or not.
|
2009-04-09 19:10:02 +00:00
|
|
|
* Added functionality to the app_dial F() option to continue with execution
|
|
|
|
at the current location when no parameters are provided.
|
2009-11-04 21:39:33 +00:00
|
|
|
* Added the 'a' option to app_dial to answer the calling channel before any
|
|
|
|
announcements or macros are executed.
|
|
|
|
* Modified app_dial to set answertime when the called channel answers even if
|
|
|
|
the called channel hangs up during playback of an announcement.
|
2009-12-19 08:59:31 +00:00
|
|
|
* Modified app_dial 'r' option to support an additional parameter to play an
|
|
|
|
indication tone from indications.conf
|
Convert the ast_channel data structure over to the astobj2 framework.
There is a lot that could be said about this, but the patch is a big
improvement for performance, stability, code maintainability,
and ease of future code development.
The channel list is no longer an unsorted linked list. The main container
for channels is an astobj2 hash table. All of the code related to searching
for channels or iterating active channels has been rewritten. Let n be
the number of active channels. Iterating the channel list has gone from
O(n^2) to O(n). Searching for a channel by name went from O(n) to O(1).
Searching for a channel by extension is still O(n), but uses a new method
for doing so, which is more efficient.
The ast_channel object is now a reference counted object. The benefits
here are plentiful. Some benefits directly related to issues in the
previous code include:
1) When threads other than the channel thread owning a channel wanted
access to a channel, it had to hold the lock on it to ensure that it didn't
go away. This is no longer a requirement. Holding a reference is
sufficient.
2) There are places that now require less dealing with channel locks.
3) There are places where channel locks are held for much shorter periods
of time.
4) There are places where dealing with more than one channel at a time becomes
_MUCH_ easier. ChanSpy is a great example of this. Writing code in the
future that deals with multiple channels will be much easier.
Some additional information regarding channel locking and reference count
handling can be found in channel.h, where a new section has been added that
discusses some of the rules associated with it.
Mark Michelson also assisted with the development of this patch. He did the
conversion of ChanSpy and introduced a new API, ast_autochan, which makes it
much easier to deal with holding on to a channel pointer for an extended period
of time and having it get automatically updated if the channel gets masqueraded.
Mark was also a huge help in the code review process.
Thanks to David Vossel for his assistance with this branch, as well. David
did the conversion of the DAHDIScan application by making it become a wrapper
for ChanSpy internally.
The changes come from the svn/asterisk/team/russell/ast_channel_ao2 branch.
Review: http://reviewboard.digium.com/r/203/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@190423 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2009-04-24 14:04:26 +00:00
|
|
|
* Added c() option to app_chanspy. This option allows custom DTMF to be set
|
2009-06-27 09:51:45 +00:00
|
|
|
to cycle through the next available channel. By default this is still '*'.
|
Convert the ast_channel data structure over to the astobj2 framework.
There is a lot that could be said about this, but the patch is a big
improvement for performance, stability, code maintainability,
and ease of future code development.
The channel list is no longer an unsorted linked list. The main container
for channels is an astobj2 hash table. All of the code related to searching
for channels or iterating active channels has been rewritten. Let n be
the number of active channels. Iterating the channel list has gone from
O(n^2) to O(n). Searching for a channel by name went from O(n) to O(1).
Searching for a channel by extension is still O(n), but uses a new method
for doing so, which is more efficient.
The ast_channel object is now a reference counted object. The benefits
here are plentiful. Some benefits directly related to issues in the
previous code include:
1) When threads other than the channel thread owning a channel wanted
access to a channel, it had to hold the lock on it to ensure that it didn't
go away. This is no longer a requirement. Holding a reference is
sufficient.
2) There are places that now require less dealing with channel locks.
3) There are places where channel locks are held for much shorter periods
of time.
4) There are places where dealing with more than one channel at a time becomes
_MUCH_ easier. ChanSpy is a great example of this. Writing code in the
future that deals with multiple channels will be much easier.
Some additional information regarding channel locking and reference count
handling can be found in channel.h, where a new section has been added that
discusses some of the rules associated with it.
Mark Michelson also assisted with the development of this patch. He did the
conversion of ChanSpy and introduced a new API, ast_autochan, which makes it
much easier to deal with holding on to a channel pointer for an extended period
of time and having it get automatically updated if the channel gets masqueraded.
Mark was also a huge help in the code review process.
Thanks to David Vossel for his assistance with this branch, as well. David
did the conversion of the DAHDIScan application by making it become a wrapper
for ChanSpy internally.
The changes come from the svn/asterisk/team/russell/ast_channel_ao2 branch.
Review: http://reviewboard.digium.com/r/203/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@190423 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2009-04-24 14:04:26 +00:00
|
|
|
* Added x() option to app_chanspy. This option allows DTMF to be set to
|
|
|
|
exit the application.
|
2009-06-23 14:54:21 +00:00
|
|
|
* The Voicemail application has been improved to automatically ignore messages
|
|
|
|
that only contain silence.
|
2009-12-14 23:16:00 +00:00
|
|
|
* If you set maxmsg to 0 in voicemail.conf, Voicemail will consider the
|
|
|
|
associated mailbox(es) to be greetings-only.
|
2009-09-17 00:58:10 +00:00
|
|
|
* The ChanSpy application now has the 'S' option, which makes the application
|
2009-06-26 21:48:41 +00:00
|
|
|
automatically exit once it hits a point where no more channels are available
|
|
|
|
to spy on.
|
2009-09-17 00:58:10 +00:00
|
|
|
* The ChanSpy application also now has the 'E' option, which spies on a single
|
|
|
|
channel and exits when that channel hangs up.
|
2009-10-21 15:21:30 +00:00
|
|
|
* The MeetMe application now turns on the DENOISE() function by default, for
|
|
|
|
each participant. In our tests, this has significantly decreased background
|
|
|
|
noise (especially noisy data centers).
|
2009-10-22 19:10:04 +00:00
|
|
|
* Voicemail now permits storage of secrets in a separate file, located in the
|
|
|
|
spool directory of each individual user. The control for this is located in
|
|
|
|
the "passwordlocation" option in voicemail.conf. Please see the sample
|
|
|
|
configuration for more information.
|
2009-11-13 17:22:47 +00:00
|
|
|
* The ChanIsAvail application now exposes the returned cause code using a separate
|
|
|
|
variable, AVAILCAUSECODE, instead of overwriting the device state in AVAILSTATUS.
|
2009-11-24 13:52:21 +00:00
|
|
|
* Added 'd' option to app_followme. This option disables the "Please hold"
|
|
|
|
announcement.
|
2009-12-02 18:35:47 +00:00
|
|
|
* Added 'y' option to app_record. This option enables a mode where any DTMF digit
|
|
|
|
received will terminate recording.
|
2009-12-03 00:38:03 +00:00
|
|
|
* Voicemail now supports per mailbox settings for folders when using IMAP storage.
|
2012-07-23 21:27:56 +00:00
|
|
|
Previously the folder could only be set per context, but has now been extended
|
2009-12-03 00:38:03 +00:00
|
|
|
using the imapfolder option.
|
2010-03-24 18:13:29 +00:00
|
|
|
* Voicemail now supports per mailbox settings for nextaftercmd and minsecs.
|
2009-12-03 22:13:56 +00:00
|
|
|
* Voicemail now allows the pager date format to be specified separately from the
|
|
|
|
email date format.
|
2009-12-07 17:59:46 +00:00
|
|
|
* New applications JabberJoin, JabberLeave, and JabberSendGroup have been added
|
|
|
|
to allow joining, leaving, and sending text to group chats.
|
2009-12-10 17:31:23 +00:00
|
|
|
* MeetMe has a new option 'G' to play an announcement before joining a conference.
|
|
|
|
* Page has a new option 'A(x)' which will playback an announcement simultaneously
|
|
|
|
to all paged phones (and optionally excluding the caller's one using the new
|
|
|
|
option 'n') before the call is bridged.
|
2010-01-05 18:46:19 +00:00
|
|
|
* The 'f' option to Dial has been augmented to take an optional argument. If no
|
|
|
|
argument is provided, the 'f' option works as it always has. If an argument is
|
|
|
|
provided, then the connected party information of all outgoing channels created
|
|
|
|
during the Dial will be set to the argument passed to the 'f' option.
|
2010-02-02 20:32:29 +00:00
|
|
|
* Dial now inherits the GOSUB_RETVAL from the peer, when the U() option runs a
|
|
|
|
Gosub on the peer.
|
2010-02-12 08:30:05 +00:00
|
|
|
* The OSP lookup application adds in/outbound network ID, optional security,
|
|
|
|
number portability, QoS reporting, destination IP port, custom info and service
|
|
|
|
type features.
|
2010-03-02 18:22:05 +00:00
|
|
|
* Added new application VMSayName that will play the recorded name of the voicemail
|
|
|
|
user if it exists, otherwise will play the mailbox number.
|
2010-03-29 14:07:44 +00:00
|
|
|
* Added custom device states to ConfBridge bridges. Use 'confbridge:<name>' to
|
|
|
|
retrieve state for a particular bridge, where <name> is the conference name
|
2010-05-18 19:30:19 +00:00
|
|
|
* app_directory now allows exiting at any time using the operator or pound key.
|
2010-06-01 21:28:19 +00:00
|
|
|
* Voicemail now supports setting a locale per-mailbox.
|
2010-06-21 05:10:06 +00:00
|
|
|
* Two new applications are provided for declining counting phrases in multiple
|
|
|
|
languages. See the application notes for SayCountedNoun and SayCountedAdj for
|
|
|
|
more information.
|
2010-07-07 06:32:39 +00:00
|
|
|
* Voicemail now runs the externnotify script when pollmailboxes is activated and
|
|
|
|
notices a change.
|
2010-07-09 19:32:47 +00:00
|
|
|
* Voicemail now includes rdnis within msgXXXX.txt file.
|
2012-05-03 14:47:58 +00:00
|
|
|
* ExternalIVR now supports IPv6 addresses.
|
2012-05-03 18:43:54 +00:00
|
|
|
* Added 'D' command to ExternalIVR. Details are available on the Asterisk wiki
|
|
|
|
at https://wiki.asterisk.org/wiki/x/oQBB
|
2011-08-16 17:23:08 +00:00
|
|
|
* ParkedCall and Park can now specify the parking lot to use.
|
2009-03-16 20:53:21 +00:00
|
|
|
|
2009-04-03 22:41:46 +00:00
|
|
|
Dialplan Functions
|
|
|
|
------------------
|
2010-04-09 14:37:50 +00:00
|
|
|
* SRVQUERY and SRVRESULT functions added. This can be used to query and iterate
|
|
|
|
over SRV records associated with a specific service. From the CLI, type
|
|
|
|
'core show function SRVQUERY' and 'core show function SRVRESULT' for more
|
|
|
|
details on how these may be used.
|
2010-03-05 20:21:13 +00:00
|
|
|
* PITCH_SHIFT dialplan function added. This function can be used to modify the
|
|
|
|
pitch of a channel's tx and rx audio streams.
|
2009-04-03 22:41:46 +00:00
|
|
|
* Added new dialplan functions CONNECTEDLINE and REDIRECTING which permits
|
|
|
|
setting various connected line and redirecting party information.
|
2009-10-22 16:33:22 +00:00
|
|
|
* CALLERID and CONNECTEDLINE dialplan functions have been extended to
|
|
|
|
support ISDN subaddressing.
|
2010-09-23 18:45:41 +00:00
|
|
|
* The CHANNEL() function now supports the "name" and "checkhangup" options.
|
2009-04-30 21:42:35 +00:00
|
|
|
* For DAHDI channels, the CHANNEL() dialplan function now allows
|
|
|
|
the dialplan to request changes in the configuration of the active
|
|
|
|
echo canceller on the channel (if any), for the current call only.
|
|
|
|
The syntax is:
|
|
|
|
|
|
|
|
exten => s,n,Set(CHANNEL(echocan_mode)=off)
|
|
|
|
|
|
|
|
The possible values are:
|
|
|
|
|
2009-06-27 09:51:45 +00:00
|
|
|
on - normal mode (the echo canceller is actually reinitialized)
|
2009-04-30 21:42:35 +00:00
|
|
|
off - disabled
|
|
|
|
fax - FAX/data mode (NLP disabled if possible, otherwise completely
|
|
|
|
disabled)
|
|
|
|
voice - voice mode (returns from FAX mode, reverting the changes that
|
|
|
|
were made when FAX mode was requested)
|
2009-09-01 23:41:06 +00:00
|
|
|
* Added new dialplan function MASTER_CHANNEL(), which permits retrieving
|
|
|
|
and setting variables on the channel which created the current channel.
|
|
|
|
Administrators should take care to avoid naming conflicts, when multiple
|
|
|
|
channels are dialled at once, especially when used with the Local channel
|
|
|
|
construct (which all could set variables on the master channel). Usage
|
|
|
|
of the HASH() dialplan function, with the key set to the name of the slave
|
|
|
|
channel, is one approach that will avoid conflicts.
|
2009-09-02 06:23:05 +00:00
|
|
|
* Added new dialplan function MUTEAUDIO() for muting inbound and/or outbound
|
|
|
|
audio in a channel.
|
2009-09-07 17:15:37 +00:00
|
|
|
* func_odbc now allows multiple row results to be retrieved without using
|
|
|
|
mode=multirow. If rowlimit is set, then additional rows may be retrieved
|
|
|
|
from the same query by using the name of the function which retrieved the
|
|
|
|
first row as an argument to ODBC_FETCH().
|
2009-11-24 04:58:44 +00:00
|
|
|
* Added JABBER_RECEIVE, which permits receiving XMPP messages from the
|
|
|
|
dialplan. This function returns the content of the received message.
|
|
|
|
* Added REPLACE, which searches a given variable name for a set of characters,
|
|
|
|
then either replaces them with a single character or deletes them.
|
|
|
|
* Added PASSTHRU, which literally passes the same argument back as its return
|
|
|
|
value. The intent is to be able to use a literal string argument to
|
|
|
|
functions that currently require a variable name as an argument.
|
2010-01-18 19:26:07 +00:00
|
|
|
* HASH-associated variables now can be inherited across channel creation, by
|
|
|
|
prefixing the name of the hash at assignment with the appropriate number of
|
|
|
|
underscores, just like variables.
|
2010-02-17 19:51:53 +00:00
|
|
|
* GROUP_MATCH_COUNT has been improved to allow regex matching on category
|
2010-06-08 05:29:08 +00:00
|
|
|
* CHANNEL(secure_bridge_signaling) and CHANNEL(secure_bridge_media) to set/get
|
|
|
|
whether or not channels that are bridged to the current channel will be
|
|
|
|
required to have secure signaling and/or media.
|
|
|
|
* CHANNEL(secure_signaling) and CHANNEL(secure_media) to get whether or not
|
|
|
|
the current channel has secure signaling and/or media.
|
2010-06-02 21:05:32 +00:00
|
|
|
* For DAHDI/ISDN channels, the CHANNEL() dialplan function now supports the
|
|
|
|
"no_media_path" option.
|
|
|
|
Returns "0" if there is a B channel associated with the call.
|
|
|
|
Returns "1" if no B channel is associated with the call. The call is either
|
|
|
|
on hold or is a call waiting call.
|
2010-06-08 23:48:17 +00:00
|
|
|
* Added option to dialplan function CDR(), the 'f' option
|
|
|
|
allows for high resolution times for billsec and duration fields.
|
2010-07-13 18:31:41 +00:00
|
|
|
* FILE() now supports line-mode and writing.
|
2010-08-03 20:29:51 +00:00
|
|
|
* Added FIELDNUM(), which returns the 1-based offset of a field in a list.
|
2010-09-20 22:16:37 +00:00
|
|
|
* FRAME_TRACE(), for tracking internal ast_frames on a channel.
|
2009-03-17 21:28:04 +00:00
|
|
|
|
2009-08-26 23:13:19 +00:00
|
|
|
Dialplan Variables
|
|
|
|
------------------
|
|
|
|
* Added DYNAMIC_FEATURENAME which holds the last triggered dynamic feature.
|
|
|
|
* Added DYNAMIC_PEERNAME which holds the unique channel name on the other side
|
|
|
|
and is set when a dynamic feature is triggered.
|
2010-02-17 18:29:48 +00:00
|
|
|
* Added PARKINGLOT which can be used with parkeddynamic feature.conf option
|
|
|
|
to dynamically create a new parking lot matching the value this varible is
|
|
|
|
set to.
|
|
|
|
* Added PARKINGDYNAMIC which represents the template parkinglot defined in
|
|
|
|
features.conf that should be the base for dynamic parkinglots.
|
|
|
|
* Added PARKINGDYNCONTEXT which tells what context a newly created dynamic
|
|
|
|
parkinglot should have.
|
2011-08-16 17:23:08 +00:00
|
|
|
* Added PARKINGDYNEXTEN which tells what parking exten a newly created dynamic
|
|
|
|
parkinglot should have.
|
2010-02-17 18:29:48 +00:00
|
|
|
* Added PARKINGDYNPOS which holds what parking positions a dynamic parkinglot
|
|
|
|
should have.
|
2009-08-26 23:13:19 +00:00
|
|
|
|
2009-04-03 22:41:46 +00:00
|
|
|
Queue changes
|
|
|
|
-------------
|
2010-07-10 14:48:03 +00:00
|
|
|
* Added "ready" option to QUEUE_MEMBER counting to count free agents whose wrap-up
|
|
|
|
timeout has expired.
|
|
|
|
* Added 'R' option to app_queue. This option stops moh and indicates ringing
|
|
|
|
to the caller when an Agent's phone is ringing. This can be used to indicate
|
|
|
|
to the caller that their call is about to be picked up, which is nice when
|
|
|
|
one has been on hold for an extened period of time.
|
|
|
|
* A new config option, penaltymemberslimit, has been added to queues.conf.
|
|
|
|
When set this option will disregard penalty settings when a queue has too
|
|
|
|
few members.
|
|
|
|
* A new option, 'I' has been added to both app_queue and app_dial.
|
|
|
|
By setting this option, Asterisk will not update the caller with
|
|
|
|
connected line changes or redirecting party changes when they occur.
|
2011-09-07 08:17:24 +00:00
|
|
|
* A 'relative-periodic-announce' option has been added to queues.conf. When
|
2010-07-10 14:48:03 +00:00
|
|
|
enabled, this option will cause periodic announce times to be calculated
|
|
|
|
from the end of announcements rather than from the beginning.
|
|
|
|
* The autopause option in queues.conf can be passed a new value, "all." The
|
|
|
|
result is that if a member becomes auto-paused, he will be paused in all
|
|
|
|
queues for which he is a member, not just the queue that failed to reach
|
|
|
|
the member.
|
2010-07-16 09:25:48 +00:00
|
|
|
* Added dialplan function QUEUE_EXISTS to check if a queue exists
|
2010-07-20 23:23:25 +00:00
|
|
|
* The queue logger now allows events to optionally propagate to a file,
|
|
|
|
even when realtime logging is turned on. Additionally, realtime logging
|
|
|
|
supports sending the event arguments to 5 individual fields, although it
|
|
|
|
will fallback to the previous data definition, if the new table layout is
|
|
|
|
not found.
|
2009-04-03 22:41:46 +00:00
|
|
|
|
|
|
|
mISDN channel driver (chan_misdn) changes
|
|
|
|
----------------------------------------
|
2010-07-10 14:48:03 +00:00
|
|
|
* Added display_connected parameter to misdn.conf to put a display string
|
|
|
|
in the CONNECT message containing the connected name and/or number if
|
|
|
|
the presentation setting permits it.
|
|
|
|
* Added display_setup parameter to misdn.conf to put a display string
|
|
|
|
in the SETUP message containing the caller name and/or number if the
|
|
|
|
presentation setting permits it.
|
|
|
|
* Made misdn.conf parameters localdialplan and cpndialplan take a -1 to
|
|
|
|
indicate the dialplan settings are to be obtained from the asterisk
|
|
|
|
channel.
|
|
|
|
* Made misdn.conf parameter callerid accept the "name" <number> format
|
|
|
|
used by the rest of the system.
|
|
|
|
* Made use the nationalprefix and internationalprefix misdn.conf
|
|
|
|
parameters to prefix any received number from the ISDN link if that
|
|
|
|
number has the corresponding Type-Of-Number. NOTE: This includes
|
|
|
|
comparing the incoming call's dialed number against the MSN list.
|
|
|
|
* Added the following new parameters: unknownprefix, netspecificprefix,
|
|
|
|
subscriberprefix, and abbreviatedprefix in misdn.conf to prefix any
|
|
|
|
received number from the ISDN link if that number has the corresponding
|
|
|
|
Type-Of-Number.
|
|
|
|
* Added new dialplan application misdn_command which permits controlling
|
|
|
|
the CCBS/CCNR functionality.
|
|
|
|
* Added new dialplan function mISDN_CC which permits retrieval of various
|
|
|
|
values from an active call completion record.
|
|
|
|
* For PTP, you should manually send the COLR of the redirected-to party
|
|
|
|
for an incomming redirected call if the incoming call could experience
|
|
|
|
further redirects. Just set the REDIRECTING(to-num,i) = ${EXTEN} and
|
|
|
|
set the REDIRECTING(to-pres) to the COLR. A call has been redirected
|
|
|
|
if the REDIRECTING(from-num) is not empty.
|
|
|
|
* For outgoing PTP redirected calls, you now need to use the inhibit(i)
|
|
|
|
option on all of the REDIRECTING statements before dialing the
|
|
|
|
redirected-to party. You still have to set the REDIRECTING(to-xxx,i)
|
|
|
|
and the REDIRECTING(from-xxx,i) values. The PTP call will update the
|
|
|
|
redirecting-to presentation (COLR) when it becomes available.
|
|
|
|
* Added outgoing_colp parameter to misdn.conf to filter outgoing COLP
|
|
|
|
information.
|
2009-04-03 22:41:46 +00:00
|
|
|
|
2009-04-21 17:44:01 +00:00
|
|
|
thirdparty mISDN enhancements
|
|
|
|
-----------------------------
|
|
|
|
mISDN has been modified by Digium, Inc. to greatly expand facility message
|
|
|
|
support to allow:
|
|
|
|
* Enhanced COLP support for call diversion and transfer.
|
|
|
|
* CCBS/CCNR support.
|
|
|
|
|
|
|
|
The latest modified mISDN v1.1.x based version is available at:
|
|
|
|
http://svn.digium.com/svn/thirdparty/mISDN/trunk
|
|
|
|
http://svn.digium.com/svn/thirdparty/mISDNuser/trunk
|
|
|
|
|
2009-05-02 19:02:22 +00:00
|
|
|
Tagged versions of the modified mISDN code are available under:
|
2009-04-21 17:44:01 +00:00
|
|
|
http://svn.digium.com/svn/thirdparty/mISDN/tags
|
|
|
|
http://svn.digium.com/svn/thirdparty/mISDNuser/tags
|
2009-04-03 22:41:46 +00:00
|
|
|
|
2009-08-18 23:53:55 +00:00
|
|
|
libpri channel driver (chan_dahdi) DAHDI changes
|
|
|
|
-------------------------------------------
|
|
|
|
* The channel variable PRIREDIRECTREASON is now just a status variable
|
|
|
|
and it is also deprecated. Use the REDIRECTING(reason) dialplan function
|
|
|
|
to read and alter the reason.
|
|
|
|
* For Q.SIG and ETSI PRI/BRI-PTP, you should manually send the COLR of the
|
|
|
|
redirected-to party for an incomming redirected call if the incoming call
|
|
|
|
could experience further redirects. Just set the
|
|
|
|
REDIRECTING(to-num,i) = CALLERID(dnid) and set the REDIRECTING(to-pres)
|
|
|
|
to the COLR. A call has been redirected if the REDIRECTING(count) is not
|
|
|
|
zero.
|
|
|
|
* For outgoing Q.SIG and ETSI PRI/BRI-PTP redirected calls, you need to
|
|
|
|
use the inhibit(i) option on all of the REDIRECTING statements before
|
|
|
|
dialing the redirected-to party. You still have to set the
|
|
|
|
REDIRECTING(to-xxx,i) and the REDIRECTING(from-xxx,i) values. The call
|
|
|
|
will update the redirecting-to presentation (COLR) when it becomes available.
|
2009-09-02 23:25:33 +00:00
|
|
|
* Added the ability to ignore calls that are not in a Multiple Subscriber
|
|
|
|
Number (MSN) list for PTMP CPE interfaces.
|
2009-10-20 12:44:09 +00:00
|
|
|
* Added dynamic range compression support for dahdi channels. It is
|
|
|
|
configured via the rxdrc and txdrc parameters in chan_dahdi.conf.
|
2009-10-22 16:33:22 +00:00
|
|
|
* Added support for ISDN calling and called subaddress with partial support
|
|
|
|
for connected line subaddress.
|
2009-10-23 16:57:33 +00:00
|
|
|
* Added support for BRI PTMP NT mode. (Requires latest LibPRI.)
|
|
|
|
* Added handling of received HOLD/RETRIEVE messages and the optional ability
|
|
|
|
to transfer a held call on disconnect similar to an analog phone.
|
|
|
|
* Added CallRerouting/CallDeflection support for Q.SIG, ETSI PTP, ETSI PTMP.
|
|
|
|
Will reroute/deflect an outgoing call when receive the message.
|
|
|
|
Can use the DAHDISendCallreroutingFacility to send the message for the
|
|
|
|
supported switches.
|
2009-11-06 22:32:17 +00:00
|
|
|
* Added standard location to add options to chan_dahdi dialing:
|
|
|
|
Dial(DAHDI/g1[/extension[/options]])
|
|
|
|
Current options:
|
|
|
|
K(<keypad_digits>)
|
|
|
|
R Reverse charging indication
|
|
|
|
* Added Reverse Charging Indication (Collect calls) send/receive option.
|
|
|
|
Send reverse charging in SETUP message with the chan_dahdi R dialing option.
|
|
|
|
Dial(DAHDI/g1/extension/R)
|
|
|
|
Access received reverse charge in SETUP message by: ${CHANNEL(reversecharge)}
|
|
|
|
(requires latest LibPRI)
|
2009-10-23 16:57:33 +00:00
|
|
|
* Added ability to send/receive keypad digits in the SETUP message.
|
2009-11-06 22:32:17 +00:00
|
|
|
Send keypad digits in SETUP message with the chan_dahdi K(<keypad_digits>)
|
|
|
|
dialing option. Dial(DAHDI/g1/[extension]/K(<keypad_digits>))
|
2009-10-23 16:57:33 +00:00
|
|
|
Access any received keypad digits in SETUP message by: ${CHANNEL(keypad_digits)}
|
2009-11-06 22:32:17 +00:00
|
|
|
(requires latest LibPRI)
|
2010-06-02 16:14:12 +00:00
|
|
|
* Added ability to send and receive ETSI Explicit Call Transfer (ECT) messages
|
|
|
|
to eliminate tromboned calls. A tromboned call goes out an interface and comes
|
|
|
|
back into the same interface. Tromboned calls happen because of call routing,
|
|
|
|
call deflection, call forwarding, and call transfer.
|
2012-07-23 21:27:56 +00:00
|
|
|
* Added the ability to send and receive ETSI Advice-Of-Charge messages.
|
2010-06-02 21:05:32 +00:00
|
|
|
* Added the ability to support call waiting calls. (The SETUP has no B channel
|
|
|
|
assigned.)
|
2010-06-02 22:28:58 +00:00
|
|
|
* Added Malicious Call ID (MCID) event to the AMI call event class.
|
2010-06-03 00:02:14 +00:00
|
|
|
* Added Message Waiting Indication (MWI) support for ISDN PTMP endpoints (phones).
|
2009-08-18 23:53:55 +00:00
|
|
|
|
2009-04-01 00:39:01 +00:00
|
|
|
Asterisk Manager Interface
|
|
|
|
--------------------------
|
|
|
|
* The Hangup action now accepts a Cause header which may be used to
|
|
|
|
set the channel's hangup cause.
|
2009-04-24 21:22:31 +00:00
|
|
|
* sslprivatekey option added to manager.conf and http.conf. Adds the ability
|
|
|
|
to specify a separate .pem file to hold a private key. By default sslcert
|
|
|
|
is used to hold both the public and private key.
|
2009-04-29 14:39:48 +00:00
|
|
|
* Options in manager.conf and http.conf with the 'ssl' prefix have been replaced
|
|
|
|
for options containing the 'tls' prefix. For example, 'sslenable' is now
|
|
|
|
'tlsenable'. This has been done in effort to keep ssl and tls options consistent
|
|
|
|
across all .conf files. All affected sample.conf files have been modified to
|
|
|
|
reflect this change. Previous options such as 'sslenable' still work,
|
|
|
|
but options with the 'tls' prefix are preferred.
|
2009-09-02 06:23:05 +00:00
|
|
|
* Added a MuteAudio AMI action for muting inbound and/or outbound audio
|
|
|
|
in a channel. (res_mutestream.so)
|
2009-11-13 20:42:03 +00:00
|
|
|
* The configuration file manager.conf now supports a channelvars option, which
|
|
|
|
specifies a list of channel variables to include in each channel-oriented
|
|
|
|
event.
|
2012-07-23 21:27:56 +00:00
|
|
|
* The redirect command now has new parameters ExtraContext, ExtraExtension,
|
2009-12-16 00:31:53 +00:00
|
|
|
and ExtraPriority to allow redirecting the second channel to a different
|
|
|
|
location than the first.
|
2010-02-18 16:34:08 +00:00
|
|
|
* Added new event "JabberStatus" in the Jabber module to monitor buddies
|
|
|
|
status.
|
2010-04-21 12:48:32 +00:00
|
|
|
* Added a "MixMonitorMute" AMI action for muting inbound and/or outbound audio
|
|
|
|
in a MixMonitor recording.
|
2010-04-21 19:02:45 +00:00
|
|
|
* The 'iax2 show peers' output is now similar to the expected output of
|
|
|
|
'sip show peers'.
|
2010-06-02 17:13:53 +00:00
|
|
|
* Added Advice-Of-Charge events (AOC-S, AOC-D, and AOC-E) in the new
|
|
|
|
aoc event class.
|
2010-06-02 19:33:56 +00:00
|
|
|
* Added Advice-Of-Charge manager action, AOCMessage, for generating AOC-D and
|
|
|
|
AOC-E messages on a channel.
|
2010-06-11 18:17:28 +00:00
|
|
|
* A DBGetComplete event now follows a DBGetResponse, to make the DBGet action
|
|
|
|
conform more closely to similar events.
|
2010-06-22 16:29:18 +00:00
|
|
|
* Added a new eventfilter option per user to allow whitelisting and blacklisting
|
|
|
|
of events.
|
2010-09-15 19:23:56 +00:00
|
|
|
* Added optional parkinglot variable for park command.
|
2011-05-25 17:14:11 +00:00
|
|
|
* Added ConnectedLineNum and ConnectedLineName headers to AMI events/responses
|
|
|
|
if CallerIDNum and CallerIDName headers are also present.
|
2009-04-30 21:42:35 +00:00
|
|
|
|
2009-06-26 15:28:53 +00:00
|
|
|
Channel Event Logging
|
|
|
|
---------------------
|
|
|
|
* A new interface, CEL, is introduced here. CEL logs single events, much like
|
|
|
|
the AMI, but it differs from the AMI in that it logs to db backends much
|
|
|
|
like CDR does; is based on the event subsystem introduced by Russell, and
|
|
|
|
can share in all its benefits; allows multiple backends to operate like CDR;
|
|
|
|
is specialized to event data that would be of concern to billing sytems,
|
|
|
|
like CDR. Backends for logging and accounting calls have been produced,
|
|
|
|
but a new CDR backend is still in development.
|
|
|
|
|
2009-05-18 14:54:43 +00:00
|
|
|
CDR
|
|
|
|
---
|
2010-01-05 18:42:36 +00:00
|
|
|
* 'linkedid' and 'peeraccount' are new CDR fields available to CDR aficionados.
|
2009-06-26 15:28:53 +00:00
|
|
|
linkedid is based on uniqueID, but spreads to other channels as transfers, dials,
|
2010-06-05 05:23:02 +00:00
|
|
|
etc are performed. Thus the pieces of CDR can be grouped into multilegged sets.
|
2009-05-18 14:54:43 +00:00
|
|
|
* Multiple files and formats can now be specified in cdr_custom.conf.
|
2009-06-26 22:08:05 +00:00
|
|
|
* cdr_syslog has been added which allows CDRs to be written directly to syslog.
|
|
|
|
See configs/cdr_syslog.conf.sample for more information.
|
2009-11-03 21:21:09 +00:00
|
|
|
* A 'sequence' field has been added to CDRs which can be combined with
|
|
|
|
linkedid or uniqueid to uniquely identify a CDR.
|
2010-06-08 23:48:17 +00:00
|
|
|
* Handling of billsec and duration field has changed. If your table definition
|
|
|
|
specifies those fields as float,double or similar they will now be logged with
|
|
|
|
microsecond accuracy instead of a whole integer.
|
2009-05-18 14:54:43 +00:00
|
|
|
|
2009-06-19 17:40:16 +00:00
|
|
|
Calendaring for Asterisk
|
|
|
|
------------------------
|
|
|
|
* A new set of modules were added supporing calendar integration with Asterisk.
|
|
|
|
Dialplan functions for reading from and writing to calendars are included,
|
|
|
|
as well as the ability to execute dialplan logic upon calendar event notifications.
|
2010-05-24 18:21:20 +00:00
|
|
|
iCalendar, CalDAV, and Exchange Server calendars (via res_calendar_exchange for
|
|
|
|
Exchange Server 2003 with no write or attendee support, and res_calendar_ews for
|
|
|
|
Exchange Server 2007+ with full write and attendee support) are supported (Exchange
|
|
|
|
2003 support does not support forms-based authentication).
|
2009-06-19 17:40:16 +00:00
|
|
|
|
Merge Call completion support into trunk.
From Reviewboard:
CCSS stands for Call Completion Supplementary Services. An admittedly out-of-date
overview of the architecture can be found in the file doc/CCSS_architecture.pdf
in the CCSS branch. Off the top of my head, the big differences between what is
implemented and what is in the document are as follows:
1. We did not end up modifying the Hangup application at all.
2. The document states that a single call completion monitor may be used across
multiple calls to the same device. This proved to not be such a good idea
when implementing protocol-specific monitors, and so we ended up using one
monitor per-device per-call.
3. There are some configuration options which were conceived after the document
was written. These are documented in the ccss.conf.sample that is on this
review request.
For some basic understanding of terminology used throughout this code, see the
ccss.tex document that is on this review.
This implements CCBS and CCNR in several flavors.
First up is a "generic" implementation, which can work over any channel technology
provided that the channel technology can accurately report device state. Call
completion is requested using the dialplan application CallCompletionRequest and can
be canceled using CallCompletionCancel. Device state subscriptions are used in order
to monitor the state of called parties.
Next, there is a SIP-specific implementation of call completion. This method uses the
methods outlined in draft-ietf-bliss-call-completion-06 to implement call completion
using SIP signaling. There are a few things to note here:
* The agent/monitor terminology used throughout Asterisk sometimes is the reverse of
what is defined in the referenced draft.
* Implementation of the draft required support for SIP PUBLISH. I attempted to write
this in a generic-enough fashion such that if someone were to want to write PUBLISH
support for other event packages, such as dialog-state or presence, most of the effort
would be in writing callbacks specific to the event package.
* A subportion of supporting PUBLISH reception was that we had to implement a PIDF
parser. The PIDF support added is a bit minimal. I first wrote a validation
routine to ensure that the PIDF document is formatted properly. The rest of the
PIDF reading is done in-line in the call-completion-specific PUBLISH-handling
code. In other words, while there is PIDF support here, it is not in any state
where it could easily be applied to other event packages as is.
Finally, there are a variety of ISDN-related call completion protocols supported. These
were written by Richard Mudgett, and as such I can't really say much about their
implementation. There are notes in the CHANGES file that indicate the ISDN protocols
over which call completion is supported.
Review: https://reviewboard.asterisk.org/r/523
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@256528 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2010-04-09 15:31:32 +00:00
|
|
|
Call Completion Supplementary Services for Asterisk
|
|
|
|
---------------------------------------------------
|
|
|
|
* Call completion support has been added for SIP, DAHDI/ISDN, and DAHDI/analog.
|
|
|
|
DAHDI/ISDN supports call completion for the following switch types:
|
|
|
|
EuroIsdn(ETSI) for PTP and PTMP modes, and Qsig.
|
2012-05-03 18:43:54 +00:00
|
|
|
See https://wiki.asterisk.org/wiki/x/2ABQ for details.
|
Merge Call completion support into trunk.
From Reviewboard:
CCSS stands for Call Completion Supplementary Services. An admittedly out-of-date
overview of the architecture can be found in the file doc/CCSS_architecture.pdf
in the CCSS branch. Off the top of my head, the big differences between what is
implemented and what is in the document are as follows:
1. We did not end up modifying the Hangup application at all.
2. The document states that a single call completion monitor may be used across
multiple calls to the same device. This proved to not be such a good idea
when implementing protocol-specific monitors, and so we ended up using one
monitor per-device per-call.
3. There are some configuration options which were conceived after the document
was written. These are documented in the ccss.conf.sample that is on this
review request.
For some basic understanding of terminology used throughout this code, see the
ccss.tex document that is on this review.
This implements CCBS and CCNR in several flavors.
First up is a "generic" implementation, which can work over any channel technology
provided that the channel technology can accurately report device state. Call
completion is requested using the dialplan application CallCompletionRequest and can
be canceled using CallCompletionCancel. Device state subscriptions are used in order
to monitor the state of called parties.
Next, there is a SIP-specific implementation of call completion. This method uses the
methods outlined in draft-ietf-bliss-call-completion-06 to implement call completion
using SIP signaling. There are a few things to note here:
* The agent/monitor terminology used throughout Asterisk sometimes is the reverse of
what is defined in the referenced draft.
* Implementation of the draft required support for SIP PUBLISH. I attempted to write
this in a generic-enough fashion such that if someone were to want to write PUBLISH
support for other event packages, such as dialog-state or presence, most of the effort
would be in writing callbacks specific to the event package.
* A subportion of supporting PUBLISH reception was that we had to implement a PIDF
parser. The PIDF support added is a bit minimal. I first wrote a validation
routine to ensure that the PIDF document is formatted properly. The rest of the
PIDF reading is done in-line in the call-completion-specific PUBLISH-handling
code. In other words, while there is PIDF support here, it is not in any state
where it could easily be applied to other event packages as is.
Finally, there are a variety of ISDN-related call completion protocols supported. These
were written by Richard Mudgett, and as such I can't really say much about their
implementation. There are notes in the CHANGES file that indicate the ISDN protocols
over which call completion is supported.
Review: https://reviewboard.asterisk.org/r/523
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@256528 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2010-04-09 15:31:32 +00:00
|
|
|
|
2009-06-25 18:25:24 +00:00
|
|
|
Multicast RTP Support
|
|
|
|
---------------------
|
|
|
|
* A new RTP engine and channel driver have been added which supports Multicast RTP.
|
|
|
|
The channel driver can be used with the Page application to perform multicast RTP
|
|
|
|
paging. The dial string format is: MulticastRTP/<type>/<destination>/<control address>
|
|
|
|
Type can be either basic or linksys.
|
|
|
|
Destination is the IP address and port for the RTP packets.
|
|
|
|
Control address is specific to the linksys type and is used for sending the control
|
|
|
|
packets unique to them.
|
|
|
|
|
2009-07-11 19:30:19 +00:00
|
|
|
Security Events Framework
|
|
|
|
-------------------------
|
|
|
|
* Asterisk has a new C API for reporting security events. The module res_security_log
|
|
|
|
sends these events to the "security" logger level. Currently, AMI is the only
|
|
|
|
Asterisk component that reports security events. However, SIP support will be
|
|
|
|
coming soon. For more information on the security events framework, see the
|
2012-05-03 18:43:54 +00:00
|
|
|
"Asterisk Security Framework" section of the Asterisk wiki at
|
|
|
|
https://wiki.asterisk.org/wiki/x/wgBQ
|
2012-04-16 21:20:50 +00:00
|
|
|
* SIP support was added in Asterisk 10
|
|
|
|
* This API now supports IPv6 addresses
|
2009-07-11 19:30:19 +00:00
|
|
|
|
2010-03-03 15:39:45 +00:00
|
|
|
Fax
|
|
|
|
---
|
|
|
|
* A technology independent fax frontend (res_fax) has been added to Asterisk.
|
|
|
|
* A spandsp based fax backend (res_fax_spandsp) has been added.
|
|
|
|
* The app_fax module has been deprecated in favor of the res_fax module and
|
|
|
|
the new res_fax_spandsp backend.
|
2010-07-26 23:35:03 +00:00
|
|
|
* The SendFAX and ReceiveFAX applications now send their log messages to a
|
|
|
|
'fax' logger level, instead of to the generic logger levels. To see these
|
|
|
|
messages, the system's logger.conf file will need to direct the 'fax' logger
|
|
|
|
level to one or more destinations; the logger.conf.sample file includes an
|
|
|
|
example of how to do this. Note that if the 'fax' logger level is *not*
|
|
|
|
directed to at least one destination, log messages generated by these
|
|
|
|
applications will be lost, and that if the 'fax' logger level is directed to
|
|
|
|
the console, the 'core set verbose' and 'core set debug' CLI commands will
|
|
|
|
have no effect on whether the messages appear on the console or not.
|
2010-03-03 15:39:45 +00:00
|
|
|
|
2009-09-25 10:54:42 +00:00
|
|
|
Miscellaneous
|
|
|
|
-------------
|
2010-01-18 17:45:18 +00:00
|
|
|
* The transmit_silence_during_record option in asterisk.conf.sample has been removed.
|
|
|
|
Now, in order to enable transmitting silence during record the transmit_silence
|
|
|
|
option should be used. transmit_silence_during_record remains a valid option, but
|
|
|
|
defaults to the behavior of the transmit_silence option.
|
2009-12-22 16:11:47 +00:00
|
|
|
* Addition of the Unit Test Framework API for managing registration and execution
|
|
|
|
of unit tests with the purpose of verifying the operation of C functions.
|
2009-09-25 10:54:42 +00:00
|
|
|
* SendText is now implemented in chan_gtalk and chan_jingle. It will simply send
|
|
|
|
XMPP text messages to the remote JID.
|
2012-07-23 21:27:56 +00:00
|
|
|
* Modules.conf has a new option - "require" - that marks a module as critical for
|
2009-11-13 08:52:28 +00:00
|
|
|
the execution of Asterisk.
|
|
|
|
If one of the required modules fail to load, Asterisk will exit with a return
|
2009-12-02 20:10:07 +00:00
|
|
|
code set to 2.
|
|
|
|
* An 'X' option has been added to the asterisk application which enables #exec support.
|
|
|
|
This allows #exec to be used in asterisk.conf.
|
2009-12-16 20:25:27 +00:00
|
|
|
* jabber.conf supports a new option auth_policy that toggles auto user registration.
|
2010-01-27 18:29:49 +00:00
|
|
|
* A new lockconfdir option has been added to asterisk.conf to protect the
|
2010-01-27 20:06:08 +00:00
|
|
|
configuration directory (/etc/asterisk by default) during reloads.
|
2010-02-17 18:29:48 +00:00
|
|
|
* The parkeddynamic option has been added to features.conf to enable the creation
|
|
|
|
of dynamic parkinglots.
|
2010-03-03 17:37:30 +00:00
|
|
|
* chan_dahdi now supports reporting alarms over AMI either by channel or span via
|
|
|
|
the reportalarms config option.
|
2010-06-09 13:17:43 +00:00
|
|
|
* chan_dahdi supports dialing configuring and dialing by device file name.
|
|
|
|
DAHDI/span-name!local!1 will use /dev/dahdi/span-name/local/1 . Likewise
|
|
|
|
it may appear in chan_dahdi.conf as 'channel => span-name!local!1'.
|
|
|
|
* A new options for chan_dahdi.conf: 'ignore_failed_channels'. Boolean.
|
|
|
|
False by default. If set, chan_dahdi will ignore failed 'channel' entries.
|
|
|
|
Handy for the above name-based syntax as it does not depend on
|
|
|
|
initialization order.
|
2010-05-27 19:25:16 +00:00
|
|
|
* The Realtime dialplan switch now caches entries for 1 second. This provides a
|
|
|
|
significant increase in performance (about 3X) for installations using this switchtype.
|
2010-06-15 17:06:23 +00:00
|
|
|
* Distributed devicestate now supports the use of the XMPP protocol, in addition to
|
2012-05-03 18:43:54 +00:00
|
|
|
AIS. For more information, please see the Distributed Device State section of the
|
|
|
|
Asterisk wiki at https://wiki.asterisk.org/wiki/x/jw4iAQ
|
2010-06-16 19:03:24 +00:00
|
|
|
* The addition of G.719 pass-through support.
|
2010-06-17 17:23:43 +00:00
|
|
|
* Added support for 16khz Speex audio. This can be enabled by using 'allow=speex16'
|
|
|
|
during device configuration.
|
2010-07-10 14:44:18 +00:00
|
|
|
* The UNISTIM channel driver (chan_unistim) has been updated to support devices that
|
|
|
|
have less than 3 lines on the LCD.
|
2010-07-23 16:19:21 +00:00
|
|
|
* Realtime now supports database failover. See the sample extconfig.conf for details.
|
2010-08-12 20:17:17 +00:00
|
|
|
* The addition of improved translation path building for wideband codecs. Sample
|
|
|
|
rate changes during translation are now avoided unless absolutely necessary.
|
2010-08-13 20:12:22 +00:00
|
|
|
* The addition of the res_stun_monitor module for monitoring and reacting to network
|
|
|
|
changes while behind a NAT.
|
2012-10-04 20:21:36 +00:00
|
|
|
* DTMF: Normal and Reverse Twist acceptance values can be set in dsp.conf.
|
|
|
|
DTMF Valid/Invalid number of hits/misses can be set in dsp.conf.
|
|
|
|
These allow support for any Administration. Default is AT&T values.
|
2009-09-25 10:54:42 +00:00
|
|
|
|
2010-03-23 14:22:27 +00:00
|
|
|
CLI Changes
|
|
|
|
-----------
|
|
|
|
* The 'core set debug' and 'core set verbose' commands, in previous versions, could
|
|
|
|
optionally accept a filename, to apply the setting only to the code generated from
|
|
|
|
that source file when Asterisk was built. However, there are some modules in Asterisk
|
|
|
|
that are composed of multiple source files, so this did not result in the behavior
|
|
|
|
that users expected. In this version, 'core set debug' and 'core set verbose'
|
|
|
|
can optionally accept *module* names instead (with or without the .so extension),
|
|
|
|
which applies the setting to the entire module specified, regardless of which source
|
|
|
|
files it was built from.
|
2010-05-05 00:44:37 +00:00
|
|
|
* New 'manager show settings' command showing the current settings loaded from
|
2012-07-23 21:27:56 +00:00
|
|
|
manager.conf.
|
2010-05-19 15:12:18 +00:00
|
|
|
* Added 'all' keyword to the CLI command "channel request hangup" so that you can send
|
|
|
|
the channel hangup request to all channels.
|
2010-08-12 20:44:39 +00:00
|
|
|
* Added a "core reload" CLI command that executes a global reload of Asterisk.
|
2010-03-23 14:22:27 +00:00
|
|
|
|
2008-08-14 18:12:16 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 1.6.1 to Asterisk 1.6.2 -------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
2008-09-30 21:32:53 +00:00
|
|
|
SIP Changes
|
|
|
|
-----------
|
|
|
|
* Added support for SUBSCRIBE/NOTIFY with dialog-info based call pickups.
|
2008-10-01 12:29:18 +00:00
|
|
|
Snom phones use this for call pickup of extensions that the phone is
|
|
|
|
subscribed to.
|
2008-10-23 15:38:26 +00:00
|
|
|
* Added support for setting the domain in the URI for caller of an
|
|
|
|
outbound call by using the SIPFROMDOMAIN channel variable.
|
2008-11-03 15:16:33 +00:00
|
|
|
* Added a new configuration option "remotesecret" for authentication to
|
|
|
|
remote services. For backwards compatibility, "secret" still has the
|
|
|
|
same function as before, but now you can configure both a remote secret and a
|
|
|
|
local secret for mutual authentication.
|
2012-07-23 21:27:56 +00:00
|
|
|
* If the channel variable ATTENDED_TRANSFER_COMPLETE_SOUND is set,
|
2009-01-29 13:24:01 +00:00
|
|
|
the sound will be played to the target of an attended transfer
|
2008-12-16 20:47:31 +00:00
|
|
|
* Added two new configuration options, "qualifygap" and "qualifypeers", which allow
|
|
|
|
finer control over how many peers Asterisk will qualify and the gap between them
|
|
|
|
when all peers need to be qualified at the same time.
|
2008-12-17 18:49:12 +00:00
|
|
|
* Added a new 'ignoresdpversion' option to sip.conf. When this is enabled
|
|
|
|
(either globally or for a specific peer), chan_sip will treat any SDP data
|
|
|
|
it receives as new data and update the media stream accordingly. By
|
|
|
|
default, Asterisk will only modify the media stream if the SDP session
|
|
|
|
version received is different from the current SDP session version. This
|
|
|
|
option is required to interoperate with devices that have non-standard SDP
|
|
|
|
session version implementations (observed with Microsoft OCS). This option
|
2009-01-16 17:09:13 +00:00
|
|
|
is disabled by default.
|
2009-01-13 21:18:13 +00:00
|
|
|
* The parsing of register => lines in sip.conf has been modified to allow a port
|
|
|
|
to be present in the "user" portion. Please see the sip.conf.sample file for more
|
|
|
|
information
|
2009-02-19 00:08:41 +00:00
|
|
|
* Added support for subscribing to MWI on a remote server and making the status available
|
|
|
|
as a mailbox. Please see the sip.conf.sample file for more information.
|
2009-01-15 13:37:46 +00:00
|
|
|
* Added a function to remove SIP headers added in the dialplan before the
|
|
|
|
first INVITE is generated - SIPRemoveHeader()
|
2012-07-23 21:27:56 +00:00
|
|
|
* Channel variables set with setvar= in a device configuration is now
|
2009-01-29 13:24:01 +00:00
|
|
|
set both for inbound and outbound calls.
|
2009-02-13 13:41:52 +00:00
|
|
|
* Added support for ITU G.722.1 and G.722.1C (Siren7 and Siren14) media streams.
|
2008-09-30 21:32:53 +00:00
|
|
|
|
2009-02-24 17:42:37 +00:00
|
|
|
IAX2 changes
|
|
|
|
------------
|
|
|
|
* Added immediate option to iax.conf
|
|
|
|
* Added forceencryption option to iax.conf
|
|
|
|
* Added Encryption and Trunk status to manager command "iaxpeers"
|
|
|
|
|
2008-10-17 06:00:28 +00:00
|
|
|
Skinny Changes
|
|
|
|
--------------
|
2008-12-23 16:04:54 +00:00
|
|
|
* The configuration file now holds separate sections for devices and lines.
|
2008-10-17 06:00:28 +00:00
|
|
|
Please have a look at configs/skinny.conf.sample and change your skinny.conf
|
|
|
|
accordingly.
|
|
|
|
|
2008-11-25 22:45:59 +00:00
|
|
|
DAHDI Changes
|
|
|
|
-------------
|
Add MFC/R2 support for chan_dahdi.
This commit introduces official support for R2 signaling in chan_dahdi. The
modifications to chan_dahdi, and the supporting library, LibOpenR2, were both
written by Moises Silva.
Many users are using this code, or a variant of it, in Asterisk 1.2, 1.4 and 1.6
in Brazil, México and Argentina. An unknown number of users (but at least 1)
are using it in each of the following countries: Colombia, Nepal, Thailand,
Venezuela, Perú, and probably others.
To use this code, LibOpenR2 must be installed from http://www.libopenr2.org/.
Information about configuration can be found in configs/chan_dahdi.conf.sample.
The code committed is the most up to date version, which was being maintained
in svn/asterisk/team/moy/mfcr2/.
I would also like to include a Thank You to the many others that tested this
code beyond those listed in this commit message. These are the names that I
could find in the mantis issue.
(closes issue #12509)
Reported by: moy
Patches:
chan_zap-mfr2.patch uploaded by moy (license 222)
Tested by: moy, korihor, viniciusfontes, Skarmeth, loloski, asbestoshead, titogarrido, heliocoelhojr, konsultex, ncorrare, ecarruda, rtorresduque, PTorres, ychen
Review: http://reviewboard.digium.com/r/40/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@182355 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2009-03-16 20:35:58 +00:00
|
|
|
* chan_dahdi now supports MFC/R2 signaling when Asterisk is compiled with
|
|
|
|
support for LibOpenR2. http://www.libopenr2.org/
|
2008-11-25 22:45:59 +00:00
|
|
|
* The UK option waitfordialtone has been added for use with BT analog
|
|
|
|
lines.
|
2009-02-13 04:22:35 +00:00
|
|
|
* Added a 'faxbuffers' configuration option to chan_dahdi.conf. This option
|
|
|
|
is used in conjunction with the 'faxdetect' configuration option. When
|
|
|
|
'faxbuffers' is used and fax tones are detected, the channel will dynamically
|
|
|
|
switch to the configured faxbuffers policy. For example, to use 6 buffers
|
|
|
|
and a 'full' buffer policy for a fax transmission, add:
|
|
|
|
faxbuffers=>6,full
|
|
|
|
The faxbuffers configuration will be in affect until the call is torn down.
|
2009-04-14 16:49:12 +00:00
|
|
|
* Added service message support for 4ESS/5ESS switches.
|
2008-11-25 22:45:59 +00:00
|
|
|
|
2008-09-05 19:12:03 +00:00
|
|
|
Dialplan Functions
|
|
|
|
------------------
|
2010-05-17 13:05:32 +00:00
|
|
|
* For DAHDI channels, the CHANNEL() dialplan function now
|
|
|
|
supports changing the channel's buffer policy (for the current
|
|
|
|
call only), using this syntax:
|
|
|
|
|
|
|
|
exten => s,n,Set(CHANNEL(buffers)=6,full)
|
|
|
|
|
|
|
|
This would change the channel to the 'full' buffer policy and
|
|
|
|
6 (six) buffers. Possible options for this setting are the same
|
|
|
|
as those in chan_dahdi.conf.
|
2008-09-05 19:12:03 +00:00
|
|
|
* Added a new dialplan function, CURLOPT, which permits setting various
|
|
|
|
options that may be useful with the CURL dialplan function, such as
|
|
|
|
cookies, proxies, connection timeouts, passwords, etc.
|
2008-10-02 17:16:54 +00:00
|
|
|
* Permit the syntax and synopsis fields of the corresponding dialplan
|
|
|
|
functions to be individually set from func_odbc.conf.
|
2008-10-22 22:11:31 +00:00
|
|
|
* Added debugging CLI functions to func_odbc, 'odbc read' and 'odbc write'.
|
2008-10-31 17:18:49 +00:00
|
|
|
* func_odbc now may specify an insert query to execute, when the write query
|
|
|
|
affects 0 rows (usually indicating that no such row exists).
|
2008-11-05 21:58:48 +00:00
|
|
|
* Added a new dialplan function, LISTFILTER, which permits removing elements
|
|
|
|
from a set list, by name. Uses the same general syntax as the existing CUT
|
|
|
|
and FIELDQTY dialplan functions, which also manage lists.
|
2008-11-19 22:01:00 +00:00
|
|
|
* Added REALTIME_FIELD and REALTIME_HASH, which should aid users in better
|
|
|
|
obtaining realtime data from the dialplan.
|
2009-12-09 23:26:50 +00:00
|
|
|
* Added LOCAL_PEEK, which allows access to variables in any stack frame within
|
|
|
|
a subroutine when using the GoSub() and Return() applications.
|
2008-12-19 22:26:16 +00:00
|
|
|
* Added AUDIOHOOK_INHERIT. For information on its use, please see the output
|
|
|
|
of "core show function AUDIOHOOK_INHERIT" from the CLI
|
2009-01-27 22:43:36 +00:00
|
|
|
* Added AES_ENCRYPT. For information on its use, please see the output
|
|
|
|
of "core show function AES_ENCRYPT" from the CLI
|
|
|
|
* Added AES_DECRYPT. For information on its use, please see the output
|
|
|
|
of "core show function AES_DECRYPT" from the CLI
|
2009-02-19 00:26:01 +00:00
|
|
|
* func_odbc now supports database transactions across multiple queries.
|
2008-08-14 18:12:16 +00:00
|
|
|
|
2008-10-03 18:30:39 +00:00
|
|
|
Applications
|
|
|
|
------------
|
|
|
|
* Scheduled meetme conferences may now have their end times extended by
|
|
|
|
using MeetMeAdmin.
|
2008-10-18 03:35:24 +00:00
|
|
|
* app_authenticate now gives the ability to select a prompt other than
|
|
|
|
the default.
|
2008-10-30 02:08:02 +00:00
|
|
|
* app_directory now pays attention to the searchcontexts setting in
|
|
|
|
voicemail.conf and will look through all contexts, if no context is
|
|
|
|
specified in the initial argument.
|
2008-12-18 13:33:34 +00:00
|
|
|
* A new application, Originate, has been introduced, that allows asynchronous
|
|
|
|
call origination from the dialplan.
|
2009-02-23 21:02:18 +00:00
|
|
|
* Voicemail now permits setting the emailsubject and emailbody per mailbox,
|
|
|
|
in addition to the setting in the "general" context.
|
2009-03-05 18:18:27 +00:00
|
|
|
* Added ConfBridge dialplan application which does conference bridges without
|
|
|
|
DAHDI. For information on its use, please see the output of
|
|
|
|
"core show application ConfBridge" from the CLI.
|
2008-10-03 18:30:39 +00:00
|
|
|
|
2008-09-10 15:57:50 +00:00
|
|
|
Miscellaneous
|
|
|
|
-------------
|
2008-12-12 20:12:23 +00:00
|
|
|
* The Asterisk CLI has a new command, "channel redirect", which is similar in
|
|
|
|
operation to the AMI Redirect action.
|
2008-10-10 18:31:38 +00:00
|
|
|
* extensions.conf now allows you to use keyword "same" to define an extension
|
|
|
|
without actually specifying an extension. It uses exactly the same pattern
|
|
|
|
as previously used on the last "exten" line. For example:
|
|
|
|
exten => 123,1,NoOp(something)
|
|
|
|
same => n,SomethingElse()
|
2008-10-16 08:30:32 +00:00
|
|
|
* musiconhold.conf classes of type 'files' can now use relative directory paths,
|
|
|
|
which are interpreted as relative to the astvarlibdir setting in asterisk.conf.
|
2008-11-12 06:46:04 +00:00
|
|
|
* All deprecated CLI commands are removed from the sourcecode. They are now handled
|
|
|
|
by the new clialiases module. See cli_aliases.conf.sample file.
|
2008-12-16 22:57:17 +00:00
|
|
|
* Times within timespecs are now accurate down to the minute. This is a change
|
|
|
|
from historical Asterisk, which only provided timespecs rounded to the nearest
|
|
|
|
even (read: evenly divisible by 2) minute mark.
|
2008-12-15 21:17:07 +00:00
|
|
|
* The realtime switch now supports an option flag, 'p', which disables searches for
|
|
|
|
pattern matches.
|
2008-12-16 22:57:17 +00:00
|
|
|
* In addition to a time range and date range, timespecs now accept a 5th optional
|
|
|
|
argument, timezone. This allows you to perform time checks on alternate
|
|
|
|
timezones, especially if those daylight savings time ranges vary from your
|
|
|
|
machine's native timezone. See GotoIfTime, ExecIfTime, IFTIME(), and timed
|
|
|
|
includes.
|
2009-01-09 23:04:46 +00:00
|
|
|
* The contrib/scripts/ directory now has a script called sip_nat_settings that will
|
|
|
|
give you the correct output for an asterisk box behind nat. It will give you the
|
|
|
|
externhost and localnet settings.
|
2009-02-13 13:41:52 +00:00
|
|
|
* The Asterisk core now supports ITU G.722.1 and G.722.1C media streams, and
|
|
|
|
can connect calls in passthrough mode, as well as record and play back files.
|
2009-02-26 18:41:28 +00:00
|
|
|
* Successful and unsuccessful call pickup can now be alerted through sounds, by
|
|
|
|
using pickupsound and pickupfailsound in features.conf.
|
2009-09-25 10:54:42 +00:00
|
|
|
* ASTVARRUNDIR is now set to $(localstatedir)/run/asterisk by default.
|
2009-03-10 21:15:29 +00:00
|
|
|
This means the asterisk pid file will now be in /var/run/asterisk/asterisk.pid on LINUX
|
|
|
|
instead of the /var/run/asterisk.pid where it used to be. This will make
|
|
|
|
installs as non-root easier to manage.
|
2008-09-10 15:57:50 +00:00
|
|
|
|
2010-06-03 18:53:24 +00:00
|
|
|
CDR
|
|
|
|
---
|
|
|
|
|
|
|
|
* The cdr.conf file must exist and be correctly programmed in order for CDR records to
|
|
|
|
be written; they will no longer be explicitly written.
|
|
|
|
|
2008-11-26 21:09:58 +00:00
|
|
|
Asterisk Manager Interface
|
|
|
|
--------------------------
|
|
|
|
* When using the AMI over HTTP, you can now include a 'SuppressEvents' header (with
|
|
|
|
a non-empty value) in your request. If you do this, any pending AMI events will
|
|
|
|
*not* be included in the response to your request as they would normally, but
|
|
|
|
will be left in the event queue for the next request you make to retrieve. For
|
|
|
|
some applications, this will allow you to guarantee that you will only see
|
|
|
|
events in responses to 'WaitEvent' actions, and can better know when to expect them.
|
|
|
|
To know whether the Asterisk server supports this header or not, your client can
|
|
|
|
inspect the first response back from the server to see if it includes this header:
|
|
|
|
|
|
|
|
Pragma: SuppressEvents
|
|
|
|
|
|
|
|
If this is included, the server supports event suppression.
|
|
|
|
|
2009-02-23 17:48:32 +00:00
|
|
|
* Added 4 new Actions to list skinny device(s) and line(s)
|
|
|
|
SKINNYdevices
|
|
|
|
SKINNYshowdevice
|
|
|
|
SKINNYlines
|
|
|
|
SKINNYshowline
|
|
|
|
|
2009-11-11 14:30:04 +00:00
|
|
|
LDAP Schema File Additions
|
|
|
|
--------------------------
|
|
|
|
* Added AsteriskDialplan, AsteriskAccount and AsteriskMailbox objectClasses
|
|
|
|
to allow standalone dialplan, account and mailbox entries (STRUCTURAL)
|
|
|
|
* Added new Fields:
|
|
|
|
- AstAccountLanguage, AstAccountTransport, AstAccountPromiscRedir,
|
|
|
|
- AstAccountAccountCode, AstAccountSetVar, AstAccountAllowOverlap,
|
|
|
|
- AstAccountVideoSupport, AstAccountIgnoreSDPVersion
|
|
|
|
* Removed redundant IPaddr (there's already IPAddress)
|
|
|
|
- Gives more configuration Flags for SIP-Users available (tested)
|
|
|
|
- Allows to create Asterisk Attributes in defined Asterisk ObjectClasses
|
|
|
|
without extensibleObject (which really should be the last resort); gives
|
2012-07-23 21:27:56 +00:00
|
|
|
also additional possibilities for LDAP-filter
|
2009-11-11 14:30:04 +00:00
|
|
|
|
2007-09-13 21:23:32 +00:00
|
|
|
------------------------------------------------------------------------------
|
2008-03-04 16:55:17 +00:00
|
|
|
--- Functionality changes from Asterisk 1.6.0 to Asterisk 1.6.1 -------------
|
|
|
|
------------------------------------------------------------------------------
|
|
|
|
|
2008-06-10 15:12:17 +00:00
|
|
|
Device State Handling
|
|
|
|
---------------------
|
|
|
|
* The event infrastructure in Asterisk got another big update to help support
|
2012-05-03 18:43:54 +00:00
|
|
|
distributed events. It currently supports distributed device state and
|
|
|
|
distributed Voicemail MWI (Message Waiting Indication). A new module has
|
|
|
|
been merged, res_ais, which facilitates communicating events between servers.
|
|
|
|
It uses the SAForum AIS (Service Availability Forum Application Interface
|
|
|
|
Specification) CLM (Cluster Management) and EVT (Event) services to maintain
|
|
|
|
a cluster of Asterisk servers, and to share events between them. For more
|
|
|
|
information on setting this up, refer to the Distributed Device State section
|
|
|
|
of the Asterisk wiki at https://wiki.asterisk.org/wiki/x/jw4iAQ
|
2008-06-10 15:12:17 +00:00
|
|
|
|
2008-03-11 22:21:19 +00:00
|
|
|
Dialplan Functions
|
|
|
|
------------------
|
|
|
|
* Added a new dialplan function, AST_CONFIG(), which allows you to access
|
|
|
|
variables from an Asterisk configuration file.
|
2008-04-22 16:47:00 +00:00
|
|
|
* The JACK_HOOK function now has a c() option to supply a custom client name.
|
2012-07-23 21:27:56 +00:00
|
|
|
* Added two new dialplan functions from libspeex for audio gain control and
|
|
|
|
denoise, AGC() and DENOISE(). Both functions can be applied to the tx and
|
2008-05-01 16:57:19 +00:00
|
|
|
rx directions of a channel from the dialplan.
|
2008-05-01 19:05:36 +00:00
|
|
|
* The SMDI_MSG_RETRIEVE function now has the ability to search for SMDI messages
|
|
|
|
based on other parameters. The default is still to search based on the
|
|
|
|
forwarding station ID. However, there are new options that allow you to search
|
|
|
|
based on the message desk terminal ID, or the message desk number.
|
2008-05-20 16:25:16 +00:00
|
|
|
* TIMEOUT() has been modified to be accurate down to the millisecond.
|
|
|
|
* ENUM*() functions now include the following new options:
|
|
|
|
- 'u' returns the full URI and does not strip off the URI-scheme.
|
2008-06-10 15:12:17 +00:00
|
|
|
- 's' triggers ISN specific rewriting
|
|
|
|
- 'i' looks for branches into an Infrastructure ENUM tree
|
|
|
|
- 'd' for a direct DNS lookup without any flipping of digits.
|
2008-05-20 16:25:16 +00:00
|
|
|
* TXCIDNAME() has a new zone-suffix parameter (which defaults to 'e164.arpa')
|
2008-06-05 16:41:36 +00:00
|
|
|
* CHANNEL() now has options for the maximum, minimum, and standard or normal
|
|
|
|
deviation of jitter, rtt, and loss for a call using chan_sip.
|
2008-03-04 16:55:17 +00:00
|
|
|
|
2008-07-11 16:18:01 +00:00
|
|
|
DAHDI channel driver (chan_dahdi) Changes
|
2008-03-12 21:37:40 +00:00
|
|
|
----------------------------------------
|
2008-07-11 16:18:01 +00:00
|
|
|
* Channels can now be configured using named sections in chan_dahdi.conf, just
|
2008-03-12 21:37:40 +00:00
|
|
|
like other channel drivers, including the use of templates.
|
2008-05-19 20:06:38 +00:00
|
|
|
* The default for pridialplan has changed from 'national' to 'unknown'.
|
2008-03-12 21:37:40 +00:00
|
|
|
|
2008-03-19 16:54:12 +00:00
|
|
|
PBX Changes
|
|
|
|
-----------
|
|
|
|
* It is now possible to specify a pattern match as a hint. Once a phone subscribes
|
|
|
|
to something that matches the pattern a hint will be created using the contents
|
|
|
|
and variables evaluated.
|
2008-04-30 05:05:25 +00:00
|
|
|
* Dialplan matching has been extended to allow an extension to return to the
|
|
|
|
PBX core to wait for more digits. This is done by using the new dialplan
|
|
|
|
application called "Incomplete". This will permit a whole new level of
|
|
|
|
extension control, by giving the administrator more control over early
|
|
|
|
matches employing one of the short-circuit pattern match operators. Note
|
|
|
|
that custom applications can trigger this same behavior by returning the
|
|
|
|
special value AST_PBX_INCOMPLETE.
|
2008-03-19 16:54:12 +00:00
|
|
|
|
2008-03-21 01:44:38 +00:00
|
|
|
Application Changes
|
|
|
|
-------------------
|
|
|
|
* Directory now permits both first and last names to be matched at the same
|
|
|
|
time. In addition, the number of digits to enter of the name can be set in
|
|
|
|
the arguments to Directory; previously, you could enter only 3, regardless
|
|
|
|
of how many names are in your company. For large companies, this should be
|
|
|
|
quite helpful.
|
2008-04-09 16:23:30 +00:00
|
|
|
* Voicemail now permits a mailbox setting to wrap around from first to last
|
|
|
|
messages, if the "messagewrap" option is set to a true value.
|
2008-05-09 17:28:06 +00:00
|
|
|
* Voicemail now permits an external script to be run, for password validation.
|
|
|
|
The script should output "VALID" or "INVALID" on stdout, depending upon the
|
|
|
|
wish to validate or invalidate the password given. Arguments are:
|
|
|
|
"mailbox" "context" "oldpass" "newpass". See the sample voicemail.conf for
|
|
|
|
more details
|
2008-04-09 16:23:30 +00:00
|
|
|
* Dial has a new option: F(context^extension^pri), which permits a callee to
|
|
|
|
continue in the dialplan, at the specified label, if the caller hangs up.
|
2008-04-17 12:25:23 +00:00
|
|
|
* ChanSpy and ExtenSpy have a new option, 's' which suppresses speaking the
|
|
|
|
technology name (e.g. SIP, IAX, etc) of the channel being spied on.
|
2008-04-22 16:47:00 +00:00
|
|
|
* The Jack application now has a c() option to supply a custom client name.
|
2008-04-25 22:24:32 +00:00
|
|
|
* Chanspy has a new option, 'B', which can be used to "barge" on a call. This is
|
|
|
|
like the pre-existing whisper mode, except that the spy can also talk to the
|
|
|
|
participant on the bridged channel as well.
|
2008-04-28 22:38:07 +00:00
|
|
|
* Chanspy has a new option, 'n', which will allow for the spied-on party's name
|
|
|
|
to be spoken instead of the channel name or number. For more information on the
|
2012-07-23 21:27:56 +00:00
|
|
|
use of this option, issue the command "core show application ChanSpy" from the
|
2008-04-28 22:38:07 +00:00
|
|
|
Asterisk CLI.
|
2008-05-14 22:15:12 +00:00
|
|
|
* Chanspy has a new option, 'd', which allows the spy to use DTMF to swap between
|
|
|
|
spy modes. Use of this feature overrides the typical use of numeric DTMF. In other
|
|
|
|
words, if using the 'd' option, it is not possible to enter a number to append to
|
|
|
|
the first argument to Chanspy(). Pressing 4 will change to spy mode, pressing 5 will
|
|
|
|
change to whisper mode, and pressing 6 will change to barge mode.
|
2008-05-22 05:10:01 +00:00
|
|
|
* ExternalIVR now takes several options that affect the way it performs, as
|
2012-05-03 18:43:54 +00:00
|
|
|
well as having several new commands. Please see the External IVR page on the Asterisk
|
|
|
|
wiki for complete documentation: https://wiki.asterisk.org/wiki/x/oQBB
|
2012-07-23 21:27:56 +00:00
|
|
|
* Added ability to communicate over a TCP socket instead of forking a child process for the
|
2008-10-02 19:27:37 +00:00
|
|
|
ExternalIVR application.
|
2008-05-23 17:12:04 +00:00
|
|
|
* ChanIsAvail has a new option, 'a', which will return all available channels instead
|
|
|
|
of just the first one if you give the function more then one channel to check.
|
2012-07-23 21:27:56 +00:00
|
|
|
* PrivacyManager now takes an option where you can specify a context where the
|
2008-06-08 11:40:44 +00:00
|
|
|
given number will be matched. This way you have more control over who is allowed
|
|
|
|
and it stops the people who blindly enter 10 digits.
|
Merged revisions 122046 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4
........
r122046 | murf | 2008-06-12 07:47:34 -0600 (Thu, 12 Jun 2008) | 37 lines
(closes issue #10668)
Reported by: arkadia
Tested by: murf, arkadia
Options added to forkCDR() app and the CDR() func to
remove some roadblocks for CDR applications.
The "show application ForkCDR" output was upgraded
to more fully explain the inner workings of forkCDR.
The A option was added to forkCDR to force the
CDR system to NOT change the disposition on the
original CDR, after the fork. This involves
ast_cdr_answer, _busy, _failed, and so on.
The T option was added to forkCDR to force
obedience of the cdr LOCKED flag in the
ast_cdr_end, all the disposition changing
funcs (ast_cdr_answer, etc), and in the
ast_cdr_setvar func.
The CHANGES file was updated to explain ALL
the new options added to satisfy this bug report
(and some requests made verbally and via
email, irc, etc, over the past months/year)
The 's' option was added to the CDR() func,
to force it to skip LOCKED cdr's in the
chain.
Again, the new options should be totally transparent
to existing apps! Current behavior of CDR,
forkCDR, and the rest of the CDR system should
not change one little bit. Until you add the
new options, at least!
........
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@122091 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2008-06-12 14:28:01 +00:00
|
|
|
* ForkCDR has new options: 'a' updates the answer time on the new CDR; 'A' locks
|
|
|
|
answer times, disposition, on orig CDR against updates; 'D' Copies the disposition
|
|
|
|
from the orig CDR to the new CDR after reset; 'e' sets the 'end' time on the
|
|
|
|
original CDR; 'R' prevents the new CDR from being reset; 's(var=val)' adds/changes
|
|
|
|
the 'var' variable on the original CDR; 'T' forces ast_cdr_end(), ast_cdr_answer(),
|
2008-06-12 14:56:26 +00:00
|
|
|
obey the LOCKED flag on cdr's in the chain, and also the ast_cdr_setvar() func.
|
2008-06-26 23:35:29 +00:00
|
|
|
* The Dial() application no longer copies the language used by the caller to the callee's
|
|
|
|
channel. If you desire for the caller's channel's language to be used for file playback
|
|
|
|
to the callee, then the file specified may be prepended with "${CHANNEL(language)}/" .
|
2008-07-28 16:49:29 +00:00
|
|
|
* SendImage() no longer hangs up the channel on error; instead, it sets the
|
|
|
|
status variable SENDIMAGESTATUS to one of 'SUCCESS', 'FAILURE', or
|
|
|
|
'UNSUPPORTED'. This change makes SendImage() more consistent with other
|
|
|
|
applications.
|
2008-08-29 17:53:32 +00:00
|
|
|
* Park has a new option, 's', which silences the announcement of the parking space number.
|
2008-10-14 23:57:46 +00:00
|
|
|
* A non-numeric, zero, or negative timeout specified to Dial() will now be interpreted as
|
|
|
|
invalid input and will be assumed to mean that no timeout is desired.
|
2008-03-21 01:44:38 +00:00
|
|
|
|
2008-03-25 15:18:41 +00:00
|
|
|
SIP Changes
|
|
|
|
-----------
|
2008-04-01 22:07:30 +00:00
|
|
|
* Added DNS manager support to registrations for peers referencing peer entries.
|
2012-07-23 21:27:56 +00:00
|
|
|
DNS manager runs in the background which allows DNS lookups to be run asynchronously
|
2008-04-17 21:09:37 +00:00
|
|
|
as well as periodically updating the IP address. These properties allow for
|
|
|
|
better performance as well as recovery in the event of an IP change.
|
2012-07-23 21:27:56 +00:00
|
|
|
* Performance improvements via using hash tables (astobj2) and doubly-linked lists to improve
|
2009-06-27 09:51:45 +00:00
|
|
|
load/reload of large numbers of peers/users by ~40x (for large lists of peers).
|
|
|
|
These changes also provide performance improvements for call setup and tear down.
|
2008-04-30 20:51:17 +00:00
|
|
|
* Added ability to specify registration expiry time on a per registration basis in
|
|
|
|
the register line.
|
2008-05-14 13:37:07 +00:00
|
|
|
* Added support for T140 RED - redundancy in T.140 to prevent text loss due to
|
|
|
|
lost packets.
|
2008-05-28 14:29:01 +00:00
|
|
|
* Added t38pt_usertpsource option. See sip.conf.sample for details.
|
2008-06-06 20:24:11 +00:00
|
|
|
* Added SIPnotify AMI command, for sending arbitrary SIP notify commands.
|
2008-06-17 20:17:20 +00:00
|
|
|
* 'sip show peers' and 'sip show users' display their entries sorted in
|
2012-07-23 21:27:56 +00:00
|
|
|
alphabetical order, as opposed to the order they were in, in the config
|
|
|
|
file or database.
|
2008-07-15 16:20:35 +00:00
|
|
|
* Videosupport now supports an additional option, "always", which always sets
|
|
|
|
up video RTP ports, even on clients that don't support it. This helps with
|
|
|
|
callfiles and certain transfers to ensure that if two video phones are
|
|
|
|
connected, they will always share video feeds.
|
2008-04-01 22:07:30 +00:00
|
|
|
|
|
|
|
IAX Changes
|
|
|
|
-----------
|
|
|
|
* Existing DNS manager lookups extended to check for SRV records.
|
2008-08-01 18:16:24 +00:00
|
|
|
* IAX2 encryption support has been improved to support periodic key rotation
|
|
|
|
within a call for enhanced security. The option "keyrotate" has been
|
|
|
|
provided to disable this functionality to preserve backwards compatibility
|
|
|
|
with older versions of IAX2 that do not support key rotation.
|
2008-03-25 15:18:41 +00:00
|
|
|
|
2008-03-26 19:19:31 +00:00
|
|
|
CLI Changes
|
|
|
|
-----------
|
2010-04-22 18:07:02 +00:00
|
|
|
* New CLI command, "data get <path> [<search> [<filter>]]" which retrieves the
|
|
|
|
data tree based on the given <path>.
|
|
|
|
* New CLI command "data show providers" that will display all the registered
|
|
|
|
callbacks.
|
2008-03-26 19:19:31 +00:00
|
|
|
* New CLI command, "config reload <file.conf>" which reloads any module that
|
|
|
|
references that particular configuration file. Also added "config list"
|
|
|
|
which shows which configuration files are in use.
|
2008-05-01 23:09:08 +00:00
|
|
|
* New CLI commands, "pri show version" and "ss7 show version" that will
|
|
|
|
display which version of libpri and libss7 are being used, respectively.
|
2008-06-10 15:12:17 +00:00
|
|
|
A new API call was added so trunk will now have to be compiled against
|
|
|
|
a versions of libpri and libss7 that have them or it will not know that
|
|
|
|
these libraries exist.
|
2008-07-17 14:00:27 +00:00
|
|
|
* The commands "core show globals", "core set global" and "core set chanvar" has
|
|
|
|
been deprecated in favor of the more semanticly correct "dialplan show globals",
|
|
|
|
"dialplan set chanvar" and "dialplan set global".
|
|
|
|
* New CLI command "dialplan show chanvar" to list all variables associated
|
|
|
|
with a given channel.
|
2008-03-26 19:19:31 +00:00
|
|
|
|
2008-04-01 22:07:30 +00:00
|
|
|
DNS manager changes
|
|
|
|
-------------------
|
|
|
|
* Addresses managed by DNS manager now can check to see if there is a DNS
|
|
|
|
SRV record for a given domain and will use that hostname/port if present.
|
|
|
|
|
2008-05-05 19:33:14 +00:00
|
|
|
AMI - The manager (TCP/TLS/HTTP)
|
|
|
|
--------------------------------
|
|
|
|
* The Status command now takes an optional list of variables to display
|
|
|
|
along with channel status.
|
2008-10-18 00:25:18 +00:00
|
|
|
* The QueueEntry event now also includes the channel's uniqueid
|
2008-05-05 19:33:14 +00:00
|
|
|
|
2008-05-20 16:25:16 +00:00
|
|
|
ODBC Changes
|
|
|
|
------------
|
|
|
|
* res_odbc no longer has a limit of 1023 total possible unshared connections,
|
|
|
|
as some people were running into this limit. This limit has been increased
|
|
|
|
to 4.2 billion.
|
|
|
|
|
2008-06-24 11:02:02 +00:00
|
|
|
Queue changes
|
|
|
|
-------------
|
|
|
|
* The TRANSFER queue log entry now includes the the caller's original
|
|
|
|
position in the transferred-from queue.
|
2008-07-03 14:34:25 +00:00
|
|
|
* A new configuration option, "timeoutpriority" has been added. Please see the section labeled
|
|
|
|
"QUEUE TIMING OPTIONS" in configs/queues.conf.sample for a detailed explanation of the option
|
|
|
|
as well as an explanation about timeout options in general
|
2009-01-28 14:39:26 +00:00
|
|
|
* Added a new option - C - for forcing the "answered elsewhere" flag on
|
|
|
|
cancellation of calls in to members of the queue. This is to avoid the
|
|
|
|
call to a member of a queue having the call listed as a "missed call".
|
2008-06-24 11:02:02 +00:00
|
|
|
|
2008-07-30 17:36:31 +00:00
|
|
|
Realtime changes
|
|
|
|
----------------
|
|
|
|
* Several (ODBC, Postgres, MySQL, SQLite) realtime drivers have been given
|
|
|
|
adaptive capabilities. What this means in practical terms is that if your
|
|
|
|
realtime table lacks critical fields, Asterisk will now emit warnings to
|
|
|
|
that effect. Also, some of the realtime drivers have the ability (if
|
|
|
|
configured) to automatically add those columns to the table with the
|
|
|
|
correct type and length.
|
|
|
|
|
2008-07-30 16:40:43 +00:00
|
|
|
Miscellaneous
|
|
|
|
-------------
|
|
|
|
* The channel variable ATTENDED_TRANSFER_COMPLETE_SOUND can now be set using
|
|
|
|
the 'setvar' option to cause a given audio file to be played upon completion
|
|
|
|
of an attended transfer. Currently it works for DAHDI, IAX2, SIP, and
|
|
|
|
Skinny channels only.
|
2012-05-03 18:43:54 +00:00
|
|
|
* You can now compile Asterisk against the Hoard Memory Allocator, see the
|
|
|
|
Hoard page on the Asterisk wiki for more information:
|
|
|
|
https://wiki.asterisk.org/wiki/x/pQBB
|
2008-08-05 18:25:16 +00:00
|
|
|
* Config file variables may now be appended to, by using the '+=' append
|
|
|
|
operator. This is most helpful when working with long SQL queries in
|
|
|
|
func_odbc.conf, as the queries no longer need to be specified on a single
|
|
|
|
line.
|
2012-07-23 21:27:56 +00:00
|
|
|
* CDR config file, cdr.conf, has an added option, "initiatedseconds",
|
(closes issue #13366)
Reported by: erousseau
This was a reasonable enhancement request, which was
easy to implement. Since it's an enhancement, it
could only be applied to trunk.
Basically, for accounting where "initiated" seconds
are billed for, if the microseconds field on the end
time is greater than the microseconds field for the
answer time, add one second to the billsec field.
The implementation was requested by erousseau, and
I've implemented it as requested. I've updated the
CHANGES, the cdr.conf.sample, and the .h files
accordingly, to accept and set a flag for the
corresponding new option. cdr.c adds in the extra
second based on the usec fields if the option is
set. Tested, seems to be working fine.
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@140057 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2008-08-26 15:57:49 +00:00
|
|
|
which will add a second to the billsec when the ending
|
2012-07-23 21:27:56 +00:00
|
|
|
time is set, if the number in the microseconds field of the end time is
|
(closes issue #13366)
Reported by: erousseau
This was a reasonable enhancement request, which was
easy to implement. Since it's an enhancement, it
could only be applied to trunk.
Basically, for accounting where "initiated" seconds
are billed for, if the microseconds field on the end
time is greater than the microseconds field for the
answer time, add one second to the billsec field.
The implementation was requested by erousseau, and
I've implemented it as requested. I've updated the
CHANGES, the cdr.conf.sample, and the .h files
accordingly, to accept and set a flag for the
corresponding new option. cdr.c adds in the extra
second based on the usec fields if the option is
set. Tested, seems to be working fine.
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@140057 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2008-08-26 15:57:49 +00:00
|
|
|
greater than the number of microseconds in the answer time. This allows
|
2012-07-23 21:27:56 +00:00
|
|
|
users to count the 'initiated' seconds in their billing records.
|
2008-07-30 16:40:43 +00:00
|
|
|
|
2008-03-04 16:55:17 +00:00
|
|
|
------------------------------------------------------------------------------
|
|
|
|
--- Functionality changes from Asterisk 1.4.X to Asterisk 1.6.0 -------------
|
|
|
|
------------------------------------------------------------------------------
|
2007-02-23 21:12:28 +00:00
|
|
|
|
2007-04-23 15:34:51 +00:00
|
|
|
AMI - The manager (TCP/TLS/HTTP)
|
|
|
|
--------------------------------
|
2007-12-19 09:20:37 +00:00
|
|
|
* Manager has undergone a lot of changes, all of them documented
|
2012-05-03 18:43:54 +00:00
|
|
|
on the Asterisk wiki at https://wiki.asterisk.org/wiki/x/tQBB
|
2007-12-19 09:20:37 +00:00
|
|
|
* Manager version has changed to 1.1
|
2007-12-06 10:27:54 +00:00
|
|
|
* Added a new action 'CoreShowChannels' to list currently defined channels
|
2012-07-23 21:27:56 +00:00
|
|
|
and some information about them.
|
2007-12-04 21:23:30 +00:00
|
|
|
* Added a new action 'SIPshowregistry' to list SIP registrations.
|
2007-07-06 03:40:57 +00:00
|
|
|
* Added TLS support for the manager interface and HTTP server
|
2007-04-23 15:34:51 +00:00
|
|
|
* Added the URI redirect option for the built-in HTTP server
|
|
|
|
* The output of CallerID in Manager events is now more consistent.
|
|
|
|
CallerIDNum is used for number and CallerIDName for name.
|
2007-12-16 13:32:48 +00:00
|
|
|
* Enable https support for builtin web server.
|
2007-04-23 15:34:51 +00:00
|
|
|
See configs/http.conf.sample for details.
|
|
|
|
* Added a new action, GetConfigJSON, which can return the contents of an
|
|
|
|
Asterisk configuration file in JSON format. This is intended to help
|
|
|
|
improve the performance of AJAX applications using the manager interface
|
|
|
|
over HTTP.
|
2012-07-23 21:27:56 +00:00
|
|
|
* SIP and IAX manager events now use "ChannelType" in all cases where we
|
2007-04-23 15:34:51 +00:00
|
|
|
indicate channel driver. Previously, we used a mixture of "Channel"
|
|
|
|
and "ChannelDriver" headers.
|
|
|
|
* Added a "Bridge" action which allows you to bridge any two channels that
|
|
|
|
are currently active on the system.
|
2007-05-24 20:51:47 +00:00
|
|
|
* Added a "ListAllVoicemailUsers" action that allows you to get a list of all
|
|
|
|
the voicemail users setup.
|
2007-08-16 06:52:17 +00:00
|
|
|
* Added 'DBDel' and 'DBDelTree' manager commands.
|
2007-12-05 16:46:47 +00:00
|
|
|
* cdr_manager now reports events via the "cdr" level, separating it from
|
|
|
|
the very verbose "call" level.
|
2007-12-16 13:32:48 +00:00
|
|
|
* Manager users are now stored in memory. If you change the manager account
|
|
|
|
list (delete or add accounts) you need to reload manager.
|
|
|
|
* Added Masquerade manager event for when a masquerade happens between
|
|
|
|
two channels.
|
2007-12-16 13:35:09 +00:00
|
|
|
* Added "manager reload" command for the CLI
|
2008-01-10 00:12:35 +00:00
|
|
|
* Lots of commands that only provided information are now allowed under the
|
|
|
|
Reporting privilege, instead of only under Call or System.
|
|
|
|
* The IAX* commands now require either System or Reporting privilege, to
|
|
|
|
mirror the privileges of the SIP* commands.
|
2008-02-12 00:24:36 +00:00
|
|
|
* Added ability to retrieve list of categories in a config file.
|
|
|
|
* Added ability to retrieve the content of a particular category.
|
|
|
|
* Added ability to empty a context.
|
|
|
|
* Created new action to create a new file.
|
|
|
|
* Updated delete action to allow deletion by line number with respect to category.
|
|
|
|
* Added new action insert to add new variable to category at specified line.
|
|
|
|
* Updated action newcat to allow new category to be inserted in file above another
|
|
|
|
existing category.
|
2008-02-18 10:10:35 +00:00
|
|
|
* Added new event "JitterBufStats" in the IAX2 channel
|
2008-02-22 22:55:35 +00:00
|
|
|
* Originate now requires the Originate privilege and, if you want to call out
|
|
|
|
to a subshell, it requires the System privilege, as well. This was done to
|
|
|
|
enhance manager security.
|
2012-07-23 21:27:56 +00:00
|
|
|
* Originate now accepts codec settings with "Codecs: alaw, ulaw, h264"
|
2012-05-03 18:43:54 +00:00
|
|
|
* New command: Atxfer. See https://wiki.asterisk.org/wiki/x/uABB for more details
|
|
|
|
or manager show command Atxfer from the CLI
|
|
|
|
* New command: IAXregistry. See https://wiki.asterisk.org/wiki/x/uABB for more
|
|
|
|
details or manager show command IAXregistry from the CLI
|
2007-04-23 15:34:51 +00:00
|
|
|
|
|
|
|
Dialplan functions
|
|
|
|
------------------
|
2007-09-06 20:27:53 +00:00
|
|
|
* Added the DEVICE_STATE() dialplan function which allows retrieving any device
|
2008-01-13 23:43:06 +00:00
|
|
|
state in the dialplan, as well as creating custom device states that are
|
|
|
|
controllable from the dialplan.
|
2007-04-23 15:34:51 +00:00
|
|
|
* Extend CALLERID() function with "pres" and "ton" parameters to
|
|
|
|
fetch string representation of calling number presentation indicator
|
|
|
|
and numeric representation of type of calling number value.
|
|
|
|
* MailboxExists converted to dialplan function
|
2007-07-09 08:30:04 +00:00
|
|
|
* A new option to Dial() for telling IP phones not to count the call
|
2008-01-13 23:43:06 +00:00
|
|
|
as "missed" when dial times out and cancels.
|
2007-07-31 18:50:06 +00:00
|
|
|
* Added LOCK(), TRYLOCK(), and UNLOCK(), which provide a single level dialplan
|
2008-01-13 23:43:06 +00:00
|
|
|
mutex. No deadlocks are possible, as LOCK() only allows a single lock to be
|
|
|
|
held for any given channel. Also, locks are automatically freed when a
|
|
|
|
channel is hung up.
|
2007-09-06 20:24:18 +00:00
|
|
|
* Added HINT() dialplan function that allows retrieving hint information.
|
2012-07-23 21:27:56 +00:00
|
|
|
Hints are mappings between extensions and devices for the sake of
|
2008-01-13 23:43:06 +00:00
|
|
|
determining the state of an extension. This function can retrieve the list
|
|
|
|
of devices or the name associated with a hint.
|
2007-09-06 20:54:07 +00:00
|
|
|
* Added EXTENSION_STATE() dialplan function which allows retrieving the state
|
|
|
|
of any extension.
|
2007-11-19 16:29:07 +00:00
|
|
|
* Added SYSINFO() dialplan function which allows retrieval of system information
|
2007-12-31 16:13:26 +00:00
|
|
|
* Added a new dialplan function, DIALPLAN_EXISTS(), which allows you to check for
|
|
|
|
the existence of a dialplan target.
|
2008-01-14 18:42:16 +00:00
|
|
|
* Added two new dialplan functions, TOUPPER and TOLOWER, which convert a string to
|
|
|
|
upper and lower case, respectively.
|
2008-01-22 20:44:56 +00:00
|
|
|
* When bridging, Asterisk sets the BRIDGEPVTCALLID to the channel drivers unique
|
|
|
|
ID for the call (not the Asterisk call ID or unique ID), provided that the
|
|
|
|
channel driver supports this. For SIP, you get the SIP call-ID for the
|
|
|
|
bridged channel which you can store in the CDR with a custom field.
|
2007-04-23 15:34:51 +00:00
|
|
|
|
|
|
|
CLI Changes
|
|
|
|
-----------
|
2008-12-01 18:52:14 +00:00
|
|
|
* Added CLI permissions, config file: cli_permissions.conf
|
|
|
|
default is to allow all commands for every local user/group.
|
|
|
|
Also this new feature added three new CLI commands:
|
|
|
|
- cli check permissions {<username>|@<groupname>|<username>@<groupname>} [<command>]
|
|
|
|
- cli reload permissions
|
|
|
|
- cli show permissions
|
2007-12-04 15:07:53 +00:00
|
|
|
* New CLI command "core show hint" (usage: core show hint <exten>)
|
2007-04-23 15:34:51 +00:00
|
|
|
* New CLI command "core show settings"
|
|
|
|
* Added 'core show channels count' CLI command.
|
2007-07-23 14:23:47 +00:00
|
|
|
* Added the ability to set the core debug and verbose values on a per-file basis.
|
2007-09-13 21:23:32 +00:00
|
|
|
* Added 'queue pause member' and 'queue unpause member' CLI commands
|
2007-11-21 18:38:18 +00:00
|
|
|
* Ability to set process limits ("ulimit") without restarting Asterisk
|
|
|
|
* Enhanced "agi debug" to print the channel name as a prefix to the debug
|
|
|
|
output to make debugging on busy systems much easier.
|
2007-11-26 16:24:27 +00:00
|
|
|
* New CLI commands "dialplan set extenpatternmatching true/false"
|
2008-01-12 19:34:38 +00:00
|
|
|
* New CLI command: "core set chanvar" to set a channel variable from the CLI.
|
2008-01-17 00:05:13 +00:00
|
|
|
* Added an easy way to execute Asterisk CLI commands at startup. Any commands
|
2008-01-22 20:33:16 +00:00
|
|
|
listed in the startup_commands section of cli.conf will get executed.
|
2008-03-01 00:53:25 +00:00
|
|
|
* Added a CLI command, "devstate change", which allows you to set custom device
|
|
|
|
states from the func_devstate module that provides the DEVICE_STATE() function
|
|
|
|
and handling of the "Custom:" devices.
|
2008-04-21 21:13:02 +00:00
|
|
|
* New CLI command: "sip show sched" which shows all ast_sched entries for sip,
|
|
|
|
sorted into the different possible callbacks, with the number of entries
|
|
|
|
currently scheduled for each. Gives you a feel for how busy the sip channel
|
|
|
|
driver is.
|
2008-09-03 18:06:35 +00:00
|
|
|
* Added 'skinny show lines verbose' CLI command. This will show the subs for every channel.
|
2008-10-03 17:36:30 +00:00
|
|
|
* Cleanup another bunch of CLI commands. Now all modules follow the same schema.
|
2008-10-07 17:49:23 +00:00
|
|
|
(Done by lmadsen, junky and mvanbaak during the devcon 2008)
|
2007-04-23 15:34:51 +00:00
|
|
|
|
|
|
|
SIP changes
|
|
|
|
-----------
|
2009-12-09 23:13:28 +00:00
|
|
|
* Added a new 'faxdetect=yes|no' configuration option to sip.conf. When this
|
|
|
|
option is enabled, Asterisk will watch for a CNG tone in the incoming audio
|
2012-07-23 21:27:56 +00:00
|
|
|
for a received call. If it is detected, the channel will jump to the
|
2009-12-09 23:13:28 +00:00
|
|
|
'fax' extension in the dialplan.
|
2007-04-23 15:34:51 +00:00
|
|
|
* The default SIP useragent= identifier now includes the Asterisk version
|
|
|
|
* A new option, match_auth_username in sip.conf changes the matching of incoming requests.
|
|
|
|
If set, and the incoming request carries authentication info,
|
|
|
|
the username to match in the users list is taken from the Digest header
|
|
|
|
rather than from the From: field. This feature is considered experimental.
|
|
|
|
* The "musiconhold" and "musicclass" settings in sip.conf are now removed,
|
|
|
|
since they where replaced by "mohsuggest" and "mohinterpret" in version 1.4
|
|
|
|
* The "localmask" setting was removed in version 1.2 and the reminder about it
|
|
|
|
being removed is now also removed.
|
2007-11-19 23:24:35 +00:00
|
|
|
* A new option "busylevel" for setting a level of calls where asterisk reports
|
2007-11-19 09:16:56 +00:00
|
|
|
a device as busy, to separate it from call-limit. This value is also added
|
|
|
|
to the SIP_PEER dialplan function.
|
2007-04-23 15:34:51 +00:00
|
|
|
* A new realtime family called "sipregs" is now supported to store SIP registration
|
|
|
|
data. If this family is defined, "sippeers" will be used for configuration and
|
|
|
|
"sipregs" for registrations. If it's not defined, "sippeers" will be used for
|
|
|
|
registration data, as before.
|
|
|
|
* The SIPPEER function have new options for port address, call and pickup groups
|
|
|
|
* Added support for T.140 realtime text in SIP/RTP
|
2007-04-28 21:01:44 +00:00
|
|
|
* The "checkmwi" option has been removed from sip.conf, as it is no longer
|
2012-07-23 21:27:56 +00:00
|
|
|
required due to the restructuring of how MWI is handled. See the descriptions
|
|
|
|
in this file of the "pollmailboxes" and "pollfreq" options to voicemail.conf
|
2007-04-28 21:01:44 +00:00
|
|
|
for more information.
|
2007-06-26 23:31:23 +00:00
|
|
|
* Added rtpdest option to CHANNEL() dialplan function.
|
2007-06-27 23:13:09 +00:00
|
|
|
* Added SIPREFERRINGCONTEXT and SIPREFERREDBYHDR variables which are set when a transfer takes place.
|
2007-07-09 08:30:04 +00:00
|
|
|
* SIP now adds a header to the CANCEL if the call was answered by another phone
|
2007-09-11 17:58:48 +00:00
|
|
|
in the same dial command, or if the new c option in dial() is used.
|
|
|
|
* The new default is that 100 Trying is not sent on REGISTER attempts as the RFC specifically
|
2007-11-25 11:46:17 +00:00
|
|
|
states it is not needed. For phones, however, that do require it the "registertrying" option
|
2012-07-23 21:27:56 +00:00
|
|
|
has been added so it can be enabled.
|
2007-11-25 11:46:17 +00:00
|
|
|
* A new option called "callcounter" (global/peer/user level) enables call counters needed
|
2008-01-13 23:43:06 +00:00
|
|
|
for better status reports needed for queues and SIP subscriptions. (Call-Limit was previously
|
|
|
|
used to enable this functionality).
|
2012-07-23 21:27:56 +00:00
|
|
|
* New settings for timer T1 and timer B on a global level or per device. This makes it
|
2008-01-13 23:43:06 +00:00
|
|
|
possible to force timeout faster on non-responsive SIP servers. These settings are
|
|
|
|
considered advanced, so don't use them unless you have a problem.
|
2007-12-19 08:57:45 +00:00
|
|
|
* Added a dial string option to be able to set the To: header in an INVITE to any
|
2008-01-13 23:43:06 +00:00
|
|
|
SIP uri.
|
2008-01-11 00:38:23 +00:00
|
|
|
* Added a new global and per-peer option, qualifyfreq, which allows you to configure
|
|
|
|
the qualify frequency.
|
2008-01-18 22:04:33 +00:00
|
|
|
* Added SIP Session Timers support (RFC 4028). This prevents stuck SIP sessions that
|
|
|
|
were not properly torn down due to network or endpoint failures during an established
|
|
|
|
SIP session.
|
2012-05-03 18:43:54 +00:00
|
|
|
* Added experimental TCP and TLS support for SIP. See https://wiki.asterisk.org/wiki/x/ygBB
|
|
|
|
and configs/sip.conf.sample for more information on how it is used.
|
2008-03-18 07:23:45 +00:00
|
|
|
* Added a new configuration option "authfailureevents" that enables manager events when
|
2012-07-23 21:27:56 +00:00
|
|
|
a peer can't authenticate properly.
|
2008-04-01 22:07:30 +00:00
|
|
|
* Added DNS manager support to registrations for peers not referencing a peer entry.
|
2007-04-23 15:34:51 +00:00
|
|
|
|
|
|
|
IAX2 changes
|
|
|
|
------------
|
|
|
|
* Added the trunkmaxsize configuration option to chan_iax2.
|
|
|
|
* Added the srvlookup option to iax.conf
|
|
|
|
* Added support for OSP. The token is set and retrieved through the CHANNEL()
|
|
|
|
dialplan function.
|
|
|
|
|
2007-12-16 13:32:48 +00:00
|
|
|
XMPP Google Talk/Jingle changes
|
|
|
|
-------------------------------
|
|
|
|
* Added the bindaddr option to gtalk.conf.
|
|
|
|
|
2007-09-06 20:16:02 +00:00
|
|
|
Skinny changes
|
|
|
|
-------------
|
|
|
|
* Added skinny show device, skinny show line, and skinny show settings CLI commands.
|
2007-11-21 18:38:18 +00:00
|
|
|
* Proper codec support in chan_skinny.
|
2007-12-16 10:51:53 +00:00
|
|
|
* Added settings for IP and Ethernet QoS requests
|
|
|
|
|
2008-03-05 16:23:44 +00:00
|
|
|
MGCP changes
|
2007-12-16 10:51:53 +00:00
|
|
|
------------
|
|
|
|
* Added separate settings for media QoS in mgcp.conf
|
2007-09-06 20:16:02 +00:00
|
|
|
|
2007-12-31 16:13:26 +00:00
|
|
|
Console Channel Driver changes
|
2008-01-30 15:36:58 +00:00
|
|
|
------------------------------
|
2007-12-31 16:13:26 +00:00
|
|
|
* Added experimental support for video send & receive to chan_oss.
|
|
|
|
This requires SDL and ffmpeg/avcodec, plus Video4Linux or X11 to act as
|
|
|
|
a video source.
|
2007-12-16 13:21:11 +00:00
|
|
|
|
2007-12-19 09:20:37 +00:00
|
|
|
Phone channel changes (chan_phone)
|
|
|
|
----------------------------------
|
|
|
|
* Added G729 passthrough support to chan_phone for Sigma Designs boards.
|
|
|
|
|
|
|
|
H.323 channel Changes
|
|
|
|
---------------------
|
|
|
|
* H323 remote hold notification support added (by NOTIFY message
|
|
|
|
and/or H.450 supplementary service)
|
|
|
|
|
|
|
|
Local channel changes
|
|
|
|
---------------------
|
|
|
|
* The device state functionality in the Local channel driver has been updated
|
|
|
|
to indicate INUSE or NOT_INUSE when a Local channel is being used as opposed
|
|
|
|
to just UNKNOWN if the extension exists.
|
|
|
|
* Added jitterbuffer support for chan_local. This allows you to use the
|
|
|
|
generic jitterbuffer on incoming calls going to Asterisk applications.
|
|
|
|
For example, this would allow you to use a jitterbuffer for an incoming
|
|
|
|
SIP call to Voicemail by putting a Local channel in the middle. This
|
|
|
|
feature is enabled by using the 'j' option in the Dial string to the Local
|
|
|
|
channel in conjunction with the existing 'n' option for local channels.
|
2008-04-10 20:28:40 +00:00
|
|
|
* A 'b' option has been added which causes chan_local to return the actual channel
|
|
|
|
that is behind it when queried. This is useful for transfer scenarios as the
|
|
|
|
actual channel will be transferred, not the Local channel.
|
2007-12-19 09:20:37 +00:00
|
|
|
|
2008-07-02 20:43:55 +00:00
|
|
|
Agent channel changes
|
|
|
|
----------------------
|
|
|
|
* The ackcall and endcall options are now supplemented with options acceptdtmf
|
|
|
|
and enddtmf. These allow for the DTMF keypress to be configurable. The options
|
2008-10-01 12:29:18 +00:00
|
|
|
default to their old hard-coded values ('#' and '*' respectively) so this should
|
|
|
|
not break any existing agent installations.
|
2008-07-02 20:43:55 +00:00
|
|
|
|
2008-07-11 16:18:01 +00:00
|
|
|
DAHDI channel driver (chan_dahdi) Changes
|
2007-12-19 09:20:37 +00:00
|
|
|
----------------------------------------
|
2008-07-11 16:18:01 +00:00
|
|
|
* SS7 support (via libss7 library)
|
2007-12-19 09:20:37 +00:00
|
|
|
* In India, some carriers transmit CID via dtmf. Some code has been added
|
2008-01-13 23:43:06 +00:00
|
|
|
that will handle some situations. The cidstart=polarity_IN choice has been added for
|
|
|
|
those carriers that transmit CID via dtmf after a polarity change.
|
2007-12-19 09:20:37 +00:00
|
|
|
* CID matching information is now shown when doing 'dialplan show'.
|
2008-07-11 16:18:01 +00:00
|
|
|
* Added dahdi show version CLI command.
|
|
|
|
* Added setvar support to chan_dahdi.conf channel entries.
|
2007-12-19 09:20:37 +00:00
|
|
|
* Added two new options: mwimonitor and mwimonitornotify. These options allow
|
|
|
|
you to enable MWI monitoring on FXO lines. When the MWI state changes,
|
|
|
|
the script specified in the mwimonitornotify option is executed. An internal
|
2007-12-31 16:13:26 +00:00
|
|
|
event indicating the new state of the mailbox is also generated, so that
|
|
|
|
the normal MWI facilities in Asterisk work as usual.
|
2008-01-11 23:10:57 +00:00
|
|
|
* Added signalling type 'auto', which attempts to use the same signalling type
|
2008-07-11 16:18:01 +00:00
|
|
|
for a channel as configured in DAHDI. This is primarily designed for analog
|
2008-01-13 23:43:06 +00:00
|
|
|
ports, but will also work for digital ports that are configured for FXS or FXO
|
2008-07-11 16:18:01 +00:00
|
|
|
signalling types. This mode is also the default now, so if your chan_dahdi.conf
|
2008-01-13 23:43:06 +00:00
|
|
|
does not specify signalling for a channel (which is unlikely as the sample
|
|
|
|
configuration file has always recommended specifying it for every channel) then
|
|
|
|
the 'auto' mode will be used for that channel if possible.
|
2008-07-11 16:18:01 +00:00
|
|
|
* Added a 'dahdi set dnd' command to allow CLI control of the Do-Not-Disturb
|
2008-01-13 23:43:06 +00:00
|
|
|
state for a channel; also ensured that the DNDState Manager event is
|
|
|
|
emitted no matter how the DND state is set or cleared.
|
2007-12-19 09:20:37 +00:00
|
|
|
|
2008-01-13 23:43:06 +00:00
|
|
|
New Channel Drivers
|
|
|
|
-------------------
|
2012-05-03 18:43:54 +00:00
|
|
|
* Added a new channel driver, chan_unistim. See the Asterisk wiki at
|
|
|
|
https://wiki.asterisk.org/wiki/x/vgsiAQ and configs/unistim.conf.sample
|
|
|
|
for details. This new channel driver allows you to use Nortel i2002,
|
|
|
|
i2004, and i2050 phones with Asterisk.
|
2008-01-13 23:43:06 +00:00
|
|
|
* Added a new channel driver, chan_console, which uses portaudio as a cross
|
|
|
|
platform audio interface. It was written as a channel driver that would
|
|
|
|
work with Mac CoreAudio, but portaudio supports a number of other audio
|
|
|
|
interfaces, as well. Note that this channel driver requires v19 or higher
|
|
|
|
of portaudio; older versions have a different API.
|
2012-07-23 21:27:56 +00:00
|
|
|
|
2007-04-23 15:34:51 +00:00
|
|
|
DUNDi changes
|
|
|
|
-------------
|
|
|
|
* Added the ability to specify arguments to the Dial application when using
|
|
|
|
the DUNDi switch in the dialplan.
|
|
|
|
* Added the ability to set weights for responses dynamically. This can be
|
|
|
|
done using a global variable or a dialplan function. Using the SHELL()
|
|
|
|
function would allow you to have an external script set the weight for
|
|
|
|
each response.
|
2007-04-28 19:52:37 +00:00
|
|
|
* Added two new dialplan functions, DUNDIQUERY and DUNDIRESULT. These
|
|
|
|
functions will allow you to initiate a DUNDi query from the dialplan,
|
|
|
|
find out how many results there are, and access each one.
|
2010-06-22 15:08:39 +00:00
|
|
|
* Added the ability to specifiy a port for a dundi peer.
|
2007-04-23 15:34:51 +00:00
|
|
|
|
2007-05-18 02:55:05 +00:00
|
|
|
ENUM changes
|
|
|
|
------------
|
|
|
|
* Added two new dialplan functions, ENUMQUERY and ENUMRESULT. These
|
|
|
|
functions will allow you to initiate an ENUM lookup from the dialplan,
|
|
|
|
and Asterisk will cache the results. ENUMRESULT can be used to access
|
2007-05-22 18:52:59 +00:00
|
|
|
the results without doing multiple DNS queries.
|
2007-05-18 02:55:05 +00:00
|
|
|
|
2007-04-23 15:34:51 +00:00
|
|
|
Voicemail Changes
|
|
|
|
-----------------
|
|
|
|
* Added the ability to customize which sound files are used for some of the
|
|
|
|
prompts within the Voicemail application by changing them in voicemail.conf
|
|
|
|
* Added the ability for the "voicemail show users" CLI command to show users
|
2007-04-27 22:08:54 +00:00
|
|
|
configured by the dynamic realtime configuration method.
|
2007-04-28 21:01:44 +00:00
|
|
|
* MWI (Message Waiting Indication) handling has been significantly
|
|
|
|
restructured internally to Asterisk. It is now totally event based
|
|
|
|
instead of polling based. The voicemail application will notify other
|
|
|
|
modules that have subscribed to MWI events when something in the mailbox
|
|
|
|
changes.
|
|
|
|
This also means that if any other entity outside of Asterisk is changing
|
|
|
|
the contents of mailboxes, then the voicemail application still needs to
|
|
|
|
poll for changes. Examples of situations that would require this option
|
|
|
|
are web interfaces to voicemail or an email client in the case of using
|
|
|
|
IMAP storage. So, two new options have been added to voicemail.conf
|
|
|
|
to account for this: "pollmailboxes" and "pollfreq". See the sample
|
|
|
|
configuration file for details.
|
2007-06-14 21:03:01 +00:00
|
|
|
* Added "tw" language support
|
2007-06-27 19:50:21 +00:00
|
|
|
* Added support for storage of greetings using an IMAP server
|
2007-06-27 22:47:08 +00:00
|
|
|
* Added ability to customize forward, reverse, stop, and pause keys for message playback
|
2007-07-06 03:48:33 +00:00
|
|
|
* SMDI is now enabled in voicemail using the smdienable option.
|
2007-08-28 16:28:26 +00:00
|
|
|
* A "lockmode" option has been added to asterisk.conf to configure the file
|
|
|
|
locking method used for voicemail, and potentially other things in the
|
2007-10-09 15:12:59 +00:00
|
|
|
future. The default is the old behavior, lockfile. However, there is a
|
|
|
|
new method, "flock", that uses a different method for situations where the
|
|
|
|
lockfile will not work, such as on SMB/CIFS mounts.
|
2008-01-14 22:19:40 +00:00
|
|
|
* Added the ability to backup deleted messages, to ease recovery in the case
|
|
|
|
that a user accidentally deletes a message, and discovers that they need it.
|
2008-02-26 00:35:30 +00:00
|
|
|
* Reworked the SMDI interface in Asterisk. The new way to access SMDI information
|
|
|
|
is through the new functions, SMDI_MSG_RETRIEVE() and SMDI_MSG(). The file
|
|
|
|
smdi.conf can now be configured with options to map SMDI station IDs to Asterisk
|
|
|
|
voicemail boxes. The SMDI interface can also poll for MWI changes when some
|
|
|
|
outside entity is modifying the state of the mailbox (such as IMAP storage or
|
|
|
|
a web interface of some kind).
|
2008-05-09 21:22:42 +00:00
|
|
|
* Added the support for marking messages as "urgent." There are two methods to accomplish
|
|
|
|
this. One is to pass the 'U' option to VoiceMail(). Another way to mark a message as urgent
|
2008-06-10 15:12:17 +00:00
|
|
|
is to specify "review=yes" in voicemail.conf. Doing this will cause allow the user to mark
|
|
|
|
the message as urgent after he has recorded a voicemail by following the voice instructions.
|
|
|
|
When listening to voicemails using VoiceMailMain urgent messages will be presented before other
|
|
|
|
messages
|
2016-06-06 16:13:01 +00:00
|
|
|
* Added "is" language support
|
2007-04-27 22:08:54 +00:00
|
|
|
|
|
|
|
Queue changes
|
|
|
|
-------------
|
2007-12-04 15:02:48 +00:00
|
|
|
* Added the general option 'shared_lastcall' so that member's wrapuptime may be
|
|
|
|
used across multiple queues.
|
2012-07-23 21:27:56 +00:00
|
|
|
* Added QUEUE_VARIABLES function to set queue variables added setqueuevar and
|
2007-04-27 22:08:54 +00:00
|
|
|
setqueueentryvar options for each queue, see queues.conf.sample for details.
|
|
|
|
* Added keepstats option to queues.conf which will keep queue
|
|
|
|
statistics during a reload.
|
|
|
|
* setinterfacevar option in queues.conf also now sets a variable
|
|
|
|
called MEMBERNAME which contains the member's name.
|
|
|
|
* Added 'Strategy' field to manager event QueueParams which represents
|
2012-07-23 21:27:56 +00:00
|
|
|
the queue strategy in use.
|
|
|
|
* Added option to run macro when a queue member is connected to a caller,
|
2007-04-27 22:08:54 +00:00
|
|
|
see queues.conf.sample for details.
|
|
|
|
* app_queue now has a 'loose' option which is almost exactly like 'strict' except it
|
|
|
|
does not count paused queue members as unavailable.
|
|
|
|
* Added min-announce-frequency option to queues.conf which allows you to control the
|
|
|
|
minimum amount of time between queue announcements for use when the caller's queue
|
|
|
|
position changes frequently.
|
2007-04-30 16:46:49 +00:00
|
|
|
* Added additional information to EXITWITHTIMEOUT and EXITWITHKEY events in the
|
|
|
|
queue log.
|
2007-08-13 15:39:48 +00:00
|
|
|
* Added ability for non-realtime queues to have realtime members
|
2007-10-26 22:21:08 +00:00
|
|
|
* Added the "linear" strategy to queues.
|
2007-11-06 22:36:55 +00:00
|
|
|
* Added the "wrandom" strategy to queues.
|
2007-12-21 20:28:04 +00:00
|
|
|
* Added new channel variable QUEUE_MIN_PENALTY
|
|
|
|
* QUEUE_MAX_PENALTY and QUEUE_MIN_PENALTY may be adjusted in mid-call by defining
|
|
|
|
rules in queuerules.conf. See configs/queuerules.conf.sample for details
|
2008-01-08 21:18:32 +00:00
|
|
|
* Added a new parameter for member definition, called state_interface. This may be
|
|
|
|
used so that a member may be called via one interface but have a different interface's
|
2008-01-13 19:19:57 +00:00
|
|
|
device state reported.
|
2009-02-13 20:57:37 +00:00
|
|
|
* Added new CLI and Manager commands relating to reloading queues. From the CLI, see
|
|
|
|
"queue reload", "queue reset stats". Also see "manager show command QueueReload" and
|
|
|
|
"manager show command QueueReset."
|
2008-03-18 18:58:42 +00:00
|
|
|
* New configuration option: randomperiodicannounce. If a list of periodic announcements is
|
|
|
|
specified by the periodic-announce option, then one will be chosen randomly when it is time
|
2008-06-10 15:12:17 +00:00
|
|
|
to play a periodic announcment
|
2008-04-30 19:30:41 +00:00
|
|
|
* New configuration options: announce-position now takes two more values in addition to "yes" and
|
|
|
|
"no." Two new options, "limit" and "more," are allowed. These are tied to another option,
|
2008-06-10 15:12:17 +00:00
|
|
|
announce-position-limit. By setting announce-position to "limit" callers will only have their
|
|
|
|
position announced if their position is less than what is specified by announce-position-limit.
|
|
|
|
If announce-position is set to "more" then callers beyond the position specified by announce-position-limit
|
|
|
|
will be told that their are more than announce-position-limit callers waiting.
|
2008-06-03 21:22:52 +00:00
|
|
|
* Two new queue log events have been added. An ADDMEMBER event will be logged
|
|
|
|
when a realtime queue member is added and a REMOVEMEMBER event will be logged
|
2008-06-10 15:12:17 +00:00
|
|
|
when a realtime queue member is removed. Since there is no calling channel associated
|
|
|
|
with these events, the string "REALTIME" is placed where the channel's unique id
|
|
|
|
is typically placed.
|
2008-10-06 15:29:56 +00:00
|
|
|
* The configuration method for the "joinempty" and "leavewhenempty" options has
|
|
|
|
changed to a comma-separated list of methods of determining member availability
|
2009-01-08 19:48:42 +00:00
|
|
|
instead of vague terms such as "yes," "loose," "no," and "strict." These old four
|
|
|
|
values are still accepted for backwards-compatibility, though.
|
|
|
|
* The average talktime is now calculated on queues. This information is reported via the
|
|
|
|
CLI commands "queue show" and "queues show"; through the AMI events AgentComplete, QueueSummary,
|
|
|
|
and QueueParams; and through the channelvariable QUEUETALKTIME if setinterfacevar=yes is set for
|
|
|
|
the queue.
|
2007-04-23 15:34:51 +00:00
|
|
|
|
2007-04-28 21:55:00 +00:00
|
|
|
MeetMe Changes
|
|
|
|
--------------
|
2012-07-23 21:27:56 +00:00
|
|
|
* The 'o' option to provide an optimization has been removed and its functionality
|
2007-04-28 21:55:00 +00:00
|
|
|
has been enabled by default.
|
2007-05-02 23:50:07 +00:00
|
|
|
* When a conference is created, the UNIQUEID of the channel that caused it to be
|
|
|
|
created is stored. Then, every channel that joins the conference will have the
|
2007-05-02 23:50:29 +00:00
|
|
|
MEETMEUNIQUEID channel variable set with this ID. This can be used to relate
|
2007-05-02 23:50:07 +00:00
|
|
|
callers that come and go from long standing conferences.
|
2007-05-07 22:14:09 +00:00
|
|
|
* Added a new application, MeetMeChannelAdmin, which is similar to MeetMeAdmin,
|
|
|
|
except it does operations on a channel by name, instead of number in a conference.
|
|
|
|
This is a very useful feature in combination with the 'X' option to ChanSpy.
|
2007-07-06 03:48:33 +00:00
|
|
|
* Added 'C' option to Meetme which causes a caller to continue in the dialplan
|
|
|
|
when kicked out.
|
2007-10-17 20:42:20 +00:00
|
|
|
* Added new RealTime functionality to provide support for scheduled conferencing.
|
|
|
|
This includes optional messages to the caller if they attempt to join before
|
|
|
|
the schedule start time, or to allow the caller to join the conference early.
|
|
|
|
Also included is optional support for limiting the number of callers per
|
|
|
|
RealTime conference.
|
2007-11-06 22:15:32 +00:00
|
|
|
* Added the S() and L() options to the MeetMe application. These are pretty
|
|
|
|
much identical to the S() and L() options to Dial(). They let you set
|
|
|
|
timeouts for the conference, as well as have warning sounds played to
|
|
|
|
let the caller know how much time is left, and when it is running out.
|
2007-11-06 23:44:39 +00:00
|
|
|
* Added the ability to do "meetme concise" with the "meetme" CLI command.
|
|
|
|
This extends the concise capabilities of this CLI command to include
|
|
|
|
listing all conferences, instead of an addition to the other sub commands
|
|
|
|
for the "meetme" command.
|
2007-11-21 00:21:38 +00:00
|
|
|
* Added the ability to specify the music on hold class used to play into the
|
|
|
|
conference when there is only one member and the M option is used.
|
2008-04-18 18:15:11 +00:00
|
|
|
* Added MEETME_INFO dialplan function which provides a way to query
|
|
|
|
various properties of a Meetme conference.
|
2012-07-23 21:27:56 +00:00
|
|
|
* Added new admin features: *81: Roll call, *82: eject all, *83: mute all,
|
2010-05-03 22:13:24 +00:00
|
|
|
and *84: record in-conf
|
2007-04-28 21:55:00 +00:00
|
|
|
|
2007-11-21 18:38:18 +00:00
|
|
|
Other Dialplan Application Changes
|
|
|
|
----------------------------------
|
|
|
|
* Argument support for Gosub application
|
|
|
|
* From the to-do lists: straighten out the app timeout args:
|
|
|
|
Wait() app now really does 0.3 seconds- was truncating arg to an int.
|
|
|
|
WaitExten() same as Wait().
|
|
|
|
Congestion() - Now takes floating pt. argument.
|
|
|
|
Busy() - now takes floating pt. argument.
|
|
|
|
Read() - timeout now can be floating pt.
|
|
|
|
WaitForRing() now takes floating pt timeout arg.
|
|
|
|
SpeechBackground() -- clarified in the docstrings that the timeout is an integer seconds.
|
|
|
|
* Added 's' option to Page application.
|
2008-10-31 20:05:46 +00:00
|
|
|
* Added an optional timeout argument to the Page application.
|
2008-10-02 19:30:45 +00:00
|
|
|
* Added 'E', 'V', and 'P' commands to ExternalIVR.
|
2007-11-21 18:38:18 +00:00
|
|
|
* Added 'o' and 'X' options to Chanspy.
|
|
|
|
* Added a new dialplan application, Bridge, which allows you to bridge the
|
|
|
|
calling channel to any other active channel on the system.
|
|
|
|
* Added the ability to specify a music on hold class to play instead of ringing
|
|
|
|
for the SLATrunk application.
|
|
|
|
* The Read application no longer exits the dialplan on error. Instead, it sets
|
|
|
|
READSTATUS to ERROR, which you can catch and handle separately.
|
2007-12-05 16:25:52 +00:00
|
|
|
* Added 'm' option to Directory, which lists out names, 8 at a time, instead
|
|
|
|
of asking for verification of each name, one at a time.
|
2007-12-14 19:27:54 +00:00
|
|
|
* Privacy() no longer uses privacy.conf, as all options are specifyable as
|
|
|
|
direct options to the app.
|
2007-12-28 16:12:06 +00:00
|
|
|
* AMD() has a new "maximum word length" option. "show application AMD" from the CLI
|
|
|
|
for more details
|
2008-02-15 23:20:48 +00:00
|
|
|
* GotoIfTime() now may branch based on a "false" condition, like other Goto-related applications
|
2008-02-19 18:40:22 +00:00
|
|
|
* The ChannelRedirect application no longer exits the dialplan if the given channel
|
|
|
|
does not exist. It will now set the CHANNELREDIRECT_STATUS variable to SUCCESS upon success
|
|
|
|
or NOCHANNEL if the given channel was not found.
|
2008-03-05 16:23:44 +00:00
|
|
|
* The silencethreshold setting that was previously configurable in multiple
|
|
|
|
applications is now settable globally via dsp.conf.
|
2007-11-21 18:38:18 +00:00
|
|
|
|
2007-05-22 18:52:59 +00:00
|
|
|
Music On Hold Changes
|
|
|
|
---------------------
|
2012-07-23 21:27:56 +00:00
|
|
|
* A new option, "digit", has been added for music on hold classes in
|
2007-05-22 18:52:59 +00:00
|
|
|
musiconhold.conf. If this is set for a music on hold class, a caller
|
|
|
|
listening to music on hold can press this digit to switch to listening
|
|
|
|
to this music on hold class.
|
Adding support for realtime music on hold. The following are the main points:
1. When moh is started, we search first in memory to find the class. If we do not
find it in memory, we search realtime instead.
2. When moh is restarted (as in, it had been started on this particular channel, stopped,
and now we're starting it again), if using the "files" mode, then realtime will always
be rechecked. If you are using other modes, however, we will simply reattach to the external
running process which was playing moh earlier in the call. This is a necessary compromise so that
we don't end up with too many background processes.
3. musiconhold.conf has a general section now. It has one option: cachertclasses. If set to yes,
then moh classes found in realtime will be added to the in-memory list. This has the advantage
of not requiring database lookups each time moh is started, but it has the disadvantage of not
truly being realtime.
I have tested this for functionality, and it passes. I also tested this under valgrind and there
are no memory problems reported under typical use.
Special thanks to Sergee for implementing this feature and enduring my complaints on the bugtracker!
(closes issue #11196, reported and patched by sergee)
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@89946 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2007-11-28 00:47:22 +00:00
|
|
|
* Support for realtime music on hold has been added.
|
|
|
|
* In conjunction with the realtime music on hold, a general section has
|
2008-01-13 23:43:06 +00:00
|
|
|
been added to musiconhold.conf, its sole variable is cachertclasses. If this
|
|
|
|
is set, then music on hold classes found in realtime will be cached in memory.
|
2007-05-22 18:52:59 +00:00
|
|
|
|
2007-07-06 03:48:33 +00:00
|
|
|
AEL Changes
|
|
|
|
-----------
|
2006-09-27 03:45:22 +00:00
|
|
|
* AEL upgraded to use the Gosub with Arguments instead
|
|
|
|
of Macro application, to hopefully reduce the problems
|
2012-07-23 21:27:56 +00:00
|
|
|
seen with the artificially low stack ceiling that
|
2006-09-27 03:45:22 +00:00
|
|
|
Macro bumps into. Macros can only call other Macros
|
|
|
|
to a depth of 7. Tests run using gosub, show depths
|
|
|
|
limited only by virtual memory. A small test demonstrated
|
|
|
|
recursive call depths of 100,000 without problems.
|
2007-06-19 23:38:54 +00:00
|
|
|
-- in addition to this, all apps that allowed a macro
|
|
|
|
to be called, as in Dial, queues, etc, are now allowing
|
2007-06-20 20:10:19 +00:00
|
|
|
a gosub call in similar fashion.
|
|
|
|
* AEL now generates LOCAL(argname) declarations when it
|
2007-07-06 03:48:33 +00:00
|
|
|
Set()'s the each arg name to the value of ${ARG1}, ${ARG2),
|
|
|
|
etc. That makes the arguments local in scope. The user
|
|
|
|
can define their own local variables in macros, now,
|
|
|
|
by saying "local myvar=someval;" or using Set() in this
|
|
|
|
fashion: Set(LOCAL(myvar)=someval); ("local" is now
|
|
|
|
an AEL keyword).
|
2007-08-15 19:21:27 +00:00
|
|
|
* utils/conf2ael introduced. Will convert an extensions.conf
|
2012-07-23 21:27:56 +00:00
|
|
|
file into extensions.ael. Very crude and unfinished, but
|
2008-01-13 23:43:06 +00:00
|
|
|
will be improved as time goes by. Should be useful for a
|
|
|
|
first pass at conversion.
|
2007-08-15 19:21:27 +00:00
|
|
|
* aelparse will now read extensions.conf to see if a referenced
|
2008-01-13 23:43:06 +00:00
|
|
|
macro or context is there before issueing a warning.
|
2012-07-23 21:27:56 +00:00
|
|
|
* AEL parser sets a local channel variable ~~EXTEN~~, to
|
2008-04-21 21:13:02 +00:00
|
|
|
preserve the value of ${EXTEN} thru switch statements.
|
|
|
|
* New operator in $[...] expressions: the ~~ operator serves
|
|
|
|
as a concatenation operator. AT THE MOMENT, it is really only
|
|
|
|
necessary and useful in AEL, especially in if() expressions.
|
2012-07-23 21:27:56 +00:00
|
|
|
Operation: ${a} ~~ ${b| with force both a and b to strings, strip
|
2008-04-21 21:13:02 +00:00
|
|
|
any enclosing double-quotes, and evaluate to the value of a
|
|
|
|
concatenated with the value of b. For example if a is set to
|
|
|
|
"xyz" and b has the value "abc", then ${a} ~~ ${b| would
|
|
|
|
evaluate to xyzabc .
|
|
|
|
|
2007-07-06 03:48:33 +00:00
|
|
|
|
|
|
|
Call Features (res_features) Changes
|
|
|
|
------------------------------------
|
|
|
|
* Added the parkedcalltransfers option to features.conf
|
Merged revisions 172517 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4
........
r172517 | twilson | 2009-01-30 11:47:41 -0600 (Fri, 30 Jan 2009) | 37 lines
Fix feature inheritance with builtin features
When using builtin features like parking and transfers, the AST_FEATURE_* flags
would not be set correctly for all instances when either performing a builtin
attended transfer, or parking a call and getting the timeout callback. Also,
there was no way on a per-call basis to specify what features someone should
have on picking up a parked call (since that doesn't involve the Dial() command).
There was a global option for setting whether or not all users who pickup a
parked call should have AST_FEATURE_REDIRECT set, but nothing for DISCONNECT,
AUTOMON, or PARKCALL.
This patch:
1) adds the BRIDGE_FEATURES dialplan variable which can be set either in the
dialplan or with setvar in channels that support it. This variable can be set
to any combination of 't', 'k', 'w', and 'h' (case insensitive matching of the
equivalent dial options), to set what features should be activated on this
channel. The patch moves the setting of the features datastores into the
bridging code instead of app_dial to help facilitate this.
2) adds global options parkedcallparking, parkedcallhangup, and
parkedcallrecording to be similar to the parkedcalltransfers option for
globally setting features.
3) has builtin_atxfer call builtin_parkcall if being transfered to the parking
extension since tracking everything through multiple masquerades, etc. is
difficult and error-prone
4) attempts to fix all cases of return calls from parking and completed builtin
transfers not having the correct permissions
(closes issue #14274)
Reported by: aragon
Patches:
fix_feature_inheritence.diff.txt uploaded by otherwiseguy (license 396)
Tested by: aragon, otherwiseguy
Review http://reviewboard.digium.com/r/138/
........
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@172580 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2009-01-30 21:29:12 +00:00
|
|
|
* Added parkedcallparking option to control one touch parking w/ parking
|
|
|
|
pickup
|
|
|
|
* Added parkedcallhangup option to control disconnect feature w/ parking
|
|
|
|
pickup
|
|
|
|
* Added parkedcallrecording option to control one-touch record w/ parking
|
|
|
|
pickup
|
2010-02-03 20:48:36 +00:00
|
|
|
* Added parkedcallparking, parkedcallhangup, parkedcallrecording, and
|
|
|
|
parkedcalltransfers option support for multiple parking lots.
|
Merged revisions 172517 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4
........
r172517 | twilson | 2009-01-30 11:47:41 -0600 (Fri, 30 Jan 2009) | 37 lines
Fix feature inheritance with builtin features
When using builtin features like parking and transfers, the AST_FEATURE_* flags
would not be set correctly for all instances when either performing a builtin
attended transfer, or parking a call and getting the timeout callback. Also,
there was no way on a per-call basis to specify what features someone should
have on picking up a parked call (since that doesn't involve the Dial() command).
There was a global option for setting whether or not all users who pickup a
parked call should have AST_FEATURE_REDIRECT set, but nothing for DISCONNECT,
AUTOMON, or PARKCALL.
This patch:
1) adds the BRIDGE_FEATURES dialplan variable which can be set either in the
dialplan or with setvar in channels that support it. This variable can be set
to any combination of 't', 'k', 'w', and 'h' (case insensitive matching of the
equivalent dial options), to set what features should be activated on this
channel. The patch moves the setting of the features datastores into the
bridging code instead of app_dial to help facilitate this.
2) adds global options parkedcallparking, parkedcallhangup, and
parkedcallrecording to be similar to the parkedcalltransfers option for
globally setting features.
3) has builtin_atxfer call builtin_parkcall if being transfered to the parking
extension since tracking everything through multiple masquerades, etc. is
difficult and error-prone
4) attempts to fix all cases of return calls from parking and completed builtin
transfers not having the correct permissions
(closes issue #14274)
Reported by: aragon
Patches:
fix_feature_inheritence.diff.txt uploaded by otherwiseguy (license 396)
Tested by: aragon, otherwiseguy
Review http://reviewboard.digium.com/r/138/
........
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@172580 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2009-01-30 21:29:12 +00:00
|
|
|
* Added BRIDGE_FEATURES variable to set available features for a channel
|
2007-07-06 03:48:33 +00:00
|
|
|
* The built-in method for doing attended transfers has been updated to
|
|
|
|
include some new options that allow you to have the transferee sent
|
|
|
|
back to the person that did the transfer if the transfer is not successful.
|
|
|
|
See the options "atxferdropcall", "atxferloopdelay", and "atxfercallbackretries"
|
|
|
|
in features.conf.sample.
|
|
|
|
* Added support for configuring named groups of custom call features in
|
|
|
|
features.conf. This means that features can be written a single time, and
|
|
|
|
then mapped into groups of features for different key mappings or easier
|
|
|
|
access control.
|
2007-11-13 20:30:13 +00:00
|
|
|
* Updated the ParkedCall application to allow you to not specify a parking
|
|
|
|
extension. If you don't specify a parking space to pick up, it will grab
|
|
|
|
the first one available.
|
2008-01-23 23:09:11 +00:00
|
|
|
* Added cli command 'features reload' to reload call features from features.conf
|
|
|
|
* Moved into core asterisk binary.
|
2008-10-30 16:38:19 +00:00
|
|
|
* Changed the default setting for featuredigittimeout to 2000 ms from 500 ms.
|
2010-09-15 19:23:56 +00:00
|
|
|
* Added the ability for custom parking lots to be configured with their own
|
|
|
|
parking extension with the parkext option.
|
2007-07-06 03:48:33 +00:00
|
|
|
|
|
|
|
Language Support Changes
|
|
|
|
------------------------
|
|
|
|
* Brazilian Portuguese (pt-BR) in VM, and say.c was added
|
|
|
|
* Added support for the Hungarian language for saying numbers, dates, and times.
|
|
|
|
|
2007-12-03 21:03:05 +00:00
|
|
|
AGI Changes
|
|
|
|
-----------
|
|
|
|
* Added SPEECH commands for speech recognition. A complete listing can be found
|
2010-06-16 18:43:22 +00:00
|
|
|
using agi show.
|
2008-05-30 16:10:46 +00:00
|
|
|
* If app_stack is loaded, GOSUB is a native AGI command that may be used to
|
|
|
|
invoke subroutines in the dialplan. Note that calling EXEC with Gosub
|
|
|
|
does not behave as expected; the native command needs to be used, instead.
|
2010-01-19 00:28:49 +00:00
|
|
|
* Added the ability to perform SRV lookups on fast AGI calls. To use this
|
|
|
|
feature, simply use hagi: instead of agi: as the protocol portion
|
|
|
|
of the URI parameter to the AGI function call in your dial plan. Also note
|
|
|
|
that specifying a port number in the AGI URI will disable SRV lookups,
|
|
|
|
even if you use the hagi: protocol.
|
2010-06-16 18:43:22 +00:00
|
|
|
* No longer support MSG_OOB flag on HANGUP.
|
2007-12-03 21:03:05 +00:00
|
|
|
|
2007-12-19 09:20:37 +00:00
|
|
|
Logger changes
|
|
|
|
--------------
|
2007-11-21 18:38:18 +00:00
|
|
|
* Added rotatestrategy option to logger.conf, along with two new options:
|
|
|
|
"timestamp" which will use the time to name the logger files instead of
|
2009-06-27 09:51:45 +00:00
|
|
|
sequence number; and "rotate", which rotates the names of the log files,
|
2007-11-21 18:38:18 +00:00
|
|
|
similar to the way syslog rotates files.
|
|
|
|
* Added exec_after_rotate option to logger.conf, which allows a system
|
|
|
|
command to be run after rotation. This is primarily useful with
|
2009-06-27 20:26:01 +00:00
|
|
|
rotatestrategy=rotate, to allow a limit on the number of log files kept
|
2007-11-21 18:38:18 +00:00
|
|
|
and to ensure that the oldest log file gets deleted.
|
2007-12-26 15:58:17 +00:00
|
|
|
* Added realtime support for the queue log
|
2007-12-19 09:20:37 +00:00
|
|
|
|
2012-07-23 21:27:56 +00:00
|
|
|
Call Detail Records
|
2008-02-25 23:04:20 +00:00
|
|
|
-------------------
|
|
|
|
* The cdr_manager module has a [mappings] feature, like cdr_custom,
|
|
|
|
to add fields to the manager event from the CDR variables.
|
|
|
|
* Added cdr_adaptive_odbc, a new module that adapts to the structure of your
|
|
|
|
backend database CDR table. Specifically, additional, non-standard
|
|
|
|
columns are supported, merely by setting the corresponding CDR variable in
|
|
|
|
your dialplan. In addition, you may alias any column to another name (for
|
|
|
|
example, if you want the 'src' CDR variable to be column 'ANI' in the DB,
|
|
|
|
simply "alias src => ANI" in the configuration file). Records may be
|
|
|
|
posted to more than one backend, simply by specifying multiple categories
|
|
|
|
in the configuration file. And finally, you may filter which CDRs get
|
|
|
|
posted to each backend, by specifying a filter (which the record must
|
|
|
|
match) for the particular category. Filters are additive (meaning all
|
|
|
|
rules must match to post that CDR).
|
|
|
|
* The Postgres CDR module now supports some features of the cdr_adaptive_odbc
|
|
|
|
module. Specifically, you may add additional columns into the table and
|
|
|
|
they will be set, if you set the corresponding CDR variable name. Also,
|
|
|
|
if you omit columns in your database table, they will be silently skipped
|
|
|
|
(but a record will still be inserted, based on what columns remain). Note
|
|
|
|
that the other two features from cdr_adaptive_odbc (alias and filter) are
|
|
|
|
not currently supported.
|
2008-02-26 19:14:04 +00:00
|
|
|
* The ResetCDR application now has an 'e' option that re-enables a CDR if it
|
|
|
|
has been disabled using the NoCDR application.
|
2008-02-25 23:04:20 +00:00
|
|
|
|
2008-01-13 23:43:06 +00:00
|
|
|
Miscellaneous New Modules
|
|
|
|
-------------------------
|
2007-03-13 21:22:33 +00:00
|
|
|
* Added a new CDR module, cdr_sqlite3_custom.
|
|
|
|
* Added a new realtime configuration module, res_config_sqlite
|
2007-12-31 21:22:31 +00:00
|
|
|
* Added a new codec translation module, codec_resample, which re-samples
|
|
|
|
signed linear audio between 8 kHz and 16 kHz to help support wideband
|
|
|
|
codecs.
|
2008-01-09 21:37:26 +00:00
|
|
|
* Added a new module, res_phoneprov, which allows auto-provisioning of phones
|
|
|
|
based on configuration templates that use Asterisk dialplan function and
|
|
|
|
variable substitution. It should be possible to create phone profiles and
|
|
|
|
templates that work for the majority of phones provisioned over http. It
|
|
|
|
is currently only intended to provision a single user account per phone.
|
|
|
|
An example profile and set of templates for Polycom phones is provided.
|
|
|
|
NOTE: Polycom firmware is not included, but should be placed in
|
2008-01-13 19:19:57 +00:00
|
|
|
AST_DATA_DIR/phoneprov/configs to match up with the included templates.
|
|
|
|
* Added a new module, app_jack, which provides interfaces to JACK, the Jack
|
|
|
|
Audio Connection Kit (http://www.jackaudio.org/). Two interfaces are
|
|
|
|
provided; there is a JACK() application, and a JACK_HOOK() function. Both
|
|
|
|
interfaces create an input and output JACK port. The application makes
|
|
|
|
these ports the endpoint of the call. The audio coming from the channel
|
|
|
|
goes out the output port and whatever comes back in on the input port is
|
|
|
|
what gets sent to the channel. The JACK_HOOK() function turns on a JACK
|
|
|
|
audiohook on the channel. This lets you run the audio coming from a
|
|
|
|
channel through JACK, and whatever comes back in is what gets forwarded
|
|
|
|
on as the channel's audio. This is very useful for building custom
|
|
|
|
vocoders or doing recording or analysis of the channel's audio in another
|
|
|
|
application.
|
2008-01-16 22:36:58 +00:00
|
|
|
* Added a new module, res_config_curl, which permits using a HTTP POST url
|
|
|
|
to retrieve, create, update, and delete realtime information from a remote
|
|
|
|
web server. Note that this module requires func_curl.so to be loaded for
|
|
|
|
backend functionality.
|
2008-01-22 22:33:20 +00:00
|
|
|
* Added a new module, res_config_ldap, which permits the use of an LDAP
|
|
|
|
server for realtime data access.
|
2008-01-30 00:58:23 +00:00
|
|
|
* Added support for writing and running your dialplan in lua using the pbx_lua
|
2008-01-30 00:04:17 +00:00
|
|
|
module. See configs/extensions.lua.sample for examples of how to do this.
|
2008-01-13 23:43:06 +00:00
|
|
|
|
2012-07-23 21:27:56 +00:00
|
|
|
Miscellaneous
|
2008-01-13 23:43:06 +00:00
|
|
|
-------------
|
|
|
|
* Ability to use libcap to set high ToS bits when non-root
|
|
|
|
on Linux. If configure is unable to find libcap then you
|
|
|
|
can use --with-cap to specify the path.
|
|
|
|
* Added maxfiles option to options section of asterisk.conf which allows you to specify
|
|
|
|
what Asterisk should set as the maximum number of open files when it loads.
|
|
|
|
* Added the jittertargetextra configuration option.
|
|
|
|
* Added support for setting the CoS for VLAN traffic (802.1p). See the sample
|
|
|
|
configuration files for the IP channel drivers. The new option is "cos".
|
2012-05-03 18:43:54 +00:00
|
|
|
This information is also documented on the Asterisk wiki at
|
|
|
|
https://wiki.asterisk.org/wiki/x/EYBG
|
2008-01-13 23:43:06 +00:00
|
|
|
* When originating a call using AMI or pbx_spool that fails the reason for failure
|
|
|
|
will now be available in the failed extension using the REASON dialplan variable.
|
|
|
|
* Added support for reading the TOUCH_MONITOR_PREFIX channel variable.
|
|
|
|
It allows you to configure a prefix for auto-monitor recordings.
|
|
|
|
* A new extension pattern matching algorithm, based on a trie, is introduced
|
|
|
|
here, that could noticeably speed up mid-sized to large dialplans.
|
|
|
|
It is NOT used by default, as duplicating the behaviour of the old pattern
|
|
|
|
matcher is still under development. A config file option, in extensions.conf,
|
|
|
|
in the [general] section, called "extenpatternmatchingnew", is by default
|
|
|
|
set to false; setting that to true will force the use of the new algorithm.
|
|
|
|
Also, the cli commands "dialplan set extenpatternmatchingnew true/false" can
|
|
|
|
be used to switch the algorithms at run time.
|
|
|
|
* A new option when starting a remote asterisk (rasterisk, asterisk -r) for
|
|
|
|
specifying which socket to use to connect to the running Asterisk daemon
|
|
|
|
(-s)
|
2008-04-16 20:09:39 +00:00
|
|
|
* Performance enhancements to the sched facility, which is used in
|
|
|
|
the channel drivers, etc. Added hashtabs and doubly-linked lists
|
|
|
|
to speed up deletion; start at the beginning or end of list to
|
|
|
|
speed up insertion.
|
2008-04-16 17:14:18 +00:00
|
|
|
* Added Doubly-linked lists after the fashion of linkedlists.h. They are in
|
|
|
|
dlinkedlists.h. Doubly-linked lists feature fast deletion times.
|
|
|
|
Added regression tests to the tests/ dir, also.
|
2008-04-16 17:45:28 +00:00
|
|
|
* Added a refcount trace feature to astobj2 for those trying to balance
|
|
|
|
object creation, deletion; work, play; space and time. See the
|
|
|
|
notes in astobj2.h. Also, see utils/refcounter as well, as a
|
|
|
|
quick way to find unbalanced refcounts in what could be a sea
|
|
|
|
of objects that were balanced.
|
2008-01-16 18:34:19 +00:00
|
|
|
* Added logging to 'make update' command. See update.log
|
2008-01-24 17:47:50 +00:00
|
|
|
* Added strictrtp option to rtp.conf. If enabled this will drop RTP packets that
|
|
|
|
do not come from the remote party.
|
2008-01-30 00:04:17 +00:00
|
|
|
* Added the 'n' option to the SpeechBackground application to tell it to not
|
|
|
|
answer the channel if it has not already been answered.
|
2008-02-18 04:43:33 +00:00
|
|
|
* Added a compiler flag, CHANNEL_TRACE, which permits channel tracing to be
|
|
|
|
turned on, via the CHANNEL(trace) dialplan function. Could be useful for
|
|
|
|
dialplan debugging.
|
2008-03-26 17:10:28 +00:00
|
|
|
* iLBC source code no longer included (see UPGRADE.txt for details)
|
2012-07-23 21:27:56 +00:00
|
|
|
* If compiled with DETECT_DEADLOCKS enabled and if you have glibc, then if
|
2008-05-23 22:35:50 +00:00
|
|
|
deadlock is detected, a backtrace of the stack which led to the lock calls
|
2008-06-10 15:12:17 +00:00
|
|
|
will be output to the CLI.
|
2008-05-23 22:35:50 +00:00
|
|
|
* If compiled with DEBUG_THREADS enabled and if you have glibc, then issuing
|
|
|
|
the "core show locks" CLI command will give lock information output as well
|
2008-06-10 15:12:17 +00:00
|
|
|
as a backtrace of the stack which led to the lock calls.
|
2008-06-19 20:35:56 +00:00
|
|
|
* users.conf now sports an optional alternateexts property, which permits
|
2008-06-19 19:22:59 +00:00
|
|
|
allocation of additional extensions which will reach the specified user.
|
2008-07-28 19:53:56 +00:00
|
|
|
* A new option for the configure script, --enable-internal-poll, has been added
|
|
|
|
for use with systems which may have a buggy implementation of the poll system
|
2008-10-01 12:29:18 +00:00
|
|
|
call. If you notice odd behavior such as the CLI being unresponsive on remote
|
|
|
|
consoles, you may want to try using this option. This option is enabled by default
|
|
|
|
on Darwin systems since it is known that the Darwin poll() implementation has
|
|
|
|
odd issues.
|
2008-11-19 22:17:05 +00:00
|
|
|
|
|
|
|
Timer Changes
|
|
|
|
--------------------
|
|
|
|
* In addition to timing from DAHDI, there is a new timing module called
|
|
|
|
res_timing_timerfd. In order to use this, you must be running Linux with
|
|
|
|
a kernel version 2.6.25 or newer as well as glibc 2.8 or newer. The configure
|
|
|
|
script will be able to tell if you have the requirements. From menuselect, select
|
|
|
|
res_timing_timerfd from the Resource Modules menu.
|