Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Attention: The Community will be in read-only mode on 12/14/2017 from 12:00 am pacific to 11:30 am.

During this time you will only be able to see content. Other interactions such as posting, replying to questions, or marking content as helpful will be disabled for few hours.

We apologize for the inconvenience while we perform important updates to the Community.

New Member

AXL soap Subscribe Services problem since update 4.1.3

Hi i try to add with XML soap but i can't

I don't understand what's " <xsd:element name="service" type="axl:XSubscribedService"

i try to push a updatephone with :

...

<services>

<service>

<telecasterServiceName>XXX</telecasterServiceName>

<name>XXX</name>

...

This code work before CCM 4.1.3

Thanks.

6 REPLIES

Re: AXL soap Subscribe Services problem since update 4.1.3

this works for me in ccm 4.1(3)sr1

SEPaabbccddeeff

Extension Mobility

Extension Mobility

http://10.1.1.1/emapp/EMAppServlet?device=#DEVICENAME#

What is the response from callmanager, look in the trace/axl directory, and/or W3SVC1 for trace/log files and tell me what was sent back to you from the soap interface.

Oh, where did you upgrade from? the format is different in ccm3.x

regards

Sascha

New Member

Re: AXL soap Subscribe Services problem since update 4.1.3

Hi,

I encountered a problem, exactly adding the extension mobility service to a phone using AXL. I discovered that if I add the device=... part of the URL I get the following error:

Item not valid: parameter not found.

This happens with CCM 4.0(2a), and it doesn't happen with CCM 4.1(3). Is this a bug? Is it because device appears in the URL as a parameter but in fact in the IP Phone Service definition it's not a parameter?

thanks!

alej

New Member

Re: AXL soap Subscribe Services problem since update 4.1.3

I can't remember the details, but in the past, you could slap any URL you wanted in there: now, the URL is validated against the URL as defined in the service--so the base URL must be the same, and also any parameters must be present.

New Member

Re: AXL soap Subscribe Services problem since update 4.1.3

What does now mean?

Anyway , the URL and the parameters are exactly the same as the service definition, so this is not the case.

New Member

Re: AXL soap Subscribe Services problem since update 4.1.3

Sorry

now = 4.1.3.

I don't know what to tell you--I know for a fact that my problem had to do that I was applying a URL drastically different than the original

New Member

Re: AXL soap Subscribe Services problem since update 4.1.3

ok. No this is not the case, I just want to subscribe to the extension mobility service. But as I said, it does work with 4.1(3). However my customer has 4.0(2a). Before i implement a workaround I wanted to know where the problem was.

194
Views
0
Helpful
6
Replies
CreatePlease to create content