[asterisk-bugs] [JIRA] (ASTERISK-21377) After sip reload 80% peers is UNREACHEBLE

Rusty Newton (JIRA) noreply at issues.asterisk.org
Fri Apr 26 09:35:38 CDT 2013


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

Rusty Newton commented on ASTERISK-21377:
-----------------------------------------

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.  Further information can be found at http://www.asterisk.org/developers/bug-guidelines


                
> After sip reload 80% peers is UNREACHEBLE
> -----------------------------------------
>
>                 Key: ASTERISK-21377
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21377
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 1.8.21.0
>         Environment: Centos 5 + FreePBX
>            Reporter: Badalian Vyacheslav
>            Assignee: Rusty Newton
>         Attachments: full.7.gz
>
>
> Full debug is attached 
> in all peers 
> quantify=5000
> Its regression. Before "sip reload" does not break peers connect.
> I do:
> # logger rotate
> # core set verbose 3
> # core set debug 3
> # sip reload
> // wait 15-30 sec... in this time 80% of peers is UNREACHEBLE and then is Reacheble
> // after is Reacheble i do:
> # core set debug off
> # logger rotate

--
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