| Summary: | ASTERISK-00213: New IAX peers are not qualified until complete Asterisk restart | ||
| Reporter: | John Todd (jtodd) | Labels: | |
| Date Opened: | 2003-09-03 14:01:06 | Date Closed: | 2008-01-15 14:33:47.000-0600 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Adding new IAX peers with a qualify= statement are not "seen" and qualified as valid until Asterisk is halted and restarted, though they show in the "show iax peers" list. ****** ADDITIONAL INFORMATION ****** I added a few peers to my server the other night to handle some failover conditions that I was seeing. A "reload" showed them correctly in the "show iax peers" list, but they were status "UNKNOWN" despite their being online and active. After some serious head scratching and packet dumps, I did a "stop now" and restarted Asterisk, at which point they became active. This is a minor issue, but might be more important at some time in the future when IAX peers are dynamically added/removed on running servers. | ||
| Comments: | By: Mark Spencer (markster) 2003-09-03 23:15:15 Fixed in CVS By: Digium Subversion (svnbot) 2008-01-15 14:33:47.000-0600 Repository: asterisk Revision: 1470 U trunk/channels/chan_iax2.c ------------------------------------------------------------------------ r1470 | markster | 2008-01-15 14:33:47 -0600 (Tue, 15 Jan 2008) | 2 lines Re-poke all peers on a reload (bug ASTERISK-213) ------------------------------------------------------------------------ http://svn.digium.com/view/asterisk?view=rev&revision=1470 | ||