This repository has been archived by the owner on Dec 21, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathCHANGES
5150 lines (4362 loc) · 250 KB
/
CHANGES
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
==============================================================================
===
=== 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.
===
==============================================================================
------------------------------------------------------------------------------
--- Functionality changes from Asterisk 13.8.0 to Asterisk 13.9.0 ------------
------------------------------------------------------------------------------
chan_pjsip
------------------
* Added 'pjsip show channelstats' CLI command.
res_pjsip_outbound_publish
------------------
* Added support for setting the transport used on outbound publish
using the transport configuration option.
------------------------------------------------------------------------------
--- Functionality changes from Asterisk 13.7.0 to Asterisk 13.8.0 ------------
------------------------------------------------------------------------------
res_pjsip_caller_id
------------------
* Per RFC3325, the 'From' header is now anonymized on outgoing calls when
caller id presentation is prohibited.
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
------------------
* 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.
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.
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.
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.
* 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.
res_pjsip
------------------
* 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.
* 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_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.
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.
Queue
-------------------
* Added field ReasonPause on QueueMemberStatus if set when paused, the reason
the queue member was paused.
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.
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.
------------------------------------------------------------------------------
--- Functionality changes from Asterisk 13.6.0 to Asterisk 13.7.0 ------------
------------------------------------------------------------------------------
Codecs
------------------
* Added format attribute negotiation for the VP8 video codec. Format attribute
negotiation is provided by the res_format_attr_vp8 module.
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.
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.
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.
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'.
* 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:
- A GAUGE statistic for the overall number of outbound registrations, i.e.:
PJSIP.registrations.count
- A GAUGE statistic for the overall number of outbound registrations in a
particular state, e.g.:
PJSIP.registrations.state.Registered
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
* If res_statsd is loaded and a StatsD server is configured, basic statistics
regarding the state of PJSIP contacts will now be emitted. This includes:
- A GAUGE statistic for the overall number of contacts in a particular
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
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.
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).
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
number of endpoints in the technology agnostic state of the endpoint -
online or offline - as well as the number of channels associated with each
endpoint. These are recorded as three different GAUGE statistics:
- endpoints.count
- endpoints.state.{unknown|offline|online}
- endpoints.{tech}.{resource}.channels
------------------------------------------------------------------------------
--- 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.
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.
The ARI version has been bumped to 1.9.0 as a result.
* 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.
------------------------------------------------------------------------------
--- 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.
* Added the Linkedid header to the common channel headers listed for each
channel in AMI events.
ARI
------------------
* A new feature has been added that enables the retrieval of modules and
module information through an HTTP request. Information on a single module
can be also be retrieved. Individual modules can be loaded to Asterisk, as
well as unloaded and reloaded.
* 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.
* A new feature has been added that allows for the rotation of log channels
through HTTP requests.
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.
* 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.
* 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.
------------------------------------------------------------------------------
--- 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.
* The configuration setting 'progressinband' now defaults to 'no', which
matches the actual behavior of previous versions.
* 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.
res_pjsip
------------------
* A new CLI command has been added: "pjsip show settings", which shows
both the global and system configuration settings.
* 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.
* 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".
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.
------------------------------------------------------------------------------
--- 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.
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.
------------------------------------------------------------------------------
--- Functionality changes from Asterisk 13.1.0 to Asterisk 13.2.0 ------------
------------------------------------------------------------------------------
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.
chan_pjsip
------------------
* New 'user_eq_phone' endpoint setting. This adds a 'user=phone' parameter
to the request URI and From URI if the user is determined to be a phone number.
* New global setting 'keep_alive_interval'. Setting this to a non-zero value
will cause keep alive messages to be sent periodically over connection
oriented transports.
* New 'PJSIP_AOR' and 'PJSIP_CONTACT' dialplan functions have been added which
allow examining PJSIP AORs or contacts from the dialplan.
res_pjsip_config_wizard
------------------
* This is a new module that adds streamlined configuration capability for
chan_pjsip. It's targetted at users who have lots of basic configuration
scenarios like 'phone' or 'agent' or 'trunk'. Additional information
can be found in the sample configuration file at
config/samples/pjsip_wizard.conf.sample.
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.
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
use this, you must be using PJProject version 2.4 or higher.
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.
* "language" (the default spoken language for the channel) is now included in
the standard channel state output for suitable events.
* 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.
AMI
------------------
* "Language" (the default spoken language for the channel) is now included in
the standard channel state output for suitable events.
* 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.
------------------------------------------------------------------------------
--- Functionality changes from Asterisk 13.0.0 to Asterisk 13.1.0 ------------
------------------------------------------------------------------------------
AMI
------------------
* Event NewConnectedLine is emitted when the connected line information on
a channel changes.
* The version of AMI has been bumped to 2.6.0 to account for the backwards
compatible feature listed above.
ARI
------------------
* Event ChannelConnectedLine is emitted when the connected line information
on a channel changes.
* The version of ARI has been bumped to 1.6.0 to account for the backwards
compatible feature listed above.
Core Transfers
-----------------
The features.conf general section has three new configurable options:
* transferdialattempts
* transferretrysound
* transferinvalidsound
For more information on what these options do, see the Asterisk wiki:
https://wiki.asterisk.org/wiki/x/W4fAAQ
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.
res_pjsip_endpoint_identifer_ip
------------------
* New CLI commands have been added: "pjsip show identif(y|ies)", which lists
all configured PJSIP identify objects
------------------------------------------------------------------------------
--- Functionality changes from Asterisk 12 to Asterisk 13 --------------------
------------------------------------------------------------------------------
Overview
------------------
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
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
------------------
* This module was deprecated and has been removed. Users of app_dahdibarge
should use ChanSpy instead.
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.
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.
ReadFile
------------------
* This module was deprecated and has been removed. Users of app_readfile
should use func_env's FILE function instead.
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.
SayCountPL
------------------
* This module was deprecated and has been removed. Users of app_saycountpl
should use the Say family of applications.
SetMusicOnHold
------------------
* The SetMusicOnHold dialplan application was deprecated and has been removed.
Users of the application should use the CHANNEL function's musicclass
setting instead.
WaitMusicOnHold
------------------
* The WaitMusicOnHold dialplan application was deprecated and has been
removed. Users of the application should use MusicOnHold with a duration
parameter instead.
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
* Add the ability to specify multiple email addresses in configuration,
separated by a |.
CDR Backends
------------------
cdr_sqlite
-----------------
* This module was deprecated and has been removed. Users of cdr_sqlite
should use cdr_sqlite3_custom.
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.
CEL Backends
------------------
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.
Channel Drivers
------------------
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.
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.
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.
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.
Core
------------------
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)
* The AMI action PJSIPShowEndpoint now includes ContactStatusDetail sections
that give information on Asterisk's attempts to qualify the endpoint.
* 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.
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
------------------
* 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).
Functions
------------------
JACK_HOOK
------------------
* The JACK_HOOK function now supports audio with a sample rate higher than
8kHz.
Resources
------------------
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.
res_pjsip_outbound_publish
------------------
* 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.
------------------------------------------------------------------------------
--- Functionality changes from Asterisk 12.4.0 to Asterisk 12.5.0 ------------
------------------------------------------------------------------------------
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.
* 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.
* 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.
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
------------------
* 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.
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.
------------------------------------------------------------------------------
--- 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.
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.
------------------------------------------------------------------------------
--- 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.
* 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.
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.
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