Re: [cisco-voip] Hide individual numbers behind hunt pilot number

2017-11-03 Thread Sebastian Hagedorn
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 contains the newly created partition
- created a new translation pattern in that partition. The pattern is the 
5-digit extension I am using for this test. The CSS is the normal one. 
Under Calling Party Transformations I have entered the hunt pilot number as 
Calling Party Transform Mask


When I assign the new CSS to the Directory Number I am using for this test 
I get the standard "your call couldn't be completed" message for any number 
I try to dial.


Any ideas where I went wrong?


Thanks
Sebastian

--On 13. Oktober 2017 um 10:43:11 -0400 Brian Meade  wrote:


Sending the calls through a translation pattern is probably easiest.  Give
everyone in the hunt group a new CSS with new partition that sends all
calls through a translation pattern that masks the number then has your
normal CSS on the translation pattern.

On Fri, Oct 13, 2017 at 9:04 AM, Sebastian Hagedorn
 wrote:


Hi,

using CUCM 10.0 we have achieved the goal stated in the subject using
Calling Party Transformation Patterns. The pattern is the number(s) we
want to hide, the field "Calling Party Transformation Mask" contains the
number of the hunt pilot, and the Partition references a CSS that is
applied to the MGCP gateway as "Calling Party Transformation CSS".

So far, so good. But this only works for calls that go through the
gateway. Ideally we would like to achieve the same effect for internal
calls as well. I haven't been able to figure out where I need to apply a
Calling Party Transformation CSS for it to work for all calls.

Ideas? Or is there a different way to achieve that?


--
   .:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:.
.:.Regionales Rechenzentrum (RRZK).:.
  .:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:.
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


[cisco-voip] jabber-config.xml not being downloaded or being ignored

2017-11-03 Thread ROZA, Ariel
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.

The jabber-config contents are this:




WEBEX


UDS



I have tried Jabber clients 11.6.4 and 11.8.2

The file is loaded to both TFTP serves in the cluster
It´s accessible via URL
The name is lowercase and the format is UTF-8
I restarted the TFTP servers when needed
The Cisco Support Field in the CSF device is empty.
In the Jabber Client I used the Diagnostics Tool (CTRL-SHIFT-D) and checked 
that all setings are ok.
I reset the client, cleared all the files under %APPDATA%\Local\Cisco\ and 
%APPDATA%\Roaming\Cisco and restarted the client.
The Jabber Client can log on, if done manually, specifiing the "Callmanager 9 
"mode and the server name/IP. If I switch to Automatic, it asks for Webex 
credentials (My customer has a couple of Webex accounts, but not enough for all 
the enterprise, hence he wants avoid Webex).
I checked the jabber.log, but I didn't get any clues.

Is there anything I am missing from the process?

P.S I also posted this question here: 
https://supportforums.cisco.com/t5/jabber-clients/jabber-config-xml-not-being-downloaded-or-being-ignored/m-p/3209901#M20756


Regards,

Ariel.


[cid:image002.jpg@01D354AF.D6B1C1A0]Ariel Roza
Support Engineer / Southern Cone
t: +54 11 5282-0458
c: +54 9 11 5017-4417
Av. Belgrano 955 - Piso 20 - CABA - Argentina - C1092AAJ
www.la.logicalis.com
_
Business and technology working as one
[cid:image006.png@01D298D0.103CDF50]

[cid:image005.jpg@01D354AF.D6B1C1A0][Descripción: Descripción: Descripción: 
Descripción: Descripción: Descripción: Descripción: Descripción: Descripción: 
Descripción: Descripción: Descripción: Descripción: Descripción: Descripción: 
Descripción: tw] [Descripción: Descripción: 
Descripción: Descripción: Descripción: Descripción: Descripción: Descripción: 
Descripción: Descripción: Descripción: Descripción: Descripción: Descripción: 
Descripción: Descripción: fb] 
  [Descripción: 
Descripción: Descripción: Descripción: Descripción: Descripción: Descripción: 
Descripción: Descripción: Descripción: Descripción: Descripción: Descripción: 
Descripción: Descripción: Descripción: yt] 


Logicalis Argentina S.A. solo puede ser obligado por sus representantes legales 
conforme los límites establecidos en el acto constitutivo y la legislación en 
vigor.
El contenido del presente correo electrónico e inclusive sus anexos contienen 
información confidencial.
El mismo no puede ser divulgado y/o utilizado por cualquiera otro distinto al 
destinatario, ni puede ser copiado de cualquier forma.

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


