On 2016-08-10 11:53, Joshua Colp wrote:
Jacek Konieczny wrote:
On 2016-08-09 10:06, Faheem Muhammad wrote:
trip time and Call Setup time of SIP Requests.
In case of GSM Network with high delay you need to set the T1 timer a
higher value like 1000ms (500 ms default). Similarly you can reduce the
Jacek Konieczny wrote:
On 2016-08-09 10:06, Faheem Muhammad wrote:
trip time and Call Setup time of SIP Requests.
In case of GSM Network with high delay you need to set the T1 timer a
higher value like 1000ms (500 ms default). Similarly you can reduce the
Call setup time by configuring 'T2' upto
On 2016-08-09 10:06, Faheem Muhammad wrote:
trip time and Call Setup time of SIP Requests.
In case of GSM Network with high delay you need to set the T1 timer a
higher value like 1000ms (500 ms default). Similarly you can reduce the
Call setup time by configuring 'T2' upto you choice as per you t
On 2016-08-09 10:06, Faheem Muhammad wrote:
Jacek,
This might be a bug or configuration issue, but you need to understand
the SIP Session Timers. With Session Timers you can control the round
trip time and Call Setup time of SIP Requests.
I don't think you really mean SIP Session Timers
(https
Jacek,
This might be a bug or configuration issue, but you need to understand the
SIP Session Timers. With Session Timers you can control the round trip time
and Call Setup time of SIP Requests.
In case of GSM Network with high delay you need to set the T1 timer a
higher value like 1000ms (500 ms d
Hi,
We have been migrating our PBX system from Asterisk 1.8 and chan_sip to
Asterisk 13 and chan_pjsip. Things are mostly, ok, but now I have
stumbled on a behaviour difference I don't like.
With chan_pjsip when a phone went unexpectedly offline (Ethernet cable
disconnected) Asterisk would detec
