Howto:Use LinuxAP Webdav Server in Redundancy Scenarios: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
No edit summary
Line 4: Line 4:
All innovaphone devices with Linux Application Platform installed with redundancy.
All innovaphone devices with Linux Application Platform installed with redundancy.


<!-- Keywords: werkseinstellung, zurücksetzen, factory reset, factory settings, platt machen, auslieferungszustand, clear config  -->
<!-- Keywords: cd card karte -->


==More Information==
==More Information==


===Problem Details===
===Problem Details===
When we install the Linux AP platform on the innovaphone IPXX10 Gateway, the webdav folder it's hosted in the Linux AP and for that reason it's no longer possible to use the loopback IP address (127.0.0.1) when setting the URL on the innovaphone PBX  objects for the announcements,voicemail scripts,etc.
When we install the Linux AP platform on the innovaphone IPxx10 Gateway, the CF card will be used by the Linux AP, not the gateway itself any more. Therefore, the webdav folder is hosted in the Linux AP and for that reason it's no longer possible to use the loopback IP address (127.0.0.1) when setting the URL on the innovaphone PBX  objects for the announcements, voicemail scripts, etc. Instead, it's necessary to use the IP address of the Linux AP to reach the webdav folder.
Instead it's necessary to set the IP address of the Linux AP to reach the webdav folder.


In a Master-Standby scenario for redundancy were Linux AP it's installed on both Master and Standby Gateway it's necessary to set an URL on the PBX Objects that works in both Gateways so when the Master fails the Standby still plays the announcements correctly for example.
The Voicemail Object features a ''backup URL'', however the ''Waiting Queue'', ''Message Waiting'', ''Boolean'' Objects don't. In a Master-Standby scenario for redundancy where the Linux AP is installed on both Master and Standby Gateway it's necessary to use an URL on the PBX Objects that works in both Gateways. So when the Master fails the Standby e.g. still plays the announcements correctly.
 
The Voicemail Object contains backup URL, what solve the problem by setting the Standby Linux AP IP address in the backup URL however the Waiting Queue Object,Message Waiting Object, Boolean Object don't contain any Backup URL option.
 
So it's necessary that when Standby replaces Master PBX, the Stanby PBX it's able to reach the Webdav folder of Standby Linux AP using the same PBX Objects.


===Resolution===
===Resolution===
The solution suggested in this scenario is to define an additional IP address on both Linux AP's (Master-Standby) ethernet interface that are identical and then set a static route on the innovaphone Gateway so the PBX is able to reach this IP address and afterwards use this IP address for the webdav URL inside the PBX.


The solution suggested in this scenario it's to define an additional IP address on both Linux AP (Master-Standby) that are identical. Do a static route on the innovaphone Gateway so the PBX it's able to reach this IP address and afterwards use this IP address for the webdav URL inside the PBX.
Since both devices now have the same additional IP address configured on the Linux AP, the URL will also work on the Standby Linux AP.
 
Since both devices have the same internal IP address configured on the Linux AP, when Standby takes charge the URL will also work on the Standby Linux AP, simulating a "loopback" Ip address for the Linux AP.




'''1) Set the Additional IP on the Linux AP using ssh (ex. Putty), do the same procedure in both Linux AP (Master/Standby):'''
'''1) Set the Additional IP on the Linux AP using ssh (ex. Putty), do the same procedure in both Linux AP (Master/Standby):'''


** Edit the interfaces file -> vi /etc/network/interfaces
* Edit the interfaces file -> <code>vi /etc/network/interfaces</code>
** Add the additional IP eth0:0, you are free to setup the address you wish that doesn't conflict with the existing networks.
* Add the additional IP eth0:0, you are free to setup the address you wish that doesn't conflict with the existing networks


