Extension Mobility API and ASA Phone Proxy

Version 1

    Subject: RE: Extension Mobility API and ASA Phone Proxy
    Replied by: David Staudt on 24-02-2010 04:57:18 PM
    This should be possible, though since the phones do not yet support HTTPS, your E/M login credentials will be sent unencrypted over the internet (unless you build the login UI in a web browser, etc.)
     
     
    This document was generated from CDN thread

    Created by: Chase Casanova on 24-02-2010 04:26:21 PM
    Can I use the Extension Mobility API with ASA Phone Proxy, i.e. does the phone need to be able to get to an HTTP/HTTPS site?
     
    The ASA Phone Proxy feature proxies phone connections through the ASA, so there is no http access to or from the phone. 
     
    Can I use the Extension Mobility API to create a web GUI that will allow my users to get their profile on their phones?
     
    Thanks,
    -C
     

    Subject: RE: Extension Mobility API and ASA Phone Proxy
    Replied by: Chase Casanova on 24-02-2010 06:22:53 PM
    Hi David,
     
    So my question is can I use the Extension Mobility API to create a web GUI that my users can access via web browser that will log them into their phone assuming the phone is connected via ASA Phone Proxy and only has SCCP and TFTP access to the Communications Manager?
     
    I think your answer was yes, but I just want to double check.
     
    Is this how it would work on the backend?  The Extension Mobility API would tell the Extension Mobility service to dynamically generate a new TFTP config file for the phone.  Then the CUCM would issue a reset for the phone and the phone would grab the new config?
     
    Thanks,
    -C

    Subject: RE: Extension Mobility API and ASA Phone Proxy
    Replied by: David Staudt on 24-02-2010 06:41:13 PM
    Correct on both counts.
     
    Your external-facing application would accept the user credentials and device name (via HTTPS), then turn around and use the E/M API to the UCM to effect the login.  The E/M API service would update the UCM config/database, and initiate an SCCP reset message to the phone (which ASA would proxy.)