<p></p>
<p dir="auto">Hi. I have simple call flow:</p>
<pre><code> UAS        PROXY        UAS
1 |   INVITE  |           |
  |---------->|           |
2 |    100    |           |
  |<----------|           |
3 |           |   INVITE  |
  |           |---------->|
4 |           |    100    |
  |           |<----------|
5 |           |    180    |
  |           |<----------|
6 |    180    |           |
  |<----------|           |
7 |           |    183    |
  |           |<----------|
8 |    183    |           |
  |<----------|           |
9 |  CANCEL   |           |
  |---------->|           |
10|           |  CANCEL   |
  |           |---------->|
11|    200    |           |
  |<----------|           |
12|           |    200    |
  |           |<----------|
13|           |    487    |
  |           |<----------|
14|           |    ACK    |
  |           |---------->|
15|    487    |           |
  |<----------|           |
16|    ACK    |           |
  |---------->|           |
</code></pre>
<p dir="auto">One of our customers complains that TO-TAGs in 183 (packet 8) and 200(packet 11) are not equal(their devices see 3 to-tag during 1 dialog). I found in RFC 3261that it's ok(<a href="https://datatracker.ietf.org/doc/html/rfc3261#section-16.10" rel="nofollow">https://datatracker.ietf.org/doc/html/rfc3261#section-16.10</a>).<br>
183 is forwarded from UAS(UAS sets to-tag) and 200 is generated by Kamailio. This is why to-tags in 183 and 200 are not equal.</p>
<p dir="auto">Is it possible to use to-tag from master branch(ofc if we have received a reply from UAS and we have this tag)?</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />Reply to this email directly, <a href="https://github.com/kamailio/kamailio/issues/3021">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABO7UZLCTM7MR4Z2SN7JBD3U2F2MVANCNFSM5N3P4IRQ">unsubscribe</a>.<br />Triage notifications on the go with GitHub Mobile for <a href="https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675">iOS</a> or <a href="https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub">Android</a>.
<br />You are receiving this because you are subscribed to this thread.<img src="https://github.com/notifications/beacon/ABO7UZNBZ7AVN22KDJPF5Q3U2F2MVA5CNFSM5N3P4IR2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4QZXQY6Q.gif" height="1" width="1" alt="" /><span style="color: transparent; font-size: 0; display: none; visibility: hidden; overflow: hidden; opacity: 0; width: 0; height: 0; max-width: 0; max-height: 0; mso-hide: all">Message ID: <span><kamailio/kamailio/issues/3021</span><span>@</span><span>github</span><span>.</span><span>com></span></span></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/kamailio/kamailio/issues/3021",
"url": "https://github.com/kamailio/kamailio/issues/3021",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>