Calls Cross connection

[Zia]

Hi,

I have two server setup one is Asterisk and other server reset. 4 port PRI card is connected. i am using two campaigns in one campaign i am getting calls cross connection, one agent is talking to customer on the same time that call lands to some other agent, and he can hear only customer voice not first agent voice also.
when i take report it shows that call landed to second agent. but he has not spoke to customer only he listen customer.

now i am scratching my head but not getting any solutions. where one more campaign working fine on the same server. so please give me a solution.

Thanks.

[williamconley]

1) Welcome to the Party!

2) As you are obviously new here, I have some suggestions to help us all help you:

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

3) Please explain "one is Asterisk and other server reset. 4 port PRI card is connected". I have no idea what that meant.

4) Please post asterisk CLI output from an example.

5) If this is a cluster (ie: multi-server vicidial installation), please describe your method of clustering.

[Zia]

ViciBox Server v.4.0, Asterisk 1.4.44. i have two server setup one telephony and other web,db,archive server.
both the machine is Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz 4 cores. Total users log into the server is 45.

[williamconley]

ViciBox Server v.4.0, Asterisk 1.4.44. i have two server setup one telephony and other web,db,archive server.
both the machine is Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz 4 cores. Total users log into the server is 45.

Vicibox has 4.0.X (not just 4.0). It makes a difference from a bug perspective. Probably 4.0.3 ... but if its 4.0.1 or 4.0.2, those had bugs.
You also cut your asterisk version short: Is it the Vicidial version? (I assume so, but then again others have reinstalled asterisk after the fact and spent hours trying to figure out what was wrong ... why not you? LOL)
You mentioned something about a PRI card, but did not post the model number (strangely enough, this helps as well and will often bring someone with the same hardware to your post, which could help you).
While "core i3" is moderately useful, as is the CPU model number, what really helps is the model number of the motherboard model number. This is where the chipset resides and will determine compatibility. (in this case, not likely an issue ... but remember for the future that cpu speed speaks to power and motherboard model number speaks to compatibility )

Vicibox 4.0.?? from .iso | Vicidial ???????? Build ?????? | Asterisk 1.4.44.?????? | 1 DB/Web/Archive & 1 Dialer | Sangoma Hardware ??????| No Extra Software After Installation? | Motherboard? | Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz 4 cores

You did NOT mention your method of clustering these servers. This is important for your question to be answered.
You did NOT post any asterisk CLI output. Also important.
You did not post your Vicidial version at all. This is a requirement, include the build number. Additionally, this makes a huge difference since Vicibox 4.0.X can be used to install virtually any version of Vicidial via SVN.

Without this information, we can just agree with you that it may be broken.