Plan a chan_sip to PJSIP migration
Migrate the behaviour of each account and route, not just its text. PJSIP divides responsibilities into objects that do not map to every old sip.conf line one for one.
Source-reviewed, 19 October 2026. Prepared from the cited documentation. No migration has been independently tested by Phone Guides. Scope: planning a move from legacy chan_sip into an Asterisk 22/PJSIP design; exact starting-version changes must also be reviewed.
Identify the supported target
The official Asterisk 21 change notes record removal of chan_sip. A target without that driver cannot use a plan that depends on leaving it loaded indefinitely.
The upstream migration guide contains historical coexistence examples. Read them in their release context. Do not turn an older Asterisk 12-era transition instruction into a promise about an Asterisk 22 installation.
Inventory the existing behaviour
For each phone, gateway and carrier, record authentication direction, registration direction, permitted source, inbound context, outbound destination format, codecs, DTMF, NAT/media handling, identity and encryption. Include subscriptions, transfer/pickup permissions, fax and integration dependencies where used.
Keep source configuration, installed versions and secrets in their approved private backup path. A public migration example must not contain real account credentials.
Map responsibilities into objects
| Responsibility | PJSIP object or decision |
|---|---|
| Protocol/address binding | Transport |
| Call policy and context | Endpoint |
| Inbound/outbound credentials | Appropriate auth object and linkage |
| Reachable destinations/contacts | AOR |
| Source-address identification | Identify object when that method is intended |
| Asterisk registers elsewhere | Outbound registration object |
Use PJSIP object relationships and the branch-22 reference for exact option semantics. Conversion output is a candidate for review, not evidence of equivalent behaviour.
Generate a review candidate
The upstream guide describes sip_to_pjsip.py as a basic converter that cannot cover every configuration. Asterisk 22.11.0 includes it under contrib/scripts/sip_to_pjsip/. Run it against a disposable copy of sip.conf and its complete include tree; keep the original files untouched. In the copied directory, name an explicit candidate output:
python3 /path/to/asterisk-22.11.0/contrib/scripts/sip_to_pjsip/sip_to_pjsip.py sip.conf pjsip-candidate.conf
The script can also write converted include files with a pjsip_ prefix. Review each generated file and include target. Inspect every comment or setting marked as not mapped, then compare the candidate with the actual PJSIP reference for the target release. Do not copy it over production configuration as a single cutover step. The tagged Asterisk 22.11.0 converter source and migration guide establish the tool's location and basic purpose; they do not establish that a generated result loads or preserves a particular service's policy.
Make a per-account review table before cutover: old setting or behaviour, intended PJSIP object/link, conversion result, remaining manual decision, and evidence needed. Include NAT/media, registration/contact limits, identity, codec/DTMF, TLS, dial strings, device-state references and each FreePBX or external system that owns configuration. A converter can produce plausible syntax while leaving an operational dependency unresolved.
Include dialplan and external owners
Find driver-specific dial strings, functions, device-state names and applications that construct channel names. Update only where the documented target semantics require it. A renamed channel reference can still carry an incorrect destination or permission.
If FreePBX owns the configuration, use its supported driver and account migration path. Do not replace generated configuration with raw examples; see configuration boundaries.
Prepare the cutover and reversal
List when registrations, provider destinations and routes change, who performs each change, and how the previous service is restored. Keep the prior compatible software/configuration pair recoverable. Reverting a file alone does not restore a removed driver or an incompatible database.
When checking the actual migration, cover registration, calls both ways, denied destinations, identity, two-way audio, digits, hold/transfer, voicemail and required features. State any unchecked paths explicitly. Preserve source and target versions with each result.
Return to Asterisk documentation.