SIP converged proxy

SIP in WebSphere 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 functions – SSL termination, Outbound SSL, Client Side Certificates, etc.

• Allows for augmentation by our other products such as WebSphere XD

SIP proxy setup considerations

• A single SIP proxy can front multiple SIP clusters.

• The SIP proxy must be installed into the same cell as the clusters it is fronting, even though it may reside on a different node.

• An IP sprayer is required for load balancing when deploying multiple SIP proxies into a single cell.

• Each SIP proxy must be configured with a default cluster. This 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.

SIP port relationships

When multiple servers, either containers or proxies are on the same host, each container or proxy must be configured with its own port.

SIP cluster routing and the default cluster

• A single SIP proxy can front multiple SIP clusters.

• Each SIP proxy must be configured with a default cluster which is used to route all messages that do not have an associated cluster routing rule.

• You can define cluster routing rules at each proxy. These dictate how messages are routed to the various backend clusters being fronted.

• You can use the default cluster when upgrading applications. (example to follow)

Related tasks