Acme Packet (MOSC)

MOSC Banner

Inactivity Timers on media Flow: Mismatch between config value and setting shown in log.mbcd.

edited Jun 7, 2013 9:37PM in Acme Packet (MOSC) 2 commentsAnswered

Hello,

 

this concerns a 4250 SBC running in BG mode. 

We have set the media guard timers in media-manager as shown here :

 

maximum-duration=86400

initial-guard = 300

subs-guard=300.

 

We setup a call and after a few FLOW modifications (latching signals, updating of remote descriptor), the final [FLOW] event shows that the flow has been installed with init_flow_guard= 30.

 

Jun  3 19:38:23.108 [FLOW] install flow timer2569844 max_flow_guard= 86400 inact_flow_guard= 300 init_flow_guard= 30

 

Is there a possible explanation why the config value seems to be overruled here? 

 

thanks

Marios

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