this post was submitted on 08 Nov 2023
1 points (100.0% liked)
VoIP
1 readers
1 users here now
Rules
-
Be civil. Disagreements of varying intensities will happen, but particularly vitriolic attacks will be pruned from the discussion.
-
Do not promote or advertise for any business, service or product unless responding to a specific request for recommendations. This includes recommending a user change providers when they have not indicated they are interested in doing so.
-
Do not send private messages to users, or invite users to send you a private message, for the purpose of promoting or advertising a business, service or product.
-
Do not invite, encourage, or seek help with engaging in unethical or fraudulent activity relating to VoIP, such as call spoofing, robocalling and autodialers, or fraudulent STIR/SHAKEN attestation.
founded 11 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Had this problem with Verizon, after MONTHS of inconsistent calling we were able to pin it down to their phased implementation of STIR/SHAKEN and how our calls were presented to them. We had to make some tweaks, and everything went back to normal. Make sure either the FROM, PAID, or CONTACT headers have the IP address of your billed trunkgroup IP address, or add a diverted header to the call from the SBC. Good luck!!