https://osmocom.org/https://osmocom.org/favicon.ico?16647414092022-02-20T14:00:22ZOpen Source Mobile Communicationsosmo-sip-connector - Bug #5462: Contact Header Missing - Way Forward?https://osmocom.org/issues/5462?journal_id=236712022-02-20T14:00:22Zlaforge
<ul></ul><p>some other folks have worked around this by adding the contact header <em>only</em> if the sofia-sip version is >= a certain version.</p>
<p><a class="external" href="https://github.com/meetecho/janus-gateway/pull/2708">https://github.com/meetecho/janus-gateway/pull/2708</a></p>
<p>This could be an acceptable workaround, if upstream doens't have any intrest in fixing their regression. They've meanwhile tagged new releases which likely still expose that regression.</p> osmo-sip-connector - Bug #5462: Contact Header Missing - Way Forward?https://osmocom.org/issues/5462?journal_id=236722022-02-21T05:51:44Zlynxis
<ul></ul><p>IMHO: libsofia is lost if nobody else is doing a fork. We should move to a different library.</p>
<p>I'm fine in doing the workaround but unsure how stable the sip-connector will be with current libsofia versions.</p>
<p>Some background about my opinion on libsofia. The freeswitch people used to have a fork of libsofia in-tree as hard copy in the freeswitch VCS. After years of keeping it in this way they split libsofia off without cleaning any version history.<br />Also there are a lot of commits without out any proper commit messages and doing multiple commits with the same commit message. (e.g. Fix FS-2342). While "FS" means a reference to the deprecated jira ticket system.<br />They also fixed bugs of freeswitch in libsofia without describing the real background and why this commit fixed the issue. Without knowing any background the commit doesn't look related and seems to fix it on the wrong end.<br />Exactly one of those commits broke libsofia for us.</p>