Re: [cisco-voip] jabber-config.xml not being downloaded or being ignored

2017-11-03 Thread Ben Amick
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 of 
Jabber that will disable the webex on the initial install, and that's the fix 
if they want to maintain having webex business accounts.

Alternatively, you might be able to get a support ticket in to remove your 
domain from the webex DNS, which the company gets added to because of the cloud 
messaging built into webex, but I don't know if they can neuter that without 
neutering the webex accounts proper.

Ben Amick
Unified Communications Analyst

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of ROZA, 
Ariel
Sent: Friday, November 3, 2017 1:27 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] jabber-config.xml not being downloaded or being ignored

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.

The jabber-config contents are this:




WEBEX


UDS



I have tried Jabber clients 11.6.4 and 11.8.2

The file is loaded to both TFTP serves in the cluster
It´s accessible via URL
The name is lowercase and the format is UTF-8
I restarted the TFTP servers when needed
The Cisco Support Field in the CSF device is empty.
In the Jabber Client I used the Diagnostics Tool (CTRL-SHIFT-D) and checked 
that all setings are ok.
I reset the client, cleared all the files under %APPDATA%\Local\Cisco\ and 
%APPDATA%\Roaming\Cisco and restarted the client.
The Jabber Client can log on, if done manually, specifiing the "Callmanager 9 
"mode and the server name/IP. If I switch to Automatic, it asks for Webex 
credentials (My customer has a couple of Webex accounts, but not enough for all 
the enterprise, hence he wants avoid Webex).
I checked the jabber.log, but I didn't get any clues.

Is there anything I am missing from the process?

P.S I also posted this question here: 
https://supportforums.cisco.com/t5/jabber-clients/jabber-config-xml-not-being-downloaded-or-being-ignored/m-p/3209901#M20756


Regards,

Ariel.


[cid:image009.jpg@01D354A8.43EBEB90]Ariel Roza
Support Engineer / Southern Cone
t: +54 11 5282-0458
c: +54 9 11 5017-4417
Av. Belgrano 955 - Piso 20 - CABA - Argentina - C1092AAJ
www.la.logicalis.com
_
Business and technology working as one
[cid:image006.png@01D298D0.103CDF50]

[cid:image012.jpg@01D354A8.43EBEB90][Descripción: Descripción: Descripción: 
Descripción: Descripción: Descripción: Descripción: Descripción: Descripción: 
Descripción: Descripción: Descripción: Descripción: Descripción: Descripción: 
Descripción: 
tw]
 [Descripción: Descripción: Descripción: Descripción: Descripción: Descripción: 
Descripción: Descripción: Descripción: Descripción: Descripción: Descripción: 
Descripción: Descripción: Descripción: Descripción: fb] 

  [Descripción: Descripción: Descripción: Descripción: Descripción: 
Descripción: Descripción: Descripción: Descripción: Descripción: Descripción: 
Descripción: Descripción: Descripción: Descripción: Descripción: yt] 


Logicalis Argentina S.A. solo puede ser obligado por sus representantes legales 
conforme los límites establecidos en el acto constitutiv

Re: [cisco-voip] jabber-config.xml not being downloaded or being ignored

2017-11-03 Thread ROZA, Ariel
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...@humanarc.com]
Enviado el: viernes, 03 de noviembre de 2017 02:33 p.m.
Para: ROZA, Ariel ; cisco-voip@puck.nether.net
Asunto: RE: jabber-config.xml not being downloaded or being ignored

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 of 
Jabber that will disable the webex on the initial install, and that's the fix 
if they want to maintain having webex business accounts.

Alternatively, you might be able to get a support ticket in to remove your 
domain from the webex DNS, which the company gets added to because of the cloud 
messaging built into webex, but I don't know if they can neuter that without 
neutering the webex accounts proper.

Ben Amick
Unified Communications Analyst

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of ROZA, 
Ariel
Sent: Friday, November 3, 2017 1:27 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] jabber-config.xml not being downloaded or being ignored

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.

The jabber-config contents are this:




WEBEX


UDS



I have tried Jabber clients 11.6.4 and 11.8.2

