Sip Server Ipv4 Rfc3262

NTT Advanced Technology Corporation

SIP Conformance

Test Specification For SIP Server (IPv4)

SIP Extended Operation

(RFC 3262)

Revision 1.0

NTT Advanced Technology Corporation - 1 - SIP Conformance Test Specification

for SIP Server (IPv4) SIP Extended Operation (RFC 3262)

References

This test specification focus on the following SIP related RFCs.

RFC 3262 Reliability of Provisional Responses in the Session Initiation Protocol

---TOC--- References..................................................................................................................... 1

1. Introduction......................................................................................................... 3

2. Common Topology................................................................................................... 4

Figure 1. Topology No.1............................................................................... 4

3. Terminology........................................................................................................... 5

4. Description........................................................................................................... 6

5. Server Test........................................................................................................... 7

5.1. Reliability of Provisional Response............................................... 7

5.1.1. SIP Proxy- Forwarding PRACK request....................................... 7

5.1.2. SIP Proxy- PRACK request without Proxy-Authorization... 19

5.1.3. SIP Proxy- Sending reliable provisional response as UAS

5.1.4. SIP Proxy- Reliability of Probisional Responses for

re-INVITE......................................................................................................... 34

1. Introduction

This test specification focuses on SIP server functionalities described in RFC3262 .

2. Common Topology

Figure 1. Topology No.1 ---+-----------+---------

| UA11

---+---R-------+---------

| NUT(ProxyServer1/Registrar)

---+-----------+---------

3. Terminology NUT : Node Under Test

TN : Tester Node

4. Description

Each test specification consists of following parts.

Category: The Category shows what classification of device must satisfy

the test.

Network Topology: Network Topology which is used in the test.

Procedure: The Procedure describes step-by-step instructions for carrying

out the test.

Judgment: The Judgment describes expected result. If we can observe as same

result as the description of Judgment, the NUT passes the test.

References: The References section contains some parts of specification

5. Server Test

5.1. Reliability of Provisional Response

5.1.1. SIP Proxy- Forwarding PRACK request

Category:

Server Test

Network Topology:

Refer the topology "Figure 1. Topology No.1".

Procedure:

This test sequence is following.

UA11 : Proxy : UA12

| : | : |

|-------:------->| : | 1.INVITE

|<------:--------| : | 2.407

|-------:------->| : | 3.ACK

| : | : |

|-------:------->| : | 4.INVITE

| : |-------:------->| 5.INVITE(*1)

|<------:--------| : | 6.100(*2)

| : | : |

| : |<------:--------| 7.183

|<------:--------| : | 8.183(*3)

| : | : |

|-------:------->| : | 9.PRACK

| : |-------:------->|10.PRACK(*4)

| : | : |

| : |<------:--------|11.200 (PRACK)

|<------:--------| : |12.200 (PRACK)(*5)

| : | : |

| : |<------:--------|13.200 (INVITE)

|<------:--------| : |14.200 (INVITE)(*6)

| : | : |

|-------:------->| : |15.ACK

| : |-------:------->|16.ACK(*7)

|<===============================>| Both Way RTP Media

| : |<------:--------|17.BYE

|<------:--------| : |18.BYE

| : | : |

|-------:------->| : |19.200

| : |-------:------->|20.200

| : | : |

1. UA11 Send INVITE.

2. UA11 Receive 407 Proxy Authentication Required.

3. UA11 Send ACK.

5. UA12 Receive INVITE.

6. UA11 Receive 100 Trying.

7. UA12 Send 183 Session Progress.

8. UA11 Receive 183 Session Progress.

9. UA11 Send PRACK.

10. UA12 Receive PRACK.

11. UA12 Send 200 OK (for PRACK).

12. UA11 Receive 200 OK (for PRACK).

13. UA12 Send 200 OK (for INVITE).

14. UA11 Receive 200 OK (for INVITE).

15. UA11 Send ACK.

16. UA12 Receive ACK.

17. UA12 Send BYE.

18. UA11 Receive BYE.

19. UA11 Send 200.

20. UA12 Receive 200.

Packet Description

4. INVITE UA11 -> NUT

INVITE sip:UA12@under.test.com SIP/2.0

Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74bf9

Max-Forwards: 70

