MT#61441 rtpengine: use to-tag for NG message when rtpp-flags

Always use to-tag for NG message with rtpp-flags,
if presented. This change is caused by the processing
logic being moved to rtpengine with rtpp-flags.

Change-Id: Ib656fdccbd366053bab37ef04c48659a6fd3acc1
(cherry picked from commit e527845822)

debian/patches/series

@@ -53,6 +53,7 @@ sipwise/cfgutils-allow-lock_set_size-14.patch
 sipwise/pua-get_record_puadb-add-pres_uri-to-the-query.patch
 sipwise/pua_dialoginfo-use_uuid.patch
 ### active development
+sipwise/rtpengine_always_add_totag_to_ng_message_when_rtpp_flags.patch
 #
 ### Don't just put stuff in any order
 ### use gbp pq import/export tooling to help maintain patches

debian/patches/sipwise/rtpengine_always_add_totag_to_ng_message_when_rtpp_flags.patch

@@ -0,0 +1,11 @@
+--- a/src/modules/rtpengine/rtpengine.c
++++ b/src/modules/rtpengine/rtpengine.c
+@@ -3179,7 +3179,7 @@ static bencode_item_t *rtpp_function_cal
+ 	 */
+ 
+ 	/* affects to-tag parsing */
+-	ng_flags.to = (op == OP_DELETE) ? 0 : 1;
++	ng_flags.to = (!parse_by_module || op != OP_DELETE) ? 1 : 0;
+ 
+ 	/* module specific parsing */
+ 	if(parse_by_module && flags && parse_flags(&ng_flags, msg, &op, flags->s))