Leaseline1

We have the Avaya IP Office V2.1 and are experiencing a few issues that our technicians are not able to resolve. First, we are using FDN PRI trunks and our outbound caller ID is apparently set correctly by the carrier as a fixed phone number, however, our system overrides this and sends the callers extension only like "201". Any ideas how to change this? Secondly, we operate several companies and we have not been able to successfully set up multiple auto attendants without causing issues with our primary auto attendant. Any ideas here? Are there any concrete release dates for v3.0 coming and does it include updates for the problematic Phone Manager Pro? Ours has all sorts of erratic popping issues and logging out issues. Lastly, we are trying to use Fax-On-Demand through voicemail pro, but are not able to find supporting information on setting this up so we can use our fax servers to handle this. Any ideas here? We appreciate any help that anyone can give us on any of these items. Thank you!

Brazil

As for the outbound caller ID, the only way that IP Office would over-ride what the CO puts on there is if it was specifically programmed to do so, which makes it sound like they set up the shortcode wrong. The telephone number field of the shortcode should look something like this: Nsi5551234e replace the "5551234" with your area code, exchange, and leading digit and the "e" is replaced automatically by the extension number of the phone triggering the shortcode. If you don't want to send DID numbers out, just get rid of the "s" and anything after it in the shortcode.

The multiple auto-attendant question should be an easy one but could you give more specifics of what you're trying to do or how it's not working?

PBXtech.info

 

macca51

Re. the Caller ID. If your dial shortcodes do not include the "s" code, the IPO will send the DDI number matching the User in the Incomming call route. ie. if there is an incomming call route entry of DDI 201 going to User 8201, when user 8201 dials out, it will send CLI 201 to line.

Normally on ISDN the carrier rejects the 201 as an invalid DDI and overwrites it with your main number.

Only way around this is to add your main number as outbound CLI in your default dial shortcode ie
SC ?
TN .s55555555
Fe Dial

Phone Manager, Make sure you are using PM 2.1.8 and system 2.1.27 and you shouldn't have too many problems. Still small "Out Of Group" and divert prob as before, but much better.

V3 includes updated PM, but would avoid upgrading until trying the Maint release of 2.1 due March.

__________________
Keen Bug Farmer..

Leaseline1

Thanks for your suggestions. We will look into this Monday. I checked our PM agent versions and they are 2.1.7. How and where are these updated? Is it a server based upgrade that gets pushed out? If so, we'll try that. I don't see any upgrade options on the agent systems. I haven't heard about the 2.1 Maint pack. Do you know a link I can go to to read on this and other Avaya issues? When have you heard the upgrade V3.0 is coming out and are you hearing anything about bugs or reliability after the upgrade?

Leaseline1

Thanks for your suggestions and we will look into this Monday. With regard to teh auto attendant, we have 2 companies that we operate and we have followed the manual on setting up a second auto attendant, but it causes the first, and primary, auto attendant to cease working and stops answering calls. The extensions are all the same ones, granted some extensions will not be part of the second attendant, so I guess we are simply stumped on the correct process to set up the second attendant. We are familiar with pointing DID's, so any help on how to do accomplish this set up would be greatly appreciated. Our Avaya tech does not know how to do this. Thanks for your help1

macca51

V2.1 Maintanence release is due in March. Currently they are tielling it, so is not generally available.
2.1.8 Phone manager is available from the http:/support.avaya.com website, listed as User Patch 2.1.10
This still has a couple of problems, so may pay to wait for the 2.1.13 release in March.

What sort of Voicemail AA is it? Integral or VM Pro.

__________________
Keen Bug Farmer..

PBXtech.info

 

Leaseline1

I ma using VM Pro. Thanks for the follow up!

macca51

Without a picture of the setup it is difficult to help, but simply if two DID's point to separate Start Points, won't be a problem. You should be able to copy and paste the call flow into the second start point. You can also use Goto Actions or Modules if they are identical.
If using Conditions or Variables, there are a couple of common causes of problems I can list if you are using these.

__________________
Keen Bug Farmer..

sjcann

I would be very keen to know of any known issues when using variables and conditions in VMPro call flows as I am currently having problems with call flows just terminating without reason.