<div dir="ltr">While Anthony's encoding is right, I actually think the documentation does intend to actually mean you can act as though the + was not in the phone number value as stored in AD.<div><br></div><div>I have used the query below</div><div><br></div><div><span style="color:rgb(0,0,0);font-family:consolas,menlo,monaco,"lucida console","liberation mono","dejavu sans mono","bitstream vera sans mono","courier new",monospace,serif;font-size:12px;background-color:rgba(0,0,0,0.0470588)">https://{host}:8443/cucm-uds/users?numberlast=3175551234</span><br></div><div><span style="color:rgb(0,0,0);font-family:consolas,menlo,monaco,"lucida console","liberation mono","dejavu sans mono","bitstream vera sans mono","courier new",monospace,serif;font-size:12px;background-color:rgba(0,0,0,0.0470588)"><br></span></div><div>To search for phone numbers in AD. This finds any number with right justified digits above. This should find results for +13175551234, 13175551234, and 3175551234. If there are hypens in the numbers in AD (e.g. 317-555-1234).<span style="color:rgb(0,0,0);font-family:consolas,menlo,monaco,"lucida console","liberation mono","dejavu sans mono","bitstream vera sans mono","courier new",monospace,serif;font-size:12px;background-color:rgba(0,0,0,0.0470588)"><br></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 13, 2017 at 12:16 AM, Anthony Holloway <span dir="ltr"><<a href="mailto:avholloway+cisco-voip@gmail.com" target="_blank">avholloway+cisco-voip@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">No worries. Transitioning to app dev will be a bumpy road for a lot of UC Engineers, we might as well help each other progress forward.</div><div class="HOEnZb"><div class="h5"><br><div class="gmail_quote"><div dir="ltr">On Wed, Apr 12, 2017 at 9:37 PM Nathan Reeves <<a href="mailto:nathan.a.reeves@gmail.com" target="_blank">nathan.a.reeves@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">lol, cheers for that, should have picked that up earlier. Quick test shows that works perfectly.<div><br></div><div>When the docs mention that it ignores the plus symbol, I was working on the assumption that it therefore would ignore the plus symbol in the actual number. Wrong assumption.</div><div><br></div><div>Thanks again</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 12, 2017 at 11:57 PM, Anthony Holloway <span dir="ltr"><<a href="mailto:avholloway+cisco-voip@gmail.com" target="_blank">avholloway+cisco-voip@gmail.<wbr>com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Plus signs (+) in URL query parameters (the part after the question mark [?]) are treated as spaces. E.g., ?name=anthony+holloway == "anthony holloway" So, you're effectively asking UDS for " 61400111111" (note the leading space, and omission of the plus sign [+]).<div><br></div><div>The work around is to use some sort of URL encoding library, which will build your URL with the plus sign (+) encoded with it's percent sign (%) equivelent, which happens to be %2B.</div><div><br></div><div>So, your submitted UDS request would actually look like:</div><div><br></div><div><a href="https://172.20.2.21:8443/cucm-uds/users?number=%2B61400111111" target="_blank">https://172.20.2.21:8443/cucm-<wbr>uds/users?number=%<wbr>2B61400111111</a><br></div><div><br></div><div>Finally, this is not a function of UDS at all, and something you'll need to know, now that you are explorely RESTful APIs which rely on URL structures to work with data.</div></div><br><div class="gmail_quote"><div><div class="m_-8174172989793503157m_-6169971909870482323h5"><div dir="ltr">On Wed, Apr 12, 2017 at 10:46 AM Nathan Reeves <<a href="mailto:nathan.a.reeves@gmail.com" target="_blank">nathan.a.reeves@gmail.com</a>> wrote:<br></div></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="m_-8174172989793503157m_-6169971909870482323h5"><div dir="ltr" class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg">Taking a look around at what options we have to drive additional directories for our IP phones and decided to take a quick look at using UDS as the data source, accessing it via the published API.<div class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg"><br class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg"></div><div class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg">One thing I'm finding (which I can't see any bug report on), is that number searches, where the number in UDS contains a plus, does not return search results based on the query submitted.</div><div class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg"><br class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg"></div><div class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg">I have a user configured with a mobile number in PlusE164 <a href="tel:+61%20400%20111%20111" value="+61400111111" class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg" target="_blank">(+61400111111</a> for example) which is pulled into the CUCM directory via LDAP sync.</div><div class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg"><br class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg"></div><div class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg">The API docs note that brackets, plus symbols etc are all ignored in the search. When I access the UDS API and construct a query string in a URL along the lines of '<a href="https://172.20.2.21:8443/cucm-uds/users?number=61400" class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg" target="_blank">https://172.20.2.21:8443/<wbr>cucm-uds/users?number=61400</a>', the returned response is 0 results. If I update the Mobile number to remove just the plus (and resync LDAP), the same search now returns my user with the mobile number correctly searched.</div><div class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg"><br class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg"></div><div class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg">Running 11.5(1)SU1 (haven't yet checked this against SU2), attempted to use native UDS but also tried searching while UDS Proxy is enabled. Same results either way.</div><div class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg"><br class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg"></div><div class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg">Anyone seen this issue or am I missing something? I can only assume that the sanitized query doesn't correctly ignore the plus symbol.</div><div class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg"><br class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg"></div><div class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg">Cheers</div><div class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg"><br class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg"></div><div class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg">Nathan</div></div></div></div>
______________________________<wbr>_________________<br class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg">
cisco-voip mailing list<br class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg">
<a href="mailto:cisco-voip@puck.nether.net" class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg" target="_blank">cisco-voip@puck.nether.net</a><br class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg">
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg" target="_blank">https://puck.nether.net/<wbr>mailman/listinfo/cisco-voip</a><br class="m_-8174172989793503157m_-6169971909870482323m_6021436004635367630gmail_msg">
</blockquote></div>
</blockquote></div><br></div>
</blockquote></div>
</div></div><br>______________________________<wbr>_________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/<wbr>mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>