Hi All, 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? TIA. Dovid
Welcome to the wide world of random call blocking. We've been seeing the same issue for some time now due to the magic of "analytics". Emergency notification calls (school closures, weather events, shootings) are especially great when getting blocked due to random systems deciding that they don't like the call patterns or the ANI. You are possibly running into where some of your ANIs have been flagged for no reason at all and that your cert or signed level isn't even being looked at before getting rejected. Of course when your customer tries making the same call on their cell phone (or a different carrier) it works just fine so you're left looking like you don't know what you are doing. Best you can do is open tickets and complain. You can also look at trying to fill out the FCR but I haven't seen that help too much. On Wed, Jan 11, 2023 at 7:08 AM Dovid Bender via VoiceOps < voiceops at voiceops.org> wrote:
Hi All,
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?
TIA.
Dovid
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Check the 608 responses for a Call-Info header. If present, it should contain a point of contact for redress. https://www.rfc-editor.org/rfc/rfc8688.html#section-3.1-3 "If there is a Call-Info header field, it MUST have the "purpose" parameter of "jwscard". The value of the Call-Info header field MUST refer to a valid JSON Web Signature (JWS) [RFC7515 <https://www.rfc-editor.org/rfc/rfc8688.html#RFC7515>] encoding of a jCard <https://www.rfc-editor.org/rfc/rfc8688.html#RFC7095> [RFC7095 <https://www.rfc-editor.org/rfc/rfc8688.html#RFC7095>] object. The following section describes the construction of the JWS.? <https://www.rfc-editor.org/rfc/rfc8688.html#section-3.1-3> 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. https://registeredcaller.com/ https://www.freecallerregistry.com/fcr/ 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. On Wed, Jan 11, 2023 at 7:08 AM Dovid Bender via VoiceOps < voiceops at voiceops.org> wrote:
Hi All,
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?
TIA.
Dovid
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
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) After collecting a few samples, and complaining to my upstream carrier, they had been improved immediately) On Wed, Jan 11, 2023 at 2:12 PM Calvin E. via VoiceOps < voiceops at voiceops.org> wrote:
Check the 608 responses for a Call-Info header. If present, it should contain a point of contact for redress.
https://www.rfc-editor.org/rfc/rfc8688.html#section-3.1-3 "If there is a Call-Info header field, it MUST have the "purpose" parameter of "jwscard". The value of the Call-Info header field MUST refer to a valid JSON Web Signature (JWS) [RFC7515 <https://www.rfc-editor.org/rfc/rfc8688.html#RFC7515>] encoding of a jCard <https://www.rfc-editor.org/rfc/rfc8688.html#RFC7095> [RFC7095 <https://www.rfc-editor.org/rfc/rfc8688.html#RFC7095>] object. The following section describes the construction of the JWS.? <https://www.rfc-editor.org/rfc/rfc8688.html#section-3.1-3>
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.
https://www.freecallerregistry.com/fcr/
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.
On Wed, Jan 11, 2023 at 7:08 AM Dovid Bender via VoiceOps < voiceops at voiceops.org> wrote:
Hi All,
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?
TIA.
Dovid
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
-- *Pinchas S. Neiman* Software Engineer At ESEQ Technology Corp. 845.213.1229 #2
participants (4)
-
calvine＠gmail.com -
dovid＠telecurve.com -
karl＠piratel.com -
neimanpinchas＠gmail.com