Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2207298.1
Update Date:2017-05-17
Keywords:

Solution Type  Problem Resolution Sure

Solution  2207298.1 :   SBC sending BYE to Session Participants After 300 Seconds  


Related Items
  • Acme Packet 4600
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Session Delivery Network>SN-SND: Acme Service Provider
  •  


SBC sending BYE message to both side of the call after 300 seconds.

In this Document
Symptoms
Cause
Solution


Created from <SR 3-13675004901>

Applies to:

Acme Packet 4600 - Version S-Cx6.4.0 to S-Cz7.3.0 [Release S-Cx6.0 to S-Cz7.0]
Information in this document applies to any platform.

Symptoms

Customer reports that chat session was getting closed after some time.

Wireshark traces showed that SBC was closing the session by sending BYE to both side of the call.

While troubleshooting this report, we suspected customer was using MSRP session for Instant Messaging hence asked them to modify following parameter under Media-Manager :

tcp-subsq-guard-timer 300

As per the ACLI Guide : t

cp-subsq-guard-timer
Allowable command values: 0 to 999999999 (seconds)
Default value: 300

Timer Expiration:
Initiates tear down of the TCP connection. In the possible, but unlikely event that the value assigned to this timer is less than the value assigned to the MSRP interval timer, expiration initiates forwarding of the delayed BYE request to the recipient MSRP endpoint and tear down of the TCP connection.

This did not resolve the behavior.

Cause

The customer chat session is established externally via UDP ports and only the signaling was going via SBC.   Since no media was received, SBC was sending the BYE after 300 seconds based on the initial-guard-timer = 300 seconds in Media-Manager.

Customer had the following configuration :

media-manager
  state                   enabled
  latching                enabled
  flow-time-limit         86400
  initial-guard-timer     300
  subsq-guard-timer       300
  tcp-flow-time-limit     86400
  tcp-initial-guard-timer 300
  tcp-subsq-guard-timer   300

Solution

To resolve this behavior, customer was advised to configure the initial-guard-timer to a higher value and test.

Note: Instead of media-manager global configuration, we asked customer to configure the initial-guard-timer in the associated REALMS, since it should not affect other realms and calls.

 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback