<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">Carlos;<br><br>You can actually disable the function on the iPhone, which is what the VZN Engineer did for our testing. I know for sure that all (4) different model Androids had VoLTE enabled. They were Motorola, Sony and 2 different Samsung<br><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">We send calls out to several carriers and each one has been involved in the issue. I'm not ready to point at carriers yet, since the evidence is overwhelmingly pointing at iOS/iPhone but.... I don't want say that IS the root cause either. The bulk of these calls are traveling the Impact network via SIP. However, it is possible 2 or 3 hops later they all ride the same carrier that is making it seem like all the carriers' networks are doing it.<br><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">As you say, VoLTE could be acting totally different than any other system out there. I just know what the Engineer at VZN told us on the phone about their network.<br><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">I've been doing this for over 30 years... nothing surprises me now.<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 15, 2016 at 3:45 PM, Carlos Alvarez <span dir="ltr"><<a href="mailto:caalvarez@gmail.com" target="_blank">caalvarez@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">Is there a way to know if a handset is using VoLTE? IE, so we could specifically test it? Can you be sure the Androids were VoLTE capable?<div><br></div><div>The VoLTE network could be handling things completely differently and I don't think it's safe to assume that it's not a carrier to carrier issue. I would still recommend trying calls with any other carrier if at all possible. And if you'd like, I can try a call from our Asterisk via Onvoy to one of the problem phones and see what happens. I don't think it's safe to eliminate ANY item, including your switch. Like I said in the private e-mail, we're fighting a signaling issue right now that ONLY happens if it's from our primary server, to Onvoy, to certain other carriers, and it's a transfer. Eliminate any one and the problem goes away.</div><div><div class="h5"><div><br></div><div><br><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 15, 2016 at 2:33 PM, 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><span style="font-family:tahoma,sans-serif">Hey Pete;<br><br></span></div><div><span style="font-family:tahoma,sans-serif">Thanks for the chime-in. That must have been a fun one to chase as well.<br><br></span></div><div><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.<br></span><ol><li><span style="font-family:tahoma,sans-serif">We have only gotten complaints related to users of iPhones</span></li><li><span style="font-family:tahoma,sans-serif">I have made test calls to Android devices and have not had the problem occur<br></span></li><ol><li><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></li><li><span style="font-family:tahoma,sans-serif"><br></span></li><li><span style="font-family:tahoma,sans-serif">However, I have also made calls to Verizon iPhones that did not reproduce the problem<br></span></li></ol><li><span style="font-family:tahoma,sans-serif">We have troubles reported to us relating to both Verizon and AT&T wireless end users</span></li><ol><li><span style="font-family:tahoma,sans-serif">Have all been end users with iPhones<br></span></li></ol><li><span style="font-family:tahoma,sans-serif">As stated earlier, when the VZN Engineer deactivated VoLTE on the iPhone, the information displayed correctly</span></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.<br></span></p><p><span style="font-family:tahoma,sans-serif">It's definitely a strange one.</span></p><p><span style="font-family:tahoma,sans-serif"><br></span></p><p><span style="font-family:tahoma,sans-serif">Thanks;</span></p><p><span style="font-family:tahoma,sans-serif">Kidd<br></span></p></div><div class="gmail_extra"><div><div><span style="font-family:tahoma,sans-serif"><br></span><div class="gmail_quote"><span style="font-family:tahoma,sans-serif">On Wed, Jun 15, 2016 at 2:50 PM, Pete Mundy <span dir="ltr"><<a href="mailto:pete@fiberphone.co.nz" target="_blank">pete@fiberphone.co.nz</a>></span> wrote:<br></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><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></span>
<span style="font-family:tahoma,sans-serif"><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></span>
<span style="font-family:tahoma,sans-serif"><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>
<span style="font-family:tahoma,sans-serif"><span><font color="#888888"><br>
Pete<br>
</font></span><br>
Ps, yes I also giggled at the Comic Sans on the first posting too ;)<br></span>
<span style="font-family:tahoma,sans-serif"><span><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.<br>
<br>
</span></span><div><div><span style="font-family:tahoma,sans-serif">______________________________</span><span style="font-family:tahoma,sans-serif">_________________<br>
VoiceOps mailing list<br></span>
<span style="font-family:tahoma,sans-serif"><a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br></span>
<span style="font-family:tahoma,sans-serif"><a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br></span>
</div></div></blockquote></div></div></div><span style="font-family:tahoma,sans-serif"><br><br clear="all"><br>-- <br></span><span><div data-smartmail="gmail_signature"><div dir="ltr"><span style="font-family:tahoma,sans-serif">Kidd Filby<br><a href="tel:661.557.5640" value="+16615575640" target="_blank">661.557.5640</a> (C)<br><a href="http://www.linkedin.com/in/kiddfilby" title="View public profile" name="m_4616145525571332047_m_-2598205205850674263_UNIQUE_ID_SafeHtmlFilter_SafeHtmlFilter_webProfileURL" target="_blank">http://www.linkedin.com/in/kiddfilby</a><br></span></div></div>
</span></div></div>
<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" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
<br></blockquote></div><br></div></div></div></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><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><span style="font-family:tahoma,sans-serif">Kidd Filby<br>661.557.5640 (C)<br><a href="http://www.linkedin.com/in/kiddfilby" title="View public profile" name="UNIQUE_ID_SafeHtmlFilter_SafeHtmlFilter_webProfileURL" target="_blank">http://www.linkedin.com/in/kiddfilby</a></span><br></div></div></div></div>
</div>