Acme Packet (MOSC)

MOSC Banner

SIP/2.0 500 Internal Server Error

edited Sep 16, 2020 5:06PM in Acme Packet (MOSC) 9 commentsAnswered ✓

I am installing a new SBC and don't seem to be able to route calls via it.  My call flow goes as below when I try and make a call and all the failure lists is SIP/2.0 500 Internal Server Error.  The ingress realm is correct but the correct egress realm is not displayed.  Test-policy with all my call details has the egress realm correctly identified.

INVITE (4094873) 

Status:100 (4094873) 

MEDIA FLOW ADD, ID=33554437, DIRECTION=CALLING

MEDIA FLOW ADD, ID=33554438, DIRECTION=CALLED

CALL FAILURE!! STATUS=500, REASON=Internal Server Error

Status:500 (4094873) 

ACK (4094873) 

I am wondering if anyone has any idea how I can get more insight into the cause of the 500 error.  I have tried tailing the sipmsg.log but it's not giving me anymore detail on the error so I am hoping there are some logs that I am not aware of that might give me a little more detail on exactly what the problem is.

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