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: [email protected] To: [email protected] CC: [email protected]
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 to 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 <[email protected]> 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 [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
