[cisco-voip] Paging

[Lelio Fulgenzi]

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. [😊]


But that at least confirms your findings. In headset mode, it bypasses the speaker. [☹]




---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph

519-824-4120 Ext 56354
lelio at uoguelph.ca
www.uoguelph.ca/ccs
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1


________________________________
From: cisco-voip <cisco-voip-bounces at puck.nether.net> on behalf of Anthony Holloway <avholloway+cisco-voip at gmail.com>
Sent: Friday, October 28, 2016 4:05 PM
To: Scott Voll
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Paging

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.

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.

XSI Audio Path Control
The XSI Audio Path Control feature enables XSI calls to specify if the audio is played on the speakerphone
or handset speaker of the phone. The feature is available on the following phones:

• Cisco Unified Wireless IP Phones 7921G, 7925G, 7925G-EX, and 7926G with release 1.4(4) and later

NOTE: In releases prior to 1.4(4), by default the audio path is set to speakerphone unless a
headset is connected.

• Cisco Wireless IP Phone 8821

The XSI Audio Path Control feature utilizes the RTP URI which has been extended to give the administrator
this option to specify whether audio received via XSI is played through the speaker phone or handset speaker
of the Cisco IP Phone.

RTP URI Format
RTPRx:i:p:v:s or RTPMRx:i:p:v:s
Where
i = equals IP address (x.x.x.x).
p = equals UDP port (20480-32768).
v = volume (0-100).
s = specifies where the audio for an XSI call should be played.

• If s = 0, then the audio for the XSI call will be played to the speaker phone.
• If s = 1, then the audio for the XSI call will be played to the handset speaker or headset.
• If s = 2, then the audio for the XSI call will be played to the current audio path.
• If s is not present, then the audio for the XSI call is played to the speaker phone.

Source: Cisco Unified IP Phone Services Application Development Notes

BONUS

Here's the base of the Python script I used for testing (you must install python<https://www.python.org/> and requests<http://docs.python-requests.org/en/master/user/install/#install>):

import requests
phone = '10.1.1.10'
creds = ('phonecontroluser', 'phonecontrolpass')
xml = {'XML': '<CiscoIPPhoneExecute><ExecuteItem URL="RTPMRx:239.1.1.1:20480:100" /></CiscoIPPhoneExecute>'}
resp = requests.post('http://{}/CGI/Execute'.format(phone), auth=creds, data=xml)


On Fri, Oct 28, 2016 at 12:14 PM, Scott Voll <svoll.voip at gmail.com<mailto:svoll.voip at gmail.com>> wrote:
we are looking at IP phone paging.  But have ran into a MAJOR problem.  wondering if any of you know a work around.

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.

Singlewire says this is a function of CM.  Anyone know of a work around?  a way to set all paging through the speaker phone?

TIA

Scott


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20161028/caff1bdc/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OutlookEmoji-?.png
Type: image/png
Size: 488 bytes
Desc: OutlookEmoji-?.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20161028/caff1bdc/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OutlookEmoji-?.png
Type: image/png
Size: 506 bytes
Desc: OutlookEmoji-?.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20161028/caff1bdc/attachment-0001.png>