FreePBX chan_sip to pjsip question


(Jeff Brubaker) #1

Hello,
I recently upgrade my FreePBX 13 to 15 and so far it’s been working pretty good. Not knowing a lot about it, I’ve read often that I should be using pjsip instead of chan_sip.

How important is it to change?

Is it as easy as enabling pjsip in the advanced settings menu and then going in to each extension and changing it over or is there something else I need to do?

Thanks!


(Itzik) #2

It’s important you understand PJSIP, so when you’ll be forced to switch you won’t be stuck.


#3

It is important to also understand that if you switch an extension from chan_sip to chan_pjsip, you will also need to inform the remote extensions that they will need to register against a different port :-).

Couple of work arounds, have your router redirect the chan_sip port to the chan_pjsip port (I think @jerrm to thank for that) but that needs you to globally update all extensions. Trunks also might need attention.

You could also switch the chan_sip and chan_pjsip ports , also globally updating all your extensions.


(xp) #4

New tool to assist converting from SIP to PJSIP | FreePBX - Let Freedom Ring

The tools is great - but please know that it does NOT move the SRTP or the Call Waiting status. We simply export the extensions when starting, and they are still on ChanSIP, using bulk export, then migrate to PJSIP using the tool, then bulk export the newly migrated PJSIP extensions, and now update based upon the ChanSip bulk export of who si SRTP and who has what call wait setting, then reimport with the correct variables and you are done. Please do note the variable names and options are slightly different for SRTP between ChanSIP and PJSIP.

After you figure out one PBX, the rest come easy.

Also, before we start we go to Advanced | SIP Channel Driver and set it to both. After the migration to PJSIP we set it to ONLY PJSIP. We modify the Server SIP Ports under Asterisk SIP Server Settings to have the PJSIP listen on the exact same ports as the ChanSIP - this way no change at the actual phone extension is required. Do not forget to recreate trunks that are PJSIP and delete the ChanSIP ports. Also do not forget you need to command line and issue an fwconsole stop, and then fwconsole start (I have had instances where the fwconsole stop and start does not work right, a reboot cured this).

After doing this, you now are on only PJSIP - which is the only support standard moving forward.

We have done this to over 60 PBXes with great success.


(Jeff Brubaker) #5

Thanks!
So a little more complicated than I expected. But now on the radar to complete this.


(Jeff Brubaker) #6

Is there any kind of “Convert chan_sip to pjsip for dummies” guide out there?


(Kapil Gupta) #7

Hi Jeff

The below blog post should help you to start with.

Regards
Kapil


(Jeff Brubaker) #8

Thanks for the info! Just a couple questions…

In addition to the article you sent, one of the comments listed above states:
“but please know that it does NOT move the SRTP or the Call Waiting status”
So how do I fix that?

And the other comment:
"if you switch an extension from chan_sip to chan_pjsip, you will also need to inform the remote extensions that they will need to register against a different port.
Do you just change the port number on the extension?