Reidar Cederqvist authored 1 year ago and Yalu Zhang committed 1 year ago

This is to avoid cases where the uci option is directly pushed into the asterisk config without
checking the value, otherwise the value can contain a newline followed by a malicious asterisk config option+value.
Note that '\n' is allowed in the value of an option or list.

Workaround for reference count correction 

Channel reference count correction for transfer

Configuration for retries of SIP Registration failover

Fix an issue that codec is not synchronised when switching between two calls

In case multiple server addresses exist, once client received
SIP regisration response 408/503/500 from one address, it will
then move to next address. If all addresses are tried and failed,
the client will schedule a new retry with certain interval.

Following options are added to UCI asterisk sip_service_provider
section for configuring SIP failover.

   - asterisk.sip0.failover_max_retries
     Max number of failover retries.
     By default, '-1', which means unlimited.

   - asterisk.sip0.failover_interval1
     The failover begin with the retry interval.
     By default, 10 seconds.

   - asterisk.sip0.failover_interval2
     After every 3 continuous failed retries (one RETRY trys all server addresses)
     the interval is used to schedule the next retry.
     By default, 60 seconds.

Lwithwma Brahma authored 2 years ago and George Yang committed 1 year ago

The outbound_proxy was added as per the asterisk doc.
https://wiki.asterisk.org/wiki/display/AST/PJSIP+with+Proxies

Change-Id: Id942ae1bae9f5e8242b7381d6e1cfd77601d3229

When applying asterisk server URI, asterisk.sip_service_provider.host
should take precedence over asterisk.sip_service_provider.domain.

TR104 parameters ...SIP.Network.RegistrarServer and .ProxyServer
are all mapped to UCI asterisk.sip_service_provider.host.

Change-Id: I685480308740b9ced922274f6837d0471bdf574c

Fix an un-hold issue during the failed 2nd outgoing call

Fix a bug that unexpected ringing is heard when transferor finishes transfer and hangs up

Fix a bug that RTP/RTCP log messages are shown even if RTP/RTCP debug is disabled

Fix a dead lock and remove some duplicated indications during un-hold

Add missing linking libraries for RDK

DNS SRV resolver: stick to the server address which is used most recently

Cleanup ast_channel references for both hold and unhold SIP channels

 - Add support for single or multiple call mode   
 - Make RTP timestamp always have a proper value 

Change the log lelvel and message to avoid misleading on devices without DECT support

- Relace the calls to ubus_free() with ast_ubus_free_context()
- Remove the definition of ubus_free_context() which has been moved to Asterisk

038e34d Fix the memory leak in blob_buf
679e002 Initialize the pointer to NULL for safety
a2cb58d Fix a memory corruption issue related to ubus_free
f5cb2e8 Add emergency attribute to the output of call_status ubus object

Fix memory leak in chan_voicemngr_request()

Merge commit 9746ae8f as specified
in feeds.conf.default of OpenWrt tag v23.05.2.

Do this merge "in the other direction", i.e. merge devel into the branch
instead of merging the branch into devel. This helps git blame attribute
code lines to the actual OpenWrt commits instead of the accidentally
squashed commit 975b3a25 (Upgrade to OpenWrt-23.05.0-rc3,
2023-10-03).

This reverts the merge-commit which was accidentally squashed and by
merging re-units the history before the bad commit with the history
after the bad commit. For details, see 4edc2c18 (Merge commit
f7fbaea4 (OpenWrt v23.05.0-rc3) into
merge-openwrt-23.05.0-rc3-properly, 2023-11-22).

This merge commit does not introduce any changes to the code. It's sole
purpose is to re-unite the histories.

Merge commit f7fbaea4 as specified
in feeds.conf.default of OpenWrt tag v23.05.0-rc3.

This merge has been done in commit 975b3a25 (Upgrade to
OpenWrt-23.05.0-rc3, 2023-10-03), but it had several issues:

1. Not a proper merge commit, thus losing all history and making future
   merges hard.
2. Things from 22.03 had been left inside the branch when merging which
   created errors when running make and feeds update due to errors in
   Makefiles. In this merge we take the 23.05.0-rc3 side and discard
   changes from 22.03.

Do this merge commit right before the bad commit had been done. After this merge
commit, the bad commit and a revert of the bad commit will be merged
into this branch to re-unite the histories. Doing it this way will make
sure that git blame will attribute lines to the proper OpenWrt commit
instead of the squashed bad commit. Later we can then merge this branch
with the history of latest devel.

This reverts commit 975b3a25.
This should have been a merge-commit, but it has been accidentally
squashed.

 * Fix a crash due to wrong handling of 200 OK to REGISTER    
 * merges the proper history of Asterisk 20.3.0 by reverting
an accidentally squashed merge and doing a proper merge commit after

 * fd273d62 : lower the log level for loading moh to debug   
 * a659b358 : cherry-picked the fix for unload mwi module during shutdown from asterisk project  

Parse RTCP SR and RR packets for inter-arrival-jitter calculations

Wenpeng Song authored 1 year ago and Yalu Zhang committed 1 year ago

Skip to use the combination of `sed` and `escape_sed_substitution` in this case. 
This fixes the incoming issue after the openwrt lift, due to the syntax and return
value for the combination usage of `sed` and `escape_sed_substitution`.