Solved Two VLANs, two SBCs and error 603

[Leo_B]

Hello guys,

Well, looks like I need Audience Assistance desperately. We are working on two test 3CX PBX setups coupled with Unifi hardware – USG security gate and 48-port PoE switch hooked up to. We set up to local network (default LAN + VLAN), added two SBC instances and a bunch of Yealink phones as well. Noteworthy both system share the same public IP.

The default LAN PBX system works perfectly, while the VLAN-located one reported SBC online, allows the SIP phones to register and provision, still fails to make outbound calls returning the following error 603:

Call or Registration to [number]@(Ln.10000@Vitelity-L) has failed. [outbound_proxy_ip] replied: 603 Declined

Could you please hint us what the culprit would be and we’re supposed to fix it? All info required goes below.

Thanks!

3CX Version: Standard Annual 16.0.2.910
Server OS: Debian 9 v16.0.655
Is the 3CX Server Hosted: yes, Azure Cloud
IP Phone Make/Model/Firmware: Yealink T56A v58.85.0.5
Provisioning Method: SBC
Trunk Provider: Vitelity
Has the Firewall Checker passed: YES
Are custom Phone Templates being used: NO

 

[cobaltit]

Information to provide when requesting help | 3CX - Software Based VoIP IP PBX / PABX

And that error has nothing to do with the SBC. That's a clear rejection from VItelity which is who you should be contacting to ask why.

And I don't even want to know why you think the setup you describe is necessary.

 

[JohnS_3CX]

3CX Version: Standard Annual 16.0.2.910


This needs to be updated as soon as possible

 

[Leo_B]

Update to original post: yes, the problem was on SIP provider's side. Fixed the issue when added the second PBX public IP to Vitelity's provisioning list. Kudos for all who responded.