1. Essentials Guide
  2. ENUM Based Oracle Communications Unified Session Manager
  3. Limiting AOR Contacts

Limiting AOR Contacts

The Oracle Communications Unified Session Manager allows you to limit the number of contacts that apply to AORs. If the Oracle Communications Unified Session Manager receives a registration request that exceeds the maximum that you configured, it responds with a local response, a 403 Forbidden by default, and does not register the additional contact. The system only rejects registration requests that exceed the maximum. Existing contacts persist normally.

The system checks against the maximum in the following circumstances:

  • A new registration is received
  • The location-update-interval expires
  • A call-id changes (and the forward-reg-callid-change option is enabled)
  • A registrar message sequence number has skipped a number
  • There is any change to the contact list

If the number of contacts in the initial registration exceeds the maximum, the Oracle Communications Unified Session Manager rejects the entire registration. In addition, if you configure this feature while the system is operational, your setting only applies to new registrations.

You configure these maximums on a per-registrar basis. The value ranges from 0-256. The feature is RTC supported.