Project

General

Profile

Actions
Copy link

Enhancement #1621

closed

iPhone: Groundwire: background: too low expiration interval (300) forced by the server

Added by Pro Backup over 12 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Registration
Target version:
-
Start date:
05/04/2012
Due date:
% Done:

0%

Estimated time:
Keywords:
expire low tls

Description

Using SIP/TLS is is not nice that the sip2sip server force an expiration interval of 300 seconds. This value is so low that I am not able to receive incoming calls in background mode. Please increase this value to at least 1700 seconds for iPhone usage.

Files

groundwire-trace.log (55.2 KB) groundwire-trace.log Pro Backup, 05/05/2012 01:05 AM
Actions
Copy link
 #1

Updated by Pro Backup over 12 years ago

transport protocol = tls (sips) @ proxy.sipthor.net:5061

Actions
Copy link
 #2

Updated by Pro Backup over 12 years ago

Please force least 600 seconds (10 minutes).
And better to not not force an expiration at all (let the client device choose).

Actions
Copy link
 #3

Updated by Pro Backup over 12 years ago

Strange is that sometimes even an Expires: 600 is is received from proxy.sipthor:

2012-05-04T22:46:36.617Z
Received:
192.168.10.220:56144 <- proxy.sipthor.net/81.23.228.129:5061 [proxy.sipthor.net/81.23.228.129:5061; 81.23.228.129:5061]
694
SIP/2.0 200 OK
Record-Route: <sip:81.23.228.129;r2=on;lr;ftag=6E51B7C670DF87F0AC08948D9D01FAAE>
Record-Route: <sip:81.23.228.129:5061;transport=tls;r2=on;lr;ftag=6E51B7C670DF87F0AC08948D9D01FAAE>
Via: SIP/2.0/TCP 192.168.10.220:56144;received=82.171.105.23;branch=z9hG4bKV4uqYHOF3IeEYASw;rport=56144
From: "" <sips:>;tag=6E51B7C670DF87F0AC08948D9D01FAAE
To: "" <sips:>;tag=64b03df7c1a4aac2e7aeb74322defa92-4566
Call-ID: 4124CED50732644C28941D6985D2B0A2A725309C
CSeq: 2 SUBSCRIBE
Expires: 600
Contact: <sip:>
Server: SIP Thor on OpenSIPS XS 1.8.0
Content-Length: 0

Actions
Copy link
 #4

Updated by Adrian Georgescu over 12 years ago

  • Status changed from New to To be closed

There is nothing strange about an Expire header related to a Subscribe packet. This trace has nothing to do with a Register message, is a response for a Subscribe as the Cseq indicates.

About registration period there is nothing good or wrong about 300 seconds, end-point should just honor the server indication as per standard.

Actions
Copy link
 #5

Updated by Adrian Georgescu over 12 years ago

  • Status changed from To be closed to Closed
Actions
Copy link
 #6

Updated by Adrian Georgescu over 12 years ago

Default expiration interval has been set to 3600 seconds.

Actions
Copy link
 #7

Updated by Pro Backup over 12 years ago

Thank you, 1. for re-considering and 2. for increasing the expires value.
Now the iOS SIP applications can go to background (= wake on TCP) and save power.

Actions
Copy link
 #8

Updated by Pro Backup over 11 years ago

The default expires value of 3600 seconds, results in re-registering usually at 50% of this interval. In reality the iPhone wakes every 9 till 26 minutes (excluding network changes) to re-register.

An example based on our Groundwire log: ===
19:18-19:41 = 23 min. - we are awake
19:41-20:07 = 26 min. - we are awake
20:07-20:32 = 25 min. - we are awake
20:32-20:34 = 02 min. - onNetworkStatusChanged
20:34-20:57 = 23 min. - we are awake
20:57-21:06 = 09 min. - we are awake
21:06-21:15 = 09 min. - we are awake ===

Please allow a larger expires value, by honouring the expires value that the SIP client requests. Because the Groundwire client is smart enough to re-register on network changes itself.

The request is not to set a larger default expires value, but to honour the value the SIP clients asks.

Actions
Copy link

Also available in: Atom PDF