Objects Description¶
Switch
¶
-
class
cdr.models.
Switch
(*args, **kwargs)¶ This defines the Switch
Attributes:
name
- Name of switch.ipaddress
- ipaddress
Name of DB table: voip_switch
HangupCause
¶
-
class
cdr.models.
HangupCause
(*args, **kwargs)¶ This defines the HangupCause
Attributes:
code
- ITU-T Q.850 Code.enumeration
- Enumerationcause
- causedescription
- cause description
Name of DB table: hangup_cause
UserProfile
¶
-
class
user_profile.models.
UserProfile
(*args, **kwargs)¶ This defines extra features for the user
Attributes:
accountcode
- Account name.address
-city
-state
-address
-country
-zip_code
-phone_no
-fax
-company_name
-company_website
-language
-note
-
Relationships:
user
- Foreign key relationship to the User model.userprofile_gateway
- ManyToManyuserprofile_voipservergroup
- ManyToManydialersetting
- Foreign key relationship to the DialerSetting model.
Name of DB table: user_profile
Alarm
¶
AlertRemovePrefix
¶
AlarmReport
¶
Blacklist
¶
Whitelist
¶
VoIPPlan
¶
-
class
voip_billing.models.
VoIPPlan
(*args, **kwargs)¶ VoIPPlans are associated to your clients, this defines the rate at which the VoIP calls are sold to your clients. A VoIPPlan is a collection of VoIPRetailPlans, you can have 1 or more VoIPRetailPlans associated to the VoIPPlan
A client has a single VoIPPlan, VoIPPlan has many VoIPRetailPlans. VoIPRetailPlan has VoIPRetailRates
The LCR system will route the VoIP via the lowest cost carrier.
BanPlan
¶
-
class
voip_billing.models.
BanPlan
(*args, **kwargs)¶ List of Ban Plan which are linked to VoIP Plan
VoIPPlan_BanPlan
¶
-
class
voip_billing.models.
VoIPPlan_BanPlan
(*args, **kwargs)¶ OnetoMany relationship between VoIPPlan & BanPlan
VoIPRetailPlan
¶
-
class
voip_billing.models.
VoIPRetailPlan
(*args, **kwargs)¶ This contains the VoIPRetailRates to retail to the customer. these plans are associated to the VoIPPlan with a ManyToMany relation. It defines the costs at which we sell the VoIP calls to clients.
VoIPRetailPlan will then contain a set of VoIPRetailRates which will define the cost of sending a VoIP call to each destination. The system can have several VoIPRetailPlans, but only the ones associated to the VoIPplan will be used by the client.
VoIPPlan_VoIPRetailPlan
¶
-
class
voip_billing.models.
VoIPPlan_VoIPRetailPlan
(*args, **kwargs)¶ ManytoMany relationship between VoIPPlan & VoIPRetailPlan
VoIPRetailRate
¶
-
class
voip_billing.models.
VoIPRetailRate
(*args, **kwargs)¶ A single VoIPRetailRate consists of a retail rate and prefix at which you want to use to sell a VoIP Call to a particular destination. VoIPRetailRates are grouped by VoIPRetailPlan, which will be then in turn be associated to a VoIPPlan
-
prefix_with_name
()¶ Return prefix with name on Retail Rate listing (changelist_view)
-
voip_retail_plan_name
()¶ Return Retail Plan name on Retail Rate listing (changelist_view)
-
VoIPCarrierPlan
¶
-
class
voip_billing.models.
VoIPCarrierPlan
(*args, **kwargs)¶ Once the retail price is defined by the VoIPPlan, VoIPRetailPlans and VoIPRetailRates, we also need to know which is the best route to send the VoIP how much it will cost, and which VoIP Gateway to use.
VoIPCarrierPlan is linked to the VoIP Plan, so once we found how to sell the service to the client, we need to look at which carrier (Provider) we want to use, The VoIPCarrierPlan defines this.
The system can have several VoIPCarrierPlans, but only the one associated to the VoIPRetailPlan-VoIPPlan will be used to connect the VoIP of the client.
VoIPCarrierRate
¶
-
class
voip_billing.models.
VoIPCarrierRate
(*args, **kwargs)¶ The VoIPCarrierRates are a set of all the carrier rate and prefix that will be used to purchase the VoIP from your carrier, VoIPCarrierRates are grouped by VoIPCarrierPlan, which will be then associated to a VoIPRetailPlan
-
prefix_with_name
()¶ Return prefix with name on Carrier Rate listing (changelist_view)
-
voip_carrier_plan_name
()¶ Return Carrier Plan name on Carrier Rate listing (changelist_view)
-
VoIPPlan_VoIPCarrierPlan
¶
-
class
voip_billing.models.
VoIPPlan_VoIPCarrierPlan
(*args, **kwargs)¶ ManytoMany relationship between VoIPPlan & VoIPCarrierPlan