slide1 n.
Skip this Video
Loading SlideShow in 5 Seconds..
Zdenek Nejedly, Campus Services PowerPoint Presentation
Download Presentation
Zdenek Nejedly, Campus Services

Loading in 2 Seconds...

play fullscreen
1 / 30

Zdenek Nejedly, Campus Services - PowerPoint PPT Presentation

  • Uploaded on

IP Phone Services: Integration of Campus IT Services with IP Phones at the University of Guelph. Zdenek Nejedly, Campus Services Rasim Duric, Lelio Fulgenzi, Deborah MacDougall, Networking Services Computing & Communications Services University of Guelph. IP Phone Services.

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'Zdenek Nejedly, Campus Services' - makara

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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

IP Phone Services: Integration of Campus IT Services with IP Phones at the University of Guelph

Zdenek Nejedly, Campus Services

Rasim Duric, Lelio Fulgenzi, Deborah MacDougall, Networking Services

Computing & Communications Services

University of Guelph

ip phone services
IP Phone Services
  • IP Phone Services : Principles & technologies
  • Case studies/sample apps: challenges & solutions
  • J2EE framework: XML object generation, identification & authentication modules
voip deployment at ug
VOIP deployment at UG
  • 2002: CCS tests
  • 2003: Active deployment to business and residence clients starts
  • 2003 Fall: development of first IP services starts
  • 2004 September: deployment of about 7200 units completed
  • More details in "VOIP at Guelph: 4 years on..." talk by Lelio and Drew
ip phone services1
IP Phone Services
  • Based on web technologies
  • XML messages sent over HTTP
  • Any server-side platforms (J2EE, ASP/.NET, php)
  • Other APIs: Java Telephony API

IP Phone Services

Includes XML browser and

a simple web server

ip services request flow
IP Services Request Flow

Two kinds of requests:

  • Client (User or Phone) initiated (pull)
    • User via the Directories/Services button
    • Phone via Idle URL settings
  • Server initiated (push)
    • requires Basic Authentication of the pushing server
ip services request flow1
IP Services Request Flow
  • Client (User or Phone) initiated (pull)





ip services request flow2
IP Services Request Flow

2. Server initiated (push)

messages xml objects
Messages: XML Objects
  • All data (text to be displayed, button actions, links/URLs) packaged in Cisco pre-defined XML objects
  • Phone’s browser interprets the XML and displays lists, menus, soft keys
  • No client-side scripting
xml object examples
XML Object Examples
  • CiscoIPPhoneText, CiscoIPPhoneMenu, CiscoIPPhoneInput, CiscoIPPhoneDirectory, CiscoIPPhoneImage, CiscoIPPhoneExecute, CiscoIPPhoneResponse, CiscoIPPhoneError, and more…


<Title>My Directory</Title>

<Text>Good bye…..</Text>







campus directory
Campus Directory
  • Phone directory based on the campus LDAP
  • Client dependent search scope and presentation (staff vs. students in residences)
  • Packaged solution (ASP/COM) not fully extensible -> need for a custom solution
  • Development goals:
    • Extensible framework
    • Complete control over the LDAP interface
    • OS independent – suitable for mixed environment
    • Interoperability with other/future company applications
  • Solution: J2EE servlet-based framework
campus directory2
Campus Directory
  • Demonstration …
campus directory lessons learned
Campus Directory – lessons learned
  • Scarce UI resources, e.g., Soft Keys – additional functionality makes existing features less accessible -> Requirements management and usability testing important.
  • The phone often fails silently and errors are difficult to debug -> Regression testing essential.
  • Implementation differences between firmware versions and different IP Phone models -> phone model aware applications.
implementation examples 2 my directory client authentication rdbms cooperation with portals
Implementation Examples:2. My Directory(client authentication, RDBMS, cooperation with portals)
my directory
My Directory
  • User-editable directory a.k.a. speed dial
  • Customization & Privacy -> user authentication
  • Authentication via phone keypad tedious - -> minimize the login/logout frequency
  • Security -> do not expose the Call Manager (packaged solution is based on the web access to the CCM)
my directory1
My Directory
  • Demonstration of speed dial, contact management (add new, edit existing, delete)
lessons learned solutions
Lessons learned & solutions
  • Persistent cookies not supported and the phone runs on DHCP -> client management on the server by MAC
  • Phone identification -> query the phone’s web server to get MAC or Phone Number
phone or browser
Phone or Browser?
  • Use IP Phone services where appropriate – phone is always on but provides only limited User Interface resources.
  • Infrequently used options waste UI resources
  • Use web browser for UI-intensive tasks – input facilitated via portlet designed under uPortal


  • Push text and audio to the IP Phones as needed
  • Emergency notifications, system management alerts, user support
  • Message delivery independent of user settings
  • Problem: Server pushing content to the phone must provide credentials of the user assigned to the phone – these are not known!
push2phone authorization
Push2phone Authorization

Default model – server must know

the user’s credentials

Modified model –

a proxy-authorization

module supports global

admin credentials

  • Challenges:
    • Limited screen capabilities and controls (software and hardware)
    • Additional features may complicate existing options
    • Intensive data input – use web apps
    • No persistent cookies – manage the persistence on the server, e.g. by MAC address
    • Minimize user authentication – implement a flavour of SSO
    • To avoid having to manage user credentials implement authentication proxy
  • Troubleshooting:
    • difficult debugging of invalid XML
    • For protocol debug use for example JMeter (in place of a packet monitor)
  • Implementation:
    • J2EE servlets & JSPs, MVC for portlet
    • Case studies: Campus Dir, My Dir, Push2Phone
dream ip phone service
Dream IP Phone Service
  • Write down a brief description of your dream IP Phone Service and submit it along with your name.
  • You can win a prize – popular vote or random draw.