[asterisk-bugs] [JIRA] (ASTERISK-22417) RTP ports left open after using click to dial application

Michael L. Young (JIRA) noreply at issues.asterisk.org
Wed Aug 28 11:19:03 CDT 2013


    [ https://issues.asterisk.org/jira/browse/ASTERISK-22417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209700#comment-209700 ] 

Michael L. Young commented on ASTERISK-22417:
---------------------------------------------

Not sure yet what would be causing this.  But a few observations.

Out of curiosity, can you fix this:
{noformat}
[Aug 28 13:29:04] VERBOSE[468][C-00000003] pbx.c:     -- Executing [s at macro-outDialRecord:6] MixMonitor("SIP/290-00000004", "/data/callRecording/Outgoing/00441142994032-07845552273-2013-08-28-13-29-04.WAV,bw(-4)v(-4)") in new stack
{noformat}

Change the lowercase w to an uppercase W for the options to MixMonitor.

You are running Asterisk in a virtual machine?

Also, noticed this in your logs:

{noformat}
[Aug 28 13:29:09] WARNING[430] asterisk.c: The canary is no more.  He has ceased to be!  He's expired and gone to meet his maker!  He's a stiff!  Bereft of life, he rests in peace.  His metabolic processes are now history!  He's off the twig!  He's kicked the bucket.  He's shuffled off his mortal coil, run down the curtain, and joined the bleeding choir invisible!!  THIS is an EX-CANARY.  (Reducing priority)
{noformat}

Some info on astcanary:
{quote}
This process serves a similar purpose, though with the realtime priority being the reason. When a thread starts running away with the processor, it is typically difficult to tell what thread caused the problem, as the machine acts as if it is locked up (in fact, what has happened is that Asterisk runs at a higher priority than even the login shell, so the runaway thread hogs all available CPU time.

If that happens, this canary process will cease to get any process time, which we can monitor with a realtime thread in Asterisk. Should that happen, that monitoring thread may take immediate action to slow down Asterisk to regular priority, thus allowing an administrator to login to the system and restart Asterisk or perhaps take another course of action (such as retrieving a backtrace to let the developers know what precisely went wrong).
{quote}

                
> RTP ports left open after using click to dial application
> ---------------------------------------------------------
>
>                 Key: ASTERISK-22417
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22417
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 11.4.0
>         Environment: Linux 3.2.0-40-virtual #64-Ubuntu SMP i686 i686 i386 GNU/Linux, Ubuntu 12.04
>            Reporter: Patrick Beaumont
>
> Ports in use at the start
> {noformat}
> root at CN1:~# netstat -tunap
> Active Internet connections (servers and established)
> Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
> tcp        0      0 0.0.0.0:5038            0.0.0.0:*               LISTEN      428/asterisk    
> tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      313/lighttpd    
> tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      129/sshd        
> tcp        0      0 10.0.3.101:22           10.0.3.1:60572          ESTABLISHED 339/sshd: steve [pr
> tcp6       0      0 :::22                   :::*                    LISTEN      129/sshd        
> udp        0      0 0.0.0.0:30000           0.0.0.0:*                           428/asterisk    
> udp        0      0 10.0.3.101:30001        0.0.0.0:*                           428/asterisk
> {noformat}
> First I initiate a call using dialer.exe through the application Siptapi.
> My desk phone rings.
> I pick it up.
> My mobile phone then rings (the destination I set in dialer.exe).
> I answer on my mobile phone.
> I place the call on hold using my desk phone.
> I initiate another call to my mobile using dialer.exe through the application Siptapi.
> My desk phone indicates I have a call waiting.
> I hang up the call I have on hold and my desk phone starts ringing.
> I pick up my desk phone and my mobile phone starts ringing.
> I answer the call on my mobile.
> I hang up the call on my mobile.
> I hang up my desk phone.
> Ports in use at the end:
> {noformat}
> root at CN1:~# netstat -tunap
> Active Internet connections (servers and established)
> Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
> tcp        0      0 0.0.0.0:5038            0.0.0.0:*               LISTEN      428/asterisk    
> tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      313/lighttpd    
> tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      129/sshd        
> tcp        0      0 10.0.3.101:22           10.0.3.1:60572          ESTABLISHED 339/sshd: steve [pr
> tcp6       0      0 :::22                   :::*                    LISTEN      129/sshd        
> udp        0      0 0.0.0.0:30000           0.0.0.0:*                           428/asterisk    
> udp        0      0 10.0.3.101:30001        0.0.0.0:*                           428/asterisk    
> udp        0      0 10.0.3.101:30034        0.0.0.0:*                           428/asterisk    
> udp        0      0 10.0.3.101:30035        0.0.0.0:*                           428/asterisk  
> {noformat}
> This is very repeatable and if performed enough times Asterisk will complain about no longing being able to allocate RTP ports and will start rejecting calls.
> Performing a core restart appears to be the only way to release the ports.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list