Phantom Sessions in Version 3.0.6.3 Evaluation

[wayne106]

1. Brekeke Product Name and version:
Standard Version 3.0.6.3 Evaluation
2. Java version:
1.7.0_02
3. OS type and the version:
Centos 2.6.32-220.23.1.el6.x86_64 (64bit)
4. UA (phone), gateway or other hardware/software involved:
Various
5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/networkpatterns.html :
BSS server has untrust IP via firewall
6. Your problem:
We are a happy BSS customer moving to version 3 from version 2. we are testing version 3 at the moment, and one issue keeps cropping up, in the server status page we see active sessions, but when you goto the Active Sessions page, there are no active sessions. This is an issue in particular if we want to restart the service, it says there are active sessions, force restart? But actually there are no sessions.

Anyone else seen this?

Wayne

[voipwell.com]

Hello,

I saw this also but i attributed it to the testing we were doing complicated by the Realtek NIC fragmentation problem. What NIC is in your computer?

[wayne106]

It's actually a VM, running on VMware ESX ver 4, so emulated NIC.

I have the version 2 machine running under VM without issue, but it is a windows box, whereas we are using Centos for Ver 3.

[voipwell.com]

The emulated nic is still subject to the physical nic's problems, but if you had no problems with v2 it does seem to indicate that it's not that. I would still check the physical nic to see if it's realtek.

I was testing SCA and BLF in V3 PBX (windows 7) and experienced that but after i configured everything correctly it appeared to go away. If it's possible for you to eliminate any firewall for testing that may reveal a communication problem.

[wayne106]

Agreed, everytime I leave a pcap running the issue doesn't occur! will persist, however I don't think BSS is missing any signalling, more that it is failing to update the 'active sessions' counter for some reason. If the sessions were really hung, then as I have seen in the past, they would display in the active sessions page, either 'closing' or still 'active'

[voipwell.com]

Yes, I agree the sessions should show. Sorry to hear everthing might not be realtek.

I have reason to believe they may add concurrent session counting by user or ip so i wonder if it has made it's way quietly into v3 and stepped on something? If you can determine the type of call that is causing it that would help. Is it an extension to extension, extension to outbound or inbound. I believe it was outbound that caused it for me.

[Mike]

Hi all,

From version3, Brekeke SIP Server will keep a session internally (we call it "zombie") for 90 sec if the session was closed with an error response (such as 404 or 603).

This is because UAS (response sender) may resend an error response within 90sec and so the SIP Server needs to proxy it to the UAC.

Also, some telephone providers requested this function.


With the variable "net.sip.timeout.bye", you can shorten the remaining period. Its default is 90000[ms] (=90[sec])
---------------------------------
net.sip.timeout.bye=90000
---------------------------------



If you want to monitor all of sessions including such hidden remained calls, please execute the "sessionlist" command.

http://<WEB_ADDESSS>/sip/cmd?cmd=sessionlist&param=-i%200%20100%20-

For example:
http://192.168.1.60:8080/sip/cmd?cmd=sessionlist&param=-i%200%20100%20-


If you got the "HTTP Status 404", please add "sipadmin.cmd.hosts.allow" with your PC's IP address in the [Configuration] > [Advanced] page.

For example:
sipadmin.cmd.hosts.allow=172.16.1.1
or
sipadmin.cmd.hosts.allow=172.+
(It can accept Regular expression.)

Thank you

[Mike]

Wayne,

> it says there are active sessions, force restart? But actually there are no sessions.

You can do force restart.

[voipwell.com]

Thanks Mike! That agrees with my inability to cause the problem once i properly configured and was not receiving any errors.

[Mike]

voipwell, I am sorry for the confusion.

We didn't mention this new behavior in the document/wiki yet.


A session will be "zombie" too if the session was canceled because the UAS may resend the response 487 within 90sec.

[voipwell.com]

Well it may not be in the Wiki, but it's now in the forum.

[wayne106]

Hi Mike, thanks for the updates. I tried the URL and get the following error:-

failed
invalid index

This is regardless as to whether a call is in progress or not.

Regards

Wayne

[wayne106]

OK I get it, the command only returns records if you have Zombies, just tried it when I caused a call to fail to 603 and got a record ending with Closing (zombie),,

[Tata]

> failed
> invalid index

If there are no session on the server, the above error message will be shown.