<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)">
<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:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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 lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks, but that doesn’t seem to fit the issue of what’s going on, from what I can tell.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Next? <span style="font-family:"Segoe UI Emoji",sans-serif">
😊</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> mgraves mstvp.com <mgraves@mstvp.com> <br>
<b>Sent:</b> Tuesday, August 17, 2021 1:32 PM<br>
<b>To:</b> Mark Wiles <mwiles@akabis.com>; VoiceOps@voiceops.org<br>
<b>Subject:</b> RE: Strange Inbound Verizon Issues<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a href="https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.androidauthority.com%2fverizon-outage-1014222%2f&c=E,1,CAj0wcxcmJ0TqOJM41axWeUQ9xjNDGe4fbHliUA6yGT56_f8py-COPOOoQGNrlU3cgxCyhCTWopct5hBou_8QRBRFar9JGfjKgmAAYN2&typo=1">https://www.androidauthority.com/verizon-outage-1014222/</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Original article: August 17, 2021 (12:36 AM ET): If you’re a <a href="https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.androidauthority.com%2fbest-verizon-deals-835801%2f&c=E,1,s1-ryDX2oI7LYQKwnVPKQwhgQNvHI5GLvaquMnETwlKn98SpACJ5csEuaoUXCXlMgTrUBJSUbIglztYWKpeT9GqYmX2QDbIJzWmxe6AqtQ,,&typo=1">Verizon</a> customer
and happen to be experiencing issues, you’re not alone. Verizon is not working in many parts of the US.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Michael Graves<o:p></o:p></p>
<p class="MsoNormal"><a href="mailto:mgraves@mstvp.com"><span style="color:windowtext">mgraves@mstvp.com</span></a><o:p></o:p></p>
<p class="MsoNormal">o: (713) 861-4005<o:p></o:p></p>
<p class="MsoNormal">c: (713) 201-1262<o:p></o:p></p>
<p class="MsoNormal"><a href="sip:mgraves@mjg.onsip.com">sip:mgraves@mjg.onsip.com</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> VoiceOps <<a href="mailto:voiceops-bounces@voiceops.org">voiceops-bounces@voiceops.org</a>>
<b>On Behalf Of </b>Mark Wiles<br>
<b>Sent:</b> Tuesday, August 17, 2021 11:55 AM<br>
<b>To:</b> <a href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a><br>
<b>Subject:</b> [VoiceOps] Strange Inbound Verizon Issues<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We are seeing an issue involving Verizon… wanted to see if anyone had thoughts… or if Verizon’s monitoring here…<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The problem seems to be happening only in FL, but I could be wrong about that.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">A Verizon customer calls a TN we have via Inteliquent. They get the following intercept message: “Welcome to Verizon wireless. Your call cannot be completed.”<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Here’s where it gets interesting… we have a technician standing next to the customer with the Verizon cell that’s failing.<o:p></o:p></p>
<p class="MsoNormal">The technician calls, using his Verizon phone, and it always completes. The customer, standing less than six feet away always fails… again, both calling the same terminating number.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We can only come up with one difference… when we get the failures, the Verizon phones being used are all personal accounts… and the ones that complete are on Verizon business accounts.<o:p></o:p></p>
<p class="MsoNormal">I’m not saying that’s the cause of the issue; but, it’s the only common denominator we can find.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We tried to open a ticket with Verizon, as the calling party (personal phone), and Verizon wouldn’t open a ticket. (what the heck???)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Has anyone seen or heard of such a thing? <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Mark<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Segoe UI",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>