Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1118
Views
0
Helpful
6
Replies

resetHuntList - HTTP 500 when using 10.5 syntax on 11.5 system

stephan.steiner
Spotlight
Spotlight

‎07-22-2016 06:22 AM

Hi

I forgot to set one of my applications to use 11.5 syntax when testing this afternoon, and ran into this.

The request

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/10.5"><soapenv:Header/><soapenv:Body><ns:resetHuntList sequence="0"> <name>HL_team_guitest</name></ns:resetHuntList></soapenv:Body></soapenv:Envelope>

The AXL debug log then only show

2016-07-22 15:10:38,601 DEBUG [http-bio-443-exec-7] servletRouters.AXLAlpha - ResponseWrapper data size: 268

2016-07-22 15:10:38,621 INFO  [http-bio-443-exec-7] filters.TimingFilter - Request 1469022270992 received from sdkuser at ip 10.80.0.132 was processed in 101ms

And the client gets an HTTP 500 error.

Swap out the 10.5 with 11.5, and things are fine.

While the dev guide for 11.5 isn't out yet, 11.5 should support 10.5 syntax, right?

Labels:
0 Helpful
6 Replies 6

dstaudt
Cisco Employee
Cisco Employee

‎09-08-2016 03:08 PM

I was able to use a <resetHuntList> request built for and successfully tested against 10.5, and then run it immediately pointing to my 11.5 CUCM.

Is it possible your request has a mismatch of the namespace (10.5) and SOAPAction HTTP header (11.5), or vice versa..?  Can you provide the full HTTP request, including all headers?

0 Helpful

stephan.steiner
Spotlight
Spotlight
In response to dstaudt

‎10-04-2016 08:13 AM

Here's the fiddler trace of my request

POST https://chdevcucm105.nxodev.intra/axl/ HTTP/1.1

Authorization: Basic c2RrdXNlcjpzZGt1c2Vy

SOAPAction: CUCM:DB ver=10.5 resetHuntList

Content-Type: text/xml

Host: chdevcucm105.nxodev.intra

Content-Length: 268

Expect: 100-continue

Connection: Keep-Alive

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/10.5"><soapenv:Header/><soapenv:Body><ns:resetHuntList sequence="0"> <name>HL_team_guitest</name></ns:resetHuntList></soapenv:Body></soapenv:Envelope>

As you can see, namespace in the soap message and the SoapAction are consistent.

And the server response is

HTTP/1.1 500 Internal Server Error

Set-Cookie: JSESSIONIDSSO=665AA6F76CD646154F992F032D347D5A; Path=/; Secure; HttpOnly

Set-Cookie: JSESSIONID=AC9E9593877A4C2FA4C82FC29E92F03B; Path=/axl/; Secure; HttpOnly

X-Frame-Options: SAMEORIGIN

Strict-Transport-Security: max-age=31536000; includeSubdomains

Content-Type: text/xml;charset=ISO-8859-1

Date: Tue, 04 Oct 2016 15:10:17 GMT

Connection: close

Server:

Content-Length: 268

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>Couldn't parse stream.</faultstring></soap:Fault></soap:Body></soap:Envelope>

<!--This API has been processed by GAXL not AXL-->

If I change it back to 11.5, the request is

POST https://chdevcucm105.nxodev.intra/axl/ HTTP/1.1

Authorization: Basic c2RrdXNlcjpzZGt1c2Vy

Content-Type: text/xml

Host: chdevcucm105.nxodev.intra

Content-Length: 268

Expect: 100-continue

Connection: Keep-Alive

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/11.5"><soapenv:Header/><soapenv:Body><ns:resetHuntList sequence="0"> <name>HL_team_guitest</name></ns:resetHuntList></soapenv:Body></soapenv:Envelope>

And the response

HTTP/1.1 200 OK

Set-Cookie: JSESSIONIDSSO=6237B58364AF2C8351105F60D87C1371; Path=/; Secure; HttpOnly

Set-Cookie: JSESSIONID=461C13E8E3D12932250D84A9153748B0; Path=/axl/; Secure; HttpOnly

X-Frame-Options: SAMEORIGIN

Strict-Transport-Security: max-age=31536000; includeSubdomains

