Re: Emergency VoIP Update

[Christopher Peabody <>]

Tyler - your slides looked great.  I will definitely be following up to see 
how
GU can start working with you guys on this.  I'm sorry I've not worked with 
you
earlier, we could have trialed some things for the spring meeting here (My
staff and MAX are doing all the networking).

However  - I'm wrestling with a couple of issues:

1. We're also trying to build something that supports inbound (DID) services,
not just outbound in a disaster.  I'm not sure how to do this without a 
carrier
- since all the carriers routing tables around the country are synchronized to
route calls to a particular carrier's end office..  If my grandmother calls my
did number - what happens? Better example (not to diss my granny here) - what
happens when the Presidents wife calls his private line - and I have no 
inbound
service.

In a crisis (which I spend a full 25% of my time planning for these days, 
being
so close to the pentagon) if my primary CLEC or PBX  fails - I have several
layers of backup in place for my data and voice networks - including multiple
carriers (internet and Ilec/Clec), multiple fibers terminating at multiple
DMarcs and we're now starting to work with Broadsoft on a hosted outsourced IP
solution that gives me back up dial tone from Gaithersburg Md (15 miles away).

But I don't have any way of controlling the DID services from the outside 
world
- since every carrier is supposed to send them to my CLEC.  How do I get them
routing around the PBX?  I cannot think of any way to accomplish this without 
a
carrier.  Hence, we've pulled PaeTec into this.

What we're proposing is to put a Broadsoft server on the MAX ring - with an IP
layer transport circuit (t1 to start) connecting this server back to PaeTec's
national network.  If they lose their CO, or I lose my PBX, PaeTec will route
calls to the broadsoft server and then via my MAX connection to one of my core
routers.

PaeTec see's this as a potential nice way for them to start engineering some
redundancy for their customers.  I love them to death, but they only have one
CO here in DC - and if it fails, my inbound services are wiped out. As I said,
I have multiple back up solutions for outbound calling (and am very interested
in the VideNet stuff) - but nothing for inbound.

I will have GU DID numbers terminating at the Broadsoft server at a MAX node 
in
Maryland. So if there is a catastrophic failure (either at PaeTec or my PBX)-
I'll have the TDM carriers pointing just as they always have to PaeTec - who
will deliver me the calls via IP as opposed to the TDM PRI's they do now.

Are we nuts?

2. Ben has tried to explain this to me also - but in your solution - can we
call anyone that does not peer with us (I2/SEGP/Gigapop)?  Again, I am not 
sure
how we could do that - without involving a carrier to "hop off".

That also brings up lots of potential interesting regulatory questions.
However, I believe these are ones we need to address.
Oh well - just food for thought.  I look forward to working with you folks.

CBP


Ben Teitelbaum wrote:

> Tyler,
>
> This is very interesting and would certainly be a big value-add for
> Internet2 H.323 VoIP testbed participants.  All the more reason to
> keep pushing to integrate the two dialing plans.
>
> I should mention that Broadsoft and the MAX are working on a SIP-based
> disaster recovery trial in the DC area.  Chris Peabody (Georgetown)
> will be briefing the VoIP WG on this at the next meeting (April 8th).
>
> There are certainly a number of possible architectures for providing
> disaster recovery services.  It might be fun to get a bunch of us
> together in DC to explore these.
>
> -- ben
>
> Tyler Miller Johnson 
> <>
>  writes:
>
> > As you know, ViDeNet has been developing a plan for emergency voice
> > communications using peered h.323 gatekeepers under GDS. Using the
> > ViDeNet directory, one can simply search for 'emergency' and identify
> > a gateway anywhere in the world to which traffic can be directed.
> >
> > I received indications of interest from about a dozen schools. To
> > date, four institutions have begun implementing this. So far, Ohio
> > State and UNC are confirmed working.
> >
> > I encourage others to view the presentation for more information:
> > http://www.unc.edu/video/imc/emergency/emergency.ppt
> >
> > These services are available to any ViDeNet institution. We hope to
> > use this as a service in this time of uncertain security, and also as
> > a test bed for the exploration of inter-realm authentication and
> > authorization architectures, leading toward an accountable mechanism
> > for resource sharing.
> >
>

---------------------------------------------------------------wg-voip-+
For list utilities, archives, subscribe, unsubscribe, etc. please visit the
ListProc web interface at 

    http://archives.internet2.edu/

---------------------------------------------------------------wg-voip--