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

CP100 uncooperative

Status
Not open for further replies.

Brutalis

Technical User
Jan 15, 2007
302
CA
Have a client with CICS 6.1 and CP100 2.0. I'm unable to change dial 0 properties. In programming disabled Gen. Del. mbox as requested by client. Made ext22 dial 0 from table 1. Made ext 22 attndt set under Op Status. Made ext 22 dial 0 in System Programming. Internal calls to ext22 go to mb22. Incoming calls are answered by AA at 2 rings. Ext 22 is FNA to voicemail at 4 rings. If I call in and press 0 after AA answers it rings 4 times and goes to GENERAL DELIVERY NO MATTER WHAT!!! Tried changing FNA, DRT and trans callback to maximum values. Dial 0 from AA and rings 10 times then goes to GENERAL DELIVERY!!! According to programming general delivery doesn't even exist. Rebooting system didn't help. Am I going crazy or have I missed something??
 
Sounds as if there is a programming conflict between "line answer"/number of rings and Forward No Answer number of rings. Make sure they are both set the same. If there is a conflict between these settings The incomming call will always go to Gen. Del. even if GD is disabled. Try this first. Check ALL sets that are programmed to forward to VM. The FNA in "set capabilities" need to match the "Line Answer" number of rings on the Call Pilot.

I'm about 99 percent sure this will fix your problem!!! OK- 98.
 
if i'm correct and i may not be, but isn't gen del. by default 0??? have you tried assigning ext.22 to mailbox 100 or is it 10 since you are using 2 digit ext's.
i would go into f983/mbox/change/10 and see what ext. is assigned to it. if none,then go to ext. f981/pswd/0000/enter new pswd/ again/ then record name and primary greeting in that mailbox for ext. 22. f982/operater status to yes
do you have a ccr tree built??? if not, the call will always revert to gen delivery.
did you make ext. 22 your prime set for all lines.

Voice Connect Plus, Inc.
have a great day and a better tomorrow
 
If your line answer in AA is set to 2 rings and your "Forward no Answer" in the system is set to 4 rings- This is ABSOLUTELY the problem!!!!! The CP will send the call to "GD" EVERY time even if the GD is dissabled. It's intentional in the software program so messages Shall NOT be lost.
Change the AA Line answer to 4 rings to match FNA on all sets that are assigned with this line, to 4 rings and this WILL FIX your problem. THE FNA AND AA LINE # of rings MUST MATCH!
The only exception to this would be if you have PRI/2 way DID's, which you don't because of your two digit DN's.
 
"Change the AA Line answer to 4 rings to match FNA on all sets that are assigned with this line, to 4 rings and this WILL FIX your problem. THE FNA AND AA LINE # of rings MUST MATCH!"

Sorry, but this makes no sense. As long as the AA ring timer is less than CFNA timer it should function correctly.

Like others have said 2.0 is buggy.

Marv
 
allworxguy- I know this makes NO sense- but this is one of the quirks of 2.0. Four rings was just an example, It won't change the O/attendant's appearance but will change the incomming calls going to general delivery every time, once this is done you'll know your on the right track. This is the starting point. He's assigned the attendant BOTH in the CICS and the Call Pilot which has created yet another software conflict. Now you have TWO auto attendants trying to do the same task.
Brutalis- if your still looking at this- Disable any and all AA functions in your CICS system programming, and let the Call Pilot's AA do ALL of the work. The CICS auto attendant and CP are butting heads!!!

 
Curly, are you suggesting you can enable the built-in CICS auto attendant AND the Call Pilot's auto attendant at the same time when both are programmed to handle the call diferently- Come on man-lol
 
True lol
Must be a 2 week vacation.

I am with Allworxguy where I dont get where AA and FNA are told to answer at the same time.
It does not make sense to me too.....yet!.

AA should always be a lesser ring count unless you want somebodies mailbox to answer lines.
I should be able to have AA answer at 0 rings and FNA my reception set to 3, 4 or 6 rings without issue.

Also I am not sure why the internal AA in the CICS is mentioned when it is a mailbox direction issue.

Thus why I thought you are offering a freakish solution to a known bug that you found by mistake.





=----(((((((((()----=
curlycord
 
Brutalis-- throw us a bone----what programming steps did you use to "make extention 22 dial 0 in "System programming"?
Curly, I know you know your "Stuff"-- what will this do?
 
That would allow internal callers to intercom 0.

I think it's bugged as well since in his first post he did everything to the T and even rebooted.

Upgrade to 3.1 is free and a 15 minute job and probably will fix the issue.





=----(((((((((()----=
curlycord
 
Gentlemen, I've been away for a while so no questions answered. Here's the set up: AA answers after 2 rings, (no ringing sets on incoming calls). Ext. 22 is the zero out from Voice mail and KSU. FNA to voicemail is 4 rings on all sets with a mailbox.
General delivery mailbox is disabled in F983 programing. All external incoming calls go to GEN. DEL when callers hit 0 regardless of voicemail/ksu programing. (internal zero calls go to ext.22 as programmed.) As a workaround I've got GEN DEL off prem notification to ext 22 and that works ok so they get GEN DEL messages but this should not be necessary. I'm thinking some kind of corruption. Any thoughts?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top