Use the SIP line’s Change password action to replace its calling credential, then update every device that uses that line. This is different from changing the password used to sign in to the IllyVoIP Portal. Begin with the exact line so you do not disconnect an unrelated phone or PBX.
1. Prepare the device cutover
- Sign in as the account owner and open SIP Lines. Identify the intended password-authenticated line using its label and SIP identity.
- List the phones, PBX trunks and other supported devices that use this credential. Decide who will update each one.
- Finish active calls where practical and choose a suitable maintenance window. Keep Portal access available while devices reconnect.
- Preserve the existing device configuration securely so host, transport, media and routing settings can remain consistent during the password change.
Do not rotate a password to repair a browser-tab ownership message or an unrelated incoming-number destination. If the line uses IP authentication or its authentication state needs review, address that state through the appropriate workflow first. A password change is not a substitute for converting authentication modes.
2. Change the credential for the intended line
- Open the line’s actions and choose Change password.
- Read the confirmation warning to apply the new password in all devices. Although the dialog can use the wording “Change Account Password,” this action is attached to the selected SIP line; check the line before confirming.
- Confirm only when ready to replace that calling credential. Wait for the result instead of pressing the action repeatedly.
- Use the returned new SIP password and store it privately in your approved credential store. Keep it out of tickets, screenshots, chat messages and ordinary logs.
If the response is lost, inspect the line’s current credential through its authorized credential-view workflow before deciding to rotate again. A second rotation can immediately make the first newly copied value obsolete. Complete any identity confirmation that the credential-view interface actually requests; do not bypass protected reveal controls.
3. Update all dependent devices
- On each intended device, replace the password in the authentication-password field for this IllyVoIP identity. Keep the correct SIP username and account endpoints.
- Save or apply the device configuration according to its supported instructions. Allow its calling connection to refresh.
- Check registration or the device’s equivalent connection state. If it fails, verify the selected account, exact username, password and any accidental whitespace before changing other settings.
- Repeat for the remaining devices on your cutover list. Retire obsolete local copies according to your credential-handling procedure.
A device can continue displaying a cached connection state for a time. Do not infer that the old password remains valid from a screen that has not refreshed. Equally, do not promise that rotation forcibly terminates every existing call or registration immediately; credential replacement and existing-session lifetime are separate concerns.
4. Verify the calling paths you use
- Confirm that each intended device has refreshed its connection successfully.
- With authorization, check an outgoing call using the expected caller ID and confirm two-way audio. Normal charges can apply.
- If the line receives incoming calls, check the associated number’s saved destination and the intended receiving device separately.
- Record completion for each device so an old credential on one forgotten handset does not become a recurring fault later.
If the device still cannot connect
Read the actual error before rotating again. A wrong credential, unavailable line, network problem and unsupported media configuration require different checks. If another administrator may have changed the same line, compare the current authorized credential state before troubleshooting a stale copy.
For Support, provide the SIP line reference, device model and software version, change time and sanitized error. Never provide the password itself. If the rotation was prompted by suspected exposure, also review the affected devices and account access through the normal security workflow; replacing one SIP password does not revoke unrelated Portal sessions or API keys.
Related guides
- How to create SIP & Agents accounts
- How to Reset Your Password
- Rotate an IllyVoIP API key without losing track of integrations
Reviewed 12 October 2026 against the current IllyVoIP controls, implementation and applicable references. Available options depend on account permissions and service state.