Thats worked for me on CME 4.1, But on 4.3 the phones does not access directly to my service but a service from CME (the devicename is sent by the phones just in the firts request, so now, using 4.3 It's not sent).
I readed that a tag called #DEVICENAME# can be usead as a part of the URL. I tried to do;
Can't you just give the phone back the service url they had on CME 4.1?
I have never seen the new service page (there really is one now... so you manage services by CME and you have the same abilities as with CCM?) but I figure it would get the device name and then you have to make that service page give the parameter to subsequent services.
you can only use the #DEVICENAME# tag in services that are provisioned via subscriptions from the callmanager and go via the ccmcip/xmldirectory scripts (that is where it get replaced with the device name, the phone is not really doing anything with the tag...
So there you have it.. if you want to have multiple services on CME, you need to write your own service selection page that mimicks the service entry page for CCM (a CiscoIPPhoneMenu listing all subscribed services).. and read out the device name and add it to each service url making sure that you check if the service url already contains a query string and in that case append &name=SEP123 instead of appending ?name=SEP123 (and of course don't forget about the xml encoding of &...)
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...