<![CDATA[Fake Continuous Call Showing]]>So I dialed *720, and *730 yesterday in attempt to get "call forwarding all prompt" to work, where you can set call forwarding for a remote extension other than your own. I later found out that freepbx and/or asterisk changed it to *93, as the 0 in *720 was causing issues.

Anyway, I now am showing to my employees as continually on a call (see attachment). I restarted FOP2 and Asterisk.

Any ideas?

]]>http://localhost:4567/topic/2015/fake-continuous-call-showingRSS for NodeTue, 27 Oct 2026 04:21:20 GMTFri, 14 Aug 2015 17:43:41 GMT60<![CDATA[Reply to Fake Continuous Call Showing on Thu, 21 Nov 2019 07:13:18 GMT]]>I've caught this bug. When released by another channel

]]>http://localhost:4567/post/8862http://localhost:4567/post/8862Thu, 21 Nov 2019 07:13:18 GMT<![CDATA[Reply to Fake Continuous Call Showing on Fri, 13 Jul 2018 17:52:01 GMT]]>I know this is an old post, but I am also running into this issue on 2.31.17 on freepbx. Haven't run into this issue before.

]]>http://localhost:4567/post/8861http://localhost:4567/post/8861Fri, 13 Jul 2018 17:52:01 GMT<![CDATA[Reply to Fake Continuous Call Showing on Fri, 04 Sep 2015 21:16:06 GMT]]>I also have such problem on all my installations.

]]>http://localhost:4567/post/8860http://localhost:4567/post/8860Fri, 04 Sep 2015 21:16:06 GMT<![CDATA[Reply to Fake Continuous Call Showing on Thu, 03 Sep 2015 19:53:23 GMT]]>What I need in order to track this kind of issues is some way to reproduce the issue. The mention of a user trying to forward seems to indicate it might be a problem when a specific feature code is being dialed. If you can tell me that dialing for example *781231231 will lead to a "stuck" call then that is great as the problem is reproducible and we can track log files in order to see why it happens, and if its a bug, fix it.

Calls stuck in a 'random' fashion are not really helpful in order to track the issue down. The idea is to reduce the randomness as much as possible and try to force/trigger the problem so we can catch the error in the act.

Restarting fop2 will always help, as it will clear all internal status and poll information fresh from Asterisk.

If anyone of you have a particular scenario where a call gets stuck or some misinformation displayed in FOP2, please let me know so I can try to reproduce that and fix it.

]]>http://localhost:4567/post/8859http://localhost:4567/post/8859Thu, 03 Sep 2015 19:53:23 GMT<![CDATA[Reply to Fake Continuous Call Showing on Thu, 03 Sep 2015 19:53:06 GMT]]>What I need in order to track this kind of issues is some way to reproduce the issue. The mention of a user trying to forward seems to indicate it might be a problem when a specific feature code is being dialed. If you can tell me that dialing for example *781231231 will lead to a "stuck" call then that is great as the problem is reproducible and we can track log files in order to see why it happens, and if its a bug, fix it.

Calls stuck in a 'random' fashion are not really helpful in order to track the issue down. The idea is to reduce the randomness as much as possible and try to force/trigger the problem so we can catch the error in the act.

Restarting fop2 will always help, as it will clear all internal status and poll information fresh from Asterisk.

If anyone of you have a particular scenario where a call gets stuck or some misinformation displayed in FOP2, please let me know so I can try to reproduce that and fix it.

]]>http://localhost:4567/post/8858http://localhost:4567/post/8858Thu, 03 Sep 2015 19:53:06 GMT<![CDATA[Reply to Fake Continuous Call Showing on Wed, 02 Sep 2015 19:54:05 GMT]]>I've seen this same issue with two installs. At one, conferences intermittently get "stuck" as in use when they are not. At the other it was, coincidentally, a user trying to forward their phone and the extension got stuck as "in use" in FOP2. Always, a 'service fop2 restart' fixes it. Running 2.29.02 in both locations where this has happened.

]]>http://localhost:4567/post/8857http://localhost:4567/post/8857Wed, 02 Sep 2015 19:54:05 GMT<![CDATA[Reply to Fake Continuous Call Showing on Fri, 28 Aug 2015 12:16:30 GMT]]>Yes. It is different. A reload re-reads configurations files only. It does not reset status.

Best regards,

]]>http://localhost:4567/post/8856http://localhost:4567/post/8856Fri, 28 Aug 2015 12:16:30 GMT<![CDATA[Reply to Fake Continuous Call Showing on Fri, 28 Aug 2015 00:29:37 GMT]]>Goodness, it sure did. The thing is, I did restart it before, but from fop2/admin GUI. Is that different than running the command service fop2 restart?

]]>http://localhost:4567/post/8855http://localhost:4567/post/8855Fri, 28 Aug 2015 00:29:37 GMT<![CDATA[Reply to Fake Continuous Call Showing on Wed, 19 Aug 2015 22:21:02 GMT]]>Did you restart fop2?

service fop2 restart

]]>http://localhost:4567/post/8854http://localhost:4567/post/8854Wed, 19 Aug 2015 22:21:02 GMT<![CDATA[Reply to Fake Continuous Call Showing on Mon, 17 Aug 2015 23:21:54 GMT]]>Call (actually calls now) still going.

]]>http://localhost:4567/post/8853http://localhost:4567/post/8853Mon, 17 Aug 2015 23:21:54 GMT