Topic
8 replies Latest Post - ‏2011-05-26T17:14:30Z by cheungda
cheungda
cheungda
20 Posts
ACCEPTED ANSWER

Pinned topic Possible enhancement to SIP trace logs?

‏2011-05-24T14:08:07Z |
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

Darryl
Updated on 2011-05-26T17:14:30Z at 2011-05-26T17:14:30Z by cheungda
  • SystemAdmin
    SystemAdmin
    45 Posts
    ACCEPTED ANSWER

    Re: Possible enhancement to SIP trace logs?

    ‏2011-05-25T12:26:02Z  in response to cheungda
    Hi 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 IDT 0000001c Dispatcher 3 Dispatcher 952 bytes received from 9.148.61.172:34512/UDP
    <raw packet is hidden>
    4/12/11 13:49:38:803 IDT 0000001c TransportComm 3 TransportCommLayerMgr onMessage In Message:
    PUBLISH sip:AsyncAPITest11@9.148.61.172:5064 SIP/2.0
    IBM-Client-Address: 9.148.61.172:16000;local-address=9.148.61.172:5064
    Content-Length: 396
    Event: presence
    Expires: 65
    Call-ID: 1-5163@9.148.61.172
    CSeq: 1 PUBLISH
    Via: SIP/2.0/UDP 9.148.61.172:34512;branch=z9hG4bK2578e2a30bc50d8c520735458f7c26a8
    Via: SIP/2.0/UDP 9.148.61.172:16000;ibmmi=0
    Content-Type: application/pidf+xml
    To: sip:AsyncAPITest11@hades.com
    Authorization: <hidden value>
    From: sip:AsyncAPITest11@hades.com;tag=1
    Max-Forwards: 70
    Require: simple

    In outgoing message:
    4/12/11 13:49:39:041 IDT 00000029 TransportComm 3 TransportCommLayerMgr createConnection from sip:9.148.61.172:5060;udp to 9.148.61.172:34512/UDP
    4/12/11 13:49:39:042 IDT 00000029 TransportComm 3 TransportCommLayerMgr TransportCommLayerMgr
    Out Message:
    OPTIONS sip:pink.haifa.ibm.com:5064 SIP/2.0
    From: sip:asaf@ibm.com;tag=6707593433811924_server1.1302604909642.0_2_1
    To: sip:asaf@ibm.com
    Call-ID: 1740047156947725@9.148.61.172
    Max-Forwards: 70
    CSeq: 2 OPTIONS
    Custom-Async: publish,server1.1302604909642.0_1
    Via: SIP/2.0/UDP 9.148.61.172:5060;ibmsid=server1.1302604909642.0_2_1;branch=z9hG4bK461958635965982
    IBM-PO: 0
    IBM-Destination: <sip:pink.haifa.ibm.com:5064;transport=udp>
    Content-Length: 0

    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.
    • cheungda
      cheungda
      20 Posts
      ACCEPTED ANSWER

      Re: Possible enhancement to SIP trace logs?

      ‏2011-05-25T14:20:30Z  in response to SystemAdmin
      That's strange, we don't see these lines

      4/12/11 13:49:38:795 IDT 0000001c Dispatcher 3 Dispatcher 952 bytes received from 9.148.61.172:34512/UDP
      or
      4/12/11 13:49:39:041 IDT 00000029 TransportComm 3 TransportCommLayerMgr createConnection from sip:9.148.61.172:5060;udp to 9.148.61.172: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?

      Darryl
      • SystemAdmin
        SystemAdmin
        45 Posts
        ACCEPTED ANSWER

        Re: Possible enhancement to SIP trace logs?

        ‏2011-05-25T14:25:23Z  in response to cheungda
        What is the WerbSphere version that you are using?
        What is you trace string? it should be com.ibm.ws.sip.*=all
        • cheungda
          cheungda
          20 Posts
          ACCEPTED ANSWER

          Re: Possible enhancement to SIP trace logs?

          ‏2011-05-25T16:01:13Z  in response to SystemAdmin
          WAS 7.0.0.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?
          • SystemAdmin
            SystemAdmin
            45 Posts
            ACCEPTED ANSWER

            Re: Possible enhancement to SIP trace logs?

            ‏2011-05-25T19:00:07Z  in response to cheungda
            You 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.
            • cheungda
              cheungda
              20 Posts
              ACCEPTED ANSWER

              Re: Possible enhancement to SIP trace logs?

              ‏2011-05-26T15:39:42Z  in response to SystemAdmin
              I don't see any header IBM-Client-Address or IBM-Destination in the SIP messages.

              Darryl
              • SystemAdmin
                SystemAdmin
                45 Posts
                ACCEPTED ANSWER

                Re: Possible enhancement to SIP trace logs?

                ‏2011-05-26T15:57:07Z  in response to cheungda
                In 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?
                • cheungda
                  cheungda
                  20 Posts
                  ACCEPTED ANSWER

                  Re: Possible enhancement to SIP trace logs?

                  ‏2011-05-26T17:14:30Z  in response to SystemAdmin
                  I enabled the Dispatcher logger you mentioned and I see the IP addresses as in the previous message. Thanks!

                  Yes, we are running standalone without a proxy.