Extension Mobility and Service URL Buttons

[jorgebaptista]

I'm using a Phone Button Template that has some Service URL buttons.

I've configured the Extension Mobility service in the URL button.

The Service doesn't work and gives me the following message : Error [100].

If I configure a Service that doesn't need to authenticate or pass a parameter the Button works fine.

Can anybody help?

Thanks

[aaronw.ca]

What URL did you use when configuring the extension mobility service? Did you set the parameters the service expects? Error 100 indicates that you did not. Refer to the following documentation:

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_administration_guide_chapter09186a00801ed107.html#85813

You need to pass the device name as a parameter to the query.

[jorgebaptista]

This is my Service URL

http://CCM IP/emapp/EMAppServlet?device=#DEVICENAME#

It works if we go to the Services Button, but if if we try to call it from a service URL Button it gives the error message.

Thanks.

JB

[aaronw.ca]

What version of CallManager?

FYI, it should work with 4.1(2), and possibly earlier, as tested on a 7960 and 7970.

One thing to know is that when you make a change to the service, the change does not seem to affect the service URL button. Remove and re-apply the service to the service URL button and see if that helps...

[jorgebaptista]

I'm running CCM 4.0(2)a.

JB

[aaronw.ca]

4.02 might not support that configuration. There used to be a problem with Service URL buttons not supporting the #DEVICENAME# parameter that could be used in regular services.

I don't know if 4.0 supports that. Any chance you could upgrade to 4.1? Otherwise, you could try and find out if there is a fix for 4.0 for this issue... but your 4.02(a) seems fairly up-to-date...

There also seem to be a number of issues relating to the service url buttons in 4.0, though they should have been fixed in 4.02(a), you never know... for example:

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCeg39622

Did you try removing the service url button and adding it again? (You probably have.. but just in case..)

[jorgebaptista]

Yes, I have tried that.

I've also tried to pass the correct parameter, instead of #devicename# i used the SEP1234567890.....

Still don't work.

Thanks.

[aaronw.ca]

So if you have a service on the CallManager with the service URL of:

http://CCM IP/emapp/EMAppServlet?device=#DEVICENAME#

and then subscribe the phone to this new service, and then assign a service url button to this new service, it returns error 100?

And if you create a new service on the CallManager with the service URL of:

http://CCM IP/emapp/EMAppServlet?device=SEP003000400050

and then subscribe the phone to this new service, and then assign a service url button to this new service, it still returns error 100?

Sorry to cover this again, but I just wanted to make sure I understand what is happening. Service URL buttons are funny, and don't always update properly, which is why I mention unsubscribing the service, then resubscribing and re-assigning the service to the service url button.

I cannot imagine why that would not work, especially when you hardcode the parameter value. I can tell you that it does work on CallManager 4.1(2) with this URL:

http://CCM IP/emapp/EMAppServlet?device=#DEVICENAME#

and this works in both a service and as a service url button.

Have you tried sniffing the network traffic to see what the phone is requesting when you call the EM service via the service url button? Is the parameter being called?

[jorgebaptista]

SORRY!!! I have done some kind of mistake...

If I hardcode the URL with the correct Device Name the URL Button WORKS. (now that makes more sense.....)

Sorry 'bout the mistake. Guess I have done anything wrong.

I have sniffed the phone and if i push the URL button it gives me :

GET /emapp/EMAppServlet?devicename=#DEVICENAME#

No parameter has been passed.

This is a bug, right? Is there any fix for my version of CCM?

Thanks

JB

[aaronw.ca]

I don't know if there is a fix for that in 4.0. Unfortunately, you might have to move to 4.1 to get that to work, but at least it works in 4.1!

You could check with TAC to see if there is a fix for that in 4.0...

[michael_davis]

Hi,

I've not had any problems with the EM Service URL in 4.0(2)a with 7940 and 7960 phones.

You might want to double-check your syntax. The GET you show in this post is using an incorrect url.

?device vs ?devicename

You are seeing:

GET /emapp/EMAppServlet?devicename=#DEVICENAME#

Should be:

GET /emapp/EMAppServlet?device=SEP1234567890

Let me know if this helps.

[jorgebaptista]

Michael,

The Get that i'm seeing is :

GET /emapp/EMAppServlet?device=SEP1234567890

it is correct. I'm not getting any error with the EM service except when using it from a Service URL Button.

JB