The file is loaded to both TFTP serves in the cluster
It´s accessible via URL
The name is lowercase and the format is UTF-8
I restarted the TFTP servers when needed
The Cisco Support Field in the CSF device is empty.
In the Jabber Client I used the Diagnostics Tool (CTRL-SHIFT-D) and checked 
that all setings are ok.
I reset the client, cleared all the files under %APPDATA%\Local\Cisco\ and 
%APPDATA%\Roaming\Cisco and restarted the client.
The Jabber Client can log on, if done manually, specifiing the "Callmanager 9 
"mode and the server name/IP. If I switch to Automatic, it asks for Webex 
credentials (My customer has a couple of Webex accounts, but not enough for all 
the enterprise, hence he wants avoid Webex).
I checked the jabber.log, but I didn't get any clues.

Is there anything I am missing from the process?

P.S I also posted this question here: 
https://supportforums.cisco.com/t5/jabber-clients/jabber-config-xml-not-being-downloaded-or-being-ignored/m-p/3209901#M20756


Regards,

Ariel.


[cid:image002.jpg@01D354B1.32D6D140]Ariel Roza
Support Engineer / Southern Cone
t: +54 11 5282-0458
c: +54 9 11 5017-4417
Av. Belgrano 955 - Piso 20 - CABA - Argentina - C1092AAJ
www.la.logicalis.com
_
Business and technology working as one
[cid:image006.png@01D298D0.103CDF50]

[cid:image005.jpg@01D354B1.32D6D140][Descripción: Descripción: Descripción: 
Descripción: Descripción: Descripción: Descripción: Descripción: Descripción: 
Descripción: Descripción: Descripción: Descripción: Descripción: Descripción: 
Descripción: 
tw]

Re: [cisco-voip] jabber-config.xml not being downloaded or being ignored

2017-11-03 Thread Brian Meade
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 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 of
> Jabber that will disable the webex on the initial install, and that’s the
> fix if they want to maintain having webex business accounts.
>
>
>
> Alternatively, you might be able to get a support ticket in to remove your
> domain from the webex DNS, which the company gets added to because of the
> cloud messaging built into webex, but I don’t know if they can neuter that
> without neutering the webex accounts proper.
>
>
>
> Ben Amick
>
> Unified Communications Analyst
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf
> Of *ROZA, Ariel
> *Sent:* Friday, November 3, 2017 1:27 PM
> *To:* cisco-voip@puck.nether.net
> *Subject:* [cisco-voip] jabber-config.xml not being downloaded or being
> ignored
>
>
>
> 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.
>
>
>
> The jabber-config contents are this:
>
>
> 
> 
> 
> WEBEX
> 
> 
> UDS
> 
> 
>
>
>
> I have tried Jabber clients 11.6.4 and 11.8.2
>
>
>
> The file is loaded to both TFTP serves in the cluster
>
> It´s accessible via URL
>
> The name is lowercase and the format is UTF-8
>
> I restarted the TFTP servers when needed
>
> The Cisco Support Field in the CSF device is empty.
>
> In the Jabber Client I used the Diagnostics Tool (CTRL-SHIFT-D) and
> checked that all setings are ok.
> I reset the client, cleared all the files under %APPDATA%\Local\Cisco\ and
> %APPDATA%\Roaming\Cisco and restarted the client.
>
> The Jabber Client can log on, if done manually, specifiing the
> "Callmanager 9 "mode and the server name/IP. If I switch to Automatic, it
> asks for Webex credentials (My customer has a couple of Webex accounts, but
> not enough for all the enterprise, hence he wants avoid Webex).
>
> I checked the jabber.log, but I didn't get any clues.
>
>
>
> Is there anything I am missing from the process?
>
>
>
> P.S I also posted this question here: https://supportforums.cisco.
> com/t5/jabber-clients/jabber-config-xml-not-being-
> downloaded-or-being-ignored/m-p/3209901#M20756
>
>
>
> Regards,
>
>
>
> Ariel.
>
>
>
>
>
> *Ariel Roza*
>
> *Support Engineer / Southern Cone *
>
> t: +54 11 5282-0458 <+54%2011%205282-0458>
>
> c: +54 9 11 5017-4417 <+54%209%2011%205017-4417>
>
> Av. Belgrano 955 – Piso 20 – CABA – Argentina – C1092AAJ
>
> www.la.logicalis.com
> 
>
>
> *_ **Business **and
> technology working as one*
>
> [image: cid:image006.png@01D298D0.103CDF50]
>
>
>
> [image: Descripción: Descripción: Descripción: Descripción: Descripción:
> Descripción: Descripción: Descripción: Descripción: Descripción:
> Descripción: Descripción: Descripción: Descripción: Descripción:
> Descripción: tw]
> 
>  [image: Descripción: Descripción: Descripción: Descripción: Descripción:
> Descripción: Descripción: Descripción: Descripción: Descripción:
> Descripción: Descripción: Descripción: Descripción: Descripción:
> Descripción: fb]
> 
>  [image: Descripción: Descripción: Descripción: Descripción: Descripción:
> Descripción: Descripción: Descripción: Descripción: Descripción:
> Descripción: Descripción: Descripción: Descripc

Re: [cisco-voip] jabber-config.xml not being downloaded or being ignored

2017-11-03 Thread Ben Amick
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 Communications Analyst

From: ROZA, Ariel [mailto:ariel.r...@la.logicalis.com]
Sent: Friday, November 3, 2017 1:37 PM
To: Ben Amick ; cisco-voip@puck.nether.net
Subject: RE: jabber-config.xml not being downloaded or being ignored

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...@humanarc.com]
Enviado el: viernes, 03 de noviembre de 2017 02:33 p.m.
Para: ROZA, Ariel 
mailto:ariel.r...@la.logicalis.com>>; 
cisco-voip@puck.nether.net
Asunto: RE: jabber-config.xml not being downloaded or being ignored

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 of 
Jabber that will disable the webex on the initial install, and that's the fix 
if they want to maintain having webex business accounts.

