Odd "TOS violation" op intercept?
Hi voiceops, I've had a rash of tickets since Friday from various customers, to varied destinations over multiple vendors where I'm getting a terrible operator intercept/recording, and I'm wondering if anyone else has heard it or knows who is playing it. Recording plays "This call was routed in violation of our terms of service" then asks to record the orig/term and advises to report it to "your phone provider." I haven't found anything definitive, but I also haven't had a lot of time to really dig in... april j.
Reminds me of the intercepts that MagicJack (Ymax) was doing to calls delivered to them across local interconnection groups that they perceived should have come across feature group d. It was all about making sure to monetize intercarrier compensation as precisely as possible (read: not allowing a single misrouted call to terminate to the wrong groups, for fear a few tenths of a cent might slip from their grasp) On May 22, 2013, at 12:51 AM, April Jones <april at teliax.com> wrote:
Hi voiceops,
I've had a rash of tickets since Friday from various customers, to varied destinations over multiple vendors where I'm getting a terrible operator intercept/recording, and I'm wondering if anyone else has heard it or knows who is playing it.
Recording plays "This call was routed in violation of our terms of service" then asks to record the orig/term and advises to report it to "your phone provider."
I haven't found anything definitive, but I also haven't had a lot of time to really dig in...
april j. _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Did anyone narrow down an offending region/carrier? I'm curious. I haven't gotten any reports, but my customers are regionalized. Regards, Jared Geiger On Tue, May 21, 2013 at 10:01 PM, Paul Timmins <paul at timmins.net> wrote:
Reminds me of the intercepts that MagicJack (Ymax) was doing to calls delivered to them across local interconnection groups that they perceived should have come across feature group d. It was all about making sure to monetize intercarrier compensation as precisely as possible (read: not allowing a single misrouted call to terminate to the wrong groups, for fear a few tenths of a cent might slip from their grasp)
On May 22, 2013, at 12:51 AM, April Jones <april at teliax.com> wrote:
Hi voiceops,
I've had a rash of tickets since Friday from various customers, to varied destinations over multiple vendors where I'm getting a terrible operator intercept/recording, and I'm wondering if anyone else has heard it or knows who is playing it.
Recording plays "This call was routed in violation of our terms of service" then asks to record the orig/term and advises to report it to "your phone provider."
I haven't found anything definitive, but I also haven't had a lot of time to really dig in...
april j. _______________________________________________ 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
We heard a few reports this week (Wednesday?) related to a number we have in a CenturyLink exchange that's forwarded to our main office. It subsided later in the day and I haven't heard of any new reports. Frank From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Jared Geiger Sent: Saturday, May 25, 2013 3:34 PM To: VoiceOps Subject: Re: [VoiceOps] Odd "TOS violation" op intercept? Did anyone narrow down an offending region/carrier? I'm curious. I haven't gotten any reports, but my customers are regionalized. Regards, Jared Geiger On Tue, May 21, 2013 at 10:01 PM, Paul Timmins <paul at timmins.net <mailto:paul at timmins.net> > wrote: Reminds me of the intercepts that MagicJack (Ymax) was doing to calls delivered to them across local interconnection groups that they perceived should have come across feature group d. It was all about making sure to monetize intercarrier compensation as precisely as possible (read: not allowing a single misrouted call to terminate to the wrong groups, for fear a few tenths of a cent might slip from their grasp) On May 22, 2013, at 12:51 AM, April Jones <april at teliax.com <mailto:april at teliax.com> > wrote:
Hi voiceops,
I've had a rash of tickets since Friday from various customers, to varied destinations over multiple vendors where I'm getting a terrible operator intercept/recording, and I'm wondering if anyone else has heard it or knows who is playing it.
Recording plays "This call was routed in violation of our terms of service" then asks to record the orig/term and advises to report it to "your phone provider."
I haven't found anything definitive, but I also haven't had a lot of time to really dig in...
april j.
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops
participants (4)
-
april＠teliax.com -
frnkblk＠iname.com -
jared＠compuwizz.net -
paul＠timmins.net