<p>At the link below, you can go to 19.1.6. It is a very strange ordering giving priority to two parameters that should be first, if present.</p>
<p><a href="https://www.ietf.org/rfc/rfc3261.txt">https://www.ietf.org/rfc/rfc3261.txt</a></p>
<p>19.1.6 Relating SIP URIs and tel URLs<br>
. . . .</p>
<pre><code>   To mitigate this problem, elements constructing telephone-subscriber
   fields to place in the userinfo part of a SIP or SIPS URI SHOULD fold
   any case-insensitive portion of telephone-subscriber to lower case,
   and order the telephone-subscriber parameters lexically by parameter
   name, excepting isdn-subaddress and post-dial, which occur first and
   in that order.  (All components of a tel URL except for future-
   extension parameters are defined to be compared case-insensitive.)
</code></pre>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you commented.<br />Reply to this email directly, <a href="https://github.com/kamailio/kamailio/issues/1173#issuecomment-312666257">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AF36Zd0mmK_ZouHbhrSEffMla-hJ74jUks5sKQBFgaJpZM4OJzVh">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AF36ZUYNusew20ISYEHX9314BNQKgF4Qks5sKQBFgaJpZM4OJzVh.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/1173#issuecomment-312666257"></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":"@doncarr in #1173: At the link below, you can go to 19.1.6. It is a very strange ordering giving priority to two parameters that should be first, if present.\r\n\r\nhttps://www.ietf.org/rfc/rfc3261.txt\r\n\r\n19.1.6 Relating SIP URIs and tel URLs\r\n. . . . \r\n```\r\n   To mitigate this problem, elements constructing telephone-subscriber\r\n   fields to place in the userinfo part of a SIP or SIPS URI SHOULD fold\r\n   any case-insensitive portion of telephone-subscriber to lower case,\r\n   and order the telephone-subscriber parameters lexically by parameter\r\n   name, excepting isdn-subaddress and post-dial, which occur first and\r\n   in that order.  (All components of a tel URL except for future-\r\n   extension parameters are defined to be compared case-insensitive.)\r\n```\r\n"}],"action":{"name":"View Issue","url":"https://github.com/kamailio/kamailio/issues/1173#issuecomment-312666257"}}}</script>