Proxy-Authorization: Digest username="UA11",

realm="under.test.com",

nonce="f84f1cec41e6cbe5aea9c8e88d359", opaque="",

qop=auth, nc=00000004, cnonce="6f54a149",

uri="sip:UA12@under.test.com",

response="b51e504e73af54829e4f2bd7f8dc4654"

From: UA11 <sip:UA11@under.test.com>;tag=9fxced76sl

To: UA12 <sip:UA12@under.test.com>

Call-ID: 3848276298220188511@under.test.com

CSeq: 2 INVITE

Contact: <sip:UA11@node.under.test.com>

Supported: 100rel

Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,PRACK

Content-Type: application/sdp

Content-Length: 151

o=UA11 2890844526 2890844526 IN IP4 192.0.10.10

c=IN IP4 192.0.10.10

m=audio 49172 RTP/AVP 0

a=rtpmap:0 PCMU/8000

5. INVITE NUT -> UA12

INVITE sip:UA12@node11.under.test.com SIP/2.0

Via: SIP/2.0/UDP ss.under.test.com:5060;branch=z9hG4bK2d4790.1

;received=192.0.10.10

Max-Forwards: 69

Record-Route: <sip:ss.under.test.com;lr>

CSeq: 2 INVITE

Supported: 100rel

Content-Length: 151

o=UA11 2890844526 2890844526 IN IP4 192.0.10.10

c=IN IP4 192.0.10.10

6. 100 Trying NUT -> UA11

SIP/2.0 100 Trying

;received=192.0.10.10

CSeq: 2 INVITE

Content-Length: 0

7. 183 Session Progress UA12 -> NUT

SIP/2.0 183 Session Progress

;received=192.0.50.50

;received=192.0.10.10

To: UA12 <sip:UA12@under.test.com>;tag=314159

Contact: <sip:UA12@node11.under.test.com>

Require: 100rel

RSeq: 1

CSeq: 2 INVITE

Content-Length: 147

o=UA12 2890844527 2890844527 IN IP4 192.0.11.11

c=IN IP4 192.0.11.11

8. 183 Session Progress NUT -> UA11

;received=192.0.10.10

Require: 100rel

RSeq: 1

CSeq: 2 INVITE

Content-Length: 147

o=UA12 2890844527 2890844527 IN IP4 192.0.11.11

c=IN IP4 192.0.11.11

9. PRACK UA11 -> NUT

PRACK sip:UA12@node11.under.test.com SIP/2.0

Via: SIP/2.0/UDP node.under.test.com:5060;branch=z9hG4bK74b7699

Max-Forwards: 70

Route: <sip:ss.under.test.com;lr>

CSeq: 3 PRACK

RAck: 1 2 INVITE

Content-Length: 0

10. PRACK NUT -> UA12

Via: SIP/2.0/UDP ss.under.test.com:5060;branch=z9hG4bK721e418c4.122

;received=192.0.10.10

Max-Forwards: 69

CSeq: 3 PRACK

RAck: 1 2 INVITE

Content-Length: 0

11. 200 OK (for PRACK) UA12 -> NUT

SIP/2.0 200 OK

;received=192.0.50.50

;received=192.0.10.10

CSeq: 3 PRACK

Content-Length: 0

12. 200 OK (for PRACK) NUT -> UA11

SIP/2.0 200 OK

;received=192.0.10.10

CSeq: 3 PRACK

Content-Length: 0

13. 200 OK (for INVITE) UA12 -> NUT

SIP/2.0 200 OK

;received=192.0.50.50

;received=192.0.10.10

CSeq: 2 INVITE

Content-Length: 0

14. 200 OK (for INVITE) NUT -> UA11

SIP/2.0 200 OK

;received=192.0.10.10

CSeq: 2 INVITE

Content-Length: 0

15. ACK UA11 -> NUT

ACK sip:UA12@node11.under.test.com SIP/2.0

Max-Forwards: 70

CSeq: 2 ACK

Content-Length: 0

16. ACK NUT -> UA12

;received=192.0.10.10

Max-Forwards: 69

CSeq: 2 ACK

Content-Length: 0

Judgment:

*1:INVITE request from NUT to UA12.

As a SIP Message,

See generic_message.txt

As a SIP request,

