Just found that this is a known bug addressed by a patch available through Avaya: 94xxT6.bin
Have to open a case to be offered the firmware bin file(s).
Good luck.
Upgraded a 406 from 4.1(12) to 4.2(17) and no longer could dial out. Monitor traps showed: 28 Invalid Number Format.
Has anyone run into this, and if so have you found that Technical Tip 212 which suggests adding "NI2_CALLED_PARTY_TYPE=UNKNOWN" to the source code tab of the 'NO USER" fixed it...
Thanks all,
That SSA conflict check sounds cool. I will look at it.
I wanted to update everyone that my issue was corrected by removing the name conflict across SCN. No messages lost last night.
Thanks again!
- cocola123
All,
I am rather certain that I found the cause of my trouble! This is a new customer for us, and I was unaware that there was another IP Office system connected via Small Community Networking. They have duplicate User Names in both systems. Apparently, housekeeping resolves the primary...
haironfire,
By the way, mine is a 412 at 4.2(49501) and VM Pro at 4.2(19). I am going to look further at what upgrade is available. I very well might include an upgrade of one or both as I take the steps I discussed above. I do not know specifically why the patch release 4.2(49501) was...
haironfire,
I too am having a similar issue. In my case, I have only a few mailboxes that lose their messages EVERY night. I have tried a few things that have not worked, so I thought I would contribute to this thread in hopes that we both get answers soon.
I have removed the actual...
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.