Use the offered authentication action on the intended SIP line when you need to move from trusted-IP calling back to username/password authentication. This changes how that SIP identity connects. It does not change your Portal login password or leave both authentication modes active in parallel.
These instructions follow the Android app version 1.0.46, build 272. Available actions depend on your account permissions and current service state. Other installed versions may present different controls.
1. Prepare the connected equipment
- Identify the SIP line and every PBX or endpoint currently relying on its IP authentication.
- Schedule the change when it will not interrupt active customer work.
- Have access to the endpoint configuration and a secure place to handle the resulting credentials.
- Record the current line identity and mode without copying secrets into a support ticket.
An IP-authenticated PBX may stop working after the mode changes until it is configured for password authentication. Do not switch just to troubleshoot a single failed destination; first establish that changing authentication is the intended solution.
2. Open the line’s authentication action
In the app’s SIP-line management screen, open the intended line’s menu and choose the offered switch-to-password-authentication action. Check the identity and current mode again. If the line is already password-authenticated, do not confuse a password reset with a mode transition.
The action is permission- and state-dependent. If it is absent or unavailable, use the account administrator or Support rather than modifying a server ACL or trying an unlisted endpoint. A visible SIP identity does not give every user authority to change its authentication.
3. Confirm the sensitive change
- Read the mode-change confirmation and choose Apply only for the intended line.
- Complete the app’s identity confirmation when requested.
- Submit once and wait for the result.
- Allow the line list and phone state to refresh.
Canceling the identity confirmation should leave the change unapplied. Do not give another person your verification code or password to finish the screen. This sensitive-action proof is separate from the SIP credentials later used by your phone or PBX.
4. Reopen the line and verify the mode
Confirm that the saved line now shows password authentication. If the response was interrupted, inspect this current state before retrying. A progress message alone does not establish completion, and repeated transitions are not a safe way to recover an uncertain response.
Use the offered credential-view workflow with its own identity confirmation to obtain the current connection details privately. Do not assume an old SIP password is still the correct credential. Keep the exact SIP username, password and server/transport settings together; the account email is not a substitute for a SIP username.
5. Update and test the endpoint
- Configure the connected phone or PBX using the current password-authentication details and its model-specific guide.
- Remove conflicting assumptions from its former IP-authenticated setup through the supported endpoint controls.
- Check registration or the documented authentication state.
- Arrange an authorized outbound test and verify the permitted caller ID and two-way audio.
- If the line receives incoming calls, check its existing incoming route separately.
A mode change does not assign incoming phone numbers or alter every destination’s caller-ID eligibility. Do not place repeated paid test calls while registration is failing. Inspect the actual authentication error and current credentials first.
If the result is unclear
Provide Support the SIP-line reference, transition time, saved mode and sanitized error. Explain which endpoint used the old IP-based configuration. Keep credentials and verification codes out of screenshots. If the product reports an inconsistent or restricted state, ask for review rather than trying to recreate the SIP identity.
Related guides
Reviewed 13 October 2026 against the current IllyVoIP controls, implementation and applicable references. Available options depend on account permissions and service state.