incoming phone don't work always

[Francisco_javier]

I have a sonicwall TZ210 as firewall and work with provider 3starsnet Belgium and 3CX run on a XP workstation.

To call internal and external someone , no problem.
To receive a call , if the destination port is 5060 than I receive the call, else the call is lost.
Can y tell to 3CX to force to use the destination port 5060?.

Thanks

 

[leejor]

I'm a bit confused. What device do you wish to change the port on?

When a SIP device (including 3CX) registers with a server, it tells the server what port it want to "receive" on. That port number, in almost all cases, can be set to a port number that will work (won't cause conflicts).

 

[willow]

Just about all SIP providers use 5060 for the SIP port. If you want to use a different port then your in for a rough time. all phones and servers and providors use 5060 so to change it will be a tremendous task.

 

[Francisco_javier]

My question was,

If a monitor a incoming call on my sonicwall, the source port is always 5060 but the destination port is sometimes other than 5060, for example 11474.

If the destination port is different then 5060 the incoming call is not working.

Who change or with unit give the destination port, the firewall (sonicwall TZ210 in my case) or the 3CX soft,

If it is the 3CX software is it possible to fix the destination port to have always 5060.


Thanks

 

[netswork]

The destination port should be 5060. The source port could vary. If your seeing different destination ports from inbound calls from your VOIP provider you should contact them with your logs and see what they say. Have you tried sniffing on the outside of the sonicwall to verify what your seeing in your sonicwall logs? Outbound traffic via NAT will always grab a random high number port, but the inbound traffic from your voip provider to your 3cx should always be 5060.

 

[willow]

on the sonicwall under the voip tab make sure to enable constant nat and disable sip transformations.