Warning in event viewer source: AvConvMsg

[arnieg]

I am getting an:

"Alternate Contact Rule Not Active for ch_"user alias" on line 790 in file e:\views\cs_UE3.1.4.39\un_ConvPhoneHandler\AvConvPHTransferSvr\AvSLoadInfo.cpp

Running conversation on PH Transfer On Port "number varies""

Any ideas about what this means? I am running Unity 3.1.(5) on a windows 2000 service pack 3 OS, exchange 2000

[lindborg]

Yes, that subscriber's alternate contact rule is not enabled - which is an error. Subscribers only have one contact rule active (as opposed to 3 for call handlers) and that's the alternate - if it's not active it can cause issues with the conversation.

dbWalker should pick this up and fix it automatically - you can get the latest version for 3.x here:

http://www.ciscounitytools.com/App_DirectoryWalker3.htm

[arnieg]

I am still a little lost. Are you talking about the "alternate extension"? Where is the alternate contact rule located and what is it's purpose? I am only having this issue with users that I have added through the subscriber admin page with a site associated subscriber template. I do not have this issue with any users that were created in AD first and then imported into Unity. I will run dbwalker to correct this issue, but unless I fix the original problem I will have this problem with future additions.

Thanks

[lindborg · Accepted solution]

It's likely a problem with one or more of your subscriber templates - dbWalker can rebuild your 2 default templates from scratch to help correct that.

That's the point, you don't _see_ any other contact rules for subscribers because only one is respected - the alternate. Subscribers only have one transfer rule that is used, so you only see one in the SA and only adjust one over the phone. But in the database it uses a call handler for this which has 3. As such it's important that the alternate contact rule associated with that call handler (called a "primary call handler" when associated with a subscriber) must always be turned on. There's no way to turn it off through normal means but if a template gets corrupted somehow or the like, it can happen which is why the conversations code and dbWalker always check for this.