Fanvil i18S ring to Yealink phones

[man416]

I recently updated the firmware for a customers Yealink phones and after the update the Fanvil 18s Intercom was no longer able call the ring group. I tried ringing a direct extension and it would ring on the intercom but not on the phone. I had all the extensions set for PBX delivers audio and when I removed that option the phones started ringing again. I'd like to leave that option checked because resolved some other issues I had with the paging. Any ideas why the firmware update would have stopped that from working?

 

[JohnS_3CX]

Hello,

I would suggest to reprovision the devices in question (doorphone and yealinks)

Also ensure that the i18S firmware is updated too. https://www.3cx.com/sip-phones/fanvil-sip-doorphones/

 

[Alphabetic]

I had this problem.

it was because i had manually configured what the BLF key does on the Fanvil and then a reprovision wiped it.

Configure the action button for the first BLF in the EXT settings.

 

[man416]

Thanks for the replies. I know I reprovisioned the Fanvil doorphone a couple times but I don't remember if I reprovisioned the phones after the firmware update. The ring group works fine when called directly or through the IVR just doesn't work from the door phone when the PBX delivers audio is enabled, which did work before the Yealink firmware updates. The firmware on the doorphone is 2.6.0.6681 so is up to date. The BLF is configured correctly. The cyberdata paging ringer is programmed in the group and was the only thing that rang.

 

[JohnS_3CX]

Set it to ring to a single yealink first (BLF -> Speed Dial as the guide describes). I think you said you did this and the doorphone dialled but the phone didn't ring.

Go ahead and tell us how your system is set up, as well as how the networks is (all devices on same IP range / subnet? )

 

[man416]

I haven't been back out to try reprovisioning the phones after the firmware update yet but not real hopeful that will fix it. It's working now with the PBX delivers audio unchecked under all the extensions but it did work with it enabled before I updated the Yealink firmware. The firmware update definitely caused it to quit working. I can try leaving it this way but it was enabled because they were having some intermittent issues with dropped calls and the paging and which went away after I enabled it. Am I correct that it's best to have the PBX delivers audio disabled for extensions under most circumstances?

They are setup with a single range and there are less than 40 devices total on network including the phones. There are 13 yealink phones, 2 Fanvil i18s doorphones and a cyberdata paging adapter used for paging and ringer. The intercom buttons are setup with a custom speed dial for the ring group (all phones + paging ringer). I tried changing to a single phone BLF and didn't work, I could hear ringing on the door phone but no phone actually rang.

 

[JohnS_3CX]

Usually PBX Delivers Audio is used for things like STUN phones, or enforced when recordings are enabled.

For phones local networks with a local PBX you leave it disabled unless there are specific reasons that require it or for troubleshooting purposes. Leaving it disabled means the devices can contact each other directly to send audio rather than having it proxied by the PBX. If no phone rang during your test you should see the logs or run a capture which you can then analyze in wireshark to see where the call was sent. Maybe the call reached the desired extension but was forwarded elsewhere for example