New calls interrupt user trying to make a call

zaptel cards I take it??

Doesn't the latest firmware address this? I wouldn't know for sure since I haven't tried it out yet.

I am pasting this from the 1.4.2 firmware release notes:
---------
A User and Administrator can now configure whether or not an incoming call interrupts an outgoing call that is dialing. A new parameter has been added
(“incoming call interrupts dialing”) to control this feature.

When you enable this parameter (1 = enable), an incoming call interrupts the
outgoing call during dialing and allows the phone to ring for the user to answer the
incoming call. This was the existing default behaviour in the previous 1.4.1 release
and is also the behaviour of this parameter in 1.4.2 if it is enabled.

IMPORTANT NOTE: If you disable this parameter, the behaviour of the phone has
changed in 1.4.2. In 1.4.2, this feature performs as follows if disabled:

When you disable the “incoming call interrupts dialing” parameter (0 = disable),
which is the default, the phone does not interrupt the outgoing call during dialing and
instead rings the incoming call on another free line (or sends busy signal if all
remaining lines are busy). You have a choice to ignore the incoming call, or answer
the incoming call on another line. If you choose to answer the incoming call, you can
answer the call, finish the call, and then hang up. You can still go back to the original
outgoing call and finish dialing out.

On the 480i, 480i CT, and 9133:
If you disable this parameter (0=disable), and the phone receives an incoming
call while you are dialing an outgoing call, you can pick up the call and perform
transfer or conference as required.

On the 9112i:
If you disable this parameter (0=disable), and the phone receives an incoming
call while you are dialing an outgoing call, you can pickup the call but you
cannot transfer or conference that call.

An Administrator can set this parameter using the configuration files (incoming call
interrupts dialing) or the Aastra Web UI (Incoming Call Interrupts Dialing) at
Basic Settings->Preferences->General). A User can set this parameter using only
the Aastra Web UI.
---------
Sounds like the parameter "incoming call interrupts dialing" would solve the problem that you are having. Hope that helps.

PS: Sorry that what I pasted was formatted that way, I can't seem to fix it.

Replying to this thread because it already exists:

I'm running the most recent firmware available at this time, 1.4.2.3000, and I still have this problem. I've explicitly set:

incoming call interrupts dialing: 0

in my MAC.cfg file and the behavior is the same: if a user is dialing the phone and receives a call at the same time, dialing will be interrupted.

This used to work fine, though.

The most recent change I made was upgrading to FreePBX 2.4, but I can't say for sure if that's the actual cause or not.

Can anyone else running FreePBX 2.4 with an Aastra 480i and the most recent firmware confirm this behavior? Please?

KodaK,

It should be only a phone issue--I don't think that FreePBX would affect this.

I'm pretty sure I have it setup the way you want it at a client's location. I'll check on this in the next day or two and get back.

KodaK,

I have the same firmware as you listed above.

In the web GUI for the phone, (logged in as admin, but you might not need to) I have unchecked "Incoming call interrupts dialing" and checked "Goodbye key cancels incoming call".

On the phone itself, in Settings, I have Live Dialpad set to ON. (This might be the magic bullet for you.)

User just told me that it works exactly as he wants. I don't know what other settings I would have changed to make it work correctly.

Umm...I don't mean to insult you, but you did reboot the phone after making changes?

Hope that helps!

KodaK,

I don't think there's a config file equivalent. I just did a quick search (Ctrl-F) of the Aastra administrator's guide (that has many of the config file commands), and searches for "live" and "dialpad" didn't turn anything up.

You could try it on one phone and see if it helps before taking the plunge and going around to every phone, I guess...or are you "off-site"? How many phones are we talking about? Enabling Live Dialpad on the phone doesn't even require the admin password, so the users could do it themselves pretty easily, I guess.

Hope that helps!

What about inbound calls going to random extensions not in the specified Ring Groups.

Yeah, my issue was that when g.729 was enabled on a 480i CT it would be garbled on a headset, but if I switched from headset to speaker and back it would be fine.

They wanted debug logs, wireshark dumps (that I even went and figured out how to extract g.729 audio from the RTP streams, confirming that the streams were clean) I brought in some of my recording equipment from home and put a microphone up to the headset to record the distortion.

That was probably over a year ago now. They called me once asking if it was still a problem, I guess hoping to close the ticket. I said "yes, it's still a problem, is someone working on it?" Of course not. Other than that, I've never heard a thing. Every time I've called about it I get "it's been sent to engineering."

The "solution" was to stop using g.729 as a codec, or to get used to switching from headset to speaker and back every time I took a call. I can't ask a user to do that.

Aaron: I'm sorry, but I don't see how that has anything to do with the topic of this thread. Why do you think so? You may be better off starting a new thread, make sure to include as much information as you can, including cli logs if you can get them and the relevant time period in /var/log/asterisk/full as well.

I have no users with headsets, so I can't be much help there!