Acme Packet (MOSC)

MOSC Banner

sipmsg.log not parsing correcting with log2cap

edited Jun 10, 2014 6:02PM in Acme Packet (MOSC) 1 commentAnswered

Hi all,

Not sure if this is actually an issue or causing problems, but when I download the sipmsg.log files from the SBC, sometimes log2cap is having a problem parsing INVITE messages from our Avaya SM to the SBC.  It looks like it is splitting it up into 2 messages.  Would this cause any issues with signaling or is this strictly a bug in the way sipmsg.log files are written?

----------------------------------------
Jun  9 10:26:49.067 On 167.69.188.77:5060 received from 167.69.190.75:39311
INVITE sip:+18773477444@aetna.com SIP/2.0
P-AV-Message-Id: 3_1
P-Asserted-Identity: "~Jones, Christie" <sip:2157758047@aetna.com>
Supported: 100rel, join, replaces, sdp-anat, timer
P-Charging-Vector: icid-value="AAS:8699-369d24801e3fc53365383d69902"

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