Found the issue and fixed it.

There were some extra entries in the default pjsip profile which were the culprit. The entries were there since quite a few versions back and hadn't caused any sort of issue with the trunks until we updated yesterday. Even after reverting to the previous working version, the trunks wouldn't get properly created until I found the extra entries and removed them. After that, the endpoints are created and the trunks are up once again.

@Romo said in Issues with remote PJSIP extension:

Same thing on Yealink SIP-T42S 66.84.0.80.

I'm out of easy ideas. I've been on site at a location all day.

Tagging @MontesVitalPBX

The benefit (to me) of setting this up like this means that your inbound routing is all just 10 digit numbers.
80b943b7-bc27-4b89-82a3-498dec52b007-image.png

We still have the error, but we did determine that it's just an error message and the clients can register fine. The registration issue was unrelated. So not a big deal, but it would be nice to know why we get this.

It's my first time running into it. Wondering if it might not be a corrupted client.

Been working with Yealink support on this and after confirming this happening with the T46G and the T42G phones, their support upped the severity and I got an answer back to add the below setting to the configuration files.

transfer.hang_up_after_success_trans = 3

I did so on the T46G, disabled the custom firewall rules, and had the operator repeat the transfer.

No ghost ringback.

I'll leave the custom firewall disabled and see if it stays good all day.

I'll test in more detail over the weekend or on Tuesday, whichever time I have a tech on site.