<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (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;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0cm;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
.MsoChpDefault
        {mso-style-type:export-only;}
@page Section1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
        {page:Section1;}
-->
</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-GB link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>Hi there,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I have a dial string similar to below, which dials two SIP
URIs, one after another using leg_delay_start of 0 and 5, and leg_timeout of 10
and 10 to stagger the calling pattern. Both SIP URI’s have a
group_confirm_file associated with them, where pressing a digit will cause the
call to be connected!<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>{group_confirm_key=exec,group_confirm_file='javascript GroupConfirm.js’,ignore_early_media=true,
,group_confirm_cancel_timeout=true}[ leg_delay_start=0,leg_timeout=10,rmvLegConfirm=true]<a
href="mailto:sofia/internal/12005@blah.com;fs_path=sip:172.30.98.31,%5bleg_delay_start=5,leg_timeout=10,rmvLegConfirm=true%5dsofia/internal/12003blah.com;fs_path=sip:172.30.98.31">sofia/internal/12005@blah.com;fs_path=sip:172.30.98.31,[leg_delay_start=5,leg_timeout=10,rmvLegConfirm=true]sofia/internal/12003blah.com;fs_path=sip:172.30.98.31</a>)<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I have set group_confirm_cancel_timeout=true to ensure that
the call doesn’t drop due to timeout when answered and in the confirm
stage.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I have two scenarios relating to timeout problems; both of
which I’m sure are the same!<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><b><u>Scenario 1<o:p></o:p></u></b></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>When a call is made, we wait for 7 seconds until both
extensions ring, then pick up the call on first extension. FS plays the group
confirm message and doesn’t timeout as expected. However the second phone
then continues to ring beyond its configured leg_timeout? Question: does
group_confirm_cancel_timeout cancel all leg timeouts as soon as one extension
answers? If so, is there a way to make it only apply to the leg that answered,
and allow other legs to carry on with their existing timeouts.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><b><u>Scenario 2<o:p></o:p></u></b></p>
<p class=MsoNormal><b><u><o:p><span style='text-decoration:none'> </span></o:p></u></b></p>
<p class=MsoNormal>When a call is made, we allow extension 1 to start ringing
and pick it up. It plays the group confirm message and doesn’t timeout as
expected. The second extension never starts ringing however, whilst the
group_confirm phase is active. This means that if the first extension is
rejected in the group_confirm phase, the second extension never gets going! Again,
is there a way to make the group_confirm_cancel_timeout apply to the single leg
and not all legs in the originate!<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Any ideas please...<o:p></o:p></p>
<p class=MsoNormal>Neil<o:p></o:p></p>
<p class=MsoNormal><b><u><o:p><span style='text-decoration:none'> </span></o:p></u></b></p>
</div>
</body>
</html>