Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Mitel 5000 UVM dial by name issue

Status
Not open for further replies.

yankblan

Vendor
Jun 17, 2010
831
CA
Don't know if it's a flag somewhere, can't find an answer.

When I set up a Call Routing Announcement with a dial by last name key, I have to spell Smith by pressing 7 x4, 6 x1, 4 x3, 8 x1...

Doesnt make any sense, I should be dialing 76484.

 
76484 should work. Are you testing by calling the CRA internally? You should get the results you want by testing from an external inbound call, try pointing a DID to your CRA and retest.
 
Huh? You say you have to spell Smith by dialing 7648 but thing you have to dial 76484? Are you saying you think you should have to dial the full 5 digits and not the first 4? Would think that the system routes the call as soon as it has enough digits to get a unique match. IF you dial that last 4 does it cause an issue?

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
 
@LoopyLou - yankblan is pressing "7" four times to reach the "s" (7,p,r,s). The dial by name works differently when accessed from the outside. When called internally you hear "spell the name" and have to scroll through the different characters under each digit. If the CRA is set for directory by last name, when called from externally, you hear "enter the person's last name" and 76484 should work. I usually just enter the first three letters and get a match. I also use # to speed things up (764#).
 
@619Tech exactly what I was saying. Tried it from outside, and no matter what I dial, I inevitably get back the admin MB, which I'm gonna guess is because it has the lowest number (300) of all the MBs (3XX).

Forgot to mention I'm at 5.1 SP4

 
Maybe the global setting is messing with it. Check Voice Processor/Application-Related Information/Auto Attendant Information/Directory Sort Order/Last Name.
 
That seems to be in order; weird.

Just to be more precise, here is exactly what is happening:

MB: Administrator - 300
Luc Charest - 311
Klaudiane Rabouin - 315

If I dial C-H-A-R-#, I get offered 300
If I dial R-A-B-O-#, Iget offered 311

The Admin MB, doesn't even have a user, username or description. Don't know why I get this one .

 
My next guess would be the user names have been changed since the MB's were first created and initialized. When a MB is created, a file associating the name (description) with letters on the keypad is created. When a user name (description) is changed, that file does not get updated, so the directory dial by name becomes corrupted as time goes by and user names change. I always train my admins to delete the MB, change endpoint username, then re-create associated MB. You can try that or just create a new non-associate MB with a name, intialize it, and test.
 
Doesn't the directory uses the Users>First Name/Last Name column, depending on the one you wish to choose?

Meaning, you create your extension, associate the user, and then create the MB?

Pretty sure that's what I did.

 
Can't figure this out, and it should be simple, yet it is sooo long, complicated, devoided of sense, and convoluted (like forwarding path that you have to edit for each freakin user).

If I delete a mailbox, create an extension id and put in a description, it works every time
If I leave the mailbox as is, put a description that fits the last name under system>devices>phones, it works every time.

So.... wether you put first or last name for search, it uses description and doesn't give a $h1t about what you put under user???

 
The directory by name associates to the description field (last name, first name) of the endpoint and associated mailbox. Users are a whole new field to allow permissions, DEE, etc... and is not linked to the directory.

I use the same single forwarding path to VM for all users and just copy the same settings onto endpoints that have MB's.

You sound as frustrated as I feel working on 3300's...

Hang in there.
 
Thx, figured the description stuff in the meantime. F1 help is not that helpful, and sorting through different guides on edoc , it's not always clear.

As the forwarding path, I mean you have to go through every phone and set no answer -IC to yes individually if you want internal calls.to go to vm

 
To copy the system forwarding of an endpoint: Program one endpoint with the system forwarding settings you want (example: x1234) to use; click on endpoints in the left window; in the right window, right click on the endpoint (x1234) and select "copy 1234"; highlight target endpoints; right click in highlighted area & select "paste 1234"; click clear all, then select system forwarding & click "OK"; this will copy the system fowarding flags of x1234 to highlighted endpoints.

I copy everything except "Transfer Recall Destination" & "Password" when doing batch programming of like endpoints.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top