Ticket #5379 (closed Bugs: wontfix)

Opened 2 years ago

Last modified 1 year ago

multiple calls to hangup()

Reported by: obelisk Assigned to: p_lindheimer
Priority: minor Milestone: 2.11
Component: Core Version: 2.9-branch
Keywords: h Cc:
Confirmation: Unreviewed Distro:
Backend Engine: All Distro Ver:
Backend Ver: SVN Revision (if applicable):

Description

As the title says, hangup() is called multiple times for no reason.

An example: Calling *97 and pressing # to end the call produces this: 

    -- Executing [*97@from-internal:107] GotoIf("SIP/123-00000000", "0?playret") in new stack
    -- Executing [*97@from-internal:108] Macro("SIP/123-00000000", "hangupcall,") in new stack
    -- Executing [s@macro-hangupcall:1] GotoIf("SIP/123-00000000", "1?theend") in new stack
    -- Goto (macro-hangupcall,s,3)
    -- Executing [s@macro-hangupcall:3] Hangup("SIP/123-00000000", "") in new stack
  == Spawn extension (macro-hangupcall, s, 3) exited non-zero on 'SIP/123-00000000' in macro 'hangupcall'
  == Spawn extension (from-internal, *97, 108) exited non-zero on 'SIP/123-00000000'
    -- Executing [h@from-internal:1] Hangup("SIP/123-00000000", "") in new stack
  == Spawn extension (from-internal, h, 1) exited non-zero on 'SIP/123-00000000'

Somebody should also look at the output from 

dialplan show h@from-internal
dialplan show h@ext-did-catchall

as this also generates double Hangup()

Change History

06/14/12 14:44:27 changed by p_lindheimer

  • status changed from new to closed.
  • resolution set to wontfix.
  • milestone changed from Undetermined to 2.11.

unless there is a side affect to this that I am not aware of, there is no harm in having hangup called more than one. If there are consequences to this, please let us know and we can revisit.