[SR-Users] Incorrect registrar Expires handling

[Daniel-Constantin Mierla]

Hello,

I tested with kamailio default config and injected some REGISTERs to 
reproduce the scenario, see the SIP trace below. The results were ok in 
200 reply, also in kamctl.

Can you send me also a SIP trace for the situation? Also, the parameters 
for registrar and usrloc modules. Do you you have a particular 
matching_mode set?

Thanks,
Daniel

U 2011/06/03 09:39:05.409702 127.0.0.1:56741 -> 127.0.0.1:5060
REGISTER sip:127.0.0.1:5060 SIP/2.0
From: "Test" <sip:test at 127.0.0.1>;tag=as23
To: "Test" <sip:test at 127.0.0.1>
Call-ID: aa at 127.0.0.1
User-Agent: snom100_1.9b
CSeq: 2 REGISTER
Via: SIP/2.0/UDP 127.0.0.1:5080
Contact: <sip:me at 127.0.0.1:2001;ob>
Expires: 900
Content-Length: 0



U 2011/06/03 09:39:05.413813 127.0.0.1:5060 -> 127.0.0.1:5080
SIP/2.0 200 OK.
From: "Test" <sip:test at 127.0.0.1>;tag=as23
To: "Test" <sip:test at 127.0.0.1>;tag=b27e1a1d33761e85846fc98f5f3a7e58.521d
Call-ID: aa at 127.0.0.1
CSeq: 2 REGISTER
Via: SIP/2.0/UDP 127.0.0.1:5080.
Contact: <sip:me at 127.0.0.1:2001;ob>;expires=900.
Server: kamailio (3.2.0-dev5 (x86_64/darwin)).
Content-Length: 0.
.


U 2011/06/03 09:39:43.616036 127.0.0.1:56948 -> 127.0.0.1:5060
REGISTER sip:127.0.0.1:5060 SIP/2.0
From: "Test" <sip:test at 127.0.0.1>;tag=as23
To: "Test" <sip:test at 127.0.0.1>
Call-ID: aa at 127.0.0.1
User-Agent: snom100_1.9b
CSeq: 3 REGISTER
Via: SIP/2.0/UDP 127.0.0.1:5080
Contact: <sip:me at 127.0.0.1:3001;transport=UDP;ob>
Contact: <sip:me at 127.0.0.1:2001;ob>;expires=0
Expires: 900
Content-Length: 0



U 2011/06/03 09:39:43.618327 127.0.0.1:5060 -> 127.0.0.1:5080
SIP/2.0 200 OK.
From: "Test" <sip:test at 127.0.0.1>;tag=as23
To: "Test" <sip:test at 127.0.0.1>;tag=b27e1a1d33761e85846fc98f5f3a7e58.521d
Call-ID: aa at 127.0.0.1
CSeq: 3 REGISTER
Via: SIP/2.0/UDP 127.0.0.1:5080.
Contact: <sip:me at 127.0.0.1:3001;transport=UDP;ob>;expires=900.
Server: kamailio (3.2.0-dev5 (x86_64/darwin)).
Content-Length: 0.
.

# kamctl ul show
Domain:: location table=512 records=1 max_slot=1
     AOR:: test
         Contact:: sip:me at 127.0.0.1:3001;transport=UDP;ob Q=
             Expires:: 889
             Callid:: aa at 127.0.0.1
             Cseq:: 3
             User-agent:: snom100_1.9b
             State:: CS_NEW
             Flags:: 0
             Cflag:: 0
             Socket:: udp:127.0.0.1:5060
             Methods:: 4294967295

# kamctl ul show
Domain:: location table=512 records=1 max_slot=1
     AOR:: test
         Contact:: sip:me at 127.0.0.1:3001;transport=UDP;ob Q=
             Expires:: 690
             Callid:: aa at 127.0.0.1
             Cseq:: 3
             User-agent:: snom100_1.9b
             State:: CS_NEW
             Flags:: 0
             Cflag:: 0
             Socket:: udp:127.0.0.1:5060
             Methods:: 4294967295

On 6/3/11 12:16 AM, Andreas Granig wrote:
> Hi,
>
> On 06/03/2011 12:10 AM, Daniel-Constantin Mierla wrote:
>> one more thing, what is the output of kamctl ul show? I want to see if
>> it is a matter of building the contact header for reply or is in
>> internal list of location records.
> Domain:: location table=512 records=1 max_slot=1
> 	AOR:: me at somedomain.com
> 		Contact:: sip:me at 10.0.0.7:52030;ob Q=
> 			Expires:: 875
> 			Callid:: DZZHTDttFd5WivydjNnWfpRLsXp8RIYh
> 			Cseq:: 4599
> 			User-agent:: myclient
> 			Received:: sip:1.2.3.4:55642
> 			Path::<sip:lb at 127.0.0.1:5060;lr;received=sip:1.2.3.4:55642>
> 			State:: CS_SYNC
> 			Flags:: 0
> 			Cflag:: 192
> 			Socket:: udp:127.0.0.1:5062
> 			Methods:: 8143
> 		Contact:: sip:me at 1.2.3.4:55642;transport=UDP;ob Q=
> 			Expires:: 876
> 			Callid:: DZZHTDttFd5WivydjNnWfpRLsXp8RIYh
> 			Cseq:: 4601
> 			User-agent:: myclient
> 			Path::<sip:lb at 127.0.0.1:5060;lr>
> 			State:: CS_SYNC
> 			Flags:: 0
> 			Cflag:: 0
> 			Socket:: udp:127.0.0.1:5062
> 			Methods:: 8143
>
> Hope this helps,
> Andreas

-- 
Daniel-Constantin Mierla -- http://www.asipto.com
http://linkedin.com/in/miconda -- http://twitter.com/miconda