Noprint | |||||||||
---|---|---|---|---|---|---|---|---|---|
|
...
Panel | ||||
---|---|---|---|---|
In this section:
|
...
Info |
---|
...
|
...
|
...
The
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
...
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
At a high-level, the following steps are needed for
...
the
Spacevars | ||
---|---|---|
|
...
The
Spacevars | ||
---|---|---|
|
sipRegRelay
which is configurable per Zone level and associated with ingress Zone with respect to message direction.When registration relay functionality is enabled, the following behavior applies:
...
Spacevars | ||
---|---|---|
|
...
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
...
noServiceRouteHdrForEmergencyRegistration
is enabled, even if createServiceRouteHeader
flag is enabled....
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
Contact header and parameters (excluding transport parameter).
Expires header
Note |
---|
Since Contact header always points to either UE or P-CSCF included URI passing the transport parameter to next hop with IBCF being in the path may NOT serve any purpose. |
Note |
---|
Enabling registration relay functionality supersedes any of provisioned values for existing transparency flags, and always passes these headers transparently. |
...
The
Spacevars | ||
---|---|---|
|
...
IBCF can route non-REGISTER requests based on the received route set.
...
Options include:
...
Spacevars | ||
---|---|---|
|
...
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
...
The
Spacevars | ||
---|---|---|
|
...
IBCF can prevent the addition of Service-Routes pointing to IBCF (both internal and external interface IP addresses) in 200 OK response.
Note |
---|
A Service-Route is not inserted in default deployment as IBCF. |
The
...
Spacevars | ||
---|---|---|
|
...
The
Spacevars | ||
---|---|---|
|
...
Header transparency is controlled using the dynamic header Transparency Profile (Note that contact and expires headers are transparently passed by default).
The
...
Spacevars | ||
---|---|---|
|
The flag noServiceRouteHdrForEmergencyRegistration
controls whether
...
the
Spacevars | ||
---|---|---|
|
...
The
Spacevars | ||
---|---|---|
|
headerEncryptionFlags encryptPathHeader/encryptServiceRouteHeader
:...
The
Spacevars | ||
---|---|---|
|
Note |
---|
While the ability to encrypt is configurable, no configuration is required to decrypt messages. When receiving messages from an untrusted network and there is no need to encrypt the messages, by default the corresponding headers that were earlier encrypted are automatically decrypted. |
...
The
Spacevars | ||
---|---|---|
|
...
using the following logic:
...
...
...
The Global command generateSipHeaderEncryptionKeys
generates header encryption keys for AES encryption. The
...
Spacevars | ||
---|---|---|
|
generateSipHeaderEncryptionKeys
command at any time. There is no specific time delay before reissuing the command. The ...
Spacevars | ||
---|---|---|
|
Note |
---|
Generating new keys too frequently may lead to a situation where the |
...
|
Since the
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
...
Spacevars | ||
---|---|---|
|
Pagebreak |
---|