Open Source Training Seminar FreePBX Paid Support

Ticket #2741 (closed Bugs: invalid)

Opened 6 months ago

Last modified 1 month ago

firstnotonphone - failing if 'call forward busy' activated on the primary extension

Reported by: compused Assigned to: p_lindheimer
Priority: minor Milestone: 2.5
Component: Follow Me Version: 2.3.0
Keywords: firstnotonphone Cc:
Confirmation: Confirmed SVN Revision (if applicable):
Backend Engine: Asterisk 1.2.x Backend Engine Version:

Description (Last modified by lazytt)

I found 'call forward busy' had been inadvertently activated on the primary extension ie extension 2003 (someone must have pressed *90 instead of *97 when checking voicemail)

So instead of the call going to the 2nd listed extension (extension 2001) in the follow-me (set up as 'firstnotonphone'), it went to the 'destination if no answer'.

The CLI was repeatedly displaying (ie overloaded and the HDD sounded overloaded): 

== Spawn extension (macro-hangupcall, s, 11) exited non-zero on 'Local/2003@from-internal-edcf,2' in macro 'hangupcall'
  == Spawn extension (macro-hangupcall, s, 11) exited non-zero on 'Local/2003@from-internal-edcf,2'
    -- Executing NoCDR("Local/2003@from-internal-1406,2", "") in new stack
    -- Executing GotoIf("Local/2003@from-internal-1406,2", "1?skiprg") in new stack
    -- Goto (macro-hangupcall,s,6)
    -- Executing GotoIf("Local/2003@from-internal-1406,2", "1?skipblkvm") in new stack
    -- Goto (macro-hangupcall,s,9)
    -- Executing GotoIf("Local/2003@from-internal-1406,2", "1?theend") in new stack
    -- Goto (macro-hangupcall,s,11)
    -- Executing Hangup("Local/2003@from-internal-1406,2", "") in new stack

Versions: -freepbx 2.3.0.3 -asterisk 1.2.13 admittedly not the latest

For more details (are 3 posts): http://freepbx.org/forum/freepbx/installation/report-firstnotonphone-not-working-with-zaptel-fxs-but-ok-with-sip

Thanks Michael

Change History

07/01/08 15:40:56 changed by lazytt

  • description changed.

07/25/08 20:09:40 changed by p_lindheimer

  • status changed from new to closed.
  • confirmation changed from Unreviewed to Confirmed.
  • resolution set to invalid.
  • milestone changed from Cut Line to 2.5.

the issue from reviewing this is that the user did a CF to themselves, which probably should not be allowed. So from what I an tell, this is invalid and a bug needs to be filed that a user should either not be able to CF to themselves, or if they do, that we basically ignore it vs. this issue. Please file a new ticket on that, thanks.

Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads