Acme Packet (MOSC)

MOSC Banner

OCSM does not detect the call termination.

in Acme Packet (MOSC) 4 commentsAnswered ✓

Hello,

I faced a problem of call termination on OCSM: it does not recognize BYE, if it is sent from IP address other than one, included in INVITE transaction. We have more than one S-CSCF in the core. A session can be established with first S-CSCF and termination can be sent from second S-CSCF, and OCSM ignores those terminations.

In result we get following situation: two external call legs are in "finished" state, and two internal call legs, where BYE was ignored are in "established" state. I am emphasizing - the call is already released in reality.

The worst consequence of this error is that number of active calls on OCSM is constantly increasing and exceeds the license. We have to reboot OCSM to clear the hanged active calls. Have you ever meet such problem? How to deal with it?

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

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center