Is there a reason for the requirement of the `;` suffix to appear in the config file? It seems like that is something that could be handled in the module itself (if there is no `;` in the first parameter, then add `;`, since as you said it's necessary for other internal processing) -- seems like lots of adopters will see this as an issue.
Also FYI, before I apply your patch, this is what I have... ``` INFO: rtp_media_server [rtp_media_server.c:583]: rms_bridging_call(): parsed[sip:conference@10.77.79.3:5080;][0] INFO: rtp_media_server [rtp_media_server.c:599]: rms_bridging_call(): si[0x7f791c637a18]call-id[0_448469831@2001:db8::99]cseq[0]ruri[31|sip:conference@10.77.79.3:5080;]remote_uri[sip:conference@10.77.79.3:5080]local_uri[sip:888@example.com] DEBUG: tm [uac.c:450]: t_uac_prepare(): next_hop=sip:conference@10.77.79.3:5080 DEBUG: tm [uac.c:158]: dlg2hash(): hashid 29747 DEBUG: tm [uac.c:678]: send_prepared_request_impl(): uac: 0x7f791c639b40 branch: 0 to 10.77.79.3:5080 DEBUG: <core> [core/onsend.c:50]: run_onsend(): required parameters are not available - ignoring ERROR: rtp_media_server [rtp_media_server.c:622]: rms_bridging_call(): tmb.t_request_within ok ```
I rebuilt Kamailio and all the Belledonne Communications deps last night.