Outbound Registration Binding Processing
An outbound registration binding is created between the AoR, instance-id, reg-id, Contact URI, and other contact parameters. This binding also stores the Path: header.
Matching re-registrations update the local registration cache as expected. REGISTER messages are replied to including a Require: header containing the outbound option-tag.
If the Oracle Communications Core Session Manager receives requests for the same AOR with some registrations with reg-id + instance-id and some without them, the Oracle Communications Core Session Manager will store them both as separate Contacts for the AOR; The AoR+sip.instance+reg-id combination becomes the key to this entry.