| Summary: | ASTERISK-21377: After sip reload 80% peers is UNREACHEBLE | ||||
| Reporter: | Badalian Vyacheslav (slavon) | Labels: | |||
| Date Opened: | 2013-04-03 07:52:33 | Date Closed: | 2013-04-26 09:35:40 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | Channels/chan_sip/General | ||
| Versions: | 1.8.21.0 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | Centos 5 + FreePBX | Attachments: | ( 0) full.7.gz | ||
| Description: | 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 | ||||
| Comments: | By: Badalian Vyacheslav (slavon) 2013-04-03 07:53:14.082-0500 Full log with debug By: Badalian Vyacheslav (slavon) 2013-04-03 15:43:27.830-0500 I don't think that this bug is related to ASTERISK-21194, but may be you right... By: Badalian Vyacheslav (slavon) 2013-04-06 08:57:23.267-0500 Every One? Our customers can't work normal... :( By: Rusty Newton (rnewton) 2013-04-10 18:17:56.704-0500 You state this is a regression. 1. What was the last version you used where this behavior *did not* occur? 2. Can you provide a VERBOSE and DEBUG log (level 5) of a sip reload on a previous working version in the 1.8 branch? and then the current non-working version? By: Rusty Newton (rnewton) 2013-04-26 09:35:21.640-0500 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 | ||||