<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Thank you Jean<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> asterisk-dev <asterisk-dev-bounces@lists.digium.com>
<b>On Behalf Of </b>Jean Aunis<br>
<b>Sent:</b> Friday, January 8, 2021 8:47 AM<br>
<b>To:</b> asterisk-dev@lists.digium.com<br>
<b>Subject:</b> Re: [asterisk-dev] Looking to input on a feature I would like to write...in depth Transfer (REFER) failure reasons<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Le 08/01/2021 à 15:40, Dan Cropp a écrit :<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Before I submit a feature request and take ownership of it, trying to gather some feedback.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I’m looking to write code for an additional feature in asterisk.<o:p></o:p></p>
<p class="MsoNormal">Currently, when performing a Transfer (REFER), the channel variable TRANSFERSTATUS only reports 3 values: SUCCESS, FAILURE, UNSUPPORTED.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">We have some customers asking for a few additional results: 404 Not Found, 408 Request Timeout, and 486 Busy Here.<o:p></o:p></p>
<p class="MsoNormal">From past experience, these same customers will likely come up with some additional results they think should be returned.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Would it be better to add support where the TRANSFERSTATUS had new values for each of the additional result codes I make asterisk look for?<o:p></o:p></p>
<p class="MsoNormal">Or would it be better to add a new variable, example TRANSFERSTATUSCODE and have it return the SIP error code for the failure notification? Personally, I like this approach because it means not having to add values for each possible sip
error code that anyone would ever look for.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Dan<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
<p>Hello Dan,<o:p></o:p></p>
<p>I would prefer the second approach of using a new variable, otherwise it may break existing dialplan.<o:p></o:p></p>
<p>Regards<o:p></o:p></p>
<p>Jean<o:p></o:p></p>
</div>
</body>
</html>