calls unable to reject on avaya j series phones for IPO 1

[rijustensilas]

Calls unable to reject on Avaya j series phones for IPO if Voicemail not active. there is any way to fix the issue, without enabling voice mail.

 

[IPOriface]

Calls unable to reject on Avaya j series phones for IPO if Voicemail not active. there is any way to fix the issue, without enabling voice mail.

Yes, there are likely many ways to fix this. It sounds like there's no route for the call to take, so fallback on the ICR or fwd on busy on the user are a couple of ways that come to mind. Need a bit more info about the circumstances like are HG's involved, is the user already on a call w/ no CA's free, are they DND/logged out, etc.

 

[rijustensilas]

extension to extension calls need to reject without enable or FWD.

 

[Mo. Abdullah]

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

 

[rijustensilas]

there is any alternative solution without enabling with voicemail or forward

 

[IPOriface]

there is any alternative solution without enabling with voicemail or forward

Apologies, I misread your initial question as "calls are rejecting"...

Did some testing and have confirmed that you're correct. Sysmon shows when the Drop key is pressed, the system attempts to retarget the call, has nowhere to go, and ends up retargetting to the user (instead of actually dropping the call), giving the impression that the Drop key is being ignored.

We setup a short code pointing to "Barred" and busy/NA forwarded the user to that, which didn't work, and we discovered that "barred" isn't a valid shortcode destination for busy/NA forwarding lol


OK so who wants to open a ticket with Avaya for this one


OP please advise if I've not understood your question.

 

[IPOriface]

there is any alternative solution without enabling with voicemail or forward

OK this annoyed us on a personal and fundamental level, so we kept at it...

Setup ICR with "block" as destination, drops external calls, doesn't work when user is forwarded to it

Setup a VMPro callflow with a Disconnect action, N/A fwd'd the user to a shortcode pointing to the VMPro callflow...
and....
IT WORKED!!! Woot. The drop button is now fixed at the tiny expense of a pile of tech debt lol

 

[snowman50]

If you don’t have voicemail pro..you could try using a shortcode button toTransfer the call to an AA with no answer disconnect.
I know you said you didn’t want to use voicemail..but we assumed you meant Mailboxes.
Technically if you want AA the voicemail functions need to be active

 

[rijustensilas]

I created ticket with Avaya last time but responses like we should sent the calls to Voicemail Pro.
I tested this scenario "Setup a VMPro callflow with a Disconnect action, N/A fwd'd the user to a shortcode pointing to the VMPro callflow". But customer not accepting this because they have other forwards too.

 

[IPOriface]

I created ticket with Avaya last time but responses like we should sent the calls to Voicemail Pro.
I tested this scenario "Setup a VMPro callflow with a Disconnect action, N/A fwd'd the user to a shortcode pointing to the VMPro callflow". But customer not accepting this because they have other forwards too.

If the user isn't using Voicemail, then how about turning voicemail on but making their LeaveMessage route to a disconnect action? Then if they're at the desk and want to Drop the call, they can; and if they don't answer the call just drops when it times out.