Voice activated handset

[mobiletrainer1]

I have a single MLX extension, that when receiving incoming calls, the person must speak into the handset before the incoming call is connected. Incoming callers do not hear hold music during the interval wating for the person to speak or blow into the MLX handset.

It almost acts like a voice activated feature. The "problem" is not in the phone because we swapped working phones and the "problem" is still there.

My thoughts are this is related to a headset setting but I've programmed the headset options to buttons and was unsuccessful in a cure. If you need more details let me know.

 

[2BAvoice]

Isn't it normal to speak into the handset on incoming calls?
For example, "hello"?

 

[mobiletrainer1]

That's a good one! And thank you for the quick reponse. Yes it is normal for you to speak into an incoming call, what is not normal is for the first few words to be cut off.

I failed to mention that there is 2 beeps that are heard in the handset before the two parties can talk.

It's not a matter of this person speaking to quickly, because she has learned to blow into the microphone first (which the caller doesn't hear) then wait for the 2 beeps and then say the greeting. The 2 beeps will not be heard in the handset until a noise is made into the mic of the handset. Hence the "voice activated" unwanted feature.

I guess that helps clarify the question, sorry. But good response, that was funny.

 

[TouchToneTommy]

Print the station and post it here. I would be looking for Headset Auto Answer, or Line Preference settings.

 

[mobiletrainer1]

you can see the buttons we added trying to "cure" this "problem"

EXTENSION INFORMATION


Extn SS/PP Type
208 1/ 8 MLX-10D

CTI Link : No Alarms: ACTIVE
Pool Access : 70
Page Group :
Primary Coverage :
Secondary Coverage :
Coverage Group : 30
Group Coverers : 770
NS Groups :
Group Calling Member:
Pickup Groups : 1
Allowed Lists :
Disallowed Lists :
Restrictions : UNRESTRICTED
ESS Sup. Status : NOT ACTIVE
ESS Restrictions : ESS-0 - NO RESTRICTION
Auto Callback : OFF
Call Waiting : OFF
Abbreviated Ring : ON
Line Preference : ON
Shared SA Ring : ON
Receive Voice Calls : ON
Coverage Inside : ON
Forwarding to :
Delay Forwarding : 2
ARS Restriction : 3
Forced Account Code : No
Microphone Disable : No
Rotary Enable : No
Remote Forward Allow: Yes
Trunk Transfer Allow: Yes
NS Exclusion : No
Voice Announce Pair : No
Voice/Data Pair : No
BIS/HFAI : No
Language : English
Authorization Code :
2B Data Port : No
Primary Ring Delay : 1
Secondary Ring Delay: 2
Group Cover Delay : 5
HotLine Extension : No
Networking and ISDN Display Preference: BOTH
Service Observer:
Service Observing Group:
EXTENSION INFORMATION


Extn SS/PP Type
208 1/ 8 MLX-10D

Button 34 *21 Blank Status None
Button 33 *21 Blank Status None
Button 32 *21 Blank Status None
Button 31 *21 Blank Status None
Button 30 *21 Blank Status None
Button 29 *21 Blank Status None
Button 28 *21 Blank Status None
Button 27 *21 Blank Status None
Button 26 *21 Blank Status None
Button 25 *21 Blank Status None
Button 24 *21 Blank Status None
Button 23 *21 Blank Status None
Button 22 *21 Blank Status None
Button 21 *21 Blank Status None
Button 20 *21 Blank Status None
Button 19 *21 Blank Status None
Button 18 *21 Blank Status None
Button 17 *21 Blank Status None
Button 16 *21 Blank Status None
Button 15 *21 Blank Status None
Button 14 *781 Headset Hang Up Status None
Button 13 *21 Blank Status None
Button 12 *21 Blank Status None
Button 11 *21 Blank Status None
Button 10 *782 Headset Status Status Off
Button 9 *84 Last Number Dial Status None
Button 8 *47 Do Not Disturb Status Off
Button 7 *9 Pickup General Status None
Button 6 *86 Park Status None
Button 5 *33 Forward Status Off
Button 4 70 Pool -N
Button 3 *18 SysAcc-OO Ring Status None
Shared System Access:

