Sten, I see. Adressing this on the client sounds to me as not being ideal. You could solve this server side with star codes based logins, for example, as it is often done for call centres in Asterisk. A user logging in to a new computer could have as part of the login procedure a script calling the Linphone CLI with a login starcode that will set that device as the currently active one.
Germán Sent from a mobile device On 10 Mar 2021, at 07:30, Sten Kultakangas <[email protected]> wrote: Hi German The Linphone is configured with auto-answer, so max_contacts=1 and remove_existing=yes (in the case of the asterisk) is the only viable solution. Otherwise multiple Linphone instances with the same username/password would be competing for answering the call first. Ideal solution would be implementing Linphone customization which would handle a NOTIFY with the Event: registered-elsewhere header. Asterisk would send such message to the previously registered Linphone and Linphone's UI would enter the state indicating that parallel login with the same username/password has been detected elsewhere. Best regards, Sten On Wed, 10 Mar 2021, 00:41 German Cancio, <[email protected]<mailto:[email protected]>> wrote: Sten, You likely have a server-side setup or configuration problem as the contact information for each device should be different (different IP’s, different ports). When configured correctly, a SIP server like Asterisk will forward an INVITE to all contacts that are registered for a given SIP username / number. Germán On 9 Mar 2021, at 15:40, Sten Kultakangas <[email protected]<mailto:[email protected]>> wrote: Hi I'm having an issue with the users who start Linphone at one computer and forget to logout from Windows. Then they login to another computer and start the Linphone there. Both Linphone instances are then competing for SIP registration leaving the other instance non-operational until the scheduled attempt to refresh the replaced registration. Is there a way to make Linphone stop further registration attempts ? One admittedly hackish way is to make Linphone crash by sending an INVITE/UPDATE message related to an established call with a specially crafted Contact header containing the "isfocus" parameter as described here https://github.com/BelledonneCommunications/linphone-desktop/issues/475 However, this will only work if the server were able to place a call to a replaced contact which would require a lot of customization to the server code. Best regards, Sten Kultakangas _______________________________________________ Linphone-users mailing list [email protected]<mailto:[email protected]> https://lists.nongnu.org/mailman/listinfo/linphone-users _______________________________________________ Linphone-users mailing list [email protected]<mailto:[email protected]> https://lists.nongnu.org/mailman/listinfo/linphone-users _______________________________________________ Linphone-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/linphone-users
_______________________________________________ Linphone-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/linphone-users
