Hello Torrance and Cesar The issue is actually not the recorder but the IP Phone/Jabber. Whats happening is that the solution is unable to bring in a transcoder to handle the multi codec calls. Example Incoming call to Jabber - G729 Jabber answers the call  Jabber then kicks of a call recording session to any recording solution that is set to use G711. In this situation the CUCM will try to bring in a transcoding resource due to the codec differences and fails. Its an old defect from well over 4 years ago. Two solutions is too. 1. Disable the call recording option on the line. 2. Ensure that the codec being used is the same as the call recording solution. Regards Hoai Huynh ... View more

To add to the information already provided by Deepak.   Not all websites can be displayed due to click jack protection .The screen pop/web gadget is really an Iframe and not a full blown browser.   Taking google as an example, the page itself is design to not support iframes. https://developer.mozilla.org/en-US/docs/Web/HTTP/X-Frame-Options   Regards Hoai Huynh   ... View more

Hello Mohamed Can you go ahead and make sure the trigger information is set correct from the UCCX side. There looks to be a mismatch between the CUCM and UCCX, should a sync ever be ran it could break the system due to updated configuration changes on CUCM isnt being reflected on the UCCX. To correct this I would advise deleting trigger information from CUCM and then run the data resync again. As for the calls failing can you look into the following: Working Call: Call arrives on the trigger and is redirected successfully to CTI Port: 11215 1194831: Dec 03 15:34:38.992 AST %MIVR-SS_TEL-7-UNK:Route Connection=[6624:BAH-PT-Phones:1/(P1-jtapi_1) GCID=(2,270036)->ACTIVE]->OFFERED, reason=1, Event= CallCtlConnOfferedEv 6624:BAH-PT-Phones:1, cause=100, metacode=129, isMaster=true 1194837: Dec 03 15:34:38.994 AST %MIVR-SS_TEL-7-UNK:Call.received() JTAPICallContact[id=331,implId=270036/2,state=STATE_RECEIVED_IDX,inbound=true,App name=BNPP_CSD,task=null,session=null,seq num=-1,cn=6624,dn=6624,cgn=6397,ani=null,dnis=null,clid=null,atype=DIRECT,lrd=null,ocn=6624,route=RP[num=6624],OrigProtocolCallRef=0000000000041ED4027F192400000000,DestProtocolCallRef=null,TP=null 1194840: Dec 03 15:34:38.995 AST %MIVR-SS_TEL-7-UNK:Route Connection: [6624:BAH-PT-Phones:1/(P1-jtapi_1) GCID=(2,270036)->ACTIVE]->OFFERED, CTI Port selected: TP[id=7,implId=11215,state=IN_USE] Failed Call: Here we can see the call arrives on trigger and redirects to CTI Port: 11221 and fails 1195131: Dec 03 15:34:42.266 AST %MIVR-SS_TEL-7-UNK:Route Connection=[6624:BAH-PT-Phones:1/(P1-jtapi_1) GCID=(2,270037)->ACTIVE]->OFFERED, reason=1, Event= CallCtlConnOfferedEv 6624:BAH-PT-Phones:1, cause=100, metacode=129, isMaster=true 1195135: Dec 03 15:34:42.267 AST %MIVR-SS_TEL-7-UNK:Call.received() JTAPICallContact[id=332,implId=270037/2,state=STATE_RECEIVED_IDX,inbound=true,App name=BNPP_CSD,task=null,session=null,seq num=-1,cn=6624,dn=6624,cgn=6397,ani=null,dnis=null,clid=null,atype=DIRECT,lrd=null,ocn=6624,route=RP[num=6624],OrigProtocolCallRef=0000000000041ED5027F192700000000,DestProtocolCallRef=null,TP=null 1195138: Dec 03 15:34:42.268 AST %MIVR-SS_TEL-7-UNK:Route Connection: [6624:BAH-PT-Phones:1/(P1-jtapi_1) GCID=(2,270037)->ACTIVE]->OFFERED, CTI Port selected: TP[id=8,implId=11221,state=IN_USE] 1195141: Dec 03 15:34:42.277 AST %MIVR-SS_TEL-3-ROUTE_FAILED:Route failed : All Call ids=JTAPICallContact[id=332,implId=270037/2,state=STATE_RECEIVED_IDX,inbound=true,App name=BNPP_CSD,task=null,session=41000000180,seq num=0,cn=6624,dn=6624,cgn=6397,ani=null,dnis=null,clid=null,atype=DIRECT,lrd=null,ocn=6624,route=RP[num=6624],OrigProtocolCallRef=0000000000041ED5027F192700000000,DestProtocolCallRef=null,TP=null,List of Active Connections=[6624:BAH-PT-Phones:1/(P1-jtapi_1) GCID=(2,270037)->ACTIVE]->OFFERED,Extension=11221,Exception=com.cisco.jtapi.InvalidPartyExceptionImpl: Attempt to redirect to an unknown destination,Failure reason= call will be rejected, CTIERR_REDIRECT_CALL_UNKNOWN_DESTINATION=0x8ccc0034::Attempt to redirect to an unknown destination,Contact.Reject.reason=TRIGGER_FAIL,(SelectRouteTime,ObtainingIdleChannelTime,RedirectTime=2,1,9) Recommendation is ensure the Route Point/CTI Ports are configured with the correct CSS/Partition on the UCCX. Run the Datasync to make sure that configuration is pushed out to CUCM. Regards Hoai Huynh ... View more

Hello JP Try dropping your user seat below 450. We got it working in the labs by scaling back the deployment size. Hoai ... View more

Hello Jeep Thats interesting that the issue is back. I have performed a base install of 9.0.1.10000-102 and don't have this issue. If you rolled back with the COP and the teams are still there I would suggest you engage tac as SU3 had this cop rolled in already. There has been instance where the teams were required to be removed manually. or the alternative is to move to 9.X and have tac fix the issue on that version. Hoai ... View more

Hello The axl,jtapi,rmcm can be application users even if the cucm is configured with an ldap. It's a choice wither you use application or end user. Regards Hoai ... View more

Hello There is no uccx recovery disc. You have to use the call manager recovery disc. Sent from Cisco Technical Support iPad App ... View more

"In my opinion Cisco should have modified the appadmin initial install  wizard to allow multiple servers to be configured for this (as with the  RM/JT services) as no one ever goes back and properly reconfigures this  setting - the wizard just asks for a the publisher details." I am fairly certain this can be done on version 8.x and 5.x/7.x once you get to the Jtapi/RMCM user setup page. Anyhow I don't believe the rule of homing it to the PUB is applicable any more assuming that was in the guides at all, don't recall too well. As Aaron stated without getting a backup AXL, assuming your PUB goes down the system is usless and dead in the water as there is no user authentication and RP/CTI ports would all be unregistered. If you refer to the HAoWAN guide it acutally states to point each respective node to their local CUCM box. So that rule alone would break the assumption it has to be pointed at the PUB. Long story short, yes home it to its respective call manager depending on your setup, PUB or SUB are fine. Hoai ... View more

Hi Nathan Can you see from the SMTP connection on the exhange that the UCCX has a connection established? The SMTP account your using is enabled for sending mail on behalf of the alias? Do you have the EEMjava logs from the server on debug for a quick look. When the agents respond, the mail should be placed in a randomly generate folder on the exchange. You can map this with the agent debugging. Hoai ... View more