Another thing to look at / consider is client DNS issues (if the client is trying to resolve the directory server by hostname). Which, should be evident in the p-caps.
Thanks, Ryan From: jason.aar...@dimensiondata.com To: ryanh...@outlook.com; george.hend...@l-3com.com; cisco-voip@puck.nether.net Subject: RE: [cisco-voip] CUCILYNC Voicemail login issues Date: Tue, 13 Jan 2015 14:46:50 +0000 Capture the packets via Wireshark/network. From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Ryan Huff Sent: Tuesday, January 13, 2015 9:19 AM To: george.hend...@l-3com.com; cisco-voip@puck.nether.net Subject: Re: [cisco-voip] CUCILYNC Voicemail login issues Have you reconfirmed all your integration credentials? You might not get a directory error because the bind request might not even be making it to your directory server. Did anything change about the directory server (ip address, bind account credentials, password expire ... etc)? Can the clients still talk to the directory server over the required ports? Thanks, Ryan From: george.hend...@l-3com.com To: cisco-voip@puck.nether.net Date: Tue, 13 Jan 2015 14:03:18 +0000 Subject: [cisco-voip] CUCILYNC Voicemail login issues Hey Guys, I’m seeing an issue where I am getting “invalid username or password” when trying to authenticate in CUCILYNC for Voicemail, but I don’t get an error for the Directory services. However, I can login to the Cisco PCA page just fine with my credentials. Nothing has changed with the voicemail system and all the registry entries are correct for pointing to the voicemail system for CUCILYNC. Any ideas what could cause this? Thanks, Bill _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip itevomcid
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
