Using GenieACS

Matthew Forbes m.forbes at
Thu Jan 17 16:39:00 EST 2019

Thank you for your response.  The client we are using has the URL for the ACS with the port number as well which is as you say, 7547.  If the port was blocked we would not be able to communicate at all, but we do connect on reboot of the client.  The client and server are physically on the same network so again the port doesn't appear to be blocked.  I am thinking there may be a way to make a connection request to the device so the device will connect rather than waiting for a reboot and then the commands will go through.
Thanks again, Matt

-----Original Message-----
From: Users <users-bounces at> On Behalf Of Oliver Kraitschy
Sent: Thursday, January 17, 2019 2:28 PM
To: Community support for GenieACS users <users at>
Subject: Re: Using GenieACS

CableLabs WARNING: The sender of this email could not be validated and may not match the person in the "From" field.

Hi Matt,

On Thu, Jan 17, 2019 at 07:41:00PM +0000, Matthew Forbes wrote:
> We are using genieacs in our lab and we are having an issue.  When we 
> send commands to the device and
> it does not respond and the commands are put into a que on the ACS.  
> Upon reboot the commands are initiated on the device.  I know you can 
> push changes to a device immediately, but I don't seem to be able to 
> find a way to set that up.  The ACS and device are on an isolated 
> network so there shouldn't be anything blocking the messages.  Also, 
> if possible we would like to change

are you sure that incoming connections on port 7547 are not blocked by a firewall on your device? For a connection request, port 7547 must be reachable from outside. Otherwise the command is executed on the next inform.

Users mailing list
Users at

More information about the Users mailing list