cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2571
Views
4
Helpful
9
Replies

Failed to Initialize VoiceView - Unable to open port 80

Brook Powers
Level 1
Level 1

When attempting to Cisco "Smart" Call Connector Advanced, under the VoiceView tab, I get the error: Failed to Initialize VoiceView - Unable to open port 80.

I worked with Sonny at CallComm for a hour or two disabling firewalls on the server, the client and changing ports here and trying this and that.

We left off thinking that port 80 on the client must be free and I dont know why it wouldnt be.

Why kind of programmer creates a local webserver, on a static port, without checking to see if its in use - to access info (voicemail) on another server?

--

Frustrated

1 Accepted Solution

Accepted Solutions

Hi Brook,

Skype has an option for not using port 80 for incoming connections. You need to uncheck under Options->Advanced->Connections the following " Use port 80 and 443 as alternatives for incoming connections"

With respect to the grey VoiceView field -- some files appear to be left in Windows System32 after the uninstallation of the previous versions of CallConnectors  including the ccTrog.dll and ccSkinny.dll. These files have caaused issues with the Advanced Client operation as the newer versions in the Common Files folder were not being accessed.

Thanks

CallConnector Team

View solution in original post

9 Replies 9

Is this problem isolated to a single client in your network?

Cole

shtalukd
Level 1
Level 1

Hi Brook:

We understand the potential issues associated with requiring port 80 to be available on the user's PC. Unfortunately CUE uses this port for authenticating the voice mail service request and it only sends the message to port 80. On the client side there was no flexibility for moving this to other ports or making this dynamic.

Thanks

CallConnector Team

Hi Brook:

Please also view information on the Advanced Client at https://supportforums.cisco.com/docs/DOC-13290

and application notes on VisualVoice at

https://supportforums.cisco.com/docs/DOC-13290

Thanks

CallConnector Team

I have read all the documentation referenced and performed Google searches on the error.

I am attempting to install the SCCA client on a second engineer's pc and am getting the error "Can connect to the SIP service".

We are now preparing a new OS install in order to test the SCCA client there.

I am not hopeful.

On a not altogether unrelated note - I bought a Sonus system and was setting it up while trying to get my Cisco software to work. I launched the app on my iphone, help down two buttons on my Sonus (as instructed pictorially on the iPhone) and I was immediately configured and streaming music wirelessly. I never even cracked the user manual. Cisco could learn a lesson in that.

On a pc used regularly the install did not prompt for server ip, local ip company, user, support email, etc.

Then errored out with "The username or password you entered is incorrect or the server is down".

On a fresh install we were prompted for the above information, then rebooted and received the same error, "The username or password you entered is incorrect or the server is down".

Other network PC's connect without a problem, using the same credentials.

Hi Brook:

A new install presents the dialogs to collect the information on Server IP, Loca IP etc. If the install program is run where the appliction is already installed, then it will go to the update mode -- and not require that information.

It looks like the user account information entered is not matching the information on the SCC Server or it is unable to locate the server. We are connecting with you to look into this.

Thanks

CallConnector Team

Resolved issue on PC#1 by uninstalling Skype. Apparently skype uses port 80.

I bet there are a few business customers of Cisco who use skype. IMHO, requiring the client to run a webserver to communicate with another server is a dumb idea.

Also, had to alter the CME IP address. Why the Smart Call Connector Server couldn�t reed the CMS IP address and populate the field when it queried the router during setup is beyond me.

Finally, we had to check some MWI fields in the UCC-540 web config pages. My fault RTFM.

Now I am still trying to figure out why the VocieView tab field is blank grey on another client and it wont remember any VoiceView client preferences, no matter how many times we try to save them.

Issue on Paul's laptop was caused by skinny.dll in system32 that was not removed after uninstall UCC 1.5 and that skinny.dll was too old that caused VoiveView app failed to load.Remove skinny.dll from system32 resovles the issue. In version 2.0 or later, all the files are moved to Common folder instead of system32.

Thanks,

CallConnector Team

Hi Brook,

Skype has an option for not using port 80 for incoming connections. You need to uncheck under Options->Advanced->Connections the following " Use port 80 and 443 as alternatives for incoming connections"

With respect to the grey VoiceView field -- some files appear to be left in Windows System32 after the uninstallation of the previous versions of CallConnectors  including the ccTrog.dll and ccSkinny.dll. These files have caaused issues with the Advanced Client operation as the newer versions in the Common Files folder were not being accessed.

Thanks

CallConnector Team

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: