CDR - Bill Rates based on Outbound Route

Discussion in 'Ideas' started by Futureweb, Jan 18, 2016.

CDR - Bill Rates based on Outbound Route 5 5 4votes
5/5, 4 votes

  1. Futureweb

    Futureweb New Member

    Joined:
    Jun 29, 2015
    Messages:
    163
    Likes Received:
    14
    Hello,

    CDR - Bill Rates are a nice Feature - but not really useable as we can't configure Bill Rates for all of our Outbound Routes.
    We got SIP, ISDN, Mobile Based Outbound Routes ...
    For Example: if I call 05352xxxx from Phone - it will Route through SIP, if I call the same Number from old analog Fax it will route through ISDN ... Call to the same Number - but totally different Bill Rates ...
    So we would need to configure Bill Rates based of Outbound Route.

    Thx, bye from sunny Austria
    Andreas Schnederle-Wagner
     
  2. laurent1

    Joined:
    Dec 8, 2015
    Messages:
    3
    Likes Received:
    0
    Hi

    I'm not sure of the need to configure bill rate by Outbound Rule.
    It would be a better choice to configure by Trunk.

    You can have several outbound rules that points finally to the same trunk.

    ie with my own rules :
    rule : out_FR_with_33
    traps only dialed numbers begining by 0033 and this rule have 2 routes : one by the PSTN gateway and one (backup) by a SIP trunk

    rule : out_FR_w/33
    traps only franch dialed numbers without 0033 and have 2 routes : one by the PSTN gateway without reformating, and one by a SIP trunk with reformating

    So, with one rule you'll have 2 bill rates.

    It would be better to have bill rate by "route" : PSTN Gateways, SIP trunks...
     
  3. Futureweb

    Futureweb New Member

    Joined:
    Jun 29, 2015
    Messages:
    163
    Likes Received:
    14
    Of course you are right!! CDRs should be configureable based on Trunk.
    Guess I was a bit confused when I wrote this post ... ;-)

    Andreas
     
  4. laurent1

    Joined:
    Dec 8, 2015
    Messages:
    3
    Likes Received:
    0
    Hi everybody

    Does anyone know if this feature is "in consideration" for a future release ?
    I've migrated to v15 hoping that.. but no luck..