search for: t38_interpret_parameters

...ut > in the source code? Which functions could be interesting? I may add own > debug code to see why things are happening as they happen here. The logic for T.38 negotiation lives all in the res_pjsip_t38 module and the request to negotiate works using a control frame which is handled by the t38_interpret_parameters function. It's up to that to initialize things and then request that a session refresh occurs (which sends the re-invite). That'd be the place to look. -- Joshua Colp Digium, Inc. | Senior Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - US Check us out at: www.digium.co...

...be interesting? I may add own > >> debug code to see why things are happening as they happen here. > > > > The logic for T.38 negotiation lives all in the res_pjsip_t38 module and > > the request to negotiate works using a control frame which is handled by > > the t38_interpret_parameters function. It's up to that to initialize > > things and then request that a session refresh occurs (which sends the > > re-invite). That'd be the place to look. > > I added a debug output at the beginning of the function to see if it's > ever > been called. >...

On Mon, Jun 5, 2017, at 12:00 PM, Joshua Colp wrote: > On Mon, Jun 5, 2017, at 11:49 AM, Michael Maier wrote: > > On 06/05/2017 at 11:30 AM, Joshua Colp wrote: > > > On Sun, Jun 4, 2017, at 10:40 AM, Michael Maier wrote: > > >> On 06/04/2017 at 01:41 PM Telium Technical Support wrote: > > >>> Just a guess (without knowing about your network), but are

On 06/14/2017 at 10:17 PM, Joshua Colp wrote: > On Wed, Jun 14, 2017, at 05:09 PM, Michael Maier wrote: > > <snip> > >> >> I can now say, that asterisk / pjsip seams to work *mostly* as expected. >> Just one exception - and that's the package in question, which can't be >> seen in tcpdump. >> >> I extended the above patch by adding