<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">I actually got a response back from my CSM and it sounds like these types of settings can be set on the back end, but through a provisioning ticket. My CSM is submitting a ticket to have the Ultrasound feature disabled. Whether that completely
locks out the user from changing the setting, or provides flexibility, I don’t know but we don’t really have anyone using it with the handful of endpoints we have anyway.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I did try to use some of the Jabber parameters, but of course, that only functions when it is registered to CUCM. Correct, the EnableProximity parameter does not apply to Webex, from my testing.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Adam Pawlowski <ajp26@buffalo.edu> <br>
<b>Sent:</b> Wednesday, July 27, 2022 10:05 AM<br>
<b>To:</b> Johnson, Tim <johns10t@cmich.edu>; cisco-voip@puck.nether.net<br>
<b>Subject:</b> [External] RE: Webex App Config XML?<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Hi Tim,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">If it’s registered on premise, it will use the same mechanism to pull the configuration as Jabber, but it supports only a handful of parameters.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><br>
They’re listed here:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><a href="https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_appendix_0100.html#id_137099">https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_appendix_0100.html#id_137099</a><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">They were pretty adamant they were not going to let the application control be as granular this time, as some of the options paint the thing into a corner depending on how they’re used.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Proximity Enable isn’t listed as one of them unfortunately.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="vertical-align:baseline"><b><span style="font-family:"Arial",sans-serif;color:#0070C0">Adam Pawlowski</span></b><span style="font-family:"Segoe UI",sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal" style="vertical-align:baseline"><span style="font-family:"Arial",sans-serif;color:black">Network Engineer | Network and Communication Services</span><span style="font-family:"Segoe UI",sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal" style="vertical-align:baseline"><span style="font-family:"Arial",sans-serif;color:black">University at Buffalo Information Technology (UBIT) </span><span style="font-family:"Segoe UI",sans-serif;color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal" style="vertical-align:baseline"><span style="font-family:"Arial",sans-serif;color:black">243 Computing Center, Buffalo, NY 14260 <o:p></o:p></span></p>
<p class="MsoNormal" style="vertical-align:baseline"><span style="font-family:"Arial",sans-serif;color:black"><img border="0" width="405" height="21" style="width:4.2187in;height:.2187in" id="Picture_x0020_1" src="cid:image001.png@01D8A1A2.1E98BD90" alt="contact_line"></span><span style="font-family:"Segoe UI",sans-serif;color:#1F497D"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> cisco-voip <<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>>
<b>On Behalf Of </b>Johnson, Tim<br>
<b>Sent:</b> Tuesday, July 26, 2022 5:02 PM<br>
<b>To:</b> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> [cisco-voip] Webex App Config XML?<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hello all,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We just recently migrated to the Webex App and have found some annoyances with the settings that are default. Is there a way to customize the settings for the Webex app globally, similar to how you could setup a jabber-config.xml file?
The thing we’re specifically looking for right now is how to disable the “Use ultrasound” option under Devices, but I imagine there will be more items we’d like to manipulate.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">TIA,<o:p></o:p></p>
<p class="MsoNormal">Tim Johnson<o:p></o:p></p>
</div>
</div>
</body>
</html>