IPOPE 7.023 PRI DID ring phones then go to AA

[socalsteve]

I have tried everything and cannot get a DID to ring a single extension, hunt group, calling group, or operator group and then go to AA day or night. The only time it will go to the AA is if i send it straight there.

 

[madwok]

Check VMS setting / Delay / Schedule

 

[CarGoSki]

Are you using the fallback destination combined with a time profile on the Incoming Call Route table?

You really have not described how it is currently programmed. Just general symptoms. Your description translates roughly to "it doesn't work". If you are a technician then you know that the cause and solution is in the minute details.

 

[CarGoSki]

I have to admit that I typed up a resolution for an IP Office and not Partner edition. It is funny that I almost posted the rules of a Partner with a T1 where you can have only one destination and cannot route to a user then auto attendant for T1 DIDs.

Your solution will be in how you have setup the programming. But you need to list the details of your setup including what type of T1. While you are waiting you can browse the configuration settings for a PRI here >

http://marketingtools.avaya.com/kno...rtner/mergedProjects/manager/pri_channels.htm

 

[socalsteve]

It doesnt work and thanks to me and all my troubles avaya has posted documentaion stating it doesnt work.

 

[CarGoSki]

Perhaps the best solution is to hire a Avaya Business partner to look at your system.

 

[socalsteve]

IP Office Partner Edition: PRI lines directed to a Calling Group will not cover to Auto Attendant


Document Id: KB01106304
Last Modified Date: 10-07-2011
Support Goal(s): All Others (IP Office), IP Office
Access Level: External Entitled


Version-Release


Partner Edition

Details


Customer uses PRI services. Channel setup is programmed with VMS delay day and night to get answered by automated attendant. Calls ring into the Calling Group but never get answered by the Auto Attendant.

Description (Problem Clarification)


IP Office Partner Edition: PRI lines are directed to a Calling Group but will not go to Automated Attendant after programmed time interval.

Cause


This is a limitation of Partner Edition Software Programming. DID mapping overrides the Coverage Destination settings of the PRI channel setup.

Problem Fix/Workaround/Solution


Partner Edition does not have Calling Group overflow. If a customer wishes to have calls come into a Calling Group or a Hunt Group and use VMS coverage to an Automated Attendant they need to use Analog lines or a T1 set for Automatic signaling. Otherwise consider IP Office Standard Edition so that the overflow can be administered.

Resolution Plan


Hunt Group and Calling Groups cannot have a delayed Auto Attendant setup if DID mapping is used on IP Office Partner Edition. If the customer uses DID or PRI services an IP Office Standard Edition will allow them to overflow to an Auto Attendant.
Best Regards,
Jerri

Jerri Cybyske | Global Remote Services, Small & Medium Enterprise Communications - Backbone Engineer | ACSS |

 

[socalsteve]

I am a business partner. I also have all my Avaya certs.

 

[SYQUEST]

Well, you can always get rid of the PRI...

....JIM....

 

[CarGoSki]

So some of the coverage limitations of a Partner ACS T-1 do appear to have been imposed on IPOPE PRI.

Also I thought that you were looking for assistance and not simply making statements.

 

[socalsteve]

Check the dates on all the posts...... I had a problem, i posted my problem, there is no fix, you posted in reply to my problem, i posted in reply to your post..........?

 

[socalsteve]

By the way avaya over nighted me all ipo standard equipment for the customer at no charge.

 

[CarGoSki]

I had asked for you to post how it was programmed. You did not.

No offense. I did not understand what you were tying to accomplish.