- Request-Line:

See generic_forward_from-UA11.txt

See generic_forward_R-URI_non-responsible-domain.txt

- Headers:

- outside of a dialog

See generic_forward_request.txt

* Supported

Must exist.

Must equal as that in the message from UA11.

Must include "100rel". [RFC3262-4-2]

- Bodies:

*2:100 response from NUT to UA11.(Optional)

As a SIP Message,

As a SIP response,

- Status-Line:

See generic_make_response.txt

Status-Code: Must be "100".

- Headers:

via-received: Must be added if the host portion of the "sent-by"

parameter contains a domain name. [RFC3261-18-27]

via-received: Must contain the source address from which the packet

was received. [RFC3261-18-28]

* RSeq:

Must not exist. [RFC3262-3-3]

* Require(if exists)

Must not include 100rel. [RFC3262-3-3]

*3:183 response from NUT to UA11.

As a SIP Message,

As a SIP response,

- Status-Line:

- Headers:

See generic_forward_response.txt

* Require

Must exist and include "100rel". [RFC3262-3-9]

* RSeq

Must exist. [RFC3262-3-10]

response-num: Must be between 1 and 2**31-1. [RFC3262-3-11]

- Bodies:

*4:PRACK request from NUT to UA12.

As a SIP Message,

As a SIP request,

- Request-Line:

See generic_forward_R-URI_responsible-domain.txt

- Headers:

* RAck

Must exist.

* Require

- Bodies:

*5:200 response for PRACK from NUT to UA11.

As a SIP Message,

As a SIP response,

- Status-Line:

- Headers:

- Bodies:

*6:200 response for INVITE from NUT to UA11.

As a SIP Message,

As a SIP response,

- Status-Line:

- Headers:

- Bodies:

*7:ACK request from NUT to UA12.

As a SIP Message,

As a SIP request,

- Request-Line:

- Headers:

* Require

- Bodies:

References:

[rfc3262.txt]

3 UAS Behavior

A UAS MUST NOT attempt to send a 100 (Trying) response reliably.

Only provisional responses numbered 101 to 199 may be sent reliably.

If the request did not include either a Supported or Require header

field indicating this feature, the UAS MUST NOT send the provisional

response reliably.

5.1.2. SIP Proxy- PRACK request without Proxy-Authorization

Category:

Server Test

Network Topology:

Procedure:

UA11 : Proxy : UA12

| : | : |

|-------:------->| : | 1.INVITE

|<------:--------| : | 2.407

|-------:------->| : | 3.ACK

| : | : |

|-------:------->| : | 4.INVITE

| : |-------:------->| 5.INVITE

|<------:--------| : | 6.100

| : | : |

| : |<------:--------| 7.183

|<------:--------| : | 8.183

| : | : |

|-------:------->| : | 9.PRACK

|<------:--------| : |10.407(*1)

| : | : |

|-------:------->| : |11.PRACK

| : |-------:------->|12.PRACK

| : | : |

| : |<------:--------|13.200 (PRACK)

|<------:--------| : |14.200 (PRACK)

| : | : |

| : |<------:--------|15.200 (INVITE)

|<------:--------| : |16.200 (INVITE)

| : | : |

|-------:------->| : |17.ACK

| : |-------:------->|18.ACK

| : |<------:--------|19.BYE

|<------:--------| : |20.BYE

| : | : |

|-------:------->| : |21.200

| : |-------:------->|22.200

| : | : |

3. UA11 Send ACK.

9. UA11 Send PRACK.

11. UA11 Send PRACK.

17. UA11 Send ACK.

19. UA12 Send BYE.

21. UA11 Send 200.

Packet Description

Max-Forwards: 70

CSeq: 3 PRACK

RAck: 1 2 INVITE

Content-Length: 0

10. 407 Proxy Authentication Required NUT -> UA11

SIP/2.0 407 Proxy Authentication Required

;received=192.0.10.10

CSeq: 3 PRACK

Proxy-Authenticate: Digest realm="under.test.com", qop="auth",

nonce="f84f1cec41e6cbe5aea9c8e88d359",

opaque="", stale=FALSE, algorithm=MD5

Content-Length: 0

Max-Forwards: 70

CSeq: 4 PRACK

