cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2251
Views
5
Helpful
6
Replies

cisco 6941 second incoming call get busy tone

Asim Afzal
Level 1
Level 1

hi.

I have cisco 6941 phone.I am getting busy tone on 6941 phone if that phone is already on call.

Any body knows whats the issue.

6 Replies 6

Aaron Harrison
VIP Alumni
VIP Alumni

Hi

Check the max calls/busy trigger on the line settings - these should be 4/2 respectively if you want call waiting.

Aaron

Aaron Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!

Rob Huffman
Hall of Fame
Hall of Fame

Hi Asim,

The 69xx series are a tad different than some/most Cisco IP phones

Configuring the Phone to Support Call Waiting

The Cisco Unified IP Phone 6921, 6941, and 6961 support one call per line. Cisco Unified Communications Manager sets the Maximum Number of Calls (MNC) per line, and Busy Trigger (BT) per line attributes to 2 and 1 respectively and these fields can not be changed, As a result, the line appears to be busy to a second incoming call when there is an active call present on the line. Cisco Unified Communications Manager forwards the second incoming call based on the Call Forward Busy settings for the line. The user, who is on a call will not be notified of an incoming call. Without further configurations, the phone does not support call waiting. However, you can configure the phone to support call waiting and receive the call by configuring an additional line on an unassigned programmable button. When the user receives an incoming call while connected on a call, the phone plays the call waiting tone (single beep), displays a caller ID notification and rolls the incoming call over to the other line.

To configure call waiting on the Cisco Unified IP Phone 6921, 6941, and 6961:

1. On an unassigned programmable button on the phone, configure an additional line by either assigning the same directory number on a different partition or by assigned a different directory number.

a. When you configure the second line by assigning the same directory number on more than one line, the DN on the second line must be on a different partition. Each time that you assign the same DN to another line, you must create a unique partition and assign the directory to that partition.

b. When you configure the second line by assigning a different directory number, you must use a previously unassigned and unlisted number.

The second line is an intermediary between the original line (your listed directory number) and your call busy destination, such as your voice messaging system.

2. On the original line, configure the destination for the Call Forward Busy Internal and Call Forward Busy External settings to your second line and the No Answer Ring Duration to a minimum of 10 seconds.

3. On the second line, configure the standard Call Forward All settings that you would normally use for the original line and set the No Answer Ring Duration to a minimum of 10 seconds.


Note You will need to assign a programmable button for each listed directory number.

http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/6921_6941_6961/7_1_2/english/admin/guide/6921usr.html

Cheers!

Rob

Gordon Ross
Level 9
Level 9

Prior to CUCM 8.6/Firmware 9.2, the 69xx series phones did not support the setting of the busy trigger.

GTG

Please rate all helpful posts.

Hey Gordon,

Thanks for this update my friend! +5

Cheers!

Rob

Go Cambridge!

Hi Rob,

I have pretty similar issue with 6941 in one of our offices. First of all, user isn't able to "Trnsfer" softkey, when they are on call at all.  I have checked the softkey template, it is fine. I did re-create it and re-configured the phone too. No luck yet.

It all started with, user wanted to transfer the second call, when they are already on another active call.

I explained it isn't possible on this phone, since 6941 supports just two calls per button/line.

CME ver 8.0

Phone firmware : SCCP6941.8-5-3-0

Please advise.

Sami

Hi Sami

You'll need to upgrade your firmware almost definitely. The latest 9.2x firmware for the 69XXs seems to have fixed most of the issues I have had with them including this kind of thing.

HTH. Barry