Yealink Forums

Any suggestions from anyone in the know? I'd appreciate anything that could be done to get this feature working.

(10-16-2017 04:55 PM)Ryandh Wrote: [ -> ]Any suggestions from anyone in the know? I'd appreciate anything that could be done to get this feature working.

I know this is a bit old but did you ever get a response back?

I've done multicast paging on yealinks and been able to get them to work.

(05-15-2018 09:32 PM)Chris708 Wrote: [ -> ]

(10-16-2017 04:55 PM)Ryandh Wrote: [ -> ]Any suggestions from anyone in the know? I'd appreciate anything that could be done to get this feature working.

I know this is a bit old but did you ever get a response back?

I've done multicast paging on yealinks and been able to get them to work.

No, unfortunately not. I tried until the wheels came off and gave up as a lost cause. Could you steer me in the right direction?

(07-12-2018 11:36 PM)Ryandh Wrote: [ -> ]

(05-15-2018 09:32 PM)Chris708 Wrote: [ -> ]

(10-16-2017 04:55 PM)Ryandh Wrote: [ -> ]Any suggestions from anyone in the know? I'd appreciate anything that could be done to get this feature working.

I know this is a bit old but did you ever get a response back?

I've done multicast paging on yealinks and been able to get them to work.

No, unfortunately not. I tried until the wheels came off and gave up as a lost cause. Could you steer me in the right direction?

I'll give a try. At home right now so don't have the default Yealink Multicast IPs in front of me. I think one of them might be 224.0.0.1:10000. So, a Multicast IP consists of an IP address and a port...the port is 10000 in this case.

I'll explain setting it up through the phone GUI rather than a config file.
I am also using a Yealink T29G for my example so your Multicast IP settings may be in a different part of the GUI.
You will need two phones and they can both be set up with the same Multicast IP info. When one phone sends out a multicast page, even though it is listening on the same Address as other phones, it acts only to send a page.

We will use the Multicast IP 224.0.0.1:10000
In the phone GUI, under Directory / Multicast IP, there is a Listening Address list and a Paging List numbered 1 through 10. If your phone already has IP addresses in the locations then we can use those but, for simplicity sake, the IP address in listening list #1 should be the same IP address in the paging list in #1 and so on for the remaining #'s 2 through 10.
The Labels are just for ease of identification
For example
Listening Address #1: 224.0.0.1:10000 Label: Zone 1
Paging Address #1: 224.0.0.1:10000 Label: Zone 1
Listening Address #2: 224.0.0.1:10001 Label: Zone 2
Paging Address #2: 224.0.0.1:10001 Label: Zone 2

Make sure both phones have the same Multicast IP addresses and ports (for simplicity sake in testing).

Now, you need to set up a button to send a multicast page. In the phone's GUI, go to DSS Key Line Key. Some Yealinks have different verbage than 'Line Key'. Pick a key to change and make the changes noted below.
Select Multicast Page from the Type field.
In the Value field, type the IP address 224.0.0.1:10000
In the Label field, type Zone 1 (this is just an identifier) this could be renamed to Page All or PageFlr2.
Confirm the settings.
You should now see a button on the phone labelled Zone 1.
If you press this button, the other similarly configured phone should Beep once and you should be able to speak from your handset or speaker and hear it over the speaker of the other phone.

Hope I didn't make this too complicated.

One thing to note. The multicast paging will not normally transmit outside a firewalled subnet. I think it can be done but requires some type of translation/extra configuration.

(07-13-2018 02:29 AM)Chris708 Wrote: [ -> ]

(07-12-2018 11:36 PM)Ryandh Wrote: [ -> ]

(05-15-2018 09:32 PM)Chris708 Wrote: [ -> ]

(10-16-2017 04:55 PM)Ryandh Wrote: [ -> ]Any suggestions from anyone in the know? I'd appreciate anything that could be done to get this feature working.

I know this is a bit old but did you ever get a response back?

I've done multicast paging on yealinks and been able to get them to work.

No, unfortunately not. I tried until the wheels came off and gave up as a lost cause. Could you steer me in the right direction?

I'll give a try. At home right now so don't have the default Yealink Multicast IPs in front of me. I think one of them might be 224.0.0.1:10000. So, a Multicast IP consists of an IP address and a port...the port is 10000 in this case.

I'll explain setting it up through the phone GUI rather than a config file.
I am also using a Yealink T29G for my example so your Multicast IP settings may be in a different part of the GUI.
You will need two phones and they can both be set up with the same Multicast IP info. When one phone sends out a multicast page, even though it is listening on the same Address as other phones, it acts only to send a page.

We will use the Multicast IP 224.0.0.1:10000
In the phone GUI, under Directory / Multicast IP, there is a Listening Address list and a Paging List numbered 1 through 10. If your phone already has IP addresses in the locations then we can use those but, for simplicity sake, the IP address in listening list #1 should be the same IP address in the paging list in #1 and so on for the remaining #'s 2 through 10.
The Labels are just for ease of identification
For example
Listening Address #1: 224.0.0.1:10000 Label: Zone 1
Paging Address #1: 224.0.0.1:10000 Label: Zone 1
Listening Address #2: 224.0.0.1:10001 Label: Zone 2
Paging Address #2: 224.0.0.1:10001 Label: Zone 2

Make sure both phones have the same Multicast IP addresses and ports (for simplicity sake in testing).