Button 2 *16 SysAcc Voice -I Status None
Shared System Access:

Button 1 *16 SysAcc Ring -I Status None
Shared System Access:

 

[dagwoodsystems]

I saw something like this happen once. The problem was with the blue pair being ever so slightly disconnected at a block. We theorized that it was the voice energy on a live call that caused the slight break to complete the circuit (like the way a toner oscillation can jump a broken connection).

On the off chance that something weird like that happened here, perhaps you could do a quick re-punch of cross connects and such and see if the problem goes away.

 

[mobiletrainer1]

gladly will give it a shot. thanks, I will reply back. How come my problems never seem to be easy?

 

[dagwoodsystems]

The beeps that you say you hear smack of what we call "zip tone", which makes me wonder if TouchToneTommy may also be onto something with the headset thing.

 

[cvrbob]

or how are they receiving the call, is it being transfered from someone who is program to send voice announce calls , does it turn on your speaker

 

[TouchToneTommy]

Try putting a Headset Auto Answer button on it, enable the Headset Status ON, toggle the Auto Answer on and off, then turn the Headset Status OfF. If it solves the problem, then delete the headset buttons.

 

[dagwoodsystems]

Did we come to a conclusion on this one? I really urge you to try TouchToneTommy's suggestion. I know what he's thinking, and I'm sure he's on the right track.

Please post back, mobiletrainer1.

 

[mobiletrainer1]

ok, sorry it took me so long to repost. Thankyou for all the suggestions so far. I had to wait for the weekend before I could attack the phone.

I tried all the above suggestions. I repunched the block on both ends. To no avail. I then added ALL the handset options to buttons. I made sure I cycled each button on then tried to pick up an incoming call. Same problem. Then I cycled each button off again. Tried an incoming call. Same irritating pause then eventually 2 beeps. I then deleted all handset buttons. No success.

It stll does the same 2 tones. one longer than the other. Longer first then short. Shorter is higher pitched.

NEW DETAILS: At one time this person did try to plug in a plantronics cordless headset, but apparentely she didn't like it. She didn't continue to use it. Supposedly, this problem did not appear immediately after disconnecting it. That's what I'm told.

Also, don't know if this is related. When I tried to pick up an incoming call ,if I spoke into the handset quickly and hungup rapidly, the operators extension then rings and can pickup the call. Only learned this out of frustration. The operator's extension is forwarded to this phone.

Short of doing a reprogram of the whole system, any more ideas? Hammer? sudden drop of a Legend? Maybe just a swift smack of a Legend.

 

[dagwoodsystems]

My bluetooth does this long/short tone thing (with the second tone being higher pitched), yet I can't help but to think that the association is anything more than grabbing at straws. And reportedly, the timing of this problem appears to be unrelated to the trial run of a headset.

Does the longer tone sound like a "go to cover" tone? You know, the sound you hear right before someone's voicemail answers?

I'm also curious about the forwarding arrangements. Nothing stands out on your station prinout, but it sounds like there might be some convolution here. You say that the Operator's phone is forwarded to this station (x208), yet this station has Remote Call Forward capability. This makes me wonder if there's a bigger picture that we should see.

There's no way to default a station, per se. However, you could go into Centralized Programming copy restrictions, lines and buttons from a known "vanilla" extension.

As a last resort, you could move this station to an available MLX port and renumber it. That sounds a bit like giving up, but you did mention hammers, dropping and smacking. Put the hammer down and take a deep breath. We'll get through this!

 

[mobiletrainer1]

As far as I know I think the legend is a little to much of a legend to worry about a bluetooth option being turned on.

Ok the hammer is down, but a little smack is not out of the question.

I tried a "vanilla" extension copy before I wrote to this forum. That seemed a smart place to go.

My next steps seem to be a card swap or reprogram with an old backup before the problem started. Maybe swapping the mlx 10 for the mlx 20 might be a suttle slap to the system? I'm going to unforward the extension just for "kicks" and giggles.

Thanks for the thoughts. I promise I won't resort to major violence.

 

[dagwoodsystems]

You're the man now, dog! --Sean Connery, Finding Forrester

 

[TravelingTom]

Have you gone into maintenance, busy out, reset and restore that particular port?