[[Image:Linux_Webdav_Redundancy_1.png]]
[[Image:Linux_Webdav_Redundancy_1.png]]
Line 35: Line 29:
'''2) Add static route to the ETH2 in the innovaphone Gateway config:'''
'''2) Add static route to the ETH2 in the innovaphone Gateway config:'''


At Master:
* On the Master: <code>http://x.x.x.x/!config add IP0 ETH2 /rt 192.192.192.192:255.255.255.255:172.16.3.149</code>
http://x.x.x.x/!config add IP0 ETH2 /rt 192.192.192.192:255.255.255.255:172.16.3.149
* On Slave: <code>http://x.x.x.x/!config add IP0 ETH2 /rt 192.192.192.192:255.255.255.255:172.16.3.150</code>
At Slave:
http://x.x.x.x/!config add IP0 ETH2 /rt 192.192.192.192:255.255.255.255:172.16.3.150


Note: At this example .149 it's the IP address of Master Linux AP and .150 it's the IP address of Standby Linux AP.
Note: In this example, <code>172.16.3.149</<code> is the real IP address of the Master Linux AP and <code>172.16.3.150</code> is the real IP address of Standby Linux AP. <code>192.192.192.192</code> is used as additional IP address on both Linux APs. Instead of <code>192.192.192.192</code> ypu could use any other private network IP address that is not used in your own network.




Line 47: Line 39:
[[Image:Linux_Webdav_Redundancy_2.png]]
[[Image:Linux_Webdav_Redundancy_2.png]]


===Known Problems===
<!-- ===Known Problems=== -->


[[Category:Howto|{{PAGENAME}}]]
[[Category:Howto|{{PAGENAME}}]]

Revision as of 10:26, 22 August 2014

Applies To

This information applies to

All innovaphone devices with Linux Application Platform installed with redundancy.


More Information

Problem Details

When we install the Linux AP platform on the innovaphone IPxx10 Gateway, the CF card will be used by the Linux AP, not the gateway itself any more. Therefore, the webdav folder is hosted in the Linux AP and for that reason it's no longer possible to use the loopback IP address (127.0.0.1) when setting the URL on the innovaphone PBX objects for the announcements, voicemail scripts, etc. Instead, it's necessary to use the IP address of the Linux AP to reach the webdav folder.

The Voicemail Object features a backup URL, however the Waiting Queue, Message Waiting, Boolean Objects don't. In a Master-Standby scenario for redundancy where the Linux AP is installed on both Master and Standby Gateway it's necessary to use an URL on the PBX Objects that works in both Gateways. So when the Master fails the Standby e.g. still plays the announcements correctly.

Resolution

The solution suggested in this scenario is to define an additional IP address on both Linux AP's (Master-Standby) ethernet interface that are identical and then set a static route on the innovaphone Gateway so the PBX is able to reach this IP address and afterwards use this IP address for the webdav URL inside the PBX.

Since both devices now have the same additional IP address configured on the Linux AP, the URL will also work on the Standby Linux AP.


1) Set the Additional IP on the Linux AP using ssh (ex. Putty), do the same procedure in both Linux AP (Master/Standby):

  • Edit the interfaces file -> vi /etc/network/interfaces
  • Add the additional IP eth0:0, you are free to setup the address you wish that doesn't conflict with the existing networks


2) Add static route to the ETH2 in the innovaphone Gateway config:

  • On the Master: http://x.x.x.x/!config add IP0 ETH2 /rt 192.192.192.192:255.255.255.255:172.16.3.149
  • On Slave: http://x.x.x.x/!config add IP0 ETH2 /rt 192.192.192.192:255.255.255.255:172.16.3.150

Note: In this example, 172.16.3.149 is the real IP address of the Master Linux AP and 172.16.3.150 is the real IP address of Standby Linux AP. 192.192.192.192 is used as additional IP address on both Linux APs. Instead of 192.192.192.192 ypu could use any other private network IP address that is not used in your own network.


3) Configure the HTTP Client Credentials for the new Address at innovaphone Gateway: