Troubleshoot URL Handler registrations

[stephan.steiner]

Hi

does anyone know if those can be troubleshooted and when they are being made? Until this day, simply installing the msi took care of everything (assuming you're not using a config file that disables registration), but now I'm in an environment where the registration is never being made and have to figure out why this is this way. I suspect a permission issue since the registration needs access to the administrative part of the registry, but without a logfile to show something isn't going right, I'm stuck.

Thanks

Stephan

[keglass]

Stephan,

I think you may have posted your question to the wrong Community. Can you please reply to this thread with more information, and I will try to help properly place your question for better visibility and feedback.

Kelli Glass

Moderator for Cisco Customer Communities

[stephan.steiner]

If you install Jabber for PC normally, then go to Default Programs and "Associate a file type or protocol", you should see that Jabber gets registered as protocol handler for various URL handlers. Amongst others, the tel uri.

So, you can then do "Start", "Run", and type tel:+412345

If you send this off, Jabber will Pop up asking you whether you want to dial +412345.

So, we have registered the tel uri and registered Jabber as handler for this uri. Every tel: link will now be sent to Jabber by Windows.

The questions is how to figure out what isn't being done and why in my customers Environment. I install the same bits, using the same msi (no Parameters) but those registrations don't get made.

[keglass]

Stephan,

Thank you for providing more information. I have contacted a Cisco expert for help in resolving your issue. In the meantime, I recommend you also post this to the Cisco Partner Community, as well, since you mention this is for a customer's environment.

Unified Communications - accessible to Cisco partners only

Kelli Glass