Dialing from CUCiMOC and JTAPI issues

Unanswered Question
Dec 9th, 2009
User Badges:

The CUCiMOC now logs in and gives all green status. When a call is made from a desk phone the corresponding desk phone and CUCiMOC ring and both can answer with two way voice.


2 outstanding issues


  1. When selecting desk phone or trying to dial from CUCiMOC in deskphone mode I get the error:

"Failed to start a conversation

A Problem occurred with the JTAPI software library that controls your desk phone"


When trying to dial, the desk phone picks up  and give the fast busy error sound.


However the desk phone does appear to be "paired" since CUCiMOC alerts when off hock or if a call is in progress.



  1. Both CUCiMOC's can receive calls (when dialled from a desk phone) and get two way audio, but neither can dial 4 digit extensions, they just give the busy signal.


I have the following setup

User1 Bill Gates, AD\OCS number +441582422001



Their physical phone DN is 2001



User2: John Chambers with the setup with +441582422001 and 2001 on CUCM



This translation pattern, 44158242.200X, allows CUCiMOC to dial with "441582422000" and successfully make a call to the 200 desk phone or CUCiMOC, but not the +44 number you get if you drop the contact on the phone icon. I am not convinced this is the correct way to set it up?



But I still can't get CUCiMOC to successfully call a 4 digit extension


Any suggestions on either issue?


thanks

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Kristof De Brouwer Thu, 12/10/2009 - 03:01
User Badges:

I would like to confirm that I'm experiencing the same issue here,


Drag and drop works fine but my deskphone is not receiving any dial string causting the JTAPI error in CUCIMOC


Untitled.jpg

Kristof De Brouwer Thu, 12/10/2009 - 04:16
User Badges:

Well I'm experiencing the same issue,when looking into the CFS log I can see that the calledParty field is empty altough CUCIMOC is able to display the number details of my contact persons as per screenshot below


Untitled.jpg

Cisco JTAPI Log


eventSequence                     = 125
  lineCallManagerID                 = 1
  lineID                            = 1390
  callCallManagerID                 = 11
  callLegID                         = 200789841
  state                             = 1
  cause                             = 16
  farEndpointSpecified              = false
  farEndpointCallManagerID          = 0
  farEndpointType                   = 0
  fwdDestinationAddress             = null
  reason                            = 1
  callingParty                      = 3222299710
  callingPartyName                  =
  calledParty                       =
  calledPartyName                   =
  originalParty                     =
  originalPartyName                 =
  lastRedirectingParty              =
  lastRedirectingPartyName          =
  callingPartyDeviceName            = SEP0021A0D82671
  mediaDeviceName                   =
  mediaResourceId                   = 0
  bRemoteInUse                      = false
  bPrivacy                          = false
  callSelectStatus                  = 0
  unModifiedCallingParty            = 3222299710
  unModifiedCalledParty             =
  unModifiedOriginalCalledParty     =
  unModifiedLastRedirectingParty    =
  callingPartyPi                    = true
  callingPartyNamePi                = true
  calledPartyPi                     = true
  calledPartyNamePi                 = true
  originalCalledPartyPi             = true
  originalCalledPartyNamePi         = true
  lastRedirectingPartyPi            = true
  lastRedirectingPartyNamePi        = true

Kristof De Brouwer Thu, 12/10/2009 - 04:17
User Badges:

I would like to confirm that I'm experiencing the same issue here,


Drag and drop works fine but my deskphone is not receiving any calledParty  number as per Cisco JTAPI Log below


Example:


eventSequence                     = 125
  lineCallManagerID                 = 1
  lineID                            = 1390
  callCallManagerID                 = 11
  callLegID                         = 200789841
  state                             = 1
  cause                             = 16
  farEndpointSpecified              = false
  farEndpointCallManagerID          = 0
  farEndpointType                   = 0
  fwdDestinationAddress             = null
  reason                            = 1
  callingParty                      = 3222299710
  callingPartyName                  =
  calledParty                       =
  calledPartyName                   =
  originalParty                     =
  originalPartyName                 =
  lastRedirectingParty              =
  lastRedirectingPartyName          =
  callingPartyDeviceName            = SEP0021A0D82671
  mediaDeviceName                   =
  mediaResourceId                   = 0
  bRemoteInUse                      = false
  bPrivacy                          = false
  callSelectStatus                  = 0
  unModifiedCallingParty            = 3222299710
  unModifiedCalledParty             =
  unModifiedOriginalCalledParty     =
  unModifiedLastRedirectingParty    =
  callingPartyPi                    = true
  callingPartyNamePi                = true
  calledPartyPi                     = true
  calledPartyNamePi                 = true
  originalCalledPartyPi             = true
  originalCalledPartyNamePi         = true
  lastRedirectingPartyPi            = true
  lastRedirectingPartyNamePi        = true


Screenshot

Untitled.jpg

tarbuthnot Thu, 12/10/2009 - 08:17
User Badges:

My issues were solved by re running the COP to recreate the xml files related to the dial rules.


I had changed the dial rules but not re run the COP, The JTAPI errors are really just the phone not being able to dial, as soon as the app dial rules were sorted the JTAPI errors disappeared.


Full credit to Cisco TAC for their great work


cheers

Actions

This Discussion

Related Content