Re: [cisco-voip] Paging port on VG-310 doesn't go off-hook

2017-06-05 Thread Schlotterer, Tommy
Do you have the TAMB2 set as a station port?

Thanks

Tommy


Tommy Schlotterer | Systems Engineer - Collaboration
Presidio (NASDAQ: PSDO) | www.presidio.com<http://www.presidio.com>
20 N Saint Clair 3rd Floor, Toledo, OH 43604
D: 419.214.1415 | C: 419.706.0259 | 
tschlotte...@presidio.com<mailto:tschlotte...@presidio.com>



From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Hamu 
Ebiso
Sent: Monday, June 05, 2017 4:46 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Paging port on VG-310 doesn't go off-hook

Hi Everyone,

Has anyone seen this issue before and know how to fix it. We are Using Bogen's 
paging system with TAMB2 and some of the port on VG doesn't go off-hook when 
dialed. When you run show voce port summ, it shows On-hook ringing. Any help 
will be appreciated.

Thanks
Hamu



Sent from my Sprint Samsung Galaxy S® 6.


This message w/attachments (message) is intended solely for the use of the 
intended recipient(s) and may contain information that is privileged, 
confidential or proprietary. If you are not an intended recipient, please 
notify the sender, and then please delete and destroy all copies and 
attachments. Please be advised that any review or dissemination of, or the 
taking of any action in reliance on, the information contained in or attached 
to this message is prohibited.
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


[cisco-voip] Paging port on VG-310 doesn't go off-hook

2017-06-05 Thread Hamu Ebiso
Hi Everyone,

Has anyone seen this issue before and know how to fix it. We are Using Bogen's 
paging system with TAMB2 and some of the port on VG doesn't go off-hook when 
dialed. When you run show voce port summ, it shows On-hook ringing. Any help 
will be appreciated.

Thanks
Hamu



Sent from my Sprint Samsung Galaxy S® 6.
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


Re: [cisco-voip] Paging

2016-10-28 Thread 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
le...@uoguelph.ca
www.uoguelph.ca/ccs
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1



From: cisco-voip <cisco-voip-boun...@puck.nether.net> on behalf of Anthony 
Holloway <avholloway+cisco-v...@gmail.com>
Sent: Friday, October 28, 2016 4:05 PM
To: Scott Voll
Cc: cisco-voip@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': ''}
resp = requests.post('http://{}/CGI/Execute'.format(phone), auth=creds, 
data=xml)


On Fri, Oct 28, 2016 at 12:14 PM, Scott Voll 
<svoll.v...@gmail.com<mailto:svoll.v...@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@puck.nether.net<mailto:cisco-voip@puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip


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


Re: [cisco-voip] Paging

2016-10-28 Thread Anthony Holloway
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  and requests
):

import requests
phone = '10.1.1.10'
creds = ('phonecontroluser', 'phonecontrolpass')
xml = {'XML': ''}
resp = requests.post('http://{}/CGI/Execute'.format(phone), auth=creds,
data=xml)


On Fri, Oct 28, 2016 at 12:14 PM, Scott Voll  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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


[cisco-voip] Paging

2016-10-28 Thread Scott Voll
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@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip