On 7/3/18 3:57 PM, D'Arcy Cain wrote:
> On 2018-06-13 07:45 AM, D'Arcy Cain wrote:
>> On 2018-06-13 07:20 AM, James Cloos wrote:
D'Arcy Cain writes:
>>>
> Ie after both sides select t38, until they agree on the t38 terms.
>>>
OK, so does that mean that setting it to 25000 should
On 2018-06-13 07:45 AM, D'Arcy Cain wrote:
> On 2018-06-13 07:20 AM, James Cloos wrote:
>>> D'Arcy Cain writes:
>>
Ie after both sides select t38, until they agree on the t38 terms.
>>
>>> OK, so does that mean that setting it to 25000 should leave time for the
>>> re-invite or does the t
On 2018-06-13 07:20 AM, James Cloos wrote:
>> D'Arcy Cain writes:
>
>>> Ie after both sides select t38, until they agree on the t38 terms.
>
>> OK, so does that mean that setting it to 25000 should leave time for the
>> re-invite or does the timeout start after that.
>
> As I wrote above, a
> D'Arcy Cain writes:
>> Ie after both sides select t38, until they agree on the t38 terms.
> OK, so does that mean that setting it to 25000 should leave time for the
> re-invite or does the timeout start after that.
As I wrote above, after that. After the sip/sdp.
-JimC
--
James Cloos
On 2018-06-12 07:10 PM, James Cloos wrote:
>> "DC" == D'Arcy Cain writes:
>
> DC> Perhaps someone can explain what t38timeout is supposed to do
>
> A 'git grep t38timeout' on the src leads one to res/res_fax.c, where one
> case see that it is the number of miliseconds to permit for t38 negot
> "DC" == D'Arcy Cain writes:
DC> Perhaps someone can explain what t38timeout is supposed to do
A 'git grep t38timeout' on the src leads one to res/res_fax.c, where one
case see that it is the number of miliseconds to permit for t38 negotiation
to complete once it starts.
Ie after both side
On 2018-06-08 06:45 AM, D'Arcy Cain wrote:
> I tried increasing the t38timeout but it did not seem to have any
> effect. Is there another variable to adjust somewhere?
Pinging the list to see if anyone has any thoughts. Perhaps someone can
explain what t38timeout is supposed to do as it seems to
