E20 provisioning using HTTP server

[epicolo]

Hi,

does someone have a document on how to use E20 provisioning with HTTP server?

I would like to know the format used for E20 downloadable configuration and the process flow.

Thanks

Elter

Provisionig mode: HTTP

: If set, the E20 will try to download configuration from a web server. The URL is the concatenation of the External Manager address and the Path parameter. If the protocol is https, the E20 will use HTTPS during the download. If the HttpMethod parameter is POST, the E20 will do an HTTP post to the web server. Otherwise, it will do a HTTP Get to the web server. LoginName and password will be used if the web server requires username and password to download the configuration.

[Martin Koch]

First, for mass deployments I would go the TMS System, TMS provisioning or CUCM way.

I do not recall haing seen the document you ask for, let me know if you find one.

And even with it is always risky when the next software version comes,...

This is some info I remember from when I once tried it:

Depending on your config it will send out a POST or GET request with the mac, serial, version,

snumber and product.

GET Example:

/provisioning/e20.xml?mac=00%3A50%3A60%3AXX%3AXX%3AXX&serial=A1AAXXXXXXXX&version=TE4.0.0.245080&snumber=sXXXXX&product=TANDBERG%20E20

It will get this file on every reboot and then every 30 minutes.

On the other hand, if you set the mode to TMS instead of HTTP and you use the XML config file format

which you can download from the e20 via the webinterface:

http(s):///configuration.xml

That seem to work, but the handling of the source of the request might be harder then the POST/GET with the

above mentioned parameters as this request uses soap/xml to identify itself and I am also not sure if the e20

might expect or send some soap message which I could not process, ...

Btw, the C-Series systems (tried with tc4.2) lack the "mode: http".

What are you trying to do?

[epicolo]

The intention is to setup several E20 remotely (external configuration), to simulate some kind of quiosk mode on E20, where the EndUser can´t change the config and the E20 retrieve the original config after boot up (like persitent settings).

We would like to try this without TMS provisioning.

I saw some samples on TE4 admin guide but we need more detailed (suported) info.

Maybe this info you sent can help, but we wouldn´t like to spend a lot of time on a posible unsupported config.

Thanks

[Martin Koch]

Just looked at the admin guide and its described there, tested it and it works with the http provisioning.

In general its still the format of the config.xml file.

As you said, page 8 admin guide: http://www.tandberg.com/support/dl.php?id=1429&dir=User_Manuals&fn=Cisco%20IP%20Video%20Phone%20E20%20Administrator%20Guide%20(TE4.0).pdf

Even if it was not described in the example I replaced the two first lines of the config.xml

http://www.tandberg.com/XML/CUIL/2.0" product="TANDBERG Codec" version="TE4.0.0.245080">

with:

1

http://www.tandberg.com/XML/CUIL/2.0" product="TANDBERG Codec" version="TE4.0.0.245080">

and added :

at the end.

it worked for my e20.

The heartbeat 1 tells the e20 to access the webserver every minute.

If its just one e20 you might be able to just store this config file on a web directory and point the config to it.

For more advanced provisioning incl serial number and software version check some php or whatever scripting should work fine.

I also tried the "provisioning mode: auto" functionality as described on page 7.

Which works fine, so you could add tandbergprovisioning to your dns/webserver and the e20

will automatically request a post request to http://tandbergprovisioning/getconfig

Please vote the answers and mark the answer if your question is answered.