Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations MikeeOK on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SV9500 8-party conference call - everyone is kicked unexpectedly

phadobas

Technical User
Jul 30, 2005
624
US
I have an 8-party conference programmed up on a VS32. Port 0 is the leader port and ports 1-7 are for participants. Everyone dials the number for port 1, which is in a hunt group with lines on port 1-7. The call goes on for about 10 minutes, then everyone is kicked unexpectedly. In reviewing SMDR logs, I see one participant dialed in to port 0 as leader, but she says she didn't push the "#" button, which is the button to press to forcefully end a conference call and kick everyone out.

The people using this conference had encountered this about 5 times this year. They make about 1-2-3 calls a week. I dialed into this conference today, with 3 IP phones in my office and 2 cell phones. I was on it for 25 minutes, no issues.

One other thing that sometimes happens is someone comes along to join the call. Instead of dialing the pilot number, they pick up the line appearance of another phone that's already in the 8-party conference. So now you have one leg of a 3-party conference joined to one leg of an 8-party conference. Technically it works. I tested it. But I don't know it this can lead to some issue.

So I'm not really sure what's happening here. Has anyone found a user error or a technical error causing this?

For example, you are the leader in the conference. After 20 minutes on the phone (with the handset squeezed to your ear), your neck gets tired and you decide to put your phone in loudspeaker mode. So you press the Speaker button and put the handset on the cradle. If this is done right, then all is fine. However, the Speaker button is right next to the "#" button, which if pressed by accident, kicks everyone out. And you could be scratching your head all day long, trying to find out what is wrong with the system, just to find that the Leader accidentally pushed the "#". I checked and in our case, this was not the problem. So I don't know what it was.
 
I found in AIVSL that you can go the DETAIL SETTING Tab, then in "Setting of Expansion Mode" you can enable / disable DTMF detection, effectively disabling the "#" button. If this really resolves the problem, it will be a few weeks before I will know (as this problem only happens every few weeks).
 

Part and Inventory Search

Sponsor

Back
Top