Browse Source

MT#55283 prevent erroneous swithch to DB 0

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)
mr11.5
Richard Fuchs 11 months ago
parent
commit
322e00b60a
2 changed files with 2 additions and 1 deletions
  1. +1
    -0
      daemon/call.c
  2. +1
    -1
      include/call.h

+ 1
- 0
daemon/call.c View File

@ -3806,6 +3806,7 @@ static struct call *call_create(const str *callid) {
c->created = rtpe_now;
c->dtls_cert = dtls_cert();
c->tos = rtpe_config.default_tos;
c->redis_hosted_db = -1;
if (rtpe_config.cpu_affinity)
c->cpu_affinity = call_socket_cpu_affinity++ % rtpe_config.cpu_affinity;
else


+ 1
- 1
include/call.h View File

@ -688,7 +688,7 @@ struct call {
sockaddr_t xmlrpc_callback;
endpoint_t dtmf_log_dest;
unsigned int redis_hosted_db;
int redis_hosted_db;
struct recording *recording;
str metadata;


Loading…
Cancel
Save