Page History

...

Authenticating New Connections by Registrar

The SBC forwards the refresh register to the Registrar under the following conditions:

• Change in the source IP address
• Change in the source Port when Integrated Access Device (IAD) is behind the Network Address Translation (NAT)

When an IAD re-establishes a TCP connection, it uses a different source port and same IP address. SBC forwards the refresh register only if the IAD is configured behind the NAT, leaving the new connection unauthenticated.

As of release 5.0.3, SIP Service Group logic is modified to forward a register request when a change in connection parameter is detected under the following conditions, and the IAD is not required to be behind NAT. By forwarding the refresh register, the Registrar can authenticate the user by sending a 401 response.

• Change in connection ID
• Change in source IP address or port

Using New Connection for Existing Calls/Subscriptions

Currently, after a failover if the IAD reestablishes the connection and sends a refresh REGISTER, SBC does not use the connection for mid dialog requests towards the IAD for both calls and subscription. With the implementation of this feature, SBC supports to use the new connection for sending in-dialog requests for the existing calls and subscriptions towards the IAD.

Quick Re-registration on Alternate SIP Server When Primary Server is Down

...