...
The
maintains registration information using a data structure called Registration Control Block (RCB). When the flag
multipleContactsPerAor is disabled,
the maintains single RCB per Address of Record (AoR) and any existing binding information is overwritten on receipt of REGISTER from a new contact for the same AoR.
This is applicable to non-IMS case as well as IMS cases with Public User Identity not having any associated PUIs (or having an implicit set of size 1).Prior to 5.0.3 release, when multipleContactsPerAor flag is enabled,
verifies the source IP address and port during Registration Control Block (RCB) lookup. If the RCB for routing calls or Out-of-Dialog (OOD) requests originated from a registered Integrated Access Device (IAD), and if multipleContactsPerAor is disabled, ...
| Excerpt |
|---|
is enhanced to support supports validating the source IP address and the port even if multipleContactsPerAor flag is disabled. The also supports locating the RCB using the AoR to perform additional validation on the source IP address and port if the the flag requireRegistration is set to "required" or "required-non-priority". This is applicable for both calls and OOD requests that are originated from the IAD.In case of refresh registration that is originated from a different IP/port, the forwards the request to the registrar and move the sate to "UPDATING". Any calls or OOD requests that are originated from the IAD while the RCB is in updating state must be validated using the previously authenticated IP/port. When the flag multipleContactsPerAor is enabled, SBC maintains different RCBs for each new registration. A registration is considered new when the source IP/port of the REGISTER request is different from earlier registration for the same AoR. Any of the registered UEs may initiate a communication on behalf of the AoR, and the fetches the corresponding RCB based on source IP port of the UE. |
...