id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	confirmation	distro	engine	distro_ver	engine_version	svn_rev
5902	Inbound CID is case sensitive, Route CID is not	tlum	p_lindheimer	The vast majority of inbound CIDs will be numbers, however, there are cases where inbound calls will be supplied with an alpha CID string and that string is mixed case.\r\n\r\nRoute CID matching appears to be case sensitive. If you specify a route CID with the string "Private" and a call comes in with a CID "private" it will not match the route.\r\n\r\nAlso, the route names are not case sensitive. If you specify a route with a CID string of "Private" you cannot then specify another route with a CID string of "PrIvAtE" because it is not considered unique.\r\n\r\nThis makes it impossible to form an inbound rule - or rules - that match all forms of "Private", "private", "PRIVATE", "PrIvAtE", etc.\r\n\r\nIt would be helpful to either make them both case sensitive or neither of them case sensitive.	Bugs	new	minor	2.11	Core - Trunks/Routing	2.10-branch				Unreviewed		Asterisk 1.8