<div dir="ltr">Well, I've never even heard of this before, so are you sure it's not related to your upstream carriers, and/or your own systems? Have you tested multiple upstreams (and which have you tried)? We're on Onvoy and calling Verizon phones that should be on VoLTE, no issues. I'm not sure if there's a way to know for sure if one particular phone is on VoLTE.<div><br></div><div>Also, why the hell would you send e-mail in comic sans font?!?</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 15, 2016 at 10:22 AM, Kidd Filby <span dir="ltr"><<a href="mailto:kiddfilby@gmail.com" target="_blank">kiddfilby@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:comic sans ms,sans-serif"><div>
<p class="MsoNormal">Group;</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I have noticed some weird trouble cases, over the
past year, dealing with US originated calls showing up on a cell phone
as an international call, using the first 2-digits as a country code.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">On one incident, we worked with Verizon, to really
nail down the culprit. Their engineer was very interested in finding
the root cause and he spent a lot of time with us (as well as our
carriers and our customer) trying to figure out what was causing this to
occur. He determined, in their network anyway, it was how they were
treating call information when he activated the VoLTE service. If he
turned off the service, on the same phone, the caller ID information
would be correct. When he activated the VoLTE, the information was
incorrect and said it was an international call and provided the country
it thought the call originated from. He said there is nothing he can
currently do about it, other than turning off VoLTE… and we all know
that isn’t going to happen. <br></p><p class="MsoNormal"><br></p><p class="MsoNormal">All of the complaints, we have had, have been
to iPhones.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><i>There is also another cause for this behavior
that has to do with a CNAM-Like AP, some people had
activated, and that had us chasing our tails for a while as well.</i></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">What I am wondering is, how many other folks out there are running into these scenarios and….</p>
<p><span>1.<span style="font:7pt "Times New Roman""> </span></span>What are your telling your customers?</p>
<p><span>2.<span style="font:7pt "Times New Roman""> </span></span>What are your carriers telling you.</p>
<p><span>3.<span style="font:7pt "Times New Roman""> </span></span>What have you determined the issue was?</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Also, if what we have been being told is incorrect, then I’d like to know that too.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Several of our customers are negatively affected by this and we really need to figure out a solution for the industry.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thanks;</p>
<p class="MsoNormal">Kidd</p>
</div></div>
</div>
<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" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
<br></blockquote></div><br></div>