Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Unity svrs in diff sites across a WAN

'ere be a few questions:<br><br>Existing Environment:<br><br>2 sites with 1 Unity server per site configure for UM users & VM only users within a CCM cluster (1 x publisher & 2 x CCMs at 1 site, 2 other CCMs at the other site). Site separated by a WAN link.<br><br>Qs:<br><br>Can I have 1 voicemail number that users use for both Unified users and VM only users across both sites? Is it possible to use 1 VM number for UM users and 1 VM number for VM only users (with the same numbers at each site - as far as I'm aware you can only setup 1 VM number up under service parameters in CCM. Is it simpler just to have 1 VM number for all users to call and if so would I be right in assuming I set both Unity servers & all CCM service parameters the same.<br><br>Can you recommend the best practice for directory alpha searches across 2 Unity locations as we will have. Will 1 dialing domain be sufficient, or are there considerations on the # of domains to the # of users? <br><br>Can you offer any advice/potential problems with using the import util to import subscribers using csv files (er, upto 1000 at a time!). What are the essential items in the .csv (will just name,alias,extension & their homed Exchange server be ok)?<br><br>Can a user dial their mailbox and check for messages from a different extension. I haven't had any joy testing this.<br><br>I think that'll do for now...<br><br>Any advice/experiences/tips folks have had with configuring Unity servers in different locations would be greatly appreciated.<br><br>Cheers for your help in advance,<br><br>d1nnsear<br><br><br>

1 REPLY
Anonymous
N/A

Re: Unity svrs in diff sites across a WAN

OK… several questions from different parts of the field here… lets see if we can knock these down one at a time.

1. I’m not sure how you’d work one number for everyone… that’d be awfully tricky. Subscribers must dial into the Unity server they were created on (i.e. you can’t check messages from another Unity server). The recommended method here would be to have everyone in site A have their messages button setup to go to their local Unity server and everyone in site B to have their own. When calling in from the outside they will need to use different DID numbers. I don’t think there’s any clean solution that gets around this. Eventually we’ll work out the security fun with Microsoft (i.e. some MAPI fun) that will allow us to let users check their messages regardless of which Unity server they dial into on a network but that’s not the case now so we have to live with this restriction.

2. no, there’s no real need to worry about the number of users in a dialing domain. A dialing domain is defined, however, as a span of users that can pick up the phone and dial each other directly without having to use trunk access codes or the like. If you have a single CCM cluster setup such that there’s no overlapping extensions or the like, I would think one dialing domain across both these sites would not be a problem. If that’s not the case (i.e. you may have and extension 2001 at site 1 and 2) a single dialing domain is a no-no.

2.5 another note: If you don’t mind doing release transfers you wont have any problems with a single dialing domain here. If you want to use supervised transfers (i.e. you want to use call screening and/or holding features in Unity) this wont work well. We can’t do supervised transfers across Unity servers in a dialing domain. Most folks use release transfers so this isn’t usually a problem but I thought I’d mention it anyway.

3. The only required data for a CSV import is a first name, last name and an extension (an NT alias is derived from the names). You can, of course, provide specific aliases and other information but those three columns must be filled in for the import to accept the row. Remember, you can only import via CSV for new users (i.e. not users that already have NT/AD and/or Exchange accounts setup). If you want to import standing users you have to import account information from Exchange instead.

4. Yes, a user can call in from anywhere to check their messages. If they call from an extension number that extension is searched for a match among subscribers. If one is found they are automatically logged in as that user, if no match is found they get the opening greeting and they have to press “*” to enter the subscriber sign in conversation. From there they provide their Subscriber ID and their password (if set) to get at their mailbox.


Jeff Lindborg
Unity Product Architect/Answer Monkey
Cisco Systems
lindborg@cisco.com
http://www.AnswerMonkey.net (new page for Unity support tools and scripts)

90
Views
0
Helpful
1
Replies
CreatePlease to create content