Consult Transfer

[breakwaterit]

Hi I used to have consult transer without the need to daul line the phones . Not sure what has happend in the last hour but I now cant do it.

Here is my Tel Service

telephony-service

load 7960-7940 P00307020200

load 7914 S00105000200

max-ephones 50

max-dn 50

ip source-address 10.1.1.254 port 2000

auto assign 1 to 50

network-locale GB

network-locale 1 GB

network-locale 2 GB

network-locale 3 GB

network-locale 4 GB

voicemail 8080

max-conferences 8 gain -6

dn-webedit

time-webedit

transfer-system full-consult

Hmm

[breakwaterit]

Ok I realised what happend we removed a second extension number from a phone. The issue is I dont want all phones to have two extensions or the user to have dual lines so they get a beep in the ear while they are on a call .

What do i do?

[Rob Huffman · Accepted solution]

Hi Stephen,

You are going to have to use either two extensions or Dual-Line if you want Consult Transfer. Have you tried this for the Dual-Line phones?

call-waiting beep

To allow call-waiting beeps to be accepted by or generated from an ephone-dn, use the call-waiting beep command in ephone-dn or ephone-dn-template configuration mode. To disable the acceptance and generation of call-waiting beeps by an ephone-dn, use the no form of this command.

call-waiting beep [accept | generate]

no call-waiting beep [accept | generate]

The call-waiting beep command must be used with the ephone-dn command. The call-waiting beep command is used like a toggle and can be switched on and off for each ephone-dn.

A beep can be heard only if both sending and receiving ephone-dns are configured to accept call-waiting beeps.

To display how call-waiting beeps are configured, use the show running-config command in the privileged EXEC configuration mode. If the no call-waiting beep generate and no call-waiting beep accept commands are configured, the show running-config output will display the no call-waiting beep command.

If you configure a button to have a silent ring using the s option of the button command, you will not hear a call-waiting beep regardless of whether the ephone-dn associated with the button is configured to generate a call-waiting beep.

If you use an ephone-dn template to apply a command to an ephone-dn and you also use the same command in ephone-dn configuration mode for the same ephone-dn, the value that you set in ephone-dn configuration mode has priority.

From this good CME doc;

http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_command_reference_chapter09186a008061134b.html#wp1064231

Call-Waiting Beep: Example

In the following example, ephone-dn 10 neither accepts nor generates a beep, ephone-dn 11 does not accept a beep, and ephone-dn 12 does not generate a beep.

ephone-dn 10

no call-waiting beep

number 4410

ephone-dn 11

no call-waiting beep accept

number 4411

ephone-dn 12

no call-waiting beep generate

number 4412

http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_configuration_guide_chapter09186a00807dc29a.html#wp1118332

Hope this helps!

Rob

Please remember to rate helpful posts.....