The translation would have to be the number you can calling to, sounds like you
have it setup as the number you are calling from.
You may be able to do that with the "route next hop by calling party number"
functionality, but I've never tried that to know if that would work.
I set this up here
Speaking of custom MSIs, I never have been able to get Orca to get that right.
Anyone got a cheat sheet on that?
I’ve always just messed with the install switches personally, much cleaner,
especially if deploying to an image.
Ben Amick
Unified Communications Analyst
From: bmead...@gmail.com [m
Thanks, Ben :)
De: Ben Amick [mailto:bam...@humanarc.com]
Enviado el: viernes, 03 de noviembre de 2017 02:39 p.m.
Para: ROZA, Ariel ; cisco-voip@puck.nether.net
Asunto: RE: jabber-config.xml not being downloaded or being ignored
I haven't tested it in a while and don't have the capability do on t
I haven't tested it in a while and don't have the capability do on the domain I
have access to, but if you reset the jabber client it might remove the
exclusion provisioning, which you would need to do to switch users. As I said,
don't quote me on that but it's a possibility.
Ben Amick
Unified
Yea, the problem here is the clients don't download the jabber-config.xml
until they connect to CUCM which is later.
For first login, you'll need to use provisioning URLs, install switches, or
make a custom MSI.
On Fri, Nov 3, 2017 at 1:33 PM, Ben Amick wrote:
> Until the first registration the
I know that, but after I´ll I read, I understand that if the jabber client is
able to log in a first time, using manual settings, it should download and
cache the jabber-config info, hence excluding Webex from them on. Right?
My customer can manually log in.
De: Ben Amick [mailto:bam...@humanar
Until the first registration they don't get the service exclusion. If the
client has any webex accounts it will attempt to connect to those first (or has
had in the past - you have to put in a formal support ticket to get it
removed). There's a command line switch you can use on the installation
I have a preexisting installation CUCM 10.5.2 that I am troubleshooting.
Jabber for Windows clients ask for Webex credentials for login, although the
jabber-config.xml file exists and is configured to exclude Webex services.
I have checked every possibility and can´t see what I´m missing here.
T
Thank you for your reply and sorry for not responding earlier, but I just
didn't get to this until now.
I tried to implement your suggestion in a test scenario, but I guess I made
a mistake because it does not work. Here's what I did:
- created a new partition
- created a new CSS that only co
