<p>Yes, devices behind NAT are not having replies processed correctly.  Kamailio forgets they're behind NAT.  Without topos loaded, it's able to remember that and handles the reply correctly.</p>
<p>I've got several IP Phones and Asterisk behind NAT that exhibit the problem. On the other side is a Metaswitch.</p>
<p>This was the first major difference I spotted, but I've since uncovered further unexpected behaviour with INVITES.  It appears the initial INVITE is forwarded with the modified headers and then a second INVITE is forwarded that's missing the Contact header, but is otherwise identical.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/kamailio/kamailio/issues/1005#issuecomment-281419458">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AF36ZVtKMiENauPvLKXXDXwh18GQsr_zks5reyHdgaJpZM4MG_mh">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AF36ZfxD5smQ5X0iq63215NxBVDBHsmQks5reyHdgaJpZM4MG_mh.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/kamailio/kamailio/issues/1005#issuecomment-281419458"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/kamailio/kamailio","title":"kamailio/kamailio","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/kamailio/kamailio"}},"updates":{"snippets":[{"icon":"PERSON","message":"@dryvoip in #1005: Yes, devices behind NAT are not having replies processed correctly.  Kamailio forgets they're behind NAT.  Without topos loaded, it's able to remember that and handles the reply correctly.\r\n\r\nI've got several IP Phones and Asterisk behind NAT that exhibit the problem. On the other side is a Metaswitch.\r\n\r\nThis was the first major difference I spotted, but I've since uncovered further unexpected behaviour with INVITES.  It appears the initial INVITE is forwarded with the modified headers and then a second INVITE is forwarded that's missing the Contact header, but is otherwise identical."}],"action":{"name":"View Issue","url":"https://github.com/kamailio/kamailio/issues/1005#issuecomment-281419458"}}}</script>