12-10-2012 01:20 PM
Can someone help me figure out why the attached script doesn't seem to want to work completely?
Background Info:
This CUE is on a SM-SRE-900-K9 on a 3945 router running CME 9.1. PSTN connectivity is 4 bundled PRI T-1's. Carrier is outpulsing 4 digits. Customer wants the following call flow:
Business Hours:
Main number (4600) call comes, call is forwarded to 6600 (CUE/AA pilot) and gets immediately diverted to a reception hunt group (5621 pilot). If no answer, call goes to 5600 which is also forwarded to 6600 where the CUE/AA presents options to the caller. If caller makes no choice, call times out and goes to 6620 (GDM).
After Hours:
Main number (4600) call comes in, call is forwarded to 6600 (CUE/AA pilot) and gets immediately diverted to 6600 (GDM).
After Hours works fine. The first part of Business Hours works, except when it comes to handing the call to 5600. Caller used to hear a message about having system problems, now the call simply goes silent and effectively hangs up even though the caller still sees an active call.
Pertinent components of CME config:
ephone-dn 500
number 4600
name BSC Main Line
call-forward all 6600
!
!
ephone-dn 501
number 5600
name BSC Options Menu
call-forward all 6600
!
!
voice hunt-group 2 parallel
final 5600
list 2620,3620
timeout 12
statistics collect
pilot 5621
!
!
dial-peer voice 6600 voip
destination-pattern 6600
b2bua
session protocol sipv2
session target ipv4:10.38.4.2
incoming called-number .T
dtmf-relay sip-notify
codec g711ulaw
no vad
!
!
Could this be something as silly and simple as not being able to direct a call to a script more than once? Any help to get this working would be appreciated.
12-11-2012 11:45 AM
Kevin,
I'm sorry you are having problems with your CUE scripting. I recommend you post this and future technical support questions to the Cisco Support Community (https://supportforums.cisco.com/index.jspa) because we do not provide technical assistance here. You will find a wealth of information under "CUE scripting" in the support forum. Another option is to open a ticket with the Cisco Technical Assistance Center (www.cisco.com/go/support) to get expert debugging assistance.
We do encourage you to participate in the Cisco Collaboration Community and to also join our Cisco Collaboration User Group program! In the community, we encourage your discussion/sharing around collaboration topics and Cisco Collaboration Solutions, including business and IT requirements, industry trends, process, culture/organization issues, how collaboration can be used to transform businesses, vendor selection, adoption, training, architecture, licensing, and product features/functionality. If you are a customer or partner, you can also join the user group program to be eligible for member-only events and influence product direction.
We hope to hear from you again.
Kelli Glass
Moderator for the Cisco Collaboration Community
12-11-2012 02:14 PM
This was posted into the support forums. TAC won't support CUE
editing. The link you provided took me back to the support forums where
I originally posted.
Apparently Cisco is not in a position or refuses to support tools that
are available from CCO, so I'll just have to figure things out on my own.
Thanks!
/Kevin Parsons/
/Unified Networking Engineer/
/Customer Service / Engineering Support 855-644-9121/
//
/kevin@flairsystems.net/ <mailto:kevin@flairsystems.net>
/http://flairdata.com/ <http://flairsystems.net/>
719.330.0326
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide