Fusion Intercom is not discovered by other Axia Intercom panels

Prev Next

SCOPE

This document applies to Axia Intercom panels that are installed in a Fusion or Element console. Other Axia Intercom panels, like the rack mount or desktop models are not covered here.

DESCRIPTION

Axia Intercom panels are not showing as an available choice in other Intercom Panels.

Assuming the Axia Intercom has been properly configured in your console configuration there are only a couple of possible issues.

ISSUE 1

All Axia Intercom panels (mounted in a console or not) use mDNS (multicast DNS) to advertise themselves. mDNS is the implementation of Apple's Bounjour protocol and is intended to provide a zero configuration experience.  

Some version of Cisco software are incorrectly blocking mDNS when the "switchport block multicast" setting is applied to ports on your network switch. Many of our documents regarding proper configuration of your switches for use with Livewire suggest the addition of that setting. Normally, it would prevent any unmanaged multicast from reaching the port, but in some cases it's having the effect of blocking some stuff we want to be sent.  This setting can be safely removed from the port. You can remove it from ALL ports, however, if desired, you can just remove it from any ports requiring mDSN (like Intercom ports).

ISSUE 2

In some RARE cases, the mDNS service in the "in console" intercoms will appear to stop advertising. This can often be remedied by restarting the console. In cases where this is not practical a more advanced method is to manually kill and then restart the Intercom service in the console.

NOTE. This requires root level access to the console engine. User accepts all responsibility for accessing the console in this way. We would prefer not to share this information about root access but this is YOUR equipment. Keep in mind that any damage done by accessing the console in this manner is considered damage. You will be charged for any repair or reconfiguration as a result of this. Heed this warning and know that you are proceeding at your own risk.

  1. Using PuTTy or other Telnet program, connect to your engine on telnet port 93

  2. log in as "root" user with a password of 1q2w3e4r

  3. From the prompt, type the command;

# killall -9 axiaicomd

You will not receive a message back if the service is killed properly.

  1. From the prompt, restart the Intercom service by typing the following command;

# /usr/sbin/Axia/axiaicomd

If the service starts properly you should receive a command back that looks similar to this.

icomd Tue Aug  2 17:44:54 EEST 2016
  1. Check your config and see if your intercoms are now being advertised properly.