Problem: I have two Presence Servers and I want to enable Presence Status and IM communication between them. I have setup Federation, but I am only getting one-way communication. By that I mean, a user associated with Site A can see the presence status of users at Site B and can send them instant messages, which they receive. However, users associates with Site B only see Site A users as off-line and cannot send IM messages, or even reply to IMs sent.
Basic info: Site A is running CUPS 188.8.131.5200-18 and Site B is running CUPS 184.108.40.20600-17. Also, both servers are connected via SIP trunk with the same CUCM cluster.
Here's my Federation setup...
I created a Federated Domain on each server. Site A: Domain Name: ci.brooklyn-center.mn.us Description: Brooklyn Center Integration Type: Inter-Domain CUP to CUP
Site B: Domain Name: logis.org Description: LOGIS Integration Type: Inter-Domain CUP to CUP
Then I created a Static Route on each server Site A: Destination Pattern: .us.mn.brooklyn-center.ci.* Description: BC Presence Server Next Hop: IP address of Site B CUPS Next Hop Port: 5060 Route Type: Domain Protocol Type: TCP Priority: 1 Weight: 1 Allow Less-Specific Routes: On In Service: On
Site B: Destination Pattern: .org.logis.* Description: LOGIS Presence Next Hop: IP address of Site A CUPS Next Hop Port: 5060 Route Type: Domain Protocol Type: TCP Priority: 1 Weight: 1 Allow Less-Specific Routes: On In Service: On
I configured the Proxy Configuration Setting on each to the following: Method/Event Routing Status: On Prefered Proxy Listener: Default Cisco SIP Proxy TCP Listener
Also, Under Presence -> Settings, I checked "Enable Email ID for Federation" on both sides.
There is no firewall between the two Presence Servers and no firewall between the clients I am using for testing.
Question: Can anyone see a problem with my Federation configuration? What trace files should I look at to find the problem?
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...