Solved Custom SIP port doesn't accepted by the provider

[apitsos]

Hi there!

I am having an issue with a new installation. I configured my 3CX with a custom SIP port and that seems to come in conflict with the provider (WIND Greece). They can provide a SIP Trunk ONLY on port 5060. I thought that this is irrelevant with the configuration I have done, because I had the feeling that the "custom" SIP port is only for the extensions. But checking with Wireshark we see that the source port on the INVITE message in an outgoing call is my custom port and not the 5060.

Also the incoming requests by the provider are directed to port 5060, but 3CX seems to ignore them.

Any ideas about that?

In addition, is there any possibility to change the SIP port? I know that as soon as you configure you can't (officially) change it, but it may be possible to alter a file. This is a Windows installation.


Kind regards,
Angelos Pitsos

 

[ChrisC_3CX]

First off, I'd recommend confirming what the SIP Port configured for this 3CX Instance is by navigating to Settings >> Network >> Ports. This is the source port used by your 3CX PBX so it normally should not matter for providers. However, since this is not a 3CX Supported provider we are talking about I cannot be certain if this is the case or not. I do recommend considering switching to a 3CX Supported provider for guaranteed compatibility and for a more trouble free experience: https://www.3cx.com/partners/sip-trunks/

If you do need to change the SIP Port, you will have to re-install, changing any configuration files, parameters, or anything else to achieve this on a running system is not recommended and will most definitely cause issues.

 

[apitsos]

Hi Chris,

Thanks a lot for the clarifications. I had to reinstall the 3CX and configure the SIP port as 5060. Then everything worked like a charm.

I have to admit that I didn't want it. I prefer the SIP port to be customized. But there was no other solution in that case.


With kind regards,
Angelos Pitsos

 

[ChrisC_3CX]

Great, glad to hear you resolved this! Well yeah I'm afraid that there's not much you can do if it is a SIP Provider's requirement other than switching to another one that does not have these kinds of limitations.