Now, you need to set up a button to send a multicast page. In the phone's GUI, go to DSS Key Line Key. Some Yealinks have different verbage than 'Line Key'. Pick a key to change and make the changes noted below.
Select Multicast Page from the Type field.
In the Value field, type the IP address 224.0.0.1:10000
In the Label field, type Zone 1 (this is just an identifier) this could be renamed to Page All or PageFlr2.
Confirm the settings.
You should now see a button on the phone labelled Zone 1.
If you press this button, the other similarly configured phone should Beep once and you should be able to speak from your handset or speaker and hear it over the speaker of the other phone.

Hope I didn't make this too complicated.

One thing to note. The multicast paging will not normally transmit outside a firewalled subnet. I think it can be done but requires some type of translation/extra configuration.

omg thank you for making this make sense, finally got ours working!

So I am just now trying Multicast Paging.

I have a Yealink T46S and a Yealink T58A/V.

I have the Multicast Page Buttons setup properly on both phones.
I have the Listen Port setup properly on both phones.

I can press the Page button on the T58v and the T46s answers/listen/spouts out the audio over the speaker.

I press the Page button on the T46s, but the T58v does nothing.

T46s Firmware 66.83.0.10
Line Key 2 - Paging - 239.255.255.254:1010
Multicast IP Listen - 239.255.255.254:1010

T58v Firmware 58.83.0.15
Line Key 2 - Paging - 239.255.255.254:1010
Multicast IP Listen - 239.255.255.254:1010
Appreciate if someone could test and perhaps share a sanitized config file.

esoare[/align]

Export your .cfg file for both phones and make sure the multicast addresses match.

Also, newer Yealink firmware has a Channel setting int he Multicast paging. I have not tested that so I left it out and it still works. It may default the channel to 0 when not specifically set via cfg file.

This is the Page All for one of our clients
--------------------------

### Listen Address ###
multicast.listen_address.1.label = Page All
multicast.listen_address.1.ip_address = 224.0.0.1:10001
multicast.listen_address.1.channel =

### Paging Address ###
multicast.paging_address.1.label = Page All
multicast.paging_address.1.ip_address = 224.0.0.1:10001
multicast.paging_address.1.channel =

-------------------------
I haven't worked with a Video phone so not sure if there is something different there but I reviewed the 58V and it seems no different than other Yealink Phones.

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

There is also a setting I found that will disable multicast paging. You can check that setting.
---
Paging Priority Active
Paging Priority Active feature decides how the phone handles incoming multicast paging calls
when there is already a multicast paging call on the phone. If enabled, the phone will ignore
incoming multicast paging calls with lower priorities, otherwise, the phone will answer incoming
multicast paging calls automatically and place the previous multicast paging call on hold. *** If
disabled, the phone will automatically ignore all incoming multicast paging calls.***
---

(07-03-2019 03:13 PM)Chris708 Wrote: [ -> ]Export your .cfg file for both phones and make sure the multicast addresses match.

Things looked the same in the GUI. But the DSS key is a little different with Line = 0 on the T58V, while the T46S shows Line = 1. Perhaps changing that to 0, but that is what shows on the in the GUI, an extension 0.

That seems to be the only difference in the config.

(07-03-2019 03:13 PM)Chris708 Wrote: [ -> ]Export your .cfg file for both phones and make sure the multicast addresses match.

Also, newer Yealink firmware has a Channel setting int he Multicast paging. I have not tested that so I left it out and it still works. It may default the channel to 0 when not specifically set via cfg file.

This is the Page All for one of our clients
--------------------------

### Listen Address ###
multicast.listen_address.1.label = Page All
multicast.listen_address.1.ip_address = 224.0.0.1:10001
multicast.listen_address.1.channel =

### Paging Address ###
multicast.paging_address.1.label = Page All
multicast.paging_address.1.ip_address = 224.0.0.1:10001
multicast.paging_address.1.channel =

-------------------------
I haven't worked with a Video phone so not sure if there is something different there but I reviewed the 58V and it seems no different than other Yealink Phones.

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

There is also a setting I found that will disable multicast paging. You can check that setting.
---
Paging Priority Active
Paging Priority Active feature decides how the phone handles incoming multicast paging calls
when there is already a multicast paging call on the phone. If enabled, the phone will ignore
incoming multicast paging calls with lower priorities, otherwise, the phone will answer incoming
multicast paging calls automatically and place the previous multicast paging call on hold. *** If
disabled, the phone will automatically ignore all incoming multicast paging calls.***
---

Thanks for the additional info.
Still no go.
I factory reset them, but still has issue receiving Multicast on the Yealink T58v.

I'll have to do more troubleshooting later.

Wonder if you got your T58V to work? The original post had a T58 I believe.

Anyway, there is also a setting in phones with newer firmware to have a channel---do not set that. I initially tried using that but needed to get paging working quickly with a client so I just left that blank. I don't see you using that so that's fine. Some time I'll try getting channels to work but I have it working in newer firmware without that so I just leave it blank.

Also, on your T58 screenshot, you have the linekey.2.line= 0 --- There is no Line 0 for Yealink phones (that I know of). That should probably be linekey.2.line = 1

You listed your Listen addresses but what are your sending addresses?

---

Wanted to add for anyone reading this.

Yealink also now (always?) has the option to bring up a Paging List - If you are going to have more than one paging button, this is a very handy option to just configure a DSS key or Arrow Key with the Paging List. The Paging List will bring up a list of all the Sending Multicast Paging addresses set up on a specific phone.

For our Asterisk Cloud PBX provider, they also use the SMARTY php script programming. I was able to use IF statements to program phones with specific extensions to listen to multicast and leave others out. This allowed me to NOT have to create multiple templates for multiple groups of phones.