View source for Configuration Guide For Stentofon Phone Application Server With Cisco Phones

This Guide describes how to install and set-up the Stentofon PhoneApplicationServer together with Cisco phones.

Prerequisites for PhoneApplicationServer with a Cisco Call Manager:

* A Cisco CallManager configured with a SIP Trunk to an AlphaCom node, see [[Cisco Call Manager 6 configuration guide]]
* [http://www.iis.net/ IIS] (Microsoft Internet Information Services)
* [http://www.microsoft.com/sqlserver/ MSSQL Server]
* [http://www.microsoft.com/NET/ Microsoft .NET Framework] (3.5 or later)

== Standard installation of prerequisites ==

The PhoneApplicationServer should be able to run in different Windows environments (XP, Vista, Windows Server etc), and with different version of the IIS and MSSQL). <br>
Also a remote MSSQL server connection should be possible. Below is step-by-step guide for setting up the prerequisites on a Windows XP, with the bundled IIS and a fresh install of MSSQL Express 2008.
In general this setup, and maintenance of the PhoneApplicationServer, will requires some "IT-knowledge". 

=== IIS and MSSQL Express on Windows XP ===

* Under the '''Control Panel''' / '''Add or Remove Programs''' selelct the '''Add/Remove Windows Components'''. Select '''Internet Information Services (IIS)''', and follow the standard setup.
* For IIS adminstration the Microsoft Management Console (mmc) can be used. Type '''mmc''' in Windows '''Run''' dialog. Add Snap-In '''Internet Information Services'''.
* From the [http://www.microsoft.com/express/sql/download/ SQL Express 2008 download page] select the '''Runtime with Management Tools''' install. Following the standard installation routine. In the final steps of installation select '''Windows Integrated Authentication''' when prompted.

=== Installing the PhoneApplicationServer ===

* Run the latest AlphaPhoneApplicationServerSetup.msi installer. If .NET 3.5 not already installed the installer will prompt for download and installation of the .NET framework.
* The PhoneApplicationServer will be added to the '''All Programs Menu''' under '''STENTOFON''' / '''AlphaCom Phone Application Server'''

==== Initializing the MSSQL Database table and Configure the AlphaCom connection ====

The PhoneApplicationServer operates by default on a MSSQL table called '''AlphaComStateDB''', and uses '''Integrated Security''' to access the table (meaning the credential of the user running the application)
The PhoneApplicationServer will create a new table in the database if it do not exist.

[[Image:PhoneAppServerDBCreated.JPG|thumb|600px|PhoneAppServer Database Table Created]] 
* Start the PhoneApplicationServer for the first time. After a short while it will report that it is not able to connect to the AlphaComStateDB table. Push the '''Create MSSQL Database''' button, and get a confirmation that the database is successfully created 
<br style="clear:both;" />
[[Image:PhoneAppServerStartNoConnection.JPG|thumb|600px|PhoneAppServer No AlphaCom Connection]]
* Restart the Application. Now PhoneApplicationServer will be able to connect to the database at start-up, but will probably fail to connect to the default AlphaCom IP address stored in the database
<br style="clear:both;" />
[[Image:PhoneAppServerStartConnected.JPG|thumb|600px|PhoneAppServer Connected to AlphaCom]]
* Store a valid AlphaCom IP address and restart the application. The PhoneApplicationServer should now connect to the AlphaCom, and discover all nodes in the AlphaNet:<br> 
<br style="clear:both;" />

=== Installing the Cisco Services Web Application ===


* Run the latest AlphaComCiscoServicesSetup.msi installer. If .NET 3.5 not already installed the installer will prompt for download and installation of the .NET framework.
* The Web Application AlphaComCiscoServices will be installed under the wwwroot folder (default location: C:\Inetpub\wwwroot\AlphaComCiscoServices)
<br style="clear:both;" />
[[Image:WebServiceInvalidDBUser.JPG|thumb|600px|User ASPNET Do not have access to the AlphaComStateDB]]
* Test the installed Cisco Service by accessing the URL from a standard Web-browser: [http://localhost/AlphaComCiscoServices/services.aspx?name=SEPxx http://localhost/AlphaComCiscoServices/services.aspx?name=SEPxx]<br/>The URL parameter ?name=SEPxx is is in the format the Cisco phone uses to identify itself. xx will be replaced with the mac address of the Cisco Phone. A fault message something like in picture to right should be returned in the Web browser window.
* Add the IIS user '''ASPNET''' to the AlphaComStateDB. 
** Start the '''SQL Server Management Studio'''. 
** Connect to the local Database engine using standard Windows Authentication.
<br style="clear:both;" />
[[Image:MSSQLDBNewASPNETUser.JPG|thumb|600px|New Database Login ASPNET ]]
** Expand '''Security''', '''Login'''. Right Click and select '''New Login..". Give a new name like '''WebService''', Click Search  Add object Name '''ASPNET''' (use Check Names)
<br style="clear:both;" />
[[Image:MSSQLDBASPNETUserMapping.JPG|thumb|600px|Give user ASPNET read right the AlphaComStateDB]]
** Select User Mapping, select AlphaComStateDB and assign memberships '''db_datareader''' and '''db_datawriter'''.
<br style="clear:both;" />
[[Image:WebServiceOK.JPG|thumb|600px|The Cisco XML page returned ]]
** Retest the Web Service. Note the returned document is in Cisco XML format. IE will just remove the XML tahs an prin all the text. Other browser might print all the XML. See also the source code of the document.
** Note! The Phone ID used for testing will be add to the table '''SipPhones''' in the '''AlphaComStateDB'''. The entry can be deleted by using the '''SQL Server Management Studio'''.

=== Configuring the External Data Location for each Cisco Phone ===

[[Image:ConfigWebServiceinCCM.JPG|thumb|600px|Configuring the URL of the Cisco Phones in the CCM admin ]]
* Use the Cisco Unified CM Adminstration tool to configure the Cisco Phones