vicidial.org

Hi,

I am using two dialers with same config and one DB server, it is running perfectly,
Very often i am getting a SESSIONID clash problem, that is two users are getting
into same session even though both of them have registered their SIP / IAX phones in different servers,
and this occurs for users registered in same server also. In real time main report i can see same
session id for two users. when this clash happens the calls will get collapsed that is both users calls will get overlapped.

Please give me your valuable suggestions to diagnose and fix this issue.

Make sure you use distinct conferences numbers for each server

describe your method of clustering. vicidial is designed to allow the same session ids for all servers in the cluster or different session ids. as long as clustering is set up properly there is rarely a conflict. i also do not understand the reference to "distracted or collapsed" calls. please post a CLI output sample from asterisk demonstrating whatever it is that happens. and post your server load when it happens via uptime or htop.

i note you also did not post your method of installation ... so here are our newbie suggestions which will help you to get more help:

when you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with build.

this IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600