Recent content by Mo. Abdullah

enable the voicemail or enable forwarding for the extensions and they will be able to reject the calls.

check this config on IPO 500 v2. it might help. navigate to System >> Telephony tab >> Tones & Music subtab . check the Busy Tone Detection check box and choose system frequency. save config. reboot. if already checked, disable it. or choose single frequency. try both. and reboot.

these files must be in wav with 16 bit rate - 8KHZ - Mono. for embeded vm for AA: you can use the LVM tool from Manager application to convert them to a c11 AA prompt files. check the attachments. rename the files as you want without spaces and special characters with the tool. or rename them as...

as my knowledge the host ID will be changed every time. you just need to rehost the license from Avaya PLDS site. or contact Avaya service desk to rehost it.

the digits that coming from the call center sip trunk to IPO 500 should start with 7 to have a short code match on the trace. and in the incoming call route destination you can make it "7N" or "." example : on the call center system short code for outgoing calls must be 7N / Dial / 7N / Line...

the digits that coming from the call center sip trunk to IPO 500 should start with 7 to have a short code match on the trace. and in the incoming call route destination you can make it "7N" or "." example : on the call center system short code for outgoing calls must be 7N / Dial / 7N / Line...

try the below config on IPO and test. System >> Telephony Tab >> Tones&Music subtab

Hi everyone, I have an issue during receiving a call from a SIP trunk created with the service provider to an Extension logging with Avaya K175 vantage registered on IPO Server Edition R11.1.3.2 The external number displayed on the vantage screen while receiving the call is repeated/ duplicated...

this is a certifcate issue. upload the provider certificate to the IPO 500 v2 or download the certificate of the IPO and upload it on the provider side.

I face the same issue, but all I know it will be achieved using Orchestration designer scripts. You will need to convert the IVR from Graphical flow to scripts. i really don't know what these scripts are like or how to be done. still searching.

in the latest upgrade and release note of R12.1, Avaya confirmed that the upgrade is available directly to R12.1 from R11.1.3.2 because of the issues of the R12.0 and it's Rocky Linux systems issues.

.

What is your Solution? Aura or IPO? I need more explanation of what configuration you did for deps 1, 2, and 3. Does each dep have its own outgoing trunks?

how is the AA getting down and how did you know that the AA is down? what is the IPO Edition? can you check this with 2 Extensions, one in the destination and the other in the failback destination then disconnect the destination Extension and check if the calls go to the failback extension?

I have seen this on SIP trunks, IP Office and H.323 Lines but never seen this working with E1 PRI Lines. I can't deny or confirm what Avaya Said. You can escalate the ticket to Tier 4 Managers and they will give you the final response. and ask them to get back to the development team with...