Are you logging in, in SIP mode, or H.323?
If SIP mode, make sure you have enough registrations allowed in your user profile. If you plan on using the phone and softphone at the same time, you may need to increase it to 2 (or more). You can do this on the user profile in System Manager.
If you are directly registering to the Session Managers, make sure the hostnames you provide in your 46xxsettings.txt file match EXACTLY what Session Manager wants to use. I'm sure there is an easier way, but to find the hostnames that ASM wants to use, open up OpenSSL, and do the following command :
opensssl s_client -connect <your ip>:5061 -showcerts
You should see a cert in the list that is targeted to a particular hostname that ASM wants to see. For example, the hostname I gave my session manager was "msu-sip-1.domain" and the hostname that it WANTED to see was "msu-sip-1-sm100.domain"
Once you have the hostname, you will want to update the 46xxsettings.txt file's SET SIP_CONTROLLER_LIST entry to match that setting. You can also look at the SET FQDN_IP_MAP option as well. I've found you had to update both.
What is happening in this case, is your phone will connect to the server and register. It eventually pulls down the PPM payload, which includes the server list that ASM wants the phone to connect to (the server list included in the security certs). Eventually the phone will try to connect to those hostnames IN ADDITION to the ones you told it to connect to. When it sends a REGISTER event to the same server (on the other hostname), the server will throw a message on the FIRST connection saying that something is connecting on the same IP/PORT, and the phone will show the error.
If you run the connections through the SBCE, it is smart enough to fix this up for you and eliminate the weird hostnames in PPM.
------------------------------
Nick Kwiatkowski
Director of Design and Engineering
Michigan State University
East Lansing MI
------------------------------
Original Message:
Sent: 12-04-2020 03:25 PM
From: Sean Yates
Subject: IX Workplace for desktop
We have recently installed IX Workplace on desktops and are getting a lot of users getting logged out with a message "someone else has logged in with your extension". There seems to be no evidence of that, though. Is there some timer where the desk phone takes over the login?
------------------------------
Sean Yates
Telecom Engineer
Milwaukee County
------------------------------