CONSIDERACIONES GENERALES EN EL DISEÑO DE TRANSFORMADORES PIEZOELECTRICOS

Client Behavior

A client must observe the contents of the Retry-After header field in a 500 or 503 response to a REGISTER or SUBSCRIBE request by deferring a repetition of the request for at least the number of seconds indicated.

OpenScape Voice Behavior

OpenScape Voice may include the Retry-After header field when sending a 500 or 503 response to a REGISTER or SUBSCRIBE request.

5.11.34 Route

Clients and servers must support sending a Route header field in mid-dialog requests as specified in RFC 3261 for a UAC.

Note: The need to send this header field can arise as a result of receiving a

Record-Route header field from an edge proxy.

5.11.35 Server

Client Behavior

A client that supports TLS must take account of the relevant tokens (see Appendix A) if present in this header field in a 2xx response to a REGISTER request.

Server Behavior

If a server sends this header field in a response, it must encode it in accordance with Appendix B.

When sending a 2xx response to a REGISTER request, a server must include this header field if support for TLS connectivity checking is applicable and must include the relevant token(s) in accordance with Appendix A.

5.11.36 Session-Expires (RFC 4028)

Clients and servers must support sending and receipt of the Session-Expires header field.

5.11.37 Subscription-State (RFC 3265)

Clients and servers must support sending and receipt of the Subscription-State header field in accordance with RFC 3265 and with any event packages that are supported.

5.11.38 Supported

Clients and servers must support sending of the Supported header field in relevant requests and 2xx responses when able to support specific options within the context of that request or dialog.

Clients and servers must support receipt of the Supported header field in requests and 2xx responses.

5.11.39 To

Clients and servers must support sending and receipt of the To header field in accordance with RFC 3261.

5.11.40 Unsupported

Clients and servers must be able to include an Unsupported header field when sending a 420 response, in accordance with RFC 3261. Servers and clients that send a Require header field in a request must be able to receive an Unsupported header field in a response.

5.11.41 User-Agent

Client Behavior

If a client sends this header field in a request, it should encode it in accordance with Appendix B, “ABNF Definition of SIP Headers Server and User-Agent”.

OpenScape Voice Behavior

For the capabilities described in this document, there are no OpenScape Voice requirements for this header field.

5.11.42 Via

Clients and servers must support the Via header field in accordance with RFC 3261.

5.0.1 Warning

Client Behavior

For the capabilities described in this document, there are no client requirements for this header field.

OpenScape Voice Behavior

OpenScape Voice may include a Warning: header with a warning code of 399 in some SIP response messages. The intent of the Warning header is to facilitate the debugging of complex scenarios; there is no need for any device to take any special action based on this header field e.g. Warning: 399 <OpenScape Voice IP> "No License"

5.11.43 WWW-Authenticate

Client Behavior

Clients must support receipt of a WWW-Authenticate header field in a 401 response.

OpenScape Voice Behavior

OpenScape Voice supports sending a WWW-Authenticate header field in a 401 response.

5.11.44 X-Siemens-Call-Type

See Sect. 5.14.1.

OpenScape Voice may send this header field with value 'recall-transfer' and clients may support receipt of this header field in accordance with Appendix E. Clients and servers that support media security (see Sect. 8.15) must support sending and receipt of this header field with values 'ST-secure' and 'ST-insecure'. Clients and servers that support directed call Pick-UP (see Sect. 8.5) must support sending and receipt of this header field with value 'DIR_PICK'.

Clients that support group call Pick-UP (see Sect. 8.6) must support receipt of this header field with value 'GROUP_PICK'. Servers that support group call Pick-UP must support sending this header field with value 'GROUP_PICK'.

Clients that support endpoint controlled recording as a recording client (see Sect. 8.16) must support sending of this header field with value 'recording' and MAY support sending this header field with value 'recorded' . Servers that support endpoint controlled recording must support receipt of these values.

Clients that support endpoint controlled recording or server controlled recording (see Sect. 8.16.1 and Sect. 8.16.1.3) must support receipt of this header field with value 'recorded'. Servers that support one or both of these features must support sending this value.

