Multicast Stops Working until Phone Rebooted

[Blake1]

I've been having this issue with a few different models of Yealink phones on a few different customers for a while. We have car dealerships as customers, they send many pages per day, we have them sending the pages via Multicast to other Yealink phones and an Algo speaker device.

The issue is that it works fine for weeks, and then one day the phone will stop sending multicast pages, and we must reboot the phone to fix the issue. At first I thought it was something on the customer's network, but I keep running into this same issue with almost all of my customers that use multicast paging.

I have tried updating firmware from V83 -> 84 -> 85 -> 86 and I still see this where the phones must be rebooted after about 2 weeks for the paging to start working again. Every network this happens on is different switch vendor/model, from very basic 5 port switches to enterprise switches like Meraki/Aruba.

Anyone else having a similar issue?

My configuration looks like this:
Sending: linekey.10.type="24" linekey.10.value="224.5.6.23:10008" linekey.10.label="Page"

Receiving: multicast.listen_address.1.ip_address="224.5.6.23:10008" multicast.listen_address.1.label="Page"

[richard.leclerc@cogeco.com]

Any luck with this issue? I am having the same problem with T46S.

[axiompm]

(06-17-2022 04:27 AM)richard.leclerc@cogeco.com Wrote:  Any luck with this issue? I am having the same problem with T46S.

Same issue here with T54W and T23G ..... no fix found as yet.

[Blake1]

I haven't found a solution yet, I am looking at IGMP on switches causing the issue potentially, but most of my customers don't know how to manage their switches to confirm if any IGMP snooping/filtering is in place. I seem to only be having this issue on the T5X series phones, but I've been unable to recreate.

[complex1]

(07-05-2022 11:18 PM)Blake1 Wrote:  I haven't found a solution yet, I am looking at IGMP on switches causing the issue potentially, but most of my customers don't know how to manage their switches to confirm if any IGMP snooping/filtering is in place. I seem to only be having this issue on the T5X series phones, but I've been unable to recreate.

Hi,

Have you ever thought about submitting a support ticket to the Yealink helpdesk?
https://ticket.yealink.com/

[Blake1]

(07-06-2022 01:47 AM)complex1 Wrote:  

(07-05-2022 11:18 PM)Blake1 Wrote:  I haven't found a solution yet, I am looking at IGMP on switches causing the issue potentially, but most of my customers don't know how to manage their switches to confirm if any IGMP snooping/filtering is in place. I seem to only be having this issue on the T5X series phones, but I've been unable to recreate.

Hi,

Have you ever thought about submitting a support ticket to the Yealink helpdesk?
https://ticket.yealink.com/

I haven't opened a ticket as I was trying to understand the bug some more, and I may have figured it out.

Just did some packet captures on a customer net where we're having this issue. The customer is using all T53 and T53W phones. We did some multicast testing and found that their switch will only relay multicast packets to ports that join the IGMP group for the MC address first, and it looks like the T5X series phones are NOT joining the IGMP group even when listening is configured.

I just tested in my office by enabling IGMP filtering on my switch (it was off by default), and now when I send an MC page all the T4X phones get the page, but none of the T5X phones do! So I have enough ammo to open a ticket now as it looks like the issue is the IGMP join on the T5X series phones is not working as expected.

[jmonroe]

Hello! We are having this issue and were wondering if you had a solution to the problem?

[Chris708]

I would definitely put a ticket in with Yealink support.

From my experience, older Yealink phones had an IP and port for multicast paging. Newer firmware/models added a channel.
I haven't heard from any of our customers that the paging becomes an issue but I also never used the channels.

I tried channels when I first came across them but only spent a short amount of time testing, couldn't get them to work, so left that value empty and stuck with the IP and port which I have not seen issues with.

[Blake1]

(07-27-2022 02:51 AM)jmonroe Wrote:  Hello! We are having this issue and were wondering if you had a solution to the problem?

For some switches, using multicast address 224.0.0.X tricks the switch into always flooding to all ports (for Dell Powerconnect I know this works, not sure about other models/vendors). But in some cases, you need to disable "IGMP Snooping" or enable "Flood unknown multicast" (Meraki) on the switch. On HP Procurve you can either just disable the IGMP feature altogether or statically add the multicast address to the IGMP group list on the VLAN where the phones are: https://techhub.hpe.com/eginfolib/networ...01s03.html

I do have a ticket open with Yealink for this, seeing if we can add an "IGMP Join Refresh" feature where we can rebroadcast the IGMP join periodically without rebooting the phone.

[jedhcrs]

Has there been any traction with your ticket? I'm in a similar situation, with 50ish T46S phones. Multicast pages work great once a phone is rebooted, however, after some amount of (undetermined) time, the pages stop going out. In some cases, phones stop receiving the multicast pages.

(08-17-2022 09:55 PM)Blake1 Wrote:  I do have a ticket open with Yealink for this, seeing if we can add an "IGMP Join Refresh" feature where we can rebroadcast the IGMP join periodically without rebooting the phone.