logging in or signing up 20040616 blair Lindon Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINTLite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: (To copy code, click on the text box) Embed: URL: Thumbnail: WordPress Embed Customize Embed The presentation is successfully added In Your Favorites. Views: 72 Category: Entertainment License: All Rights Reserved Like it (1) Dislike it (0) Added: October 02, 2007 This Presentation is Public Favorites: 0 Presentation Description No description available. Comments Posting comment... Premium member Presentation Transcript sip.EDU @ UPenn: sip.EDU @ UPenn Steve Blair Sr. Network Engineer ISC Networking & Telecommunications blairs@isc.upenn.edu Background: BackgroundSlide3: sip.EDU @ UPenn 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)Slide4: 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 @ UPennSlide5: 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 sip.EDU Proxy Selection: sip.EDU Proxy Selection Q: What went into your choice of SIP proxy and gateway? sip.EDU @ UPenn A: Inexperiencesip.EDU Implementation Design: sip.EDU Implementation Design Q: What went into the design of our implementation? sip.EDU @ UPenn A: Addressing format <pennkey>@upenn.edu Respect for privacy in PennCommunity DB Understand results for support staff & ROI Reuse existing info sip.EDU Lessons Learned: sip.EDU Lessons Learned Q: What are our Lessons learned? sip.EDU @ UPenn A: New stuff scares the hell out of people.sip.EDU Issues Faced: Q: What issues did we face? sip.EDU @ UPenn 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 sip.EDU Future Plans: Q: What are our future plans? sip.EDU @ UPenn sip.EDU Future Plans A: Productionize our proxy Directory integration for provisioning Hosted Gateway service Residential Living VoIP offering You do not have the permission to view this presentation. In order to view it, please contact the author of the presentation.
20040616 blair Lindon Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINTLite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: (To copy code, click on the text box) Embed: URL: Thumbnail: WordPress Embed Customize Embed The presentation is successfully added In Your Favorites. Views: 72 Category: Entertainment License: All Rights Reserved Like it (1) Dislike it (0) Added: October 02, 2007 This Presentation is Public Favorites: 0 Presentation Description No description available. Comments Posting comment... Premium member Presentation Transcript sip.EDU @ UPenn: sip.EDU @ UPenn Steve Blair Sr. Network Engineer ISC Networking & Telecommunications blairs@isc.upenn.edu Background: BackgroundSlide3: sip.EDU @ UPenn 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)Slide4: 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 @ UPennSlide5: 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 sip.EDU Proxy Selection: sip.EDU Proxy Selection Q: What went into your choice of SIP proxy and gateway? sip.EDU @ UPenn A: Inexperiencesip.EDU Implementation Design: sip.EDU Implementation Design Q: What went into the design of our implementation? sip.EDU @ UPenn A: Addressing format <pennkey>@upenn.edu Respect for privacy in PennCommunity DB Understand results for support staff & ROI Reuse existing info sip.EDU Lessons Learned: sip.EDU Lessons Learned Q: What are our Lessons learned? sip.EDU @ UPenn A: New stuff scares the hell out of people.sip.EDU Issues Faced: Q: What issues did we face? sip.EDU @ UPenn 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 sip.EDU Future Plans: Q: What are our future plans? sip.EDU @ UPenn sip.EDU Future Plans A: Productionize our proxy Directory integration for provisioning Hosted Gateway service Residential Living VoIP offering