I agree: I incorrectly typed pjsip send registration while I should have typed pjsip send register.
Sorry for this.
On another hand, the issue I see is while doing I don’t see anything “sent over the wire” nor any error message displayed on screen: the only trace of something happening is a mysterious “(exp 17s)” implying something was done 17s ago.
In my testing, I added a “outbound_proxy=126.96.36.199:5060” line in my registration section. Removing it changed the whole result as my trunk could at last come up.
The point, IMHO, is that if anything prevent a REGISTER message to be sent, it should trigger some logging.
It normally does. I don’t know why it wouldn’t in your particular scenario, unless it’s some internal PJSIP thing that didn’t bubble up to Asterisk or produce a log message. Did you check the past log to see if something did come up?
It queues the REGISTER command. So no direct error should be visible. Does it generate the message “Re-register all queued” for you?
On another terminal I use sngrep to see if the register is really done and I see here it works. You could also enable debugging to see if the re-register is done. Otherwise there should be an entry in the logs.