Content-Type: text/xml;charset=ISO-8859-1

Transfer-Encoding: chunked

Date: Tue, 04 Oct 2016 15:11:50 GMT

Server:

146

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/11.5"><soapenv:Body><ns:resetHuntListResponse><return>b9d69cd8-f086-ea67-2c0c-cf3e1d21b7a7</return></ns:resetHuntListResponse></soapenv:Body></soapenv:Envelope>

<!--This API has been processed by GAXL not AXL-->

0

0 Helpful

dstaudt
Cisco Employee
Cisco Employee
In response to stephan.steiner

‎10-06-2016 02:49 PM

I note that:

- Neither request is going to the appropriate port (8443)

- The 2nd request does not include the SOAPAction header

though I'm not sure if either of those explain what you're seeing...

0 Helpful

stephan.steiner
Spotlight
Spotlight
In response to dstaudt

‎10-07-2016 07:03 AM

Well, I've been using the standard HTTPs Port since CUCM 4, and that has always worked. The missing header has me concerned.. undesireable things do happen if you leave it away so I guess I need to check my code. Interestingly enough, things work fine when I target a 10.5 CUCM with 10.5 syntax (and I do send a lot of commands.. I have customer making entire rollouts on 10.5 with my code)

0 Helpful

stephan.steiner
Spotlight
Spotlight
In response to stephan.steiner

‎10-20-2016 08:23 AM

I've added the missing SOAPAction header to my 11.x requests.. but what used to work still works.. and on a 10.5 it doesn't.

Do you have an 11.5 somewhere where you could run that command to see if you're getting the same behavior? Here's the latest failed attempt again:

POST https://chdevcucm105.nxodev.intra/axl/ HTTP/1.1

Authorization: Basic c2RrdXNlcjpzZGt1c2Vy

SOAPAction: CUCM:DB ver=10.5 resetHuntList

Content-Type: text/xml

Host: chdevcucm105.nxodev.intra

Content-Length: 268

Expect: 100-continue

Connection: Keep-Alive

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/10.5"><soapenv:Header/><soapenv:Body><ns:resetHuntList sequence="0"> <name>HL_team_guitest</name></ns:resetHuntList></soapenv:Body></soapenv:Envelope>

0 Helpful

dstaudt
Cisco Employee
Cisco Employee
In response to stephan.steiner

‎10-27-2016 02:51 PM

Spent some time looking at this and just about out of ideas   Something perhaps is not as it appears..

Enclosed is as close as I could get to your failure request using curl (command.sh and request.xml attached).  Running this against a known 11.5.1.10000-6 CUCM:

[SSL overhead ommitted]

> POST /axl/ HTTP/1.1

> Host: ds-ucm115-1.cisco.com

> Authorization: Basic QWRtaW5pc3RyYXRvcjpjaXNjb3BzZHQ=

> User-Agent: curl/7.47.0

> Accept: */*

> Expect: 100-continue

> SOAPAction: CUCM:DB ver=10.5 resetHuntList

> Content-Type: text/xml

> Content-Length: 265

>

< HTTP/1.1 100 Continue

* We are completely uploaded and fine

< HTTP/1.1 200 OK

< Set-Cookie: JSESSIONIDSSO=F7102891FF736C1E5DCE3020626B4CB3; Path=/; Secure; HttpOnly

< Set-Cookie: JSESSIONID=731A7DA88CCCE9955F8111BE054D2C48; Path=/axl/; Secure; HttpOnly

< X-Frame-Options: SAMEORIGIN

< Strict-Transport-Security: max-age=31536000; includeSubdomains

< Content-Type: text/xml;charset=ISO-8859-1

< Transfer-Encoding: chunked

< Date: Thu, 27 Oct 2016 21:40:27 GMT

< Server:

<

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><ns2:resetHuntListResponse xmlns:ns2="http://www.cisco.com/AXL/API/10.5"><return>f575c929-051b-c7dc-1ccc-8d8da3d4714e</return></ns2:resetHuntListResponse></soap:Body></soap:Envelope>

* Connection #0 to host ds-ucm115-1.cisco.com left intact

If this still fails for you, can you attach a Fiddler output log?

command.zip
request.xml.zip
0 Helpful
Customers Also Viewed These Support Documents