Solved Multiple Cisco VoIP phone / ports forwarding

[AndWei]

Hello!

Somehow I'm blocked right now and maybe have a wrong approach.... following problem:

3CX system set up a few days ago and tested a little. runs so far wonderfully. 3CX app for making calls also works. Also a Cisco 525g2 was quickly set up. However, it only registers when I enable port 5060 in the router and forward it to the phone. Ok and kind of logical.
The current problem... how do I get a second, third Cisco phone to run, because the port 5060 was already linked to the first phone!?

Thanks for any tips and help, because right now I'm a bit "confused"!

 

[Evolute IT]

Hello!

Somehow I'm blocked right now and maybe have a wrong approach.... following problem:

3CX system set up a few days ago and tested a little. runs so far wonderfully. 3CX app for making calls also works. Also a Cisco 525g2 was quickly set up. However, it only registers when I enable port 5060 in the router and forward it to the phone. Ok and kind of logical.
The current problem... how do I get a second, third Cisco phone to run, because the port 5060 was already linked to the first phone!?

Thanks for any tips and help, because right now I'm a bit "confused"!

In STUN mode, each phone must have a separate SIP and RTP port range, as well as a static IP/DHCP reservation so that you can forward those ports to each phones respectively.

The SBC would fix all that and prevent any port forwarding.

 

[AndWei]

In STUN mode, each phone must have a separate SIP and RTP port range, as well as a static IP/DHCP reservation so that you can forward those ports to each phones respectively.

The SBC would fix all that and prevent any port forwarding.

Hello Frederick!

Thank you ver much for you for your answer and explanation.

According to instructions (https://www.3cx.com/sip-phones/cisco-spa/#h.bge13mhpeyf3):

Limitations
Note that these phones can not be used from a remote location or in combination with a 3CX in the cloud.

Known limitations of Cisco SPA 302, 303, 501G, 502G, 504G, 508G, 509G, 512G, 514G, 525G, 525G2 are:

No PnP Support
No STUN Support
No SBC Support
No Full CTI Support (Make Call Only)
BLF Functionality (only on applicable models)
Company Phone Book with limited size only
Manual DST Support

The only port that works and does not seem to be changeable in the 3CX configuration is port 5060.

I think that simply settles the issue of 3CX in the cloud. :-(


Have a nice day and stay healthy...

 

[Evolute IT]

Hello Frederick!

Thank you ver much for you for your answer and explanation.

According to instructions (https://www.3cx.com/sip-phones/cisco-spa/#h.bge13mhpeyf3):


The only port that works and does not seem to be changeable in the 3CX configuration is port 5060.

I think that simply settles the issue of 3CX in the cloud. :-(


Have a nice day and stay healthy...

Well, those phones are very old and indeed, if the page says "No STUN", it won't work. They don't even support the SBC, which is a bit surprising to me but anyway.

I recommend going VPN or host the PBX on-prem, or even better: get better phones that are fully supported!

 

[AndWei]

Well, those phones are very old and indeed...

Sorry, but this is really total nonsense. About two years after the first version of 3CX, the Cisco 525G2 was released. It's ok if 3CX is interested in marketing the cruel Fanvil phones, but to think that the software has to dictate which hardware to use is absolutely not up to date and bulls***. Especially when after about 13 years, only about a dozen phones are officially supported.

...or even better: get better phones that are fully supported!

No, even much better would be to bring the software to a level that you can customize the way you need it and not that you have to adapt to the software.

But all no problem, there are other solutions... ! ;-)

 

[cobaltit]

So you want 3CX to bend over backwards to support a phone that is EOL'd by the manufacturer? Yeah I'd rather them focus on something made in this decade.

And 3CX is not dictating what hardware to use. They are dictating what hardware is supported. Just because YOU can't support the Cisco phone and make it work is not 3CX's fault. Other people have made them work. Just about any SIP compliant device can be made to work and has been made to work with 3CX.

 

[AndWei]

So you want 3CX to bend over backwards to support a phone that is EOL'd by the manufacturer? Yeah I'd rather them focus on something made in this decade.

And 3CX is not dictating what hardware to use. They are dictating what hardware is supported. Just because YOU can't support the Cisco phone and make it work is not 3CX's fault. Other people have made them work. Just about any SIP compliant device can be made to work and has been made to work with 3CX.

Well, except for infantile comments, they probably haven't needed anything to run yet. You forgot the 3CX Fanboy Certified button below the post. ;-)

 

[Evolute IT]

Well, except for infantile comments, they probably haven't needed anything to run yet. You forgot the 3CX Fanboy Certified button below the post. ;-)

No one forces you to use 3CX. Plenty of other software where you can do whatever you want and nobody will care.

As for 3CX, they care about their customers and the experience of using the software. So, if a manufacturer is not interested in getting the hardware to a certain level, why would 3CX bend themselves? They make a PBX, not phones.

Now, as for your attitude, I can tell you for a fact that no one here will help you if you keep it this way.

 

[leejor]

The SPA525g does support STUN, and each line can, and should be set to use a different local SIP port. And, you may have to forward those ports to the appropriate local IP of each device.

The only port that works and does not seem to be changeable in the 3CX configuration is port 5060.

No, you normally would not change port 5060 at the PBX end, but you can at the set end, and each extension, behind a router, using STUN. should be using a unique local SIP port.

https://www.3cx.com/community/threads/stun.65555/

If using more than a couple of sets, and depending on your router, you may also have to forward certain audio ports to each set as well. You may also find it necessary to enable the PBX Delivers Audio option on each STUN extension, which may "fix" no, or one way audio issues.
If you are installing a number of sets, at one location, you may find it much easier to install an inexpensive Raspberry Pi 3CX SBC rather than mucking about (pseudo technical term) with STUN.

You may have to resort to manually configuring the sets.

 

[AndWei]

The SPA525g does support STUN, and each line can, and should be set to use a different local SIP port. And, you may have to forward those ports to the appropriate local IP of each device.




No, you normally would not change port 5060 at the PBX end, but you can at the set end, and each extension, behind a router, using STUN. should be using a unique local SIP port.

https://www.3cx.com/community/threads/stun.65555/

If using more than a couple of sets, and depending on your router, you may also have to forward certain audio ports to each set as well. You may also find it necessary to enable the PBX Delivers Audio option on each STUN extension, which may "fix" no, or one way audio issues.
If you are installing a number of sets, at one location, you may find it much easier to install an inexpensive raspberry Pi 3CX SBC rather than mucking about (pseudo technical term) with STUN.

You may have to resort to manually configuring the sets.

Thank you for your post. It was really helpful. Now everything works... Thank you!

 

[leejor]

The 525G is a great set, with lots of features, but, like with many pieces of hardware that are no longer made, not enough are in use, to justify continuing to support it. The fact that it has a GUI, rather than requiring the download of a configuration file, means , for those who are familiar with SIP, it can be made to work with just about any SIP PBX, or provider. And the bonus.... the price keeps dropping on used sets, as people replace them