B2B video, Jabber Guest, immersive telepresence endpoints, etc. that they were occasionally working into issues when dialing via SIP URI. It was found out that the entries in MS Active Directory might not have been regularly entered as lower case. Some may have been entered using camel case, and I suppose some may all be uppercase as well. When CUCM synchronized it’s users with Active Directory, those full instances were well known.
Per RFC 3261 (section 19.1.4, URI Comparison) comparison of the userinfo of SIP URIs needs to be case-sensitive. When routing directory site URIs, Unified CM respects this standard and searches for a case-sensitive full match of the user portion and a case-insensitive match of the sponsor portion. To avoid misunderstandings, Cisco highly suggests provisioning only directory URIs with all lowercase userinfo so that directory site URIs can reliably be dialed by entering all lowercase information. Unified CM 9.1 and later produces can be configured to always use case-insensitive assessment of the user-info portion of index URIs.
- General Liability
- Tweet #15: 10 p.m
- Upper-Intermediate Advanced (104)
- Useful for decision making
- The story-telling ability of the author
- After law college, proceeded to go into litigation and hated it, although, it taught him how to attack
- 1 tbsp veggie oil
- To prevent manpower obsolescence in an organisation
This can be achieved by configuring the business parameter URI Lookup Policy accordingly. This setting applies to coordinating locally configured listing URIs and to matching index URIs for which an ILS lookup is done. …