Acme Packet (MOSC)

MOSC Banner

logs getting slammed with Unknown Session errors

edited Mar 21, 2013 3:47PM in Acme Packet (MOSC) 3 commentsAnswered

I have 450 stations registered via a 4500 through to an Avaya session manager and the call load is approximately 3,000 calls per hour.  After about 1.5 hours calls stop working and the sipd log starts getting flooded with the following messages to the point where even registrations get lost:

 

----------------------------------------

01:48.886 On 127.0.0.1:2945 received from 127.0.0.1:2944
0000: ac 3e fd 01 00 05 95 81 00 1c 10 00 01 52 02 00 .>...........R..
0010: 00 00 00 00 11 24 00 01 52 03 00 0a 36 00 07 92 .....$..R...6...
0020: 00 04 00 00 00 01 ......
Transaction = 365953 {
Context = 86530 {
Notify = 86531 {
ObsEvent {
mbc/start=1
}
}
}
}
----------------------------------------

01:48.886 On 127.0.0.1:2945 sent to 127.0.0.1:2944
0000: ac 3e fd 02 00 05 95 81 00 2c 10 00 01 52 02 00 .>.......,...R..
0010: 00 00 00 00 21 24 00 01 52 03 00 1a 37 01 9b 00 ....!$..R...7...
0020: 15 55 6e 6b 6e 6f 77 6e 20 73 65 73 73 69 6f 6e .Unknown session
0030: 3d 38 36 35 33 30 =86530
Reply = 365953 {
Context = 86530 {
Notify = 86531 {
Error=411 { "Unknown session=86530" }
}
}
}
----------------------------------------

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