Guest

Preview Tool

Cisco Bug: CSCtf11400 - CTI Port remains unregistered after application restart

Last Modified

Feb 22, 2014

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

5.1(3) 6.1(3)

Description (partial)

Special Note:

 The fix for this issue also requires the fix for CSCtg40742.

 Symptom:
  
  Some UCCE Mobile Agents may be unable to login to CTIOS Desktop client.
  
  The following pop-up warning will be presented to the agent:
  =====
  CTI Warning:
  IPCC Error [12005]Login coult not be performed -
  Possible causes are Invalid Instrument; Media
  Termination Problem or other CM issue
  =====
  
  Conditions:
  
  Topology:
  PGA-----CTI1/CCM1-----WAN-----CCM2/CTI2-----PGB
  
  Mobile Agent login failures may occur after a forced PG failover/failback due
 to planned PG service restarts or server reboots during engineering special
 patching or other planned maintenance.
  
  The following sequence of events may trigger this type of failure.
  1. Side A PG is the "active" PG
  2. Side A PG services are stopped or server is shutdown which forces Side B PG
 to become active.
  3. Side A PG services are started or server is booted (Side B PG remains active).
  4. Side B PG services are stopped or server is shutdown which forces Side A PG
 to become active again.
  5. Side B PG services are started or server is booted (Side A PG remains active).
  
  The following types of errors may be a signature for this problem.
  
  From CCM SDL traces:
  =====
  100188139| 2010/02/02 03:34:46.197| 008| SdlError 
 |CtiDeviceLineAssignmentsReq| NA| StationD(8,100,62,1657)|
 CTIDeviceLineMgr(14,200,18,1)| (14,200,15,1).9700858-(*:X.X.X.X) | Destination
 process does not exist
  =====
  
  From CTI SDL traces:
  =====
  257091825| 2010/02/02 02:34:51.192| 014| SdlSig    |CtiRequestTimer| ready|
 CTIDeviceLineMgr(14,200,18,1)|
 SdlTimerService(14,200,3,1)|(14,200,15,1).9700859-(*:X.X.X.X) | [R:HP - HP: 0,
 NP: 1, LP: 0, VLP: 0, LZP: 0 DBP: 0]
  257091826| 2010/02/02 02:34:51.192| 014| AppError  |||
 CTIDeviceLineMgr(14,200,18,1)   ||| Timer Expired - ctiCommandCode:135718446,
 AsyncRspns:12532
  257091827| 2010/02/02 02:34:51.192| 014|
 AppInfo|||CTIDeviceLineMgr(14,200,18,1)||| [CTI-APP][Device(601)::requestTimer]
     (Signal=CtiRequestTimer DeviceName=LCPABCDEF123456
 State=deviceState_opening OpenMode=ThirdParty, mLocalDeviceHandle=14|601,
 mOutStandingDRRTimer=0, DeviceRequestTimeout=5)
  257091828| 2010/02/02 02:34:51.193| 014| SdlSig|CtiDeviceLineAssignmentsRes |
 ready | CTIDeviceLineMgr(14,200,18,1)   | CTIDeviceLineMgr(14,200,18,1)   |
 (14,200,15,1).9700858-(*:X.X.X.X) | [R:NP - HP: 0, NP: 1, LP: 0, VLP: 0, LZP: 0
 DBP: 0]AsyncResponse=12531 Result=0x8ccc0001
  257091829| 2010/02/02 02:34:51.193| 014|
 AppInfo|||CTIDeviceLineMgr(14,200,18,1)||| [CTI-APP]
 [Device(1789)::star_deviceLineAssignmentsRes](Signal=CtiDeviceLineAssignmentsRes DeviceName=LCPABCDEF123456
 State=deviceState_opening OpenMode=ThirdParty, mLocalDeviceHandle=14|1789,
 mOutStandingDRRTimer=0, DeviceRequestTimeout=5)
  
  257091833| 2010/02/02 02:34:51.193| 014| AppInfo|||
 CTIHandler(14,200,16,2712)|||[CTI-APP] [CTIHandler::OutputCtiMessage]     CTI 
  FailureResponse    ( seq#=4240 result=2362179585
 description=DeviceGetLineInfoFetch failed)
  =====
  
  From the PG jgw log:
  =====
  03:40:28 pg8a-jgw1 Trace: performAddCallObserver: Provider hit exception in
 getAddress for address: 1234567com.cisco.jtapi.InvalidArgumentExceptionImpl:
 Address 1234567 is not in provider's domain. 
  =====
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.