Re: [pjsip] Explanation of T1/T2/T4/TD timer values
Thank you, that link is helpful. However when I modify the PJSIP timer values the results don't seem to correspond with my expectations based on the calculations in the link.
For example, here are my PJSIP timer values:
PJSIP_T1_TIMEOUT 9350PJSIP_T2_TIMEOUT 34000PJSIP_T4_TIMEOUT 34000
...but as you can see from the logs below the retransmits are happening on a much higher frequency (~1200ms), and the transaction timesout (4679ms) before the response is returned from the server over the high latency satellite link (5314ms).
Why is the PJSIP timer behaviour differing from my configuration options?
12:12:10.202 tsx0x1188f0c0 Transaction created for Request msg REGISTER/cseq=31167 (tdta0x1188e03c)12:12:10.202 tsx0x1188f0c0 Sending Request msg REGISTER/cseq=31167 (tdta0x1188e03c) in state Null12:12:10.202 sip_resolve.c DNS resolver not available, target 'asterisk.local:5060' type=Unspecified will be resolved with getaddrinfo()12:12:10.946 sip_resolve.c Target 'asterisk.local:5060' type=Unspecified resolved to '10.10.10.5:5060' type=UDP (UDP transport)12:12:10.946 tsx0x1188f0c0 State changed from Null to Calling, event=TX_MSG12:12:10.946 pjsua_acc.c Registration sent
+1138 milliseconds12:12:12.084 tsx0x1188f0c0 Retransmit timer event12:12:12.084 tsx0x1188f0c0 Retransmiting Request msg REGISTER/cseq=31167 (tdta0x1188e03c), count=0, restart?=1
+1313 milliseconds12:12:13.397 tsx0x1188f0c0 Retransmit timer event12:12:13.412 tsx0x1188f0c0 Retransmiting Request msg REGISTER/cseq=31167 (tdta0x1188e03c), count=1, restart?=1
+1297 milliseconds12:12:14.694 tsx0x1188f0c0 Retransmit timer event12:12:14.694 tsx0x1188f0c0 Retransmiting Request msg REGISTER/cseq=31167 (tdta0x1188e03c), count=2, restart?=1
+187 milliseconds12:12:14.881 tsx0x1188f0c0 Timeout timer event12:12:14.881 tsx0x1188f0c0 State changed from Calling to Terminated, event=TIMER12:12:14.881 pjsua_acc.c SIP registration failed, status=408 (Request Timeout)
12:12:15.516 sip_endpoint.c Processing incoming message: Response msg 200/REGISTER/cseq=31167 (rdata0x1187a2a0)12:12:15.516; sip_endpoint.c Message Response msg 200/REGISTER/cseq=31167 (rdata0x1187a2a0) from 10.10.10.5:5060 was dropped/unhandled by any modules
First REGISTER to transaction timeout = 4679 milliseconds Response received from server = 5314 milliseconds PJSIP version is 1.12.0.
Cheers. Dave.
On Tuesday, 1 March 2016, 16:13, BS Chandu <chandrashekara.shivaiah@gmail.com> wrote:
This link has explanation for all SIP timers.https://tools.ietf.org/html/rfc3261#page-265On Mar 1, 2016 6:11 PM, "David Dean" just_bytesize@yahoo.co.uk wrote:
Hello all,
I'm trying to understand the exact impact of the PJSIP timeout configuration options because I need to match the high latency of a satellite service. I'm getting lots of 408 timeouts at the moment, particularly for REGISTER messages:
PJSIP_T1_TIMEOUT
PJSIP_T2_TIMEOUT
PJSIP_T4_TIMEOUT
PJSIP_TD_TIMEOUT
The problem is I cannot find any documentation explaining these timers, and when I change the default values the PJSIP timer behaviour is not matching the time periods I enter. Can anyone point me to a source of documentation or correct my understanding below?
PJSIP_T1_TIMEOUT = Retry frequency within transaction timeout; e.g. PJSIP will retransmit the message at the defined interval
PJSIP_T2_TIMEOUT = What is this?
PJSIP_T4_TIMEOUT = Transaction timeout period for non-INVITE requests
PJSIP_TD_TIMEOUT = Transaction timeout period for INVITE requests
Also when I change these values, the retransmits/timeouts do not match the time periods I enter. Why is that?
Cheers. Dave.
Visit our blog: http://blog.pjsip.org
pjsip mailing list
pjsip@lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
Can anyone explain why the PJSIP timers don't match the configuration values I'm entering?
I've tried reviewing the source but I couldn't find any explanation for what I'm seeing.
Cheers. Dave.
On Wednesday, 2 March 2016, 9:48, David Dean <just_bytesize@yahoo.co.uk> wrote:
Thank you, that link is helpful. However when I modify the PJSIP timer values the results don't seem to correspond with my expectations based on the calculations in the link.
For example, here are my PJSIP timer values:
PJSIP_T1_TIMEOUT 9350PJSIP_T2_TIMEOUT 34000PJSIP_T4_TIMEOUT 34000
...but as you can see from the logs below the retransmits are happening on a much higher frequency (~1200ms), and the transaction timesout (4679ms) before the response is returned from the server over the high latency satellite link (5314ms).
Why is the PJSIP timer behaviour differing from my configuration options?
12:12:10.202 tsx0x1188f0c0 Transaction created for Request msg REGISTER/cseq=31167 (tdta0x1188e03c)12:12:10.202 tsx0x1188f0c0 Sending Request msg REGISTER/cseq=31167 (tdta0x1188e03c) in state Null12:12:10.202 sip_resolve.c DNS resolver not available, target 'asterisk.local:5060' type=Unspecified will be resolved with getaddrinfo()12:12:10.946 sip_resolve.c Target 'asterisk.local:5060' type=Unspecified resolved to '10.10.10.5:5060' type=UDP (UDP transport)12:12:10.946 tsx0x1188f0c0 State changed from Null to Calling, event=TX_MSG12:12:10.946 pjsua_acc.c Registration sent
+1138 milliseconds12:12:12.084 tsx0x1188f0c0 Retransmit timer event12:12:12.084 tsx0x1188f0c0 Retransmiting Request msg REGISTER/cseq=31167 (tdta0x1188e03c), count=0, restart?=1
+1313 milliseconds12:12:13.397 tsx0x1188f0c0 Retransmit timer event12:12:13.412 tsx0x1188f0c0 Retransmiting Request msg REGISTER/cseq=31167 (tdta0x1188e03c), count=1, restart?=1
+1297 milliseconds12:12:14.694 tsx0x1188f0c0 Retransmit timer event12:12:14.694 tsx0x1188f0c0 Retransmiting Request msg REGISTER/cseq=31167 (tdta0x1188e03c), count=2, restart?=1
+187 milliseconds12:12:14.881 tsx0x1188f0c0 Timeout timer event12:12:14.881 tsx0x1188f0c0 State changed from Calling to Terminated, event=TIMER12:12:14.881 pjsua_acc.c SIP registration failed, status=408 (Request Timeout)
12:12:15.516 sip_endpoint.c Processing incoming message: Response msg 200/REGISTER/cseq=31167 (rdata0x1187a2a0)12:12:15.516; sip_endpoint.c Message Response msg 200/REGISTER/cseq=31167 (rdata0x1187a2a0) from 10.10.10.5:5060 was dropped/unhandled by any modules
First REGISTER to transaction timeout = 4679 milliseconds Response received from server = 5314 milliseconds PJSIP version is 1.12.0.
Cheers. Dave.
On Tuesday, 1 March 2016, 16:13, BS Chandu <chandrashekara.shivaiah@gmail.com> wrote:
This link has explanation for all SIP timers.https://tools.ietf.org/html/rfc3261#page-265On Mar 1, 2016 6:11 PM, "David Dean" just_bytesize@yahoo.co.uk wrote:
Hello all,
I'm trying to understand the exact impact of the PJSIP timeout configuration options because I need to match the high latency of a satellite service. I'm getting lots of 408 timeouts at the moment, particularly for REGISTER messages:
PJSIP_T1_TIMEOUT
PJSIP_T2_TIMEOUT
PJSIP_T4_TIMEOUT
PJSIP_TD_TIMEOUT
The problem is I cannot find any documentation explaining these timers, and when I change the default values the PJSIP timer behaviour is not matching the time periods I enter. Can anyone point me to a source of documentation or correct my understanding below?
PJSIP_T1_TIMEOUT = Retry frequency within transaction timeout; e.g. PJSIP will retransmit the message at the defined interval
PJSIP_T2_TIMEOUT = What is this?
PJSIP_T4_TIMEOUT = Transaction timeout period for non-INVITE requests
PJSIP_TD_TIMEOUT = Transaction timeout period for INVITE requests
Also when I change these values, the retransmits/timeouts do not match the time periods I enter. Why is that?
Cheers. Dave.
Visit our blog: http://blog.pjsip.org
pjsip mailing list
pjsip@lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
Visit our blog: http://blog.pjsip.org
pjsip mailing list
pjsip@lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org