Disconnected by system in Log but call has 1 hour duration
Moderator: Brekeke Support Team
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
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
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.
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.
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.
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.