Solved: Transfer Call

mljevakovic · ‎09-17-2007

I'm using CCME on 2821 router with 7960,7940 and 7911 IP phones. My problem is the next: when users (only who use 7911 IP phone) try to make transfer call to another IP phones they cannot here the rings of other phones. So they only can suppose that caller accept call and put the hang up. In the attach is part of config file. Any idea?

Rob Huffman · ‎09-18-2007

Hi Mustafa,

It looks like because you are using Transfer System Full-Consult that the 7911 would need to be setup with a Dual Line config;

A dual-line ephone-dn has one virtual voice port and two channels to handle two independent calls. This capacity allows call waiting, call transfer, and conference functions within a single ephone-dn. Dual-line mode is supported on all phone types, but is not appropriate for voice-mail numbers, intercoms, or ephone-dns used for message-waiting indicators, paging, loopback, or hunt groups. Overlays of single-line hunt groups onto dual-line buttons are supported.

Ephone-dns are created in single-line mode if the dual-line keyword is not used. Changing an ephone-dn from dual-line mode to single-line mode (and vice versa) requires that you delete the ephone-dn and then recreate it.

Examples

The following example enters ephone-dn configuration mode to create the ephone-dn 5576:

Router(config)# ephone-dn 1

Router(config-ephone-dn)# number 5576

Router(config-ephone-dn)# exit

The following example creates an ephone-dn with the number 1001 in dual-line mode. The no huntstop command allows calls to continue to hunt to other ephone-dns if this one is busy or does not answer. The huntstop channel command disables call hunting to the second channel of this ephone-dn if the first channel is busy or does not answer.

Router(config)# ephone-dn 10 dual-line

Router(config-ephone-dn)# number 1001

Router(config-ephone-dn)# no huntstop

Router(config-ephone-dn)# huntstop channel

Router(config-ephone-dn)# exit

From this good CME doc;

http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_command_reference_chapter09186a0080611350.html

Hope this helps!

Rob

View solution in original post

Rob Huffman · ‎09-18-2007

Hi Mustafa,

It looks like because you are using Transfer System Full-Consult that the 7911 would need to be setup with a Dual Line config;

A dual-line ephone-dn has one virtual voice port and two channels to handle two independent calls. This capacity allows call waiting, call transfer, and conference functions within a single ephone-dn. Dual-line mode is supported on all phone types, but is not appropriate for voice-mail numbers, intercoms, or ephone-dns used for message-waiting indicators, paging, loopback, or hunt groups. Overlays of single-line hunt groups onto dual-line buttons are supported.

Ephone-dns are created in single-line mode if the dual-line keyword is not used. Changing an ephone-dn from dual-line mode to single-line mode (and vice versa) requires that you delete the ephone-dn and then recreate it.

Examples

The following example enters ephone-dn configuration mode to create the ephone-dn 5576:

Router(config)# ephone-dn 1

Router(config-ephone-dn)# number 5576

Router(config-ephone-dn)# exit

The following example creates an ephone-dn with the number 1001 in dual-line mode. The no huntstop command allows calls to continue to hunt to other ephone-dns if this one is busy or does not answer. The huntstop channel command disables call hunting to the second channel of this ephone-dn if the first channel is busy or does not answer.

Router(config)# ephone-dn 10 dual-line

Router(config-ephone-dn)# number 1001

Router(config-ephone-dn)# no huntstop

Router(config-ephone-dn)# huntstop channel

Router(config-ephone-dn)# exit

From this good CME doc;

http://www.cisco.com/en/US/products/sw/voicesw/ps4625/products_command_reference_chapter09186a0080611350.html

Hope this helps!

Rob

mljevakovic · ‎09-20-2007

Hi Rob,

Thank you very much for your suggestion. It was because of "dual-line". Nice work!

Mustafa

Rob Huffman · ‎09-21-2007

Hi Mustafa,

Thanks for the nice vote :) There is always something weird going on with this stuff isn't there!

Take care,

Rob

chrisdoleglo · ‎10-04-2007

Hi Mustafa,

I noticed that your telephony-service lists load statement ending with .loads extension. Cisco recommends and states in all their documentation that you do not issue statements with extensions of file names on it. Just the name of the firmware. It tells the telephony service basically what to load and for what device. It should not effect your service but I would do it post business hours.

You show:

telephony-service

load 7960-7940 P0030702T023

load 7911 SCCP11.8-0-4SR2S.loads

Just take it out and then reapply statement:

load 7911 SCCP11.8-0-4SR2S

Reset one of the 7911 phones and recheck your firmware. You should have it done. This maybe what you're missing.

I hope this works for you.

Good luck

mljevakovic · ‎10-05-2007

Thank you for your care about my issue. I've already corrected the above mistake. Anyway thanks. May I ask you another question? Does the ATA 186 support using POS terminal through its ports?

Rob Huffman · ‎10-05-2007

Hi Mustafa,

We have successfully used the ATA 186 for "Point of Sale" dialup style terminals in the past. Should work just fine :)

Hope this helps!

Rob

mljevakovic · ‎10-05-2007

what about this:

"Q. Does the ATA 186 support modem pass-through/relay?

A. No, the ATA 186 does not support modem pass-through/relay. "

from http://www.cisco.com/en/US/products/hw/gatecont/

ps514/products_qanda_item09186a00800946e1.shtml

Anyway how did you make that? I've spent the whole day to make this but without success.