Table of Contents |
---|
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
A SIP registrar is a server in an SIP network that accepts SIP REGISTER requests. The
...
Spacevars | ||
---|---|---|
|
In the owner mode the
...
Spacevars | ||
---|---|---|
|
In the proxy mode the AOR is owned by another network device and the
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
The
...
Spacevars | ||
---|---|---|
|
The figure below illustrates how registration is processed in the Forward After Local Processing mode.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Under normal circumstances, when a device registers with the
...
Spacevars | ||
---|---|---|
|
...
Note | ||
---|---|---|
| ||
If an Outbound Proxy is specified in the SIP Signaling Group, it takes precedence over the SIP Server. Therefore, proxy registration is moot. |
...
...
Caption | ||||
---|---|---|---|---|
| ||||
When Forward After Registration is the selected SIP mode and the SIP server becomes unavailable, the local registrar maintains the call bindings. However, for this to occur, Routing Tables and Cause Codes must be properly configured on the
...
Spacevars | ||
---|---|---|
|
In order for the fail-over scenario to function properly alternate call routes must be defined.
The primary call route entry of the Call Routing Table in the Signaling group must specify a Cause Code Reroute, defined under the Telephony Mapping Tables section of the UI.
The subsequent call route entry must specify the Destination Type as Registrar Table.
Pagebreak |
---|