asterisk users - Nov 2017 - pjsip Transfer 'Failed to parse destination uri'

Hi Richard
> That could be possible and would be a bug in chan_sip.
Ok, so I switched to PJSIP to see if this behaves differently

So ip do a

Transfer(PJSIP/${DESTNUMBER}@trunk)

And this results in:

Failed to parse destination URI '[destnumber scrubber]' for channel
PJSIP/trunk-00000011

Do I have to specify the destination number differently when using
Transfer with pjsip that I used it in chan_sip?

-Beno?t Panizzon-
-- 
I m p r o W a r e   A G    -    Leiter Commerce Kunden
______________________________________________________

Zurlindenstrasse 29             Tel  +41 61 826 93 00
CH-4133 Pratteln                Fax  +41 61 826 93 01
Schweiz                         Web  http://www.imp.ch
______________________________________________________

Ok, answering myself:

Asterisk 13.14.1~dfsg-2+deb9u2

Apparently suffers the pjsip transfer bug described @

https://reviewboard.asterisk.org/r/4316/diff/

Specifying the full URI:

Transfer(PJSIP/sip:${DESTEXTEN}@trunk) does resolve the URI parsing
problem and is sending back the 302 message (which does not containg a
Diversion header, Jay promising, testing that next), but as described in
the Bug the Contact header is being messed up.

-Beno?t Panizzon-
-- 
I m p r o W a r e   A G    -    Leiter Commerce Kunden
______________________________________________________

Zurlindenstrasse 29             Tel  +41 61 826 93 00
CH-4133 Pratteln                Fax  +41 61 826 93 01
Schweiz                         Web  http://www.imp.ch
______________________________________________________

On Mon, Nov 27, 2017, at 05:42 AM, Benoit Panizzon
wrote:
> Ok, answering myself:
> 
> Asterisk 13.14.1~dfsg-2+deb9u2
> 
> Apparently suffers the pjsip transfer bug described @
> 
> https://reviewboard.asterisk.org/r/4316/diff/
> 
> Specifying the full URI:
> 
> Transfer(PJSIP/sip:${DESTEXTEN}@trunk) does resolve the URI parsing
> problem and is sending back the 302 message (which does not containg a
> Diversion header, Jay promising, testing that next), but as described in
> the Bug the Contact header is being messed up.
PJSIP requires a full SIP URI that can be used by the remote endpoint to
be provided. The code does not look up an endpoint and try to construct
a SIP URI for you.

-- 
Joshua Colp
Digium, Inc. | Senior Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - US
Check us out at: www.digium.com & www.asterisk.org