<div dir="ltr">I had some termination issues with random cell phone carriers, some where 608d other where 200d but really the phone didn't ring. (a rate of 60% of calls was like this)<div><br></div><div>After collecting a few samples, and complaining to my upstream carrier, they had been improved immediately)</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 11, 2023 at 2:12 PM Calvin E. via VoiceOps <<a href="mailto:voiceops@voiceops.org">voiceops@voiceops.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Check the 608 responses for a Call-Info header. If present, it should contain a point of contact for redress.<div><br><div><a href="https://www.rfc-editor.org/rfc/rfc8688.html#section-3.1-3" target="_blank">https://www.rfc-editor.org/rfc/rfc8688.html#section-3.1-3</a><br></div><div>"<span style="font-family:"Noto Sans",Arial,Helvetica,sans-serif;font-size:14px">If there is a Call-Info header field, it</span><span style="font-family:"Noto Sans",Arial,Helvetica,sans-serif;font-size:14px"> </span><span style="font-family:"Noto Sans",Arial,Helvetica,sans-serif;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-caps:small-caps;font-weight:bold;font-size:0.9em">MUST</span><span style="font-family:"Noto Sans",Arial,Helvetica,sans-serif;font-size:14px"> </span><span style="font-family:"Noto Sans",Arial,Helvetica,sans-serif;font-size:14px">have the "purpose" parameter of "jwscard". The value of the Call-Info header field</span><span style="font-family:"Noto Sans",Arial,Helvetica,sans-serif;font-size:14px"> </span><span style="font-family:"Noto Sans",Arial,Helvetica,sans-serif;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-caps:small-caps;font-weight:bold;font-size:0.9em">MUST</span><span style="font-family:"Noto Sans",Arial,Helvetica,sans-serif;font-size:14px"> </span><span style="font-family:"Noto Sans",Arial,Helvetica,sans-serif;font-size:14px">refer to a valid JSON Web Signature (JWS)</span><span style="font-family:"Noto Sans",Arial,Helvetica,sans-serif;font-size:14px"> </span><span style="font-family:"Noto Sans",Arial,Helvetica,sans-serif;font-size:14px">[<a href="https://www.rfc-editor.org/rfc/rfc8688.html#RFC7515" style="text-decoration-line:none;color:rgb(34,34,238);background-color:rgb(242,242,242)" target="_blank">RFC7515</a>]</span><span style="font-family:"Noto Sans",Arial,Helvetica,sans-serif;font-size:14px"> </span><span style="font-family:"Noto Sans",Arial,Helvetica,sans-serif;font-size:14px">encoding of a</span><span style="font-family:"Noto Sans",Arial,Helvetica,sans-serif;font-size:14px"> </span><span style="font-family:"Noto Sans",Arial,Helvetica,sans-serif;font-size:14px"><a href="https://www.rfc-editor.org/rfc/rfc8688.html#RFC7095" style="text-decoration-line:none;color:rgb(34,34,238)" target="_blank">jCard</a> [<a href="https://www.rfc-editor.org/rfc/rfc8688.html#RFC7095" style="text-decoration-line:none;color:rgb(34,34,238)" target="_blank">RFC7095</a>]</span><span style="font-family:"Noto Sans",Arial,Helvetica,sans-serif;font-size:14px"> </span><span style="font-family:"Noto Sans",Arial,Helvetica,sans-serif;font-size:14px">object. The following section describes the construction of the JWS.</span><a href="https://www.rfc-editor.org/rfc/rfc8688.html#section-3.1-3" style="font-family:"Noto Sans",Arial,Helvetica,sans-serif;font-size:14px;text-decoration-line:none;color:rgb(102,102,102)" target="_blank">¶</a></div></div><div><br></div><div>You can also look into registering your calling numbers at sites like the two below. It may also help to cover the basics like CNAM and a Directory Listing to improve the "legitimacy" of the numbers.</div><div><br></div><div><a href="https://registeredcaller.com/" target="_blank">https://registeredcaller.com/</a></div><div><br></div><div><a href="https://www.freecallerregistry.com/fcr/" target="_blank">https://www.freecallerregistry.com/fcr/</a></div><div><br></div><div>Some analytics will assume the worst until proven otherwise. You could attempt a low volume, low velocity, high ASR test pattern on an affected carrier to ensure your calling numbers have some positive reputation established before any mass calling.</div><div> </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 11, 2023 at 7:08 AM Dovid Bender via VoiceOps <<a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi All,<br><div><br></div><div>We are a small ITSP and every so often we have issues with calls that go to T-Mobile. We sign all our calls with our cert. Lately we have been getting 404's, 608's etc through 382, Telnyx and SIPRoutes. Bandwidth has been worse than the rest as they don't outright reject calls but they send a 100 trying and leave us hanging for 30 seconds. Peerless and one other carrier are completing the calls. Anyone know what makes T-Moble special that so many carriers will just 404 calls to their network?</div><div><br>TIA.</div><div><br></div><div>Dovid</div><div><br></div></div>
_______________________________________________<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>
</blockquote></div>
_______________________________________________<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>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><b>Pinchas S. Neiman</b></div><div>Software Engineer At ESEQ Technology Corp.</div><div>845.213.1229 #2</div><img width="200" height="68" src="https://ci3.googleusercontent.com/mail-sig/AIorK4z1Lx063u893FlkIV1C3aJbVPjgKnaA2Xu8q_iPdyFOnK_JX05usgghpAIwmPqB-1t-3fdaShNHoCPf7fFwa1twYZt-xjsBZheqmsCQrg"><br></div></div></div></div></div></div></div></div></div></div></div></div></div></div>