This document was generated from CDN thread
Created by: Andrew Fraser on 01-03-2012 05:31:46 AM
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:
>>> 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
Qmatic => TP HTTP
Request
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
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
soapenv:mustUnderstand="true"><wsse:UsernameToken
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
wsu:Id="UsernameToken-8560954"><wsse:Username>Administrator</wsse:Username><wsse
assword
Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">InG321!</wsseassword></wsse:UsernameToken></wsse:Security></soapenv:Header><soapenv:Body><ns2:scheduleTMeetings
xmlns:ns2="http://api.adapters.soap.scheduler.ts.cisco.com"><ns2:param0
xmlns:ns1="http://object.api.adapter.scheduler.ts.cisco.com/xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ns1:TiCalMeeting"><ns1:iCalData>BEGIN
CALENDAR
VERSION:2.0
METHOD:REQUEST
BEGINEVENT
ATTENDEE:MAILTO:rmass@ingicec.com
ORGANIZER:MAILTO:branch1room1@ingicec.com
DTSTART:20120229T133000Z
DTEND:20120229T134500Z
STATUS:CONFIRMED
UID:79c9ecb9-a195-4f59-85dd-89f3b90837d2
SUMMARY: Customer '__just_testing_tp__' with reference 'aaa'
scheduled by Qmatic
ENDEVENT
ENDCALENDAR
</ns1:iCalData></ns2:param0></ns2:scheduleTMeetings></soapenv:Body></soapenv:Envelope>
0
TP => Qmatic HTTP
Response
Note that a valid web service
XML response is provided this time, with a more meaningful error message (in
red):
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
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Body><ns2:scheduleTMeetingsResponse
xmlns:ns2="http://api.adapters.soap.scheduler.ts.cisco.com"><ns2:return
xmlns:ns1="http://object.api.adapter.scheduler.ts.cisco.com/xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ns1:TMeetingResponse"><ns1:responseCode>501214</ns1:responseCode><ns1:responseDescription>NOT_ENOUGH_PRIVILEGES_ERROR:
Invalid Organizer</ns1:responseDescription></ns2:return></ns2:scheduleTMeetingsResponse></soapenv:Body></soapenv:Envelope>
0
Subject: RE: Error 505214 - scheduler insufficient privileges
Replied by: Andrew Fraser on 01-03-2012 08:16:21 PM
Thanks to some troubleshooting with Paul we determined a couple of things:
1) The UID for the ECA user needs to be fully qualified...i.e. user@domain.com in the API call. We had it just as UID....changing it to be fully qualified solved that problem!
2) We then noticed that the meeting got scheduled but there was only one participant. This was because we hadn't added the organiser as an attendee of their own meeting. Must confess that we made an incorrect assumption that the user organising would implicitly be added as an attendee...
Thanks for your support!
Subject: RE: Error 505214 - scheduler insufficient privileges
Replied by: Tan An Chen on 01-03-2012 05:56:04 PM
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
Created by: Andrew Fraser on 01-03-2012 05:31:46 AM
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:
>>> 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
Qmatic => TP HTTP
Request
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
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
soapenv:mustUnderstand="true"><wsse:UsernameToken
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
wsu:Id="UsernameToken-8560954"><wsse:Username>Administrator</wsse:Username><wsse
asswordType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">InG321!</wsse
assword></wsse:UsernameToken></wsse:Security></soapenv:Header><soapenv:Body><ns2:scheduleTMeetingsxmlns:ns2="http://api.adapters.soap.scheduler.ts.cisco.com"><ns2:param0
xmlns:ns1="http://object.api.adapter.scheduler.ts.cisco.com/xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ns1:TiCalMeeting"><ns1:iCalData>BEGIN
CALENDAR
VERSION:2.0
METHOD:REQUEST
BEGIN
EVENT
ATTENDEE:MAILTO:rmass@ingicec.com
ORGANIZER:MAILTO:branch1room1@ingicec.com
DTSTART:20120229T133000Z
DTEND:20120229T134500Z
STATUS:CONFIRMED
UID:79c9ecb9-a195-4f59-85dd-89f3b90837d2
SUMMARY: Customer '__just_testing_tp__' with reference 'aaa'
scheduled by Qmatic
END
EVENT
END
CALENDAR
</ns1:iCalData></ns2:param0></ns2:scheduleTMeetings></soapenv:Body></soapenv:Envelope>
0
TP => Qmatic HTTP
Response
Note that a valid web service
XML response is provided this time, with a more meaningful error message (in
red):
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
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Body><ns2:scheduleTMeetingsResponse
xmlns:ns2="http://api.adapters.soap.scheduler.ts.cisco.com"><ns2:return
xmlns:ns1="http://object.api.adapter.scheduler.ts.cisco.com/xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ns1:TMeetingResponse"><ns1:responseCode>501214</ns1:responseCode><ns1:responseDescription>NOT_ENOUGH_PRIVILEGES_ERROR:
Invalid Organizer</ns1:responseDescription></ns2:return></ns2:scheduleTMeetingsResponse></soapenv:Body></soapenv:Envelope>
0
Subject: RE: Error 505214 - scheduler insufficient privileges
Replied by: Andrew Fraser on 01-03-2012 08:16:21 PM
Thanks to some troubleshooting with Paul we determined a couple of things:
1) The UID for the ECA user needs to be fully qualified...i.e. user@domain.com in the API call. We had it just as UID....changing it to be fully qualified solved that problem!
2) We then noticed that the meeting got scheduled but there was only one participant. This was because we hadn't added the organiser as an attendee of their own meeting. Must confess that we made an incorrect assumption that the user organising would implicitly be added as an attendee...
Thanks for your support!
Subject: RE: Error 505214 - scheduler insufficient privileges
Replied by: Tan An Chen on 01-03-2012 05:56:04 PM
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
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:
>>> 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
Qmatic => TP HTTP
Request
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
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
soapenv:mustUnderstand="true"><wsse:UsernameToken
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
wsu:Id="UsernameToken-8560954"><wsse:Username>Administrator</wsse:Username><wsse
Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">InG321!</wsse
xmlns:ns2="http://api.adapters.soap.scheduler.ts.cisco.com"><ns2:param0
xmlns:ns1="http://object.api.adapter.scheduler.ts.cisco.com/xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ns1:TiCalMeeting"><ns1:iCalData>BEGIN
VERSION:2.0
METHOD:REQUEST
BEGIN
ATTENDEE:MAILTO:rmass@ingicec.com
ORGANIZER:MAILTO:branch1room1@ingicec.com
DTSTART:20120229T133000Z
DTEND:20120229T134500Z
STATUS:CONFIRMED
UID:79c9ecb9-a195-4f59-85dd-89f3b90837d2
SUMMARY: Customer '__just_testing_tp__' with reference 'aaa'
scheduled by Qmatic
END
END
</ns1:iCalData></ns2:param0></ns2:scheduleTMeetings></soapenv:Body></soapenv:Envelope>
0
TP => Qmatic HTTP
Response
Note that a valid web service
XML response is provided this time, with a more meaningful error message (in
red):
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
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Body><ns2:scheduleTMeetingsResponse
xmlns:ns2="http://api.adapters.soap.scheduler.ts.cisco.com"><ns2:return
xmlns:ns1="http://object.api.adapter.scheduler.ts.cisco.com/xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="ns1:TMeetingResponse"><ns1:responseCode>501214</ns1:responseCode><ns1:responseDescription>NOT_ENOUGH_PRIVILEGES_ERROR:
Invalid Organizer</ns1:responseDescription></ns2:return></ns2:scheduleTMeetingsResponse></soapenv:Body></soapenv:Envelope>
0