Closed freddy36 closed 5 years ago
It is normal as i can not force it for the setup, but it is needed for routing. I think to make it evolve and to use genering ratecard for did attached to customer. What do you think about that ?
there are probably good use case for both design choices (attaching the ratecard to the customer vs attaching it to the DID route). Attaching it to the DID route (the current design) is probably the more flexible solution.
If it's not possible to change the freeswitch script to handle calls without ratecards I suggest to add a form check to make sure prov_ratecard and cust_ratecard is set if customer is configured.
i thought to add a choice to use free did (customer and provider). With a boolean, so no needs of ratecards in this case ! My customers use the same prices for all did (depending on prefix) so associating a ratecard to a customer and a provider is simple for them. I prefer always simple things. What do you think about that ?
99% of our customers don't pay anything for DIDs so a simple free checkbox (or default free if ratecards are not configured) would make things simpler for us. Moving the ratecard associations to the provider/customer sounds ok to me too.
The simplest solution for me would be not to use ratecards at all for DIDs, instead configure the buy/sell charges directly at the DID level. That's probably the most user friendly way (But would break some (future) use cases). Personally we would prefer to keep it like it is or just move the ratecard associations to provider/customer. (or hide them from the GUI)
OK, i will change this
i will publish it in the same time of outbound calls modifications. I am moving this part from FS script to kamailio.
Done in the next release
Currently the django DID model doesn't require Provider rate plan or Customer rate plan to be set.
But if they aren't set freeswitch routing fails because it generates the following invalid SQL queries with empty ID values:
Note the
AND rc.id = ''
The same happens for provider rates.I worked around this by creating corresponding dummy ratecards but I personally would prefer to fix the freeswitch script to support inbound calls without ratecard.