[asterisk-users] pjsip Transfer 'Failed to parse destination uri'

Joshua Colp jcolp at digium.com
Mon Nov 27 05:11:53 CST 2017

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

More information about the asterisk-users mailing list