<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style>
<!--
@font-face
{font-family:Wingdings}
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:link, span.MsoHyperlink
{color:#0563C1;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:#954F72;
text-decoration:underline}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
span.E-MailFormatvorlage17
{font-family:"Calibri",sans-serif;
color:windowtext}
.MsoChpDefault
{font-family:"Calibri",sans-serif}
@page WordSection1
{margin:70.85pt 70.85pt 2.0cm 70.85pt}
ol
{margin-bottom:0cm}
ul
{margin-bottom:0cm}
-->
</style><style type="text/css" id="owaParaStyle"></style>
</head>
<body lang="DE-AT" link="#0563C1" vlink="#954F72" fpstyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 13px;">
<div style="">Hi,</div>
<div style=""><br>
</div>
<div style="">without further looking (not currently with access to our lab)</div>
<div style="">you can try to set "force_inbound_calls_to_peer" to true for this subscriber. I did not have time to do</div>
<div style="">proper testing with the porting-feature yet but in the next few weeks I hope to find a window.</div>
<div style="">It would be interesting to see if the header gets manipulated properly if you configure the</div>
<div style="">LNP-settings for this number. (Did you do that?)</div>
<div style=""><br>
</div>
<div>
<div style="font-family:Tahoma; font-size:13px">kind regards,<br>
<br>
Julian Seifert<br>
<div style="font-family:Tahoma; font-size:13px"></div>
</div>
</div>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div id="divRpF554511" style="direction: ltr;"><font face="Tahoma" size="2" color="#000000"><b>Von:</b> Spce-user [spce-user-bounces@lists.sipwise.com]" im Auftrag von "Matthias Hohl [matthias.hohl@telematica.at]<br>
<b>Gesendet:</b> Freitag, 1. Juli 2016 16:24<br>
<b>An:</b> spce-user@lists.sipwise.com<br>
<b>Betreff:</b> [Spce-user] Best practice handling with ported numbers in 4.4.1<br>
</font><br>
</div>
<div></div>
<div>
<div class="WordSection1">
<p class="MsoNormal">Hello,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span lang="EN-US">today i tried something with a subscriber which is currently not in use cause the number is ported.</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">I want the ported number is not anymore a local call.</span></p>
<p class="MsoNormal"><span lang="EN-US">I want that if a subscriber calls another subscriber that still exists but which number is ported away to another carrier, that the call goes out to our peering partner.</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">How can I solve this right now?</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">I tried to set the subscriber to lock level “ported” but I always get the same message “The number you are trying to reach is currently not available. Please try again later.”</span></p>
<p class="MsoNormal"><span lang="EN-US">Also if I edit the subscriber and delete the E164 number the I can hear the same message (maybe a bug? Cause if totally delete the e164 number, the subscriber should has no number and should not be reachable or not?)</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">But anyway, what is the right behavior to handle with ported numbers?</span></p>
<p class="MsoNormal"><span lang="EN-US">At the moment it looks like that only deleting the whole subscriber will solve my problem.</span></p>
<p class="MsoNormal"><span lang="EN-US">But then I have the problem that I have no “warning” that I create another subscriber with a number that was already given to another subscriber that have ported away his number.</span></p>
<p class="MsoNormal"><span lang="EN-US">So it would be good if the subscriber could be active, but if I set the lock level to “ported” to call would be going out to the peering, instead of checking if the Callee is local.</span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
<p class="MsoNormal"><span lang="EN-US">Thank you for your informations.</span></p>
</div>
</div>
</div>
</div>
</body>
</html>