SIP Register - expires timers

[woodywesty]

I'm currenlty seeing my SIP trunk re-register every 12 - 15 seconds, Contact: <sip:4account@x.x.x.x:5060;transport=udp;line=c81e728d>;expires=30

 

[7] 2011/08/13 09:25:06: SIP Tx udp:1.1.1.1:5060:

REGISTER sip:spitfiretsp.net SIP/2.0

Via: SIP/2.0/UDP 2.2.2.2:5060;branch=Payload Removed;rport

From: "Spitfire Trunk" <sip:4account@spitfiretsp.net>;tag=11279

To: "Spitfire Trunk" <sip:4account@spitfiretsp.net>

Call-ID: xiscmeig@pbx

CSeq: 47279 REGISTER

Max-Forwards: 70

Contact: <sip:4account@2.2.2.2:5060;transport=udp;line=c81e728d>;+sip.instance="<urn:uuid:6e6f73fe-****-****-****-46da1b8a891c>"

User-Agent: snom-PBX/4.2.0.3950

Supported: outbound

Expires: 3600

Content-Length: 0

 

 

[7] 2011/08/13 09:25:06: SIP Rx udp:1.1.1.1:5060:

SIP/2.0 200 OK

Via: SIP/2.0/UDP 2.2.2.2:5060;received=217.13.145.130;branch=Payload Removed;rport=38084

From: "Spitfire Trunk" <sip:4account@spitfiretsp.net>;tag=11279

To: "Spitfire Trunk" <sip:4account@spitfiretsp.net>;tag=aprqgdtra01-pidclg0000eva

Call-ID: xiscmeig@pbx

CSeq: 47279 REGISTER

Contact: <sip:4account@2.2.2.2:5060;transport=udp;line=c81e728d>;expires=30

[Vodia PBX]

That is quiet normal. By the time when SIP was specified, the engineers were optimistic that by the day that SIP would be used by anyone, everyone would have IPv6 and there would be no need to refresh bindings so quickly. In the meantime, we have to live with such dirty workaround like refreshing every so-and-so seconds.