[cisco-voip] MoH on CME & Internal Network

Dana Tong (AU) Dana.Tong at didata.com.au
Thu Oct 1 19:28:06 EDT 2009


Where does the voice layer 3 terminate? On the gateway or on the switches? If you are routing on the switch you might need to configure an rp-address on both the gateway and the switch. The switch will also need to be an advanced image to support multicast routing.

Else if you are terminating the phones on the gateway you can add the voice vlan IP and the lookback to the telephony configuration.

Ie

Telephony-service
multicast moh 239.1.1.1 port <port> <IP address of Voice vlan> <IP address of loopback interface>

for example, in the past I might have used something like:
multicast moh 239.1.1.1 port 16384 10.1.1.1 10.1.2.1

Cheers
Dana


From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Sean Walberg
Sent: Friday, 2 October 2009 6:46 AM
To: Nick Matthews
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] MoH on CME & Internal Network

Instead of disabling IGMP snooping, try enabling PIM on the routers. There's also the "ip gmp snooping querier" command on 3750s that will keep the queries going and therefore the snooping tables primed.

I've run into enough problems caused by the lack of snooping (either because it was turned off, or the switch didn't support it) to last a while. IGMP snooping is there for a very good reason.

Sean


On Thu, Oct 1, 2009 at 2:58 PM, Nick Matthews <matthnick at gmail.com<mailto:matthnick at gmail.com>> wrote:
Some common things to get multicast MoH working:  Enabling multicast routing on any l3 points between the CME and phones, and disabling igmp snooping - 'no ip igmp snooping'.


-nick
On Thu, Oct 1, 2009 at 3:34 PM, Chris Ward (chrward) <chrward at cisco.com<mailto:chrward at cisco.com>> wrote:

The fact that they quit beeping is actually a positive sign as this means the MOH stream is probably being allocated, just not making it to the phone.



Can you give us the logical topology between the CME and the phones? Is the GigE 0/0 connected to the subnet that the phones are on or are there other hops?



Also, on the "multicast moh 239.1.1.1 port 2000" command you should try to specify a source address of the GigE interface and see if that helps.



-Chris



From: cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net> [mailto:cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>] On Behalf Of Kim, Hyoun S
Sent: Thursday, October 01, 2009 3:30 PM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] MoH on CME & Internal Network



I'm running CME 7.0 and have a question on MoH.



I've successfully changed my music-on-hold for my VoIP system.  However, my manager has told me he wants to play the music-on-hold file for internal calls as well.  Previously, the phone would just beep to remind you that you have a call on hold (for internal calls).  For outside calls, the MoH plays fine.



I've read that in order to play MoH for the internal network, you have to do it through multicast.  So on my router, I did the following:

----------------------

ip multicast-routing

!

Interface GigabitEthernet0/0

ip pim dense-mode (also did sparse-dense-mode)

!

ccm-manager music-on-hold

!

telephony-sevice

moh On-Hold-Rev2.wav

multicast moh 239.1.1.1 port 2000 (I've also tried 239.1.1.3, 5, etc)

----------------------



Things to note:  All entries in ephone-dn have "multicast-moh" enabled.



What am I missing here?  When I make the above changes, our phones quit "beeping" when internal calls are placed on hold.  When I remove the 'multicast moh 239.1.1.1 port 2000' line, our phones beep again internally when on hold.



Any help would be appreciated.



-Hyoun





Error! Filename not specified.

________________________________

Hyoun Kim * Network Administrator I - East Division

640 Broadmor Blvd * Suite 80 * Murfreesboro, TN 37129

' 615.217.6245 * ' 859.312.6941 * 7 615.217.6255 * * Hyoun.Kim at chartercom.com<mailto:Hyoun.Kim at chartercom.com>





E-MAIL CONFIDENTIALITY NOTICE:















The contents of this e-mail message and

any attachments are intended solely for the

addressee(s) and may contain confidential

and/or legally privileged information. If you

are not the intended recipient of this message

or if this message has been addressed to you

in error, please immediately alert the sender

 by reply e-mail and then delete this message

and any attachments. If you are not the

intended recipient, you are notified that



any use, dissemination, distribution, copying,

or storage of this message or any attachment

is strictly prohibited.















_______________________________________________
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


_______________________________________________
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



--
Sean Walberg <sean at ertw.com<mailto:sean at ertw.com>>    http://ertw.com/

******************************************************************************
 - NOTICE FROM DIMENSION DATA AUSTRALIA
This message is confidential, and may contain proprietary or legally privileged information.  If you have received this email in error, please notify the sender and delete it immediately.

Internet communications are not secure. You should scan this message and any attachments for viruses.  Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments.
******************************************************************************

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091002/553b544e/attachment.html>


More information about the cisco-voip mailing list