Issue with SBC since final V18 update

[COM-TEL]

Friends, I'm not sure if this is a bug or a fix.

Since the final v18 update, my SBC is not working correctly although it is showing as registered on 3CX

I have 8 DID's each going to their own extension on a single Fanvil X4u (previously it was a Yealink T46G, but that is now EOL)

Each extension is connected via the SBC and appears as registered on the phone ONLY. No inbound or outbound calls can be made and they do not appear as registered on 3CX.

When I change the SIP server to the 3CX FQDN the extension by passes the SBC and registers on the 3CX instance and everything works fine.

Prior to the update, I could register each extension on the phone via the SBC and it would appear as registered on 3CX. This makes me wonder if it was previously a bug that let you register more than one extension per phone via the SBC.

Any ideas as to why the SBC is not recognising that the extensions are registered? It was working fine until the upgrade.

 

[JohnS_3CX]

I have 8 DID's each going to their own extension on a single Fanvil X4u (previously it was a Yealink T46G, but that is now EOL)

Each extension is connected via the SBC and appears as registered on the phone ONLY. No inbound or outbound calls can be made and they do not appear as registered on 3CX.

Do you mean you have 8 DIDs going to a single Fanvil? (ie. 8 SIP accounts on a single device)

If you are registering multiple extensions on a single device, please be advised that this was never supported and there are no plans to make this work.

 

[COM-TEL]

Do you mean you have 8 DIDs going to a single Fanvil? (ie. 8 SIP accounts on a single device)

If you are registering multiple extensions on a single device, please be advised that this was never supported and there are no plans to make this work.

Thanks for the reply.

Yes that is correct. 8 SIP accounts on one phone, each represents an extension on the 3CX instance, registering via the SBC, or not as the case is now.