cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
275
Views
0
Helpful
2
Replies

MPX 1.2 with upgraded CCM directory authentication problem

jjia
Level 2
Level 2

Hi,

The customer had MPX 1.2 integrated with CallManager 4.2 directory for end-user authentication. It worked fine.

Now we did CallManager upgrade from 4.2 to version 6.1(2), we followed the procedure on CallManager 6.1(2) and MPX 1.2 for external directory authentication configuration (use AXL service). The problem is that I found the authentication looks like didn't work: the existing users can not join the meeting from the phone(password is not correct), or access the MPX webpage: password is not correct or the user does not exists.

Any idea?

Thanks,

JJ

2 Replies 2

smahbub
Level 6
Level 6

You can simplify user profile administration by enabling an external directory to authenticate Cisco Unified MeetingPlace Express users. Cisco Unified MeetingPlace Express automatically creates a user profile in the local database when a new user attempts to log in on the web and successfully authenticates through an external directory. User authentication by an external directory does not work if you try to log in to Cisco Unified MeetingPlace Express on the phone.

Refer the following url for more information about "Configuring User Authentication by an External Directory-Cisco Unified Communications Manager Release 5.x and 6.x":

http://www.cisco.com/en/US/docs/voice_ip_comm/meetingplace_express/2_0/english/administration/guide/cm20call.html#wp1142735

jvweigand
Level 1
Level 1

We ran into this same issue upgrading from MPX 1.2 to 2.0. How do you have the AXL URL configured in MPX? We had to set it to "https://ipaddressofccm:8443/axl" and then it started working properly.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: