9 Feb
2016
9 Feb
'16
9:48 a.m.
On 09.02.2016 03:09, Juha Heinanen wrote:
With latest rtpengine module, rtpengine_offer
generates to syslog:
Feb 9 03:05:03 lohi /usr/bin/sip-proxy[11835]: NOTICE: rtpengine [rtpengine.c:2792]:
select_rtpp_node_old(): rtpengine hash table lookup failed to find node for calllen=16
callid=48e2ba8176be0f4a viabranch=z9hG4bK9c06a007a1197f4b0
Why such a message? Looking at the code, it seems to be OK that the
node is not found on a first call of rtpengine_offer:
Hi Juha,
The NOTICE message indicates that there is no entry in the hastable for
the *(callid, viabranch)* pair, and the node selection algorithm will
start running (select_rtpp_node_new()). This means that a new entry will
be added in the hastable, containing the selected node for the pair.
The above is applicable for the delete() also, meaning that maybe other
node could be selected than the one for the offer() and the call not
being deleted properly from the original, offer() node.
IMO, the logs can go LM_DBG, because the info is useful when trying to
debug a rtpengine call.
Regards,
Stefan