Hi, AFAIK PJSIP is supposed to implement RFC 5626 "Managing
Client-Initiated Connections" (AKA "Outbound" spec).

If this feature is not implemented in the version of PJSIP used within
CSipSimple or Blink softphones, then please tell it to me and just
ignore the rest of the mail :)

Using CSipSimple r944 I see a REGISTER like this (ommiting some headers):

REGISTER sip:domain.net SIP/2.0
Contact: "Alice"<sip:ibc@192.168.1.13:60461;transport=TCP;ob>

Such a REGISTER has nothing to do with the text of the draft. An
example of really valid REGISTER implementing RFC 5626 appears in the
RFC itself:

 REGISTER sip:example.com SIP/2.0
 Via: SIP/2.0/TCP 192.0.2.2;branch=z9hG4bKnashds7
 Max-Forwards: 70
 From: Bob<sip:bob@example.com>;tag=7F94778B653B
 To: Bob<sip:bob@example.com>
 Call-ID: 16CB75F21C70
 CSeq: 1 REGISTER
 Supported: path, outbound
 Route:<sip:ep1.example.com;lr>
 Contact:<sip:bob@192.0.2.2;transport=tcp>;reg-id=1
  ;+sip.instance="<urn:uuid:00000000-0000-1000-8000-AABBCCDDEEFF>"
 Content-Length: 0

Please note the "outbound" option tag in Supported header and the
;reg-id and ;+sip.instance header parameters in the Contact header.

For sure, PJSIP implements it correctly but maybe both CSipSimple and
Blink do not make usage of it, or they use a previous version of
PJSIP. Am I right?

Thanks a lot for the clarification.

I can tell for CSipSimple ;).

The option is not yet integrated to the application. It (should be) behind
in pjsip but no ways to enable/disable it in the app yet (I'm not sure if it
is in r944 but for sure it is in nightly builds).

Since nobody asked me for these options, I didn't take time to add these
options in the UI. If someone need it, I can add options so that you can do
more tests.

Hi, AFAIK PJSIP is supposed to implement RFC 5626 "Managing
Client-Initiated Connections" (AKA "Outbound" spec).

If this feature is not implemented in the version of PJSIP used within
CSipSimple or Blink softphones, then please tell it to me and just
ignore the rest of the mail :)

Using CSipSimple r944 I see a REGISTER like this (ommiting some headers):

REGISTER sip:domain.net SIP/2.0
Contact: "Alice" sip:ibc@192.168.1.13:60461;transport=TCP;ob

Such a REGISTER has nothing to do with the text of the draft. An
example of really valid REGISTER implementing RFC 5626 appears in the
RFC itself:

REGISTER sip:example.com SIP/2.0
Via: SIP/2.0/TCP 192.0.2.2;branch=z9hG4bKnashds7
Max-Forwards: 70
From: Bob sip:bob@example.com;tag=7F94778B653B
To: Bob sip:bob@example.com
Call-ID: 16CB75F21C70
CSeq: 1 REGISTER
Supported: path, outbound
Route: sip:ep1.example.com;lr
Contact: sip:bob@192.0.2.2;transport=tcp;reg-id=1
;+sip.instance="urn:uuid:00000000-0000-1000-8000-AABBCCDDEEFF"
Content-Length: 0

Please note the "outbound" option tag in Supported header and the
;reg-id and ;+sip.instance header parameters in the Contact header.

For sure, PJSIP implements it correctly but maybe both CSipSimple and
Blink do not make usage of it, or they use a previous version of
PJSIP. Am I right?

Thanks a lot for the clarification.