Hello Aaron,
We would love to help you troubleshoot this issue; to do that we're at the point of needing to see 'what is going on under the hood'. Please set up a test case for us by selecting a jabber desktop client impacted by this issue and clearing the local cache content of the client. * Cache location for PC Clients: http://www.cisco.com/c/en/us/support/docs/unified-communications/jabber-windows/116433-probsol-jabber-00.html * Cache location for Mac Clients: http://www.cisco.com/c/en/us/support/docs/unified-communications/jabber-mac/116682-technote-jabber-00.html After you've clear the cache files; use the Jabber client to attempt an external call (replicate the same method the business unit is attempting to use for external calls that are failing). Immediately after the call fails (assuming it still does fail) and you get that annunciation message, I need you to end the call with the Jabber client and collect the "Calls" PRT (Problem Reporting Tool) logs from that Jabber client. You can access the PRT menu from the Help->Report A Problem menu of the Jabber Client. Follow the on-screen instructions and it will eventually allow you to download an archive file. [cid:976983cc-3df8-4817-81c1-d341cd020363] The next thing I'd like for you to do is to open the Real-Time Reporting Tool (RTMT) application and point it to the publisher node of your CCM cluster (if you do not have the RTMT application, you can download it from the Applications->Plugins section of CUCM). If needed, you can research RTMT at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/8_6_1/rtmt/rtmt/rtinst.html. Once you are logged into the tool, please replicate the following workflow and follow the on-screen prompts to download the traces (make sure you get the traces from ALL CUCM nodes for a time period covering the time of the example call). You can research more about getting trace files at http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/8_6_1/rtmt/rtmt/rttlc.html. [cid:4b623c9c-04cc-49ce-be22-d938309539ff] Once you have all the files gathered, upload them to dropbox/box .. etc and send a linkcinto this list along with the called and calling party number of the example call and the device name of the CSF profile used by the Jabber Desktop client for the example call. Hope this help, -Ryan ________________________________ From: cisco-voip <cisco-voip-boun...@puck.nether.net> on behalf of Aaron Banks <amichaelba...@hotmail.com> Sent: Thursday, November 5, 2015 1:51 PM To: Anthony Holloway Cc: cisco-voip@puck.nether.net Subject: Re: [cisco-voip] External calls from Jabber Per Charles' suggestion, I used the DNA tool to analyze the dialed call from jabber. Nothing is being blocked. Digits are not being dialed by clicking on the contact, the dial pad is being used in jabber or entered in the calling window. ________________________________ Date: Thu, 5 Nov 2015 12:01:13 -0600 Subject: Re: [cisco-voip] External calls from Jabber From: avholloway+cisco-v...@gmail.com To: amichaelba...@hotmail.com CC: cisco-voip@puck.nether.net It's pretty straight forward, if you already have a grasp on CUCM core functionality. Your reported error message sounds like the Annunciator telling you there were no matches in the dial plan for what you dialed. You didn't mention what was dialed, so we cannot help you there. If however, the error message was more like fast busy or ringback then call drop, I would say it was a failure tCacheo establish bi-directional media. That's not that case though, so I would focus on your dialing habits and your matched patterns. Also, Cisco Jabber does not use en bloc dialing, dispite the fact there is no dial tone. Seems a bit backwards, but that's how it is. On Thu, Nov 5, 2015 at 11:10 AM, Aaron Banks <amichaelba...@hotmail.com<mailto:amichaelba...@hotmail.com>> wrote: inShare The jabber questions never end. I am struggling with Jabber. Users can call each other internally, check voicemail and IM each other, no problem. When they go to make an external call to any number, they hear "your call cannot be completed as dialed" which would tell me maybe a calling search space issue. Not that. I've changed the jabber client to start calls with audio instead of video. I've checked regions and there are only defaults. Would the jabber-config.xml file create issues? I would think it might bugger up directory services but not actually calling. _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
