I've rebooted the Audix server and I'll have to check with the department that uses the number a bit later since the number is heavily used during business hours.
I'll update tomorrow.
When checking the message on x7346 the message was not there yesterday when the call was received at 6AM. It did show up this morning on x7346 with the time stamp from yesterday when the vm was checked.
When this 800 number is called it routes to a vector, which routes to extension 7346.
- 7436 then goes to a coverage path 73
- coverage path 73 goes to coverage answer group 11, then coverage answer group 12, then voicemail.
The issue is that the aut-msg-wt light doesn't light up all the time...
The x-ported station is setup as a 6408d+ and on the second page I had the following:
LWC Reception: spe
LWC Activation: yes
Audix Name: audix
***Did Not Work****
---------------------------------
LWC Reception: audix
LWC Activation: yes
Audix Name: audix
***Did Not Work****...
Another issue just came up, I was able to make long distance and local calls out of the PBX prompt for an authorization code by using FRLs in the COR, but I cannot figure out how to make a toll-free number prompt for the auth code.
Any suggestions?
I've setup the extension as an X port and setup vm in Audix, but the phones being used are 9611Gs emulated as 9620s on our system.
I've made sure the extension had no vm's in it and then setup the button, called the extension, left a vm, but the message light does not light up.
Any suggestions?
Can anyone tell me, if possible, how to program a button to show that another extension has voicemail?
I'm trying to setup an 800 number to route to a voicemail if it's not answered. Once that 800 number leaves a voice mail message I'd like to have multiple extensions be able to see that new...
We have a paging system that is setup as a DAC type in our Dial Analysis Table, so when users dial 7400 they can page within the facility.
Since this is setup as a DAC type, when we setup phones to have a COR that restricts "Calling Party Restriction" to "outward" or "originating," then those...
We ended up fixing this issue. Our long distance trunks were not PRI, they were TIE trunks, which do not allow EC500 to work. So we ended up creating a new routing pattern so long distance cell phones use the local PRIs to go out.
Thanks anyways.
We have EC500 working fine for most users, but we ran into one area code that will not translate correctly when dialed thru EC500. Below are the trace results of the dialed number.
We dial 8 to get out, not 9 because years ago before I worked here the employees made it a habit to dial 911 to...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.