<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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:212234548;
mso-list-template-ids:1935025404;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">For what it’s worth, I have an iPhone 6 Plus running IOS 9.2.1 on ATT. I’ve recently been experiencing this “problem” on received calls.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I haven’t had a chance to investigate it, just know that it started occurring on 6/6/2016, and it’s only when receiving calls from a specific calling party, and
it doesn’t happen all the time.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><img width="308" height="456" id="Picture_x0020_1" src="cid:image001.png@01D1C748.8FBD36D0"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> VoiceOps [mailto:voiceops-bounces@voiceops.org]
<b>On Behalf Of </b>Jared Geiger<br>
<b>Sent:</b> Wednesday, June 15, 2016 6:49 PM<br>
<b>To:</b> Kidd Filby <kiddfilby@gmail.com><br>
<b>Cc:</b> <voiceops@voiceops.org> <voiceops@voiceops.org><br>
<b>Subject:</b> Re: [VoiceOps] Appearance of an International call<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">I'm thinking since the VoLTE call is going through a GSM type Verizon switch which is separate from their 1X CDMA voice network. The VoLTE switch would be e164 format (+1) all the way whereas the legacy switch is probably more catered to
act like a US PSTN switch (10 Digit).<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I don't think this is 100% related but could be: When we setup our trunks to Verizon Business, we had to choose between sending our ANI in e164 or in 10 digit US form. Maybe a carrier along the path isn't transforming the ANI correctly
to match their trunk with Verizon. Granted I don't know how interconnection with Verizon wireless looks like at all so it could be completely different than VZB. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Wed, Jun 15, 2016 at 3:11 PM, Kidd Filby <<a href="mailto:kiddfilby@gmail.com" target="_blank">kiddfilby@gmail.com</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Tahoma",sans-serif">Jared;<br>
<br>
We did not try that specific call scenario. What I can tell you is that I get calls from people all the time, to my VZN Motorola phone, sometimes they show up with a + and other times they don't. I'm talking about the same calling number. So, I think it
depends on what tower they are hitting or something along those lines as to what the translations are in the routing.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Tahoma",sans-serif">What are you thoughts about the +1?? Are you thinking that is a info bit that does something in the VZN network or w/in VoLTE?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif">Thanks;<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif">Kidd<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Wed, Jun 15, 2016 at 3:54 PM, Jared Geiger <<a href="mailto:jared@compuwizz.net" target="_blank">jared@compuwizz.net</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class="MsoNormal">What happens if you send the call with a +1 in the beginning of the ANI? Does the VoLTE phone correctly show or does Verizon reject the call?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Wed, Jun 15, 2016 at 2:33 PM, Kidd Filby <<a href="mailto:kiddfilby@gmail.com" target="_blank">kiddfilby@gmail.com</a>> wrote:<o:p></o:p></p>
<div>
<div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Tahoma",sans-serif">Hey Pete;</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Tahoma",sans-serif">Thanks for the chime-in. That must have been a fun one to chase as well.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif">Well, I cannot say... for certain, it is an iOS problem or directly related to the iPhone. Here is what I know for sure, from testing.</span><o:p></o:p></p>
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-family:"Tahoma",sans-serif">We have only gotten complaints related to users of iPhones</span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-family:"Tahoma",sans-serif">I have made test calls to Android devices and have not had the problem occur</span><o:p></o:p></li></ol>
<ol start="2" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
<span style="font-family:"Tahoma",sans-serif">We have made numerous test calls to (4) different Android models of Verizon phones w/o any issue</span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
<o:p> </o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
<span style="font-family:"Tahoma",sans-serif">However, I have also made calls to Verizon iPhones that did not reproduce the problem</span><o:p></o:p></li></ol>
</ol>
<ol start="3" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-family:"Tahoma",sans-serif">We have troubles reported to us relating to both Verizon and AT&T wireless end users</span><o:p></o:p></li></ol>
<ol start="3" type="1">
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
<span style="font-family:"Tahoma",sans-serif">Have all been end users with iPhones</span><o:p></o:p></li></ol>
</ol>
<ol start="4" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-family:"Tahoma",sans-serif">As stated earlier, when the VZN Engineer deactivated VoLTE on the iPhone, the information displayed correctly</span><o:p></o:p></li></ol>
<p><span style="font-family:"Tahoma",sans-serif">The reason why its not as wide spread, I think, is that people mostly call people they know and the contact list on their cell phone overrides the presentation and a lot more calls are wireless to wireless today
(even on the same network) that were landline related in the past.</span><o:p></o:p></p>
<p><span style="font-family:"Tahoma",sans-serif">It's definitely a strange one.</span><o:p></o:p></p>
<p><o:p> </o:p></p>
<p><span style="font-family:"Tahoma",sans-serif">Thanks;</span><o:p></o:p></p>
<p><span style="font-family:"Tahoma",sans-serif">Kidd</span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif">On Wed, Jun 15, 2016 at 2:50 PM, Pete Mundy <<a href="mailto:pete@fiberphone.co.nz" target="_blank">pete@fiberphone.co.nz</a>> wrote:</span><o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Tahoma",sans-serif"><br>
Do you think this is an iPhone-specific issue? Ie a fault in iOS and the way it's dealing with decoding the caller ID?<br>
<br>
We saw similar issues with txt messages from other mobile users inside our country (New Zealand) way back when the iPhone first hit the market. Basically txt messages would be shown as coming from the full number including country code prefix (+64) and not
matched against the number already in the contacts list. Users would then add the new number to the existing contact, then when they tried to txt or call the number back the carrier would refuse the transmission. It all came right once Apple cottoned on to
the problem and a fix was included in an iOS update (although it took like 2 months for that to occur, meanwhile pretty much everyone with an iPhone in NZ experienced the hassle of it).<br>
<br>
I just wonder if it might be worth testing the same scenario from an Android phone to see if it works. That may help discount the carriers and upstreams as being part of the equation and give you more credence when trying to escalate the issue to Apple (and
good luck with that too!).<br>
<span style="color:#888888"><br>
Pete<br>
</span><br>
Ps, yes I also giggled at the Comic Sans on the first posting too ;)<br>
<br>
<br>
> On 16/06/2016, at 6:54 am, Carlos Alvarez <<a href="mailto:caalvarez@gmail.com" target="_blank">caalvarez@gmail.com</a>> wrote:<br>
><br>
> That sort of conversation was the intent of my original message. We have seen odd things happen from one carrier to another when we don't send the whole presentation. The carriers will accept a 10 digit caller ID but then something strange will happen at
random. So that's just one of many things that could be going on.<br>
><br>
> Sent from my iPhone<br>
><br>
>> On Jun 15, 2016, at 10:57 AM, Alex Balashov <<a href="mailto:abalashov@evaristesys.com" target="_blank">abalashov@evaristesys.com</a>> wrote:<br>
>><br>
>> Comic sans isn't a fashion accessory in my part of town.<br>
>><br>
>> I figure this is an issue of presentation and locality setting transmission. Don't GSM/3GPP and LTE require all numbers to be internally represented as fully-qualified E.164 anyhow? What gives a number "local" presentation is a setting on the phone that
says "I'm within this country code", and I imagine that whether this is honoured can be modulated via some calling number presentation setting in the signalling message.</span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif">_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a></span><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
</div>
</div>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif"><br>
<br clear="all">
<br>
-- </span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif">Kidd Filby<br>
<a href="tel:661.557.5640" target="_blank">661.557.5640</a> (C)<br>
<a name="m_1479874125199248738_m_3277957576839233"></a><a href="http://www.linkedin.com/in/kiddfilby" target="_blank" title="View public profile">http://www.linkedin.com/in/kiddfilby</a></span><o:p></o:p></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<br>
-- <o:p></o:p></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Tahoma",sans-serif">Kidd Filby<br>
<a href="tel:661.557.5640" target="_blank">661.557.5640</a> (C)<br>
<a name="m_1479874125199248738_UNIQUE_ID_SafeHtml"></a><a href="http://www.linkedin.com/in/kiddfilby" target="_blank" title="View public profile">http://www.linkedin.com/in/kiddfilby</a></span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>