System information

4.5.13. Notes
Call forward billing: 2 cdr record will be generated. A->B and B->C
Call forward from IVR: one cdr will be generated. Whether we charge the call to the IVR or only bill the forwarded call can be controlled by
“resetdurationonfwd”
Call transfer by SIP signaling: the second call is completely different from the first call. Billing goes normally (2 calls)
Call transfer with dtmf (*5*): only one call leg is billed
Conference with dtmf (*1*): separate cdr will be generated for all call legs
Conference by sip: technically separate calls. Will be billed normally (2 cdr)
Call forwarding from IVR (2-leg calls):
CDR’s generated based on “ivrbilling” global and user setting: 0: one CDR including the forwarded call, 1: load duration only from forwarded call, 2:
generate 2 CDR records (A leg + B leg), 3=both merged,4=merged with short a-leg,5=only b-leg billing if call is connected
 ivrbilling is 0: (server side) 1 CDR will be generated with total client call duration. The billing will be done after the final called user (the IVR
accessnumber when the call was not forwarded. Otherwise the final destination number)
 ivrbilling is 1: (client side) 1 cdr will be generated. The call duration will be set after B-leg call duration and billed accordingly
 ivrbilling is 2: (both) 2 (or more) cdr will be generated (when there was call forwarding action). The 2 cdr record can be billed separately after
different billing tables
 ivrbilling is 3: (both merged) 1 cdr will be generated, but the enduserprice can be loaded from different billing tables (2-leg merged)
 ivrbilling is 4: (both merged with short a-leg) 1 cdr will be generated, but the enduserprice can be loaded from different billing tables (2-leg
merged). The A leg duration is shortened (only the time spent with IVR until the call forward action)
 ivrbilling is 5: (server side if connected –mostly the same like ivrbilling 0) 1 CDR will be generated. If the call was not connected then all duration
will be billed (you can setup different billing for these calls by marking the entry as “is ivr call” and set the “called” to the access number. If the call
is connected, then the B-leg will be billed (possibly after a different billing packet)
4.6. GSM/SIM Platform
Skip this chapter if you don’t have VoIP-GSM gateways
4.6.1. SIM Packets
Id: database primary key. Autoincrement
Provider, type, subtype: the name of the packet
Owner: simowner in case of simpackets
Allowedpartners: applied when it is a simpacket
AbsPriorityPartner: this partner will have big priority on sims that belong to this packet
PriorityPartner: this partner will have increased priority on sims that belong to this packet
NopriorityPartner: this partner will have lowered priority on sims that belong to this packet
Filtering: determines how we check the blacklist and the known numbers