SIP converged proxy

SIP converged proxy

SIP in WebSphere Application Server offers a converged proxy.

The SIP converged proxy:

Handles SIP and HTTP.
Provides application level session failover, regardless of protocol.
Fronts clusters of containers, SIP or HTTP.
Provides a highly scalable I/O concentration.
Handles session affinity.
Provides a framework for extending the base functions of proxy using an API consistent with proxy flows (Proxy Filter Layer).
Contains support for failover and load balancing.
Provides first pass protocol validation.
Provides a framework for secure proxy server functions, such as SSL termination, Outbound SSL, and Client Side Certificates.
Allows for augmentation by our other products, such as WebSphere Extended Deployment.
Provides DMZ Secure Proxy Server for IBM WAS support.

SIP proxy setup considerations

A single SIP proxy server can front multiple SIP clusters.
An IP sprayer is required for load balancing when deploying multiple SIP proxies into a single cell.
Each SIP proxy server must be configured with a default cluster. This default cluster is used to route inbound messages that do not match a cluster routing rule.
When deploying converged applications, both HTTP and SIP should be enabled on the proxy server .
SIP proxy servers can be clustered.

SIP port relationships

When multiple application servers, or proxy servers are on the same host, each server must be configured with its own port.

SIP cluster routing and the default cluster

A single SIP proxy server can front multiple SIP clusters.
Each SIP proxy server must be configured with a default cluster which is used to route all messages that do not have an associated cluster routing rule.
We can define cluster routing rules for each proxy server. These rules dictate how messages are routed to the various backend clusters being fronted.
By changing the default cluster, we can have a SIP proxy server reroute messages to a new cluster containing upgraded versions of our deployed applications.

Browse all SIP topics