no audio sip stun

Status
Not open for further replies.

Hostname

SOHO User
Joined
May 5, 2021
Messages
49
Reaction score
5
Hello i have provisionned my phones yealink t46u and t30p via sip stun
the problem is in my desk phone i can hear but from the app cannot hear even on the firewall the service is all
 
I just wanna know why its telling me
Sun discovery of public ip is disable
 
I just wanna know why its telling me
Sun discovery of public ip is disable
It's your network, so you should have an idea of what devices are on it. One of them seems to be telling you that an option is disabled. Whether this is the cause of the problems, I can't be certain.

However, when using STUN, if a device is unable to "discover" the public IP, of the router it is behind, then it may use the private IP assigned to it, when communicating with 3CX. Devices themselves usually don't complain about this, as they are not aware of what IP they should be using, they assume you have set the options correctly. This can lead to 3CX using a private IP, to communicate with the remote device, which, of course, won't work. You might check the 3CX Activity Log to see what IP and port, each device is using to register.
 
  • Like
Reactions: NickD_3CX
1 For remote phone using sip stun i need to change the range rtp port for every one of the ip phones and port forward them to they private ip for rtp works ?
2 if i want to change the method of provisionnnig (for example remote SBC ) there is any port forward i have to do for the firewall in front of sbc ?
 
1 For remote phone using sip stun i need to change the range rtp port for every one of the ip phones and port forward them to they private ip for rtp works ?
That is correct. If you have multiple STUN IP Phones at the same remote location behind the same Public IP, each one must have a unique SIP port and RTP Port range usually of at least 12 ports (some phones require more, check guides)

2 if i want to change the method of provisionnnig (for example remote SBC ) there is any port forward i have to do for the firewall in front of sbc ?
When switching Provisioning Method, it's best to Factory Reset the IP Phone to remove any residual settings that may stay behind.
No, no port forwarding is requires though.
 
  • Like
Reactions: Evolute IT
When switching Provisioning Method, it's best to Factory Reset the IP Phone to remove any residual settings that may stay behind.
No, no port forwarding is requires though.
In the 3cx session border conTroller i need to put the public ip of the sbc ?
However there is no port forwarding
 

Attachments

  • Screenshot_20220515-143656.jpg
    Screenshot_20220515-143656.jpg
    280 KB · Views: 5
The LAN IP of the SBC goes in that field.

But if you assign the IP Phone to an Extension from the "Phones" node in the Management Console after you factory reset it, it will fill this field in automatically, assuming of course that you have the SBC already setup on the LAN the phone is.
 
The LAN IP of the SBC goes in that field.

But if you assign the IP Phone to an Extension from the "Phones" node in the Management Console after you factory reset it, it will fill this field in automatically, assuming of course that you have the SBC already setup on the LAN the phone is.
Okey i will try that then i will told, and rtp how it work in sbc ?
 
Okey i will try that then i will told, and rtp how it work in sbc ?
The phone sends all it's traffic to the SBC and the SBC sends to the server. All NAT issues is avoided as the SBC makes outbound connection to 3CX so upstream devices typically carry that state through and return traffic is delivered to the SBC.
 
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,083
Members
164,900
Latest member
Silent_Guru