Closed GoogleCodeExporter closed 9 years ago
STUN feature is not related to your sip provider.
Many sip providers provides on the same server a registrar and a stun server.
But in fact that's two different features !
Even better, you can use a stun server from one provider to resolve your public
ip for any account. (you should probably read that :
http://fr.wikipedia.org/wiki/Simple_Traversal_of_UDP_through_NATs as a starting
point to understand why stun is not related to an account).
Besides, for now csipsimple only support 1 stun server, but that's just a user
interface limitation since the sip stack on which we rely support multiple stun
server. Anyway, when we will support many stun server, for all your account,
the first stun server will be asked, if he don't respond then the second stun
server will be tried etc. So, that definitely not linked to the account and
once one stun server resolve you, all the sip stack will share your public ip
information between all accounts.
For you UDP port issue, you are probably confusing between the local bind
transport port (the one available on the general settings) and the remote
registrar server port, that can be configured using the expert wizard (that
make sense since most providers listen to 5060).
So if you are just a mainstream user,
* use Basic account creation (or the wizard of your provider - in the feature I hope that we will have a bigger list).
* You can then configure STUN (if the provider wizard has not already done that for you... for now no wizard take it in charge but should be done in the future). To do so, you use the general settings since this is a feature that can be shared by all your accounts.
If you want some extra stuff to configure your account then you can use the
expert account, but you must know what mean each field.
For now I concede that the settings interface is a little bit confusing since I
mix settings for expert and settings for mainstream users. But I'll rework that
part soon (remember that's still an alpha ;) )
Original comment by r3gis...@gmail.com
on 2 Sep 2010 at 7:46
Original issue reported on code.google.com by
baumi1...@gmail.com
on 2 Sep 2010 at 6:25