Summary:	ASTERISK-16733: SIP Channel config will not reload if Name is only different by CaSe
Reporter:	Craig Arno (craigarno)	Labels:
Date Opened:	2010-09-26 01:08:34	Date Closed:	2012-02-02 17:53:23.000-0600
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_sip/Registration
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	I named one SIP channel [office1], then performed a CLI> reload sip.  A CLI> sip show peer office1 showed the sip.conf description loaded and my Sipura 2100 registered... Then I decided I liked uppercase better, so I renamed the sip.conf entry to [OFFICE1], then performed a reload sip.  A CLI> sip show peer OFFICE1 said OFFICE1 couldn't be found.  An attempt to register a Sipura 2100 using OFFICE1 also failed. After shutting down Asterisk CLI> core stop now then restarting asterisk, the Sipura 2100 was able to register using OFFICE1. It appears that a case -insensitive- compare was performed on "office1" to "OFFICE1" and the result was the new sip.conf entry was not loaded.  Shutting down Asterisk made Asterisk forget the old "office1" entry and after sip.conf was fully loaded, the new configuration worked with OFFICE1. ****** ADDITIONAL INFORMATION ****** I consider this bug pretty minor, but it was confusing as all get out until I figured this little ditty out. Otherwise 1.8-rc2 is running better than any previous version I've tried.
Comments:	By: Leif Madsen (lmadsen) 2010-09-28 10:42:07 I know I triaged an issue just like this one the other day and I wanted to mark them as duplicates (or at least related) but I simply can't find the other issue anywhere in the bug tracker. Perhaps it got fixed already? Can you try the 1.8 branch directly and see if it still has the same issue? If so we'll leave this issue open. Thanks! By: Mark Michelson (mmichelson) 2012-02-02 17:53:23.959-0600 I have verified both that this problem existed in 1.8.0-rc2 and that it is fixed in the tip of the 1.8 branch. Closing.