Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 22 Next »

 

Redirection server

When the VoIP phone contacts the Gigaset server, in order to get all the necessary configuration data, the redirection server supplies the URL of the provisioning server which is responsible for providing the VoIP phone with the provider data (SIP account).
To enable auto-provisioning (i.e. the end-user does not need to select the provider manually) the provisioner must add the redirection information for the VoIP phones to the redirection database.

Setting up redirection information using the web-interface


To add the redirection data to the redirection database, Gigaset provides a web user interface for provisioners.

You need a user account (user name and password) which has to be provided by Gigaset Communications.

Open the web user interface:

http://prov.gigaset.net

 

Temporary address:

https://prov.gigaset.net/Editor/#loginPage

Login using the user name and password provided by Gigaset.



Select the option Redirect portal.


 



 

If the login is successful, the main menu is opened. The following functions are available:

  • Registration, control and deregistration of single devices
  • Display of devices list
  • Upload of prepared XML files






 

Registering VoIP phones

 

  • To register a Gigaset VoIP phone, enter the MAC-ID (XXXXXXXXXXXX-XXXX) of the device, the URL of the provisioning server and the Provider for the device configuration.

    URL and Provider can be entered manually or selected from a list of known provisioner URLs and providers.

Example: http://provider.com/xml/%MACD.xml

  • Click on the Register buttonWhen to save the entry.

    The corresponding parameters are checked and – if approved – saved in the Gigaset redirection database. The provisioner is informed accordingly.

 

 

When using Maxwell 10, connection to the server and loading the XML configuration data takes longer then with other Gigaset devices. The reason is that other Android processes also need to be started after boot.

Connection to Redirect server 50 seconds after boot.

Activate new xml configuration 2 minutes after boot.

 

Example of usage

1 Registration of the single device
          To register a single device you may follow two different scenarios:

  • do it manually, by using "Register" tab, as shown below

 

 

 

 

 

 

 

 

 

 

 

  • using XML file of the next structure:
Registration of the single device
<methodCall>
  <methodName>autoprov.registerDevice</methodName>
    <params>
     <param>
	 <value>
	   <string>7C2F80820EC0-55DF</string>
	 </value>
	 </param>
	 <param>
	 <value>
		<string>http://172.29.0.103/plainxml/42/2/xml/7C2F80820EC0.xml</string>
	 </value>
	 </param>
	 <param>
	 <value>
		<string>Daryna</string>
	 </value>
	 </param>
	</params>
</methodCall>

 

XML template can be find here:

You need to create valid XML – file in accordance with the provided example below, then “Browse” it and “Upload”.                                                                                                                                                                                                                                                                          

 

 

 

 

 

 

 

 

 

 

 

Next server's answers are possible:

Server's answrers
Return value (1) (Boolean) 1 | 0
                           1 = true, 0 = false
Return value (2) (String)
                          if true: OK: password
                          if false: mac_already_in_use
                                    mac_invalid
                                    url_invalid
                                    name_invalid

 

After successful uploading your XML – file, you will see server response:

 

 

 

 

 

 

 

 

 

 

 

 


2 Derigestration of a single device
         You can derigester device with a MAC - ID – address e.g. 7C2F80820EC0” manually, by pressing, “Deregister” button
on the left corner of the window:












Usage of XML file instead is also possible:

Deregistration of the single device
<methodCall>
  <methodName>autoprov.deregisterDevice</methodName>
   <params>
    <param>
    <value>
      <string>7C2F80820EC0-55DF</string>
    </value>
    </param>
   </params>
</methodCall>

 

XML template for the deregistration can be downloaded here:

 

After XML file was constructed, it is necessary to upload it, in the same way as it was described previously. Different
server's answers are possible:

 

Server's answrers
Return value (1) (Boolean) 1 | 0
                           1 = true, 0 = false
Return value (2) (String)
                           if true: OK
                           if false: mac_not_found
                                     mac_invalid

 

In our case XML file within MAC-ID were valid and we got next response:

 


3 Register device list

          Let's assume that at once, you may need to register not a single device, but a list containing several of them,
XML structure for such a case will look like this:

Deregistration of the single device
<methodCall>
  <methodName>autoprov.registerDeviceList</methodName>
   <params>
    <param>
    <value>
      <array>
      <data>
         <value><string>7C2F80820EC0-55DF</string></value>
         <value><string>7C2F80208295-1910</string></value>
     </data>
     </array>
    </value>
    </param>
    <param>
        <value><string>http://172.29.0.103/plainxml/%DVID/xml/%MACD.xml</string></value>
   </param>
    <param>
       <value><string>Daryna</string></value>
   </param>
  </params>
</methodCall>

XML template can be downloaded here:

 

As previously, several server's answers are possible:

Server's answrers
Return value (1) (Boolean) 1 | 0
                           1 = true, 0 = false
Return value (2-n) (String)
                           if true: OK: Password
                           if false: mac_invalid
                                     url_invalid
                                     name_invalid
                                     mac_already_in_use
                                     mac_not_exist

The next picture shows, 'True' server's answer:


An example of real server response after usage of the XML – file with incorrect data (inappropriate MAC-ID was used ):

 

4 Deregister list of the devices

 

 

 

  • No labels