Looking for some insight from the Unity Gods(tm) from an issue my customer presented to me. Unity 4.0(3)ES28, Domino 6.0(2) message store.
This system was deployed in December, and has been operating mostly trouble-free (other than the occasional, dcoumented Domino or DUCS integration issue). However the other day, supposedly out of the blue, a voicemail was sent by a user that was identified as being from another subscriber.
Typically these error reports are in error: A lot of times, Susie left the message from Bob's phone or whatnot. However, in this case, the phones are in different parts of the campus and the customer swore this was impossible.
After some digging, it turned out the two users in question had the same extension. This issue is two-pronged:
1. The system should not allow this, and
2. It was NOT like this from the get-go
The customer is quite sure it happened out of the blue; no changes were made prior to this happened. It has, to date, only happened this one time.
This certainly smells like buggy behavior, however, I was unsuccessful in finding anything in Bug Tool.
Certainly the SA wont let you add a new user or alternate extension or edit an extension such that it conflicts with any other extension in the dialing domain - when there's multiple boxes on the network there can be replication lag which will alllow this but that's not the case here. I've never seen anything along these lines - I'm reasonably sure Unity's not just randomly changing Extension values around on you, though, so there's got to be something else at the root of it.
I'm curious, does dbWalker note the extension conflict?
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...