Re: [asterisk-users] asterisk 13.16 / pjsip / t.38: res_pjsip_t38.c:207 t38_automatic_reject: Automatically rejecting T.38 request on channel 'PJSIP/91-00000007'

2017-06-11 Thread Daniel Tryba
On Sun, Jun 11, 2017 at 01:16:10PM +0200, Michael Maier wrote: > Let's go into details: > I'm starting at the point where asterisk / fax client receives the T.38 > reininvite from the server from the provider 195.185.37.60:5060 for the > fax client (extension 91): I'm running Asterisk 11 on my

Re: [asterisk-users] asterisk 13.16 / pjsip / t.38: res_pjsip_t38.c:207 t38_automatic_reject: Automatically rejecting T.38 request on channel 'PJSIP/91-00000007'

2017-06-11 Thread Joshua Colp
On Sun, Jun 11, 2017, at 01:47 PM, Joshua Colp wrote: > On Sun, Jun 11, 2017, at 01:31 PM, Michael Maier wrote: > > On 06/11/2017 at 04:39 PM Joshua Colp wrote: > > > On Sun, Jun 11, 2017, at 11:34 AM, Michael Maier wrote: > > > > > > > > > > > >>> > > >>> PJSIP uses a dispatch model. The

Re: [asterisk-users] asterisk 13.16 / pjsip / t.38: res_pjsip_t38.c:207 t38_automatic_reject: Automatically rejecting T.38 request on channel 'PJSIP/91-00000007'

2017-06-11 Thread Joshua Colp
On Sun, Jun 11, 2017, at 01:31 PM, Michael Maier wrote: > On 06/11/2017 at 04:39 PM Joshua Colp wrote: > > On Sun, Jun 11, 2017, at 11:34 AM, Michael Maier wrote: > > > > > > > >>> > >>> PJSIP uses a dispatch model. The request is queued up, acted on, and > >>> then that's it. The act of acting

Re: [asterisk-users] asterisk 13.16 / pjsip / t.38: res_pjsip_t38.c:207 t38_automatic_reject: Automatically rejecting T.38 request on channel 'PJSIP/91-00000007'

2017-06-11 Thread Michael Maier
On 06/11/2017 at 04:39 PM Joshua Colp wrote: > On Sun, Jun 11, 2017, at 11:34 AM, Michael Maier wrote: > > > >>> >>> PJSIP uses a dispatch model. The request is queued up, acted on, and >>> then that's it. The act of acting on it removes it from the queue. >> >> That's the *expected* behavior

Re: [asterisk-users] asterisk 13.16 / pjsip / t.38: res_pjsip_t38.c:207 t38_automatic_reject: Automatically rejecting T.38 request on channel 'PJSIP/91-00000007'

2017-06-11 Thread Joshua Colp
On Sun, Jun 11, 2017, at 11:34 AM, Michael Maier wrote: > > > > PJSIP uses a dispatch model. The request is queued up, acted on, and > > then that's it. The act of acting on it removes it from the queue. > > That's the *expected* behavior ... . I rechecked again and again. All > existing

Re: [asterisk-users] asterisk 13.16 / pjsip / t.38: res_pjsip_t38.c:207 t38_automatic_reject: Automatically rejecting T.38 request on channel 'PJSIP/91-00000007'

2017-06-11 Thread Michael Maier
On 06/11/2017 at 01:29 PM Joshua Colp wrote: > On Sun, Jun 11, 2017, at 08:16 AM, Michael Maier wrote: > > > >> I did some further investigations and fixed a local problem. Now, >> asterisk is able to successfully activate T.38 - unfortunately just for >> very shot time because of a phantom

Re: [asterisk-users] asterisk 13.16 / pjsip / t.38: res_pjsip_t38.c:207 t38_automatic_reject: Automatically rejecting T.38 request on channel 'PJSIP/91-00000007'

2017-06-11 Thread Joshua Colp
On Sun, Jun 11, 2017, at 08:16 AM, Michael Maier wrote: > I did some further investigations and fixed a local problem. Now, > asterisk is able to successfully activate T.38 - unfortunately just for > very shot time because of a phantom package it receives! What was the local problem? >

Re: [asterisk-users] asterisk 13.16 / pjsip / t.38: res_pjsip_t38.c:207 t38_automatic_reject: Automatically rejecting T.38 request on channel 'PJSIP/91-00000007'

2017-06-11 Thread Michael Maier
On 06/05/2017 at 09:32 PM Joshua Colp wrote: > On Mon, Jun 5, 2017, at 04:26 PM, Michael Maier wrote: >> On 06/05/2017 at 06:29 PM, Joshua Colp wrote: >>> On Mon, Jun 5, 2017, at 01:22 PM, Michael Maier wrote: Do you have any idea where to start to look at? Adding additional output