Summary:	ASTERISK-13373: Cannot tell which registry item is which when username exceeds 12 characters
Reporter:	nick_lewis (nick_lewis)	Labels:
Date Opened:	2009-01-15 03:41:43.000-0600	Date Closed:	2009-02-02 13:28:30.000-0600
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_sip/Registration
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	The cli command "sip show registry" displays the registration status of sip trunks. If there is more than one sip trunk with the same ITSP and the usernames exceed 12 characters then it is not possible to determine which trunk is registered and which is not. 12 characters is not sufficient for the display of a username. I have customers whose ITSPs supply usernames greater than 12 characters. Real examples are 0001078131495, 0001078131496
Comments:	By: Leif Madsen (lmadsen) 2009-01-15 08:09:43.000-0600 This isn't really a bug, as much as a feature request, which are not accepted on the bug tracker. You'd need to provide code to solve this issue if you wish to keep it open. By: Olle Johansson (oej) 2009-01-15 08:15:05.000-0600 There's a limit on how much we can put in a row too... Maybe with need to implement a "sip show registry xxxx" - the problem is that there's really no unique identifier. By: nick_lewis (nick_lewis) 2009-01-15 08:39:24.000-0600 Ok I will put a varient of the oej patch for 14248 here or at 14247 once tested. Regarding "sip show registry xxxx" I think Exten is either "s" or it is unique so "sip show registry <exten>" could be supported but with an rejection message for "sip show registry s" By: Olle Johansson (oej) 2009-01-15 08:44:15.000-0600 exten is not unique - I have five different registrations that point to the same exten. Two of them with the same service provider. We will have to add a unique identifier if we're going this direction. By: Leif Madsen (lmadsen) 2009-01-20 12:53:52.000-0600 Are we still interested in going down this route? Or do we have a better idea of how to support this? Or are we actually better off with leaving it as is? :) By: Olle Johansson (oej) 2009-01-23 02:28:27.000-0600 There's a patch for this in bug 12248 that I will look at and possibly submit later today in trunk. By: Leif Madsen (lmadsen) 2009-02-02 13:25:26.000-0600 Does this issue still need to be open? I see another issue that creates a new CLI command as well. By: Leif Madsen (lmadsen) 2009-02-02 13:26:02.000-0600 Issue 14248 is the issue I was thinking about. No point in having duplicates open if the patch is somewhere else. By: Olle Johansson (oej) 2009-02-02 13:28:29.000-0600 Closing this as a feature request - Added it to todo in the source code instead - Also mentioned the issue in sip object documentation It doesn't mean that work stops, but it's not considered a bug and thus gets closed.