Clients and servers that support 1-way speaker call must support sending and receipt of this header field with value 'speaker-1-way'. Clients that support this 1- way speaker call must auto-answer and carry out special procedures for this feature when this value of this header field is received in an INVITE request. Clients and servers that support 2-way speaker call must support sending and receipt of this header field with value 'speaker-2-way'. Clients that support this 2- way speaker call must auto-answer and carry out special procedures for this feature when this value of this header field is received in an INVITE request.

Note: Special client procedures for 1-way/2-way speaker call involve initially

playing a warning tone to both parties and then periodically playing a reminder tone to both parties.

5.11.45 X-Siemens-CDR

See Sect. 5.14.2.

OpenScape Voice may be configured to accept billing information received in this SIP header field of a SIP INVITE or REFER request and to store such information in the CDR.

Clients may use this header field, if received in an INVITE request, to correlate the incoming call with some other entity (e.g., a CSTA call). In order to receive it, clients must include the x-siemens-cdr option tag when sending a REGISTER request.

5.11.46 X-Siemens-Proxy-State

OpenScape Voice supports sending this header field and clients may support receipt of this header field in accordance with OpenScape Voice survivability procedures. These procedures are described in other Unify specifications that are available upon request, but are outside the scope of this document.

Clients may include this header field to report session quality statistics for audio when sending a BYE request or a 200 response to a BYE request under both of the following conditions:

• Immediately prior to sending the message the call had in a session that includes audio.

• The session duration was not less than the Minimal Session Length specified in Appendix J.

In this situation, the report period comprises the entire session duration, either from the start of the call or from the most recent session change (e.g., remote IP address change, codec change), whichever is later, and relates to the sole or first audio medium in the SDP. The client must include in the header field one instance of each of the parameters specified in Appendix J for this header field, but omitting any parameters for which information is not available.

Notes:

• The provision of statistics for video is outside the scope of this version of this specification.

• The provision of statistics when a session changes during a call (e.g., owing to call transfer by the remote party) is outside the scope of this version of this specification. The main purpose is to provide statistics in the event that a user terminates the call because of bad audio quality, and this will generally result in sending or receipt of a BYE request.

• Where two SDP m-lines are used to represent alternatives for the same medium (e.g., with and without SRTP), the first audio medium might not correspond to the first m=audio line.

OpenScape Voice supports receipt of this header field in a BYE request or a 200 response to a BYE request and interprets the contents as relating to the sole or first audio medium in the SDP. If more than one of instance of this header field is present, OpenScape Voice will use information only from the first one.

5.11.48 X-Siemens-Original-Called-Identity

For Group Call Pick-UP or Directed Call Pick-UP, OpenScape Voice sends an X- Siemens-Original-Called-Identity header field to the picking-up UA containing the identity of the party that is being picked up.

It is supported for the SIP Subscriber (keyset and non-keyset) interface only. If the identity of the party that is picking up the call has its presentation restricted, the X-Siemens-Original-Called-Identity header field is anonymized.

5.11.49 X-Siemens-IID

The purpose of this header field is the conveyance of a network interface identifier (e.g. MAC address) in the course of client registration. This information helps in identifying a device in the network and can assist in locating the device, e.g. for the purpose of emergency calls.

A client that can determine its network interface identifier(s) must support sending this header field in every REGISTER request it sends to OpenScape Voice. OpenScape Voice supports receipt of this header field in REGISTER requests. The header field is defined in Section 5.14.7, “X-Siemens-IID”.

5.11.50 X-Siemens-IL

The purpose of this header is to inform SIP phones when the call enters a network or involves a user that has a lower security classification (a.k.a. impact level). When establishing a call, OpenScape Voice will include this header field in SIP INVITE, 1xx or 200 OK messages sent to SIP clients assigned the feature to notify them that a peer has a lower impact level.

Note: Due to OpenScape Voice redirection features occuring before the call is

answered the impact level may change or even be removed.

Once the call is answered, the SIP UPDATE message is used to notify SIP clients if there is any change to the impact level for the call (or multi-party conference).