1. Kinda doubt it's that (very old) memory leak issue - you'd notice AvCsMgr bloating like a mad dog, it'd be hard to miss.
2. ConvSub.DLL is used in all conversations - the first post on this thread is likely an unhandled exception which is not unheard of (i.e. the conversation engine gets the rug pulled out from under it if the call goes away before it gets a hangup event or the like). There's no way to speculate what the actual problem is without specific version information and traces.
3. The 2nd error (Randy's) is a different ball of wax - an entry point missing is likely a bug. If you're not getting rocketed to failsafe it's not likely a critical bug, but a missing entry/exit point is something that should be looked into. Again, trace info, version info and a TAC case would be called for here.
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...