When troubleshooting the SIP container session repository, you might need the SIP session details to dump to a specified trace file.
You can use the SIP session memory dump utility to help debug problems related to SIP container sessions. The SIP container uses the SipContainerMBean method to perform several serviceability type operations on the SIP container, including the initiation of a server quiesce through wsadmin (command-line interface). This task describes how you can use the SipContainerMBean method to dump SIP Application Session and SIP Session information that is contained in the in-memory session repository for SIP containers. By configuring the SIPContainerMBean method to use various trace methods, you can specify the SIP session details to dump to the specified trace file.
When the session dump methods are started using wsadmin scripting, the requested information about the sessions prints, by default, into the SystemOut.log file or sent to a predefined source, if set through the setDumpMethod method.
If you use the succinct session dump methods, only the session IDs are printed for every dump method execution.
The trace printouts occur per SIP application; therefore, the sorting of all the SIP session data structures occurs before printing. You can use the SIPContainerMBean dump facility for a production server by dispatching the work to a low priority thread so that all dumps are on a separate thread and the tracing does not affect the call processing latency of the overall system.
The dump distinguishes between a transaction user that has a SIP session created versus a transaction user that has no SipSession object. Also included in the dump, in a delineated fashion, are SIP sessions that no longer exist, those that are no longer valid, or those that exist at the time of the trace snapshot.
Method | Description |
---|---|
dumpAllSASIds() | Prints a number of all SIP application sessions and the SIP application session IDs. |
dumpAllTUSipSessionIds() | Prints a number of transaction users and the SIP session IDs within the transaction user (TU), if one exists. |
Method | Description |
---|---|
dumpAllSASDetails() | Prints a number of all SIP application sessions and the SIP application session ID details. |
dumpAllTUSipSessionDetails() | Prints a number of transaction users and details of the SIP session IDs within the transaction user (TU), if one exists. |
dumpSASDetails(String sasId) | Prints the details of the SIP application session that is specified by the sasId parameter. |
dumpSipSessionDetails(String sessionId) | Prints the details of the SIP session that is specified by the sessionId parameter. |
You have configured the SIP session memory dump utility to print the level of trace information that you want for the SIP application session and SIP session to help you troubleshoot problems with the SIP container.
$AdminControl invoke $apps dumpAllSASIds
AdminControl.invoke (apps, "dumpAllSASIds")
dump.ids.test.app1 2
local.1347524282775_8
local.1347524282775_7
This information is provided in the
following format: [SAS_ID]
$AdminControl invoke $apps setDumpMethod {{FILE} {/opt/IBM/output.log}}
$AdminControl invoke $apps dumpAllSASDetails
AdminControl.invoke (apps, "setDumpMethod", ["FILE", "/opt/IBM/output.log"])
AdminControl.invoke (apps, "dumpAllSASDetails")
dump.ids.test.app1 1
local.1348147884986_2 Sep 20,2012 16:31 DumpSasDetailsAttr;
This information is provided in the following format: [SAS_ID] [CreationTime] [attributes]
$AdminControl invoke $apps dumpAllTUSipSessionIds
AdminControl.invoke (apps, "dumpAllTUSipSessionIds")
DumpSessionsTest 1
local.1349965420866_1_0 true local.1349965420866_1_0_1
This information is provided in the following format: [TU_ID] [hasSIPSession] [SipSessionId]
$AdminControl invoke $apps dumpAllTUSipSessionDetails
AdminControl.invoke (apps, "dumpAllTUSipSessionDetails")
DumpSessionsTest 1
local.1349965420866_1_0 true local.1349965420866_1_0_1 8-8548@9.148.57.128 2 false INVITE
local.1349965420866_1 Jan 24,2013 14:41 TestSSAttr1; TestSSAttr2;
This information is provided in the following format: [TU_ID] [hasSIPSession] [SipSessionId] [Call-Id] [DialogState] [hasOutgoingTransaction] [initialMethod] [SAS_ID] [CreationTime] [attributes]
$AdminControl invoke $apps dumpSASDetails $sasId
AdminControl.invoke (apps, "dumpSASDetails ", "sasId")
local.1358950127352_20 Jan 23,2013 16:19 TestSASAttr1; TestSASAttr2;
If the requested session does not exist, an error message is given;
for example:ERROR: Requested session <local.1358950127352_20> does not exist.
$AdminControl invoke $apps dumpSipSessionDetails $sessionId
AdminControl.invoke (apps, "dumpSipSessionDetails", "sessionId")
local.1358950127352_21_20_1 local.1358950127352_21 Jan 23,2013 16:22 TestSSAttr1; TestSSAttr2;
If the requested session does not exist, an error message is given;
for example:ERROR: Requested session <local.1358950127352_21_20_1> does not exist.