Technical Helpweb

Dialogic® PowerMedia™ Extended Media Server (PowerMedia XMS) - more articles

Unable to Connect to PowerMedia XMS WebAdmin or to connect REST Client

Symptom:  

On Dialogic® PowerMedia™ Extended Media Server (XMS), attempting to connect to the Web Admin or REST service times out.  

Reason for the issue:

The web services on the PowerMedia XMS system are not started or properly configured.   

Fix:

A simple fix is to reinstall PowerMedia XMS using the ISO image, as this will have the firewall (iptables) and the services correctly configured.

However, if you are using the rpm install process you will need to manually check that the firewall and services are correctly configured as described below.

Step 1:

Check that the iptables configuration has rules to allow packets for the web port (default:80) as well as the REST port (default:81)

Here is an example iptables configuration:

# Firewall configuration written by system-config-firewall

# Manual customization of this file is not recommended.

*filter

:INPUT ACCEPT [0:0]

:FORWARD ACCEPT [0:0]

:OUTPUT ACCEPT [0:0]

-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT

-A INPUT -p icmp -j ACCEPT-A INPUT -i lo -j ACCEPT

-A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT

-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT

-A INPUT -m state --state NEW -m tcp -p tcp --dport 15001 -j ACCEPT

-A INPUT -m state --state NEW -m udp -p udp --dport 49152:53152 -j ACCEPT

-A INPUT -m state --state NEW -m udp -p udp --dport 57344:57840 -j ACCEPT

-A INPUT -m state --state NEW -m udp -p udp --dport 5060 -j ACCEPT

-A INPUT -m state --state NEW -m tcp -p tcp --dport 5060 -j ACCEPT

-A INPUT -m state --state NEW -m tcp -p tcp --dport 81 -j ACCEPT

-A INPUT -m state --state NEW -m tcp -p tcp --dport 443 -j ACCEPT

-A INPUT -m state --state NEW -m tcp -p tcp --dport 10443 -j ACCEPT

-A INPUT -m state --state NEW -m tcp -p tcp --dport 1080 -j ACCEPT

-A INPUT -j REJECT --reject-with icmp-host-prohibited-A FORWARD -j REJECT --reject-with icmp-host-prohibited

COMMIT

For more information on using iptables on CentOS, please consult the CentOS documentation.

Step 2:

Check that the httpd and lighttpd web services are installed and started, and are automatically set to start on reboot.

To check that the services are installed, search for the packages:

 [root@xms xms]# rpm -qa | grep httpd

If both the httpd and lighttpd packages are installed, you should see a result similar to this:

[root@xms xms]# rpm -qa | grep 

httpdlighttpd-1.4.28-3.el6.x86_64

httpd-tools-2.2.15-15.el6.centos.x86_64

lighttpd-fastcgi-1.4.28-3.el6.x86_64

httpd-2.2.15-15.el6.centos.x86_64

These packages should have been installed as part of the XMS rpm install. If they are not present, please reinstall the XMS rpm.

To check that the services are started, run the following commands:

[root@xms xms]# service httpd status

httpd (pid  4218) is running...

[root@xms xms]# service lighttpd status

lighttpd (pid 4231) is running...

If these services are not running, you can restart them by calling:

[root@xms xms]# service httpd start

Starting httpd:                                            [  OK  ]

To check that the services are set to automatically start on reboot, use the chkconfig command:

chkconfig --list httpd

chkconfig --list lighttpd

You should see something like this:

httpd           0:off   1:off   2:on    3:on    4:on    5:on    6:off

If these are all set to off, enable the services to start by default by running these commands:

 chkconfig lighttpd on

 chkconfig httpd on

 <open source disc>

Legal Note

This document discusses one or more open source products, systems and/or releases. Dialogic is not responsible for your decision to use open source in connection with Dialogic products (including without limitation those referred to herein), nor is Dialogic responsible for any present or future effects such usage might have, including without limitation effects on your products, your business, or your intellectual property rights