My Oracle Support Banner

6300/4600/3900 SBC server stops sending data to Oracle Communication Session Monitor (Doc ID 2330460.1)

Last updated on MAY 18, 2023

Applies to:

Acme Packet 6300 - Version S-Cz7.3.0 and later
Acme Packet 3900 - Version E-Cz7.4.0 and later
Oracle Communications Session Monitor - Version 3.3.90 to 4.3 [Release 3.0 to 4.0]
Acme Packet 4600 - Version S-Cz7.3.0 and later
Information in this document applies to any platform.

Symptoms

6300/4600/3900 SBC server(s) configured as SBC probes for Oracle Communications Session Monitor stops sending data (though originally this was working)

The SBC's log file: log.commMonitord may show:

CommMonitorServerReq::process: no agent for socket

And output from the command "show comm-monitor" will show an increase in the "internal msg dropped" counter e.g.

 

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.