Search results for query: *

I haven't used their new multi-cell but I have used the W60 and it works fine with 5111 licenses. I've also used the Ascom DECT solution and Cisco DBS-210 + 6825 sets on the 9100 and 9300 with no issues. The Cisco DECT sets are quite nice to use and also support wideband audio:

I can confirm the 6400 series sets work mostly fine on 12.1 as well. About the only weirdness I've seen is when you press # it comes up as a £ symbol. I use the UK English locale so wonder if it's some form of find and replace for the regional settings.

I do always forget that BRI was never that popular in North America. Just about every CICS I've encountered here in Australia has BRI trunks including the one I had installed at home over 20 years ago (BRI was cheaper than 2 POTS lines). The Australian MICS doesn't need a keycode for 10...

I haven't used that specific one on the IP Office yet but I am using Grandstream HT818 units on my R12 IPO for remote analogue stations and they work fine (with 3rd party SIP licenses). As IPOriface said you need to create the extensions as normal and then configure the ports on the Grandstream...

Plenty of deployments still out there with PRI to SIP gateways. My MICS gets a PRI from my Cisco ISR and works just fine. It outlived my BCM which switched its last call about 5 years ago.

Even though they look like ethernet cables, they're not. The system uses a proprietary protocol to connect from the main unit to the modules and any distance longer than the included cable will throw out the timing and cause you a world of grief. If you can't run twisted pairs for the analog...

CUCM itself is a virtualised/software platform and doesn't have ISDN as such so the Cisco side of the PRI is likely terminating on a Cisco ISR or similar device. Are you able to run an ISDN trace on this device? It's entirely possible that there are number translations occurring there...

These sets do the same thing on Aura too and it's quite frustrating: https://www.tek-tips.com/threads/j179-display-question.1828747/post-7565401 I never found a fix for it but would love to know if the behaviour can be changed.

You will need a license for an Avaya IP Endpoint to use this phone on your IPO.

UM8000 has nothing to do with InMail.

I wrote a script that uses 'sox' which is preinstalled on the Server Edition/Application Server.

The J179 will run just fine on earlier versions in H323 mode and will identify themselves as a 9611. It will have the older interface and won't support the wifi/bluetooth module but otherwise it's a good intermediary step before upgrading.

Why don't you just buy 3x MOH players, load the audio file onto them, and plug them into the MOH port on your 3x IPOs?

Not to mention the microwaves. If you have a customer site that has voice/wifi issues around lunchtime every day that's a likely culprit!

I concur. I do this at home for some J179 sets I can't easily get cabling to but wouldn't roll them out in a commercial environment unless they were occasional phones (kitchen/lobby/etc). Even though I have a commercial grade Cisco WiFi network at home they're still lacking and will...

The 18D is a Partner set. You might have more luck posting in the legacy SMB forum which includes Partner.

Not to mention new handset firmware now requiring a PLDS login (something I always appreciated with Avaya was them making set firmware freely available). The mention of license files to unlock "enhanced features" in the latest J100 release notes is also a bit concerning. I wouldn't be...

They used to have the H200 series but I think they were discontinued recently.

You could just get a generic ATA and third party SIP licenses. I use Grandstream and Cisco ATAs on my IP Office.

It's definitely not a supported configuration but I can confirm that if you extract the older TTS RPM files using rpm2cpio and put the files on the file system (they live under /opt/Loquendo/LTTS7) it works just fine.