<div dir="ltr">Anthony, that's what I experienced too, just an endless loop of not being able to find what I was looking for.<div>Nathan, you have WAY more patience than I do right now. Thank you!</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Oct 1, 2017 at 1:35 PM, 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">Oh man, you just solved my major problem with Postman desktop app. I was getting the domain not allowed error, and just quit after that. I have not experienced that before, but now I know. Thanks!</div><div class="HOEnZb"><div class="h5"><br><div class="gmail_quote"><div dir="ltr">On Sun, Oct 1, 2017 at 12:25 AM 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">Taken a quick look and yeah, Anthony is correct in regards to the use of DELETE.<div><br></div><div><b>To Delete the existing UM Service account:</b></div><div>- A GET to https://<connection-server>/<wbr>vmrest/users/ will dump the users on the Connection Server.</div><div>- For each user you'll find an objectId listed. A GET to https://<connection-server>/<wbr>vmrest/users/<user-objectid>/<wbr>externalserviceaccounts will dump any attached external services account for the user.<br></div><div>- You'll want to then grab the '<URI>' value in the returned data (looking like '/vmrest/users/<user-objectid><wbr>/externalserviceaccounts/<<wbr>ObjectId>' and execute a DELETE against that URI (obv adding 'https://<connection-server>/' to the URI).</div><div>- Note that you need to use basic auth to login as an appadmin for the request.</div><div>- CURL wise: curl --basic --user <app admin>:<password> -k -X DELETE https://<connection-server>/<wbr>vmrest/users/<user-objectid>/<wbr>externalserviceaccounts/<<wbr>object-id> </div><div><br></div><div><b>To add the new UM Service to the user account:</b></div><div>- Update the XML below with:</div><div> - %umservice-objectid% - The guid of the um service (easiest way is to grab the guid from the CUC Admin pages for the UM service listed under Unified Messaging > Unified Messaging Services).</div><div> - %user-objectid% - As per the id you found prev when you did the delete.</div><pre style="padding:1em;border:1px dashed rgb(47,111,171);color:rgb(0,0,0);background-color:rgb(249,249,249);line-height:1.1em"><ExternalServiceAccount>
<ExternalServiceObjectId><b>%<wbr>umservice-objectid%</b></<wbr>ExternalServiceObjectId>
<SubscriberObjectId><b>%user-<wbr>objectid%</b></SubscriberObjectId>
<UserURI>/vmrest/users/<b>%user-<wbr>objectid%</b></UserURI>
<EnableCalendarCapability><wbr>true</<wbr>EnableCalendarCapability>
<EnableMeetingCapability><wbr>false</<wbr>EnableMeetingCapability>
<EnableTtsOfEmailCapability><wbr>true</<wbr>EnableTtsOfEmailCapability>
<IsPrimaryMeetingService><wbr>false</<wbr>IsPrimaryMeetingService>
<LoginType>0</LoginType>
<UserPassword/>
<EnableMailboxSynchCapability><wbr>true</<wbr>EnableMailboxSynchCapability>
<EmailAddressUseCorp>true</<wbr>EmailAddressUseCorp>
</ExternalServiceAccount></pre><div class="gmail_extra">You'll need to then POST this XML to url: 'https://<connection-server>/<wbr>vmrest/users/<user-objectid>/<wbr>externalserviceaccounts'. Note that again you need to provide basic auth.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Note that the XML Above worked for me when adding a UM Service configured to point to Exchange, so ~in theory~ this should work for O365 as well. Not got a tenancy I can test against at the moment in O365 to confirm.</div><div class="gmail_extra"><br></div><div class="gmail_extra">If you use Postman to run this stuff, make sure you use the desktop version (not the chrome extension version), and make sure you add the 'Origin' header. The value should be the url of the CUC Server (eg '<a href="http://172.20.2.25" target="_blank">http://172.20.2.25</a>'). This should stop you receiving the 'domain not allowed' error message'</div><div class="gmail_extra"><br></div><div class="gmail_extra">Hope this assists.</div></div><div dir="ltr"><div class="gmail_extra"><br></div><div class="gmail_extra">Nathan</div></div><div dir="ltr"><div class="gmail_extra"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 29, 2017 at 7:56 AM, Nathan Reeves <span dir="ltr"><<a href="mailto:nathan.a.reeves@gmail.com" target="_blank">nathan.a.reeves@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">While people are possibly playing around with the CUC Provisioning API, let me know if you ever get the import of CUCM Local users to CUC working correctly. The last rollout I did I was trying to pull in local users but the api just didn't work. Had to use LDAP imports instead. Never looked too much deeper as I just needed to get on with things.<div><br></div><div>But yeah, the API for CUC is really hit and miss. lol, and the API for UCCX can be a bit the same.</div><span class="m_3136173880218811874m_-8433428979503428799gmail-HOEnZb"><font color="#888888"><div><br></div><div>Nathan</div></font></span></div><div class="m_3136173880218811874m_-8433428979503428799gmail-HOEnZb"><div class="m_3136173880218811874m_-8433428979503428799gmail-h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 29, 2017 at 5:07 AM, 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:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Wow, the documentation for the CUC API has gone to shit. There's literally a link on the <a href="http://developer.cisco.com" target="_blank">developer.cisco.com</a> site that sends you to a wiki site, which itself then sends you to <a href="http://developer.cisco.com" target="_blank">developer.cisco.com</a>. Nice.<div><br></div><div>Anyway, I tried to look into this quick for you, but I got stuck with the documentation on POSTing a new UM account for end users. It literally just says:</div><div><br></div><div><div>"To create an a new external service account, POST an XML document (<font color="#ff0000">formatted similar to the one above</font>) to the following URL:</div><div>POST https://<connection-server>/<wbr>vmrest/users/<user-objectid>/<wbr>externalserviceaccounts"</div></div><div>Source: <a href="http://docwiki.cisco.com/wiki/Cisco_Unity_Connection_Provisioning_Interface_(CUPI)_API_--_User_Unified_Messaging_Account" target="_blank">http://docwiki.cisco.<wbr>com/wiki/Cisco_Unity_<wbr>Connection_Provisioning_<wbr>Interface_(CUPI)_API_--_User_<wbr>Unified_Messaging_Account</a></div><div><br></div><div>The key part being "similar to." It's beyond my comprehension that anyone would think that this is sufficient documentation to make an API request work. Suffice it to say, it didn't work for me, and now I'm done troubleshooting it.</div><div><br></div><div>Since any good REST API should use CRUD, it would then make sense that you issue an HTTP DELETE to the user object + um account object URI to remove the old one, after you successfully run the POST above to Create the new association.</div><div><br></div><div>Good luck. If I have more time in the next few days, I'll try again.</div></div><br><div class="gmail_quote"><div><div class="m_3136173880218811874m_-8433428979503428799gmail-m_-5394767432683339272h5"><div dir="ltr">On Wed, Sep 27, 2017 at 10:25 AM Nick Barnett <<a href="mailto:nicksbarnett@gmail.com" target="_blank">nicksbarnett@gmail.com</a>> wrote:<br></div></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class="m_3136173880218811874m_-8433428979503428799gmail-m_-5394767432683339272h5"><div dir="ltr">I can handle most things in CUCM with SOAP, but I always get confused when trying to use VMREST in CUC. I cannot find a way to add and remove a UM account via automation. We're stuck using a CSV and it's really putting a cramp in our migration to Exchange Online.<div><br></div><div>The particular change I'm needing is here: Users->EditMenu->Unified messaging accounts</div><div>1) Need to add an additional one that connects to Exchange Online (this already exists in CUC)</div><div>2) Need to delete the old one that connects to on prem Exchange. (Not delete the whole UM connector service, but just the account association to a particular user)</div><div><br></div><div>Does anyone have any pointers on this? We have batches of people migrating every week, sometimes multiple times per week... so I can't just make some global change.</div><div><br></div><div>We're on CUC 10.5</div><div><br></div><div>Thanks!</div><div>Nick</div><div><br></div><div>P.S. I hate that MSFT and CSCO both have a product called "Unified Messaging" :)</div></div></div></div>
______________________________<wbr>_________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">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>
</blockquote></div>
<br>______________________________<wbr>_________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">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>
</div></div></blockquote></div><br></div></div></blockquote></div>
</div></div></blockquote></div><br></div>