<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Remote login ok but actions not working]]></title><description><![CDATA[<p dir="auto">Hi, I have tested a system on a remote network that logs in properly but is unable to dial, etc.  Does 4445 need to be  opened on the client network?</p>
<p dir="auto">Thanks</p>
]]></description><link>http://localhost:4567/topic/892/remote-login-ok-but-actions-not-working</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 14:25:42 GMT</lastBuildDate><atom:link href="http://localhost:4567/topic/892.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 19 Sep 2011 12:25:57 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Remote login ok but actions not working on Tue, 20 Sep 2011 01:11:29 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">If you can login to fop2, then the port is open. Performing actions in FOP2 once logged is not related to having the port open or closed. It might be related to fop2 user permissions, manager permissions, or unreachable sip peer as seen by asterisk.</p>
<p dir="auto">Best regards,</p>
]]></description><link>http://localhost:4567/post/3967</link><guid isPermaLink="true">http://localhost:4567/post/3967</guid><dc:creator><![CDATA[nicolas]]></dc:creator><pubDate>Tue, 20 Sep 2011 01:11:29 GMT</pubDate></item></channel></rss>