Re: [asterisk-users] taskprocessor.c: The 'sorcery/contact-00000015' task processor queue reached 1500 scheduled tasks.

On Thu, Nov 23, 2017 at 3:25 PM, Brian Capouch wrote: > Running 15.1.2. I have four devices transitioned to use pjsip. > > After about 1-2 days of uptime, psjip stops accepting registrations, > and the messages log contains the entry as per the subject. > > At any given

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

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: > >

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

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

[asterisk-users] 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-0011 Do I