The Experts below are selected from a list of 57 Experts worldwide ranked by ideXlab platform
Mary Barnes - One of the best experts on this subject based on the ideXlab platform.
-
SIP "cause" URI Parameter for Service Number Translation
2017Co-Authors: Marianne Mohali, Mary BarnesAbstract:RFC 4458 (regarding SIP URIs for applications) defines a "cause" URI parameter, which may appear in the Request-URI of a SIP request, that is used to indicate a reason why the request arrived to the User Agent Server (UAS) receiving the message. This document updates RFC 4458 by creating a new predefined value for the "cause" URI parameter to cover service number translation for cases of retargeting due to specific service action leading to the translation of a called service access number. This document also provides guidance, which was missing in RFC 4458, for using the "cause" URI parameter within the History-Info header field, since this use is mandatory in some IP networks' implementations.
-
Session Initiation Protocol (SIP) Cause URI parameter for Service Number translation
2016Co-Authors: Marianne Mohali, Mary BarnesAbstract:RFC4458 defines a "cause" URI parameter, which may appear in the Request-URI of a SIP request, that is used to indicate a reason why the request arrived to the User Agent Server (UAS) receiving the message. This specification creates a new predefined value for the "cause" URI parameter to cover service number translation for cases of retargeting due to specific service action leading to the translation of a called service access number. This document updates RFC4458.
Marianne Mohali - One of the best experts on this subject based on the ideXlab platform.
-
SIP "cause" URI Parameter for Service Number Translation
2017Co-Authors: Marianne Mohali, Mary BarnesAbstract:RFC 4458 (regarding SIP URIs for applications) defines a "cause" URI parameter, which may appear in the Request-URI of a SIP request, that is used to indicate a reason why the request arrived to the User Agent Server (UAS) receiving the message. This document updates RFC 4458 by creating a new predefined value for the "cause" URI parameter to cover service number translation for cases of retargeting due to specific service action leading to the translation of a called service access number. This document also provides guidance, which was missing in RFC 4458, for using the "cause" URI parameter within the History-Info header field, since this use is mandatory in some IP networks' implementations.
-
Session Initiation Protocol (SIP) Cause URI parameter for Service Number translation
2016Co-Authors: Marianne Mohali, Mary BarnesAbstract:RFC4458 defines a "cause" URI parameter, which may appear in the Request-URI of a SIP request, that is used to indicate a reason why the request arrived to the User Agent Server (UAS) receiving the message. This specification creates a new predefined value for the "cause" URI parameter to cover service number translation for cases of retargeting due to specific service action leading to the translation of a called service access number. This document updates RFC4458.
Gonzalo Camarillo - One of the best experts on this subject based on the ideXlab platform.
-
Re-INVITE and Target-refresh Request Handling in the Session Initiation Protocol (SIP)
2011Co-Authors: Gonzalo Camarillo, Christer HolmbergAbstract:In this document, we clarify the handling of re-INVITEs in SIP. We clarify in which situations a UAS (User Agent Server) should generate a success response and in which situations a UAS should generate an error response to a re-INVITE. Additionally, we clarify issues related to target-refresh requests.
-
Media State under Preconditions in the Session Initiation Protocol (SIP)
2010Co-Authors: Gonzalo Camarillo, Jouni Mäenpää, Gao YangAbstract:In this document, we describe how a UAS (User Agent Server) involved in a session modification can explicitly signal the point where the new session parameters start being used. Explicitly signalling such a change in the session parameters can be useful so that network intermediaries such as B2BUAs (Back-to-back User Agents) have a clear picture of the session's state at every point.
-
Re-INVITE Handling in the Session Initiation Protocol (SIP)
2009Co-Authors: Gonzalo CamarilloAbstract:In this document, we clarify the handling of re-INVITEs in SIP. We clarify in which situations a UAS (User Agent Server) should generate a success response and in which situations a UAS should generate an error response to a re-INVITE. Additionally, we clarify issues related to target refresh requests.
-
Extending the Session Initiation Protocol Reason Header with Warning Codes
2005Co-Authors: Gonzalo Camarillo, Jani HautakorpiAbstract:This document specifies a new protocol value, called 'SIP- Warning', for the Session Initiation Protocol (SIP) Reason header. The values for the name space of 'SIP-Warning' are taken from the Warning codes (warn-codes) of SIP. In addition, this document also defines one new SIP Warning code to be used in situations where User Agent Server (UAS) does not accept calls from an anonymous source.
Victor Pascual - One of the best experts on this subject based on the ideXlab platform.
-
A Taxonomy of Session Initiation Protocol (SIP) Back-to-Back User Agents
2013Co-Authors: Hadriel Kaplan, Victor PascualAbstract:In many SIP deployments, SIP entities exist in the SIP signaling path between the originating and final terminating endpoints, which go beyond the definition of a SIP proxy, performing functions not defined in Standards Track RFCs. The only term for such devices provided in RFC 3261 is for a Back-to-Back User Agent (B2BUA), which is defined as the logical concatenation of a SIP User Agent Server (UAS) and User Agent Client (UAC). There are numerous types of SIP B2BUAs performing different roles in different ways; for example, IP Private Branch Exchanges (IPBXs), Session Border Controllers (SBCs), and Application Servers (ASs). This document identifies several common B2BUA roles in order to provide taxonomy other documents can use and reference.
Yazdan Nasr Harandi - One of the best experts on this subject based on the ideXlab platform.
-
Scenarios for Testing Reliable Transmission of Provisional Responses in SIP User Agent
2008Co-Authors: Nasrin Hezareh Moghadam, Hamideh Sabaei, Mohammad Dindoost, Yazdan Nasr HarandiAbstract:Summary In this paper, we present testing scenarios for reliable transmission of provisional responses in SIP User Agent. Several test scenarios for different functionalities of SIP User Agent have been presented by European Telecommunications Standards Institute (ETSI). However, no scenarios have been given for reliable transmission of provisional responses. Scenarios in this paper are got from the finite state machines designed in the paper for both SIP User Agent Server and User Agent client. State machines are designed according to the behavior of SIP User Agent client and Server. These behaviors are observed from the functionalities and conditions adopted from accredited RFCs and standards of SIP protocol. A major characteristic of this set of scenarios is that it is optimum in terms of the number, since the designed state machines are minimal in terms of the states. Finally, these tests are executable in a real lab environment as are to be executed in Iran Telecommunication Research Center (ITRC)'s Next Generation Network (NGN) Pilot lab.
