CME wont call-forward to CUE

Unanswered Question
Mar 25th, 2009
User Badges:


I cant seem to get CME to call-forward to CUE - or when it does the call just gets disconnected.

Here is my config - pretty much the same as this good example:

Anyone have any ideas?

interface GigabitEthernet0/0

description Private Link Network

ip address

duplex auto

speed auto


interface Service-Engine0/0

ip unnumbered GigabitEthernet0/0

service-module ip address

service-module ip default-gateway



dial-peer voice 1 voip

mailbox-selection last-redirect-num

destination-pattern 99..

session protocol sipv2

session target ipv4:

dtmf-relay sip-notify

codec g711alaw

no vad



no auto-reg-ephone

authentication credential otn Ms3rv1c3

em logout 0:0 0:0 0:0

max-ephones 58

max-dn 192 no-reg primary

ip source-address port 2000

url services

url authentication

cnf-file location flash:

load 7921 CP7921G-1.2.1.LOADS

load 7942 SCCP42.8-4-2S.loads

load 7962 SCCP42.8-4-2S.loads

load ata ATA030203SCCP051201A.zup

time-zone 47

time-format 24

date-format dd-mm-yy

dialplan-pattern 1 566727.. extension-length 4 extension-pattern 27..

voicemail 9999

max-conferences 8 gain -6

hunt-group logout HLog

web admin system name otn password Ms3rv1c3


transfer-system full-consult

fac standard

create cnf-files version-stamp 7960 Mar 25 2009 20:44:32

ephone-dn 92

mailbox-selection last-redirect-num

number 2792

label Adam

name Adam

call-forward busy 9999

call-forward noan 9999 timeout 10

ephone-hunt login

ephone 92

description Adam

mac-address 0024.97A9.F649

codec g729r8

type 7942

button 1:92


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 1 (1 ratings)
craig.corbett Wed, 03/25/2009 - 05:59
User Badges:


Not sure if this is your issue but I have seen issues like this when Cue is not initialised.

Connect to the GUI of the CME module log in and initialise.

sivakarthiks Wed, 03/25/2009 - 06:38
User Badges:


In the dial-peer voice 1 voip change that codec to g711ulaw and try.

Nicholas Matthews Wed, 03/25/2009 - 08:25
User Badges:
  • Red, 2250 points or more

This is correct - the CUE module only supports G711ulaw. alaw isn't supported on CUE.


kent.plummer Wed, 03/25/2009 - 13:44
User Badges:

Great - thanks for spotting this error.

I'll try G711ulaw and let you know the result.

kent.plummer Thu, 03/26/2009 - 17:56
User Badges:

Unfortunately changing the codec to G711ulaw didn't seem to help.

CUE is also initialised and I have created a number of mailboxes.

Any further suggestions?

paolo bevilacqua Thu, 03/26/2009 - 18:42
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Take "debug ccsip message" with "term mon" and you will see why CUE is refusing the call.

Nicholas Matthews Thu, 03/26/2009 - 20:24
User Badges:
  • Red, 2250 points or more

A few things to check on CME:

-Do you have the route defined statically pointing towards the service engine?

-Can you ping CUE?

-If you have a SIP trunk coming in, you need:

voice service voip

allow sip-to-sip

A few things to check on CUE:

-Under ccn subsystem sip, do you have the correct IP address defined for CME

-Does your sip target match what you're dialing?


kent.plummer Thu, 03/26/2009 - 20:54
User Badges:

I was using 9999 as the CUE extension. I changed it to 9992 and all now works fine.

Looks like ext9999 is used by a public distribution list for all users.

Thanks for the tips anyway.



mrugeshpatel_2 Fri, 03/27/2009 - 10:29
User Badges:

Do you have transcoders configured? If yes, can you make a test call and see them engaging?


david.vanherck Fri, 05/08/2009 - 07:14
User Badges:


I had the same thing: I could call the VM pilot (being 9999 in your case), but transfer to 9999 fails. Try to remove the command "dialplan-pattern 1 566727.. extension-length 4 extension-pattern 27.. " under Telephony-service. That fixed my problem.




This Discussion