MWI Extensions

[brown.george]

Hi,

Unity403, exchange 2000. Is there a quick way of changing the MWI Extension number in the MWI extension field for a large number of Unified users?

Thanks,

gmb

[lindborg]

What change were you wanting to make? Is it a pattern change for everyone (i.e. adding "77" to the begining of their extension for the MWI code) or is it more random for each user?

If it's a pattern you might be able to use BulkEdit depending on what it is you'd like to change - you can use the "X" to represent the extension on the "messages" tab and then tack on digits before/after. If you need to get more fancy than that, this wont work.

You can also use the CUBI tool to do this via CSV - check out the documentation for CUBI for more on this - you'll want to edit the "MWI_EXTENSION_1" column - this works well if you have more random MWI string changes to make for users.

[mbell]

My issue related to this is that the phones in CallManager have 4-digit extensions but the mailboxes in Unity have 7-digit extensions. We had to use the 7-digit extensions because of some overlapping extension/AMIS networking issues.

Calls that roll to voice mail work fine because we have a voice mail profile mask of 321XXXX in CallManager. The problem comes when Unity tries to light the lamp. The CallManager trace shows that the calling party number is the 7-digit extension, which will not light the lamp. I used translation patterns in CallManager to work around this and got it to work but the ideal solution would be to have Unity just use the 4-digit extension for MWI. Problem is, the 450 users were already entered in the system before I started working on this and it doesn't seem like BulkEdit can create MWI extensions like it can Alternate Extensions.

So, if BulkEdit can't be used and CUBI can't be used because the subscribers are already in Unity, is there any other alternative besides editing each subscriber individually?

[lindborg]

What version of Unity are you at? Recent versions of Unity ship with a CUBI that _can_ edit existing subscribers (it's not just for imports any more, despite it's name). You can edit the MWI extension for users in the system via CSV.

Check out the help file for CUBI, it has a section in there for modifying existing users. The CSV basically looks the same but there's a few properties you aren't allowed to edit in bulk via CSV (i.e. the Alias or SMTP address). This is probably your best bet.

[mbell]

Thanks, Jeff! It never occurred to me to check existing tools for new features. :-)

I tried using the CUBI to modify subscribers but I get a bunch of error messages like this:

(Error)

Unable to set the One Key Rule for the Zero Key.

Subscriber record: PATELBVM,XFER- 8620

(Error)

Unable to modify Subscriber record.

Subscriber record: PATELBVM,XFER- 8620

Yes, there is a space between XFER- and the extension for the call handler and I don't know if that makes a difference. It seems that when I used the BCHC, it automatically inserts a space between the name prefix and the extension.

Also, if you wanted to use the CUBI to set the zero-out destination to another subscriber, is this possible and would you use the subscriber's "TextName" as the Call Handler name?

[lindborg]

I doubt the space is causing a problem there - it's likely not finding the target call handler by that name for some other reason - but since CUBI isn't mine, I'll have to chat with the DB boys about it on Monday.

Were you able to change the MWI string, though?

[mbell]

Yes, I was able to make the change to the MWI string. Thanks very much!