IM and Presence Service Tracing
On the IM and Presence Service node, the SIP Proxy is responsible for SIP request routing, while the XCP SIP Federation Connection Manager is responsible for SIP Protocol Translation between Microsoft SIP and native XMPP. Therefore, these services are central to the SIP partitioned intradomain federation integration between IM and Presence Service and Skype for Business/Lync/OCS.
The XCP Router is a core service of IM and Presence Service. It determines whether the request recipient is a Microsoft server user or an IM and Presence Service user.
The locations of the log files are as follows:
-
Logs for XCP SIP Federation Connection Manager: /var/log/active/epas/trace/xcp/log/sip-cm-3_000*.log
-
Logs for SIP Proxy: /var/log/active/epas/trace/esp/sdi/esp000*.log
-
Logs for XCP Router: var/log/active/epas/trace/xcp/log/rtr-jsm-1_000*.log
Example of SIP Proxy Logging
2:26:18.719 |PID(25333) sip_protocol.c(5964) Received 536 bytes TCP packet from 10.53.56.17:34282SUBSCRIBE sip:ysam@implync.net SIP/2.0^M From: <sip:fbear@implync.net>;tag=a4cdaec0-1138350a-13d8-45026-4d755b8a-2162aa7a-4d755b8a^M To: <sip:ysam@implync.net>^M Call-ID: a30386f0-1138350a-13d8-45026-4d755b8a-2c25871c-4d755b8a^M CSeq: 1 SUBSCRIBE^M Via: SIP/2.0/TCP 10.53.56.17:5080;branch=z9hG4bK-4d755b8a-926d95b4-3c330144^M Expires: 7446^M Accept: application/pidf+xml, application/cpim-pidf+xml^M User-Agent: Cisco-Systems-Partitioned 8.0^M Max-Forwards: 70^M Event: presence^M Contact: <sip:10.53.56.17:5080;transport=TCP>^M Content-Length: 0^M … 22:26:18.719 |ID(25333) sip_sm.c(4977) SIPGW Partitioned Fed UA Header found in this request 22:26:18.719 |ID(25333) sip_sm.c(5010) This is a partitioned federation request, skip User Location DB lookup 22:26:18.719 |ID(25333) sip_sm.c(5200) This is an outbound Partitioned federation request. 22:26:18.719 |Mon Mar 07 22:26:18 2011] PID(25333) mod_sip_routing.c(1435) Routing: dipping for cuplcs.net 22:26:18.719 |Mon Mar 07 22:26:18 2011] PID(25333) mod_sip_routing.c(1473) Routing: Found domain route for cuplcs.net:10.53.56.18:5061;TLS pwf 1:1:5 22:26:18.719 |ID(25333) sip_dns.c(811) "A" Query for 10.53.56.18 successful, Got 1 IP addresses 22:26:18.719 |ID(25333) sip_dns.c(139) A Record : 10.53.56.18
Example of SIP Federation Connection Manager Logging
The following is a extract from an outbound request log:
21:48:44.277 |SIPGWDir.cpp:463: [FROM XMPP] <presence from='fbear@implync.net' to='ysam@implync.net' type='probe'/>... ... 21:48:44.743 |SIPGWController.cpp:622: Skipping DNS lookup: <presence from='fbear@implync.net' to='ysam@implync.net' type='probe'/> 21:48:44.743 |SIPGWController.cpp:704: Entering _handleOutContinue: <presence from='fbear@implync.net' to='ysam@implync.net' type='probe'/> 21:48:44.743 |SIPGWController.cpp:989: _findSession (JID): local(fbear@implync.net) remote(ysam@implync.net) 21:48:44.743 |SIPGWController.cpp:999: _findSession: Session not found 21:48:44.743 |SIPHostInfo.cpp:82: hostinfo(0x09a10ce8) refInc: 3 cuplcs.net:cuplcs.net 21:48:44.743 |SIPGWSession.cpp:58: Creating SIPGWSession sess=0x09a5a090 local=fbear@implync.net remote=ysam@implync.net 21:48:44.743 |SIPGWController.cpp:1017: _findSession: Made new session: sess=0x09a5a090 local(fbear@implync.net) remote(ysam@implync.net) 21:48:44.743 |SIPGWSession.cpp:990: sess=0x09a5a090 Entering handleOut: <presence from='fbear@implync.net' to='ysam@implync.net' type='probe'/> 21:48:44.743 |SIPGWSession.cpp:1090: _createOutgoingSubs local=fbear@implync.net, remote=ysam@implync.net 48:44.744 |SIPSubs.cpp:1037: from=<sip:fbear@implync.net> to=<sip:ysam@implync.net> local_contact=sip:10.53.56.17:5080;transport=TCP remote_contact=sip:ysam@implync.net
Example of XCP Router Logging
12:29:24.762 |debug sdns_plugin-1.gwydlvm453 sdns_plugin handling:<presence type='subscribed' to='ysam@implync.net' from='bbird@implync.net'><status>Already Subscribed</status></presence> 12:29:24.762 |debug ConnectionPool.cpp:166 connection pool checkout: ccm2/dbuser (success) 12:29:24.762 |debug IdsODBC.cpp:648 Performing SQL operation select userid, jsmid from enduser, enterprisenode where my_lower(xep106userid) = my_lower(?) and primarynodeid=id 12:29:24.763 |debug ODBCConnection.cpp:315 (elapsed 0.002407) select userid, jsmid from enduser, enterprisenode where my_lower(xep106userid) = my_lower(?) and primarynodeid=id 12:29:24.763 |debug CUPDatabaseAlgorithm.cpp:311 This is probably a Partitioned OCS user ... redirecting to cm-3-sip-fed-s2s.gwydlvm453 component 12:29:24.763 |debug IdsODBC.cpp:229 (elapsed 0.000137) rollback 12:29:24.763 |debug ConnectionPool.cpp:207 connection pool checkin: ccm2/dbuser (success) 12:29:24.763 |debug sdns_plugin-1.gwydlvm453 sdns_plugin redirecting to: cm-3-sip-fed-s2s.gwydlvm453
You can enable debug tracing for the SIP Proxy, XCP SIP Federation Connection Manager and XCP Router on the Cisco Unified IM and Presence Service Serviceability user interface.
Configure Tracing on the IM and Presence Service
The following procedure describes how to configure tracing for the SIP Proxy, XCP SIP Federation Connection Manager and XCP Router services on the Cisco Unified IM and Presence Serviceability GUI. Repeat this procedure for each service that you want to configure for tracing.
Caution |
Debug level tracing can affect system performance. Enable debug level tracing only when required and reset to default log settings after the investigation is complete. |
Procedure
Step 1 |
Log in to the Cisco Unified IM and Presence Serviceability user interface. Choose . |
Step 2 |
Choose the IM and Presence Service node, and click Go. |
Step 3 |
Choose IM and Presence Services from the Service Group drop-down list, and click Go. |
Step 4 |
From the Service drop-down list, choose one of the following options and click Go:
|
Step 5 |
Check the check box for Trace On. |
Step 6 |
In the Trace Filter Settings area, choose the Debug Trace Level from the drop-down list. If you want to enable debug level tracing on the traces choose Debug. |
Step 7 |
When you configure tracing for the SIP Proxy, there are a number of trace options under Trace Filter Settings. Check the check boxes for the following traces:
|
Step 8 |
Click Save. See the Cisco Unified IM and Presence Serviceability Online Help for more information about initiating debug tracing for each of these services. |