Alternatively, you might be able to get a support ticket in to remove your 
domain from the webex DNS, which the company gets added to because of the cloud 
messaging built into webex, but I don't know if they can neuter that without 
neutering the webex accounts proper.

Ben Amick
Unified Communications Analyst

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of ROZA, 
Ariel
Sent: Friday, November 3, 2017 1:27 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] jabber-config.xml not being downloaded or being ignored

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.

The jabber-config contents are this:




WEBEX


UDS



I have tried Jabber clients 11.6.4 and 11.8.2

The file is loaded to both TFTP serves in the cluster
It´s accessible via URL
The name is lowercase and the format is UTF-8
I restarted the TFTP servers when needed
The Cisco Support Field in the CSF device is empty.
In the Jabber Client I used the Diagnostics Tool (CTRL-SHIFT-D) and checked 
that all setings are ok.
I reset the client, cleared all the files under %APPDATA%\Local\Cisco\ and 
%APPDATA%\Roaming\Cisco and restarted the client.
The Jabber Client can log on, if done manually, specifiing the "Callmanager 9 
"mode and the server name/IP. If I switch to Automatic, it asks for Webex 
credentials (My customer has a couple of Webex accounts, but not enough for all 
the enterprise, hence he wants avoid Webex).
I checked the jabber.log, but I didn't get any clues.

Is there anything I am missing from the process?

P.S I also posted this question here: 
https://supportforums.cisco.com/t5/jabber-clients/jabber-config-xml-not-being-downloaded-or-being-ignored/m-p/3209901#M20756


Regards,

Ariel.


[cid:image001.jpg@01D354A9.1FF5B940]Ariel Roza
Support Engineer / Southern Cone
t: +54 11 5282-0458
c: +54 9 11 5017-4417
Av. Belgrano 955 - Piso 20 - CABA - Argentina - C1092AAJ
www.la.logicalis.com

Re: [cisco-voip] jabber-config.xml not being downloaded or being ignored

2017-11-03 Thread Ben Amick
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 [mailto:bmead...@gmail.com] On Behalf Of Brian Meade
Sent: Friday, November 3, 2017 1:38 PM
To: Ben Amick 
Cc: ROZA, Ariel ; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] jabber-config.xml not being downloaded or being 
ignored

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 
mailto:bam...@humanarc.com>> wrote:
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 of 
Jabber that will disable the webex on the initial install, and that’s the fix 
if they want to maintain having webex business accounts.

Alternatively, you might be able to get a support ticket in to remove your 
domain from the webex DNS, which the company gets added to because of the cloud 
messaging built into webex, but I don’t know if they can neuter that without 
neutering the webex accounts proper.

Ben Amick
Unified Communications Analyst

From: cisco-voip 
[mailto:cisco-voip-boun...@puck.nether.net]
 On Behalf Of ROZA, Ariel
