> New description: > When QuteCom is started with -s (several) switch, all instances try to > bind to the same SIP port number. This results in all but the first > instance can't connect, and report the following error to the console: > > (error) 14:01:46 [PhApi] : osip: > qutecom-2.2-r639/wifo/eXosip/src/eXosip.c:580: eXosip: TCP > transport_listen failed! > (error) 14:01:46 [PhApi] : eXosip_init failed > -- > > Comment(by chris-mac): > > With this patch it is possible to start two instances of QuteCom, but both > are binding to the same port number??? See netstat output below:
Binding to the same number means that they cannot be used for different VoIP accounts (at least simultaneously). I might be wrong here, but the SIP RFC's does allow for multiple clients to register with the same account (so that both your office and home phones ring at the same time when someone calls you), but what is the purpose of having two instances of the client binding to the same port? Someone more knowledgeable might want to clue me in. It might be better to have a -p command line option and/or a corresponding XML config option and set the port explicitly. So far only the sip registrar's and sip proxy's UDP ports are configurable. Also, using the first available UDP port (5061), after the default SIP port 5060, when someone uses the -s option might be problematic, as 5061 is used by SRTP (service SIP-TLS). Source: http://www.iana.org/assignments/port-numbers I sugggest that the application's UDP port be user settable (and the following port be used for SRTP, if the user opts for that). _______________________________________________ QuteCom-dev mailing list [email protected] http://lists.qutecom.org/mailman/listinfo/qutecom-dev
