[OpenSIPS-Users] A Record-Route header field exists in 200 OK from openser-1.3.4-12.fc13.i686 SIPv6 Registrar Server

[Xiaoqiang Hu]

how can I remove the RR in REGISTER request or 200 OK?
--------------------------------------
Regards!
Hu xiaoqiang
Quality Assurance Engineer
IRC Account:xhu Channel:#apac #apac-qa

----- Original Message -----
From: "Bogdan-Andrei Iancu" <bogdan at voice-system.ro>
To: "OpenSIPS users mailling list" <users at lists.opensips.org>
Sent: Wednesday, June 23, 2010 5:40:47 PM GMT -05:00 US/Canada Eastern
Subject: Re: [OpenSIPS-Users] A Record-Route header field exists in 200 OK from openser-1.3.4-12.fc13.i686 SIPv6 Registrar Server

Hi,

the RR header is mirrored in 200 OK as it is present in the request - 
that is how SIP works.

Better check how is responsible for adding the RR in REGISTER request. 
Anyhow, that RR in 200 OK is more or less harmless.

Regards,
Bogdan

Xiaoqiang Hu wrote:
> Hi all,
> A Record-Route header field exists in 200 OK from openser register server after sending a REGISTER request with a Record-Route header field. The details can be as follows:
> 1 Test topology:
>
>
>                    NUT(REG && PX)           UA11                         UA12                           DNS
>                         |                      |                          |                              |
> IP          : 3ffe:501:ffff:50::50   3ffe:501:ffff:1::1          3ffe:501:ffff:2::2                3ffe:501:ffff:4::1
> aor-uri     : ss.under.test.com      UA11 at under.test.com         UA12 at under.test.com
> contact-uri :                        UA11 at node.under.test.com    UA12 at node11.under.test.com
> 2  the test result can be seen as follows:
>                         NUT  UA11 UA12 UA13 UA14 PX2  PX3  PX4  DNS
>  No     time             |    |    |    |    |    |    |    |    |
>  No     time             |    |    |    |    |    |    |    |    |
> [0001:  0.00|    ]       |--->|    |    |    |    |    |    |    |  NS 
> [0002:  0.00|    ]       |<---|    |    |    |    |    |    |    |  NA 
> [0003:  0.69|    ]       |--->|    |    |    |    |    |    |    |  NS 
> [0004:  0.69|    ]       |<---|    |    |    |    |    |    |    |  NA 
> [0005:  3.79|U   ] REGIS |<---|    |    |    |    |    |    |    | REGISTER sip:ss.under.test.com:5060
> [0006:  3.79|U   ] 401   |--->|    |    |    |    |    |    |    | 401 Unauthorized (REGISTER)
> [0007:  3.87|U   ] REGIS |<---|    |    |    |    |    |    |    | REGISTER sip:ss.under.test.com:5060
> [0008:  3.87|U   ] 200   |--->|    |    |    |    |    |    |    | 200 OK (REGISTER)
>
> 0005: <UA11	 REGISTER sip:ss.under.test.com:5060 SIP/2.0
> Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bKPUA9435267
> Max-Forwards: 70
> Record-Route: <example.under.test.com;lr>
> From: UA11 <sip:UA11 at under.test.com>;tag=11167
> To: UA11 <sip:UA11 at under.test.com>
> Call-ID: 11167 at air.example.com
> CSeq: 1 REGISTER
> Contact: <sip:UA11 at node.under.test.com;transport=udp>
> Expires: 3600
> Content-Length: 0
>
> 0006: >UA11	 SIP/2.0 401 Unauthorized
> Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bKPUA9435267;received=3FFE:501:FFFF:1:0:0:0:1
> From: UA11 <sip:UA11 at under.test.com>;tag=11167
> To: UA11 <sip:UA11 at under.test.com>;tag=0c0d2af89845c72ddfdc7de2133116df.d47d
> Call-ID: 11167 at air.example.com
> CSeq: 1 REGISTER
> WWW-Authenticate: Digest realm="under.test.com", nonce="4c147cd5d3988992c60c68b56197183f92cdda2f", qop="auth"
> Server: OpenSER (1.3.4-tls (i386/linux))
> Content-Length: 0
>
> 0007: <UA11	 REGISTER sip:ss.under.test.com:5060 SIP/2.0
> Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bKPUA9435268
> Max-Forwards: 70
> Record-Route: <example.under.test.com;lr>
> Authorization: Digest username="UA11", realm="under.test.com", qop=auth, nonce="4c147cd5d3988992c60c68b56197183f92cdda2f", opaque="", nc=00000001, cnonce="6f54a149", uri="sip:ss.under.test.com:5060", response="ed182e82cbc19b5be4f3ee7e6d1f397a"
> From: UA11 <sip:UA11 at under.test.com>;tag=11167
> To: UA11 <sip:UA11 at under.test.com>
> Call-ID: 11167 at air.example.com
> CSeq: 2 REGISTER
> Contact: <sip:UA11 at node.under.test.com;transport=udp>
> Expires: 3600
> Content-Length: 0
>
> 0008: >UA11	 SIP/2.0 200 OK
> Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bKPUA9435268;received=3FFE:501:FFFF:1:0:0:0:1
> Record-Route: <example.under.test.com;lr>
> From: UA11 <sip:UA11 at under.test.com>;tag=11167
> To: UA11 <sip:UA11 at under.test.com>;tag=0c0d2af89845c72ddfdc7de2133116df.abf2
> Call-ID: 11167 at air.example.com
> CSeq: 2 REGISTER
> Date: Sun, 13 Jun 2010 06:33:13 GMT
> Contact: <sip:UA11 at node.under.test.com;transport=udp>;expires=3600
> Server: OpenSER (1.3.4-tls (i386/linux))
> Content-Length: 0
>
> 3  openser configuration file can be seen in "openser.cfg" attachment
> How can I remove the Record-Route field from 200 OK?
>
> --------------------------------------
> Regards!
> Hu xiaoqiang
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>   


-- 
Bogdan-Andrei Iancu
OpenSIPS Bootcamp
20 - 24 September 2010, Frankfurt, Germany
www.voice-system.ro



_______________________________________________
Users mailing list
Users at lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users