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

Company Greetings on a Call Pilot 150 3.1

Status
Not open for further replies.

srachmaninoff

IS-IT--Management
Jun 2, 2008
122
US
I am working with a MICS 6.1 and a Call Pilot 3.1. Company greetings are recorded with all associated CCR Tree programming. When lines, whether PRI (target lines) or analog, are programmed to appear and ring on the sets, everything works like it it supposed to: the company greeting plays, then the CCR recordngs and all call processing takes place. However, the customer does not want any incoming phone lines to appear or ring on any sets. So everything rings directly into the Call Pilot. All Analog and PRI lines have the Prime Set programmed as the Voice Mail Pilot number. All calls go to voice mail as planned, without appearing or ringing on any sets. Now the company greeting will not play anymore. The customized company greeting is still recorded. Callers now hear the auto attendant default greeting and then the custom CCR Recordings. The lines programming in the auto attendant does not have any impact on what is happening here. Can anyone help here?

 
You need to tell the AA to answer the Analog and Target Lines on 0 rings. Just having the Vmail DN as Prime isn't enough.

"Adversity is Opportunity
 
I have tried that: 1 ring, 2 rings, 0 rings. That all seems to have no effect on the problem. When programmed for 2 rings, for example, voice mail answers immediately anyway, it does not change.
 
1. Verify that no phones are currently being fowarded to voicemail.
2. Verify your line numbers for your analog lines-on 6.1 i think it is 031-034 for lnes 4-8.
What lines are you testing on when you call in?
What greeting table are you using?
 
On one of the systems the analog lines are 1-4 and the PRI is lines 31 to 53. On another system, for testing purposes, I am using a T-1, lines 1-24 and analog lines 25-28. Both systems are behaving identically.
 
Do you have the lines set to answer under F982?
Also check and see if the the system is in Bussiness open oe closed status.
 
If you have already tried a reeboot put all of the settings on a different greeting table.Move gretings and lines and assign them to new table.
 
Yes, business is open, yes, answer lines and yes, attendant available
 
Verify the CallPilot ports on the Norstar have no lines assigned.

War Eagle!
Lions Baseball '09!
 
No lines are assigned, however I did try that approach as a possible solution to no avail.
 
The only way calls can be answered by the AA, without having the AA programming effect it is if, the lines are ringing on the Vmail DN, or it's in a Service Mode.

Reboot Call Pilot.

"Adversity is Opportunity
 
The Voice Mail has been rebooted many times. The problem seems to be related to the Prime Set of the Trunk/Line data configuration being set to the Voice Mail pilot number. I don't know how that has any bearing on the company greeting and how to work around it.
 
For anyone concerned, I was able to fix the problem by using the services programming. I took all of the extensions out of ring group 1 except for the voice mail plot number and the auto attendant works perfectly in night services mode. Put the system back into normal ringing and the problem is back. Thanks DeweyHumbolt for the recommendation
 
Curious... You referred to the PRI lines by trunk number. The target lines start at 145.

You did say the analog ports behaved the same way, but the Line programming under AA should be programmed for the target numbers, not the ports.
 
Normally I would agree with you, but in this case the lines programming did nothing! I repeat, nothing! Even now the system is working as requested with no lines programming involved, no target lines and no analog lines. The key to this solution was the night services programming and the Prime Set configuration in the Trunk/Line Data. I can't explain it, I never would have reason it out. The solution to this problem was discovered through mere chance with a dash of trial and error.
 
And a lot of hair pulling, I'm sure.

Customers never want to pay for troubleshooting when everything's working, but if you ever figure it out, let us know.
 
I am making notes to be put in that proverbial file of "solutions to once in a lifetime problems.
 
I thought the early bugs on the first 2 6.1's were strictly PRI AA related. Maybe they were analog, too.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top