Send VoiceOps mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/voiceops
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of VoiceOps digest..."
Today's Topics:
1. Odd "TOS violation" op intercept? (April Jones)
2. Re: Odd "TOS violation" op intercept? (Paul Timmins)
----------------------------------------------------------------------
Message: 1
Date: Tue, 21 May 2013 22:51:38 -0600
From: April Jones <[email protected]>
To: [email protected]
Subject: [VoiceOps] Odd "TOS violation" op intercept?
Message-ID:
<ca+vteyzofkcfywuy2vrp8oddkf5y5bquxc0ds1xf7s2nqkr...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/voiceops/attachments/20130521/bb2e50d3/attachment-0001.html>
------------------------------
Message: 2
Date: Wed, 22 May 2013 01:01:22 -0400
From: Paul Timmins <[email protected]>
To: April Jones <[email protected]>
Cc: [email protected]
Subject: Re: [VoiceOps] Odd "TOS violation" op intercept?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
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 <[email protected]> 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
> [email protected]
> https://puck.nether.net/mailman/listinfo/voiceops
------------------------------
Subject: Digest Footer
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
------------------------------
End of VoiceOps Digest, Vol 47, Issue 13
****************************************
