I have a problem I am trying to work out here. I saw a similar discussion however that fix did not work for me. So right now I have deployed CUPS v7.07 and have integrated it with CUCM v7.1. Everything seems to be working on all the Diagnostics tests I have run so far. Server Health on IM clients seems to be all good.
I have integrated CUPS with LDAP but CUCM is NOT integrated with LDAP which is okay since as I understand it LDAP is used to add and find the contacts for the CUPC.
Status changes work good, calls work etc. When I add a contact or just attempt to IM a contact from the search pane the contact name shows but next to the name is a little gray circle that to me should be green.
I type a message and when I hit enter I get "John Doe did not recieve your message because it could not be delivered"
Things I have checked
1. Incoming and Outgoing ACL's both set to ALL
2. I was not sure of DNS at the time of deployment so my server name is actually the IP address
3. Under SIP Proxy Domain I have XXXX.local under the federation routing paramters I have CUPS1.XXXX..local- since the name was initially CUPS1
4. I do not have any type of client firewalls running.
A similar post suggested that under the Proxy Domain Field that the user actually just put the FQDN of the server with as in MISD1. but when I try that it does not allow me to.
I'm having an issue similar to this however I believe the problem is to do with the fact the usernames are configured as 'joe bloggs' with the space, apparently this is a valid character with in AD and seems to be causing problems with IM's.
I`m having the same issue as the one listed here, in CUPS 7.0.5, when the users try to send a message to eachother they get the response: [Person] did not receive your message because the message could not be sent. We are running CUCM 7.1.3 and both CUP and CUCM are sync with LDAP. I have checked all the suggestions listed here and everything seems to be properly configured do you guys have any other suggestion?
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...