<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>RE: Error 505214 - scheduler insufficient privileges</title>
  <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_recent_posts?p_l_id=" />
  <subtitle>RE: Error 505214 - scheduler insufficient privileges</subtitle>
  <id>http://developer.cisco.com/c/message_boards/find_recent_posts?p_l_id=</id>
  <updated>2013-05-21T06:19:07Z</updated>
  <dc:date>2013-05-21T06:19:07Z</dc:date>
  <entry>
    <title>RE: Error 505214 - scheduler insufficient privileges</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5234838" />
    <author>
      <name>Tan An Chen</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=5234838</id>
    <updated>2012-03-01T23:56:04Z</updated>
    <published>2012-03-01T23:56:04Z</published>
    <summary type="html">HI Andrew,
 
Did you setup your CTSMan server as "Scheduling API" Mode during the First time setup? 
 

Every API invocation must pass the user name (logon name) and password that is associated with ECA account that is created in LDAP server.

 
The user name and password need to match the user name and password you set in the "First time setup".
 
Because your screen shot is not complete, so I did not see the "SchedulingAPI" link, you should be able to fine out your setting from that link.
 
Regards,
 
Paul
 
[quote]Hello all,
 
We are using the CTS MAN scheduling API to create a OBTP meeting between two EX90 devices.  These are controlled by UNified CM 8.6 and are using TC5 with latest device pack.  We are getting an error 505214 which indicates lack of organiser/scheduler privileges.  We can see the SOAP message coming back from CTSMan which is copied below.  Question is:
 
&gt;&gt;&gt; Is anyone aware of what we should configure to ensure that a user in Unified CM (imported from AD with email address) can have the right privileges on CTSMan to be able to schedule a meeting with an EX90?
 
Many thanks,
Andrew


[b]Qmatic =&gt; TP HTTP
Request[/b]
[color=#1f497d] [/color]
POST /adapters/services/SchedulingAPI HTTP/1.1
Content-Type: application/soap+xml; charset=UTF-8;
action="urn:scheduleTMeetings"
User-Agent: Axis2
Host: ctsman.ingicec.com:8081
Transfer-Encoding: chunked
 
58b
&lt;?xml version='1.0' encoding='UTF-8'?&gt;&lt;soapenv:Envelope
xmlns:soapenv="[url=http://www.w3.org/2003/05/soap-envelope]http://www.w3.org/2003/05/soap-envelope[/url]"&gt;&lt;soapenv:Header&gt;
&lt;wsse:Security xmlns:wsse="[url=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd]http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd[/url]"
soapenv:mustUnderstand="true"&gt;&lt;wsse:UsernameToken
xmlns:wsu="[url=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd]http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd[/url]"
wsu:Id="UsernameToken-8560954"&gt;&lt;wsse:Username&gt;Administrator&lt;/wsse:Username&gt;&lt;wsse:Password
Type="[url=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText]http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText[/url]"&gt;InG321!&lt;/wsse:Password&gt;&lt;/wsse:UsernameToken&gt;&lt;/wsse:Security&gt;&lt;/soapenv:Header&gt;&lt;soapenv:Body&gt;&lt;ns2:scheduleTMeetings
xmlns:ns2="[url=http://api.adapters.soap.scheduler.ts.cisco.com/]http://api.adapters.soap.scheduler.ts.cisco.com[/url]"&gt;&lt;ns2:param0
xmlns:ns1="[url=http://object.api.adapter.scheduler.ts.cisco.com/xsd]http://object.api.adapter.scheduler.ts.cisco.com/xsd[/url]"
xmlns:xsi="[url=http://www.w3.org/2001/XMLSchema-instance]http://www.w3.org/2001/XMLSchema-instance[/url]"
xsi:type="ns1:TiCalMeeting"&gt;&lt;ns1:iCalData&gt;BEGIN:VCALENDAR&amp;#xd;
VERSION:2.0&amp;#xd;
METHOD:REQUEST&amp;#xd;
BEGIN:VEVENT&amp;#xd;
ATTENDEE:MAILTO:rmass@ingicec.com&amp;#xd;
ORGANIZER:MAILTO:branch1room1@ingicec.com&amp;#xd;
DTSTART:20120229T133000Z&amp;#xd;
DTEND:20120229T134500Z&amp;#xd;
STATUS:CONFIRMED&amp;#xd;
UID:79c9ecb9-a195-4f59-85dd-89f3b90837d2&amp;#xd;
SUMMARY: Customer '__just_testing_tp__' with reference 'aaa'
scheduled by Qmatic&amp;#xd;
END:VEVENT&amp;#xd;
END:VCALENDAR&amp;#xd;
&lt;/ns1:iCalData&gt;&lt;/ns2:param0&gt;&lt;/ns2:scheduleTMeetings&gt;&lt;/soapenv:Body&gt;&lt;/soapenv:Envelope&gt;
0
[color=#1f497d] [/color]
[b]TP =&gt; Qmatic HTTP
Response[/b]
[color=#1f497d] [/color]
Note that a valid web service
XML response is provided this time, with a more meaningful error message (in
red):
[color=#1f497d] [/color]
HTTP/1.1 200 OK
Date: Wed, 29 Feb 2012 12:15:48 GMT
Server: Apache/2.0.59 (Unix)
X-Powered-By: TSBU
Connection: close
Transfer-Encoding: chunked
Content-Type: application/soap+xml;
action="urn:scheduleTMeetingsResponse";charset=UTF-8
 
257
&lt;?xml version='1.0' encoding='UTF-8'?&gt;&lt;soapenv:Envelope
xmlns:soapenv="[url=http://www.w3.org/2003/05/soap-envelope]http://www.w3.org/2003/05/soap-envelope[/url]"&gt;&lt;soapenv:Body&gt;&lt;ns2:scheduleTMeetingsResponse
xmlns:ns2="[url=http://api.adapters.soap.scheduler.ts.cisco.com/]http://api.adapters.soap.scheduler.ts.cisco.com[/url]"&gt;&lt;ns2:return
xmlns:ns1="[url=http://object.api.adapter.scheduler.ts.cisco.com/xsd]http://object.api.adapter.scheduler.ts.cisco.com/xsd[/url]"
xmlns:xsi="[url=http://www.w3.org/2001/XMLSchema-instance]http://www.w3.org/2001/XMLSchema-instance[/url]"
xsi:type="ns1:TMeetingResponse"&gt;&lt;ns1:responseCode&gt;501214&lt;/ns1:responseCode&gt;&lt;ns1:responseDescription&gt;[b][i]NOT_ENOUGH_PRIVILEGES_ERROR:
Invalid Organizer[/i][/b]&lt;/ns1:responseDescription&gt;&lt;/ns2:return&gt;&lt;/ns2:scheduleTMeetingsResponse&gt;&lt;/soapenv:Body&gt;&lt;/soapenv:Envelope&gt;
0                  [/quote]</summary>
    <dc:creator>Tan An Chen</dc:creator>
    <dc:date>2012-03-01T23:56:04Z</dc:date>
  </entry>
</feed>