Sent: Friday, November 3, 2017 1:27 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] jabber-config.xml not being downloaded or being ignored

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.

The jabber-config contents are this:




WEBEX


UDS



I have tried Jabber clients 11.6.4 and 11.8.2

The file is loaded to both TFTP serves in the cluster
It´s accessible via URL
The name is lowercase and the format is UTF-8
I restarted the TFTP servers when needed
The Cisco Support Field in the CSF device is empty.
In the Jabber Client I used the Diagnostics Tool (CTRL-SHIFT-D) and checked 
that all setings are ok.
I reset the client, cleared all the files under %APPDATA%\Local\Cisco\ and 
%APPDATA%\Roaming\Cisco and restarted the client.
The Jabber Client can log on, if done manually, specifiing the "Callmanager 9 
"mode and the server name/IP. If I switch to Automatic, it asks for Webex 
credentials (My customer has a couple of Webex accounts, but not enough for all 
the enterprise, hence he wants avoid Webex).
I checked the jabber.log, but I didn't get any clues.

Is there anything I am missing from the process?

P.S I also posted this question here: 
https://supportforums.cisco.com/t5/jabber-clients/jabber-config-xml-not-being-downloaded-or-being-ignored/m-p/3209901#M20756


Regards,

Ariel.


[cid:image001.jpg@01D354A9.52E6A5D0]Ariel Roza
Support Engineer / Southern Cone
t: +54 11 5282-0458
c: +54 9 11 5017-4417
Av. Belgrano 955 – Piso 20 – CABA – Argentina – C1092AAJ
www.la.logicalis.com
_
Business and technology working as one
[cid:image006.png@01D298D0.103CDF50]

[cid:image003.jpg@01D354A9.52E6A5D0][Descripción: Descripción: Descripción: 
Descripción: Descripción: Descripción: Descripción: Descripción: Descripción: 
Descripción: Descripción: Descripción: Descripción: Descripción: Descripción: 
Descripción: 
tw]
 [Descripción: Descripción: Descripción: Descripción: Descripción: Descripción: 
Descripción: Descripción: Descripción: Descripción: Descripción: Descripción: 
Descripción: Descripción: Descripción: Descripción: fb] 


Re: [cisco-voip] jabber-config.xml not being downloaded or being ignored

2017-11-03 Thread ROZA, Ariel
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 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 Communications Analyst

From: ROZA, Ariel [mailto:ariel.r...@la.logicalis.com]
Sent: Friday, November 3, 2017 1:37 PM
To: Ben Amick mailto:bam...@humanarc.com>>; 
cisco-voip@puck.nether.net
Subject: RE: jabber-config.xml not being downloaded or being ignored

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...@humanarc.com]
Enviado el: viernes, 03 de noviembre de 2017 02:33 p.m.
Para: ROZA, Ariel 
mailto:ariel.r...@la.logicalis.com>>; 
cisco-voip@puck.nether.net
Asunto: RE: jabber-config.xml not being downloaded or being ignored

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 of 
Jabber that will disable the webex on the initial install, and that's the fix 
if they want to maintain having webex business accounts.

Alternatively, you might be able to get a support ticket in to remove your 
domain from the webex DNS, which the company gets added to because of the cloud 
messaging built into webex, but I don't know if they can neuter that without 
neutering the webex accounts proper.

Ben Amick
Unified Communications Analyst

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of ROZA, 
Ariel
Sent: Friday, November 3, 2017 1:27 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] jabber-config.xml not being downloaded or being ignored

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.

The jabber-config contents are this:




WEBEX


UDS



I have tried Jabber clients 11.6.4 and 11.8.2

The file is loaded to both TFTP serves in the cluster
It´s accessible via URL
The name is lowercase and the format is UTF-8
I restarted the TFTP servers when needed
The Cisco Support Field in the CSF device is empty.
In the Jabber Client I used the Diagnostics Tool (CTRL-SHIFT-D) and checked 
that all setings are ok.
I reset the client, cleared all the files under %APPDATA%\Local\Cisco\ and 
%APPDATA%\Roaming\Cisco and restarted the client.
The Jabber Client can log on, if done manually, specifiing the "Callmanager 9 
"mode and the server name/IP. If I switch to Automatic, it asks for Webex 
credentials (My customer has a couple of Webex accounts, but not enough for all 
the enterprise, hence he wants avoid Webex).
I checked the jabber.log, but I didn't get any clues.

