This is a normal condition for a first offer. Reduce log level to debug.

NGCP-Flow: mr13.1
Change-Id: I785cee82ead90b1e797c09017c3e3a77da113553
(cherry picked from commit d483ef185b)
(cherry picked from commit 6da0da81e8)

Change-Id: I5aa4a887eedd3eff31097a2fe8ba935470309100
(cherry picked from commit caeeb26f16)
(cherry picked from commit 2c69c26a86)

Make sure we properly return a failure if no supported payload type is
present.

Change-Id: Ia483e0819b2d8ca0c2c5184c929dfe3d05c96ca1
(cherry picked from commit 5f6609de5d)
(cherry picked from commit e0d72cc445)

Make sure a codec is not only known to us, but that it can actually be
used, in places where it makes sense. This is partially redundant
because ensure_codec_def_type already takes care of this, but a codec
definition may come from a different source, so it doesn't help to
double check.

Change-Id: I91af84afc2477840f1400674b2538ad8fb7746ee
(cherry picked from commit 7b60e85970)
(cherry picked from commit 8256c1662b)

Change-Id: Iff873374618c37efcbb366ed1f8914ee53bac28f
(cherry picked from commit c31b421ce2)
(cherry picked from commit 66e6af52ae)

These are potentially computed from inside each subdir, and in addition
due to what appears to be a regression in GNU make 4.4, where it is
reevaluating variables that contain $(shell) functions, many times (in
the order of thousands, this was slowing down the build, were on the
Debian amd64 build daemons it went from 5m with GNU make 4.3 to 2h40m
with GNU make 4.4. Although the bulk of the slow down has been fixed
with previous commits, the remaining optimizations are only to avoid
this potentially happening again in the future, and to reduce useless
duplicate work.

Instead of trying to cache the values from within make itself, where
programming this there is extremely painful, and does not seem to be
able to greatly reduce the number of calls, because the build system
is going to be called multiple times for different targets. Simply
externalize the generation into several shell scripts, that we call
to generate a make fragment that then we include from the various
Makefiles.

For a Debian build with GNU make 4.3, this reduces the amount of total
pkg-config calls from around ~1600 to 128, for dpkg-buildflags from
~1100 down to 6, and for dpkg-parsechangelog from ~56 to 17, but the
slow down is not as significant there anyway.

For a Debian build with GNU make 4.4, this reduces the amount of total
pkg-config calls from around ~2600 to 128, for dpkg-buildflags from
~2800 down to 6, and for dpkg-parsechangelog from ~350 to 21.

For a Debian build with GNU make 4.4, this reduces the build time
on this system from 2m10s to ~ 1m30s.

Change-Id: I427d0ea5106dc6ed1ff9e664ccdba2fa0725b7d0
(cherry picked from commit 7dbe24e4e5)
(cherry picked from commit 47205d8824)

This variable is unknown to dpkg-buildflags. This also reduces the
amount of global calls generated with GNU make 4.4 (which has a
regression causing massive amounts of shell calls to be generated).

Change-Id: Ia9d7099228bf5e181df4725939ed4f76f1e63dc9
(cherry picked from commit bb2bf3a702)
(cherry picked from commit 46bac41b1a)

This makes sure the target is the default, regardless of the place where
it gets declared, so that we do not get surprises due to targets
declared in includes that might happened to be performed before the
default target.

Change-Id: I2fab47ccb46d68dc56332acef966e369c5183c07
(cherry picked from commit 5cb1002949)
(cherry picked from commit a333308431)

Change-Id: I6998c501042db66897d2f790d82b90b6fd09d909
(cherry picked from commit 2f53560f25)
(cherry picked from commit 2f8116b8b3)

Starting with GNU make 4.4, build time have massively regressed
where before they would take 5m on amd64 now can take 2h40m. While this
seems clearly broken, the release notes are filled with notices for
breaking changes, and in particular the one for passing all make
variables down to the invoked programs executed via the «shell» GNU make
function, so it is not clear what is expected breakage and what is not.

This has been reported in Debian, but not yet upstream, and while it
seems like a clear regression, it's not clear what will be the upstream
take on it. For now apply workarounds that do not change semantics, and
which do not regress with older GNU make versions.

Use the GNU make «origin» function instead of «?=» which defaults to
defining a variable as a recursive one. Coerce already defined variables
into simple ones to avoid GNU make re-evaluating these variables for
each «shell» function invocation.

Ref: https://bugs.debian.org/1092051
Change-Id: I076fc05dd616918473a22e7e942fecfdc9851d47
(cherry picked from commit 887fb40f3f)
(cherry picked from commit 4c114ab9af)

Change-Id: I842b65571dc571c7c1a482dea62bb69d47700efd
(cherry picked from commit 928dd269b0)
(cherry picked from commit 415f9c2d85)

Change-Id: Ib881bfc3311a0d1e19a2d95bca671a607b678f08
(cherry picked from commit e234e11c98)
(cherry picked from commit 965f3590c0)

Change-Id: I1ed0a25b25e22f901d4811ff9e4ef9d8e087a4ad
(cherry picked from commit 7a58f4eb29)
(cherry picked from commit ee612d6f55)

If the receiver of a previously passthrough T.30 stream gets switched to
a generated PCM stream from a T.38 gateway, continue the sequencing of
the previous SSRC. Technically this is not necessary as the generated
PCM stream gets a new SSRC, but at least Asterisk seems to ignore this
and expect sequencing to continue, and will ignore PCM if the sequence
jump is too large.

Change-Id: Ia4656770db11f5fa1a1e9bf5bd71a0398deb1e00
(cherry picked from commit 18579227a9)
(cherry picked from commit 6422500ba3)

Just add the make target. Don't run it as part of the test suite as it's
quite extensive. Update the script a bit as well.

Change-Id: I192e90413bd7ffde842571324c816e4271367b42
(cherry picked from commit 0f55781a58)
(cherry picked from commit f8b8e7e80e)

Add a simple function that acts as an encryption callback to just update
the ext_seq (index) of the egress SSRC context. The kernel module
already does this, but the daemon only did it when SRTP was involved.
This now tracks egress packet indexes in all cases.

Change-Id: I9460744de55ead4b05aceb322fd8482442ff2b41
(cherry picked from commit 0da49000ba)
(cherry picked from commit 9279f30f75)

Change-Id: Ia43e1eb373c893df6693032a14eb631f16593094
(cherry picked from commit a19bed611c)
(cherry picked from commit edc98621c8)

Some components (the timer thread used by the codec handlers in
particular) may hold references to components owned by the codeclib (the
.so handles in particular). Move codeclib cleanup towards the end.

Change-Id: Ic581588c27b69c025576c14a69e999c9ca5d1597
(cherry picked from commit 43cc9cc06d)
(cherry picked from commit c747a9ad26)

Fixes a corner case that happens when trying to delete a call created with
ng offer and no-redis-update flag and for which no ng answer was received.
In such cases, one would receive warning messages from Redis
"ERR DB index is out of range".

What happens is that on call creation redis_hosted_db defaults to -1. This
value is changed when writing to Redis, but the writing is not done for a
ng offer with no-redis-update.

Kudos go to Pawel Kuzak.

Closes #1910

Change-Id: Iad19ec8ac69b169e6352662697b17eb23e6970fb
(cherry picked from commit bba9625b25)
(cherry picked from commit 1df2df383e)

Change-Id: I4b5536692d7076d8bcadd4ffbaf2312ecac5981e
(cherry picked from commit 4cdb8eaaca)
(cherry picked from commit 4223696ddb)

Just cover it with already existing lock
used below, but move upper.

Fixes Covery Scan detected defect:

*** CID 1621443:  Concurrent data access violations  (MISSING_LOCK)
/daemon/redis.c: 2232 in json_restore_call()
2226                            call_destroy(c);
2227                    release_closed_sockets();
2228                    if (must_release_pop) // avoid deadlock with redis_notify->lock below
2229                            redis_ports_release_pop(false);
2230                    must_release_pop = false;
2231
>>>     CID 1621443:  Concurrent data access violations  (MISSING_LOCK)
>>>     Accessing "rtpe_redis_write->db" without holding lock "redis.lock".
>>>     Elsewhere, "redis.db" is written to with "redis.lock" held 1 out of 1 times.
2232                    redis_select_db(rtpe_redis_write, rtpe_redis_write->db);
2233
2234                    mutex_lock(&rtpe_redis_write->lock);
2235                    redisCommandNR(rtpe_redis_write->ctx, "DEL " PB, PBSTR(callid));
2236                    mutex_unlock(&rtpe_redis_write->lock);
2237

Change-Id: Iff3425451f82218480dcc08f42ea7bddbd6f672f
(cherry picked from commit bebc6f8f31)
(cherry picked from commit 0a9b5fbdff)

Deleting a call can have the side effect of changing the active Redis DB
on the writing instance. Restore the correct DB afterwards if needed.

Fixes #1905

Change-Id: I12dae767ffa5d25703e024d2ec59aa21ba9da101
(cherry picked from commit fdabc9b59e)
(cherry picked from commit 6df71f2be7)

A call that gets created but then doesn't get initialised would have its
Redis DB left at zero. At destruction it would then try to switch to DB
zero. Fix this by using an appropriate initial value.

Closes #1905

Change-Id: I852e48c5a06b732b37d2ccd5c478de4760aacd4e
(cherry picked from commit add46f265a)
(cherry picked from commit 55f48a3bd6)

If keyspace notifications are used at all, the respective objects and
threads must be created during startup. This requires at least some
keyspace to be configured. To support usage without any keyspaces
initially (and add them during runtime), add a special case (set
keyspace to -1).

Convert all keyspace variables to signed ints. Ignore negative keyspace
numbers where appropriate. Support Redis endpoint addresses without
database number.

Fixes #1902

Change-Id: I45a3c87bc515f9b14e64ec1ec0906dde271b5f8d
(cherry picked from commit fb1ad3f0cf)
(cherry picked from commit bf60ce2744)

If keyspace notifications are not configured at all, bail with an error
when there is an attempt to add a new keyspace or remove one. We get a
segfault otherwise.

Closes #1902

Change-Id: Ie47cf5f7762792aabe38476739f0dcf9927787ce
(cherry picked from commit 6dbf098bc7)
(cherry picked from commit 96f5adaee1)

Change-Id: I949a715f1037df2c84c84565df8ea0fda14be191
(cherry picked from commit c07ab48457)
(cherry picked from commit 947b551781)

Avoids segfault is extra connection can't be established

Closes #1903

Change-Id: I6eb7315f6774015703c7ad036e08596f7f550d60
(cherry picked from commit 172f389395)
(cherry picked from commit 4ed9638e02)

Change-Id: I76f21d6c44f04e063cb57dd04f1f631dead0600a
(cherry picked from commit 3bbf4d94a1)
(cherry picked from commit 858ea8966d)

Change-Id: I55f1dad9480a991e512061f3ecaee00b865d9cad
(cherry picked from commit 3e0bd2e76f)
(cherry picked from commit 8125f29afa)

A matching payload type number in an answer might not be enough to
establish compatible codecs. Also check the format parameters. Reject
and ignore answer codecs that are not compatible.

Change-Id: I12a1287216886926ec4b3c704029c923f815b429
(cherry picked from commit 9c00f30475)
(cherry picked from commit 4860915441)

We don't parse these out and formats should be compatible.

Change-Id: Ie106591f3d12539eb1101793b50df9db97637625
(cherry picked from commit 68ad1dc8df)
(cherry picked from commit 008cb84e32)

Teach rtpengine to distinguish between G.729 with and without annex B,
which are incompatible to each other.

Change-Id: I09b66a097007ba3283546880f06f81b4f89e126d
(cherry picked from commit 7ab4009a0b)
(cherry picked from commit 55d76399f5)

Change-Id: I297199255b0d5204b0f978dc7306da8f2b6e6e34
(cherry picked from commit 9262cac855)
(cherry picked from commit d5947c47ad)

Make the year's value automatic.

Change-Id: I6b1ab23144c758aa047cdcbaf26ba86745d150c9
(cherry picked from commit 20d9db2966)
(cherry picked from commit d7e8810185)

Make entry tree simpler and give
links to commonly used things like
NG control protocol.

This simplifies usage of documentation.

Change-Id: I1283bf8a88c7c6e4ff7ab9451610bc6e224c0119
(cherry picked from commit 16b7200ed1)
(cherry picked from commit 38534f3dea)

Secondary titles have to be smaller:
- to embed it easier into the toctree of index file
- to have better readability for users (github,RTD)

Change-Id: If8f97f97b1d64b7593228eeda16c794e66453c27
(cherry picked from commit 2514d36129)
(cherry picked from commit 08e54d8152)

Remove the intro information from index,
because already mentioned in the overview.

Also change a greeting title.

Change-Id: I5c232fa033eac8e3097ad5adb351e8940a33a4ee
(cherry picked from commit a07b972000)
(cherry picked from commit f3bc68d7b4)

Reported in #1896

Change-Id: I58d09ef930c8fa55efa5592ff746a65270dea68b
(cherry picked from commit aca2433bbd)
(cherry picked from commit 1ca5c55808)

HTTP/WS init creates worker threads, which would be terminated by a fork
to background. Reverse the order.

Closes #1896
Possibly also relevant to #1895

Change-Id: I30b61e07ad3bed41b6b241e8943ed479277c1474
(cherry picked from commit dd04af1163)
(cherry picked from commit 12e22f2c8b)

Closes #1898

Change-Id: I585db2307f750abc18f9918451cab6c6c693965c
(cherry picked from commit f443bd8ce2)
(cherry picked from commit da90378b4b)

Change-Id: I2367ac1d490e5451d46629618ece513166faa2bd
(cherry picked from commit 7c7f627418)
(cherry picked from commit 4df2cf75b8)

Fixes regression from the sdp_create rework.

Change-Id: I875052a0e229bca529ea461d7cd3c1c068feebee
(cherry picked from commit 18e0db51a9)
(cherry picked from commit 10c83eca5a)

No-op.

Change-Id: Ie63441499544d39f9de2eb87c305b17a84a5ec8c
(cherry picked from commit e97aaca4a3)
(cherry picked from commit de6f1a30c1)