CSS Stylesheet |
---|
img.confluence-embedded-image { display: inline-block !important; } |
Add_workflow_for_techpubs AUTH1 cclemetsonUserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} JIRAIDAUTH SYM-24006 REV5 cclemetsonUserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} REV6 cclemetsonUserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} REV3 pdeepakUserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cef30cd0, userName='null'} REV1 sarkasaliUserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc2d0797, userName='null'}
...
Failover SIP registration is for redundant SIP servers within a SIP Server Table (either multiple entries, or DNS SRV that returns multiple servers). If the SBC registration to the primary SIP Server fails, becomes unreachable, or the registrations expires and a re-register fails, the SBC attempts to register to the secondary SIP Server and continues calls to the server. Failover SIP registration is completed according to the Priority order of the SIP Servers. Fallback will occur if the primary SIP Server becomes reachable again.
Failover to another SIP server will also occur if the SBC receives the following SIP response code from an active SIP server for calls: 4xx, 5xx, or 6xx.
Note |
---|
When Load Balancing is configured as Priority: Register Active Only in the SIP Signaling Group, a SIP Failover Cause Code should be selected under Mapping Tables in the SIP Signaling Group. If a SIP Failover Cause Code is selected, Failover occurs for timeout cases and failure response codes. If a SIP Failover Cause Code is not selected, Failover occurs only for timeout cases and not for failure response codes. |
Refer to Creating and Modifying Entries in SIP Server Tables for configuring Failover SIP Registration.
...
Include Page | ||||||
---|---|---|---|---|---|---|
|
Children Display | ||||
---|---|---|---|---|
|
Pagebreak |
---|