79xx IP Phone IGMP support

[BuckWeet]

Has anyone come across 'certified documentation' of what the cisco ip 79xx handsets support via IGMP??

from what i can tell they only support IGMPv1, which had some serious downfalls due to the fact that it can't do IGMP leaves. Therefore any multicast group will take 3 minutes to timeout..

What in turn, this means that if you deploy multi-cast MoH in your WAN sites, it will be flooded for 3 minutes after the MoH is not needed anymore. All due to the fact that it only operates at IGMPv1..

Does anyone have any info on this?


BuckWeet

 

[ccmuser]

Hey buckweet.. We noticed that too. We took the approach that it just seemed more prudentto run MOH off the remote routers that way there is no traffic moving over the wan at all for MOH services.

 

[BuckWeet]

Hrm, thats a good idea actually...
Is there any kind of application that can help you roll this out centrally (other than writing a script)

Unfortunately that is not an acceptible solution for us..(have about 1600 remote sites to roll this out to)

So I think we're going to push this off to Cisco to get them to support IGMPv2...

Also, on your gateways when you did the Multicast MoH, do you use H.323 or MGCP? It seems that can you can't use a Multicast MoH source with the H.323 (can't find docs on how to support this if possible) The only other solution I can think of is to put the H.323 gateways in a different device pool and have them use a unicast source.

Thoughts?

Thanks for the info as well.

BuckWeet

 

[ccmuser]

ahh good question.. You acutally use The SRST MOH locally on the router to SPOOF the stream that CCM is advertising in the device pool. You then change the Hop count in in media resourses to not allow MOH traffic originating from ccm to access the WAN.

Besides starting SRTS MOH on the router and changing hop count on media-resource nothing else actually has to be done. Quite a good trick actually. Just remember when you enter the multicast adress on each local router it willl be the SAME adress on all 1600 routers. Just don't let the traffic leave each local LAN. You can push out these changes through Ciso works if you are using it.

Good luck. But this one is actually alot simpler then you were expecting I think..

 

[BuckWeet]

Yea, that does sound simple actually..

Our main issue is that if we need to change the MoH for the retail branches, thats 1600 change controls we have to put in.. Even if we did it via the cisco works, it would still require the 1600 change controls. LOL... (gotta love being so big that you have to do change controls just to sneeze on the routers/switches)

That would make someones life hell if we did have to change the MoH. It'd be much easier for us to just make Cisco implement this

I just emailed our global account team, hopefully they'll have an answer for us shortly.

I'll update once I hear back from them

BuckWeet

 

[ccmuser]

HEHE.. I know what they are going to tell you..We have allready been through this with them. But the more people that ask and put pressure on them for things like this the better.

 

[ccmuser]

Oh BTW. this for a retail store chain? Just curios who is implementing? And you really should should run MOH locally just from a traffic management perspective. Kinda six cisco did not recommend this when you did your initial installation.

 

[BuckWeet]

Yea its for our retail banking centers. We're implementing this ourselves actually.. Multicasting has been rolled out worldwide on our network, so this is just another application being shot over the network, which is why we're going this route.

We haven't rolled this out to the branch sites yet, we're deploying the 1st VSM (voice services module) next week in our regional data center.. We're doing a centralized setup, the local sites will only have 2 POTS lines used just for 911, and then local dialing in SRST mode. Each branch site has 2 T1's, one going to a different regional touch point. So there is redundancy everywhere.. In the VSM we have 2 6506's as our distribution routers, then 4 6513's with 10 WS-X6608-T1 blades per 6513 serving as our gateways.

Retail sites are scheduled to go live in january.

Once its all said and done, there will be 4 VSM's (at this time)

There is some massive cash being dropped onto this IPT rollout, so we have some power over Cisco .. (I hope, heh)

Time will tell

BuckWeet

 

[ccmuser]

why did you choose 6608 blades? we have deployed them and in the long run I wish we never choose them. You may not be needing alot of the features we found lacking; most have to due with fax. Iether t.38 funtions for fax server, Or fax tone detection for call routing based on call type. depending on were your orginization wants to take voip you can really back yourself into a whole with these cards. they are really transcoded devices being double marketed as PRI gateways. They are adding some new features, but much to slowly.

 

[BuckWeet]

well that answer I don't have, I didn't do the design...

I think really merely for density is why they chose it..

I personally haven't implemented these gateways since CCM 3.2 days, back when it was a SCCP device..

Don't they have newer devices out for the 6500's?

BuckWeet

 

[BuckWeet]

word back from cisco is the 7912's only support IGMPv1, whereas the 7940/60's support v2