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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

CUE will not answer pilot number

Status
Not open for further replies.

doubleE1

Vendor
Jun 29, 2010
3
US
Our shop has aquired a used Cisco 3745 router with CME ver 3.3 and CUE ver 2.3 (AIM card in slot 1). All works except when you press the VM key (or dial 5000) you get a busy signal. The AA number 1000 works. I can talk to both CME and CUE using CLI and GUI. Initially we would get dead air. Then I configured a dial-peer for 5000 which changed the response to a fast busy.
We see "[time stamp]% call control-6-call_loop:The incoming call has a global indentfier already present in the list of currently handled calls. It is being refused" on the console.

I have factory defaulted the CUE and ran the install wizard again with the same results. What are we missing?


 
Yes, I have Voicemail = 5000.
Do I need the Dial-Peer for 5000? And if so, should it point to the router ip or the CUE ip?

I question this only because I'm making the assumption this worked before we aquired it and it did not have a dial-peer for 5000, although there was one for 50.
 
Your original post says that you have a dial-peer for 5000.
it needs to point to the CUE and not the CME.
example:
dial-peer voice 10 voip
description Voice Mail pilot
destination-pattern 5000
session protocol sipv2
session target ipv4:x.x.x.x (ip adddress of CUE )
codec g711ulaw
no vad
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top