The session limit is only for calls an rtpengine is responsible for.
Foreign calls (coming in via redis notification) are not counted as
long as the rtpengine is not responsible for those calls.
At least that means that the limit may exceed if the calls the rtpengine
is responsible for plus the former foreign calls are greater than the limit.
This will happen suddenly when the rtpengine becomes responsible for the
foreign calls.
@ -33,6 +33,8 @@ static void cli_incoming_list_totals(char* buffer, int len, struct callmaster* m
ADJUSTLEN(printlen,outbufend,replybuffer);
printlen=snprintf(replybuffer,(outbufend-replybuffer)," Total managed sessions :"UINT64F"\n",num_sessions);
ADJUSTLEN(printlen,outbufend,replybuffer);
printlen=snprintf(replybuffer,(outbufend-replybuffer)," Total foreign sessions :"UINT64F"\n",atomic64_get(&m->totalstats.total_foreign_sessions));
ADJUSTLEN(printlen,outbufend,replybuffer);
printlen=snprintf(replybuffer,(outbufend-replybuffer)," Total rejected sessions :"UINT64F"\n",atomic64_get(&m->totalstats.total_rejected_sess));
ADJUSTLEN(printlen,outbufend,replybuffer);
printlen=snprintf(replybuffer,(outbufend-replybuffer)," Total timed-out sessions via TIMEOUT :"UINT64F"\n",atomic64_get(&m->totalstats.total_timeout_sess));
@ -164,8 +166,8 @@ static void cli_incoming_list_callid(char* buffer, int len, struct callmaster* m