Mobility Manager configuration help

Unanswered Question
Feb 21st, 2007

CCM 4.2(3) with Mobility Manager version 1.2

I have followed the install guide and admin guide for the Call Manager configuration as well as the Mobility Manager configuration, but can't get it to ring a phone.

I have 2 users in CCM that are the users in CMM. I was able to add a user in CMM along with a group, line appearance and remote destination (which is a cell phone)

My CTI ports are all registered...I'm not sure if I missed a step or am reading into the directions wrong.

Thanks,

Erin

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
tjmaurin Thu, 02/22/2007 - 17:24

I am also running the same versions and following the same guides and I have the same symptoms. Can you tell me if your cmmApp.log shows the following:

2007-02-22 20:12:50,297 ERROR - [EXT_HNDLR][ ADDRESS ][2035] Could not get/set Auto Accept after failure: Exception: com.cisco.jtapi.InvalidStateExceptionImpl: Adress not in service

2007-02-22 20:12:50,354 WARN - [CTI_PORT ][ ADDRESS ][7601] Unhandled event: (P2-CMMOUTGOINGUSER) [7601] CiscoAddrOutOfServiceEv [#38]

2007-02-22 20:12:50,395 INFO - [CTI_PORT ][ ADDRESS ][7601] Registered Successfully

2007-02-22 20:12:50,502 WARN - [CTI_PORT ][ ADDRESS ][7602] Unhandled event: (P2-CMMOUTGOINGUSER) [7602] CiscoAddrOutOfServiceEv [#43]

2007-02-22 20:12:50,517 ERROR - [CTI_PORT ][ ADDRESS ][7602] Could not get/set Auto Accept after failure: Exception: com.cisco.jtapi.InvalidStateExceptionImpl: Adress not in service

2007-02-22 20:13:20,345 INFO - [EXT_HNDLR][ ADDRESS ][2035] Registered Successfully

emikelso Thu, 02/22/2007 - 18:14

I actually got it to work, and I havent looked at the logs. My problem was that the Telco needed to see a certain DNIS outbound, or else it blocks the call. So I had to override the feature of carrying original caller ID and replace it with the main number of the trunk.

In your case, make sure that under system parameters, you enter the proper JTAPI information. It looks like your CTI Ports are becoming unregistered, which would lead to the CTI connection. Double check the userID, device association, jtpai version.

Actions

This Discussion