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. Sandy Watch (Hiers, David (DS))
2. Re: Sandy Watch (Hiers, David (DS))
3. SIP Syntax Checker (Michael Hirschbichler)
4. Re: SIP Syntax Checker (Max M?hlbronner)
5. Re: SIP Syntax Checker (Alex Balashov)
6. Re: SIP Syntax Checker (Dan York)
7. Re: Sandy Watch (Jared Geiger)
----------------------------------------------------------------------
Message: 1
Date: Mon, 29 Oct 2012 13:58:15 -0500
From: "Hiers, David (DS)" <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [VoiceOps] Sandy Watch
Message-ID:
<81cdfc77fb2dc54db875d4f8ffc36ce01438da4...@dsmail2he.ds.ad.adp.com>
Content-Type: text/plain; charset="us-ascii"
Hi,
Is anyone seeing any storm related issues yet? I've got the expected drop in
calls as the NE shuts down, not much more on the radar.
I'll be watching/updating this list (and outages) tonight for any significant
events.
Thanks,
David
PS: Having your machines prepped for disaster is good, but what about your
people? All that expensive gear might not be not worth much if you've got no
one to operate it when the big one hits. After all, even first responders
don't respond if doing so would imperil their families... are your people wired
in to ready.gov?
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/voiceops/attachments/20121029/004c0915/attachment-0001.html>
------------------------------
Message: 2
Date: Tue, 30 Oct 2012 01:37:23 -0500
From: "Hiers, David (DS)" <[email protected]>
To: "Hiers, David (DS)" <[email protected]>, "[email protected]"
<[email protected]>
Subject: Re: [VoiceOps] Sandy Watch
Message-ID:
<81cdfc77fb2dc54db875d4f8ffc36ce01437822...@dsmail2he.ds.ad.adp.com>
Content-Type: text/plain; charset="us-ascii"
Nothing too surprising so far...
There seems to be pretty strong correlation between flooded areas with no
electricity and unregistered devices. I probably don't need to drop a 650 into
a fish tank to see if the issue is reproducible, but it is oddly tempting.
David
________________________________________
From: [email protected] [[email protected]] On Behalf
Of Hiers, David (DS)
Sent: Monday, October 29, 2012 11:58 AM
To: [email protected]
Subject: [VoiceOps] Sandy Watch
Hi,
Is anyone seeing any storm related issues yet? I've got the expected drop in
calls as the NE shuts down, not much more on the radar.
I'll be watching/updating this list (and outages) tonight for any significant
events.
Thanks,
David
PS: Having your machines prepped for disaster is good, but what about your
people? All that expensive gear might not be not worth much if you've got no
one to operate it when the big one hits. After all, even first responders
don't respond if doing so would imperil their families... are your people wired
in to ready.gov?
________________________________
________________________________
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.
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: 3
Date: Tue, 30 Oct 2012 11:57:18 +0100
From: Michael Hirschbichler <[email protected]>
To: [email protected]
Subject: [VoiceOps] SIP Syntax Checker
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
Hi all,
for a little SIP security project, I want to check, if the syntax of an
incoming (recorded) SIP request is syntax-correct according to rfc3261.
Does anybody know a (opensource) application (perl-, python- or
whatsoever module) which is capable to do this job?
thx and br from vienna
Michael
--
Michael Hirschbichler, Mag. Dipl.-Ing.
Institute of Telecommunications
Vienna University of Technology
A-1040 Wien, Favoritenstr. 9-11/III/389
Phone: +43 1 58801 38846
Fax: +43 1 58801 9 38846
------------------------------
Message: 4
Date: Tue, 30 Oct 2012 12:20:21 +0100
From: Max M?hlbronner <[email protected]>
To: [email protected]
Subject: Re: [VoiceOps] SIP Syntax Checker
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi,
not sure if there is any standalone software, but have not heard of
anything yet (something like sipp but including validation of SIP
requests/responses according to rfc3261).
But you can build something similar with Opensips:
http://www.opensips.org/html/docs/modules/devel/sipmsgops.html#id293050
You would just have to send the calls through opensips, where you
execute sipmsg_validate() and log every malformed request.
Best Regards
Max M.
On 10/30/2012 11:57 AM, Michael Hirschbichler wrote:
> Hi all,
>
> for a little SIP security project, I want to check, if the syntax of an
> incoming (recorded) SIP request is syntax-correct according to rfc3261.
>
> Does anybody know a (opensource) application (perl-, python- or
> whatsoever module) which is capable to do this job?
>
> thx and br from vienna
> Michael
>
------------------------------
Message: 5
Date: Tue, 30 Oct 2012 15:45:42 +0400
From: Alex Balashov <[email protected]>
To: Max M?hlbronner <[email protected]>, [email protected]
Subject: Re: [VoiceOps] SIP Syntax Checker
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8
That doesn't do a whole lot, apart from applying a few select validation checks
and verifying that OpenSIPS finds the message legible on the whole.
"Max M?hlbronner" <[email protected]> wrote:
>Hi,
>
>
>not sure if there is any standalone software, but have not heard of
>anything yet (something like sipp but including validation of SIP
>requests/responses according to rfc3261).
>
>
>But you can build something similar with Opensips:
>
>http://www.opensips.org/html/docs/modules/devel/sipmsgops.html#id293050
>
>
>You would just have to send the calls through opensips, where you
>execute sipmsg_validate() and log every malformed request.
>
>
>
>Best Regards
>
>
>Max M.
>
>On 10/30/2012 11:57 AM, Michael Hirschbichler wrote:
>> Hi all,
>>
>> for a little SIP security project, I want to check, if the syntax of
>an
>> incoming (recorded) SIP request is syntax-correct according to
>rfc3261.
>>
>> Does anybody know a (opensource) application (perl-, python- or
>> whatsoever module) which is capable to do this job?
>>
>> thx and br from vienna
>> Michael
>>
>
>
>_______________________________________________
>VoiceOps mailing list
>[email protected]
>https://puck.nether.net/mailman/listinfo/voiceops
--
Sent from my mobile, and thus lacking in the refinement one might expect from a
fully-fledged keyboard.
Alex Balashov - Principal
Evariste Systems LLC
235 E Ponce de Leon Ave
Suite 106
Decatur, GA 30030
Tel: +1-678-954-0670
Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
------------------------------
Message: 6
Date: Tue, 30 Oct 2012 09:17:12 -0400
From: Dan York <[email protected]>
To: Michael Hirschbichler <[email protected]>
Cc: [email protected]
Subject: Re: [VoiceOps] SIP Syntax Checker
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Michael,
There are a good number of SIP security tools listed on:
http://www.voipsa.org/Resources/tools.php
You may find something there to help.
Dan
On Oct 30, 2012, at 6:57 AM, Michael Hirschbichler wrote:
> Hi all,
>
> for a little SIP security project, I want to check, if the syntax of an
> incoming (recorded) SIP request is syntax-correct according to rfc3261.
>
> Does anybody know a (opensource) application (perl-, python- or
> whatsoever module) which is capable to do this job?
>
> thx and br from vienna
> Michael
>
> --
> Michael Hirschbichler, Mag. Dipl.-Ing.
> Institute of Telecommunications
> Vienna University of Technology
> A-1040 Wien, Favoritenstr. 9-11/III/389
> Phone: +43 1 58801 38846
> Fax: +43 1 58801 9 38846
> _______________________________________________
> VoiceOps mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/voiceops
--
Dan York [email protected]
Phone: +1-802-735-1624 skype:danyork
http://www.danyork.com/
http://twitter.com/danyork
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/voiceops/attachments/20121030/a31dd78e/attachment-0001.html>
------------------------------
Message: 7
Date: Tue, 30 Oct 2012 09:34:36 -0400
From: Jared Geiger <[email protected]>
To: "Hiers, David (DS)" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [VoiceOps] Sandy Watch
Message-ID:
<cahuchrc1squfeq+tjczugze5fv+kez+qxhhaw9lohvhowyy...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
1) Looks like TATA NYC1 and NYC2 GSXes are down.
2) I got an email saying Telia only had 6 hours of power left at 6 AM
Eastern, so they may go dark as well at noon.
3) Our IP routes to Belgacom are broken and die in NYC on nlayer,
Cogent, and Abovenet.
4) Looks like Hypercube in NYC is down.
5) Reliance is going down in NYC
It seems all of our other trunks are up.
On Tue, Oct 30, 2012 at 2:37 AM, Hiers, David (DS) <[email protected]> wrote:
> Nothing too surprising so far...
>
> There seems to be pretty strong correlation between flooded areas with no
> electricity and unregistered devices. I probably don't need to drop a 650
> into a fish tank to see if the issue is reproducible, but it is oddly
> tempting.
>
>
> David
>
>
>
> ________________________________________
> From: [email protected] [[email protected]] On Behalf
> Of Hiers, David (DS)
> Sent: Monday, October 29, 2012 11:58 AM
> To: [email protected]
> Subject: [VoiceOps] Sandy Watch
>
> Hi,
>
> Is anyone seeing any storm related issues yet? I've got the expected drop in
> calls as the NE shuts down, not much more on the radar.
>
> I'll be watching/updating this list (and outages) tonight for any significant
> events.
>
> Thanks,
>
> David
>
> PS: Having your machines prepped for disaster is good, but what about your
> people? All that expensive gear might not be not worth much if you've got no
> one to operate it when the big one hits. After all, even first responders
> don't respond if doing so would imperil their families... are your people
> wired in to ready.gov?
>
>
>
> ________________________________
>
> ________________________________
> 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.
>
>
>
> 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.
>
> _______________________________________________
> VoiceOps mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/voiceops
------------------------------
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
End of VoiceOps Digest, Vol 40, Issue 29
****************************************
