atcomsystems.ca/forum
Have an issue affecting multiple customer and is as follows:

Receptionist answer an incoming call and transfers that call through to another extension. The extension takes the call and then places that call on hold, when they go back to retrieve the call from hold, call goes to speaker and they are unable to get the call off speaker, they must continue the conversation on speaker or hang up and call the customer back.

It is a very intermittent fault and i have been unable to replicate, although have had reports from 3 different sites. Common link seems to be a 16dli2 card.

All 3 sites are v4.93 - 2 x 7100's and 1 x 7200s

Hoping someone may have experienced the same problem.
I've heard of this issue happening a few times, i've only ever seen it once on our in house OS7200, my boss managed to-do it, he was using a SMT phone at the time (5220 from memory)

Had a customer on OS7200S do it today whilst I was talking to them on a digital handset.

Don't know the cause, it doesn't happen very often.

If they put the caller back on hold and pick them up again does it remain on speaker or work as normal?

4.93 only exists on OS7030. I'm guessing you mean 4.95 (current release)

Open a ticket with tech support, this is a known issue. There is a T-Package release that we are beta testing right now from Korea that seems promising but it's only been out for a week so there isn't enough data to know yet.
Posted By: Lacota Re: Incoming call issue on Digital Extensions - 08/25/16 02:08 PM
The problem I was having with this issue is the user was putting the call on hold and just putting the hand piece on the desk and not on the cradle, this will cause it to time out and the phone will go back to an idle state and forget about the hand piece.
You can either get them to put it back on the cradle once on hold which is what I do or before they take them off hold just give the hook switch a press to bring the hand piece back in to play.
Originally Posted by Lacota
The problem I was having with this issue is the user was putting the call on hold and just putting the hand piece on the desk and not on the cradle, this will cause it to time out and the phone will go back to an idle state and forget about the hand piece.
You can either get them to put it back on the cradle once on hold which is what I do or before they take them off hold just give the hook switch a press to bring the hand piece back in to play.

That's a separate issue than what we have in the US. That issue is also corrected with a new software release. What he is describing the phone will literally go to speaker phone when you pickup your handset and occasionally in the middle of a call.
Sorry my mistake V4.91
I haven't seen the fault in action, from my understanding they are unable to get the call off speaker at all. Having said that im not sure they would have tried putting the call back on hold.
This is not a known issue in Australia, i will send tech support the 3 databases as they requested - although often its easier to indentify faults on here than tech support.
Nameless does tech support know of your issues?
It's an issue with all dli cards manufactured with the new chip. They are finding most people aren't reporting it until recently and are now scrambling to fix it. Your issue is exactly like 50% of the sites we have the issue with. The temp workaround is to park the call and and then pick it back up
I actually think one of the 3 sites may have been the issue of the customer placing the handpiece on the desk - i tried to replicate the fault with him and noticed he placed it on the desk and not back on the cradle, I just didn't leave it on hold long enough for it to time out.
So 2 of the 3 sites have been fixed up by getting them to place the handset back in the cradle whenever they place a call on hold.
3rd site is different, where they get a call transferred to them and it automatically just goes to speaker, without placing the call on hold or anything - this sounds a lot like the other issue. Customer has figured out a way to get it off speaker, so i guess i will have to wait and see what samsung come up with.
I haven't ever been able to replicate the issue so I haven't spoken to Tech Support about it.

In saying that we have a customer who has just reported that fault who we are going out to see soon, so maybe we'll be able to replicate it and let them know
Had 1 person 1 time complain about this OS7400 4.60b Pri trunks. To the best of my knowledge never happened again and I was never able to duplicate it.
I have this occurring on two sites. Both have single cabinet 7400 systems. One recently upgraded to 4.95 the other is still at 4.6.

Has the T patch, been made available?

-Will
The patch is available for the 7100 and 7200s. I believe they are going to apply the fix in 4.99 for all systems though.
© Sundance Business VOIP Telephone Help