[asterisk-users] Billing pulses

[George Camilleri]

There are two types of ISDN line, Primary Rate Access (PRI) and Basic Rate 
Access (BRI). PRI has 30 (+ 1) channels, BRI has 2 (+1) channels. You are 
talking about BRI which consists of two 64 kbit/s data channels and 1 
signalling channel. In telephony, the two data channels are decoded and used 
as two voice channels. At the end of the decoding process and after passing 
through some interfacing hardware the voice channels end up in an analogue 
device such as a telephone set so that we humans can hear it.

The FXS hardware you invested in can be used for your analogue extensions. 
The FXO hardware is used to interface with analogue telco lines so if you 
want ISDN telco lines you will have to invest in BRI interface cards. 
(Google Asterisk ISDN BRI)

You then ask the telco to include Advice of Charge (AOC) in your ISDN setup. 
The AOC then is included somewhere in the Asterisk CDR, but I don't have 
direct experience of this. You can then get appropriate software to issue 
bills to telephone users.

This is as far as I know and have personal experience of. If anyone can add 
to it it will be appreciated.

George

----- Original Message ----- 
From: "Stefano Corsi" <scorsi at floo.it>
To: <dboyd at ignitetrx.com>; "Asterisk Users Mailing List - Non-Commercial 
Discussion" <asterisk-users at lists.digium.com>
Sent: Thursday, February 08, 2007 3:13 PM
Subject: Re: [asterisk-users] Billing pulses


>I must clarify my original message. Maybe confusion is due to my poor 
>english. So I'll make a list of statements:
>
> - Each ISDN line in Italy can be splitted in two analog lines
> - You can use those analog lines as normal analog lines
> - I have already invested in analog hardware (my fault of course) for both 
> FSX and FXO
> - ISDN hardware installed by the telco can, in Italy, be programmed to 
> send a "billing pulse".
> - I guess this billing pulse is sent on each of the two analog lines in 
> which a single ISDN line can be splitted (so there's no risk, I guess, for 
> double billing).
> - I'm considering if there's a small chance for me to avoid buying 
> additional hardware (ISDN cards or gateways) and have an accurate billing 
> using those analog lines resulting from splitting an ISDN line.
> - To get an accurate billing, I'm wandering if it's possibile to use 
> "billing pulse" provided by those analog lines.
> - I have full specifications of the "billing pulse" provided:
>
> frequency 
> .................................................................... 12 
> kHz ± 1%
> level 
> .......................................................................... 
> 200 mVrms on 200
> distortion................................................................... 
> < 5%
> pulse duration 
> .............................................................125 ± 25 ms
> pause duration 
> ................................................................> 180 ms
> period 
> .......................................................................> 
> 300 ms
>
> Do you think it's worth considering it?
>
> Rgds
> Stefano
>
>> > Bill them both.  We are talking about mere BRI's, right:-)  Good catch,
>> > David.  As others noted, billing pulse really applies to analogue lines
>> > only, and ISDN providers should always send status.
>> >
>> > Yuan Liu
>>
>>Thanks, Yuan
>>
>>
>>But my confusion came from the original post stating the use of ISDN
>>circuits for this  implementation.  Id ISDN is in fact the circuit of
>>choice for this app, I agree why wouldn't he simply use the cause codes
>>for billing purposes.  We have a lot of experience in telecommunications
>>billing, and have always found cause codes to be more than sufficient
>>even for weird tiers, and bizarre rounding functions.
>
>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>
>
>
> -- 
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.432 / Virus Database: 268.17.30/674 - Release Date: 2/7/2007 
> 3:33 PM
>
>