No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.

Knowledge Base

FAQ-SoftCo sends update message to terminal and has no response, causing call disconnect after 5 minutes

Publication Date:  2012-10-11  |   Views:  208  |   Downloads:  0  |   Author:  q00229199  |   Document ID:  EKB1000016991


Issue Description

Certain bureau has 1 SoftCo9500 and some IPphone, SoftCo version is V100 R002B06c, to avoid talk hang to death, open heart beat switch: config modify sip parameter usesessiontimer yes
Heart beat default time is 300s (We can change with the order of config modify sip parameter sessioninterval  xxx) 
But during the test of calling, the call halts after 5 minutes.

Alarm Information


Handling Process

Close heart beat message:
config modify sip parameter usesessiontimer no
dial to test again, the malfunction disappeared.

Root Cause

The malfunction is not individual phenomenon; it exists during calling inside the bureau and outside the bureau. It may because of the wrong setting of some timer.
Catch the package to analyze calling procedure, find out that after the call is established for 150 secnonds, SoftCo sends a UPDATE message to IPphone, but doesn’t receive response.
SoftCo thinks IP terminal stops, and release the call
Confirm through SIP parameter.

[%SoftCo5816(config)]$show sip parameter     

SIP Parameter

T1(*100ms) T2(*100ms) T4(*100ms) MinSubExpires(min) SrvPort MinRegExpires(min)
---------- ---------- ---------- ------------------ ------- ------------------
5          40         50         5                  5060    2                 
MaxRegExpires(min) MinSessionInterval(s) SessionInterval(s) UseCompact
------------------ --------------------- ------------------ ----------
60                 90                    300                No        
====  Command executed success !  ====

Catch the package in upward port of IPphone, find out there is no UPDATE message sent. We can judge that it is the network reason that cause UPDATE can’t sent to IPphone side normally, IPphone can’t response normally, and make SoftCo thinks IPphone is offline, and disconnect.


The heart beat message normally use private protocol, it can be used when they passed the test between equipments, and we need to pay attention to the affect that network cause, we can’t judge the network is normal only when the network is reachable and can be pinged through or it call ring.