Log In
Developer Network
Technologies
Join the Network
Member Services
Events & Community
MediaSense (MediaSense) Developer Center
Overview
Documentation
Community
Wiki
MediaSense Forums
Message Boards Home
Recent Posts
Statistics
Answer
(
Unmark
)
Mark as an Answer
« Back to Technical Discussion
Unspecified error in signIn
Threads [
Previous
|
Next
]
Unspecified error in signIn
Shahar Mosek
10/25/11 3:40 PM
RE: Unspecified error in signIn
David Lender
11/8/11 3:00 PM
Shahar Mosek
Posts:
1
Join Date:
3/22/11
Recent Posts
Unspecified error in signIn
api
Answer
10/25/11 3:40 PM
Mark as an Answer
Submit
Reply with Quote
Quick Reply
I have a new system installed. It has a CUCM server and a MediaSense server.
I'm trying to use the MediaSense API, and get stuck with the signIn method (the getAPIVersion method works).
I created a user and group on CUCM with the AXL role.
When I post to the signIn URL with the following parameters:
{
"requestParameters": {
"username": "AXLUser",
"password": "xxxxxxxx"
}
}
I get back the following:
{"responseMessage":"Failure: An unknown server error occurred. Please try again later.","responseCode":5000}
In the Real Time Monitoring Tool, I see in the ora node the following:
0000000834: 192.168.5.118: Oct 25 2011 16:32:08.249 +0200: %CCBU____________API-6-CAPTURE_SERVICE_ADAPTER_REQUEST: %[request_sent_to_psbu_recorder=http://192.168.5.118:8081/PurgedRecordings]: Request sent to PSBU Recorder
0000000835: 192.168.5.118: Oct 25 2011 16:32:08.305 +0200: %CCBU____________API-6-CAPTURE_SERVICE_ADAPTER_RESPONSE: %[response_received_from_psbu_recorder=<PurgedRecordings>
</PurgedRecordings>
]: Response received from PSBU Recorder
0000000836: 192.168.5.118: Oct 25 2011 16:32:12.706 +0200: %CCBU____________API-6-SESSION_VERIFIER_TASK_INFO: %: Session verification task information
0000000837: 192.168.5.118: Oct 25 2011 16:32:12.727 +0200: %CCBU____________API-6-SESSION_VERIFIER_TASK_INFO: %: Session verification task information
0000000838: 192.168.5.118: Oct 25 2011 16:32:14.716 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer makeRequest first level: entered function.
0000000839: 192.168.5.118: Oct 25 2011 16:32:14.717 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer makeRequest second level: entered function.
0000000840: 192.168.5.118: Oct 25 2011 16:32:14.717 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer getNextIP: useServer= 0.
0000000841: 192.168.5.118: Oct 25 2011 16:32:14.717 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} RequestState getServerToBeUsed: serverToBeUsed= 1.
0000000842: 192.168.5.118: Oct 25 2011 16:32:14.717 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} RequestState setServerToBeUsed: serverToBeUsed= 0.
0000000843: 192.168.5.118: Oct 25 2011 16:32:14.717 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} RequestState getServerToBeUsed: serverToBeUsed= 0.
0000000844: 192.168.5.118: Oct 25 2011 16:32:14.717 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} RequestState incrementServerToBeUsed: serverToBeUsed= 1.
0000000845: 192.168.5.118: Oct 25 2011 16:32:14.718 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer getIP: server to be used is 192.168.5.118
0000000846: 192.168.5.118: Oct 25 2011 16:32:14.718 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer hasMoreServers: state counter = 0, serversList size = 1.
0000000847: 192.168.5.118: Oct 25 2011 16:32:14.718 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer makeRequest second level: making a(nother) request
0000000848: 192.168.5.118: Oct 25 2011 16:32:14.718 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer makeRequest third level: entered function.
0000000849: 192.168.5.118: Oct 25 2011 16:32:14.718 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer makeRequest: URL Path being sent to the HttpClient is: http://192.168.5.118:8080/oraconfiguration/authenticationService/authentication/authenticateAPIUser
0000000850: 192.168.5.118: Oct 25 2011 16:32:16.105 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer makeRequest third level: response received.
0000000851: 192.168.5.118: Oct 25 2011 16:32:16.106 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer makeRequest second level: actual makeRequest passed.
0000000852: 192.168.5.118: Oct 25 2011 16:32:16.106 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer processResponse: entered function
0000000853: 192.168.5.118: Oct 25 2011 16:32:16.106 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer processResponse: httpResponse is not null.
0000000854: 192.168.5.118: Oct 25 2011 16:32:16.106 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer processResponse: httpStatusCode is valid.
0000000855: 192.168.5.118: Oct 25 2011 16:32:16.106 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer processSuccessfulResponse: entered function.
0000000856: 192.168.5.118: Oct 25 2011 16:32:16.106 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer getNextIP: useServer= 0.
0000000857: 192.168.5.118: Oct 25 2011 16:32:16.106 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} RequestState getServerToBeUsed: serverToBeUsed= 1.
0000000858: 192.168.5.118: Oct 25 2011 16:32:16.107 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} RequestState setServerToBeUsed: serverToBeUsed= 0.
0000000859: 192.168.5.118: Oct 25 2011 16:32:16.107 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} RequestState getServerToBeUsed: serverToBeUsed= 0.
0000000860: 192.168.5.118: Oct 25 2011 16:32:16.107 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} RequestState incrementServerToBeUsed: serverToBeUsed= 1.
0000000861: 192.168.5.118: Oct 25 2011 16:32:16.107 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer getIP: server to be used is 192.168.5.118
0000000862: 192.168.5.118: Oct 25 2011 16:32:16.107 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer processSuccessfulResponse: resultcode is 5; request needs redirection; now trying 192.168.5.118
0000000863: 192.168.5.118: Oct 25 2011 16:32:16.107 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer processSuccessfulResponse: exiting function.
0000000864: 192.168.5.118: Oct 25 2011 16:32:16.107 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer processResponse: exiting function.
0000000865: 192.168.5.118: Oct 25 2011 16:32:16.108 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer hasMoreServers: state counter = 1, serversList size = 1.
0000000866: 192.168.5.118: Oct 25 2011 16:32:16.108 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer makeRequest: state is not null
0000000867: 192.168.5.118: Oct 25 2011 16:32:16.108 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer makeRequest second level: state is not done.
0000000868: 192.168.5.118: Oct 25 2011 16:32:16.108 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer hasMoreServers: state counter = 1, serversList size = 1.
0000000869: 192.168.5.118: Oct 25 2011 16:32:16.108 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer makeRequest second level: has no more servers
0000000870: 192.168.5.118: Oct 25 2011 16:32:16.108 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer makeRequest: state ip is = 192.168.5.118
0000000871: 192.168.5.118: Oct 25 2011 16:32:16.108 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer makeRequest: state httpresponse is = not null
0000000872: 192.168.5.118: Oct 25 2011 16:32:16.109 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer makeRequest second level: exited function.
0000000873: 192.168.5.118: Oct 25 2011 16:32:16.109 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} LoadBalancer makeRequest first level: OraHttpResponse is not null. returning from function with responseBody.
0000000874: 192.168.5.118: Oct 25 2011 16:32:16.109 +0200: %CCBU____________API-7-TRACE: {Thrd=http-8443-7} Result from the command - {"responseMessage":"Failure: An unknown server error occurred. Please try again later.","responseCode":5000}
0000000875: 192.168.5.118: Oct 25 2011 16:32:16.109 +0200: %CCBU____________API-6-AUTH_SERVICE_IMPL_SIGN_IN_RESULT: %[auth_service_impl_sign_in_result={"responseMessage":"Failure: An unknown server error occurred. Please try again later.","responseCode":5000}]: Authentication service impl signIn result
Sign in to vote.
Flag
Please sign in to flag this as inappropriate.
Top
David Lender
Posts:
8
Join Date:
4/4/08
Recent Posts
RE: Unspecified error in signIn
Answer
11/8/11 3:00 PM as a reply to Shahar Mosek.
Mark as an Answer
Submit
Reply with Quote
Quick Reply
- Confirm if you have added this user as a MediaSense user in MediaSense¿s API User configuration page
- If on UCM, confirm this is an End User and NOT an application user
- Collect logs from RTMT for the ¿Cisco MediaSense Configuration Service¿
- In MediaSense¿s serviceability page, confirm if all services are up & running (¿in service¿)
Sign in to vote.
Flag
Please sign in to flag this as inappropriate.
Top
Overview
Documentation
Community
Wiki
Search CDN
Go
By API/SDK:
Select an API
Application eXtension Platform (AXP)
Network Management - Active Network Abstraction (ANA)
Network Management - IP Solution Center (ISC)
Network Management - Network Analysis Module (NAM)
Network Management - Cisco Transport Manager (CTM)
Network Management - Managed Services Management Solution (MSMS)
Cisco Headset/Handset API
Cisco Unified Application Environment (CUAE)
Cisco Unified CM Administration XML (AXL)
Cisco Unified CM Call Detail Records (CDR)
Cisco Unified CM Extension Mobility API
Cisco Unified CM JTAPI (JTAPI)
Cisco Unified CM Log Collection
Cisco Unified CM Performance Monitoring
Cisco Unified CM Real-time Device & CTI Information
Cisco Unified CM Service Control
Cisco Unified CM Servicability XML
Cisco Unified CM SIP (SIP)
Cisco Unified CM SNMP/MIB
Cisco Unified CM TAPI (TAPI)
Cisco Unified CM Web Dialer (WebDialer)
Cisco Unified Communication Express Services Interface
Cisco Unified Presence (CUP)
Cisco Unified TCL IVR/Voice XML API
Cisco Unified Gatekeeper TMP API (GKTMPAPI)
Cisco Unity Connection Provisioning Interface (CUPI)
Cisco Unity Connection Messaging Interface (CUMI)
Computer Telephony Integration (CTI) Server C-API
Computer Telephony Integration (CTI) Server Protocol (GED 188)
Computer Telephony Integration (CTI) Object Server
Contact Center Enterprise/Hosted/ICM IVR PG Protocol (GED-125)
Contact Center Reporting (CCR)
Contact Center TCL IVR/Voice XML API
Customer Voice Portal (CVP)
Enterprise Contact Center Scripting (ECCS)
Enterprise Application Gateway Protocol (AGP)
Hardware eXtension Platform (HXP)
IP Phone Services (IPPS)
Mobility – Cisco Compatible Extensions Program
Mobility – Context-Aware Mobility(Location)
Mobility – Guest Access (GAP)
Mobility – Solution Verification
Meetingplace SOAP API (MPSA)
Smart Business Portal (SBP)
Unified Contact Center Express CTI (UCCXCTI)
WebEx - Connect
WebEx - Meeting Services