Search results for query: *

Looking to upgrade a customer to R10.1 or R11 and they still have 4400 series phones. I know Avaya says they are unsupported, but has anyone tried them? Often unsupported phones still work.

Circling back to this thread. Has anyone tried the 4400 sets on R10.1 or R11? I know its stated they are not supported but do they work?

sizbut? why reply at all? what is the value of your comment? Of course I asked Avaya. I'm asking this forum as well. Below is Avaya's response in case you'd like to see it. Atac: "I reported this to the A1S programmers and this was the response I got back: J169 and J179 are already...

Thanks intrigent. Is there a document that states its supported on R10.1 SP3?

Has anyone got the J139 phone to register to R10.1? AIS allows you to design an R10 licensed system with J139 (J169/179 are greyed out). Yet all the documentation says R11 is required for J139. Why the contradiction?

You read that correct. Not H323 to SIP. I have a customer that already has these phone on SIP firmware and needs to convert them back to H323. Has anyone had any luck doing this before?

Our Distributor doesn't think its possible. Could you detail the process so I can follow up with them with some ammo?

Also, just to note, we do have a current IPOSS contract.

We have a customer that had multiple projects going on at once. They were deploying 3rd party licenses on 9.0 and upgrading to R10. Unfortunately they ordered 3rd party R9 ADI licenses that were received after the R10 upgrade. So now we have system running R10 with PLDS licensing and we are...

Just found out you can buy the lowest denomination of an old license. You can still buy licensing such as T1 channels but only in 2 packs, not the 8 packs. Material code 215180 is still available in A1S. Case solved.

We have a new customer that has a 500v1 and is still back on R5. We are upgrading to a 500v2 and R9.1 later this year but they are in need of more PRI channels now. Is there a material code that is still available that will work on 5.0(20). 215181 is no longer available in A1S 275641 is...

thanks amriddle01, have you got this working with server edition 9.1? I've seen it work as you described on 9.0

janni78, Why is the mac sofphone different from Avaya Communicator in that regard. With Communicator, you can log in "simultaneous" with an H.323 desk phone. I've used older versions of the mac client on 9.0 and it at least logs you in and while logging out your desk phone. Is 9.1 different...

Thanks amriddle01. So in a normal upgrade, without the hardware swap, is it the 500v2 that realizes an upgrade occurs and check for the license?

You must have a standard IP endpoint license for the E129

We have a customer that is on 8.0 today and they already have a 500v2 but it is dead. They have purchased a new 500v2 chassi that is on 9.0 and are wondering if they can follow the below process without needing an upgrade license. Back up configuration, recreate existing SD card from 8.0 to...

I do have 5 URI's (each with 6 max call paths). So that's where the 30 number comes from. So there is a way to wild card the URI?

Workiing on an IP Office 9.1.7. When looking in system status it shows the number of administered channels is 30. We only have 6 license for SIP Channels. The max calls per channel in the URI is also set to 6. Where is the 30 number coming from?

Yes, we are using 9.1.6. Should we upgrade to 9.1.7?

We have a customer using a sip trunk and everything is working fine except there is no name presented on their 9608G phones. They receive the full 10 digit number from the caller but there is no name presented. When we go to the call log to look at the missed or received calls in more detail...