RAck: 1 2 INVITE

Content-Length: 0

Judgment:

As a SIP Message,

As a SIP response,

- Status-Line:

- Headers:

See generic_proxy-auth.txt

via-received: Must contain the source address from which the packet was

received. [RFC3261-18-28]

References:

[rfc3262.txt]

9 Security Considerations

The PRACK request can be injected by attackers to force

retransmissions of reliable provisional responses to cease. As these

responses can convey important information, PRACK messages SHOULD be

authenticated as any other request. Authentication procedures are

specified in RFC 3261.

5.1.3. SIP Proxy- Sending reliable provisional response as UAS

Category:

Server Test

Network Topology:

Procedure:

UA11 : Proxy : UA12

| : | : |

|-------:------->| : | 1.INVITE

|<------:--------| : | 2.407

|-------:------->| : | 3.ACK

| : | : |

|-------:------->| : | 4.INVITE

| : |-------:------->| 5.INVITE

|<------:--------| : | 6.100

| : | : |

|<------:--------| : | 7.183(*1)

|-------:------->| : | 8.PRACK

|<------:--------| : | 9.200 (PRACK)(*2)

| : | : |

| : |<------:--------|10.183

|<------:--------| : |11.183

| : | : |

|-------:------->| : |12.PRACK

| : |-------:------->|13.PRACK(*3)

| : | : |

| : |<------:--------|14.200 (PRACK)

|<------:--------| : |15.200 (PRACK)

| : | : |

| : |<------:--------|16.200 (INVITE)

|<------:--------| : |17.200 (INVITE)

| : | : |

|-------:------->| : |18.ACK

| : |-------:------->|19.ACK

| : |<------:--------|20.BYE

|<------:--------| : |21.BYE

| : | : |

|-------:------->| : |22.200

| : |-------:------->|23.200

| : | : |

3. UA11 Send ACK.

8. UA11 Send PRACK.

18. UA11 Send ACK.

20. UA12 Send BYE.

22. UA11 Send 200.

Packet Description

INVITE sip:UA12@under.test.com SIP/2.0

Max-Forwards: 70

CSeq: 2 INVITE

Supported: 100rel

Content-Length: 151

o=UA11 2890844526 2890844526 IN IP4 192.0.10.10

c=IN IP4 192.0.10.10

;received=192.0.10.10

Max-Forwards: 69

CSeq: 2 INVITE

Supported: 100rel

Content-Length: 151

o=UA11 2890844526 2890844526 IN IP4 192.0.10.10

c=IN IP4 192.0.10.10

SIP/2.0 100 Trying

;received=192.0.10.10

CSeq: 2 INVITE

Content-Length: 0

;received=192.0.10.10

To: UA12 <sip:UA12@under.test.com>;tag=px3012

Require: 100rel

RSeq: 1

CSeq: 2 INVITE

Content-Length: 0

Max-Forwards: 70

CSeq: 3 PRACK

RAck: 1 2 INVITE

Content-Length: 0

SIP/2.0 200 OK

;received=192.0.10.10

CSeq: 3 PRACK

Content-Length: 0

10. 183 Session Progress UA12 -> NUT

;received=192.0.50.50

;received=192.0.10.10

Require: 100rel

RSeq: 1

CSeq: 2 INVITE

Content-Length: 147

o=UA12 2890844527 2890844527 IN IP4 192.0.11.11

c=IN IP4 192.0.11.11

;received=192.0.10.10

Require: 100rel

RSeq: 1

CSeq: 2 INVITE

Content-Length: 147

o=UA12 2890844527 2890844527 IN IP4 192.0.11.11

c=IN IP4 192.0.11.11

Max-Forwards: 70

CSeq: 4 PRACK

RAck: 1 2 INVITE

Content-Length: 0

/* To tag is different from that of 7.183 response, */

/* and is same as that of 10.183 response. */

13. PRACK NUT -> UA12

;received=192.0.10.10

Max-Forwards: 69

CSeq: 4 PRACK

RAck: 1 2 INVITE

Content-Length: 0

14. 200 OK (for PRACK) UA12 -> NUT

SIP/2.0 200 OK

;received=192.0.50.50

;received=192.0.10.10

CSeq: 4 PRACK

Content-Length: 0

