If you use chan_sip extensions without a SIP secret, they should work for you.
Until now, I had never tested a pjsip extension without a SIP secret, and I see the same thing. FreePBX generates an auth line for the endpoint even tho the secret is null, which causes the call to fail. Removing the auth line from the endpoint definition resolves this, but it’s not easily done by the end user. Since there are a non-zero quantity of SIP endpoints that don’t support authorization, so you may want to file a feature request for pjsip to support this.
I managed to do it by deleting the auth-part in the pjsip.endpoint.conf file.
I think this is really bad practice because it gets overwritten whenever I press the “Reload Config” button on the web interface.
I hope somebody knows a better way. the CHAN_SIP possibility did not work.
What goes wrong? Did you remember to have the device send to port 5160 (or whatever you have bind port set to)?
Set up your device as a pjsip trunk w/no registration or authentication. You’ll be able to make and receive calls, but you won’t have voicemail, follow-me, forwarding, DND, etc. What kind of device is this? A trunk might be more suitable.
Set it up as a custom extension and put the config in the pjsip custom config files.
Possibly, you can modify the existing config as shown in
I now managed to switch CHAN_SIP to port 5060 now and configurated my extensions from PJSIP to CHAN_SIP.
I am actually able to call FROM the devices now. But I can’t call TO them.
I always get “503 service unavailable” with reason “Subscriber absent”. Do you know how I can fix that?