Separate Unity's

[t.dhaliwal]

I have two Unity's Vm only in a two separate locations. What is the best way to network them together so user can send messages between the two different unity subscribers?

[Brandon Buffin]

If the Unity servers are using a common directory, you can use Digital Networking which is included with Unity. Please see the link below for requirements and procedures for setup.

http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guide_chapter09186a008022cd84.html

Hope this helps. If so, please rate the post.

Brandon

[Ginger Dillon]

Hi -

Your networking options depend on how the Unity's have been designed. For example, if they are part of the same Active Directory infrastructure (same forest), you can digitally network them together. Digital Networking allows messaging among multiple Unity servers that access the same subscriber directory. Here is the networking document, which describes the requirements for digital networking, plus other options - http://www.cisco.com/en/US/customer/products/sw/voicesw/ps2237/products_device_support_table09186a0080531ba9.html#wp102015

Note: These options will require schema modifications. If each of your Unity servers is installed in its own AD forest, look at the VPIM networking. SMTP networking is no longer supported in the Unity 4.1 and higher releases.

Ginger

[t.dhaliwal]

Thanks for your responses. My two unity will not be part of same directory infrast. They will be totally separate AD domains. What is the other solution to network them together.

[Ginger Dillon · Accepted solution]

Hi -

That would be VPIM networking - you can read about it in the link I sent. VPIM is for Unity servers installed in separate directories. It requires a license update - the doc lists the requirements. I would consult with your Cisco account rep.

Ginger

[t.dhaliwal]

Thanks again.

[thisisshanky]

Ginger,

Hope I am not getting the wrong picture here, but based on this document,

http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_device_support_table09186a0080531ba9.html#wp102689

it looks like SMTP networking is supported in 4.1, 4.2 etc.

Also, Reading from "Cisco Unity Fundamentals" book a flowchart (Chapter 10, page 274) indicates that if both Unity servers dont use same directory, use SMTP networking with blind addressing. I will see if I can scan the flowchart off the book as a reference.

Since both Unity servers supports VPIM its definitely an option. Each server will need a $8500 (list) license to enable VPIM. I just dont see a cost justification for spending 17000$ on licenses to network them together when they could possibly be networked via SMTP (blind).

Thoughts?

Sankar.

PS: please remember to rate helpful posts!

[Ginger Dillon]

Hi Sankar -

Here is the document I read when we were on Unity 4.0(5) that referenced migrating from SMTP to VPIM networking - http://www.cisco.com/en/US/customer/products/sw/voicesw/ps2237/products_feature_guide_chapter09186a0080449a8a.html

We don't have a need, currently, for VPIM networking. Otherwise I would definitely have researched with Cisco and discussed licensing options, best practices etc.

Ginger

[thisisshanky]

Ginger,

Its quiet evident from the link you sent that 4.05 will be last to support SMTP networking. I am wondering how two documents could convey mutually exclusive info. Hopefully the documentation team reads this thread.

Or is it that 4.1, 4.2 will support networking via SMTP, but TAC wont support the config.?

Sankar.

[navinger]

Hello,

When the 4.0.5 Networking Guide was published way back when, the plan at that time was to discontinue support for the SMTP Networking option in subsequent Unity releases. However, the plan changed, and SMTP Networking does work and is TAC supported in 4.1 and 4.2.

Planning is currently underway for Unity 4.3, and I've heard rumors that the SMTP Networking option will definitely be removed this time (you won't be able to configure it). But this is still in the planning stage - no commitments yet.

You can always use VPIM Networking instead. When doing VPIM between Unity servers or between Unity and Unity Express, the license fee for VPIM is waived. Your Cisco SE or customer service person should be able to help you with the ordering.

Yes, the documentation is confusing on this point. I'll let the tech pubs manager know.

Nancy

[Ginger Dillon]

Hi Nancy -

Thank you for the great update :-)

Ginger

[t.dhaliwal]

Nancy, thanks for the answer. I have customer with 4 totatlly separate independent unity's. What is the best option to network? SMTP or VPIM? What is the best practice?

Thanks,

[navinger]

Hi,

If the message store is Exchange 5.5, then SMTP Networking is the only option.

If the message store is Exchange 2000 or Exchange 2003, I would recommend VPIM because SMTP Networking will eventually be phased out. Plus with 4.0.5 and later, there's the Automatic VPIM Subscriber Directory Updates feature, described in the Networking Guide here: http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guide_chapter09186a0080449aa1.html#wp1700940

If Domino is the message store, then VPIM Networking is the only option.

I know it's a boring read (I can say that because I wrote it :-), but the VPIM Networking chapter in the Networking Guide has lots of info in it: http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guide_chapter09186a0080449aa1.html.

Also take a look at the chapter "Using VPIM for Networking with Cisco Unity Express or Other Cisco Unity Systems"

http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guide_chapter09186a0080449a39.html

(I didn't write that one, so probably it isn't as boring.)

I've set up VPIM Networking on test servers, but never in the real world, so I don't now what to tell you with respect to best practices. If you have a more specific question, do ask.

Please be sure to read through this section of the VPIM chapter: http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_feature_guide_chapter09186a0080449aa1.html#wp1129559. It's the domain naming, DNS/host file stuff that seems to trip people up.

Nancy