CUBAC 3.1.1.8 BLF issue

[Ayodeji Okanlawon]

Guys,

I am recently working on a project with CUBAC been deployed.

The customer has full E.164 (eg +441228406699) numbers in AD because of CUCiMOC. However the extensions in CUCM are 4 digits.(6699)

When a search is made on the console, it returns users with their full E.164 which is correct, but the problem is that it does not show the BLF status for users.

Is the problem due to the fact that a user contact on the console is different from the extension number on the phones?

Is there a work around to this? Or should this not be a problem?

[Jaime Valencia · Accepted solution]

The problem is what you mention, the DNs do not match what you have in CUCM and what you have in AD.

Last time i checked with the ARC guys we had no workaround for this using the CUxAC, they are not affected by the directory lookup rules like the old AC.

They suggested to redo the dial plan, also mentioned that the console you could use is:

Arc Enterprise Premium (not the Solutions + product, but the one sold directly by Arc  - this one will chop off digits when importing to the attendant console directory

HTH

java

If this helps, please rate

www.cisco.com/go/pdihelpdesk

[Ayodeji Okanlawon]

Java,

Many thanks for this. This is going to be a big big issue! With new applications like CUCiMOC, arc has got to do better than this. To redo the dial plan will be impossible. This pproduct is way behind technology