<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=iso-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML - förformaterad Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Ballongtext Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
color:black;}
span.HTML-frformateradChar
{mso-style-name:"HTML - förformaterad Char";
mso-style-priority:99;
mso-style-link:"HTML - förformaterad";
font-family:Consolas;
color:black;}
span.st
{mso-style-name:st;}
p.HTML-fouml, li.HTML-fouml, div.HTML-fouml
{mso-style-name:"HTML - fö\,rformaterad";
mso-style-link:"HTML - fö1\,rformaterad Char1";
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
span.HTML-fouml1
{mso-style-name:"HTML - fö1\,rformaterad Char1";
mso-style-priority:99;
mso-style-link:"HTML - fö\,rformaterad";
font-family:Consolas;
color:black;}
span.E-postmall22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;
font-weight:normal;
font-style:normal;}
span.BallongtextChar
{mso-style-name:"Ballongtext Char";
mso-style-priority:99;
mso-style-link:Ballongtext;
font-family:"Tahoma","sans-serif";
color:black;}
span.E-postmall26
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;
font-weight:normal;
font-style:normal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
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 bgcolor="white" lang="SV" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I’m not sure how Polycom does their transfers, but usually these are the differences;<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">When doing blind transfer, the phone has one call leg, and then sends a SIP REFER (to FreeSWITCH in this case), telling it to take that call and
blindly transfer it to another extension. In this case the original CallerID should be transferred correctly.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">When doing supervised/consultation transfer, the phone will start by making a new call to the extension you want to transfer to. In this state
the call will be from the phone doing the transfer, to the phone that is the destination (and the caller-id on the destination phone will be the transferers phone). When the destination phone picks up, the transferer says something like “Ok, here is a call
for you”, and then completes the transfer. Now it will probably send a REFER with replaces tags to FreeSWITCH, telling it to drop the two call legs to the transferer, and instead directly bridge the incoming external call to the transfer destination (these
two legs already exist, so FS will just start bridging the RTP for these channels). As soon as this has happened, FS will send a display update, since the CallerID actually changed now, from the transferers phone to the original external call.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">As I said, I’m not sure if this is how Polycom does their transfers, but the basic difference between a blind and supervised transfer is as described
above. So in this case, if you want to do a supervised transfer, and let the transfer target get the original callerID directly (before the call are actually transferred), I think you will need to check out the entire SIP call flow, and then take appropiate
actions (either change config in FS, and/or change config on the phones).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">However, most people expect it to work as it does by default...<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">/Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">Från:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"> freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org]
<b>För </b>ghallab<br>
<b>Skickat:</b> den 21 maj 2012 14:18<br>
<b>Till:</b> FreeSWITCH Users Help<br>
<b>Ämne:</b> Re: [Freeswitch-users] ignore_display_updates meaning an polycom problem (urgent please)<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Could you tell me what is the impact of each one (<span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> transferred using blind or supervised transfer)?</span><br>
On 05/21/2012 09:22 AM, Peter Olsson wrote: <o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I guess it mostly depends on the Polycom device. For instance, it’s a big difference if the call is transferred using blind or supervised transfer.
You will probably need to collect the SIP traffic, and check what actually happens when doing this scenario.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Mvh</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Peter Olsson</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">Från:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">
<a href="mailto:freeswitch-users-bounces@lists.freeswitch.org">freeswitch-users-bounces@lists.freeswitch.org</a> [<a href="mailto:freeswitch-users-bounces@lists.freeswitch.org">mailto:freeswitch-users-bounces@lists.freeswitch.org</a>]
<b>För </b>ghallab<br>
<b>Skickat:</b> den 21 maj 2012 12:07<br>
<b>Till:</b> FreeSWITCH Users Help<br>
<b>Ämne:</b> [Freeswitch-users] ignore_display_updates meaning an polycom problem (urgent please)</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Hi guys,<o:p></o:p></p>
<p class="MsoNormal">Can you explain me what well happen if I set the variable "ignore_display_updates=true" before I make bridge action and what will happen if I set it to false? because I have a problem with FS and Polycom 550: when A call from outside of
the FS network to B which is inside, then B answer and transfer the call to C which is inside also, when C's phone is ringing he see B's caller ID and when he answer, he see A's caller ID. Me I want that he see always caller ID of A. I tried to set "ignore_display_updates=true"
in this case B see just C's caller ID when his is ringing and when he answer. There is any way to fix this issue? I am thinking about to set
<em>"effective_caller_id_number={$origination_caller_id_number}" but I am not sure if this will work.
</em><o:p></o:p></p>
<pre> <o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<p class="MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
<pre>_________________________________________________________________________<o:p></o:p></pre>
<pre>Professional FreeSWITCH Consulting Services:<o:p></o:p></pre>
<pre><a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><o:p></o:p></pre>
<pre><a href="http://www.freeswitchsolutions.com">http://www.freeswitchsolutions.com</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>FreeSWITCH-powered IP PBX: The CudaTel Communication Server<o:p></o:p></pre>
<pre><a href="http://www.cudatel.com">http://www.cudatel.com</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Official FreeSWITCH Sites<o:p></o:p></pre>
<pre><a href="http://www.freeswitch.org">http://www.freeswitch.org</a><o:p></o:p></pre>
<pre><a href="http://wiki.freeswitch.org">http://wiki.freeswitch.org</a><o:p></o:p></pre>
<pre><a href="http://www.cluecon.com">http://www.cluecon.com</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Join Us At ClueCon - Aug 7-9, 2012<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>FreeSWITCH-users mailing list<o:p></o:p></pre>
<pre><a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><o:p></o:p></pre>
<pre><a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><o:p></o:p></pre>
<pre>UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><o:p></o:p></pre>
<pre><a href="http://www.freeswitch.org">http://www.freeswitch.org</a><o:p></o:p></pre>
<p class="MsoNormal"><br>
!DSPAM:4fba232f32763870889139! <o:p></o:p></p>
</div>
</body>
</html>