SIP in higher education

[Shrihari Pandit <>]

IMO it makes sense to create e164.internet2.edu,  Allow the existing
I2 members to peer their telephone calls via the I2 network (if I2
policy permits).

The idea behind VPF is to create a Voice WAN designed to interconnect
VoIP networks together and allow them to "peer" directly among one
another across a common network.

Currently on VPF,  MIT and Yale are only reachable by using the 1010xx
access codes and they have not loaded any e164 numbers.  We hope once
we're running at 1 Summer we can connect to NOX and gain direct
connectivity to them and increase the participation with us.

There's a lot of equipment now on the market that is supporting ENUM
and SRV;  Especially in Softswitches, PBX, and Gateways.  There's 
off-the-shelf system (1U, 2U) that convert PRI trunks (1, 2, 4, 8, 16)
to Ethernet/SIP and supports ENUM for example.  Any university can 
now easily interface into the "VoIP" world if you well without having
to perform a fork-lift upgrade of their PBX, and take advantage of 
what's out there (VoIP origination, termination, ENUM, etc).

--- Shrihari 1-212-232-2020

On Tue, Mar 29, 2005 at 03:25:03PM -0800, David Paul Zimmerman wrote:
> Hi, all.  I've been reading all of the past mail and meeting archives, 
> and am offically chasing my own tail now.  I'm hoping that other 
> SIP.edu participants might be able to shed some light.
> 
> From the Feb 3, 2005 SIP.edu archived discussion:
> 
>  A question is posed about the testing of E.164 dialing - overall, 
> people
>  are interested in such a thing but most call participants are currently
>  too busy or otherwise involved to devote a lot of time to it. Others 
> are
>  unconvinced of the benefits in relation to the amount of configuration
>  work necessary to implement such a thing.
> 
> From Ben Teitelbaum's presentation at the Jun 16, 2004 workshop at 
> UPenn:
> 
>  o Internet2 acting both as private ENUM root (e164.internet2.edu) and 
> as trial campus ENUM (enum.internet2.edu)
>  o Was working, currently down
> 
> Please bear with me in my newness to all of this, but it appears to me 
> that ENUM support in the US is pretty fractured, due in no small part 
> to the non-delegation of 1.e164.arpa.  In response to my email from 
> last week, I did get one answer from Duane who runs the e164.org ENUM 
> registry, so that was appreciated, but only part of the answer I'm 
> searching for.  So I did better searches of the SIP.edu archives and in 
> general, tried to make some sense of the state of things.
> 
> Regarding the note above about I2 running a private ENUM root and trial 
> campus ENUM, I can't find anything real (i.e., NS or NAPTR RRs), only a 
> CNAME and IP.  Apparently it was working, but is down, and the UMich 
> undergrad who was putting it together is now working at Cisco.  So I 
> don't know where that goes from here, or if I2 has chosen to pursue a 
> different direction.  In general, there appears to not be a lot of 
> interest in e.164, from what I can tell.  My reading of various SIP.edu 
> archive postings seems that it is viewed with the deprecated importance 
> of "legacy" 12-key phone integration, rather than something 
> "interesting" like 
> sip:.
> 
> Beyond that, I've found a number of private ENUM providers:
> 
>       - E164.org (http://www.e164.org/)
>       - ENUM.org (http://www.enum.org/information/trial.cfm)
>       - Stealth VPF (http://www.thevpf.com/?action=enum)
>       - FreeWorld Dialup (http://www.pulver.com/fwd/)
> 
> and there are more, I'm sure, but there's no advice in the cookbook 
> about any of this.  Some of those ENUM providers have their own 
> presence on the PSTN side (e.g. FWD has +87810 393), some are 
> completely virtual (e.g. ENUM.org), and other mixes.  Stealth lists 
> Yale and MIT as members.  It appears that E164.org also allows you to 
> put your own number in verbatim, as I believe Stealth VPF does.  At the 
> end of the day, I'm not sure how to deal with putting ENUM support in 
> place for +1-510-66x-xxxx (e.g. 4.5.9.9.4.6.6.0.1.5.1.???) in such a 
> way that follows a SIP.edu roadmap (paved or not).
> 
> I'm getting dizzy :-) and see three choices at the moment:
> 
>       - wait and see, keep in touch with SIP.edu progress on ENUM
>       - sign up with nearly-free (i.e., pay or donate) private ENUM 
>       provider (but which one for SIP.edu?)
>       - specifically pursue operation of e164.internet2.edu ENUM root for 
> SIP.edu testing
> 
> Am I way off base?
> 
>                       dp