1 / 10

sip.EDU @ UPenn

sip.EDU @ UPenn. Steve Blair Sr. Network Engineer ISC Networking & Telecommunications blairs@isc.upenn.edu. Background. Currently a Verizon Centrex environment ~26,000 lines 4500 student lines Local, intra-Lata, 411 service LD & International from MCI and Paetec

dianewhite
Download Presentation

sip.EDU @ UPenn

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. sip.EDU @ UPenn Steve Blair Sr. Network Engineer ISC Networking & Telecommunications blairs@isc.upenn.edu

  2. Background

  3. Currently a Verizon Centrex environment • ~26,000 lines • 4500 student lines • Local, intra-Lata, 411 service • LD & International from MCI and Paetec • Switched 10/100 Campus LAN • ~ 30,000 public IP addresses • Redundant Gigabit Ethernet core links • Commodity Internet via Cogent, DCAnet, UUnet • I2 access via MAGPI GigaPOP (www.magpi.net) sip.EDU @ UPenn

  4. June 2001 began lab tests on Cisco Call Manager. June 2002 began lab tests on Cisco SIP Proxy Server (CSPS) September 2002 began lab tests on Broadworks January 2003 began lab tests on SER August 2003 began production pilot of Broadworks October 2003 sip.EDU operational with 23,000 subscribers for Fall I2 Members Meeting. May 2004 began production pilot of SER sip.EDU @ UPenn

  5. Cisco 2620XM with a single VWIC 1MFT-T1 per router T1/PRI trunks to Verizon DMS100 CO switch Sun V100 or Dell PowerEdge 1750 server hardware Cisco, ipDialog, Polycom hardphones Xten, Session soft clients

  6. sip.EDU Proxy Selection Q: What went into your choice of SIP proxy and gateway? A: Inexperience Talk about skinnyto phoneset sip.EDU @ UPenn

  7. sip.EDU Implementation Design A: Addressing format <pennkey>@upenn.edu Respect for privacy in PennCommunity DB Understand results for support staff & ROI Reuse existing info Q: What went into the design of our implementation? sip.EDU @ UPenn

  8. sip.EDU Lessons Learned A: New stuff scares the hell out of people. Q: What are our Lessons learned? Skip to next slide after saying we learned alot sip.EDU @ UPenn

  9. sip.EDU Issues Faced A: 1. Organizational boundaries 2. Defining requirements Identifying metrics 3.Proxy software bugs Poor client & server documentation Finding qualified vendor support 4.Getting a directory extract Q: What issues did we face? sip.EDU @ UPenn

  10. sip.EDU Future Plans A: Productionize our proxy Directory integration for provisioning Hosted Gateway service Residential Living VoIP offering Q: What are our future plans? sip.EDU @ UPenn

More Related