Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Associate IP Office With VM Module in VM Pro

Status
Not open for further replies.

AJ800

MIS
Jul 22, 2013
36
US
I created a Voicemail module (flowchart) of an incoming call answering sequence in Avaya Voicemail Pro. I saved it (Save & Make Live), then created a Short Code to point to it in Avaya IP Office, manually by adding a code *## and then typing the exact name of the module in that code (saved/merged). I tested it from my phone using that short code and it worked (menu items allowed dialing the correct extensions once connected). However, I need to associate this answering module to a new telephone number we are incorporating into this system, and from my understanding, this association is done in the 'Incoming Call Route' section of Avaya IP Office. When I select the test telephone number we're using to associate with this answering module (The entry was there already for a test telephone number, but it points to the main answering system, so if someone called the test number they would get the exact same answering sequence as our main number. For this test number, I'm basically mocking our main telephone number entry in the 'Incoming Call Route' section that we are currently using), I go to the 'Destinations' tab and under the 'Destination' drop down menu, I do not see the new Voicemail module I created for this number, unlike the other one that is there for our main number. How do I populate that drop down menu with the new module to be selected? There are actually 4 live answering modules in VM Pro (one in use, the other 3 were created for testing) but only the main one displays in that drop down menu. How do I associate other modules with IP Office?
 
just manually enter the shortcode you created under Destination. Once this is done it will be in the dropdown menu until you remove it.

***ACSS SME***
 
Yes that was it. It didn't look like you could manually type it in. Thanks. It works.
 
Using shortcodes in the incoming call route means you have no clue.
Use VM:module name in the incoming call route.


BAZINGA!

I'm not insane, my mother had me tested!

 
He might be an old guy like me because the VM:Module did not work all the time and sending calls to shortcodes has always worked reliably.

Joe W.

FHandw, ACSS (SME), ACIS (SME)



Interrupt the silence only if you improve it by saying something, otherwise be quiet and everybody will be grateful.
 
Short codes is for internal use.

Follow-up question (which I may make it's own topic): Is there some way to have the dialed number display on the end user's phone extension? For example: We have 2 lines coming in to this IP Office system: (111)111-1111 and (222)222-2222. (111)111-1111 routes to the answering module 'Sales Division' and (222)222-2222 routes to the 'Purchasing Division' answering module. While they are different divisions/numbers, the internal extensions answering these calls may be the same at times (Jane, at extension 123, may work 'Sales' in the morning, 'Purchasing' in the afternoon from the same desk). If a 'Purchasing' client outside our organization dialed our (222)222-2222 number in the morning, is there some way for the internal user to see which number that person dialed and/or their source number? (Currently, it only shows the source number of the caller, so the internal user at extension 123 doesn't know the call is regarding a 'Purchasing' inquiry)
 
You can enter text into the "Tag" field in incoming call route, it shows on the screen :)



"No problem monkey socks
 
You can also set that in de Transfer action in VMPro $CLI is the callers number and $DDI is the called number
But you also can set names there if you like.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top