SIP/2.0 200 OK

;received=192.0.10.10

CSeq: 4 PRACK

Content-Length: 0

16. 200 OK (for INVITE) UA12 -> NUT

SIP/2.0 200 OK

;received=192.0.50.50

;received=192.0.10.10

CSeq: 2 INVITE

Content-Length: 0

17. 200 OK (for INVITE) NUT -> UA11

SIP/2.0 200 OK

;received=192.0.10.10

CSeq: 2 INVITE

Content-Length: 0

18. ACK UA11 -> NUT

Max-Forwards: 70

CSeq: 2 ACK

Content-Length: 0

19. ACK NUT -> UA12

;received=192.0.10.10

Max-Forwards: 69

CSeq: 2 ACK

Content-Length: 0

Judgment:

As a SIP Message,

As a SIP response,

- Status-Line:

- Headers:

* Require

Must exist and include "100rel". [RFC3262-3-9]

* RSeq

Must exist. [RFC3262-3-10]

response-num: Must be between 1 and 2**31-1. [RFC3262-3-11]

*2:200 response for PRACK from NUT to UA11.

As a SIP Message,

As a SIP response,

- Status-Line:

- Headers:

*3:PRACK request from NUT to UA12.

As a SIP Message,

As a SIP request,

- Request-Line:

- Headers:

See generic_forward_message.txt

* RAck

Must exist.

* Require

- Bodies:

See generic_forward_message.txt

References:

[rfc3262.txt]

3 UAS Behavior

An element that can act as a proxy can also send reliable provisional

responses. In this case, it acts as a UAS for purposes of that

transaction. However, it MUST NOT attempt to do so for any request

that contains a tag in the To field. That is, a proxy cannot

generate reliable provisional responses to requests sent within the

context of a dialog. Of course, unlike a UAS, when the proxy element

receives a PRACK that does not match any outstanding reliable

provisional response, the PRACK MUST be proxied.

(snip)

Retransmissions of the reliable provisional response cease when a

matching PRACK is received by the UA core. PRACK is like any other

request within a dialog, and the UAS core processes it according to

the procedures of Sections 8.2 and 12.2.2 of RFC 3261. A matching

PRACK is defined as one within the same dialog as the response, and

whose method, CSeq-num, and response-num in the RAck header field

match, respectively, the method from the CSeq, the sequence number

from the CSeq, and the sequence number from the RSeq of the reliable

provisional response.

5.1.4. SIP Proxy- Reliability of Probisional Responses for

re-INVITE

Category:

Server Test

Network Topology:

Procedure:

UA11 : Proxy : UA12

| : | : |

|-------:------->| : | 1.INVITE

|<------:--------| : | 2.407

|-------:------->| : | 3.ACK

| : | : |

|-------:------->| : | 4.INVITE

| : |-------:------->| 5.INVITE

|<------:--------| : | 6.100

| : | : |

| : |<------:--------| 7.183

|<------:--------| : | 8.183

| : | : |

|-------:------->| : | 9.PRACK

| : |-------:------->|10.PRACK

| : | : |

| : |<------:--------|11.200 (PRACK)

|<------:--------| : |12.200 (PRACK)

| : | : |

| : |<------:--------|13.200 (INVITE)

|<------:--------| : |14.200 (INVITE)

| : | : |

|-------:------->| : |15.ACK

| : |-------:------->|16.ACK

|-------:------->| : |17.INVITE

| : |-------:------->|18.INVITE

|<------:--------| : |19.100

| : | : |(*1)

| : |<------:--------|20.183

|<------:--------| : |21.183

| : | : |

|-------:------->| : |22.PRACK

| : |-------:------->|23.PRACK

| : | : |

| : |<------:--------|24.200 (PRACK)

|<------:--------| : |25.200 (PRACK)

| : | : |

| : |<------:--------|26.200 (INVITE)

|<------:--------| : |27.200 (INVITE)

|-------:------->| : |28.ACK

| : |-------:------->|29.ACK

| : |<------:--------|30.BYE

|<------:--------| : |31.BYE

| : | : |

|-------:------->| : |32.200

| : |-------:------->|33.200

| : | : |

3. UA11 Send ACK.

9. UA11 Send PRACK.

15. UA11 Send ACK.

