[cisco-voip] RE: Call Manager Music Hold

Kris Seraphine Kris.Seraphine at cliftoncpa.com
Thu Jul 14 14:17:03 EDT 2005


You're absolutely right; I stand corrected. 

Kris Seraphine
Senior Technology Specialist
Clifton Gunderson Technology Solutions
1111 Deming Way suite 101
Madison, WI  53717
Phone: 608.833.8638
Fax: 608.833.0194
Direct: 608.662.7640
Web: www.cliftoncpa.com <http://www.cliftoncpa.com/> 


_____________________________________________
From: wsisk at cisco.com [mailto:wsisk at cisco.com] 
Sent: Thursday, July 14, 2005 1:10 PM
To: Kris Seraphine; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] RE: Call Manager Music Hold

Kris - believe you have the concept but challenge the wording:

phone1-----------phone2

phone2 presses hold
the 'user hold source id' of phone2 is used
and the MRGL of phone1 is used to locate the MOH server.

/Wes
-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net]On Behalf Of Kris Seraphine
Sent: Thursday, July 14, 2005 1:54 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] RE: Call Manager Music Hold


The MOH server is determined by the device that initiates the hold so
changing the MRGL on the held device won't work.



One way to accomplish this is to change the default MOH file ID system
parameters to an ID that doesn't exist.  Then, anything that does not
have
music sources explicitly defined (at the device pool, device or line)
will
get tone.  The downside to this is that it will fill the Event Log with
errors.



Otherwise you could create a silent music source and assign that to the
devices.



If the devices are across a router hop from the MOH server you could use
an
access list to block the multicast traffic from reaching the phones; in
which case the caller would hear silence (no tone).

Kris Seraphine




 << File: TEXT.htm >>  << File: Mime.822 >> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20050714/e591b46d/attachment.html


More information about the cisco-voip mailing list