Button Programming - Outgoing Caller ID

[R2_]

Hello All!

I'm looking for some pointers/assistance as my poor brain just can't seem to figure this out...

Avaya IP Office 500v2 - 9.0.12
Avaya 9608G
Voicemail Pro 9.0.12

Goal: Allow user to press physical button on phone to use a predefined outbound caller ID for a specific call.

Example: We currently use 9 for an outside line, then the user dials the destination number, system sends main CallerID - all good.
When the user is returning a specific type of call, we want to be able to present a specific CallerID for that call. I would like to
use a button for this so that I can label it for better user adoption. Calling sequence preferred = press button, have it prompt for destination number, then it dials out.

Current knowledge: We have 4 sites and about 350 users. My personal knowledge is limited but I love to learn.

I know I can use a shortcode, but that's at least 3 button presses and the user would have to write it down to remember to use it. Just trying to make it as user friendly as possible.



Many thanks in advance for any tips/pointers... reading the help documents get's me super close but I can't seem to get the buttons just right...

Best,
Richard

 

[critchey]

You did not specify the kind of lines you have so I can't give exact info on how to output the callerID you want. However, if you say create a 8N shortcode to output a different callerID, then make a dial button that dials the 8 for you it would do what you want(A dial button with a 8 will let you continue dialing.)... its a waste of a button because they could just hit 8 and number and it would use that callerID but I have done this before.

The truth is just an excuse for lack of imagination.

 

[derfloh]

The only thing I can think of is to create several ARS forms. A main ARS form the user uses and a second ARS form that sends the other number.

Then create a button that takes the first ARS OOS. I'm not sure if this is available as button function.

Need some help with IP Office?

https://www.fwilke.com/home

CLI based cale blocking:

https://blog.fwilke.com/ip-office-block-calls-from-specific-cli/

SCN fallback over PSTN:

https://blog.fwilke.com/ip-office-scn-fallback/

 

[R2_]

@critchey
Apologies - PRI line

We currently use the 8 and 9 for dial out callerID and hold music setting/options...
Maybe I just need to do a 7 ...

I don't know that this is super scale-able, but I may be asking too much from the buttons LOL

Thank you !!!

 

[R2_]

@derfloh

That's an interesting idea for sure! I'll have to test it out and see!
Thank you for that option!

 

[telecomtekperson]

The other option would be MADN buttons.

Create a dummy user, set that users dialing for outbound caller ID...
Now you can go to a users button programming, and create a MADN Appearance button, for MADN Multiple.

Now, when that user presses that button, it will dial out like it is that Dummy extensions caller ID...

 

[R2_]

@telecomtekperson

I would love to be able to do that, that's got to be the slickest way to do this! Unfortunately 9.0.12 doesn't have MADN options...

We're soooo far behind in updates... we're just trying to look at the server edition setup / costs.

 

[derfloh]

Oh yeah... MADN... I wrote something about that option a while ago:

https://blog.fwilke.com/use-case-ip-office-madn/

But with 9.0 not possible.

Need some help with IP Office?

https://www.fwilke.com/home

CLI based cale blocking:

https://blog.fwilke.com/ip-office-block-calls-from-specific-cli/

SCN fallback over PSTN:

https://blog.fwilke.com/ip-office-scn-fallback/

 

[critchey]

Just use 71N, 72N, 73N etc if you have a bunch of numbers. Could even be 711N 712N 713N if you have just a crap ton of numbers. Then button dials the dial out code for you and bobs your uncle you are automagically selecting the correct callerID and just have to dial the number you want to dial.

The truth is just an excuse for lack of imagination.

 

[R2_]

@critchey

Your solution is a hit! Works like a champ!

Thank you to everyone! I'm looking forward to our departure from 9.0 but for now you've helped put this one issue to bed!

I'm forever in your debt!