<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>Interesting. What you find to be a problem, I find useful. I have test phones here that are page recipients that I put into headset mode so the pages don't bother people.
<img class="EmojiInsert" id="OWAEmoji936116" alt="😊" style="vertical-align: bottom;" src="cid:b49e8b63-b6bc-440e-b180-32eacf352742"></p>
<p><br>
</p>
<p>But that at least confirms your findings. In headset mode, it bypasses the speaker.
<img class="EmojiInsert" id="OWAEmoji27767" alt="☹" style="vertical-align: bottom;" src="cid:7275233e-dc21-44ee-b3cd-87ec6a9a95ec"></p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<div id="Signature">
<div id="divtagdefaultwrapper" style="font-size:12pt; color:#000000; background-color:#FFFFFF; font-family:Calibri,Arial,Helvetica,sans-serif">
<p></p>
<div>---</div>
<div>Lelio Fulgenzi, B.A.</div>
<div>Senior Analyst, Network Infrastructure</div>
<div>Computing and Communications Services (CCS)</div>
<div>University of Guelph</div>
<div><br>
</div>
<div>519-824-4120 Ext 56354</div>
<div>lelio@uoguelph.ca</div>
<div>www.uoguelph.ca/ccs</div>
<div>Room 037, Animal Science and Nutrition Building</div>
<div>Guelph, Ontario, N1G 2W1</div>
<p></p>
</div>
</div>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> cisco-voip <cisco-voip-bounces@puck.nether.net> on behalf of Anthony Holloway <avholloway+cisco-voip@gmail.com><br>
<b>Sent:</b> Friday, October 28, 2016 4:05 PM<br>
<b>To:</b> Scott Voll<br>
<b>Cc:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] Paging</font>
<div> </div>
</div>
<div>
<div dir="ltr">I don't think you are alone in this. I can confirm that my 8861 running 11.0(1) firmware does this too, and there are other reports of it happening online.
<div><br>
</div>
<div>If only Cisco would implement the XSI Audio Path Control for all phone models, then we'd be set. By the way, I did try to use this on my 8861 phone, but it doesn't work. Oh well.</div>
<div>
<blockquote style="margin:0px 0px 0px 40px; border:none; padding:0px">
<div><br>
</div>
<div>
<div><b>XSI Audio Path Control</b></div>
</div>
<div>
<div>The XSI Audio Path Control feature enables XSI calls to specify if the audio is played on the speakerphone</div>
</div>
<div>
<div>or handset speaker of the phone. The feature is available on the following phones:</div>
</div>
<div>
<div><br>
</div>
</div>
<blockquote style="margin:0px 0px 0px 40px; border:none; padding:0px">
<div>
<div>• Cisco Unified Wireless IP Phones 7921G, 7925G, 7925G-EX, and 7926G with release 1.4(4) and later</div>
</div>
</blockquote>
<blockquote style="margin:0px 0px 0px 40px; border:none; padding:0px">
<div>
<div><br>
</div>
</div>
</blockquote>
<blockquote style="margin:0px 0px 0px 40px; border:none; padding:0px">
<div>
<div>NOTE: In releases prior to 1.4(4), by default the audio path is set to speakerphone unless a</div>
</div>
</blockquote>
<blockquote style="margin:0px 0px 0px 40px; border:none; padding:0px">
<div>
<div>headset is connected.</div>
</div>
</blockquote>
<blockquote style="margin:0px 0px 0px 40px; border:none; padding:0px">
<div>
<div><br>
</div>
</div>
</blockquote>
<blockquote style="margin:0px 0px 0px 40px; border:none; padding:0px">
<div>
<div>• Cisco Wireless IP Phone 8821</div>
</div>
</blockquote>
<div>
<div><br>
</div>
</div>
<div>
<div>The XSI Audio Path Control feature utilizes the RTP URI which has been extended to give the administrator</div>
</div>
<div>
<div>this option to specify whether audio received via XSI is played through the speaker phone or handset speaker</div>
</div>
<div>
<div>of the Cisco IP Phone.</div>
</div>
<div>
<div><br>
</div>
</div>
<div>
<div>RTP URI Format</div>
</div>
<div>
<div>RTPRx:i:p:v:s or RTPMRx:i:p:v:s</div>
</div>
<div>
<div>Where</div>
</div>
<div>
<div>i = equals IP address (x.x.x.x).</div>
</div>
<div>
<div>p = equals UDP port (20480-32768).</div>
</div>
<div>
<div>v = volume (0-100).</div>
</div>
<div>
<div>s = specifies where the audio for an XSI call should be played.</div>
</div>
<div>
<div><br>
</div>
</div>
<blockquote style="margin:0px 0px 0px 40px; border:none; padding:0px">
<div>
<div>• If s = 0, then the audio for the XSI call will be played to the speaker phone.</div>
</div>
</blockquote>
<blockquote style="margin:0px 0px 0px 40px; border:none; padding:0px">
<div>
<div>• If s = 1, then the audio for the XSI call will be played to the handset speaker or headset.</div>
</div>
</blockquote>
<blockquote style="margin:0px 0px 0px 40px; border:none; padding:0px">
<div>
<div>• If s = 2, then the audio for the XSI call will be played to the current audio path.</div>
</div>
</blockquote>
<blockquote style="margin:0px 0px 0px 40px; border:none; padding:0px">
<div>
<div>• If s is not present, then the audio for the XSI call is played to the speaker phone.</div>
</div>
</blockquote>
<div><br>
</div>
<div>Source: Cisco Unified IP Phone Services Application Development Notes</div>
<div><br>
</div>
</blockquote>
BONUS</div>
<div><br>
</div>
<div>Here's the base of the Python script I used for testing (you must install <a href="https://www.python.org/">
python</a> and <a href="http://docs.python-requests.org/en/master/user/install/#install">
requests</a>):</div>
<div><br>
</div>
<div><font face="monospace, monospace">import requests</font></div>
<div><font face="monospace, monospace">phone = '10.1.1.10'</font></div>
<div><font face="monospace, monospace">creds = ('phonecontroluser', 'phonecontrolpass')</font></div>
<div>
<div><font face="monospace, monospace">xml = {'XML': '<CiscoIPPhoneExecute><ExecuteItem URL="RTPMRx:239.1.1.1:20480:100" /></CiscoIPPhoneExecute>'}</font></div>
<div><font face="monospace, monospace">resp = requests.post('http://{}/CGI/Execute'.format(phone), auth=creds, data=xml)</font></div>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Oct 28, 2016 at 12:14 PM, Scott Voll <span dir="ltr">
<<a href="mailto:svoll.voip@gmail.com" target="_blank">svoll.voip@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
<div dir="ltr">we are looking at IP phone paging. But have ran into a MAJOR problem. wondering if any of you know a work around.
<div><br>
</div>
<div>Informacast does a Multicast to all the phones. My problem is that I'm using 8861 phones and 80%+ use headsets. if they are all set to use headsets..... then all the paging goes over the headsets, even if they are cradled. Which in a sense makes the
paging ineffective at best.</div>
<div><br>
</div>
<div>Singlewire says this is a function of CM. Anyone know of a work around? a way to set all paging through the speaker phone?</div>
<div><br>
</div>
<div>TIA</div>
<span class="HOEnZb"><font color="#888888">
<div><br>
</div>
<div>Scott</div>
<div><br>
</div>
</font></span></div>
<br>
______________________________<wbr>_________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/<wbr>mailman/listinfo/cisco-voip</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</body>
</html>