28. UA11 Send ACK.

30. UA12 Send BYE.

32. UA11 Send 200.

Packet Description

Max-Forwards: 70

CSeq: 5 INVITE

Supported: 100rel

Content-Length: 151

o=UA11 2890844526 2890844527 IN IP4 192.0.10.10

c=IN IP4 192.0.10.10

a=sendonly

;received=192.0.10.10

Max-Forwards: 69

CSeq: 5 INVITE

Supported: 100rel

Content-Length: 151

o=UA11 2890844526 2890844527 IN IP4 192.0.10.10

c=IN IP4 192.0.10.10

a=sendonly

SIP/2.0 100 Trying

;received=192.0.10.10

CSeq: 5 INVITE

Content-Length: 0

Judgment:

Must not be transmitted. [RFC3262-3-5]

References:

[rfc3262.txt]

3 UAS Behavior

An element that can act as a proxy can also send reliable provisional

responses. In this case, it acts as a UAS for purposes of that

transaction. However, it MUST NOT attempt to do so for any request

that contains a tag in the To field. That is, a proxy cannot

generate reliable provisional responses to requests sent within the

context of a dialog. Of course, unlike a UAS, when the proxy element

receives a PRACK that does not match any outstanding reliable

provisional response, the PRACK MUST be proxied.

Sip Server Ipv4 Rfc3262

Documents

Transcript of Sip Server Ipv4 Rfc3262

iS3000 and SIP@Net - uk.nec.com · (VoIP) services, NEC’s offer includes the SIP@Net server. This SIP@Net server provides a powerful server based platform for IP communication services.

2833 Bwp Sip Server Screen

Configuring Virtual SIP Server

EZVMS-6800 IPV4+V6 Dual IP Centrex Server · Support IPv4 and IPv6 SIP Calls Simultaneously Support Multi-Company & Multi-Language Auto Attendant Service/AA Call Flow Editor Voice

Web Call Server - Call Flow - Flashphoner · SIP Server SIP proxy-server, PBX, IMS or other SIP equipment with the support for SIP-protocol. Synonyms: SIP provider, SIP server. WCS

Inferring Internet Server IPv4 and IPv6 Address · PDF fileInferring Internet Server IPv4 and IPv6 Address Relationships Robert Beverly, Arthur Berger∗, Nicholas Weaver†, Larry

SIP Proxy Server - PLANETplanet.com.tw/storage/products/485/em-sip50v1[1].pdf · 2007-11-22 · SIP-50 SIP Proxy Server User’s Manual 1.3 SIP Proxy Server Front View - Front View:

LAB SIP Server Installation & Testing

SIP Proxy Server...SIP-50 SIP Proxy Server User’s Manual 1.4 SIP Proxy Server Rear Panel - Rear View: Console Port Power On / Off switch LAN Port Port Function Power This is where

SIP Server Tech Overview - StarTrinitystartrinity.com/VoIP/Resources/sip226.pdf · 2 RADVISION SIP Server Technical Overview What is a SIP Server? In addition to the functionality

JBoss Communications Platform 5.1 SIP Servlets Server …€¦ · SIP Servlets Server User Guide ... High-Availability: SIP Servlets Server Load Balancing, Clustering and Failover

Windows Server 2012 Test Lab Guide - Single Server Mixed IPv4 and IPv6

Communication Server 1000 systems T1/PRI Certified SIP .../media/catalyst... · Certified SIP Gateways, ... (CM) and Aura SIP Enablement Server (SES) ... • Simplified configuration

SIP Feature Server Administration Guide

IPv6/IPv4 Translation for SIP Applications-acpang/course/voip_2004/... · 2005-02-24 · IPv6/IPv4 Translation for SIP Applications-Socket-Layer Translator and SIPv6 Translator Whai-En

Radvision Sip Server Technical Overview

BEAWebLogic SIP Server · BEAWebLogic SIP Server ™ Configuration Reference Manual Version 3.0 Revised: December 13, 2006

Configuring a Net2 Entry panel as a SIP client Notes/AN1132.pdf · 2 AN1132 Net2 Network The SIP server uses IPv4 addressing for communication and so we need to obtain an IPv4 address

MCP SIP Audio Server Basics

Locating SIP Server & ENUM