dslepnev Posted September 10, 2009 Report Posted September 10, 2009 Hello, Fom time to time we hear from customers that they have a problems with NAT traversal (no audio in both or one direction). To solve this problem we recommend to use STUN servers with pbxnsip. In most cases it helps. Questions is: have pbxnsip any plans to implement STUN inside the pbxnsip code? It's will be very useful, and from my point of vew will not take a long time for development... Quote
Vodia PBX Posted September 14, 2009 Report Posted September 14, 2009 Fom time to time we hear from customers that they have a problems with NAT traversal (no audio in both or one direction). To solve this problem we recommend to use STUN servers with pbxnsip. In most cases it helps. Questions is: have pbxnsip any plans to implement STUN inside the pbxnsip code? It's will be very useful, and from my point of vew will not take a long time for development... In the SIP world, STUN today is used essentially for outbound and ICE. In the old times, vendors believed that STUN would help overcome the problems with NAT. But it soon became clear that it makes support very difficult. There are so many different NAT implementations out there that a vendor better assums the worst case, where STUN must be sent to the exact address and port of the SIP server. That is exactly what outbound is doing. That does solve the issues with the SIP signalling traffic. For media, ICE is useful if you want to establish a direct path between the communication endpoints. Because the PBX is a media-aware application there is no point for ICE on the PBX (at least not for calls from extensions). ICE might become interesting for trunks, when OCS-based installations are mainstream. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.