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. Strange calling patterns (Ryan Delgrosso)
2. Local ringback on SIP 180 from Broadsoft media server vs
phone generated RBT (John Botha)
3. Re: Strange calling patterns (Hiers, David)
4. Re: Local ringback on SIP 180 from Broadsoft media server vs
phone generated RBT (PE)
5. Re: Local ringback on SIP 180 from Broadsoft media server vs
phone generated RBT (John S. Robinson)
----------------------------------------------------------------------
Message: 1
Date: Mon, 05 Nov 2012 16:09:43 -0800
From: Ryan Delgrosso <[email protected]>
To: [email protected]
Subject: [VoiceOps] Strange calling patterns
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
All,
So I know with the election tomorrow all bets are basically off for
weird calling patterns but I have seen some really strange stuff today
and was hoping someone else might have seen it as well or be able to
validate some theories.
I had a number in a Michigan exchange receive 99,000 inbound calls in a
single hour (no that is actually ninety nine thousand) and that user had
their number forwarded off to another overloaded Michigan exchange so it
generated nearly a million outbound call attempts as my system attempted
to find an open trunk to get through. Earlier I had a similar case with
a Florida exchange where a single user received 150,000 calls in an hour
all with invalid source numbers, and all arrived through otherwise
reputable origination carriers (L3, Paetec etc).
The commonality here is that in both cases the customer account had no
registered device and had forwarding setup, and the destination for both
was an overloaded exchange in a swing state. In all cases I have
suspended the accounts and stopped the traffic but it still doesn't give
me the warm and fuzzies.
My first inclination is this feels like some kind of DDOS to hurt
polling or last minute campaigning since if the attempts were legitimate
they wouldn't be winning supporters by calling them 150,000 times but im
really open to ideas here.
Anyone out there with some experience or theories, feel free to chime in
or reply off list if paranoid.
-Ryan
------------------------------
Message: 2
Date: Tue, 6 Nov 2012 07:40:48 +0200
From: John Botha <[email protected]>
To: <[email protected]>
Subject: [VoiceOps] Local ringback on SIP 180 from Broadsoft media
server vs phone generated RBT
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
We are debating on having our Broadsoft media server generating RBT on a SIP
180 vs having the phone generate it locally, which is currently the case.
We have found sporadic ringback issues when the phones generate local RBT
when it plays one ring and then goes silent or no RBT at all. This only
happens once out of approximately 10 calls though, and signalling looks
normal (ie no 180 followed by 183 or duplicate messaging).
The end-user hardware devices are mostly Polycom.
Does anyone have some experience, advice and information this?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/voiceops/attachments/20121106/5568e354/attachment-0001.html>
------------------------------
Message: 3
Date: Tue, 6 Nov 2012 14:38:13 +0000
From: "Hiers, David" <[email protected]>
To: "[email protected]" <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: [VoiceOps] Strange calling patterns
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
Phone Jamming is a time-honored political tradition, just ask Allen Raymond.
Keep your logs/cdrs handy, the Feds might visit.
David
-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Ryan Delgrosso
Sent: Monday, November 05, 2012 16:10
To: [email protected]
Subject: [VoiceOps] Strange calling patterns
All,
So I know with the election tomorrow all bets are basically off for weird
calling patterns but I have seen some really strange stuff today and was hoping
someone else might have seen it as well or be able to validate some theories.
I had a number in a Michigan exchange receive 99,000 inbound calls in a single
hour (no that is actually ninety nine thousand) and that user had their number
forwarded off to another overloaded Michigan exchange so it generated nearly a
million outbound call attempts as my system attempted to find an open trunk to
get through. Earlier I had a similar case with a Florida exchange where a
single user received 150,000 calls in an hour all with invalid source numbers,
and all arrived through otherwise reputable origination carriers (L3, Paetec
etc).
The commonality here is that in both cases the customer account had no
registered device and had forwarding setup, and the destination for both was an
overloaded exchange in a swing state. In all cases I have suspended the
accounts and stopped the traffic but it still doesn't give me the warm and
fuzzies.
My first inclination is this feels like some kind of DDOS to hurt polling or
last minute campaigning since if the attempts were legitimate they wouldn't be
winning supporters by calling them 150,000 times but im really open to ideas
here.
Anyone out there with some experience or theories, feel free to chime in or
reply off list if paranoid.
-Ryan
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
This message and any attachments are intended only for the use of the addressee
and may contain information that is privileged and confidential. If the reader
of the message is not the intended recipient or an authorized representative of
the intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication
in error, please notify us immediately by e-mail and delete the message and any
attachments from your system.
------------------------------
Message: 4
Date: Tue, 6 Nov 2012 09:51:18 -0500
From: PE <[email protected]>
To: John Botha <[email protected]>
Cc: [email protected]
Subject: Re: [VoiceOps] Local ringback on SIP 180 from Broadsoft media
server vs phone generated RBT
Message-ID:
<CAHm=SaLLOHsr+S-uSr_jg+hV2=jcgzaoi+yxn-dcwrrodnm...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
So, this is mostly on outbound calls (from the User)? What version of
firmware on the phones?
On Tue, Nov 6, 2012 at 12:40 AM, John Botha <[email protected]> wrote:
> We are debating on having our Broadsoft media server generating RBT on a
> SIP 180 vs having the phone generate it locally, which is currently the
> case.****
>
> We have found sporadic ringback issues when the phones generate local RBT
> when it plays one ring and then goes silent or no RBT at all. This only
> happens once out of approximately 10 calls though, and signalling looks
> normal (ie no 180 followed by 183 or duplicate messaging).****
>
> The end-user hardware devices are mostly Polycom.****
>
> Does anyone have some experience, advice and information this? ****
>
> _______________________________________________
> VoiceOps mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/voiceops/attachments/20121106/178f1902/attachment-0001.html>
------------------------------
Message: 5
Date: Tue, 06 Nov 2012 09:06:41 -0600
From: "John S. Robinson" <[email protected]>
To: [email protected], [email protected]
Subject: Re: [VoiceOps] Local ringback on SIP 180 from Broadsoft media
server vs phone generated RBT
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
In general, I advise my clients to *not *generate ringback tone on
phones. Best practice is to have phones indicate alerting state by
responding with 180 RINGING with no SDP, and require PRACK method.
Media flow from phones /before /200 OK may cause other problems,
especially in a simultaneous ringing environment.
One common practice is that 180 RINGING is sent without SDP, and a media
gateway closer to the caller furnishes the ringback tone. PRACK is
optionally used to ensure that the provisional response is reliable.
Another common practice is to send 183 PROGRESS with SDP indicating the
availability of early media and progress tone, but that practice isn't
bullet proof.
Hope this helps. If you would like additional discussion, please feel
free to contact me off list.
John S. Robinson
/[email protected] <mailto:[email protected]>/
Communichanic Consultants, Inc.
On 11/5/2012 23:40, John Botha wrote:
>
> We are debating on having our Broadsoft media server generating RBT on
> a SIP 180 vs having the phone generate it locally, which is currently
> the case.
>
> We have found sporadic ringback issues when the phones generate local
> RBT when it plays one ring and then goes silent or no RBT at all. This
> only happens once out of approximately 10 calls though, and signalling
> looks normal (ie no 180 followed by 183 or duplicate messaging).
>
> The end-user hardware devices are mostly Polycom.
>
> Does anyone have some experience, advice and information this?
>
>
>
> _______________________________________________
> VoiceOps mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/voiceops
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/voiceops/attachments/20121106/0c4dee4b/attachment-0001.html>
------------------------------
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
End of VoiceOps Digest, Vol 41, Issue 6
***************************************
