Recent content by Bill P

this is the response from Avaya Ada. Avaya Communication Manager supports up to 6 levels of call coverage. However, the voicemail system may not be able to handle calls that pass through multiple coverage points effectively, especially if there are more than 4 points. Solution: Review Coverage...

note cov pa 200 is set to no for Cvg Enabled for VDN Route-To Party. not sure how your vector is set up. seems like a bug if its working with just 4 coverage points.

this is before numbering format after numbering format change.

one thing to check is to make sure the route pattern or aar are set to unk-unk for numbering format. when you dial the pilot number of voicemail does it ask for just your password, or does it prompt you for extension and password? (this will determine if its integrated)

do you have a proxy route on the locations table? and are you synching that CM with SMGR in the inventory? and just to clarify, you are using 1 voicemail system for 2 different CM systems? and they are all connected to the same ASM/SMGR environment?

Also, is the trunk set to public or private? And do you use the calltype analysis table? And I'm assuming the DIDs got moved over to the new trunk?

Keep in mind that even when you get what appears to be a traditional PRI, they are most likely SIP on the back end...so you can still have SIP type issues.

Did you convert to SIP trunks? If so you probably need to change the setting on page 2 of the station form Per Station - Send Calling Number and Name? to yes. It defaults to no.

depending on the version of your CM there is now a calltype analysis table that can manipulate digits. Here is how the numbers flow through the Avaya system.

yes Night Destination is what I meant. One other option you may need to change is on the console screen. Allow Night Service Calls To Forward? may need to be set to yes. Let me know if this works.

also, is your VDN set to yes for VDN override? Have you tried using the hunt group in the coverage path? I'm assuming your vector is just configured with a "messaging" step that sends it to a hunt group.

sounds like a COR issue...like the trunk COR is restricted to the COR of the VDN or something like that. Either that or a tenant restriction. Make sure on the 2nd page of your tenant that it can talk to all the other tenants (all tenants except tenant 1 are set to no as a default)

Is 0 configured as "attd" in your dial plan parameters? Are you using actual attendant consoles (if you run the command list attendant are those the ones you use?) Do your attendants log into a queue? Is the tenant configured with the same attendant group as the attendants? If you are using the...

I'm not sure on the IPO side, but I know you can accomplish SSO on Avaya Aura with AADS (Device Services). Do you have a System Manager in your environment? I'm not sure how you would accomplish SSO for digital sets since they dont really have a login since they are hard coded to a physical...

I would try the setting on page 2 of the station "Bridged Idle Line Appearance" I think that forces the call to use the call appearance of the bridged station instead of using your own call appearance for outgoing calls but it sounds like you may have already tried that. How do your stations...