<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.mohali-dispatch-cause-for-service-number" target="https://datatracker.ietf.org/doc/html/draft-mohali-dispatch-cause-for-service-number-14">
   <front>
      <title>SIP &quot;cause&quot; URI Parameter for Service Number Translation</title>
      <author initials="M." surname="Mohali" fullname="Marianne Mohali">
         <organization>Orange</organization>
      </author>
      <author initials="M." surname="Barnes" fullname="Mary Barnes">
         </author>
      <date month="January" day="30" year="2017" />
      <abstract>
	 <t>RFC 4458 (regarding SIP URIs for applications) defines a &quot;cause&quot; URI parameter, which may appear in the Request-URI of a SIP request, that is used to indicate a reason why the request arrived to the User Agent Server (UAS) receiving the message.  This document updates RFC 4458 by creating a new predefined value for the &quot;cause&quot; URI parameter to cover service number translation for cases of retargeting due to specific service action leading to the translation of a called service access number.  This document also provides guidance, which was missing in RFC 4458, for using the &quot;cause&quot; URI parameter within the History-Info header field, since this use is mandatory in some IP networks&#x27; implementations.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-mohali-dispatch-cause-for-service-number-14" />
   
</reference>
