[cisco-voip] Unable to use phone to make calls in CUCILYNC/JABBER

[george.hendrix at l-3com.com]

It is set to 389.  However, it has been set like that for quite a while and it was working with it set to 389.

-Bill


From: Eric Pedersen [mailto:PedersenE at bennettjones.com]
Sent: Tuesday, September 18, 2012 10:54 AM
To: Hendrix, George (Bill) @ NSS - STRATIS; cisco-voip at puck.nether.net
Subject: RE: Unable to use phone to make calls in CUCILYNC/JABBER

Is CUCM configured to use global catalog port 3268 on the domain controllers? I had CTI issues when using the standard LDAP port 389.





[Bennett Jones]

Eric Pedersen

Senior Network and VoIP Analyst, Bennett Jones SLP

4500 Bankers Hall East, 855 - 2nd Street SW, Calgary, AB, T2P 4K7
P. 403 298 4498 | F. 403 265 7219
E. pedersene at bennettjones.com<mailto:pedersene at bennettjones.com>




From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of george.hendrix at l-3com.com
Sent: 18 September 2012 5:08 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Unable to use phone to make calls in CUCILYNC/JABBER

Hey Guys,

  We have a lot folks that are suddenly unable to make calls in CUCILYNC using their phone.  We've been testing Jabber and the same is also the case with Jabber. If I set it to use my computer for calls, there are no errors.  However, if I try to set it to use my phone for calls, it doesn't work.  There have been NO changes to the phones/lines associated with the users nor have there been any changes to the user accounts.  The ONLY thing that has recently happened was that much of our AD environment had to be rebuilt, and one of the LDAP servers in the CUCM LDAP configuration was rebuilt. In CUCILYNC, below is a screenshot of the error we're seeing.  The error I kept getting every time I would try to set my phone to make calls, it would be the error "Device Error. Service internal error. [101].  I have checked CTI Manager in CUCM and that doesn't appear to be the issue.  I have checked all the line/device/user associations and all of those seem to be in place as well.  Any idea of what to check and what this issue can be?

[cid:image004.png at 01CD94DD.38949FC0]

Thanks,
Bill Hendrix


The contents of this message may contain confidential and/or privileged

subject matter. If this message has been received in error, please contact

the sender and delete all copies. Like other forms of communication,

e-mail communications may be vulnerable to interception by unauthorized

parties. If you do not wish us to communicate with you by e-mail, please

notify us at your earliest convenience. In the absence of such

notification, your consent is assumed. Should you choose to allow us to

communicate by e-mail, we will not take any additional security measures

(such as encryption) unless specifically requested.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120918/6dac26b5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 13272 bytes
Desc: image001.jpg
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120918/6dac26b5/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 25598 bytes
Desc: image002.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120918/6dac26b5/attachment.png>