Re: [VoiceOps] Canadian Reputation and Spam

Few things 1. Canada has a separate S/S token authority and there is no agreement in place to be able to delegate from the USA to Canada and vice versa. That being said - S/S is not being widely used for call filtering as far as we can tell 2. Hiya and the rest of the racketeers have only

Re: [VoiceOps] troubleshooting RTP loss - and does anyone use webair/opti9?

+1 for MTR also iperf in both directions. And if the only tool you have is ping. Change ping frequency and packet size to match G711. Ping each individual hop along the way, that you can, and look for discrepancies. Keep in mind it's ICMP so it will get deprioritized, but if it works fine

Re: [VoiceOps] STIR/SHAKEN warning!

Hopefully on-topic. How are you handling TFN atestations? Although a part of NANP - it's a different technology at the network level in terms of chain of authority and routing. RespOrg manages the number, but can provision and use many carriers to make outbound calls using the TFN Caller ID (and

Re: [VoiceOps] TF number ported out/re-assigned without authorization

NASC is a name for a process where your RespOrg takes ownership of the TFN without the cooperation of the losing carrier. So you can expect it to be bumpier than the usual give and take. If you are not your own RespOrg - then thinQ is likely not going to cooperate - since it would create

Re: [VoiceOps] TF number ported out/re-assigned without authorization

Do you have a <30 day invoice with the number on it? I would try to NASC it... it may set off a pissing match between you and the current user, but if you can show that you had it first... you may win it. [image: Star Telecom - Cloud Communications and Customer Experience Solutions]

Re: [VoiceOps] Bell Canada wholesale SIP outage?

Our monitoring detected their public SBCs going down at around 6pm et. Our private connections and their TFN/local services seem to be up and running. May be an outage or a really blunt DDoS mitigation. [image: Star Telecom - Cloud Communications and Customer Experience Solutions]

Re: [VoiceOps] Five9 Issues / DDoS?

hone numbers that are having issues on inbound and check their actual > owner. > > > > *From: *VoiceOps on behalf of Ivan > Kovacevic via VoiceOps > *Reply-To: *Ivan Kovacevic > *Date: *Monday, September 27, 2021 at 3:23 PM > *To: *VoiceOps > *Subject: *[VoiceOps] Five9 Iss

[VoiceOps] Five9 Issues / DDoS?

So we have a Five9 SIP Trunking client who is being told by Five9 that their IVR/DTMF isn't working because of the Bandwidth.com outage. which is strange because their call path does not touch bandwidth.com at all... and raises the prospect of Five9s being targeted separately from Bandwidth?

Re: [VoiceOps] Bandwidth East Coast Issues

third. and our monitoring picked up packet loss to their IPs. Hopefully not a DDOS or if it is, they are better prepared to mitigate it than voip.ms. [image: Star Telecom - Cloud Communications and Customer Experience Solutions] *Ivan Kovacevic* *Co-Founder and