<p>Yes, this only makes sense with CONTACT_ONLY matching mode. That mode, along with a UAC which changes call IDs when re-registering, will provoke this case.</p>

<p>I observed it in a situation where we added our own custom matching mode which matched off of a token sent by UACs to better handle multiple network NAT situations. It's much easier to run across in that situation.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br>Reply to this email directly or <a href="https://github.com/OpenSIPS/opensips/pull/346#issuecomment-57709008">view it on GitHub</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/5479561__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcyNzkwMzQ5OCwiZGF0YSI6eyJpZCI6NDQ1MTA1Njh9fQ==--2e9efcc999a2ac2d3cfd74550f54c4fe876e3db1.gif" width="1" /></p>
<script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","description":"View this Pull Request on GitHub","action":{"@type":"ViewAction","url":"https://github.com/OpenSIPS/opensips/pull/346#issuecomment-57709008","name":"View Pull Request"}}</script>