Acme Packet (MOSC)

MOSC Banner

OCSM not responding to SBC

in Acme Packet (MOSC) 1 commentAnswered

Hello,

We have installed and configured a new Session Monitor (OCSM 6.1), which is going to replace an existing one. Selinux is disabled.
Everything is set up correctly (we assume), but we can't see any call records on the new Session Monitor.

We have added a second monitor collector (10.167.197.7) to the SBC's system-config:
comm-monitor
state enabled
sbc-grp-id 0
tls-profileqos-enable enabled
interim-qos-update enabled
monitor-collector
address 10.71.78.88
port 4739
network-interface wancom0:0
monitor-collector
address 10.167.197.7
port 4739
network-interface wancom0:0

But, when we look at the commMonitord log file on the SBC, we see:

Apr 24 11:07:50.344 [COMM] (0) Reconnect Trying to reconnect
Apr 24 11:09:20.345 [COMM] (0) Reconnect Trying to reconnect

or sh comm-monitor errors:

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