jgw1 state is configuring instead of active

Unanswered Question
Dec 6th, 2008
User Badges:
  • Bronze, 100 points or more

We are using Duplex system. When I update ICM PG from 7.0 to 7.2.2 jgw1 state change configuring on both the PGs. also on opc service we are getting the below message


14:24:35 Trying to set DefaultPeripheralRoute to unknown RouteID -1 on Peripheral 5000.

14:24:35 ADDED 1 PeripheralDefaultRoutes.

14:24:35 ADDED 2 ApplicationInstance.

14:24:36 ADDED 1 ServiceLevelThreshold.

14:24:36 Initial configuration received.

14:24:36 Trace: Controller Data Service ACTIVATED

14:24:36 Activating Half-Hour 28 for PG (12/06/2008 13:00:00).

14:24:36 Trace: PG_DATA_READY_IND issued to router

14:24:36 Initial configuration for Peripheral 5000 received.

14:24:36 Update ConfigurationUpdateComplete:: CurrentConfigSequenceNumber (New=508842309028.000000, Old=-1.000000)

14:24:36 Update ConfigurationUpdateComplete:: LastGoodConfigSequenceNucmber (New=508842309028.000000, Old=-1.000000)

14:24:36 Update ConfigurationUpdateComplete:: ControllerConfigSequenceNumber (New=508842309028.000000, Old=-1.000000)

14:24:38 Trace: Peripheral::SetCSTAEventConfig - Peripheral 5000 request RulesForConferencedCallIDs=2

14:24:38 Trace: Peripheral::SetCSTAThirdPartyServicesSupported - Peripheral 5000 supports CSTA_ANSWER_CALL TPService

14:24:38 Trace: Peripheral::SetCSTAThirdPartyServicesSupported - Peripheral 5000 supports CSTA_CLEAR_CALL TPService

14:24:38 Trace: Peripheral::SetCSTAThirdPartyServicesSupported - Peripheral 5000 supports CSTA_CLEAR_CONNECTION TPService

14:24:38 Trace: Peripheral::SetCSTAThirdPartyServicesSupported - Peripheral 5000 supports CSTA_CONFERENCE_CALL TPService

14:24:38 Trace: Peripheral::SetCSTAThirdPartyServicesSupported - Peripheral 5000 supports CSTA_HOLD_CALL TPService

14:24:38 Trace: Peripheral::SetCSTAThirdPartyServicesSupported - Peripheral 5000 supports CSTA_MAKE_CALL TPService

14:24:38 Trace: Peripheral::SetCSTAThirdPartyServicesSupported - Peripheral 5000 supports CSTA_RETRIEVE_CALL TPService

14:24:38 Trace: Peripheral::SetCSTAThirdPartyServicesSupported - Peripheral 5000 supports CSTA_TRANSFER_CALL TPService

14:24:38 Trace: Peripheral::SetCSTAThirdPartyServicesSupported - Peripheral 5000 supports CSTA_SET_AGENT_STATE TPService

14:24:38 Trace: Peripheral::SetCSTAThirdPartyServicesSupported - Peripheral 5000 supports CSTA_QUERY_AGENT_STATE TPService

14:24:38 Trace: Peripheral::SetCSTAThirdPartyServicesSupported - Peripheral 5000 supports CSTA_CONSULTATION_CALL TPService

14:24:38 Trace: Peripheral::SetCSTAThirdPartyServicesSupported - Peripheral 5000 supports CSTA_RECONNECT_CALL TPService

14:24:38 Trace: Peripheral::SetCSTAThirdPartyServicesSupported - Peripheral 5000 supports CSTA_MAKE_PREDICTIVE_CALL TPService

14:24:38 Trace: Peripheral::SetCSTAThirdPartyServicesSupported - Peripheral 5000 supports CSTA_QUERY_DEVICE_INFO TPService

14:24:38 Trace: Peripheral::SetCSTAThirdPartyServicesSupported - Peripheral 5000 supports CSTA_SEND_DTMF TPService

14:24:38 Trace: Peripheral::SetCSTAThirdPartyServicesSupported - Peripheral 5000 supports CSTA_ASSOCIATE_DATA TPService

14:24:38 Trace: Peripheral::SetCSTAThirdPartyServicesSupported - Peripheral 5000 supports CSTA_SUPERVISOR_ASSIST TPService

14:24:38 Trace: Peripheral::SetCSTAThirdPartyServicesSupported - Peripheral 5000 supports CSTA_EMERGENCY_CALL TPService

14:24:38 Trace: Peripheral::SetCSTAThirdPartyServicesSupported - Peripheral 5000 supports CSTA_SUPERVISE_CALL TPService

14:24:38 Trace: Peripheral::SetCSTAThirdPartyServicesSupported - Peripheral 5000 supports Unknown CSTA Event Type TPService

14:24:38 Device Target Pre-Route Notification Service ACTIVATED on Peripheral 5000.

14:24:39 Error acknowledgment received from Peripheral 5000 Message Type = 9 Peripheral State = 2.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

The JTAPI on side A connects to the CTI Manager on subscriber 1, and the JTAPI on side B connects to the CTI Manager on subscriber 2. Only one will be active at any one time, controlled by ICM.


Check that the PIM is configured correctly on each side to point to the correct subscriber, and ensure that the user and password are correct for the "ICMJTAPI" user configured in CUCM as an "application user".


Is the CTI Manager service running on both subscriber 1 and subscriber 2? Did you upgrade CUCM too? If so, did you pull down the new JTAPI plug in and install it?


Does JTAPI show correct connection to the provider?


Regards,

Geoff


Anonymous (not verified) Tue, 04/21/2009 - 20:50
User Badges:


Actions

This Discussion