When to use managed mode
Use managed mode when:
- Your PBX grants short registrations.
- You want to ring all of a user’s devices from pgw, with one contact at the PBX.
- Your apps sign in with a token instead of a SIP password.
How managed mode works
Example Corp moves user1001 to managed mode. It gives pgw the password for 1001, which pgw stores encrypted. From then on, the app’s registration with pgw and pgw’s registration at the PBX are separate:
- The app registers with pgw. pgw sends the digest challenge itself and checks the answer against the stored password. The app uses the same username and password as before.
- pgw registers at the PBX. It sends its own REGISTER, with its own address as the contact and the stored password. The PBX never sees the app’s push token.
- pgw keeps renewing. It renews before each grant from the PBX expires, however short the grant is. The app isn’t involved.
One contact for each user, or one for each device
By default, pgw registers one contact at the PBX for each user, however many devices the user has. When a call arrives, pgw rings all of the user’s devices at once, and the first one to answer takes the call.
Use
per_user unless a feature of your PBX must act on a single device. To change it, see Set up managed mode.
When pgw removes a device
In managed mode, a registration no longer expires on its own, so pgw decides when a device is gone:
The user and the stored password stay. A removed device comes back the next time its app registers.
Settings
Next steps
Set up managed mode
Create a managed upstream and add its users.
Sign in with a Bearer token
Let apps register with a token from your sign-in service.
Kamailio user source
Read the users from Kamailio’s database.