[Serusers] Contact in 200 OK response to REGISTER

Stefan Sayer stefan.sayer at iptego.de
Mon Nov 27 15:39:16 CET 2006


Hi,

registrar at iptel.org (0.10.99-iptelorg/tekelec-SOPv2) and ser 0.9.6 as 
well do not return a contact header in 200 response to REGISTER (see 
trace below), but in rfc (10.3) I read it's a MUST


       8. The registrar returns a 200 (OK) response.  The response MUST
          contain Contact header field values enumerating all current
          bindings.  Each Contact value MUST feature an "expires"
          parameter indicating its expiration interval chosen by the
          registrar.  The response SHOULD include a Date header field.

Am I missing something (apart from the contact header) or is my register 
message not correct?

Stefan

U 192.168.5.101:5070 -> 213.192.59.75:5060
REGISTER sip:iptel.org SIP/2.0.
Via: SIP/2.0/UDP 192.168.5.101:5070;branch=z9hG4bK15f6.4d8faeb.0.
To: Stefan <sip:sayer at iptel.org>.
From: Stefan <sip:sayer at iptel.org>;tag=0E520893-456AF6AD0009055B-B7963B90.
CSeq: 10 REGISTER.
Call-ID: 0D1543AB-456AF6AD00090738-B7C66B90 at 192.168.5.101.
Content-Length: 0.
User-Agent: Sip EXpress router(0.9.6-sems (i386/linux)).
Contact: <sip:sayer at 192.168.5.101:5070>.
Expires: 0.
.

#
U 213.192.59.75:5060 -> 192.168.5.101:5070
SIP/2.0 401 Unauthorized.
Via: SIP/2.0/UDP 
192.168.10.144:5070;rport=5070;received=91.64.139.240;branch=z9hG4bK15f6.4d8faeb.0.
To: Stefan <sip:sayer at iptel.org>;tag=17da4c1f77cf571798ae2c71e6d4b5c0.4003.
From: Stefan <sip:sayer at iptel.org>;tag=0E520893-456AF6AD0009055B-B7963B90.
CSeq: 10 REGISTER.
Call-ID: 0D1543AB-456AF6AD00090738-B7C66B90 at 192.168.5.101.
P-Nat: Yes.
WWW-Authenticate: Digest realm="iptel.org", 
nonce="456af887c3eac5c30c87bab4268389ee5e796372".
Server: Sip EXpress router (0.10.99-iptelorg/tekelec-SOPv2 (i386/linux)).
Content-Length: 0.
Warning: 392 213.192.59.77:5070 "Noisy feedback tells:  pid=4141 
req_src_ip=213.192.59.75 req_src_port=5060 in_uri=sip:iptel.org 
out_uri=sip:iptel.org via_cnt==2".
.

#
U 192.168.5.101:5070 -> 213.192.59.75:5060
REGISTER sip:iptel.org SIP/2.0.
Via: SIP/2.0/UDP 192.168.5.101:5070;branch=z9hG4bK25f6.dae56b14.0.
To: Stefan <sip:sayer at iptel.org>.
From: Stefan <sip:sayer at iptel.org>;tag=0E520893-456AF6AD0009055B-B7963B90.
CSeq: 11 REGISTER.
Call-ID: 0D1543AB-456AF6AD00090738-B7C66B90 at 192.168.5.101.
Content-Length: 0.
User-Agent: Sip EXpress router(0.9.6-sems (i386/linux)).
Contact: <sip:sayer at 192.168.5.101:5070>.
Expires: 0.
Authorization: Digest username="sayer", realm="iptel.org", 
nonce="456af887c3eac5c30c87bab4268389ee5e796372", uri="sip:iptel.org", 
response="880ff39073b5eeb3cda68352b78de368", algorithm="MD5".
.

#
U 213.192.59.75:5060 -> 192.168.5.101:5070
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 
192.168.5.101:5070;rport=5070;received=91.64.139.240;branch=z9hG4bK25f6.dae56b14.0.
To: Stefan <sip:sayer at iptel.org>;tag=17da4c1f77cf571798ae2c71e6d4b5c0.4003.
From: Stefan <sip:sayer at iptel.org>;tag=0E520893-456AF6AD0009055B-B7963B90.
CSeq: 11 REGISTER.
Call-ID: 0D1543AB-456AF6AD00090738-B7C66B90 at 192.168.5.101.
P-Nat: Yes.
Server: Sip EXpress router (0.10.99-iptelorg/tekelec-SOPv2 (i386/linux)).
Content-Length: 0.
Warning: 392 213.192.59.77:5070 "Noisy feedback tells:  pid=4140 
req_src_ip=213.192.59.75 req_src_port=5060 in_uri=sip:iptel.org 
out_uri=sip:iptel.org via_cnt==2".
.


-- 
Stefan Sayer
Media Services Development

iptego GmbH
Am Borsigturm 40
13507 Berlin
Germany

stefan.sayer at iptego.de
www.iptego.de



More information about the sr-users mailing list