2006
DOI: 10.1109/glocom.2006.193
|View full text |Cite
|
Sign up to set email alerts
|

ISE03-3: Towards Stateless Core: Improving SIP Proxy Scalability

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
2

Citation Types

0
10
0

Year Published

2007
2007
2016
2016

Publication Types

Select...
6
2

Relationship

0
8

Authors

Journals

citations
Cited by 12 publications
(10 citation statements)
references
References 4 publications
0
10
0
Order By: Relevance
“…Balasubramaniyan et al [5] propose a dynamic distribution algorithm to continue to maintain state and yet improve throughput in a proxy farm. Cortes et al [9] propose that SIP proxies in an IMS infrastructure should be configured with stateless and stateful functionality, allowing them to adapt to network and CPU conditions dynamically. Singh et al [25,26,27] present a reliable, scalable and interoperable Internet telephony architecture for user registration, call routing, conferencing and unified messaging using commodity hardware.…”
Section: Related Workmentioning
confidence: 99%
“…Balasubramaniyan et al [5] propose a dynamic distribution algorithm to continue to maintain state and yet improve throughput in a proxy farm. Cortes et al [9] propose that SIP proxies in an IMS infrastructure should be configured with stateless and stateful functionality, allowing them to adapt to network and CPU conditions dynamically. Singh et al [25,26,27] present a reliable, scalable and interoperable Internet telephony architecture for user registration, call routing, conferencing and unified messaging using commodity hardware.…”
Section: Related Workmentioning
confidence: 99%
“…Is has also been proposed to configure a proxy such that state information creation is limited to a fraction of messages (such as INVITE and BYE) based on message type, CPU load and link quality parameters and stateless proxies be used in case of having low packet loss probability or when a reliable transport protocol such as TCP is used [12].…”
Section: B Common Deployment Scenariosmentioning
confidence: 99%
“…Proxy servers which are used for forking calls, NAT traversal, retransmission handling, and accounting, must be configured stateful and are typically located at the edge of network. Instead, the translator and forwarding proxies, located in the core of the network must be configured stateless [12].…”
Section: B Common Deployment Scenariosmentioning
confidence: 99%
“…Current discussion in the IETF [9][16] centers on creating an overload control framework and adopting appropriate new headers to convey additional information beyond a simple 503 response. The approach taken in [5] leverages the fact that throughput of a SIP proxy is higher when processing requests in a transaction-stateless manner, and thus their solution consists of handling a subset of requests statelessly during the onset of congestion, thus trying to avoid overload. In contrast to the aforementioned work, our focus is on creating a mechanism in the form of a programmable engine that enables user-defined policies to be executed efficiently, without modifications to the SIP server.…”
Section: Related Workmentioning
confidence: 99%