When the SIP trace logs are printed out, is it possible to also print the outbound destination IP of outgoing messages, and the remote IP of incoming messages? i.e. the IP of who we are sending to or receiving from
This topic has been locked.
8 replies Latest Post - 2011-05-26T17:14:30Z by cheungda
Pinned topic Possible enhancement to SIP trace logs?
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2011-05-26T17:14:30Z at 2011-05-26T17:14:30Z by cheungda
Re: Possible enhancement to SIP trace logs?2011-05-25T12:26:02Z in response to cheungdaHi Darryl,
When you enable the Websphere SIP container traces you can see the ip address of client in in coming and out going messages.
Here you can see an example from the traces:
In coming message:
4/12/11 13:49:38:795 IDT0000001c Dispatcher 3 Dispatcher 952 bytes received from 22.214.171.124:34512/UDP
<raw packet is hidden>
4/12/11 13:49:38:803 IDT0000001c TransportComm 3 TransportCommLayerMgr onMessage In Message:
PUBLISH sip:AsyncAPITest11@126.96.36.199:5064 SIP/2.0
CSeq: 1 PUBLISH
Via: SIP/2.0/UDP 188.8.131.52:34512;branch=z9hG4bK2578e2a30bc50d8c520735458f7c26a8
Via: SIP/2.0/UDP 184.108.40.206:16000;ibmmi=0
Authorization: <hidden value>
In outgoing message:
4/12/11 13:49:39:041 IDT00000029 TransportComm 3 TransportCommLayerMgr createConnection from sip:220.127.116.11:5060;udpto 18.104.22.168:34512/UDP
4/12/11 13:49:39:042 IDT00000029 TransportComm 3 TransportCommLayerMgr TransportCommLayerMgr
OPTIONS sip:pink.haifa.ibm.com:5064 SIP/2.0
CSeq: 2 OPTIONS
Via: SIP/2.0/UDP 22.214.171.124:5060;ibmsid=server1.1302604909642.0_2_1;branch=z9hG4bK461958635965982
When your deployment has only standalone server the above traces should give you what you need, when you are using cluster with proxy deployment you can get the same information from the proxy traces.
Re: Possible enhancement to SIP trace logs?2011-05-25T14:20:30Z in response to SystemAdminThat's strange, we don't see these lines
4/12/11 13:49:38:795 IDT 0000001c Dispatcher 3 Dispatcher 952 bytes received from 126.96.36.199:34512/UDP
4/12/11 13:49:39:041 IDT 00000029 TransportComm 3 TransportCommLayerMgr createConnection from sip:188.8.131.52:5060;udp to 184.108.40.206:34512/UDP
We do see everything after In Message or Out Message and the SIP message itself. Do the lines with the IP address come from the same logger?
Re: Possible enhancement to SIP trace logs?2011-05-25T16:01:13Z in response to SystemAdminWAS 220.127.116.11 with CEA feature pack 5
We wanted to redirect the SIP logs into their own file, separate from SystemOut, so we grabbed the logger for com.ibm.ws.sip.stack.transaction.transport.TransportCommLayerMgr . If we use com.ibm.ws.sip.* will we get too much information?
Re: Possible enhancement to SIP trace logs?2011-05-25T19:00:07Z in response to cheungdaYou can enable the com.ibm.ws.sip.stack.dispatch.Dispatcher=all.
Other option is to look at the messages that are being printed in the traces, you will see that in incoming message a new header was added called "IBM-Client-Address" this header includes the client ip address.
in the outgoing requests you will see a new header called "IBM-Destination" this header includes the address of the remote client.
Re: Possible enhancement to SIP trace logs?2011-05-26T15:57:07Z in response to cheungdaIn this case you are probably using standalone server, those headers are being added when running in a cluster with a SIP proxy in front of the sip containers.
Did you try to enable the new trace string that I sent you? do you still have problems seeing the ip addresses when this traces string is enabled?