SIP Call Session Logs

These logs are identified by a session ID ("SID"). The following shows an example of a SIP-session related Syslog message:

13:10:57.811 : 10.13.4.12 : NOTICE : [S=235][SID:2ed1c8:96:5] (lgr_flow)(63) UdpTransportObject#0- Adding socket event for address 10.33.2.42:5060 [Time: 04-19-2012@18:29:39]

The SID is a unique SIP call session and device identifier for the following types of SIP calls:

Gateway application: A call session is either a Tel-to-IP or an IP-to-Tel leg, where each leg is assigned a unique session number.
SBC application: A session includes both the outgoing and incoming legs, where both legs share the same session number.
Forked legs and alternative legs share the same session number.

The device identifier facilitates debugging by clearly identifying the specific device that sent the log message. Unique numbering enables filtering the information (SIP, Syslog, and media) according to device or session ID

Syntax of the session and device identifiers: [SID=<last 6 characters of device's MAC address>:<number of times device has reset>:<unique SID counter indicating the call session; increments consecutively for each new session; resets to 1 after a device reset>]

Example:

14:32:52.028: 10.33.8.70: NOTICE: [S=9369] [SID=2ed1c8:96:5] (lgr_psbrdex)(274) recv <-- OFF_HOOK Ch:4

Where:

2ed1c8 is the device's MAC address
96 is the number of times the device has reset
5 is a unique SID session number (in other words, this is the fifth call session since the last device reset)

For later software versions of Mediant Software and Mediant 9000, instead of MAC address, the SID contains the serial number.

Example of an event in syslog that includes a SIP message with OPTIONS:
11:36:54.582  10.15.45.49  local0.notice  [S=12614840] [SID=50e91b:74:353424]  OPTIONS sip:195.189.192.135 SIP/2.0
                                                                               Via: SIP/2.0/TLS sbc11.AUDCTrunk.aceducation.info:5061;alias;branch=z9hG4bKac1026719750
                                                                               Max-Forwards: 70
                                                                               From: <sip:195.189.192.135>;tag=1c942573283
                                                                               To: <sip:195.189.192.135>
                                                                               Call-ID: 286566002172202093652@sbc11.AUDCTrunk.aceducation.info
                                                                               CSeq: 1 OPTIONS
                                                                               Contact: <sip:sbc11.AUDCTrunk.aceducation.info:5061;transport=tls>
                                                                               Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUBSCRIBE,UPDATE
                                                                               User-Agent: M800B/v.7.20A.254.604
                                                                               Accept: application/sdp, application/simple-message-summary, message/sipfrag
                                                                               Content-Length: 0
Example of outgoing SIP message:
11:36:18.833  10.15.45.49  local0.notice  [S=12614761] [SID=50e91b:74:353422]  (N 11900023)  ---- Outgoing SIP Message to 52.114.75.24:5061 from SIPInterface #2 (Teams) TLS TO(#206) SocketID(10518) ---- [Time:17-02@09:36:17.003]
Example of successful classification of an IP Group entity:
11:36:18.949  10.15.45.49  local0.notice  [S=12614774] [SID=50e91b:74:353423]  (N 11900034)  Classification Succeeded - Source IP Group #2 (Teams) [Time:17-02@09:36:17.093]