Skip to Content
Odoo model · Enterprise

voip.requirement

VoIP Regulatory Requirement. Defined in module voip; exists in Odoo 20. Across the upgrade steps we tracked: 0 fields added, 0 removed, 0 renamed.

  1. Odoo 16 not covered
  2. Odoo 17 not covered
  3. Odoo 18 not present
  4. Odoo 19 not present
  5. Odoo 20 voip

This is an Enterprise model: Odoo 16 and 17 Enterprise sources are not part of the data, so those versions show as not covered.

Odoo 19 to 20

Community + Enterprise All changes in this step

New model in Odoo 20.

All fields declared on voip.requirement (27)

Fields this model declares itself in any version, with the versions they exist in. Inherited fields (mail.thread and other mixins) are on the parent model's page.

present not present not covered (Enterprise, Odoo 16 and 17)

Show all 27 fields
FieldTypeLabelModule1617181920
action_first_namecharvoipE
action_last_namecharvoipE
action_verification_urlcharvoipE
address_business_namecharBusiness NamevoipE
address_citycharCityvoipE
address_country_idmany2one res.countryCountryvoipE
address_extendedcharApt/Suite/FloorvoipE
address_first_namecharFirst NamevoipE
address_is_filledbooleanAddress FilledvoipE
address_last_namecharLast NamevoipE
address_phonecharPhone NumbervoipE
address_postal_codecharPostal CodevoipE
address_statecharState/ProvincevoipE
address_streetcharStreet AddressvoipE
descriptiontextvoipE
did_number_idmany2one voip.did.numbervoipE
document_filebinaryvoipE
exampletextvoipE
field_typeselectionTypevoipE
is_fulfilledbooleanFulfilledvoipE
namecharvoipE
requirement_group_idsmany2many voip.requirement.groupvoipE
review_statusselectionvoipE
telnyx_address_idcharvoipE
telnyx_document_idcharvoipE
telnyx_requirement_idcharvoipE
text_valuecharvoipE

Related models

Linked by its relational fields: res.countryvoip.did.numbervoip.requirement.group

Coverage. Odoo 16 to 17 and 17 to 18 compare Community modules only (the Enterprise 16 and 17 sources are not available to us). Odoo 18 to 19 and 19 to 20 include Community and Enterprise modules. Everything here comes from a static read of the Odoo source code: a field counts as removed only when no parent model, mixin or delegated model still provides it. Fields created dynamically at run time can be missed, and entries we could not confirm are marked as low confidence.