Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Trouble with Auto Attendant on CUC500

Status
Not open for further replies.

matt054

Technical User
May 5, 2008
8
NZ
I have recently been configuring a new CUC520 for a client -using a SIP trunk I am able to call from the PSTN into the CUC520 IP phones and out from the IP phones to the PSTN.
I have configured the prompt management number and AA and VM numbers as below but I am unable to call from the PSTN to the pilot number or from within the CUC520 environment to the pilot number? As such I can't get the Auto Attendant to work on the CUC520! Any suggestions ideas would be greatly appreciated...........

dial-peer voice 2000 voip
description ** cue voicemail pilot number **
destination-pattern 4781
b2bua
session protocol sipv2
session target ipv4:10.1.10.1
dtmf-relay sip-notify
codec g711ulaw
no vad
!
dial-peer voice 2001 voip
description ** cue auto attendant number **
translation-profile outgoing PSTN_CallForwarding
destination-pattern 4000
b2bua
session protocol sipv2
session target ipv4:10.1.10.1
dtmf-relay sip-notify
codec g711ulaw
no vad

dial-peer voice 4778 voip
description dial-peer for prompt management
destination-pattern 4801
b2bua
session protocol sipv2
session target ipv4:10.1.10.1
dtmf-relay sip-notify
codec g711ulaw
no vad

 
Is 10.1.10.1 the IP address of the CUE module??
 
Thanks for the reply - yes 10.1.10.1 is the CUE IP address (default on CUC520). Any ideas???
 
Here is the config that worked in a CME. Not much difference between CME and UC500.

interface Service-Engine1/0
ip unnumbered GigabitEthernet0/0
service-module ip address 10.1.1.13 255.255.255.0
service-module ip default-gateway 10.1.1.1

ip route 10.1.1.13 255.255.255.255 Service-Engine1/0

dial-peer voice 111 voip
description ** cue auto attendant number **
destination-pattern 6000
session protocol sipv2
session target ipv4:10.1.1.13
dtmf-relay sip-notify
codec g711ulaw
no vad
!
dial-peer voice 112 voip
description ** cue prompt management number **
destination-pattern 6001
session protocol sipv2
session target ipv4:10.1.1.13
dtmf-relay sip-notify
codec g711ulaw
no vad
 
Yes - I changed the prompt management via the CUE.
 
Do a debug voip ccapi inout and see what is happening when you call the number. Make sure it is hitting the right dial peer.
 
Thanks for your help but we are having more issues with this box now and as it is in a production environment we have decided to get the Cisco TAC guys involved (its covered by 90 day warranty). I will let you know how I get on - once again cheers for your help
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top