On Tue, Jul 31, 2012 at 8:58 AM, Kumaran <thiru.venkateshwa...@ttplservices.com> wrote: > On 7/31/2012 5:54 PM, Mircea Carasel wrote: > > > > On Tue, Jul 31, 2012 at 3:20 PM, Mircea Carasel <mirc...@ezuce.com> wrote: >> >> >> On Tue, Jul 31, 2012 at 3:15 PM, Kumaran >> <thiru.venkateshwa...@ttplservices.com> wrote: >>> >>> Hi All, >>> If I enable firewall I can login to user IM client(issue fixed >>> XX-10335) but openfire console is not opening(The connection has timed >>> out).... >> >> Openfire console runs on port 9094 (non secure) or 9095 (secure) - these >> two should be added as firewall rules, IMO >> Please open a ticket. You can assign to me > > Not quite, we have a firewall rule for port 9094 - this is the XML-RPC port > as well, please go to Firewall page and mark XMPP xml RPC public, and you > will have port 9094 opened > mircea >> >> mircea >> >> There is no service with XMPP xml RPC but IM xml RPC is present,once I >> changed to Public from Cluster then I can access openfire console...But I >> also can access openfire console even after changing IM xml RPC from public >> to cluster.....
takes a few seconds, you sure? can you send along /etc/sysconfig/iptables file and screenshot of firewalls page? _______________________________________________ sipx-dev mailing list sipx-dev@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-dev/
