What settings need to change to convert chan_sip to chan_pjsip?

I am trying to work with my provider to stabilize the cookbook for pjsip settings on his network.

Our current chan_sip settings are:

OUTGOING:
Trunk Name: SIPproviderNAME
host=sip.providername.com
user=NPANXXXXXX
authuser=NPANXXXXXX
username=NPANXXXXXX
secret=assigned by provider
type=peer
qualify=yes
insecure=very
dtmfmode=rfc2833
auth=md5

INCOMING:
User Context: NPANXXXXXX
type=user
context=from-trunk

Registry String: NPANXXXXXX:secret:[email protected]:listenport/NPANXXXXXX

What needs to change?

so I would fill in the fields in he pjsip trunk pages

then turn off sip and set pjsip to use port 5060.

Something is very strange here: I assume that listenport is a ‘secret’ port other than 5060; otherwise you would not have redacted it. But to send calls to that port, you would also need a ‘port=listenport’ entry in the outgoing config, unless the provider somehow uses port 5060 for calls but another port for registration. I’ve never heard of that.

Yes, OK, it is 5060. . . BUT
To avoid admonishment from Dicko I omitted that part.
We have the firewall configured to allow only the provider to use that port.

Still no changes necessary otherwise?

I am sorry for taking this off topic but this was extremely funny to me. @dicko got everyone here scared to u̶s̶e̶ admit to using UDP 5060 for their SIP signaling.

Have you looked a PJSIP trunk configuration and tried to match up settings from your SIP trunk to fields in the PJSIP trunk settings?

Username: NPANXXXXXX
Secret: (as supplied by provider)
SIP Server: sip.providername.com
Contact User: NPANXXXXXX
From Domain: sip.providername.com (may not be needed but shouldn’t hurt)
From User: NPANXXXXXX (unless provider allows sending other caller IDs in From)

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.