As far as i am concerned we have no integration. when the call covers to vmail, the IPO is not providing the mailbox info. Audix answers as if one was checking their voice mail. i have had a CM-Audix engineer look at it, we both feel it is the IPO. We sent a sysmon to Catalyst and they had me...
We have an IP Office networked to Communication Manager R5 using the Intuity Audix LX2. We are not getting the audix to send the mailbox info along with the call when it covers to voice mail. all i see when i trace the call is the hunt group ext number for audix.
we have read the Avaya doc from...
We are installing a DuVoice to replace our Audix. We have the MWI working on Node 1, but not the remote switch using DCS and and IP trunk.Does any one know the solution?
Ref:
thread690-1229599
This thread was for R6 and no responses.
we recently upgraded our IPO 406V2 from 3.2 to 5.0. I am now getting complaints that hold recall is ringing back versus the hold recall beep and does not stop. i have copied the email from our office manager.
Calls on Hold:
Before the upgrade…when calls were placed on hold it would ring...
i am installing an IP Office Partner Version. Cannot get the loudspeaker page to work.
I assigned a analog station port as the page via TEI. now when i call the extension i get a busy signal. Cannot find the end user advanced tab in the GUI (IP Office Manager).
I have a Communication Manager networked to a IP Office. They were up and running and now the link is down. Status of the signaling group is "Far End Bypass". Anybody know what that means and or indicates off the top of their head?
Thanx
Interesting, it has been ZERO ever since voice processing became available how many years ago? This is something i expect from trunk slammers like Samsung.
Thanx for the answer
i have a IPO R7.0.5 that when somebody tries to zero out of a mailbox, the call goes nowhere and does not break dial tone. Some users have personal operators and some have the system default. what am i missing here?
i had to change the short code to vmail node, then change it back to vm collect.
we have 1416 telephones.
Thanx, got it to work. i was told a periodic bug since 4.x
I cannot get the voice mail short code for VM Transfer to work as indicated in thread 1638468.
code: #XXX
Feat: voicemail collect
Telephone Number: "#N" or "#"N or #"N"
I have a Essentials IPO.
Thanx in advance
verified she is in the hunt. The denial event indicates MCH enabled on the hunt, already logged in or ... something to do with EAS. you would think something so simple ...
They do have CMS but agent id verification is N. this person is the only one whose agent id does not match extension number...
yesterday when i was working with the end user, she was logged into hunt 50 and could not get into hunt 52. i had her log out of 50 and she could not get into hunt 52. Status station showed her in and out of hunt 50, otherwise i saw nothing unusual.
They are not entering agent id.
they enter login feature code and hunt group number. she gets waived off before she could even enter agent id. Her agent id does not match extension number like the other agents, but she can log into other groups. Does that help
I verified all hunt groups multiple call handling is none. Verified person is not logged into any hunt groups, had her dial the login feature code versus pre programmed button. Does not appear to be a logged in agent RTU. Compared hunt groups looking for misc error somewhere. The denial event...
A client is having issues with agents logging into various hunt groups.
We get the following when tracing the event:
denial event 1381: Agent login failure: D1=Oxc D2=Oxlfa
system features:
BCMS/VuStats LoginIds: Y
Validate BCMS/VuStats: N
they do not have EAS, they have G3csiV12
Everybody's...
where do i see "showrun protocol"?
they are provisioning 6 loop start lines out of the IAD tomorrow, then dropping local loop for dedicated PRI. The IAD cannot be programmed for NI1(custom). maybe some of the newer technology we're seeing will have bugs like this with Legacy equipment
thanx...
Thanx Jim,
that is my understanding as well. funny thing is when i first got involved with job site 6 months ago, i got the thing to work with the switch type as DMS 250. it had errors, but was functional. what ever the carrier did to their network, did her in.
Thanx again, it's good to have a...
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.