CME 4.0 call-forward busy

[jeremy.t]

Hi, I am running CME 4.0(1) with CUE 2.2.2. When an extension is busy and call-forward busy is configured for that extension to transfer to VM, instead of transfering directly to VM the caller hears a ringing tone and only transfers to VM after the call-forward noan timeout has expired. Does anyone know how you can configure calls to busy extensions to go straight to VM?

Thanks

[Rob Huffman · Accepted solution]

Hi Jeremy,

Just a guess here, but it almost sounds as if this DN is set up as dual-line? Have a look;

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 CME 4.0 doc;

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

Hope this helps!

Rob

[jeremy.t]

That's fixed it! Thanks for your help.