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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Voicemail Pro 9.3.1.1 new, not connecting to IPO 5.0 V2

Status
Not open for further replies.

telbouy916

Vendor
Aug 27, 2015
32
US
First time here, hello!
Scenario,
IPO direct connect to Win7 PRO PC all updates etc seem as proper.
short code present to dial AA
simple modules start, menu, 1, 2, 3, 0, ???
Xfer to specific ext's. dial by last name also.
No MB's will be created
AA greeting done from EXT 300 and saved, plays back.
Made live.
IPO VM type set to VM PRO/Lite
Incoming route set to AA:Same name as the module

Delima: cannot access AA using short code and calling into the system the AA does not answer.


 
If you're using VM Pro you ICR should point to VM:module
AA: is for AA in Embedded.

"Trying is the first step to failure..." - Homer
 
Hi Jani,


Thanks for the suggestion however the issue remains the same.
Incidentally the system is freshly installed,
Dell 745 USFF 2 GB memory, 7200 RPM drive bare bones other than the OS and VM PRO.

 
I assume it's v9.1.3.

Have you set the Voicemail Password in security settings and entered the same password in VM Pro Client?

"Trying is the first step to failure..." - Homer
 
its VMPro9_0(311)(1)
i'm not aware of this setting as the manual mentions there's no need for specific password?

I have no notion how this is done however the VM PRO shows the PC is connected



Thanks!!
 
HI Intrigrant,

Dialing *17 renders "unobtainable" on the diaplay.

we set shortcode (s) *5494 and *80 as voicemail collect
the scripts used were "?"AutoAttend and "AutoAttend" which match our module name.

any ideas?

Thank you!
 
had this happen to me several times, erase your security settings then you will be prompted to enter passwords for Administrator/security and then system password. then stop and restart service and you should be good to go.
 
also if you change your voicemail pro password in security settings, make sure you also define the new password under preferences in the voicemail pro client or it will not work
 
Thanks everyone!

we of course created a shortcode to access AA which now works as we can now hear the greeting when the shortcode is dialed however then the facility is called we hear the built in Avaya greeting instructing the caller to dial their extension.

Hmm, wonder why the .wav file is not playing.

simple module setup, 1 greeting yet the greeting doesn't announce.

we've reset the security settings. from here sis not add a voicemail password in manager security.

Any thoughts on this one? pretty please?

the last time we had issues with in this manner was on an old 406 box and VM PRO 2.X

Thank you!!
 
@ Telecomboy

we applied shortcode to the inbound route several times, apparently klunked along and finally worked :)

Now the AA greeting is heard when inbound calling, dial by name doesn't work.
I mean this is such a simple module.
 
DBN is only working if you have the users names recorded

Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter
 
Hey Westi,
Thanks for this tip however all users names were recorded however in embedded voicemail.
 
do you have a transfer action after dial by name with the $key under specific in the transfer action
 
That's a different product so those recording aren't used. They need to re-record their names.

Stuck in a never ending cycle of file copying.
 
you mention embedded voice mail and voice mail pro, which is it
 
It's VM Pro 9.x.x
My understanding is the mailboxes etc would replicate to pro however we don't need mail boxes, only need the following
1 for sales
2 for medication
These work properly..

3 for dial by name
1??
2??
3??
These do not work.

We have tried assisted transfer and transfer using $NAM

Simple "AutoAttend" just isn't working.

Can we record names without creating many modules?
 
$key under specific on transfer action as stated earlier
 
Hey Joe,
We tried a few $ key options in transfer action.
Perhaps we used the incorrect keys?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top