Search results for query: *

Never done it but done you need to be using the TURN/STUN configuration within the ASBCE. https://documentation.avaya.com/bundle/DeployingAvayaMeetingsServer_r91/page/TURN_STUN_for_WebRTC_calls_in_OTT.html

No. The feature needs a caller ID. It uses it to look for a matching user, by comparing to the user Twinned Mobile Number settings.

30 seconds is the normal timeout for SIP call setup not being completed. Some expected response has not been received. You would need to go through a full trace pairing off the invites and responses.

Then you may need to add some new entries and to do that you may have to delete some of the expired ones.

For my sins I've been given the task of crawling through a pile of Avaya end-of-sale notices. And just to prove that Avaya has always been a fun factory, I just came across a hoot in the end-of-sale for IP Office DL120/R210 servers (https://download.avaya.com/css/public/documents/101008944)...

Virtual server installs are only supported using the OVA (or the equivalent image for whichever virtualization platform you are using).

If Avaya haven't done whatever is necessary to make 3755/3759 the features work automatically through provisioning, then yes - you need either an charger that can be used for phone programming or an AIWS.

If its true T1-PRI (rather than through a SIP converter) then check with the provider that they have brought their end into service.

Further tested, fallback works with my analog extension (Combo card phone port) except for the unplugged scenario. So: DND off and no voicemail. On a call and no call waiting and no voicemail. Logged out.

Don't ever use xxxxxxxxxx as a fake number in discussion of IP Office shortcode - x actually means something in IP Office shortcodes. And your screenshot still included just a single + and nothing else. And as the folks have said several times now, wasn't set to actually be applied.

Hmmm. I had an analog extension involved but may have only done fallback to it, not from it (it was a frantic half-hour of testing at the end of the day). I'll see if I can sneak another 5 minutes.

Where is the IP Office - at your end or the hotline end? Were you testing your own system? Does this happen anywhere else (call you own mobile and test what happens when you hold the call). If you want help, add some details rather than just the bare minimum.

Look at what you said was in the short code at the start of the thread and what is in the short code at in the screen shot. 1) They are different, and 2) neither makes any sense. In the first, the user dialing 4444 is supposed to send +xxxxxxxxxxx but that's never going to happen since they've...

Just played with it and works for me with an extension as the fallback destination. The scenarios tested so far work with the following conditions for the original destination extension: DND on and no voicemail. All call appearances in use and no voicemail. Extension unplugged and no...

Brain fade on my part, just saw fallback and hunt group and recalled that there we're extra conditions for when it was a hunt group. I can test analog/digital/IP extension tomorrow. Analog is usually only an issue when its an analog line, not for internal analog extensions. Unless that no...

Meanwhile, the Do Not Disturb On and Do Not Disturb shortcode features do not use the telephone number field. In IP Office terms, that means you can't pass an extension number to the features using that field, they only work for the user dialing the shortcode. As said, a custom callflow in...

...except for the 11.1.3.2 Admin CD. Meanwhile, does one of the Rights Groups to which the Administrator belongs have System Status | SysMonitor Access enabled?

Not true, just not sensible as it makes issues with shortcodes and misdialling more likely.

"if the primary destination is a hunt group returning busy and without queuing or voicemail."

Different install but same software so it may give some hints: https://documentation.avaya.com/bundle/DeployingAvayaSBConaHardwarePlatform_r102/page/Password_policies.html