Disconnected by system in Log but call has 1 hour duration

1. Brekeke Product Name and version:
Brekeke SIP Server , Version 2.4.8.6 Advanced
2. Java version:
1.5.0_17
3. OS type and the version:
SunOS 5.10
4. UA (phone), gateway or other hardware/software involved:
N/A
5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/ ... terns.html :
http://www.brekeke-sip.com/bbs/network/ ... terns.html
6. Your problem:

The session that was received by the person i sent this call to their system didn’t get any messages “Cancel” or “Bye” and this call stuck and had duration 1 hour. In my logs it shows ", Disconnected by system, -1"

Please advise on what the problem here is and how to go about fixing such

Which value did you set at the [Talking Timeout] in the SIP Config page?

Talking Timeout (ms) = 259200000

The two calls in question disconnected @ 25 seconds/@ 32 seconds.


Thoughts?

Was the call disconnected just after 1 hour?

Yes, this is what the receiving party explained to me that the call was a duration of 1 hour. The one that was 32 seconds on our end and gave the disconnect message in our logs.

EDIT:
Any update? Suggestions?

Do you have "net.sip.timeout.bye" settings in the [Configuration] > [Advanced] page, or the "sv.properties" file?

If yes, which value do you have?

No we don't have that set, what would be the ideal setting for that?

Please advise. Thanks!!


EDIT:

net.sip.timeout.bye=true

is that what you want me to add and test? or magical number i can try?

You can set a value in millisecond.
For example: 20min
net.sip.timeout.bye=1200000

It means the SIP Server will end a session after 20min which is at closing phase.

Also I doubt.... are you using any session plugin which has a timer??

file.log.plugin = *********.ShutdownCheck
net.sip.fixed.addrport.uas = true
^
That's the settings in total under Config>Advanced tab in GUI

I don't see anything else that could be affecting,nothing in the dial plan would affect this either right:

Here is the the only dial plan i see that built deals with logging:
It's the first Priority Rule in our Dial Plan

Deploy Patterns:
&net.sip.len.logging=15
$session=*.Logging
$continue=true

Note that *.Logging is actually a custom rule that was given to my group in regards to logs, but those are the only things I am aware of.

* = company name censored

Please advise and thanks for continuing to follow up.

I see.

One more thing I want to know... were you using the RTP-Relay when the call got the "Disconnected by system"?
Because it has the timeout.

Configuration(Tab)>RTP(Tab)

RTP relay = Auto
RTP relay (UA on this machine) = Off

What's the [RTP Session Timeout]'s value?

RTP Session Timeout (ms) = 600000

Your these settings seem no problem.

Does the disconnection issue still persist?

Well..it did for that call,i guess the question is since were using the latest version, should we have this setting?

net.sip.timeout.bye

Should we add this and have the client retry? I'm not sure how many times it's happened overall. I read in earlier versions it was a bug.

You don't have to set "net.sip.timeout.bye" because it has default value.

Does the caller or callee have a problem in sending CANCEL and BYE?

Thanks alot!

i have spoken with the group here and since things are configured correctly, we can't see where the BYE or CANCEL was sent, so we've addressed this with client and are leaving it at that since this is just on one call, and since this was a known bug in older versions,we'll chalk it up to that.


Appreciate your help in this resolution!



Kent C.