Is there anything I am missing from the process?

P.S I also posted this question here: 
https://supportforums.cisco.com/t5/jabber-clients/jabber-config-xml-not-being-downloaded-or-being-ignored/m-p/3209901#M20756


Regards,

Ariel.


[cid:image007.jpg@01D354B1.C88BB520]Ariel Roza
Support Engineer / Southern Cone
t: +54 11 5282-0458
c: +54 9 11 5017-4417
Av. Belgrano 955 - Piso 20 - CABA - Arg

Re: [cisco-voip] Hide individual numbers behind hunt pilot

2017-11-03 Thread Pawlowski, Adam
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 internally as a "PoC" just by putting in ! and using the CSS 
I'd like to have dumped that line to. 

Best,

Adam


> -Original Message-
> From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of
> cisco-voip-requ...@puck.nether.net
> Sent: Friday, November 03, 2017 12:00 PM
> To: cisco-voip@puck.nether.net
> Subject: cisco-voip Digest, Vol 169, Issue 3
> 
> Send cisco-voip mailing list submissions to
>   cisco-voip@puck.nether.net
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>   https://puck.nether.net/mailman/listinfo/cisco-voip
> or, via email, send a message with subject or body 'help' to
>   cisco-voip-requ...@puck.nether.net
> 
> You can reach the person managing the list at
>   cisco-voip-ow...@puck.nether.net
> 
> When replying, please edit your Subject line so it is more specific than
> "Re: Contents of cisco-voip digest..."
> 
> 
> Today's Topics:
> 
>1. Re: Hide individual numbers behind hunt pilot number
>   (Sebastian Hagedorn)
> 
> 
> --
> 
> Message: 1
> Date: Fri, 03 Nov 2017 14:25:20 +0100
> From: Sebastian Hagedorn 
> To: Brian Meade 
> Cc: cisco-voip list 
> Subject: Re: [cisco-voip] Hide individual numbers behind hunt pilot
>   number
> Message-ID: <2b9acb2cab5a029aab635...@tyrion.rrz.uni-koeln.de>
> Content-Type: text/plain; charset=utf-8; format=flowed
> 
> 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 contains the newly created partition
> - created a new translation pattern in that partition. The pattern is the
> 5-digit extension I am using for this test. The CSS is the normal one.
> Under Calling Party Transformations I have entered the hunt pilot number
> as Calling Party Transform Mask
> 
> When I assign the new CSS to the Directory Number I am using for this test
> I get the standard "your call couldn't be completed" message for any
> number I try to dial.
> 
> Any ideas where I went wrong?
> 
> 
> Thanks
> Sebastian
> 
> --On 13. Oktober 2017 um 10:43:11 -0400 Brian Meade 
> wrote:
> 
> > Sending the calls through a translation pattern is probably easiest.
> > Give everyone in the hunt group a new CSS with new partition that
> > sends all calls through a translation pattern that masks the number
> > then has your normal CSS on the translation pattern.
> >
> > On Fri, Oct 13, 2017 at 9:04 AM, Sebastian Hagedorn
> >  wrote:
> >
> >> Hi,
> >>
> >> using CUCM 10.0 we have achieved the goal stated in the subject using
> >> Calling Party Transformation Patterns. The pattern is the number(s)
> >> we want to hide, the field "Calling Party Transformation Mask"
> >> contains the number of the hunt pilot, and the Partition references a
> >> CSS that is applied to the MGCP gateway as "Calling Party
> Transformation CSS".
> >>
> >> So far, so good. But this only works for calls that go through the
> >> gateway. Ideally we would like to achieve the same effect for
> >> internal calls as well. I haven't been able to figure out where I
> >> need to apply a Calling Party Transformation CSS for it to work for all
> calls.
> >>
> >> Ideas? Or is there a different way to achieve that?
> 
> --
> .:.Sebastian Hagedorn - Weyertal 121 (Geb?ude 133), Zimmer 2.02.:.
>  .:.Regionales Rechenzentrum (RRZK).:.
>.:.Universit?t zu K?ln / Cologne University - ? +49-221-470-89578.:.
> 
> 
> --
> 
> Subject: Digest Footer
> 
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> 
> 
> --
> 
> End of cisco-voip Digest, Vol 169, Issue 3
> **
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip