Acme Packet (MOSC)

MOSC Banner

Enabling and disabling debug logging

edited Jan 5, 2013 5:36AM in Acme Packet (MOSC) 10 commentsAnswered

SIP Logs


##########################################################
Note: Debug logging settings require significant CPU usage, please only use debug logging settings during maintenance windows or low call traffic periods for troubleshooting purposes.
#########################################################

The sipmsg.log is most often used to troubleshoot SIP call flow issues. Logs all SIP messages that pass through the SBC, so this requires significant CPU resources (typically adds about 10-20% CPU):
To enable: notify sipd siplog
To disable: notify sipd nosiplog

SIP debug logs are also required when troubleshooting SIP call flow problems. The following command enables a subset of the full logging behavior of sipd on the Session Director:
To enable: notify sipd debug

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center