This is a bug in the Allegro Webclient, as best I can tell, but a workaround would be great if somebody has one.
I'm attempting to configure an email parameter for a phone server on the callmanager. For whatever reason, passing an email redirects the web request to the domain in the email address, not the actual URL given in the services config.
I suppose I should clarify a little. I can make this work from a developer's perspective fairly easily. There's no reason an escape character can't be used, since this is just for passing an initial parameter to the application when its called from the services menu.
What bothers me, and maybe this should be reported as a bug rather than posted here, is that I won't be able to simply tell the users to subscribe to the service and enter their email address when they subscribe.
I can guarantee this is going to cause issues down the road, as this application is being rolled out to a customer, not internally, and I'm not looking forward to the customer complaining about having to enter foo%40bar.com when they subscribe instead of an unescaped email address, particularly since the @ character is not required to be escaped in a standard URL in any other web client.
Actually, the @ character does have special meaning in an URL when using authentication. That may be why the Allegro web client is having trouble with it.
Browsers handle it a bit differently, though if I recall correctly at one time it was possible to make you think you were visiting one website when you were actually visiting another (ie email@example.com')">http://firstname.lastname@example.org The first site would be treated as a authentication to the actual site. This was probably fixed for security reasons. I may be wrong though :)
EDIT: the Cisco forum software seems to be having trouble with that sample URL as well..
That being said, the problem remains unsolved. I would think that it is up to Cisco to properly encode the URLs when sending the service list to the phone (just as we would when developing our own services). The alternative is to have Allegro change their client code, and I would think that the former would be changed more quickly than the latter.
The only "workaround" I could think of would be to break the email address into two parts (username and host/mailserver name) and have your code put them back together. Not very nice, but perhaps better than the %40 alternative.
Thanks for bringing this up, and good luck with it!
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...