Hello.
Dne 21.7.2015 v 04:47 Emmanuel Lepage napsal(a):
As for the "as a server" message, it is misleading. Any bidirectional TLS communication
have 2 sides. In this case, it just tell the SFLphone need to validate the certificate of incoming
connection on its open port. If a communication is established from the "SIP server" to
you, then you are the server.
Just a Note FYI. I'm afraid it is not so.
If VoIP provider is used, then SFL is always in TLS client role.
The server do not initiate connection to SFL opened port.
The INVITE comes over established TLS/TCP connection (keeped
alive) which was initialised from SFL in client role.
SFL in server role (listening on port) is rare used only for
direct PC2PC calls - without SIP server/provider.
SIP provider is necessary today e.g. for NAT traversal (for
symmetric NAT do not help even STUN helper), for PSTN/GSM gateway, ...
--kapetr
_______________________________________________
SFLphone mailing list
[email protected]
https://lists.savoirfairelinux.net/mailman/listinfo/sflphone
